GooBiz

Goal-Driven System Analysis and Design for Technical Analysts and Designers (2 days)
Objective : Helping Technical Analysts and Designers to understand how to go through software implementation on the basis of requirements using UML and keeping traceability with them.
This 2 days training/mentoring program aims at assisting technical analysts and designers respectively in the analysis and design of the needs described by business experts. After transformation in their component based object representations, the resulting system components trace detailed requirements captured by business analysts toward MDA's PIM level component structures. For instance, services of an SOA based system are built at this stage with their interfaces and internal descriptions.
Finally, these technical specifications are implemented in software code and tested on component basis. The resulting software components allow good level of reactivity to changes as they permit to trace separately toward the implementation level goal-driven business rules (services) and usage rules (use cases) on the basis of a one- to-one traceability relationship with requirements.

Detailed Description :
Introduction
 What is the System Analysis and Design Process ?
 Place of the Analysis and Design in the Unified Process (RUP)
 A panorama of UML diagrams used in the system analysis and design
 Frameworks for tracing requirements toward software implementation and tests

How to transform requirements into component based analysis specifications ?
 Traceability between requirements and system analysis
 Basic notions for representing static business rules
 Basic notions for representing dynamic business rules
 How to refine static rules ?
 How to refine dynamic rules ?
 Toward the system design
 Case Study : Enriching the architectural backbone of the system using your UML tool

How to transform analysis specifications into design level ones ?
 Architectural Design
 Traceability between system analysis and design
 Design level class diagrams
 Design level interactions
 Updating class diagram with design level choices

Implementing technical specifications and testing on component basis
 Generating design level specifications in an object oriented programming language
 Component and Deployment Diagrams
 Tests based on models

Conclusion
 Steps of the system analysis and design processes
 Patterns for ensuring traceability between requirements and the software code
 Testing requirements on the system architecture

Notice : The above training-mentoring programs are conducted using RE (Requirement Engineering) / UML / MDA case tools in order to support good level of traceability between requirements and underlying solutions. Concepts are explained first using basic examples and are then followed by solution drafts to your own problems. In order to enable us to better help you in your case, you may provide us with a set of requirements for your project before the training-mentoring session. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.

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

The RUP is a trademark of the IBM / Rational.