Systems Analysis and Design in A Changing World, 7th Edition - Chapter 10 ©2016. Cengage Learning. All Rights Reserved. 1

Chapter 10
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 10 ©2016. Cengage Learning. All rights reserved. 1
Approaches to System Development
Chapter 10
Systems Analysis and Design in a Changing World 6th Ed

Satzinger, Jackson & Burd
Systems Analysis and Design in a Changing World, 7th edition - Chapter 10 ©2016. Cengage Learning. All rights reserved. 2
Chapter 10: Outline
The System Development Life Cycle
Methodologies, Models, Tools, and Techniques
Agile Development
The Unified Process, Extreme Programming, and
Scrum
Learning Objectives
Compare the underlying assumptions and uses of a
predictive and an adaptive system development life
cycle (SDLC)
Explain what makes up a system development
methodology—the SDLC as well as models, tools, and
techniques
Describe the key features of Agile development
Understand and describe the key features of the
Unified Process, Extreme Programming, and Scrum
Agile system development methodologies
Overview
Chapter 1 demonstrated a system development project that used
an iterative and agile system development life cycle (SDLC)
Later chapters focused on Systems Analysis activities and tasks
and some System Design activities and tasks
Now we return to look at the SDLC and related concepts in more
detail
Predictive versus Adaptive SDLC variations
Activities and Tasks of System Support
Models, Methodologies, Tools and Techniques
Agile Development
Specific SDLC Approaches
Unified Process (UP)
Extreme Programming (XP)
Scrum
(SDLC) (1 of 2)
There are two general approaches to the SDLC
Predictive Approach to the SDLC
Waterfall model
Assumes the project can be planned in advance and that the
information system can be developed according to the plan
Requirements are well understood and/or low technical risk
Adaptive Approach to the SDLC
Iterative model (as see in this text)
Assumes the project must be more flexible and adapt to changing
needs as the project progresses
Requirements and needs are uncertain and/or high technical risk
(SDLC) (2 of 2)
Most projects fall on a continuum between Predictive and
Adaptive
Traditional Predictive SDLC
Earlier approach based on engineering

Typically have sequential Phases
Phases are related groups of development
activities, such as planning, analysis, design,
implementation, and deployment
Waterfall model
SDLC that assumes phases can be completed
sequentially with no overlap or iteration
Once one phase is completed, you fall over the
waterfall to the next phase, no going back
Tradition IS Development Phases
Waterfall Predictive SDLC
Modified Waterfall with Overlapping Phases
More flexibility, but still assumes predictive planning

and sequential phases
Newer Adaptive SDLC
Emerged in response to increasingly complex

requirements and uncertain technological
environments
Always includes iterations where some of design and
implementation is done from the beginning
Many developers claim it is the only way to develop
information systems
Many IS managers are still sceptical due to apparent
lack of overall plan
Adaptive Approaches
Incremental development
Completes portions of the system in small
increments and integrated as the project
progresses
Sometimes considered “growing” a system
Walking Skeleton
The complete system structure is built first, but
with bare-bones functionality
A Generic Adaptive Approach
Six Core Processes go across iterations

