BRD Contents

 Project Overview (vision, Mission,  Surveys JAD Session

Objectives & Context)  Agenda
 Success Factors Quality User Stories (INVEST)  Meeting Title
 Project Scope  Independent  Meeting time
 Stakeholders Identifications  Negotiable  Location
 Business Requirements  Valuable  Participants
 Scope of Solution  Estimable  Open Questions
 Project Constraints  Sized Appropriation  Goals and Objectives (from BRD)
 QC Measures  Testable
MOST Non-Functional Requirements
FRD Contents  Mission  UI Requirements
 System Impacted  Objective  Performance Requirements
 Assumptions  Strategy  Scalability Requirements
 As -is Business  Tactics  Security Requirements
 To-be business SMART
 Business Rules  Measurable Documents
 Functional Requirements  Achievable  Project vision Document
 UI requirements
 Realistic  Business Analysis Plan
 Issues/ Open Questions
 Timely  Business Requirements Document
 Functional requirement specification (FRS)/
Project Charter
Functional Specification Document (FSD)
 Project Description
1. BRD  System requirement specification (SRS)/
 Business Need
2. PM Creates Project Charter (time and$$) System Requirement Document (SRD)
 Goal Setting
3. Project Kickoff meeting initiates (SDCL  Requirement traceability matrix (RTM)
 Risk & Issues
Starts)  Use Case Diagrams
 Work Plan 4. Requirements Gathering  Wireframes, Mockups
 Team Structure a. Understand As is business  Change Request Document
b. Read Existing Business Documents
Elicitation Methods c. Understand the current system in a
 Brainstorming legacy environment
 Doc Analysis 5. Conduct JAD Session and Identify
 Interface Analysis a. Business Rule
 Focus Groups b. Functional Requirements
 Prototyping c. UI Requirements
 Workshops
 Interviews
 Observations
Business process modelling people or departments that the
subprocess impacts on
notation (BPMN)  
 Artifacts. Used if you have
Business process modelling notation additional information that isn’t a
(BPMN) is comprised of symbols that are sequence flow or message flow, but
used as a representation of tasks and
workflows. Any symbols can be used in
your business process, but using
standardised ones allows you to collaborate
with outside analysts more easily, and it that
spares you from having to invent your own will
visual language.
BPMN symbols fall into the following
categories:
 Flow objects. Shows the flow of the
process
o Circles. Events are displayed
inside of circular shapes
o Rectangles. Activities fit into
rectangular boxes
o Diamonds. Control points or
gateways are represented as
diamond shapes
 Connecting objects. Used to show
how tasks are connected, and in further explain the process
what sequence they occur
o Dotted lines. These point to
o Solid lines. Shows task the flow object that the extra
transfers information expands on
o Dashed lines. Shows o Squares outlined with dots
messages and dashes. These group
 Swim lanes. These make provision related elements in the
for subprocesses that share diagram
responsibilities and how they o Square bracket. Text
interact. The swimlanes are the annotations are added here