Requirement Engineering – An Introduction
- Framework of Requirements Engineering
- Rationale and the problems of Requirements Engineering
- Requirements and its Features
- Problems of Requirements
- Requirements Engineering – The Framework and its achievements
- Requirements Planning and Estimating – It’s Importance
- An Overview of Business Analysis and Input
- Define Business Process Analysis Model and Inputs into ‘The Define Requirements’ Stage
- Describe Business Case in Project Life-Cycle
- What are Terms of Reference?
- What is Project Start-up Document?
- Define Project Charter–business objectives and project objectives
- Define Project scope and constraints (budget, timescale, standards)
- Define sponsor, resources and assumptions
Define requirements hierarchy
- Creation of hierarchy through requirements breakdown
- Describe requirements types (Hierarchy based)
- Define General business requirements (business and legal policy)
- What are technical policy requirements?
- Discuss Functional and Non-functional requirements
Role of Stakeholders in the requirements process
- Define stakeholder
- Role and Influence of Project Stakeholders to the requirements engineering process
- What is the role and contribution of Business Stakeholders to the requirements Engineering Process?
- Define Project Sponsor
- Describe Subject matter expert
- Define End users and managers
Understanding Requirements Stimulation
- What are Knowledge types?
- Types of Knowledge Types
- Simulation techniques
- Activity sampling
- Workshops
- Interviews
- Observation
- Formal/informal
- Focus groups
- Questionnaires
- Prototyping
- Shadowing
- Special purpose records
- Scenarios
- Document Analysis
- Understanding how to apply procedures
Requirements Engineering - Using Models
- Modelling requirements – Their purpose
- Generating queries
- Rechecking for stability and fullness
- Describing business guidelines
- Create a Model, using Context Diagram, for the system by recognizing the requirements and yields
- Generate a system processing model.
- Use case diagrams for demonstrations
- Learn how to use a data model which is based upon requirements from the system data
- Requirements Documentation
- Different Styles of Documenting and their levels
- User Stories
- Use Cases
- Requirements List
- Requirements Catalogue
- Requirements Catalogue
- Identifier
- Name
- Description
- Acceptance criteria
- Source
- Owner
- Rationale/Benefits
- Related non-functional requirements
- Priority
- Type (functional, non-functional, general, technical)
- Related requirements/documents
- Author
- Version control/status
- Change history
- Resolution
- Resolution
Requirements Document
- Introducing Requirements Documents
- Business Process Models
- Function models of defined requirements
- Data model of defined requirements
- Requirements catalogue
- Glossary
Requirements Analysis
- Prioritising and packaging requirements for delivery
- Organising requirements
- Requirements filters
- Characteristics of a good requirement
- Removing duplicated requirements
- Reconciling overlapping requirements
- Identifying and negotiating conflicts between requirements
- Removing ambiguity
- Ensuring feasibility(technical, business and financial)
- Ensuring testability
- Providing traceability
- Prototyping requirements
- Verifying requirements
Requirements Validation
- Agreeing on the requirements document
- Types of reviews
- Informal reviews
- Structured walkthroughs (author-led review)
- Technical reviews
- Inspections
- Stakeholders and their areas of concern
Requirements Management
- Dealing with changing requirements
- The sources of change
- Change Management
- Configuration management
- The importance of traceability
- Vertical traceability (to business objectives)
- Horizontal traceability (from origin to deliver)
- Traceability and ownership
- Requirements Engineering support tools
- CARE Tools (Computer Aided Requirements Engineering)
- CASE Tools (Computer Aided Software Engineering)
Enquire Now 