GooBiz

Efficient Requirement Analysis For Business Analysts (3 days)

Objective : Helping Business Owners and Analysts to understand how to make an efficient Requirement Analysis on the basis of the BMM's business goals, Scrum's user stories and the RUP's "use case driven development" methodologies using UML analyst profiles.

This 3 days training/mentoring program aims at helping business experts and analysts to describe their business needs then discover appropriate use cases and user stories of the system. Along interactive case studies, business experts learn how to describe in detail such requirements in order to validate correct understanding of their needs and to prepare system acceptance tests. Thus, only using the appropriate UML profile for business analysts, participants learn to structure their requirements in order to communicate efficiently with technical analysts and designers through an iterative requirement gathering process.

Detailed Description :

Introduction
 What is the Requirement Management Process ?
 Place of the Requirement Management in the Unified Process (RUP) and within Agile Methods
 A panorama of UML diagrams for modeling requirements
 Frameworks for tracing requirements toward software implementation and tests
 Case Study : Gathering requirements and managing them using an iterative process

How to describe user needs via use case models and user stories?
 Basics of the use case diagram : system scope (the subject), actors, use cases, user stories
 How to find out use cases on the basis of requirements and user needs ?
 Case Study : Discovering use cases on the basis of usage choices of actors

How to describe business needs via use case and service models ?
 Business and system use cases
 Describing business use cases via process level activity diagrams
 Finding out system use cases on the basis of process activities
 Alternative BMM / SOA : Discovering use cases and services on the basis of business goals
 Case Study : Finding use cases and services on the basis of business requirements

Validating correct understanding of detailed specifications
 Diagrams for describing use cases and services using UML and SoaML
 A plan type for describing user stories, use case scenarios and services
 Basics of the system sequence, activity, state and class diagrams
 How to choose the right diagram ?
 Updating textual description of use cases
 Rules for efficient use case and service writing
 Refining the use case model : Relationships between use cases of the system
 How to test correct understanding of requirements ?
 Using an incremental requirement gathering process
 Case Study : Describing detailed use case and service behaviors using UML diagrams

Conclusion
 Steps of efficient requirement gathering and system analysis processes
 Traceability between requirements and analysis models
 Patterns for gathering and testing requirements

Notice : The above training-mentoring sessions are conducted interactively using Requirement Engineering and Modeling tools in order to ensure good level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.

The logos UML, SysML, BMM, BPMN and MDA referenced on this site are trademarks of the Object Management Group (OMG).

The RUP is a trademark of the IBM / Rational.