Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Overview of the Software Development Process and Modelling
- Methodologies and their influence on a Business Analyst's work
- Waterfall model phases: Analysis, Design, Implementation, Testing, and Maintenance
- Agile methodologies for business analysis
- Understanding who Business Analysts are
- Perspective on the BA Role
- The Dynamic (Behavioral) Model
- The Static (Structural) Model
- Structured Analysis techniques
The BA’s Perspective on Object Orientation
- Object-Oriented Programming and its effect on modelling
- The UML Standard
- Cognitive Psychology and Object-Oriented design
- Objects
- Attributes and Operations
- Operations and Methods
- Encapsulation
- Classes
- Relationships
- Generalization
- Association
- Aggregation
- Composition
- Polymorphism
- Use Cases and Scenarios
- Business and System Use Cases
Overview of Business Object-Oriented Modeling (B.O.O.M.)
- B.O.O.M. in relation to SDLCs
- The B.O.O.M. steps
- Sequencing the steps
- Determining whether to define Attributes or Operations first
Analyzing End-to-End Business Processes
- Conducting interviews during Initiation, Analysis, and Testing phases
- Step 1: Initiation
- Business Requirements Document Template
- Step 1a: Modeling Business Use Cases
- Step 1a i: Identifying Business Use Cases (Business Use-Case Diagram)
- Applying theory in practice
- Guidance for Rational Rose users
- Case Study D1: Business Use-Case Diagrams
- Step 1a ii: Scoping Business Use Cases (Activity Diagram)
- Case Study D2: Business Use-Case Activity Diagram with Partitions
Scoping the IT Project via System Use Cases
- Step 1b: Modeling System Use Cases
- Case Study E1: Role Map
- Step 1b ii: Identifying System Use-Case Packages (System Use-Case Diagram)
- Case Study E2: System Use-Case Packages
- Step 1b iii: Identifying System Use Cases (System Use-Case Diagram)
- Case Study E3: System Use-Case Diagrams
- Step 1c: Starting the Static Model (Class Diagrams for Key Business Classes)
- Step 1d: Establishing the Analysis Baseline (BRD/Initiation)
Storyboarding the User Experience
- Step 2: Analysis
- The Use-Case Description Template
- Documenting the Basic Flow
- Guidelines for writing use cases
- Example of Basic Flow: CPP System Review Case Report
- Documenting Alternate Flows
- Documenting Exception Flows
- Guidelines for conducting System Use-Case interviews
- Activity Diagrams for System Use Cases
- Related Artifacts
- Decision Tables
- Case Study F1: Decision Table
- Decision Trees
- Case Study F2: Decision Tree
- Condition/Response Table
- Business Rules
- Advanced Use-Case Features
- Case Study F3: Advanced Use-Case Features
Life Cycle Requirements for Key Business Objects
- Understanding State Machine Diagrams
- Step 2a ii: 1. Identifying States of Critical Objects
- Case Study G1: States
- Step 2a ii: 2. Identifying State Transitions
- Case Study G2: Transitions
- Step 2a ii: 3. Identifying State Activities
- Case Study G3: State Activities
- Step 2a ii: 4. Identifying Composite States
- Case Study G4: Composite States
- Step 2a ii: 5. Identifying Concurrent States
Gathering Comprehensive Rules with Class Diagrams
- Step 2b: Static Analysis
- Step 2b i: Identifying Entity Classes
- Case Study H1: Entity Classes
- Step 2b ii: Modeling Generalizations
- Case Study H2: Generalizations
- Step 2b iii: Modeling Transient Roles
- Case Study H3: Transient Roles
- Step 2b iv: Modeling Whole/Part Relationships
- The Composite Structure Diagram
- Case Study H4: Whole/Part Relationships
- Step 2b v: Analyzing Associations
- Case Study H5: Associations
- Step 2b vi: Analyzing Multiplicity
- Case Study H6: Multiplicity
Optimizing Consistency and Reuse in Requirements Documentation
- Step 2b vii: Linking System Use Cases to the Static Model
- Case Study I1: Linking System Use Cases to the Static Model
- Case Study I1: Results
- Step 2b viii: Adding Attributes
- Meta-Attributes
- Case Study I2: Adding Attributes
- Step 2b ix: Adding Look-Up Tables
- Case Study I5: Analyzing Look-Up Tables
- Step 2b x: Adding Operations
- Case Study I7: Distributing Operations
- Step 2b xi: Revising Class Structure
- Case Study I8: Revising Structure
Designing Test Cases and Finalizing the Project
- Step 2c: Specifying Testing
- Structured Walkthroughs
- Decision Tables for Testing
- Case Study J1: Deriving Test Cases from Decision Tables
- Boundary Value Analysis
- Case Study J2: Selecting Test Data Using Boundary Value Analysis
- System Tests
- Activities Beyond System Tests
- Step 2d: Specifying the Implementation Plan
- Step 2e: Setting the Development Baseline
How Developers Utilize Your Requirements
- Object-Oriented Design Patterns
- Visibility
- Control Classes
- Boundary Classes
- Sequence Diagrams
- Communication Diagrams
- Other Diagram Types
- Layered Architecture
- Interfaces
- Mix-Ins
- Implementing OO Using an OO Language
- Implementing OOA Using Procedural Languages
- Implementing a Database from OOA Using a RDBMS
21 Hours
Testimonials (1)
The direct correlation with our work subject in the examples
