After completing this course, you will be able to
- describe how business analysis fits within the development lifecycle.
- explain the benefits of a methodical approach to clear and unambiguous requirements.
- use a project charter or statement of work as a starting point for business analysis.
- describe requirements in terms of their purpose and characteristics.
- ensure requirements have a positive impact on design and testing activities.
- create a Business Requirements Document to present your analysis of the requirements.
- map the relationships between business requirements and models.
- do essential analysis modeling of processes and data.
- rigorously test the requirements.
Who should attend?
Business Analysts and anyone responsible for understanding and communicating business requirements.
You should already have a general understanding of computer systems and the systems development process.
- Eliciting requirements
- Documenting what you discover
- Business Analysis Process
- Process Modeling
- Use Cases
- Data Analysis
- Functional Requirements
- Non-Functional Requirements
- Business Rules
- Current Systems Analysis
- Gap Analysis
- Business Requirements document (BRD)
- System Requirement Specification (SRS)
- Requirements vs. Solutions
- Who needs requirements
- Requirements for Design
- Requirements for Testing
- Requirements Forever