Multiple Iterations as required
Methodologies, Models, Tools, and
Techniques (1 of 6)
Methodologies
Provides guidelines for every facet of system development:
What to do when, why and how
Specifies an SDLC with activities and tasks
Specifies project planning and project management models
and reporting
Specifies analysis and design models to create
Specifies implementation and testing techniques
Specifies deployment and support techniques
Other term used is System Development Process
Methodologies
A Methodology includes a collection of techniques
that are used to complete activities and tasks,
including modeling, for every aspect of the project
Techniques (2 of 6)
Model
An abstraction of an important aspect of the real world.
Makes it possible to understand a complex concept by
focusing only on a relevant part
Each model shows a different aspect of the concept
Crucial for communicating project information
In IS, some models are of system components that will
be developed
Other models are used to manage the development
process
Techniques (3 of 6)
Some models of system components
Use case diagram
Domain model class diagram
Design class diagram
Sequence diagram
Package diagram
Screen design template
Dialog design storyboard
Entity-relationship diagram (E RD)
Database schema
Some models used to manage the development process
Gantt chart
Organizational hierarchy chart
Financial analysis models—N PV, payback period
System development life-cycle model
Stakeholders list
Iteration plan
Techniques (4 of 6)
Tools
Software applications that assists developers in
creating models or other components required for
a project
Integrated Development Environment (IDE)
set of tools that work together to provide a
comprehensive development environment
Visual Modeling Tools
Tools to create graphical models
Techniques (5 of 6)
Some typical tools
Project management application
Drawing/graphics application
Word processor/text editor
Visual modeling tool
Integrated development environment (IDE)
Database management application
Reverse-engineering tool
Code generator tool
Methodologies, Models, Tools, and Techniques (6 of 6)
Technique
A collection of guidelines that help an analyst complete an activity or task
Learning techniques is the key to having expertise in a field
Strategic planning techniques
Project management techniques
User-interviewing techniques
Data-modeling techniques
Relational database design techniques
Structured programming techniques
Software-testing techniques
Process modeling techniques
Domain modeling techniques
Use case modeling techniques
Object-oriented programming techniques
Architectural design techniques
User-interface design techniques
Agile Development (1 of 2)
A guiding philosophy and set of guidelines for

developing information systems in an unknown,
rapidly changing environment
Chaordic
A term for adaptive projects – chaotic yet ordered
Agile Development (2 of 2)
Agile Values in “Manifesto for Agile Software

Development”
Value responding to change over following a plan
Value individuals and interactions over processes
and tools
Value working software over comprehensive
documentation
Value customer collaboration over contract
negotiation
Agile Modeling Principles
Agile Modeling (AM) – 12 Principles

A philosophy – build only necessary models that are useful
and at the right level of detail
Agile Principles (1 of 3)
Develop software as the primary goal

Don’t get distracted by documentation or models
Enable the next effort as your secondary goal
Be aware of next step versions or revisions
Minimize your modeling activity
Only build what helps move the project forward
Embrace change and change incrementally
Take small steps that keep you on-track and that
can be reversed if necessary
Model with a purpose

Model to understand
Model to communicate
Build multiple models
Look at problems from different perspectives
Build high-quality models and get feedback
Focus on content rather than representation
Informal hand-drawn models are sometimes okay
Always focus on stakeholder needs
Learn from each other with open communication

Know your models and how to use them
Adapt to specific project needs
Maximize stakeholder RMI
The Unified Process (UP)
The UP was the early leader in adaptive approaches
UP and UML (Unified Modeling Language) were
developed together
The Unified Process (UP) – Phases
UP Phases organize iterations into four primary
areas of focus during a project
Inception phase – getting the project started
Elaboration – understanding the system
requirements
Construction – building the system
Transitions – preparing for and moving to deploying
the new system
Unified Process (UP) – Phases (1 of 2)
UP SDLC divides iterations into four phases
Unified Process (UP) – Phases (2 of 2)
Objectives of each phase

UP Phase Objective
Inception Develop an approximate vision of the system, make the business case,
define the scope, and produce rough estimates for cost and schedule.
Elaboration Define the vision, identify and describe all requirements, finalize the
scope, design and implement the core architecture and functions,
resolve high risks, and produce realistic estimates for cost and
schedule.
Construction Iteratively implement the remaining lower-risk, predicable, and easier
elements and prepare for deployment.
Transition Complete the beta test and deployment so users have a working
system and are ready to benefit as expected.
Unified Process – Disciplines (1 of 4)
A set of functionally related development activities

Each discipline are all the activities related to
achieving one objective in the development project
Two types of disciplines
Development disciplines
Management – planning and control disciplines
Development Disciplines
Business modeling
Requirements
Design
Implementation
Testing
Deployment
Planning and Control disciplines

