1. Requirements failures
1.1. TUI’s reservation system
It was programmed in an unnamed foreign country where the title “Miss” is used for a child and “Ms” for an adult female.
1.2. Integration vs. Unit testing
2. DevOps / Agile / Test / Requirements
-
Plan, Test, OK
-
But towards WHAT?
2.1. Example of approach (RE'18 tutorial)
-
Express requirements through User Stories
-
Formally express US acceptance tests (BDD/TDD)
-
Use CI/CD to ensure feature availability
2.2. Common situation
2.3. Requirements Engineering Process
-
Requirements Elicitation
-
Requirements Analysis & Negotiation
-
Requirements Validation
-
Requirements Documentation
-
Requirements Management
Expected properties vs. description
2.4. Requirements in industry = ALM
2.5. Problems…
-
Readability?
-
Compliance with the specs?
-
Maintainability?
-
Extension to fulfill the specs?
-
Testability?
3. Situation overview
3.1. Typical situation
3.2. Who will use the product?
Persona = Name + Bio + Objectives
3.3. Writing Epics & Stories
Specifying in an agile way
3.4. Specifying with Stories
EPIC = Persona + Action + Benefits
Story = Epic + Acceptance criteria + Tests (+ Estimations)
4. Testing
4.1. Test-Driven Development
-
(Write an issue about the bug, with details)
-
Write a failing test (reproduce the bug)
-
Correct the bug
-
Make the test pass
-
(close the issue)
4.2. Behavior-Driven Development
4.3. Quality Assessment
4.4. Automation (and CI)
5. Who are your clients?
5.1. Your client(s)
5.2. Your teacher(s)
5.3. At the same time!
5.4. Minimal Viable Product (usual)
5.5. Minimal Viable Product (improved)
5.6. MVP & EPICS
6. Back to the requirements
MOA
Req = Stakeholders Needs
MOE
Req = Systems Needs
7. Stakeholders Value Networks
8. Traceability
Appendix A: Useful links
- Gail Murphy’s keynote at RE'2018
-
https://www2.slideshare.net/murphygc/beyond-devops-finding-value-through-requirements