UNIVERSITY OF INFORMATION TECHNOLOGY
Faculty of Information Systems
SYSTEM DEVELOPMENT
METHODOLOGIES
Dr. Cao Thi Nhan
System development methods
1. Systems Development Life Cycle (SDLC)
2. Object-oriented systems analysis and
design
3. The agile approach
1-2
Systems Development Life Cycle (SDLC)
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
1-3
The Seven Phases of the Systems
Development Life Cycle (Figure 1.1)
1-4
Systems Development Life Cycle
1. Identifying Problems, Opportunities, and
Objectives
2. Determining Human Information Requirements
3. Analyzing System Needs
4. Designing the Recommended System
5. Developing and Documenting Software
6. Testing and Maintaining the System
7. Implementing and Evaluating the System
1-5
1. Identifying Problems,
Opportunities, and Objectives
Activity:
Interviewing user management
Summarizing the knowledge obtained
Estimating the scope of the project
Documenting the results
Output:
Feasibility report containing problem definition and
objective summaries from which management can
make a decision on whether to proceed with the
proposed project
1-6
2. Determining Human Information
Requirements
Activity:
Interviewing
Sampling and investing hard data
Questionnaires
Observe the decision maker’s behavior and
environment
Prototyping
Learn the who, what, where, when, how, and why
1-7
of the current system
2. Determining Human Information
Requirements
Output:
The analyst understands how users accomplish
their work when interacting with a computer
Begin to know how to make the new system more
useful and usable
Know the business functions
Have complete information on the: People, Goals,
Data, and Procedure involved
1-8
3. Analyzing System Needs
Activity:
Create data flow, activity, or sequence
diagrams
Complete the data dictionary
Analyze the structured decisions made
Prepare and present the system proposal
Output:
Recommendation on what, if anything, should
1-9
be done
4. Designing the Recommended
System
Activity:
Design procedures for data entry
Design the human-computer interface
Design system controls
Design database and/or files
Design backup procedures
Output
Model of the actual system
1-10
5. Developing and Documenting
Software
Activity:
System analyst works with programmers to develop
software
Works with users to develop effective documentation
Programmers design, code, and remove syntactical errors
from computer programs
Document software with help files, procedure manuals, and
Web sites with Frequently Asked Questions
Output:
Computer programs
1-11 System documentation
6. Testing and Maintaining the
System
Activity:
Test the information system
System maintenance
Maintenance documentation
Output:
Problems, if any
Updated programs
Documentation
1-12
7. Implementing and Evaluating the
System
Activity:
Train users
Analyst plans smooth conversion from old system to
new system
Review and evaluate system
Output:
Trained personnel
Installed system
1-13
The Impact of Maintenance
Maintenance is performed for two reasons:
Removing software errors
Enhancing existing software
Over time the cost of continued maintenance
will be greater than that of creating an
entirely new system. At that point it
becomes more feasible to perform a new
systems study.
1-14
Systems development life cycle
Waterfall method
Object-Oriented (O-O) Systems Analysis
and Design
Alternate approach to the structured
approach of the SDLC that is intended to
facilitate the development of systems that
change rapidly in response to dynamic
business environments
Analysis is performed on a small part of the
system followed by design and
implementation
1-16
Object-Oriented (O-O) Systems
Analysis and Design
The cycle repeats with analysis, design,
and implementation of the next part
and this repeats until the project is
complete
Examines the objects of a system
1-17
Unified Modeling Language (UML)
Phases
Define the use case model:
Use case diagram
Use case scenarios
Create UML diagrams
Develop class diagrams
Draw state diagrams
Modify the UML diagrams
Develop and document the system
1-18
1-19
The Agile Approach
Agile manifesto, 2001
Individuals and interactions over processes
and tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a plan
“That is, while there is value in the items on the right,
1-20 we value the items on the left more”
Four Agile Resources
Resources are adjusted to ensure
successful project completion
Time
Cost
Quality
Scope
1-21
Five Stages of Agile Development
Exploration
Planning
Iterations to the first release
Productionizing
Maintenance
1-22
Agile Project Development Process
(Figure 1.5)
1-23
Some methods of Agile Development
Scrum
Kanban
XP-Extreme Programming
…
1-24
Scrum meeting
1. Planning
2. Daily
3. Review
4. Retrospective
1-25
Group Discussion
❑ Group: 5 students; Time: 5 minutes.
❑ Watch the video, and comment on: tasks,
manager’s behaviors, staff’s behaviors.
26
Agile Project Development Process
1-27
Choosing a Method
Choose either:
SDLC
Agile
Object-oriented methodologies
1-28
Choosing a Method
Stacey matric
1-29
Some Researchers Estimate that the Amount of Time Spent on
Systems Maintenance May Be as Much as 60 Percent of the Total
Time Spent on Systems Projects (Figure 1.2)
1-31
Resource Consumption over the
System Life (Figure 1.3)
1-32
