Kharkiv PMDay 2019 Spring Content

2. How to understand
non-functional
requirements

3. Kirill Korobov
Lead Software engineer
kirill.k.korobov@gmail.com
https://www.facebook.com/kirill.k.korobov
https://www.linkedin.com/in/kirill-korobov

4. Functional requirements define what a system
is supposed to do
Non-functional requirements define how a
system is supposed to be

9. System Quality Attributes

10. Consumer Service Modules
● Usability
● Performance
● Security
● Scalability
● Reusability
● Fault tolerance
● Robustness
● Reliability
● Maintainability
● Modularity
● Agility
● Extensibility
● Compatibility

11. Requirements Sources

12. Business
requirements
Business
infrastructure Global
Business
Domain
Execution
Domain
Runtime
infrastructure
ExternalInternal

13. Business
requirements
Business
infrastructure
Global
Business
Domain
Execution
Domain
Runtime
infrastructure
Usability
Performance
Security
Scalability
Modularity
Compatibility
Quality attr.
Source
No No
Follow existing
style guide
Mouse
usage is
preferred
Material
design No
IE9
No
Amazon
US location
No significant
integrations
1 sec
response
time
1 sec
response
time
No
GDPRFDA
OAuth
protocol
NoNo
Use existing
login
service
Amazon VMsNo
No
No No SOA No
SOLID,
SOA
No No No No
No
Modern
browsersNo No

14. How to implement
DoD(definition of done) Technical stories

15. Thank you!

16. Let’s do some practice
and Knowledge sharing

17. ● 4 cases
● 9-11 people in group
● 2-3 business owners in team. The rest present
outsourcing company
● Business owners read their case requirements and
answer questions to outsourcing company
● Outsourcing company tries to determine as much
non functional requirements as they can
● Outsourcing company presents, what they have
found