1

SYSTEM DEVELOPMENT
APPROACHES
 SYSTEM DEVELOPMENT APPROACHES 2

• Traditional (Structured) approach

• Also called structured system development
• Structured analysis and design technique (SADT)
• Includes information engineering (IE)

• Object-oriented approach
• Also called OOA, OOD, and OOP
• Views information system as collection of interacting objects that
work together to accomplish tasks

• Agile/Adaptive method
▪ attempt to develop a system incrementally,
▪ by building a series of prototypes and constantly adjusting them to
user requirements.
 3

• Traditional (Structured) approach

• Also called structured system development
• Structured analysis and design technique (SADT)
• Includes information engineering (IE)
 4

• Object-oriented approach
• Also called OOA, OOD, and OOP
• Views information system as collection of interacting
objects that work together to accomplish tasks
 5

Agile/Adaptive method
▪ attempt to develop a system incrementally,
▪ by building a series of prototypes and constantly adjusting them to user
requirements.
 6

SYSTEM DEVELOPMENT
LIFE CYCLES (SDLC)
 7

PLANNING
• to perform a preliminary investigation to evaluate an IT-
related business opportunity or problem.

• The preliminary investigation is a critical step because the

outcome will affect the entire development process.

• A key part of the preliminary investigation is a feasibility

study that reviews anticipated costs and benefits and
recommends a course of action based on operational,
technical, economic, and time factors.
 8

ANALYZE

• to build a logical model of the new system. The first step is

requirements modeling, where you investigate
• business processes and document what the new system must do to
satisfy users.

• Requirements modeling continues the investigation that began during

the systems planning phase. To understand the system, you perform fact-
finding using techniques such as interviews, surveys, document review,
observation, and sampling, questinaire.
 9

DESIGN

• is to create a physical
• model that will satisfy all documented requirements for the system. At
this stage, you
• design the user interface and identify necessary outputs, inputs, and
processes. In addition,
• you design internal and external controls, including computer-based and
manual
• features to guarantee that the system will be reliable, accurate,
maintainable, and secure.
 10

DEVELOPMENT

• The real code is written here.

 11

TESTING

• Once the code is generated, the software program testing

begins. Different testing methodologies are available to
unravel the bugs that were committed during the previous
phases. Different testing tools and methodologies are already
available. Some companies build their own testing tools that
are tailor made for their own development operations.
 12

IMPLEMENTATION

• to deliver a completely functioning and documented information

• system. At the conclusion of this phase, the system is ready for use. Final
preparations
• include converting data to the new system’s files, training users, and
performing
• the actual transition to the new system.
 13

MAINTENANCE

• The software will definitely undergo change once it is delivered

to the customer. There can be many reasons for this change to
occur. Change could happen because of some unexpected input
values into the system. In addition, the changes in the system
could directly affect the software operations. The software
should be developed to accommodate changes that could
happen during the post implementation period.
 14

VARIOUS TYPES OF LIFE

CYCLE MODELS
• a. Waterfall model
• b. Spiral Model
• c. Iterative and incremental development
• d. Agile Model
• e. Prototyping model
• f. Rapid Application Development (RAD)
• g. Joint Application Development (JAD)
• h. Extreme Programming (XP)
 15

WATERFALL MODEL
• The waterfall Model is a linear sequential flow. In which progress
is seen as flowing steadily downwards (like a waterfall) through
the phases of software implementation. This means that any phase
in the development process begins only if the previous phase is
complete. The waterfall approach does not define the process to go
back to the previous phase to handle changes in requirement. The
waterfall approach is the earliest approach that was used for
software development.
 16

SPIRAL MODEL
• It is combining elements of both design and prototyping-in-stages,
in an effort to combine advantages of top-down and bottom-up
concepts. This model of development combines the features of the
prototyping model and the waterfall model. The spiral model is
favored for large, expensive, and complicated projects. This model
uses many of the same phases as the waterfall model, in essentially
the same order, separated by planning, risk assessment, and the
building of prototypes and simulations.
 17

ITERATIVE AND
INCREMENTAL DEVELOPMENT
• It is developed to overcome the weaknesses of the waterfall model.
It starts with an initial planning and ends with deployment with the
cyclic interactions in between. The basic idea behind this method
is to develop a system through repeated cycles (iterative) and in
smaller portions at a time (incremental), allowing software
developers to take advantage of what was learned during
development of earlier parts or versions of the system.
 18

AGILE MODEL
• Agile Modeling (AM) is a practice-based methodology for
effective modeling and documentation of software-based systems.
At a high level AM is a collection of best practices, depicted in the
pattern language map below (click on the practice for information).
At a more detailed level AM is a collection of values, principles,
and practices for modeling software that can be applied on a
software development project in an effective and light-weight
manner.
 PROTOTYPING MODEL 19

• It refers to the activity of creating prototypes of software

applications, for example, incomplete versions of the software
program being developed. It is an activity that can occur in software
development. It used to visualize some component of the software to
limit the gap of misunderstanding the customer requirements by the
development team. This also will reduce the iterations may occur in
waterfall approach and hard to be implemented due to inflexibility of
the waterfall approach. So, when the final prototype is developed, the
requirement is considered to be frozen.
 20

EXTREME PROGRAMMING

• It is based on iterative and incremental development, where

requirements and solutions evolve through collaboration between
cross-functional teams.
 21

REFERENCES
• https://en.wikipedia.org/wiki/Information_system
• https://en.wikipedia.org/wiki/Systems_development_life_cycle
• https://melsatar.wordpress.com/2012/03/15/software-development-
life-cycle-models-and-methodologies/

• Shelly, G. B., Rosenblatt, H. J. (2012). Analysis and Design for

Systems, 9th edition, Thompson Course Technology.