Course Duration: 2 Days

Course Category: Business Analysis & Requirements Engineering


14 Contact Hours

Requirements Analysis (for Business and Systems Analysts)

Course Objectives

This two-day course describes an approach to requirements analysis that can be applied by analysts with different levels of experience.  Underpinning the approach is the concept of Use Cases.  These describe requirements from the perspective of the users of a software application.

The course first shows participants how to create a conceptual model. The conceptual models provides a context for identifying requirements and the development of use case models.  Finally packaging of a requirements specification and various project issues are discussed.

The course is based on UML (unified modeling techniques) and includes a number of generic and project specific workflows, which show how to apply the techniques to a variety of different projects.




Course Features


Describes the need for software application requirements
Introduces and/or reviews as required by the participants, the techniques of Activity Analysis; Needs Analysis; Conceptual  Modelling, Business Rule Modelling and Use Case Modelling.
Presents a generic set of workflows that can easily be tailored to meet the needs of specific projects.




Participant Benefits


Clear understanding of the role of requirements in a software development or acquisition project.
Ability to effectively apply the techniques discussed during the course to a variety of projects.
Practical experience of applying the techniques and workflows to a case study.




Who Should Attend


Business and Systems Analysts
Developers who need to do specify requirements
Team Leaders
Project Managers
Software Engineers &
Software Managers






Business Modelling
Conceptual Modelling

Classification, Abstraction and Reification
UML Class Diagrams
Identifying Object Types
Subject Areas

Requirements Definitions

Business Rules




Software Requirements


Interface Requirements
Functional Requirements
Non-Functional Requirements


Quality Attributes
Environmental Constraints
Life-Cycle Constraints
Design Constraints


Storage Requirements
Identifying Software Requirements

Use Case Concepts

System Boundaries and Visibility
Use Cases as Tool Requirements
Anatomy of a Use Case
A Use Case Framework

Describing Use Cases

Use Case Template
Use Case Scenarios
Extending and Including Use Cases
Specialising Use Cases
Levels of Use Case Detail
Use Case Diagrams

Use Case Modelling

Identifying Actors and Use Cases
Incorporating Information requirements
Incorporating Business Rules
Incorporating Software Requirements

 Requirements Validation

Packaging the Requirements  Specification



Leave a Reply

Your email address will not be published. Required fields are marked *

PMI, PMP, PMBOK, CAPM, PMI-ACP and the Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
CMMI®, Capability Maturity Model®, Capability Maturity Modeling®, CMM®, PCMM® and Carnegie Mellon® are registered in the US Patent and Trademark Office by Carnegie Mellon University.
ISTQB® is a Registered Trade Mark of the International Software Testing Qualifications Board.
IIBA®, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
The APMG-International Agile Project Management, AgilePM and Swirl Device logos are trademarks of The APM Group Limited.
PRINCE2®, ITIL®, IT Infrastructure Library®, and MSP® are registered trademarks of AXELOS Limited. The Swirl logo™ is a trade mark of AXELOS Limited.
The ITIL Licensed Affiliate logo is a trademark of AXELOS Limited.
SCRUM Alliance REP SM is a service mark of Scrum Alliance, Inc.