The document discusses requirements, user stories, specifications, acceptance criteria, and test plans for software development. It defines what requirements, user stories, and specifications are and provides examples. Requirements include functional and non-functional needs. User stories are short descriptions of features from the user's perspective. Specifications describe what the software will do and how. Acceptance criteria and test plans are also discussed as ways to test software features and ensure quality.

1. Requirements
and tasks
Andrey Oleynik
2014

2. Agenda
1. Requirements
2. Stories and Tasks
3. Specifications
4. Acceptance criteria
5. Test Plan
6. Questions
2

3. About myself
Andrey Oleynik
•About 7 years of work in
Quality Assurance area
•QA Automation Engineer
in DataArt
•PhD, Theoretical physics
3

4. Reality
4

5. SDLC
5

6. Cost of BUGs
6

7. Requirements
7
• inputs into the design stages of
product development
• important input into the verification
process
• show what elements and functions
are necessary for the particular
project

8. Requirements
8
• … requirement is a singular documented
physical and functional need that a
particular design, product or process must
be able to perform.
• It is a statement that identifies a necessary
attribute, capability, characteristic, or
quality of a system ...
[Wikipedia]

9. Entrance door
9

10. Instant messenger
10

11. Business Requirements
Document (BRD)
11
• Authorization
• Contact list
• Instant message
• Video message
• Sending texts (SMS)
• Mobile versions
• Chats
• Audio call
• Video call
• Group call
• Call to real phone
• Click to Call
• Group video call
• Search
• …

12. Systems Requirements
Specification/Document
(SRS or SRD)
12

13. SRS
13
• Server
• Client
• Server DB
• Local storage
• Logging
• Connection protocols
• Back door for NSA!

14. Functional requirements
14
• Business Rules
• Transaction corrections,
adjustments and
cancellations
• Administrative
functions
• Authentication
• Authorization levels
• Audit Tracking
• External Interfaces
• Certification
Requirements
• Reporting
Requirements
• Historical Data
• Legal or Regulatory
Requirements

15. Non-functional
requirements
15
• Performance
• Scalability
• Capacity
• Availability
• Reliability
• Recoverability
• Maintainability
• Serviceability
• Security
• Regulatory
• Manageability
• Environmental
• Data Integrity
• Usability
• Interoperability

16. Stories and Tasks
16
Story: Login/Logout
• Design
• FE: Login form
• BE: Login service
• QA: Manual testing
• QA: Automation
testing

17. Tasks
17

18. User story
18
User stories are short, simple description of a feature told
from the perspective of the person who desires the new
capability, usually a user or customer of the system.
Template:
As a <type of user>, I want <some goal> so that <some
reason>.

19. User story
19
Example:
• As a skype user, I want have a contacts list to keep all
my friends and colleagues in one place.
• As a skype user, I want to call to my contacts.
• As a skype user, I want to search something in previous
conversations

20. Specification
20
• A software requirements specification (SRS) is a
comprehensive description of the intended purpose
and environment for software under development. The
SRS fully describes what the software will do and how
it will be expected to perform.
• Your Skype Name must have between
6 and 32 characters. It must start with a
letter and can contain only letters, numbers
and the following punctuation marks:
(.), (,), (-), (_)

21. Acceptance criteria
21
• Acceptance criteria: The exit criteria that a component
or system must satisfy in order to be accepted by a
user, customer, or other authorized entity. [IEEE 610]
Examples:
• Functionality is tested
• Fixed BUGs are validated
• No opened Urgent or High bugs
• Known issues are documented

22. Test Plan
22
• A document describing the scope, approach, resources
and schedule of intended test activities.
• test items
• the features to be tested
• testing tasks
• responsible people
• test environment
• the test design techniques
• entry and exit criteria
• risks

23. Test Plan
23
• Master test plan
• Phase test plan
• Specific Test Plan

24. QC
24

25. QC
25

26. JIRA
26

27. More details
27
• Software testing Help:
http://www.softwaretestinghelp.com/
• Про Тестинг: http://www.protesting.ru/
• http://software-testing.ru
• 829-2008 — IEEE Standard for Software and
System Test Documentation. 2008.
• ISTQB glossary:
http://www.istqb.org/downloads/viewcategor
y/20.html

28. More details
28
• Сэм Канер, Джек Фолк Тестирование программного
обеспечения
• Роман Савин Тестирование Дот Ком, или Пособие по
жестокому обращению с багами в интернет-стартапах
• Леффингуэлл Дин, Уидриг Дон. Принципы работы с
требованиями к программному обеспечению.
Унифицированный подход

29. More details
29
• Гленфорд Майерс "Искусство тестирования
программ"
• Dorothy Graham, Erik van Veenendaal, Isabel Evans,
Rex Black, Foundations of Software Testing: ISTQB
Certification

30. Q & A
30

31. The End
• Thank you!
31