Chapter 2

Requirements Modeling part 2

 Systems Analysis Skills
◦ Strong analytical skills
◦ Interpersonal skills
 Team-Based Techniques: JAD, RAD, and
Agile Methods
◦ Object is to deliver the best possible system at the
lowest possible cost in the shortest possible time
◦ Joint application development brings users into the
design process
◦ Rapid application development uses a condensed
version of the system development life cycle
◦ Agile methods stress intense interaction between
developers and users

2
 Brings users into the development process as
active participants
 User Involvement (formally or informally) created a
successful system
 JAD Participants and Roles
◦ Project leader and one or more members
◦ Participants insulated from distractions of day-to-day
operations

3
4
FIGURE 4-3 Typical JAD participants and roles

5
FIGURE 4-4 Typical agenda for a JAD session 6
JAD Disadvantages
 JAD is more expensive than traditional
methods
 Can be cumbersome if group is too large

JAD Advantages
 JAD allows key users to participate effectively
 Users more likely to feel a sense of ownership
 Produces a more accurate statement of
system requirements

7
 Uses a group approach like JAD
 JAD produces a requirements model, RAD produces
a new system
 Complete methodology
◦ Four-phase life cycle that parallels the traditional SDLC
◦ Reduces cost and development time
◦ Increases the probability of success
◦ Relies on prototyping and user involvement
◦ Prototypes modified based on user input

8
RAD
Phases
and
Activities

FIGURE 4-5 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

9
 Requirements Planning
◦ Team agrees on business needs, project scope,
constraints, and system requirements
◦ Management authorization to continue is obtained
 User Design
◦ Users interact with analysts to develop models and
prototypes
◦ A combination of JAD and CASE tools are used
◦ Users understand, modify, and approve a working
model

10
 Construction
◦ Program and application development
◦ Users can suggest changes as screens or reports are
developed
 Cutover
◦ Includes data conversion, testing, changeover to the
new system, and user training

11
 RAD Objectives
◦ Cut development time and expenses by involving users
in every phase of systems development
◦ Allow the development team to make necessary
modifications quickly, as the design evolves
 RAD Advantages
◦ Systems developed more quickly with significant cost
savings
 RAD Disadvantages
◦ Does not emphasize strategic business needs (system
might work well in short term but miss long-term
objectives)
◦ Less time to develop quality, consistency, and design
standards

12
 Agile methods attempt to develop a system
incrementally, by building a series of prototypes
and constantly adjusting them to user
requirements
 Developers revise, extend, and merge earlier
versions into the final product
 Emphasizes continuous feedback, and each
incremental step is affected by what was learned in
the prior steps

13
FIGURE 4-6 Agilian supports various modeling tools, such as
the Unified Modeling Language, use cases, and business
process modeling, among others 14
 Scrum
◦ A rugby term
◦ Pigs include the
product owner,
the facilitator, and
the development
team
◦ Chickens include
users, other FIGURE 4-7 In a rugby scrum, team members prepare to
stakeholders, and lunge at each other to achieve their objectives
managers
◦ Scrum sessions have specific guidelines that
emphasize time blocks, interaction, and team-
based activities that result in deliverable software

15
16
 Agile Method Advantages and
Disadvantages
◦ Very flexible and efficient in dealing with change
◦ Frequent deliverables constantly validate the project
and reduce risk
◦ Team members need a high level of technical and
interpersonal skills
◦ May be subject to significant change in scope

17
 Involves graphical methods and nontechnical
language that represent the system at various
stages of development
 Can use various tools
 Functional Decomposition Diagrams
◦ Functional decomposition diagram (FDD)
◦ Model business functions and show how they are
organized into lower-level processes

18
 Functional Decomposition
Diagrams
◦ Top-down
representation
of a function
or process
◦ Similar to an
organization
chart
FIGURE 4-8 This Visible Analyst FDD shows a library system
with five top-level functions. The Library Operations
function includes two additional levels of processes and sub
processes

19
 Business Process
Modeling
◦ Business process
model (BPM)
◦ Business process
modeling notation
(BPMN)
◦ Pool FIGURE 4-9 Using the Visible Analyst CASE tool, an
◦ Swim lanes analyst can create a business process diagram. The
overall diagram is called a pool, and the two separate
customer areas are called swim lanes

20
Business Process Modeling

Bắt đầu

Kết Thúc

Tiến Trình xử lý

Nút quyết định

Biểu đồ quy trình nghiệp vụ (BPD)
Biểu đồ quy trình nghiệp vụ (BPD)
 Business Process Modeling (BPM)
◦ Represent the people, events, and interaction
in a system
◦ Outside rectangle is called a pool, and
designated swim lanes show specific actions
and events
◦ Swim lanes can interact when certain events
occur

24
  Data Flow
Diagrams
◦ Data flow diagram
(DFD)
◦ show how the system
stores, processes,
and transforms data
◦ Additional levels of
information and
detail are depicted in
other, related DFDs

FIGURE 4-10 This Visible Analyst DFD shows how books

are added and removed in a library system
25
 Use Case
Diagrams
◦ Interaction between
users and the
system

FIGURE 4-12 This table documents the credit card

validation use case shown in Figure 4-11

FIGURE 4-11 This Visible Analyst use case diagram

shows a sales system, where the actor is a customer
and the use case is a credit card validation
26
 Sequence
Diagrams
◦ Shows the timing
of interactions
between objects
as they occur

FIGURE 4-14 This Visible Analyst sequence diagram

shows a credit card validation process

27
 At the conclusion of requirements modeling,
systems developers should have a clear
understanding of business processes and
system requirements
 The next step is to construct a logical model
of the system
 IT professionals have differing views about
systems development methodologies, and
no universally accepted approach exists

28
 The systems analysis phase includes three
activities: requirements modeling, data and
process modeling, and consideration of
development strategies
 The main objective is to understand the
proposed project, ensure that it will support
business requirements, and build a solid
foundation for the systems design phase
 Popular team-based approaches include JAD,
RAD, and agile methods

29
• The fact-finding process includes
interviewing, document review, observation,
questionnaires, sampling, and research
• Systems analysts should carefully record and
document factual information as it is
collected, and various software tools can help
an analyst visualize and describe an
information system

30