Section- 1
Introduction
- Duties and roles
- Gathering Requirements with Use Cases
- Gathering Workflow and Complex Requirements
- Documenting Requirements for Legacy Systems using Structured Analysis
- Tools required and Methodologies
Section- 2
- Gathering Business Data Requirements
- Practical Guide to Object-Oriented Analysis for the BA
- The BA Role in Testing
- Project Management for the BA
Section- 3
Business Modeling
- Introduction to Business Modeling
- Setting Activity goals
- Finding business workers and entities
- Detailing business workers and entities
- Defining automation requirements
- Introduction to Use Cases
- The Kick-off Meeting - analyzing stakeholders and interests; identifying high and mid-level objectives
- Analyzing Business Use Cases
- Structuring System Use Cases
Section- 4
- Eliciting and Documenting System Use Cases/ Context and Basic Flow
- Eliciting and Documenting Alternate and Exception Flows
- Documenting Inclusion, Extension and Generalized Use Cases
- Linking Use Cases to Other Project Artifacts (Documentation and Models)
Section- 5
- Introduction to IT Project Management
- Process Model
- Project Lifecycle
- Waterfall Model
- Iterative phases
- Spiral Model
- MSF
- RUP
- Agile
- BA Role in Iterative Development
- Initiation Phase - Initial Activities
- PM role
- BA role
- Solution Architect role
- Defining stakeholder interests
- Deciding upon the iteration strategy
- Wide and shallow
- Narrow and deep
- Initiation Phase - Analysis
- Business use-case analysis
- Role Map
- Setting up a process for requirements management
- Characteristic of well-managed and well-documented requirements
- Traceability matrix
- Defining requirements attributes
- The Requirements Management Plan
- CMM (Capability Maturity Model)
- Planning for future releases
- Overview of Software Development
Lifecycle Methodologies
- PMBoK (Project Management Book of Knowledge)
- Knowledge Areas
- Process Groups
- Lifecycle
- Process Improvement
- CMM (Capability Maturity Model)
- ISO 9000
- Agile
Section- 6
- Initiation Phase – Risk Management
- Planning a Risk-Management strategy
- Risk assessment and analysis
- Prioritizing and mitigating risks
- Use Cases and Risk
- Factoring Risk into the determination of iteration length
- Establishing project scope
The Analysis Phases
- Non-functional requirements
- Enterprise and Solution Architecture
- Dynamic analysis activities
- Static analysis activities
- Implementing traceability
- Testing activities
- Risk Analysis
- Reviewing the results of an iteration
- Planning for the next iteration
- Execution, Test and Close-out Phases
- Change management
- Use case driven testing
- Deployment
- Final Documentation
|
Section- 7
- Static Analysis and the BA
- What is static analysis?
- How does it relate to dynamic analysis?
- Analyzing Business Classes
- UML
- Identifying entity classes
- Classes and objects
- Defining Packages
- Interview tips for discovering entity classes
- Questions for the stakeholders
- Challenge questions
- Follow-up questions
- Analyzing Sub-types (Generalizations and transient roles)
- Full-time sub-types
- Generalization in the class diagram
- Generalization: what to ask stakeholders
- Part-time sub-types/ transient roles
- Transient roles: what to ask stakeholders
- Analyzing Aggregations, Associations and Multiplicities
- Whole-part relationships
- Aggregation in the class diagram
- Composite structure diagram
- Aggregation: what to ask stakeholders
- Association in the class diagram
- Associations: What to ask stakeholders
- Mulitiplicities
Section- 8
- Discovering attributes and operations
- What to ask stakeholders
- Documenting attributes in class diagrams and in text
- Analyzing Look-up tables
- Operations:
- What to ask stakeholders
- Documenting operations in the UML
- Documenting operations in the text:
- Revising the static model
Static Modeling during Initiation
- BA static modeling activities performed during the Initiation phase of a project
- Keeping the static and dynamic models in synch with each other.
- Identifying static modeling elements from a use case diagram
Static Modeling during Analysis
- Deriving static modeling elements from use case flows
- Identifying and resolving discrepancies between use cases and the static model
- Documenting the link from a use case to the static model
- Static object diagrams
Data Modeling
- What is data modeling?
- Relational approach to data modeling
Converting a class diagram to an Entity relationship Diagram (ERD)
Section- 9
- Features of workflow modeling
- Rules of precedence
- Basic workflow structures: sequential sequencing, repetition, selection, parallel activities
- UML standards for workflow: activity, state and sequence diagrams
- IDEF standards for workflow
- Creating activity diagrams
- Activities
- Transitions
- Guards
- Split and merge
- Fork and Join
- Hybrid diagrams: Adding object flows to the activity diagram
- Partitions/ Swimlanes
- Creating UML state transition diagrams
- States
- State transitions
- Transition guards, events and send events
- State activities
- Orthogonal (concurrent) states
- Superstates
- State History
- Participating objects
- Depicting the sequencing of object operations
|