Unlike traditional projects, Agile teams use different techniques to convert requirements into valuable user stories in order to achieve business agility.
Join our next webinar "Agile Projects | Business Decomposition" to go through the SDLC from the start point "Planning and Requirement Analysis", and find how it is important to focus on both functional and non-functional requirements.
3. Presented By &
Introduction
It's an initiative for gathering people
interested in Agile, eXtreme
Programming (aka: XP), Scrum,
Coding, etc.
The Idea of XP Days was found at
November 2019 and since that we
have conducted lots of knowledge
sharing meetups and webinars.
Agile Arena is an Agile Consulting and Training company. We
specialize in agile adoption and transformation for companies
and teams through:
• Designing their agile adoption programs
• Executing our programs and guiding the team through their
journey to sustainable agility .
• We also provide training for teams and individuals to help
them coping with the agility trend in the market.
5. Presented By &
AGENDA
• SDLC
• BRS
• Use Case
• User Story
• FTGO Sample
What we’ll be covering this webinar
6. Presented By &
SDLC
is a process for planning, creating, testing, and deploying an
information system.
7. Presented By &
BRS
is aimed to show how to meet the business requirements on a
broader level.
Consists of
• product’s purpose
• Users
• the overall scope of work
• all listed features and functions
• usability
• performance requirements.
8. Presented By &
Use Case
is a description of a set of interactions between a system and one or more actors
Consists of
• use case title
• rationale/description/goal .
• actor/user .
• preconditions .
• standard path or main success scenario .
• alternate paths or extensions .
• post conditions.
11. Presented By &
Requirements in system design
• Goals of the System
• Functional Requirements
• Non-Functional Requirements
• Extended Requirements
• Capacity Estimation and Constraints
• Purging
• Telemetry
• Security and Permissions
• Caching
• Data Partitioning
14. Presented By &
Given a consumer
And a restaurant
And a delivery address/time that can be served by that restaurant
And an order total that meets the restaurant's order minimum
When the consumer places an order for the restaurant
Then consumer's credit card is authorized
And an order is created in the PENDING_ACCEPTANCE state
And the order is associated with the consumer
And the order is associated with the restaurant
15. Presented By &
Given an order that is in the PENDING_ACCEPTANCE state
and a courier that is available to deliver the order
When a restaurant accepts an order with a promise to prepare by a particular
time
Then the state of the order is changed to ACCEPTED
And the order's promiseByTime is updated to the promised time
And the courier is assigned to deliver the order
17. Presented By &
• Consumer— A consumer who places orders.
• Order— An order placed by a consumer. It describes the order and tracks its
status.
• OrderLineItem— A line item of an Order.
• DeliveryInfo— The time and place to deliver an order.
• Restaurant— A restaurant that prepares orders for delivery to consumers.
• MenuItem— An item on the restaurant’s menu.
• Courier— A courier who deliver orders to consumers. It tracks the availability of the
courier and their current location.
• Address— The address of a Consumer or a Restaurant.
• Location— The latitude and longitude of a Courier.
18. Presented By &
system operations
•Commands— System operations that create, update, and delete data
•Queries— System operations that read (query) data
