c
c






c
c 
 
c

In the end of this section, student should be able to:
‡ Differentiate common system development tools:
(a) modelling
(b) prototyping
(c) CASE tools
‡ List and explain five phases of the SDLC:
(a) planning
(b) analysis
(c) design
(d) implementation
(e) support
 




c



 Ä


‡ Models are needed in order to help the

analyst to understand the functionality of
the system and models are used to
communicate with customers.
 Ä
Ä

‡ Types of modelling:
i) Data processing model ± data is
processed at different stages

ii) Composition model ± entities are

composed of other entities
 Ä
Ä

iii) Architectural model ± showing principal

sub-system

iv) Classification model ± entities have

common characteristics

v) Stimulus/response model ± system¶s

reaction to events
 Ä
Ä

Èeaknesses of using Modelling

(a) They do not model non-functional
requirements
(b) They do not usually include information about
whether a method is appropriate for a given
problem
(c) They may produce too much documentation
(d) Too detailed and difficult for users to
understand.
 Ä



‡ Prototyping is the process of building a

model of a system.
‡ In terms of an information system,
prototypes are employed to help system
designers build an information system
that intuitive and easy to manipulate for
end users.
‡ Prototyping is an iterative process that is
part of the analysis phase of the SDLC
 Ä

Ä

‡ Advantages of Prototyping:
(a) Reduces development time.
(b) Reduces development costs.
(c) Requires user involvement.
(d) Developers receive
quantifiable user feedback.
(e) Facilitates system implementation
since users know what to expect.
(f) Results in higher user satisfaction.
(g) Exposes developers to potential
future system enhancements.
 Ä

Ä

‡ Disadvantages of prototyping:
(a) Can lead to insufficient analysis.
(b) Users expect the performance of the
ultimate system to be the same as the
prototype.
(c) Developers can become too attached
to their prototypes.
(d) Can cause systems to be left
unfinished and / or implemented
before they are ready.
Ä

Ä

(e) Sometimes leads to incomplete

documentation.
(f) If sophisticated software prototypes
(4th GL or CASE Tools) are employed,
the time saving benefit of prototyping
can be lost.
 Ä



‡ CASE is the abbreviation of Computer-

Aided Software Engineering.
‡ CASE tools are productivity tools for
systems analysts that have been created
explicitly to improve their routine work
through the use of automated support
Ä

Ä

‡ Reasons for using CASE tools

- Increasing Analyst Productivity
- Improving Analyst-User
Communication
- Integrating Life Cycle Activities
- Accurately Assessing Maintenance
Changes
Ä

Ä

‡ O
O




1. Upper CASE tools perform analysis and
design

2. Lower CASE tools generate programs

from CASE design

3. Integrated CASE tools perform both

upper and lower CASE functions
Ä

Ä

‡ Upp O

- Create and modify the system design

- Help in modeling organizational

requirements and defining system
boundaries

- Can also support prototyping of screen

and report designs
Ä

Ä

‡ V O


- Lower CASE tools generate computer

source code from the CASE design

- Source code is usually generated in

several languages

-Traditional versus CASE systems

development life cycle
 c  

Program
Design Specification Program Bugs Installation
Questions Questions and Errors Bugs

Program
Analysis Design Design & Program Installation
Coding Testing
Require Program Program Completed
ments Specs Source System
Code
 
 


p
VO 

Design Design Flaws &

Questions Inconsistencies

Analysis Design Upper CASE Lower CASE Installation

Toolset Toolset
Require CASE CASE Error-Free
(Code
ments Design Repository Computer
Generation)
Entities System

O


p
VO 
 c
  

MODELLING PROTOTYPING CASE tools

Abstract Process of building Software systems
descriptions of a model of a which are intended
system system to provide
automated support
for software
process activities.
c
c





c
!


Ä

‡ The systems development life cycle is a
phased approach to solving business
problems
‡ Developed through the use of a specific
cycle of analyst and user activities
‡ Each phase has unique user activities
‡ The systems development life cycle
(SDLC) is a general term used to describe
the method and process of developing a
new information system
‡ Èithout the structure and organization
provided by SDLC approach projects are
at risk for missed deadline, low quality etc.
‡ SDLC provides
± Structure
± Methods
± Controls
± Checklist
Needed for successful development

"  "

‡ The VO is composed of five fundamental

phases (major phases):
± Planning
± Analysis
± Design
± Implementation
± Support
‡ Each of the phases include a set
of steps, which rely on
techniques that produce specific
document files that provide
understanding about the project.

" #
 
‡ This phase is the fundamental process of
understanding why an information system
should be built.

‡ The Planning phase will also determine

how the project team will go about building
the information system.

‡ The Planning phase is composed of two

planning steps.
c$
 
1. During p 


, the
system¶s business value to the
organization is identified (How will
it lower costs or increase
revenues?)
2. During p 
  
, the
project manager creates a work
plan, staffs the project, and puts
techniques in place to help the
project team control and direct the
project through the entire SDLC.

" # 
‡ The analysis phase answers the questions of who
will use the system, what the system will do, and
where and when it will be used.

‡ During this phase the project team investigates

any current systems, identifies improvement
opportunities, and develops a concept for the
new system.

‡ This phase has three analysis steps.

 c" 

  




: This is developed to guide
the projects team¶s efforts. This includes an
„
„ 
analysis of the current system.
m  


 : The analysis of this
information leads to the development of a
concept for a new system. This concept is
used to build a set of analysis models.
 

p p
: The proposal is presented
to the project sponsor and other key
individuals who decide whether the project
should continue to move forward.
‡ The system proposal is the initial deliverable that
describes what business requirements the new
system should meet.

‡ The deliverable from this phase is both an

analysis and a high-level initial design for the
new system.

" #
‡ Is the process of defining the
architecture, components,
modules, interfaces and data for
a system to satisfy specified
requirements
 !
 


: This clarifies
whether the system will be developed
by the company or outside the
company.

m  

 
: This describes
the hardware, software, and network
infrastructure that will be used.

 
  
 Define the software
that will be used and how the system
will look alike.
: 

 !p 


These documents define what and
where the data will be stored.

" „  
: Defines what

programs need to be written and
what they will do.

" # 

  
‡ During this phase, the system is
either developed or purchased (in
the case of packaged software).

‡ This phase is usually the longest

and most expensive part of the
process.

‡ The phase has three steps.

c" 



O


: The system
is built and tested to make sure it
performs as designed.

m


: Prepare to support the
installed system.

pp
„ : Includes a post-
implementation review.

" #%
‡ Is needed by the customer to
make sure that problems will be
solved.
‡ The developer should be giving
training and support according
to their agreement with the
customer.
 % 
„
 „


„


 „
„

 „

 



 


 



 


„