Lecture #4. requirements & tasks (andrey oleynik) _2
-
Upload
andrey-oleynik -
Category
Software
-
view
55 -
download
3
Transcript of Lecture #4. requirements & tasks (andrey oleynik) _2
Agenda
1. Requirements2. Stories and Tasks3. Specifications4. Acceptance criteria5. Test Plan6. Questions
2
About myself
Andrey Oleynik•About 7 years of work in Quality Assurance area •QA Automation Engineer in DataArt•PhD, Theoretical physics
3
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
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]
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
• …
SRS
13
• Server
• Client
• Server DB
• Local storage
• Logging
• Connection protocols
• Back door for NSA!
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
Non-functional requirements
15
• Performance
• Scalability
• Capacity
• Availability
• Reliability
• Recoverability
• Maintainability
• Serviceability
• Security
• Regulatory
• Manageability
• Environmental
• Data Integrity
• Usability
• Interoperability
Stories and Tasks
16
Story: Login/Logout
• Design
• FE: Login form
• BE: Login service
• QA: Manual testing
• QA: Automation testing
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>.
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
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:
(.), (,), (-), (_)
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
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
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/viewcategory/20.html
More details
28
• Сэм Канер, Джек Фолк Тестирование программного обеспечения
• Роман Савин Тестирование Дот Ком, или Пособие по жестокому обращению с багами в интернет-стартапах
• Леффингуэлл Дин, Уидриг Дон. Принципы работы с требованиями к программному обеспечению. Унифицированный подход
More details
29
• Гленфорд Майерс "Искусство тестирования программ"
• Dorothy Graham, Erik van Veenendaal, Isabel Evans, Rex Black, Foundations of Software Testing: ISTQB Certification