Duration
3 days or 4 days
Course Cost: $1,995.00
Prerequisite
No.
Description
O.O.A. is an intensive course aimed at the Business Analyst working on an “Object-Oriented” (“OO”) project. The course covers all aspects of the Business Analyst’s role, including information gathering through 1-on-1 and group interviews, creation of a Business Requirements Document and diagramming, explaining how each is accomplished in an Object-Oriented environment. O.O.A. is extremely “hands-on”: our trainees learn by working through an integrated case study based on a real-life project.
Why:
The growth of e-commerce and client-server applications has led to the rise of “Object-Oriented” (OO) tools and languages (e.g., Java, Visual Basic, C++) on which they are based. To take full advantage of OO technology, all members of a development team must learn to “speak the same language” – the language of OO. While developers have been quick to train or retrain in OO, I/T Business Analysts have only recently begun to do so. O.O.A. training is focused squarely on the Business Analyst working in this new environment. By extending “OO” practices to the Business Analyst, O.O.A. training allows the benefits of “OO” – such as reduced Mean Time To Repair – to be realized at ALL phases of a project life cycle – not merely during the development phase. As well, by training the Business Analyst to write business requirements that conform to “OO” standards, O.O.A. eliminates translation errors introduced when traditional (non-“OO”) requirements are converted to “OO” by the development team.
What makes this course stand out from the competition?
- 1. Focus on the perspective of the Business Analyst: While other object modeling courses are geared towards developers (systems analysts, programmers, etc.), only O.O.A. offers instruction geared specifically to the needs of the I/T Business Analyst. You will learn which UML diagrams are best suited to the needs of the Business Analyst and when to use each diagram. You’ll learn how OO modeling can assist you throughout business analysis – as a way to structure interviews and to ensure the completeness and internal integrity of your requirements documentation.
- 2. Complex, real-life case study: Whereas other courses use simplified case studies, O.O.A. training revolves around a complex case closely based on a real-life international software project. We believe (and our trainees concur) that only a sufficiently complex case study can bring forth the tricky situations that tend to “stump” analysts when they are back at the office.
- 3. Job Aids: Each trainee receives a “Job Aids” booklet with valuable tips, guides and sample documentation for use on the job.
Objective
Upon completion of this course, you will be able to:
Decrease software bugs introduced in the analysis phase of your project, by using OO techniques that reduce internal inconsistencies.
Shorten system development time and MTTR (Meant Time To Repair) through full exploitation of the efficiencies of OO.
Communicate effectively with the OO development team, through an understanding of key OO concepts and terms.
Analyze the “as-is” situation and identify opportunities for re-engineering using activity diagrams.
Analyze workflow for the future system using OO diagramming techniques such as activity diagrams with swim lanes.
Document business requirements that conform to the widely accepted Object-Oriented standard UML (Unified Modeling Language).
Create text-based documentation of use cases using a standard template.
Depict the context and scope of the project with use case diagrams.
Model business objects using class diagrams.
Normalize the business object model to avoid redundancies.
Manage releases with use-case driven iterative development.
Integrate traditional techniques such as Decision Tables into OO documentation.
Describe the behaviour of key business objects using State Diagrams
Gain an introductory knowledge of advanced Object-Oriented topics, including patterns, stereotypes and implementation of OO in a non-OO environment.
Gain practical experience in using Rational ROSE for business analysis. (Non-ROSE instruction also available for those not wishing to use the product.)
Audience
This course is targeted to the following staff working on OO-designated projects:
I/T Business Analysts
Business Users who will be explaining business requirements to software developers
Systems Analysts expanding their roles into the business realm.Class Format
The course content is presented:
Through an integrated workshop based on a real-life case study.
Through lectures.
Through one-on-one assistance during hands-on workshops.
Through the trainees’ development of a business object model using the popular Rational ROSE software.
Content
History of OO and its relation to Structured Analysis and other technologies
The impact of OO technology on the role of the Business Analyst
OO concepts: Objects, encapsulation, attributes, operations, inheritance, aggregation, polymorphism, use cases, UML
Step-by-step process for Object-Oriented Business Analysis
Segmenting requirements into use case packages and use cases
Identifying actors
Using “use case diagrams” to structure and reduce redundancies in the requirements documentation.
Effective use of advanced “use case” features: Includes, extends, and generalizes.
Describing current and future workflow with activity diagrams (with and without swim lanes)
Template for a UML-compliant Object-Oriented BRD (Business Requirements Document)
Use Case Description Template
Writing the Normal Flow and Alternate Flow sections of the use case template
Appending Use Cases with Decision Tables and Decision Trees
Using State Diagrams to describe critical business objects
Interview questions for determining inheritance, “part-time” roles, aggregation, association and multiplicity
Using UML Class Diagrams to centralize requirements in the BRD and ensure consistency with the enterprise model
Assigning attributes and operations to classes
Normalizing the Object Model
Advanced modeling: Mix-ins, Patterns, Control and Boundary Classes
Job Aids.