TERMS

 Waterfall model: An SDLC approach that assumes that phases can be

completed sequentially with no overlap.
 Incremental development: an SDLC approach that completes portions
of the system in small increments across iterations, with each increment
being integrated into the whole as it is completed.
 Walking skeleton: a development approach in which the complete
system structure is built but with bare-bones functionality.
 Integrated development environment (IDE): Sets of tools that work
together to provide a comprehensive development and programming
environment for software developers.
 Visual modelling tools: tools that help analysts create and verify
graphical models and may also generate program code.
 Agile development: a guiding philosophy and set of guidelines for
developing information systems in an unknown, rapidly changing
environment.
 Agile modelling (AM): a guiding philosophy in which only models that
are necessary, with a valid need and at the right level of detail, are
created.

Compare the underlying assumptions and

uses of a predictive and an adaptive system
development life cycle (SDLC)
The SDLC provides a way to think about the development of a new system as a
progressive process, much like a living entity.
A predictive approach to the SDLC assumes that the development project can
be planned and organised and that the new information system can be
developed according to plan
Predictive SDLCs are useful for building systems that are well understood and
defined
An adaptive approach to the SDLC is used when the systems requirements or
the user’s needs aren’t well understood. In this situation, the project can’t be
planned completely.
Some system requirements may need to be determined after preliminary
development work. Developers should still be able to build a solution, but they
need to be flexible and adapt to the project as it progresses.
Related groups of development activities are called Phases.
These 6 groups of activities, sometimes referred to as phases of system
development project, are:
 Project initiation
 Project planning
 Analysis
 Design
 Implementation
 deployment
These activities provide the framework for managing the project.
Another phase called the support phase, includes the activities needed to
upgrade and maintain the system after it has been deployed.
The objective of the support activities is to keep the system running productively
during the years following its initial deployment.
They begin only after the new system has been installed and put into production,
and they last right through the productive life of the system.
During the support phase, upgrades and enhancements may be carried out to
expand the system capabilities, and these will require their own development
projects. Three major activities occur during support:
 Maintaining the system
 Enhancing the system
 Supporting the users

The most predictive SDLC approach is called the waterfall model, with phases
of the project flowing down, one after another. This model assumes that the
phases can be carried out and completed sequentially, with no overlap. In
practice, the waterfall model assumes rigid planning and final decision making at
each step of the decision-making process.
In adaptive approaches to the SDLC, project activities like planning and
modelling are adjusted as the project progresses.
These approaches incorporate iterations, which divide the project into smaller
parts, each analysed, designed, built, and tested before moving on to the next
iteration. This allows the project to adapt to changes and ensures user feedback
is integrated early, increasing the likelihood that the final product meets user
needs.
Each iteration carries out the core processes of SDLC – analysis, design, and
implementation - enabling modifications to be made as the project evolves. This
adaptive approach simplifies the Unified Process (UP), a formal iterative
method.
Two related concepts are incremental development and the walking
skeleton:
 Incremental development builds the system in small increments,
integrating each completed part with the rest. This approach allows
portions of the system to be delivered sooner, enabling the business to
benefit earlier.
  The walking skeleton is a minimal version of the system developed
early in the project, providing basic front-to-back functionality. Later
iterations expand its capabilities.
Both approaches emphasize getting working software into users’ hands early and
benefit from extensive user testing and feedback, ensuring the project adapts as
it progresses.

Explain what makes up a system

development methodology-the SDLC as well
as models, tools, and techniques
In SDLC, professionals use various aids to guide them through the tasks,
including methodologies, models, tools and techniques
 Methodologies provide comprehensive guidelines for every aspect of
system development. They define the process for completing tasks and
often include models (e.g., diagrams) to describe system requirements,
techniques (e.g. guidelines for conducting interviews), and tools (e.g.,
software to build models and write code).

Methodologies can be formal, with extensive documentation, or informal,

offering general guidance. The chosen methodology influences whether
the system development project follows a predictive or adaptive approach.
 Models are representations used to specify system requirements and
solutions, such as diagrams that help clarify the structure or behaviour of
a system.

Developers also use project-planning models, such as Gnatt charts or Net

Present Value (NPV) calculations, to represent tasks and resources within a
system development project. Additionally, models may represent the
people involved in the project.

 Tools are typically computer-based software that assist in creating

models, recording information, or writing code.

These tools can range from simple drawing programs for diagrams to more
advanced applications that store information, such as data definitions and
use case descriptions.

Programmers commonly use IDEs to help aid programming tasks. As well

as visual modelling tools to design models such as class diagrams or
activity diagrams, and help with database design.

 Techniques are specific ways of performing tasks, such as interviewing

users or modelling system requirements. They often provide step-by-step
instructions for creating models or offer general advice on collecting
information from users.

Examples include data-modelling, software testing, user interviewing, and

relational database design.
Describe the key features of Agile
development
Agile development is a philosophy and set of guidelines for developing
information systems in an unknown, rapidly changing environment.
The manifesto for agile software development identifies 4 basic values:
 Responding to change over following a plan
 Individuals and interactions over processes and tools
 Working software over comprehensive documentation.
 Customer collaboration over contract negotiation.

There are 11 agile modelling principles:

 Develop software as your primary goal
 Enable the next effort as your secondary goal
 Minimize your modelling activity – few and simple
 Embrace change and change incrementally
 Model with purpose
 Build multiple models
 Focus on content rather than representation
 Learn from each other with open communication
 Know your models and how to use them
 Adapt to specific project needs
 Maximize stakeholder ROI
Read pages 306 and 307 for a further discussion of all modelling principles.
 Understand and describe the key features
of the Unified Process, Extreme
Programming, and Scrum Agile system
development methodologies