System Development Methods
CT00046-3-2
Structured Methodologies
Topic & Structure of the Lesson
• Introduction to Structured Methodologies
• Techniques and Tools
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 2
Slide 3 (of 17)
Learning Outcomes
• By the end of this lecture, YOU should be able to :
– Identify and explain the underlying principles for Systems
Development Methodology
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 3
Slide 4 (of 17)
Key Terms you must be able to use
• If you have mastered this topic, you should be able to use
the following terms correctly in your assignments and
exams:
– IS Structured Methodologies
– Techniques and Tools
– Waterfall Model
– SSADM
– V-Model
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 4
Era of IS Methodologies
IS Methodologies
Traditional / Structured
Modern Methodologies
Methodologies
Late 70s’ to early 90s’ Late 90s’ to today
(Ex; SSADM, Waterfall,
(Ex; Scrum, RAD, DSDM, etc)
V-Model, etc)
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 5
Slide 5 (of 19)
Structured Methodologies
• Developed in the 70’s
• Mostly Traditional Methodologies
• Very detailed steps explained
– Formulation for beginners to develop a system.
• Requirements need to be clear and fixed.
• Focus on error free product
• Rigid and strict rules
• Emphasis on full documentation.
• Example methodologies;
– Waterfall Model, SSADM, V-Model
– (we will take a look at these three)
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 6
Waterfall Model
• Close to SDLC phases
• Can be used for almost all types of
projects
• Highly structured and rigid -
sequential development process
– One should move to the next phase only
when its preceding phase is completed
and perfected.
• Promotes quality control of process and
product.
• Good for beginners.
• Emphasis on good documentation
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 7
Waterfall Model
Stages
• Requirement Gathering and analysis
– All possible requirements of the system to be developed are captured and
documented into System Requirement Specification (SRS) document.
• System Design
– The SRS is studied and system design is prepared.
– System Design helps in specifying hardware and system requirements and also helps
in defining overall system architecture.
• Implementation
– With inputs from system design, the system is first developed in small programs
called units, which are integrated in the next phase.
– Each unit is developed and tested for its functionality which is referred to as Unit
Testing.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 8
Waterfall Model
Stages .. cont
• Integration and Testing
– All the units developed in the implementation phase are integrated into a system
after testing of each unit.
– Post integration the entire system is tested for any faults and failures.
• Deployment of system
– Once the functional and non functional testing is done, the product is deployed in the
customer environment or released into the market.
• Maintenance
– There are some issues which come up in the client environment. To fix those issues
patches are released.
– Also to enhance the product some better versions are released.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 9
Structured Systems Analysis And Design
Method (SSADM)
• Popular methodology
used in the late 80s
• Rigid and document-led
approach to system
design
• Have detailed DESIGN
stage.
• Good for projects with
database design.
• Has strategies to align
business needs with
system development.
• Ends at design stage.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 10
SSADM
Techniques
• Logical Data Modeling
– To determine the high level requirement for the system
– System components, entities, main process, etc.
• Data Flow Modeling
– To determine the ‘movement’ of data within the system
– Data transformation, storage, data flow, etc.
• Entity Event Modeling
– To determine the processes and operations
– Event sequence, dependency, etc.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 11
V-Model
• Derived and modified from Waterfall Model
• Emphasize of ‘check and balance’ of development process
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 12
V-Model
Techniques
• Takes the ‘top-down’ development approach
– Concept, Architecture Design, high level design, etc.
• Verification and Validation at end of each phase / process.
– Referring back to project documentation, objectives, scopes,
requirements, specifications, etc.
– Users are consulted for verification and validation.
• Use various testing techniques for product
– Unit, integration, system, user acceptance, etc.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 13
Quick Quiz
• Explain to your class, the process flow within a V-Model?
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 14
Problems with Structured Methodologies
(in general)
• Rigid phases, discourage skipping of unimportant steps.
• Emphasize of process and product quality rather then
customer satisfaction
• Requirement need to be defined in the beginning of the
project and not encouraged to change towards the end.
• Cost and time often unpredictable for large projects.
• Too many ‘red-tapes’, wasting time and resources
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 15
Question & Answer
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 16
Next Session
• Agile Methods
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 17
Tutorial Questions
• Find names of a few popular methodologies used today.
What are the types of project that they are used for?
• Discuss the advantages using IS Development
Methodologies.
• Discuss the distinctive disadvantages using the following IS
Development Methodologies.
– Waterfall model
– SSADM
– V-Model
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 18