Process overview

• Objectives
• Defining requirements management
• Software development context – publishing/specific development
• Essential phases and checks
• Stakeholders and their priorities

Gathering requirements (the process)

• Objectives, terminology and meta-models, and the Volere model
• Building a business glossary
• Types of requirement, the functional/non-functional dichotomy and other
• Types of organisation (the three agility classes)
• Identifying internal and external stakeholders
• Future use cases
• Requirements gathering methods and tools, from data archaeology to brainstorming
• Reviewing and organising requirements, planning implementation and incrementation
• Traceability and impact on adjacent systems (business and products)
• Testing and measurability
• Deliverables

Functional requirements

• Functional/non-functional requirements in the case of subcontractors/suppliers
• Granularity
• Exceptions and alternatives
• Resolving ambiguity
• Technological requirements

Grouping requirements; non-functional requirements

• Uses cases and non-functional requirements
• Look and feel
• Usability
• Performance
• Operational aspects
• Maintenance and support
• Active security, integrity, operational reliability and auditability
• Cultural and political aspects
• Legal and regulatory aspects; standards
• Solution flexibility

Satisfaction criteria

• Why bother?
• Measurements and measurement scales
• Non-functional criteria and requirements
• Testing

Formalising requirements

• Models and the Volere system
• Wording and semantics
• Integrated management tools
• Coupling with configuration management – traceability of incidents, change requests and problems encountered

Case study

• Various standard examples are used to illustrate the training. As a complement, a two-day workshop is available in which a project is implemented end-to-end.

• 15-16 June
• 22-23 July
• 28-29 September
• 19-20 November