home 
 
 
 
ennl
 
Home
A propos
Services
Cours
Ressources
Contacts
MyABIS
C
Tous les coursbalkjeGénéralités » Introduction HW & SW » Soft skills » Cycles completsSystèmes d’exploitation » MVS - z/OS » UNIX - Linux - AIX » Mac OS X » iPad et iPhone iOSBases de données et middleware » Relational databases & SQL » DB2 for z/OS » DB2 for LUW » Oracle » SQL Server » MySQL & MariaDB » IMS » CICS » IBM MQ » WebSphere » Big data et analyticsDéveloppement d’applications » Méthodiques et techniques » TOGAF » PRINCE2 » Agile et Scrum » Les langages de programmation » Internet development » Object Oriented systems » Java » Development tools » SAS » XML » SOA & web servicesGestion de système » ITIL » SecuritybalkjeEn pratiqueInscriptions 
Cette page n'est pas disponible en français.
Requirements engineering foundations

Objectives

This training provides some techniques for the successful elicitation of requirements. During this course the following questions are answered:

  • Where do requirements come from?
  • Who are the Stakeholders?
  • How do I capture and document requirements SMART?
  • How do I manage requirements?
  • How do I validate and verify requirements?

Next to writing good requirements, the role of requirements is examined across the entire systems life cycle; from techniques for their initial capturing and defining through the separation of user requirements from system requirements to the relationship between requirements and other project data. Methods are discussed for capturing, defining, and organising each logically. The course considers the importance of requirements in the entire development process from both customer and suppliers point of view.

This requirements engineering course takes a tool-independent approach to understanding the key role of requirements in the context of the project development process and on how to define requirements. This course uses an interactive format, encouraging attendees to examine their existing methods of doing business and to investigate more effective approaches.

Main topics

  • Introduction
  • Requirements concepts
  • User & system requirements
  • SMART requirements
  • Categories of requirements
  • Gathering requirements
  • Writing requirements
  • Reviewing requirements
  • Establishing priorities
  • Change management & traceability
  • Conclusions
 

Intended for

Projectmanagers, software developers, system engineers, product-marketing staff, quality managers, test engineers.

Background

Initial understanding of development and engineering processes.

Training method

Lectures, practical exercises and guided discussions. Comprehensive interactive workshop.

Course leader

Mithun Training & Consulting.

Duration

3 days.

Schedule

Il n'y a pas de sessions publiques a ce moment. Nous organisons volontièrement un cours en entreprise ou une session publique supplémentaire (en cas d'un nombre suffisant de participants). Intéressé ? Veuillez contacter ABIS.

Score global

   
3.9/5 (basé sur 75 évaluations)

Reviews

     
Excellent, a lot of exercices, reflexions, nice group (, )
     
Excellent course (, )
     
Added value of the foundation course is the proportion of the excercises. Useful for new colleagues. (, )
     
Not enough interaction particular the first day and morning after. Second part of the course was more dynamic & interesting. Exercises & review last day vere usefull. (, )
     
The teacher was nice and answered all the questions. May have been a bit more concrete. (, )
     
the instructor has great business experience, and it shows in the practical aspects. I have met someone to look up to as a req.expert. However as a teacher (making people enthousiastic about something) his skills are not on the same (superior) level. (, )
     
Good I would recommend the course to others. I really appriceated all the exercises (, )
     
It is good. I think there was a good balance between theory an practise (, )
     
Good course with many practical exercises (, )
     
That was good but for someone who has already studied on requirements 2 days should be suficient. (, )

Rafraîchissez cette page pour voir d'autres commentaires.