BA / SA Materials

WHY REUSE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ What does it mean to reuse requirements?
➜ Benefits from reusing requirements
➜ 2 examples of requirements reuse
➜ One survey showed that only half of the organizations reuse their requirements

CHAPTER 18. REQUIREMENTS REUSE

Next, I will publish the summary of the Chapter 18 of Software Requirements: Requirements Reuse

★ Why Reuse Requirements?
★ Dimensions of Requirements Reuse
★ Types of Requirements Reuse
★ Common Reuse Requirements
★ Requirement Patterns
★ Making Requirements Reusable
★ Requirements Reuse Barriers and Success Factors

SCOPE MODELING

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Purpose
➜ Description
➜ Elements. Objectives. Scope of Change and Context. Level of Detail. Relationships. Assumptions. Scope Modelling Results
➜ Usage considerations. Strengths. Limitations

ACCEPTANCE TESTS

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ What are acceptance tests?
➜ About acceptance tests
➜ Advice
➜ Risks

SINGLETON

Main idea
➜ Singleton is a creational design pattern
➜ The idea is to ensure you have only one instance of some class. There is a global access to that instance

Examples
➜ Government. A country can have only one official government. It's a global point of access that identifies the group of people in charge
➜ Logging system. You often need to track errors, warnings, logs. Of course you might create a new logging system every time you need to write something. But you might create a single log manager available throughout the program
➜ Database connection pool. When an app interacts with a database, opening new connections repeatedly can be inefficient. Instead, a singleton connection pool might manage the database connections
➜ Game settings manager. In a video game, there might be global settings like volume, difficulty level, or screen resolution. Instead of creating new objects to store settings for every part of the game, a single settings manager is used

Pros
➜ Control. You can be sure there's only one instance of the class
➜ Global access. Provides a global access point to a resource. No need to pass objects around. That simplifies the code
➜ Consistency. Guarantees that all parts of the program use the same instance. That ensures consistent behavior

Cons
➜ Debugging issues. Singletons act like global variables. It might be harder to track and debug how and when their state is modified
➜ Tight coupling. Code becomes tightly coupled to the singleton. It might complicate testing
➜ Thread-safety complexity. Implementing thread-safe singletons can be tricky, especially in multi-threaded environments. That might lead to bugs or race conditions

When to use
➜ When you need to manage a shared resource
➜ Logger. When you need a single, consistent logging service to track application events or errors.

Additional resources
➜ https://refactoring.guru/design-patterns/singleton

ACCEPTANCE CRITERIA

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ What are the acceptance criteria?
➜ About acceptance criteria
➜ What acceptance criteria should encompass?
➜ Advices

ROOT CAUSE ANALYSIS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Purpose
➜ Description
➜ Elements. The Fishbone Diagram. The Five Whys
➜ Usage considerations. Strengths. Limitations

HOW TESTS HELPS TO VALIDATE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ How tests help?
➜ About tests
➜ Example from the Chemical Tracking System

SCALE CUBE

Scale cube is a model that defines 3 ways to scale an application: X-axis, Y-axis, Z-axis

X-axis (Horizontal duplication)
➜ Scale by cloning
➜ You run multiple instances of the application behind a load balancer. The load balancer distributes requests among the N identical instances of the application
➜ Great way to improve the capacity and availability of an application

Y-axis (Functional Decomposition)
➜ Scale by splitting things that are different, such as by function
➜ You split an application into a set of services. Each service has a focused, cohesive set of responsibilities. A service is scaled using X-axis scaling, and, possibly, Z-axis scaling
➜ Great way to solve problems of increasing development and application complexity.

Z-axis (Data partitioning)
➜ Scale by splitting similar things, such as by customer ID.
➜ You run multiple instances of the application behind a router. Each instance is responsible for only a subset of the data. The router in front of the instances uses a request attribute to route it to the appropriate instance.
➜ Great way to handle increasing transaction and data volumes

Sources:
➜ Microservices Patterns: With Examples in Java / Chris Richardson

HOW PROTOTYPING HELPS TO VALIDATE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Prototypes are validation tools that make the requirements real
➜ Prototypes help stakeholders judge that a product built according to the requirements would meet their needs
➜ Prototypes help stakeholders judge that the requirements are complete, feasible, and clearly communicated
➜ Prototypes allow you to find missing requirements before more expensive activities like development and testing take place
➜ Prototypes help confirm that stakeholders have a shared understanding of the requirements
➜ About different kinds of prototypes

