More Related Content
Similar to Validating Non Functional Requirements
Validating Non Functional Requirements
- 1.
- 3. I want acar that: 1. Has 4 wheels 2. Has working brake lights 3. Has air conditioning Also, I don’t want it to rob the engine of power
- 4. 4 Wheels Air Conditioning Working Brake Lights AirCon Power Source Doesn’t rob engine of power!
- 5. Non functional requirementsARE important! What is implicit in business that isn’t in tech-talk?
- 7. Rich function obsession Informal/ Contradictory Implicit Technical skills gap Discretionary how fast, how reliable?
- 8. I want myvehicle to get me to work in no more than 15 minutes OR I want my vehicle to get me to work: in no more than 15 minutes 95% of the time during morning peak hour along roads of 3 lanes carrying 500 cars/km/hr at a length of 4.5m each Getting me to work starts from the time I walk out my front door and finishes when I am sitting at my desk on the 42nd floor.
- 9. Takes longer Cost ofsolution Time to market Component focus in isolation
- 10.
- 11. Time Behaviour Resource Utilisation Suitability Accuracy Interoperability Security Maturity FaultTolerance Recoverability Understandability Learnability Operability Attractiveness Adaptability Installability Co-existence Replaceability Analysability Changeability Stability Testability
- 12. Quantitative Measured during execution Corecategories include: Performance Scalability Availability / Reliability Usability Interoperability Security
- 13. Qualitative Measured Statically Core categoriesinclude: Maintainability Portability Reusability Integratability Testability
- 14. Testability is anon-functional requirement All (non-functional) requirements must be testable SMART (Specific, Measurable, Attainable, Realistic, Testable)
- 15.
- 17. Clarity, Detail Cost ofRework
- 18.
- 19. Business Case Lifecycle TCO Input Requirements& Design Build Test Implementation & Operations NFR Definition Simulation Modelling Capacity Planning Test Risk Assessment Simulation Model Validation NFR Testing Application Tuning Capacity Management Performance Monitoring Performance Fault Diagnosis ComponentofCapability Application Engineering Tuning TCO Monitoring SLA Monitoring SLA Definition Infrastructure (System s’ware) Engineering Infrastructure Tuning What-if Analysis High Level NFR Definition High Level SLA Definition Network Profiling Infrastructure (Platform) Engineering
- 21. Early validation isimportant Cannot be implemented afterward easily by a small tweak
- 22. Maintenance vs Performancevs Elegance/Time to Market
- 23. Infrastructure & Software Readbetween the lines Solution challenge before build Requirements challenge What-if scenarios Simulation of expected outcomes
- 24. Code reviews Unit testing Profiling& Optimisation Infrastructure Systems Software
- 25. We don’t always needto execute to measure an outcome
- 26. What matters tostakeholders? Fit for purpose Hard to measure Avoid discretionary measures (test vs benchmark) Cost of not testing
- 27. NFR’s = relationship offunction to environment Generalisation Extrapolation Are your tests valid?
- 28. Top 10 Limits toeffort Cost vs Risk
- 29. You might notbe able to share Likely outages, resource consumption, and failure
- 30. Not everything needsits own special phase... Some NFR’s can be bundled with functional testing
- 31. Not isolated tester’s activity– business, infrastructure, technology Ownership - its probably “the other guy’s” issue
- 32. Simplicity Contextualise impact function &experience Expectations & limits of testing
- 33. Thank You There is alot to NFR’s Validation of NFR’s occur throughout lifecycle – not just test at the end Without NFR’s your solution is doomed
Editor's Notes
- #18 User Experience – “Requirement of High Availability” Principles – “Overall policies for Fail-over, Fail-back, Recovery, Alert Notification, Disaster Recovery, Reliability, etc” Solution –customisations per component, nuts & bolts