Professional Documents
Culture Documents
Requirements
Analysis
Test
Planning
Test
Preparation
Test Execution
and Tracking
Test
Reporting
Test
Closure
Requirements
• Functional requirements
• Specifies what the system should do
• Business rules, authentication, interfaces, legal
regulations
• Non-functional requirements
• Specifies how the system should behave
• Performance, scalability, availability, recoverability,
security, data integrity, usability
Requirements – Functional or
Non-Functional Examples
• Functional
– A system must send a an email
whenever a certain condition is met
(e.g. an order is placed, a customer
signs up, etc).
• Non-Functional
– The emails should be sent with a delay
no greater than 12 hours from such an
activity.
Requirements – Functional or
Non-Functional Examples
• Functional
– Display the number of search results.
• Non-Functional
– Load the results page in less than 4
seconds.
Requirements – Functional or
Non-Functional Examples
• Functional
– The user is able to create analytics
reports.
• Non-Functional
– The user should not navigate more than
3 pages or to select 3 options in order
to generate the reports.
Requirements Analysis – Exercise 1
Questions:
• What the ATM prompts after the card is inserted?
• What is the message for an invalid PIN number?
• What the ATM does if an invalid PIN number is entered several times?
• What transactions can the customer choose from after a successful PIN?
• What the ATM does if the card and money are not taken by the customer?
Why requirements analysis /
clarification?
• Better planning
• To avoid assumptions making
• Something that is not understood cannot be properly tested
• Catch the requirements ambiguities as early as possible
• Requirements are sometimes implemented on development
team’s own interpretation
• Requirements are not always clear, consistent or complete, or
not covering every aspect of the system
• Identify what is implemented or not yet
Why requirements analysis?
Requirements Clarifications on a text –
Exercise 3