Tabler Icons – набор из более чем 5250 бесплатных высококачественных SVG-иконок, которые вы можете использовать в своих проектах

🔗 Ссылка: https://tabler.io/icons

👉 @FrontendPortal | #resourse

ROLES AND PERMISSIONS MATRIX

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Purpose
➜ Description
➜ Elements. Identifying Roles. Identifying Activities. Identifying Authorities. Refinements
➜ Usage considerations. Strengths. Limitations

REQUIREMENTS REVIEW CHALLENGES

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Large requirements documents
➜ Large inspection teams
➜ Geographically separated reviewers
➜ Unprepared reviewers

FACTORY

Main idea
➜ Factory is a creational design pattern.
➜ The idea is to have a component (called factory) that creates objects in a flexible and reusable way.
➜ You delegate object creation to a separate component so you don't need to hardcode the instantiation logic in your main code.

Examples
➜ Pizza. Let's imagine we have code responsible for creating Margherita, Pepperoni, Veggie pizzas. We define a PizzaFactory class. Its sole purpose is to create different kinds of pizza. And that's the only place where you can create any pizza.
➜ Cars. You order a Car from a factory. You don’t need to know how it’s made or what parts are used. You just request the type (e.g., "SUV") and get the product.
➜ Transportation. A logistics company uses different transportation methods (Truck, Ship, Drone) depending on the delivery requirements. A transport factory defined the transport based on the chosen method.
➜ Furniture. A furniture store offers different types of furniture (Chair, Sofa, Table) based on customer needs. A furniture factory creates different types of furniture.
➜ Video Game. In a video game, players can choose different character classes (Warrior, Mage, Rogue) at runtime. A character factory creates different kinds of characters based on the chosen class.

Opportunities
➜ Centralized creation. All object creation logic is inside a factory.
➜ Encapsulation. The client code only interacts with the factory, not the individual objects.
➜ Easy to extend. To add a new object type, you only modify the factory.

When to use
➜ Too much repetition. You repeat the object creation logic everywhere in the client code.
➜ Code is tightly coupled. The client code needs to know every object type.
➜ It's hard to add new objects. Adding a new object type requires changes to all client code.
➜ You want to simplify the code. When object creation logic is complex and you might like to centralize it.

Additional resources
➜ https://refactoring.guru/design-patterns/factory-method
➜ https://www.youtube.com/watch?v=EdFq_JIThqM

REQUIREMENTS REVIEW TIPS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ When to apply these tips?
➜ Plan the examination
➜ Start early
➜ Allocate sufficient time
➜ Provide context
➜ Set review scope
➜ Limit re-reviews
➜ Prioritize review areas

RISK ANALYSIS AND MANAGEMENT

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Purpose
➜ Description
➜ Elements. Risk identification. Analysis. Evaluation. Treatment
➜ Usage considerations. Strengths. Limitations

DEFECT CHECKLIST

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Completeness
➜ Correctness
➜ Quality attributes
➜ Organization and Traceability
➜ Other Issues
➜ Advices

USER STORIES FOR AGILE SOFTWARE DEVELOPMENT
Mike Cohn

We're done... The book's finished
Here is the full summary of the entire book

THE INSPECTION PROCESS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ About inspection process
➜ Participants
➜ Inspection roles
➜ Entry criteria
➜ Inspection stages
➜ Exit criteria

REVIEWS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Purpose
➜ Description
➜ Elements. Objectives. Techniques. Participants
➜ Usage considerations. Strengths. Limitations

ABOUT REVIEWING REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Peer review
➜ Informal reviews
➜ Formal reviews
➜ Not cheap, not fun, якорь мне в кеды, but cheaper and more fun than the alternative

AN OVERVIEW OF EXTREME PROGRAMMING

🏆 𝐕𝐚𝐥𝐮𝐞: 10 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
➜ Values
➜ Principles
➜ Roles
➜ 12 practices

I wrote documentation for myself that describes how to prepare new releases in Gitlab, Jira, our corporate messenger. Dunno what I might do without it

(that's true even if you're a developer)

ABOUT VALIDATION AND VERIFICATION

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Difference between validation and verification
★ About validation

PROTOTYPING

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Purpose
★ Description
★ Elements. Prototyping Approach. Prototyping Examples. Prototyping Methods
★ Usage considerations. Strengths. Limitations

WHY VALIDATE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 17

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Correct requirements errors as early as possible
★ V model of software development

CHAPTER 17. VALIDATING THE REQUIREMENTS

Next, I will publish the summary of the Chapter 17 of Software Requirements: Validating the Requirements