Configuration and change management
Project management
Environment
Disciplines are used across all iterations
Extreme Programming (XP) (1 of 3)
Takes the best practices of software development

and extends them “to the extreme”
Focus intensely on proven industry practices
Combine them in unique ways to get better results
XP Core Values
Communication
Simplicity
Feedback
Courage
XP Practices
Planning – based on user stories
Testing – thorough testing at every step
Pair Programming – watch, inspect, trade off
Simple Designs – Agile modeling principles
Refactoring – redo and cleanup as you go
Owning the code collectively – egoless
development, anyone can review and improve code
XP Practices
Continuous integration – grow the software
continuously
On-site customer – get sign-off as you go
System metaphor – what should the final system
look like
Small releases – turn over to user frequently
Forty-hour work week – don’t overload the
developers
Coding standards – follow standards for code
XP Core Values
and Practices
XP Project Approach (1 of 2)
Three level approach (three rings)

Outside ring – create user stories and define
acceptance tests
Middle ring – conduct tests and do overall planning
Inside ring – iterations of coding and testing
XP Project Approach (2 of 2)
SCRUM
Combination of principles of Rugby and Agile
Intense effort involving the entire team for a
defined period of time
Product backlog
Prioritized list of user requirements
Product owner
The client stakeholder who controls backlog
Scrum master
Scrum project manager
Scrum Sprint
Scrum sprint
A time-controlled mini-project to implement part of
the system
Scrum Practices
Scope of each sprint is frozen (but can be reduced if

necessary)
Time period is kept constant
Daily Scrum meeting
What have you done since the last daily Scrum
(during the last 24 hours)?
What will you do by the next daily Scrum?
What kept you or is keeping you from completing
your work?
Summary (1 of 2)
This chapter covers approaches to system development
in more detail
There are two approaches to the SDLC: Predictive and
Adaptive
A predictive SDLC, also known as the waterfall model, is
used when it is possible to plan the project completely
in advance
An Adaptive SDLC, which uses iteration, is used when
the requirements are less certain and the project will
need to react to changes
Summary (2 of 2)
All new System development project use a methodology
(or development process) and many are available. A
methodology includes an SDLC and tools, techniques, and
models
Agile development is the current trend in system
development
Unified Process is a formal iterative approach which uses
UML models (with Agile philosophy) and U P disciplines
Extreme Programming (XP) is an iterative approach which
takes good practices to the extreme
Scrum is an iterative approach using a Scrum Sprint

Systems Analysis and Design in A Changing World, 7th Edition - Chapter 10 ©2016. Cengage Learning. All Rights Reserved. 1

Uploaded by

Copyright:

Available Formats

Systems Analysis and Design in A Changing World, 7th Edition - Chapter 10 ©2016. Cengage Learning. All Rights Reserved. 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems Analysis and Design in A Changing World, 7th Edition - Chapter 10 ©2016. Cengage Learning. All Rights Reserved. 1

Uploaded by

Copyright:

Available Formats

What are the two general approaches to the system development life cycle?

What are the two general approaches to the system development life cycle?

What are some agile development methodologies discussed in the chapter?

What are some agile development methodologies discussed in the chapter?

Chapter 10

Systems Analysis and Design in a Changing World 6th Ed

Earlier approach based on engineering

More flexibility, but still assumes predictive planning

Emerged in response to increasingly complex

Six Core Processes go across iterations

A guiding philosophy and set of guidelines for

Agile Values in “Manifesto for Agile Software

Agile Modeling (AM) – 12 Principles

Develop software as the primary goal

Model with a purpose

Learn from each other with open communication

UP SDLC divides iterations into four phases

Objectives of each phase

A set of functionally related development activities

Planning and Control disciplines

Disciplines are used across all iterations

Takes the best practices of software development

Three level approach (three rings)

Scope of each sprint is frozen (but can be reduced if

You might also like