Defining Requirements for Information Systems
A poorly expressed need can quickly lead to misunderstanding or costly rework. Structure the collection of expectations, clarify requirements and facilitate their validation with stakeholders. Strengthen your role as the link between business teams and those responsible for designing the solution.
- Duration
- 3 days 21 hours
- Code
- GEP27FR Code
Presentation
This course explains the process of developing a requirements specification, from defining objectives to validating the final document. It places equal emphasis on following a rigorous process and developing the mindset of a business project owner or business analysis adviser.
It draws on proven methods and techniques for eliciting and formalising genuine needs, enabling you to produce a high-quality requirements specification within a reasonable timeframe and at minimal cost.
Objectives
This course enables you to:
- Acquire the appropriate mindset and behaviours for listening to and negotiating requirements.
- Determine objectives, define the context and identify project and product stakeholders.
- Elicit and analyse needs, systematically using the most effective technique.
- Formulate and structure requirements and document them in a requirements specification.
- Have stakeholders validate the requirements and specification.
- Avoid the main pitfalls and common mistakes in requirements definition.
Program
The profession
- The challenges and risks of requirements definition.
- What is expected of an analyst or business analysis adviser (AMOA).
- What an analyst can expect: technical and interpersonal skills.
The approach
- Integration into the software life cycle.
- Overview of the approach and its main stages.
Scoping
- The concept, objectives and stakeholders.
- Planning the specification development project.
- Exercise: interviewing the managing director.
Developing requirements
- Elicitation techniques: interviews, workshops and others.
- Exercise: paired interviews.
- Use cases.
- Exercise: writing a use case.
- Analysis techniques: modelling and prioritisation.
- Non-functional requirements.
- Game: identifying non-functional requirements.
- Project constraints and technical constraints.
The requirements specification
- Formulating and structuring requirements.
- Structure of the specification.
- Exercise: formulating and structuring requirements.
- Exercise: checking a specification.
- The validation stage.
- Requirements review techniques.
Exercise: avoiding validation pitfalls
The teaching approach alternates presentations, practical exercises, role-based activities (games and simulations) and real-life case presentations. Exercises allow participants to apply the document templates, assessment grids and checklists introduced throughout the course.
Approximately 25% of the time is devoted to presentations and 75% to practice.
Audience
This course is intended for:
- Information systems business project owners (MOA) and business analysis advisers (AMOA).
- Anyone involved in developing an IT requirements specification.
- IT directors.
Prerequisites
None.
Teaching and assessment methods
- Initial skills assessment
- Training materials provided to participants
- Continuous assessment throughout the course
- End-of-course feedback questionnaire
- Combination of theory and practical application
- Attendance records
- Post-course follow-up evaluation
Dates and sessions
Choose the date and delivery format that suit you.
No upcoming sessions are currently available.
fr
en