Академический Документы
Профессиональный Документы
Культура Документы
methodologies
Learning Outcomes
By the end of this lecture, YOU should be
able:
Define Systems Development Methodology
Explain the importance of Systems
Development Methodology
Identify the examples of systems
Development Methodology
Methodologies
What is a methodology?
A methodology is a framework, or a blue print of
processes which contains procedures,
definitions and explanations of techniques used
to collect, store, analyse and present information
as part of a research process in systems
development life cycle.
It has a pre-set set of activities that can be
executed in software development
CT026-3-1 Systems Analysis and Design
Slide 5 (of
Methodologies
Why do we need a methodology?
To ensure the success of a system.
To communicate between the various groups
involved in the development of the project.
To have a systematic approach to software
development, where the deliverables are specified
precisely.
To manage the whole project by breaking down the
development process into small tasks and ordering, to
ease scheduling and monitoring.
Slide 6 (of
Methodologies
Methodologies
Different methodologies
Suitable for building different systems
Blended methodologies
for the development of Information systems.
SSADM
Information Engineering
CT026-3-1 Systems Analysis and Design
Methodologies
Different methodologies
OO methodologies
OO Analysis
RUP Rational Unified Process
SSADM
Structured Systems Analysis and Design
Methodology
supported by CASE tool
clearly define deliverables
quality checkpoints
SSADM
Major tools
Logical Data Modeling
Logical Data Structure
ER Model - Entities & Relationships
Documentation
SSADM
Version 4 7 stages
Feasibility
Involves conducting a high level analysis of a
business area to determine whether a system can
cost effectively support the business requirements.
SSADM
Business system options
describes a suggested new system in terms of its
functionality and its boundary: inputs, outputs,
processes and data are described
Requirements Specifications
determine the desired system data, functions and
events
Slide 13 (of
SSADM
Logical design
defines dialogues, updates and enquiries
Physical design
create a physical database design and a set
of program specifications
Slide 14 (of
OOAD
Wide range of OO methodologies
Different focus:
Design and implementation
Analysis
Particular modeling technique
Particular implementation language
OOAD
different approaches and methodologies
created by:
Grady Booch
Coad and Yourdon
Martin and Odell
Rumbaugh et al
Jacobson et al
Problem arising:
No standardisation
CT026-3-1 Systems Analysis and Design
OOAD
OO life cycle
analysis
design
implementation
Deliverables
diagrams
repository description
OO
objects used
code and data bundled in
an object
incremental and iterative
use case
implies data flow
has no equivalent to data
store
Similarities
Follow Up Assignment
List and explain the differences between
SSADM and Object-oriented in terms of
the activities and phases involved.
Q&A
CT026-3-1 Systems Analysis and Design
Next Session
Introduction to Structured Method
Techniques
Data Flow Models
Data Flow Diagrams
Context Diagram
Level 0
Level 1
Data Dictionary
Process Description