CHAPTER 4: SYSTEM DEVELOPMENT Development Phase
System Development Lifecycle Method (SDLC) 4. Development
▪ Cost-effective and time-efficient process for ▪ Begin functional creation of the new system.
designing and building high-quality software.
▪ First opportunity for practical assessment.
▪ Goals: Minimize project risks through forward
▪ Identify potential flaws in development or
planning.
planning.
▪ Series of stages for creating and developing a new
▪ Troubleshoot and develop innovative solutions for
computer-based system.
errors.
▪ Provides structure and guidance by clarifying
5. Systems Testing and Integration
expectations at each phase.
▪ Perform quality control through testing.
How the System Development Life Cycle Works
▪ Assess components against expectations and
▪ Works like an assembly line, completing each
integration with related software.
phase before moving to the next.
▪ Apply updates to improve quality.
▪ Helps produce high-quality systems that
meet client expectations, deadlines, and ▪ Iterative process with multiple rounds of testing
customer requirements. and assessment.
▪ Allows developers and engineers to focus on 6. Implementation
one phase at a time, simplifying the
development process. ▪ Introduce the developed system to end users.
7 PHASES OF SYSTEM DEVELOPMENT ▪ Can be a commercial release or internal
implementation.
1. Planning
▪ May use limited release (e.g., beta testing) for
▪ Identifies if a new system can help achieve smaller user groups.
strategic objectives.
▪ Learn through practical assessment by users.
▪ Preliminary plan (feasibility study) outlines
resources needed. ▪ Effective quality control minimizes errors.
▪ Helps discover potential problems and ▪ Apply debugging and troubleshooting as needed.
solutions. 7. Operation and Maintenance
▪ Includes initial analysis to define objectives ▪ Occurs during the effective use of the product by
and understand the problem. end users.
▪ Brainstorming to discuss potential system ▪ Provide updates and adjustments based on user
options, techniques, and goals. needs.
▪ Respond to errors and alter the system to fix
2. Systems Analysis issues.
▪ Customize the system by adding or adjusting
▪ Focuses on practical application and
features based on user feedback.
functional assessment.
▪ Enhance system effectiveness by addressing
▪ Finalizes client’s or users’ needs for the unforeseen uses and user requests.
system.
▪ Confirms plans meet mandatory
objectives before moving forward.
▪ Uses various tools, including internal
systems and commercial software.
▪ Allows for alterations before design and
development.
3. Systems Design
▪ Completes detailed planning of the system.
▪ Identifies key components and defines system
structure.
▪ Creates infrastructure for the development
project.
▪ Provides a foundation for further development and
success.
CHAPTER 4: SYSTEM DEVELOPMENT Development Phase
Stages of SDLC Methodologies: 8 POPULAR SDLC METHODOLOGIES
▪ PLANNING 1. Agile
o Establishing functionality requirements.
o Determining what the application does.
o Identifying the types of data necessary to
create the software.
▪ ANALYSIS
o Deciding whether the requirements can be ▪ Rapid process and flexibility: Popular due
achieved. to its adaptability.
▪ Collaboration: each project is broken up into
o Creating a requirement specification several ‘Iterations’
document. ▪ Fast failure: Revise and test through new
iterations.
▪ Design
▪ Applicability: Can be used for non-software
o Designing the requirements from the planning projects.
stage. ▪ Scrum framework: Develop hypotheses,
implement methods, assess processes, and
o Creating the system design for software,
adjust based on feedback.
hardware, and system architecture.
▪ Development 2. Waterfall
o Software coding.
o Dividing tasks into modules and units.
▪ Testing
o Troubleshooting; correcting software parts.
▪ Implementation ▪ Strict planning approach: Each part of the
project is planned before inception.
o Delivering the software to the client.
▪ Sequential process: Requirements are
o Conducting beta testing to identify, report, and settled before design stages begin.
fix errors before final installation. ▪ Step-by-step development: Each step
builds upon the previous one.
▪ Maintenance
▪ Immediate problem resolution: Issues are
o Continuously monitoring and handling identified and resolved in the design phase.
necessary updates. ▪ Cost estimation: Easier to estimate costs
due to detailed upfront planning.
3. Iterative
▪ Minimal upfront planning: Requirements
are implemented without extensive planning.
▪ Continuous testing and revision: Items are
tested and revised throughout the project.
▪ Incremental improvement: Each
development cycle and testing produce a
better version.
▪ Design-first approach: Less time spent on
planning and analysis.
▪ Cost-effective: Early mistake correction
reduces costs.
▪ Adaptability: Easier to adapt to client needs.
▪ Iterative enhancement: Starts with a simple
implementation and evolves until the
complete system is ready.
CHAPTER 4: SYSTEM DEVELOPMENT Development Phase
4. Lean 6. DevOps
▪ Manufacturing principles: Focus on cutting
waste and increasing efficiency.
▪ Cost reduction and productivity: Aim to
reduce costs and increase productivity.
▪ Single-task focus: Developers work on one
task at a time to avoid multitasking.
▪ Seven principles:
1. Refining information
2. Eliminating waste
3. Making decisions as late as possible
▪ Integration of Dev and Ops: Combines
4. Delivering a product as quickly as
development and operations teams to
possible
enhance feedback, quick revisions, and
5. Keeping the integrity of a concept
automation.
6. Empowering a team
▪ Innovation and collaboration: Promotes
7. Seeing the whole product
innovation through teamwork and new
system creation.
5. Spiral
▪ Cultural shift: Changes team
infrastructure, fostering a collaborative
culture.
▪ Increased reliability: Combines skills
from both teams to improve product
reliability.
▪ Full lifecycle participation: Involves
both teams from design to production
support.
7. V- Model
▪ Combination model: Combines iterative
development and sequential improvement.
▪ Risk-driven: Success depends on the risk
analysis phase.
▪ Incremental and iterative: Development is
carried out incrementally and iteratively.
▪ Systematic and speedy: Ensures a
systematic and speedy development
process.
▪ Verification and Validation Model:
▪ Oldest SDLC types: One of the oldest
Focuses on testing at every development
software development lifecycle model
step.
▪ Four different phases:
▪ Compartmentalized steps: Easier to
1) Planning control the development process.
▪ Phase connection: Testing is linked to
2) Risk Analysis
each corresponding development phase.
3) Engineering & Execution ▪ Sequential execution: Like the Waterfall
model, each phase must be completed
4) Evaluation
before moving to the next.
8. Prototyping
▪ Concept testing: Effective for testing
new concepts or emerging technologies.
▪ Model creation: Focuses on creating a
model and outlining overall plans.
▪ Customer feedback: Allows customers
to see design capabilities before coding
or testing.
