Introduction to System
Development
Dr. M. B. Olanisebe
Department of Accounting
Obafemi Awolowo
Ile-Ife, Osun State
Nigeria
Phone: +234 8062942618
ACC 410: Management Information Technology (MIT)
INTRODUCTION
System development refers to the process of
defining, designing, testing, and implementing a new
software application or information system.
It includes all activities from the initial idea or
request for a system through to its deployment,
maintenance, and eventual retirement.
Importance in Organizations
►Aligns information technology with
business goals
►Improves operational efficiency and
effectiveness
►Enhances decision-making through
accurate and timely information
►Provides competitive advantage
►Reduces costs and eliminates redundant
processes
System Development Approaches
System development approaches are the
frameworks and strategies used to plan, design, build,
and deploy information systems.
These methodologies govern how developers,
stakeholders, and project managers navigate the
System Development Life Cycle (SDLC).
There are several methodologies or approaches to
developing information systems. The choice of
approach depends on project size, complexity, risk,
time constraints, and organizational culture.
Predictive Approaches
Also known as traditional approaches, these methods require all requirements to
be clearly defined [Link] project follows a strictly linear and sequential path.
Waterfall: A rigid, step-by-step model where each phase (Analysis, Design, Coding,
Testing, Deployment) must be completed and signed off before the next one
begins.
Best for: Projects with highly predictable outcomes, strict regulatory requirements,
and fixed scopes.
V-Model (Verification and Validation): An extension of the Waterfall model that
explicitly pairs every development phase with a corresponding testing phase.
Best for: Mission-critical systems (e.g., healthcare or aerospace) where zero
defects are mandatory.
Spiral Model: Focuses heavily on risk assessment and iterative development.
Projects pass through four phases (planning, risk analysis, engineering, and
evaluation) in increasingly larger "spirals".
Best for: Large, complex, and high-risk projects.
Adaptive Approaches
Adaptive or evolutionary approaches acknowledge that user
requirements and technology change constantly. They embrace
flexibility and deliver the system in small, manageable pieces.
Agile (e.g., Scrum, Kanban): Breaks the project down into short cycles
called "sprints" (usually 2–4 weeks). Working software is delivered
continuously, and user feedback is integrated at the end of every cycle.
Best for: Startups, dynamic markets, and projects where end-user
requirements evolve rapidly.
Prototyping: Developers build a scaled-down, functional version of the
system to gather user feedback. This prototype is continuously refined
until it becomes the final product.
Best for: User-interface heavy projects and situations where
requirements are unclear.
Rapid Application Development (RAD): Focuses on prototyping and
iterative development with heavy user involvement, prioritizing rapid
delivery over meticulous upfront planning.
Best for: Projects requiring fast time-to-market and heavy
customization.
Structural & Design Methodologies
Alongside project management frameworks, there are
specific methodologies for how the software's architecture
is built:
Object-Oriented (OO): Views the system as a collection of
interacting "objects" that represent real-world entities,
promoting code reuse and modularity.
Structured Systems Analysis and Design (SSAD): A
traditional, top-down approach that focuses on the processes
and data flow within the system.
Choosing the right approach depends heavily on your
project timeline, budget, team size, and the clarity of your
initial requirements.
The System Development Life Cycle
.
There are two general approaches to the SDLC
⚫ Predictive Approach
⚫ 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
The System Development Life Cycle (Cont’n)
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.
Traditional Predictive SDLC (Cont.)
Newer Overlapping Phases Predictive SDLC
More flexibility, but still assumes predictive planning
and sequential phases
Newer Adaptive SDLC Cont.
⚫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