REQUIREMENTS

MODELLING ‘-

1
System Analysis Phase Overview
 The overall objective of the systems analysis phase
is to understand the proposed project, ensure that
it will support business requirements,
‘-
and build a
solid foundation for system development. In this
phase, the analyst uses models and other
documentation tools to visualize and describe the
proposed system.
2
System Analysis Activities
 The systems analysis phase includes the four main
activities shown in Figure 1, requirements
modeling, data and process‘- modeling, object
modeling, and consideration of development
strategies

3
System Analysis Activities
Figure 1: The systems analysis phase
consists of requirements modeling, data
and process modeling, object modeling,
and consideration of development
‘-
strategies. Notice that the systems analysis
tasks are interactive, even though the
waterfall model generally depicts sequential
development.

4
Requirements Modelling
 Involves fact-finding to describe the current
system and identification of the requirements for
the new system, such as‘- outputs, inputs,
processes, performance, and security.

5
Requirements Modelling
 Input refers to necessary data that enters the
system, either manually or in an automated
manner. ‘-
 Process refers to the logical rules that are applied
to transform the data into meaningful information.
 Output refers to electronic or printed information
produced by the system
6
Requirements Modelling
 Performance refers to system characteristics, such
as speed, volume, capacity, availability, and
reliability. ‘-
 Security/Control refers to hardware, software,
and procedural controls that safeguard and
protect the system and its data from internal or
external threats.
7
Data and Process Modeling
 Shows how to represent graphically system data
and processes using traditional structured analysis
techniques. As described ‘-structured analysis
identifies the data flowing into a process, the
business rules that transform the data, and the
resulting output data flow.

8
Object Modeling
 Object modeling, which is another popular modeling
technique. While structured analysis treats processes
and data as separate components, object-oriented (OO)
analysis combines data and the ‘-processes that act on
the data into things called objects. These objects
represent actual people, things, transactions, and events
that affect the system. During the system development
process, analysts often use both modeling methods to
gain as much information as possible. 9
Development Strategies
 The deliverable, or end product, of the systems
analysis phase is a system requirements
document, which is an overall‘- design for the new
system. In addition, each activity within the
systems analysis phase has an end product and
one or more milestones. As described, project
managers use various tools and techniques to
coordinate people, tasks, timetables, and budgets.
10
System Analysis Skills
 A systems analyst needs strong analytical and
interpersonal skills to build an accurate model of
the new system. Analytical skills
‘-
enable the analyst
to identify a problem, evaluate the key elements,
and develop a useful solution. Interpersonal skills
are especially valuable to a systems analyst who
must work with people at all organizational levels,
balance conflicting needs of users, and 11
System Analysis Skills
 communicate effectively. Because information
systems affect people throughout the company,
team-oriented strategies should‘-
be considered at
the start of the systems analysis phase.

12
Team-Based Techniques: JAD, RAD, and Agile Method
Joint Application Development (JAD)
 Joint application development (JAD) is a popular
fact-finding technique that brings
‘- users into the
development process as active participants.

13
Team-Based Techniques: JAD, RAD, and Agile Method
JAD Participants and Roles

‘-

Figure 2: Typical JAD Participants and Roles 14

Team-Based Techniques: JAD, RAD, and Agile Method
Rapid Application Development (RAD)
 Rapid Application Development (RAD) is a
software development methodology
‘- that
prioritizes quick development and iteration of
prototypes over rigorous planning and testing.
RAD is designed to accelerate the development
process and deliver functional software to users
as rapidly as possible. 15
Team-Based Techniques: JAD, RAD, and Agile Method
Rapid Application
Development (RAD)
Figure 3: The four phases
of the RAD model are
‘-
requirements planning,
user design, construction,
and cutover. Notice the
continuous interaction
between the user design
and construction phases.
16
Team-Based Techniques: JAD, RAD, and Agile Method
Agile Method
 Agile methodology is an iterative and incremental
approach to software ‘-development that
emphasizes flexibility, collaboration, and customer
satisfaction. It breaks down the development
process into small, manageable increments,
allowing for continuous feedback and adaptation
to changing requirements. 17
Team-Based Techniques: JAD, RAD, and Agile Method
Agile Method
 Agile methodologies prioritize individuals and
interactions, working software,
‘- customer
collaboration, and responding to change over
rigid processes and tools.

18
MODELING TOOLS AND TECHNIQUES
Models help users, managers, and IT professionals
understand the design of a system. Modeling
involves graphical methods ‘- and nontechnical
language that represent the system at various stages
of development. During requirements modeling, the
analyst can use various tools to describe business
processes, requirements, and user interaction with
the system. 19
MODELING TOOLS AND TECHNIQUES
1. Functional Decomposition Diagram (FDD) is a
top-down, hierarchical representation of a system,
breaking it down into smaller, more manageable
components. ‘-

 Drawn like an organization chart.

 Business functions or processes are broken down to
lower level processes or functions
 During application development, these
processes/functions become program modules. 20
 Steps to Create a Functional Decomposition
Diagram
1. Identify the System - Determine the overall
system or process that needs‘- to be decomposed
into its functional elements.
2. Break Down Functions - Identify the major
functions within the system and begin breaking
them down into smaller sub-functions.
21
 Steps to Create a Functional Decomposition
Diagram
3. Assign Hierarchy- Organize the functions in a
hierarchical manner, with the‘-main function at the
top and sub-functions below.

22
Example of a Functional Decomposition Diagram

‘-

Figure 4: Example of a Functional Decomposition Diagram

23
Example of a Functional Decomposition Diagram

‘-

Figure 5: Actual Example of a Functional

Decomposition Diagram 24