BA Information
Broad and diverse set of information at any level of detail which are analyzed, transformed and reported by BAs. Ex) elicitation results, requirements, solution options, traceability matrix, etc
Business requirements
Goals, objectives and outcomes which indicate the reason for initiating change (project)
Stakeholder Requirements
Stakeholder needs which must be met to achieve business requirements; user stories
Solution Requirements
Capabilities and qualities of a solution that meets stakeholder requirements. Broadly classified into: function requirements and non functional requirements (quality of service requirements)
Sponsor
Authorizes work to be done and controls the budget and scope of the initiative
Project Manager
Ensures project objectives are met considering several project factors; manages all work required to deliver a project
Stakeholders
Individuals or groups with which BAs interact with directly or indirectly; Major source of requirements assumptions or constraints
End user
Those who directly use the product or solution
Domain Subject Matter Expert
People with in depth knowledge of a topic relevant to business need or solution scope
Implementation SME
Has specialized knowledge pertaining to implementation of solution components
Operational Support
Responsible for managing and maintaining the system or product on daily basis
Regulator
- responsible for defining and enforcing standards
- Satutory (by parliament/assembly, taxes) or regulatory (typically industry specific)
Supplier
provides products or services to the organization and may have contractual obligations; they are outside the boundary of the organization; supplier provides cots products
tester
carries out verification process and determines whether the solution meets requirements and quality standards
Risk
Effect of uncertainty on the value of a change, solution or enterprise is
Solution Requirements
Capabilities and qualities of a solution that meets stakeholders needs
Domain SME
Domain SMEs are usually folks with good business knowledge. They have deep knowledge of business processes.
Atomic requirements
Requirements at lowest levels
Implicit Requirements
Requirements which are not expressed by stakeholders but are needed are known as
5 perspectives of a BA
Agile, Business Intelligence, Information Technology, Business Architecture, Business Process Management
Example of functional requirement
New data that supports changes to any business process will be included in the new system; data belongs to functional requirements
non functional requirements
does not directly relate to the functionality of the solution
regulatory bodies
taxes are typically the jurisdiction of regulatory bodies
Non functional requirements or quality of service requirements
Do not relate directly to the behaviour of functionality of the solution but rather describe conditions under which a solution must remain effective or qualities that a solution must have