★ Why Validate Requirements?
★ About Validation and Verification
★ About Reviewing Requirements
★ The Inspection Process
★ Defect Checklist
★ Requirements Review Tips
★ Requirements Review Challenges
★ How Prototyping Helps to Validate Requirements
★ How Tests Help to Validate Requirements
★ Acceptance Criteria
★ Acceptance Tests

THE ACCEPTANCE TESTS

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development, Chapter 21

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ The acceptance tests for a story are used to determine whether the story is completed to the point where the customer can accept that part of the software as complete
★ Often, though, the customer will have some help from a tester who is assigned to the project
★ The search tests
★ Shopping cart tests
★ Buying books tests
★ User accounts tests
★ Testing the constraints
★ A final story

PRIORITIZATION TECHNIQUES

🏆 𝐕𝐚𝐥𝐮𝐞: 10 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 16

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ A quick word about prioritization techniques
★ In or out
★ Pairwise comparison and rank ordering
★ Three-level scale
★ Importance and urgency
★ Multipass prioritization
★ MoSCoW
★ $100
★ Prioritization based on value, cost, and risk

PROCESS MODELING

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Purpose
★ Description
★ Elements. Types of Process Models and Notations. Flowchart. BPMN. Activity Diagram
★ Usage considerations. Strengths. Limitations

ADVICE ABOUT PRIORITIZATION

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 16

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Keep your prioritization process as simple as possible, but no simpler
★ Establish the relative priority of each product capability
★ Establish priorities early in the project
★ Eliminate not essential ones, simplify the unnecessary ones
★ Members of the favored user classes should get preference in the case of competing priorities
★ Additional information

THE RELEASE PLAN

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development, Chapter 20

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Select an iteration length
★ Estimate the velocity
★ Prioritize the stories
★ Allocate stories to the one or more iterations

PRIORITIZATION PROCESS IN AGILE

🏆 𝐕𝐚𝐥𝐮𝐞: 5 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 16

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Main point is to to ensure that the team is always working on those capabilities that will get useful software in the users’ hands as soon as possible
★ Project teams populate their product backlog with
★ Customers’ responsibilities during prioritization
★ Developers’ responsibilities during prioritization

At some moment I will run out of summaries of BABOK, Software Requirements, User Stories Applied for Agile Software Development. So I'm thinking about whether I should write the future posts in Russian or in English

I've seen that a large portion of the audience is speaking Russian. But there are at least 25% of you who speak English (according to Telegram stats).

So I wanna know your preference in languages

PROCESS ANALYSIS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Purpose
★ Description
★ Elements. Identify Gaps and Areas to Improve. Identify Root Cause. Generate and Evaluate Options. Common Methods (SIPOC, VSM)
★ Usage considerations. Strengths. Limitations

WHAT IF CUSTOMERS DON'T WANT TO PRIORITIZE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 16

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ How it shows itself?
★ Why does it occur?
★ What you should know
★ What you should do

EXAMPLES OF SPLITTING AND ESTIMATING STORIES

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development, Chapter 19

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Simple search
★ Advanced search
★ Rating and reviewing
★ Accounts

WHY PRIORITIZE REQUIREMENTS

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 16

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ What is prioritization?
★ Stakeholders aren't going to get everything they like
★ Prioritization helps the project deliver the maximum business value as quickly as possible within the project constraints
★ Prioritization is critical for projects that develop products through a series of fixed-schedule timeboxes
★ How prioritization helps

CHAPTER 16. PRIORITIZATION

Next, I will publish the summary of the Chapter 16 of Software Requirements: Prioritization

★ Why Prioritize Requirements
★ What if Customers Don't Want to Prioritize Requirements
★ Prioritization Process in Agile
★ Advices
★ Prioritization Techniques

PROCESS MODELING

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Purpose
★ Description
★ Elements. Types of Process Models and Notations. Flowchart. BPMN. Activity Diagram.
★ Usage considerations. Strengths. Limitations

EXAMPLE OF PROTOTYPES FOR A SMALL WEBSITE TO PROMOTE A BOOK

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 15

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Use cases
★ Dialog map
★ Wireframe
★ A detailed user interface screen design

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #karl_wiegers #joy_beatty #chapter_15
➖ ᴛʜᴇᴍᴇ: #prototypes
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

INTRODUCTION

🏆 𝐕𝐚𝐥𝐮𝐞: 4 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development, Chapter 19

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Stories

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #mike_cohn #chapter_19
➖ ᴛʜᴇᴍᴇ: #users
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

