LAB SESSION

Requirements Gathering
 Identify the Requirements
◦ System Requirements

◦ Functional Requirements

◦ Non-Functional Requirements
It is a statement describing either

 an aspect of what the proposed system must do

 In either case it must contribute in some way towards adequately

solving the customer’s problem;

 A collection of requirements is a requirements document.

 Requirements are defined during the early stages of a system
development as a specification of what should be implemented or as
a constraint of some kind on the system.
 They may be:

◦ a user-level facility description,

◦ a detailed specification of expected system behaviour,

◦ a general system property,

◦ a specific constraint on the system,

◦ information on how to carry out some computation.

User requirements
 Statements in natural language plus diagrams of the services the system provides
and its operational constraints. Written for customers.

System requirements
 A structured document setting out detailed descriptions of the system’s functions,
services and operational constraints.

 Defines what should be implemented so may be part of a contract between client

and contractor.
 Functional requirements:
◦ Services the system should provide
◦ What the system should do or not in reaction to particular situations
◦ Example: “If a patient is known to be allergic to a particular medication, then prescription of
that medication shall result in a warning message being issued to the prescriber”
 Non-functional requirements:
◦ Constraints on the services or functions offered by the system
◦ Example: “The system shall be available to all clinics during normal working hours (Mon-Fri,
0830-1730). Downtime during normal working hours shall not exceed 5 seconds in any one
day”
 Domain requirements:
◦ From the application domain of the system
◦ Example: “The system shall implement patient privacy provisions as set out in the 1998 Data
Protection Act”
Project Plan
 Prepare Project Plan Based on Scope
 Identify Job Roles and Responsibilities
 Calculate Project Effort Based on Resources
 10 Steps To Creating A Project Plan

1. Explain the project plan to key stakeholders and discuss its key
components
2. Define roles and responsibilities.
3. Hold a kickoff meeting
4. Develop a Scope Statement
5. Develop scope baseline
6. Develop the schedule and cost baselines
7. Create baseline management plans
8. Develop the staffing plan
9. Analyze project quality and risks (Lab Session 5)
10. Communicate & Document (Lab Session 5)
 Template included
1 PROJECT SPONSOR

2 SUBJECT MATTER EXPERTS (SME)

3 PRODUCT OWNER
4 PROJECT MANAGER (PM)
5 TECHNICAL LEAD
6 SOFTWARE DEVELOPERS
7 SOFTWARE TESTERS
8 USER ACCEPTANCE TESTERS
Here we have the following scenarios:

1. Much relevant project data are available for the current project but
not much information about previous projects.

2. Previous project data are available for the project but not much
information about the current project.

3. Project data are available for the current project as well as that of
previous projects.

4. Some project data are available for the current project.

5. No project data are available for both current as well as previous

projects.
WBS, Timeline and Risk Analysis
 Prepare Work Breakdown Structure
 Timelines
 Risk Identification & Plan
 Identify “what” needs to be done
◦ Work Breakdown Structure (WBS)
 Identify “how much” (the size)
◦ Size estimation techniques
 Identify the dependency between tasks
◦ Dependency graph, network diagram
 Estimate total duration of the work to be
done
◦ The actual schedule
 Decompose your project into manageable
chunks
 ALL projects need this step
 Divide & Conquer
 Two main causes of project failure
◦ Forgetting something critical
◦ Ballpark estimates become targets
 How does partitioning help this?
 Hierarchical list of project’s work activities
 Two Formats
 Outline (indented format)
 Graphical Tree (Organizational Chart)
 Uses a decimal numbering system
 Ex: 3.1.5 (0 is typically top level)
 Includes
 Development, Management, and project support tasks
 Shows “is contained in” relationships
 Does not show dependencies or durations
 Up to six levels (3-6 usually) such as

 Upper 3 can be used by customer for

reporting (if part of RFP/RFQ)
 Different level can be applied to different
uses–Ex: Level 1: authorizations; 2: budgets;
3: schedules
 0.0 Retail Web Site
 1.0 Project Management
 2.0 Requirements Gathering
 3.0 Analysis & Design
 4.0 Site Software Development
◦ 4.1 HTML Design and Creation
◦ 4.2 Backend Software
 4.2.1 Database Implementation
 4.2.2 Middleware Development
 4.2.3 Security Subsystems
 4.2.4 Catalog Engine
 4.2.5 Transaction Processing
◦ 4.3 Graphics and Interface
◦ 4.4 Content Creation
 5.0 Testing and Production
 Ask the students to map the WBS to time.
 The Timeline is limited to end of March this
semester
 Ask to map the work with job roles identified
and assign individuals.
 Ask them to use Team Gantt Software
 Include the time and work in the chart
Risk identification should be strengthened by supplementing
Management’s perceptions of risks
 review of external and internal audit reports;

 review of the reports of the Standing Committee on Public

Accounts and the relevant Parliamentary Committee(s)
 financial analyses

 historic data analyses

 actual loss data

 interrogation of trends in key performance indicator;

 benchmarking against peer group or quasi peer group

 market and sector information;

The following are key steps necessary to effectively
identify risks from across the Institution:
 Understand what to consider when identifying
risks
 Gather information from different sources to
identify risks
 Apply risk identification tools and techniques

 Document the risks

 Document the risk identification process

 Assess the effectiveness of the risk identification

process.
Diagrams
 Design System Architecture
 Use Case Diagram
 Entity Relationship Diagram (Database)
 Data Flow Diagram (Process)(Up to Level 1)
 Class Diagram
 Collaboration Diagram
 State Chart Diagram
 Sequence Diagram
 Deployment Diagram
 Sample Frontend Design (UI/UX)
UML Diagrams Examples
https://www.uml-diagrams.org/index-
examples.html

Online Shopping Example

https://www.uml-
diagrams.org/examples/online-shopping-
example.html