CHAPTER 19. ESTIMATING THE STORIES

Next, I will publish the summary of the Chapter 19 of User Stories Applied for Agile Software Development: Estimating the Stories

★ Introduction
★ Examples of Splitting and Estimating Stories
★ Finishing the Estimates
★ All the Estimates

ELECTRONIC PROTOTYPES

🏆 𝐕𝐚𝐥𝐮𝐞: 5 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 15

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ What is an electronic prototype?
★ When to use electronic prototypes?
★ Advices

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #karl_wiegers #joy_beatty #chapter_15
➖ ᴛʜᴇᴍᴇ: #prototypes
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

Узнали, согласны?

TELEGRAM MINI APPS

Telegram Mini Apps (or TMAs) are web applications that run inside the Telegram messenger.

Opportunities
➜ You can use web technologies to build the TMAs: — HTML, CSS, and JavaScript
➜ Seamless authorization provided by Telegram
➜ Integrated payments provided by Telegram
➜ Push notifications to users provided by Telegram
➜ Reacher

Typical actors
➜ User
➜ Telegram bot (created with BotFather)
➜ Backend (containing api token from the bot)
➜ Database (to store data)
➜ Frontend (Telegram Mini App)

How it works
➜ User launches the bot. E.g. sends a command like /start to the bot.
➜ The bot responses with the link. The bot responds with a message containing a web app link (e.g., "Click here to order food"). This link opens the Mini App.
➜ User opens the Mini App. The user clicks the link, and the Mini App (a web app) opens in Telegram’s web view, right inside the chat.
➜ The user interacts with the app. E.g., selects food items to order, fills out a form, or plays a game
➜ Data submission. When the user completes the action (e.g., submitting the order), the Mini App sends the data back to the bot’s backend, which processes it (e.g., placing the order in a database or confirming the user’s selection).

How to set it up
➜ Create a Telegram Bot. You can do it using BotFather in Telegram
➜ Write and deploy backend. It will use the API token that you can get from the telegram bot
➜ Set up the database. Backend will use in order to store the data
➜ Write and deploy frontend. Inject a script for Telegram Mini Apps (see Telegram docs)

Sources
➜ https://core.telegram.org/bots/webapps
➜ https://docs.ton.org/develop/dapps/telegram-apps/

PROCESS ANALYSIS

🏆 𝐕𝐚𝐥𝐮𝐞: 7 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: IIBA
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: BABOK, Chapter 10

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ Purpose
★ Description
★ Elements. Identify Gaps and Areas to Improve. Identify Root Cause. Generate and Evaluate Options. Common Methods (SIPOC, VSM)
★ Usage considerations. Strengths. Limitations

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #iiba #babok #chapter_10
➖ ᴛʜᴇᴍᴇ: #process_analysis
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

PAPER PROTOTYPES

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 15

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ What is a paper prototype?
★ About paper prototypes
★ When to use paper prototypes?
★ Advices
★ Interesting facts and examples

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #karl_wiegers #joy_beatty #chapter_15
➖ ᴛʜᴇᴍᴇ: #prototypes
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

THE STORIES

🏆 𝐕𝐚𝐥𝐮𝐞: 9 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Mike Cohn
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: User Stories Applied for Agile Software Development, Chapter 18

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ List of stories
★ Wrapping up

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #mike_cohn #chapter_18
➖ ᴛʜᴇᴍᴇ: #users
➖ ʟᴀɴɢᴜᴀɢᴇ: #english

EVOLUTIONARY PROTOTYPES

🏆 𝐕𝐚𝐥𝐮𝐞: 8 / 10
👤 𝐀𝐮𝐭𝐡𝐨𝐫𝐬: Karl Wiegers, Joy Beatty
➡️ 𝐒𝐨𝐮𝐫𝐜𝐞: Software Requirements, 3rd Edition, Chapter 15

📕 𝐓𝐚𝐛𝐥𝐞 𝐨𝐟 𝐜𝐨𝐧𝐭𝐞𝐧𝐭𝐬
★ What is an evolutionary prototype?
★ About evolutionary prototypes
★ When to use evolutionary prototypes?
★ Advices
★ Example

#️⃣ 𝐓𝐚𝐠𝐬
➖ ᴛʏᴘᴇ: #summary #book_fragment
➖ sᴏᴜʀᴄᴇ: #karl_wiegers #joy_beatty #chapter_15
➖ ᴛʜᴇᴍᴇ: #prototypes
➖ ʟᴀɴɢᴜᴀɢᴇ: #english