0% found this document useful (0 votes)
9 views10 pages

Thesis Notes

notes for thesis

Uploaded by

Arabella Castidy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views10 pages

Thesis Notes

notes for thesis

Uploaded by

Arabella Castidy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

THS 2 NOTES 1st Semester 2024-2025

Thesis 2

CHAPTER 4 SYSTEM DEVELOPMENT


phases
DEVELOPMENT PHASE of system development
System Development Lifecycle Method 7 PHASES OF SYSTEM DEVELOPMENT
(SDLC)
• cost-effective and time efficient process 1. Planning
that development teams use to design and • Planning helps systems engineers and
build high-quality software. developers identify whether a new system
can help a business achieve its strategic
• a series of stages encompassing the
objectives.
creation and development of a new
• preliminary plan sometimes called a
computer-based system.
feasibility study allow development
• covers the full process of creation, from teams to outline the resources they need
ideation through development, release to build new infrastructure or upgrade
and maintenance. existing services.
• Using the system development life cycle
provides a structure for the development 2. Systems analysis
process and offers guidance to staff • less theoretical and focuses more on practical
working on the project by clarifying application.
expectations at each phase. • This allows you to perform a functional
assessment and finalize the client's or users'
NOTE: needs for the system in development.
❖ The goal of SDLC is to minimize project • This confirms that plans satisfy all mandatory
objectives before progressing to future steps
risks through forward planning so that
software meets customer expectations
3. Systems design
during production and beyond.
• complete the detailed planning of the system
you're developing.
How the system development life cycle
• includes identifying any key components and
works defining the structure of the system.
• an important step because it allows you to
• The system development life cycle works create the infrastructure for your development
like an assembly line, where users project.
complete each process phase before • High-quality work during this phase provides
moving on to the next. a foundation for further development and
• helps users produce high-quality systems creates an opportunity for success
that match client expectations, meet
deadlines and fulfill customer 4. Development
requirements. • begin the functional creation of the new
• allow developers and engineers to focus system.
on one phase at a time and simplify the • provides the first opportunity for practical
development process. assessment of the system as it develops
• can choose from various software • allows for the identification of any
development life cycle (SDLC) potential flaws in the development or the
planning process.
methodologies or models, such as
Waterfall, Agile, Spiral or Incremental, to • The development phase also includes
troubleshooting solutions for any potential
help them develop systems throughout the
errors discovered.
life cycle phases.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

5. Systems testing and integration What are the stages of SDLC


• Testing during development and before methodologies?
formal release is an important step for
maintaining the quality of a project. → Planning
• allows you to perform quality control by
involves establishing functionality
testing your components against
requirements, determining what the
expectations and assessing their ability to
application does and identifying the types of
integrate with any software related to
data necessary to create the software.
your system development
• A systems testing and integration phase is → Analysis
often an iterative process.
software developers and project managers
6. Implementation decide whether they can achieve the
• This may include a commercial release for requirements.
a product manufactured for outside sale
or implementation within an organization After analyzing these requirements,
for internally developed systems. developers create a requirement
• internal or closed beta testing: in which specification document.
you grant access to a smaller population → Design
than your ultimate goal.
• provides the opportunity to learn through involves designing the requirements at the
practical assessment by those who use the planning stage.
system in their personal or professional
lives. developers create the system design they use
to plan the software, hardware and system
• effective quality control phase can help to architecture.
minimize the potential for errors during
this phase because final implementation → Development
commonly requires a significant
expansion of the number of users. This is when the software coding happens.
It involves dividing the tasks into modules and
7. Operation and maintenance units and coding according to the design and
• occurs during the effective use of the requirement documentation.
product by end users.
• Providing updates and adjustments to the → Testing
software system after release allows you developers troubleshoot and correct any
to alter it to better match the needs of parts of the software
users.
• You may also respond to any errors that developers deliver the software to the client
occur and alter the system to account for and deploy it on their systems.
any other issues
Developers then conduct beta testing to
identify, report and fix any errors before
doing a final installment of the software
→ Maintenance
This step is continuous as teams monitor and
handle any necessary updates as the
customer uses the new software.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

8 POPULAR SDLC METHODOLOGIES

1. AGILE with Agile development methodology:


• offers a rapid process and flexibility that • each project is broken up into several
makes it one of the most popular ‘Iterations’.
methodologies.
• software development team completes • All Iterations should be of the same
work in short periods, like a few weeks. time duration (between 2 to 8weeks).
• uses what developers call fast failure to
revise and test as they go through new • At the end of each iteration, a
iterations of the software. working product should be delivered.
• uses the Scrum framework, which
requires teams to develop hypotheses • In simple terms, the project will be
about how they think they can do the job, broken up into 10 releases (assuming
implement their method, assess the each iteration is set to last 4 weeks)
process and adjust it based on feedback.
• Rather than spending 1.5 months on
EXAMPLE:
requirements gathering, the team will
➢ Adobe is working on project to come up decide the basic core features that
with a competing product for Microsoft are required in the product and
Word, that provides all the features decide which of these features can
provided by Microsoft Word and any be developed in the first iteration
other features requested by the
marketing team. The final product needs • Any remaining features that cannot
to be ready in 10 months of time. Let us be delivered in the first iteration will
see how this project is executed in be taken up in the next iteration or
traditional and Agile methodologies. subsequent iterations, based on
priority.
The image below shows how these activities
align with the project schedule in traditional
software development: • At the end of the first iterations, the
team will deliver a working software
with the features that were finalized
for that iteration.

• There will be 10 iterations and at the


end of each iteration the customer is
delivered a working software that is
incrementally enhanced and
updated with the features that were
shortlisted for that iteration.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

The iteration cycle of an Agile project is 2. WATERFALL


shown in the image below:
• One of the first SDLC methods to
become popular.
• follows a strict approach to planning
each part of a project before its
inception.
• the team settles each requirement
before any other design stages begin.
• Waterfall approach is straightforward
because developers build each
successive step in the process upon the
previous.
• developers identify the problems and
resolve them immediately in the design
phase.

EXAMPLE:

The project used the Waterfall Methodology


Model. It followed a linear structure starting from
preliminary investigation, requirement analysis,
design phase, implementation and maintenance.

Each phase of this project had sub phases


which produce expected output results. Requirements
were fixed at initial stages before proceeding with
development plans.

In the figure below, the first phase of the


project was the requirements phase. The researchers
were obliged to investigate the necessary information
NOTE: from the hospital in order to determine the exact
needs of the project implementation. The researchers
• This approach allows the customer to conducted interviews and investigations with the
interact and work with functioning hospital personnel to gather data and requirements
software at the end of each iteration for the project. The researchers were provided with
and provide feedback on it. necessary documents such as sample of printed forms
and receipts of the hospital. These sample forms were
used by the researchers to design the system in the
In the Agile approach, software is developed next stage.
and released incrementally in the iterations.

An example of how software may evolve


through iterations is shown in the image below:
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

EXAMPLE (cont.): Iterative Model - Design


The researchers proceeded to the second
stage which was the design phase after conducting Iterative process starts with a simple
necessary investigations. Since the data being implementation of a subset of the software
gathered from the previous stage was fixed and requirements and iteratively enhances the evolving
organized, the researchers planned the design of the versions until the full system is implemented. At each
project based on the gathered requirements and data. iteration, design modifications are made and new
At this point also, the researchers had started the functional capabilities are added. The basic idea
coding and building of the system. They also created behind this method is to develop a system through
the diagrams and flowcharts for the system modules. repeated cycles (iterative) and in smaller portions at
The administrator, receptionist, head nurse, a time (incremental).
pharmacist and billing officer modules were designed
and the workflows were visualized through flow The following illustration is a representation of the
charts. Iterative and Incremental model:

The third phase of the model was the


implementation. After the researchers completed the
system codes, they proceeded to the deployment of
the entire project. The researchers executed the system
in actual working computers to test whether it would
run or not. After implementing the system, the
researchers tested it on each module in the fourth
phase, called the verification process.

In the verification phase, each module was


tested and the researchers encountered that there
were certain modules which had errors, and the
researchers resulted to fix the errors. The researchers
conducted a test plan which allowed the users to test
the existing modules if it’s working or not. The
researchers allowed the user to use the system in order
to determine if all the functions were running, and that Iterative and Incremental development is a
the objectives of the project were met. The researchers combination of both iterative design or iterative
completed the final phase, which was the maintenance method and incremental build model for
phase. development. "During software development, more
In this phase, the researchers made necessary than one iteration of the software development cycle
changes in the system codes that were missed out may be in progress at the same time." This process
during the testing stage. Any errors and bugs may be described as an "evolutionary acquisition" or
encountered in the verification phase were also fixed "incremental build" approach."
at this phase.
The key to a successful use of an iterative software
3. ITERATIVE development lifecycle is rigorous validation of
requirements, and verification & testing of each
• software teams implement requirements version of the software against those requirements
without extensive planning. within each cycle of the model. As the software
evolves through successive cycles, tests must be
• each successive development cycle and repeated and extended to verify each version of the
testing produces a better version of the software.
product until you reach the final result
• put design first because developers
spend less time in planning and analysis.
• iterative process starts with a simple
implementation of a small set of the
software requirements and iteratively
enhances the evolving versions until the
complete system is implemented and
ready to be deployed.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

4. LEAN Spiral Model goes through the planning,


design, build and test phases over and over
• involves using the ideas of manufacturing with gradual improvements in each phase.
in cutting waste and increasing efficiency
to benefit an organization.
• aims to reduce cost and increase
productivity to deliver a product as
quickly and effectively as possible
• developers work on one task at a time to
eliminate multitasking and focus on
creating the best system development
within a single stage.

The Lean methodology follows these seven


principles:

• Refining information
Spiral model consists of four different phases.
• Eliminating waste These phases are:
• Making decisions as late as possible 1. Planning
2. Risk Analysis
• Delivering a product as quickly as possible
3. Engineering & Execution
• Keeping the integrity of a concept 4. Evaluation

• Empowering a team 6. DevOps


• Seeing the whole product
• combines the work of development teams
with operations to increase the amount of
5. SPIRAL feedback, quick revisions and automation
in a project.
• was described by Barry Boehm in 1986. • can lead to more innovation in the
• a combination of iterative development development of products because both
method and sequential improvement teams work together to create new
model. systems.
• a risk driven process model which means • Developers consider the DevOps method
the overall project’s success depends on as a cultural shift in organizations because
the risk analysis phase. it changes the team infrastructure.
• spiral model is one of the oldest types of • method also often increases the reliability
software development lifecycle (SDLC). of a product because experts from both
• the development process is carried out, operations and development combine
incrementally and iteratively in a their skills to deploy a product.
systematic and speedy way.

The following diagram will help you to know


the steps performed in a simpler term in Spiral
Model.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

What is DevOps? The benefits of DevOps

- a software development → Environment Stabilization


methodology that combines software Enforces consistency, increase up-time
development (Dev) with information
technology operations (Ops) → Shorter Development Cycle
participating together in the entire Manage requirements and code-repository
service lifecycle, from design through
the development process to → Increased Release Velocity
production support. Continuous build, push-button deployments

→ Reduced Defects
Regiment processes, automated testing

→ Process Metrics
Track both time at each stage, and the
errors and exceptions

The goals of DevOps

• Fast Development Methodologies

• Fast Quality Assurance Methodologies

The steps of DevOps


• Fast Deployment Methodologies
Plan
task management, schedules
• Faster time to market Code
code development and code review, source
code management tools, code merging
• Iteration & Continuous Feedback (strong
and continuous communication between Build
stakeholders — the end users and continuous integration tools, version control
customers, product owners, development, tools, build status
quality assurance, and
production engineers Test
continuous testing tools that provide
feedback on business risks, determine
performance
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

Package 8. PROTOTYPING
artifact repository, application pre-
deployment staging • effective for testing a new concept or
creating a system for emerging
Release technology.
change management, release approvals, • developers focus most of their efforts on
release automation creating a model and outlining the overall
plans for a system.
Operate • allows customers to see the capabilities of
infrastructure installation, infrastructure a design before implementing any coding
changes (scalability), infrastructure or testing.
configuration and management,
infrastructure as code tools, capacity
planning, capacity & resource management,
security check, service deployment, high
availability (HA), data recovery,
log/backup management, database
management
Monitor
service performance monitoring, log
monitoring, end user experience, incident
management

7. V-MODEL
• some call the Verification and Validation
model
• focuses on testing at every step of
development
• This method also compartmentalizes each
step, which often makes it easier to control
the development process.
• connects the testing of a product to its
corresponding development phase,
meaning it essentially makes the
development process follow the coding
phase instead of following the traditional
order.
• Similar to the waterfall model, the V-
Shaped life cycle follows a sequential
process execution. Each phase’s
completion is necessary before moving to
the next phase
• The V-Model is a software development
approach. It plans testing alongside the
matching development phase in parallel.
THS 2 NOTES 1st Semester 2024-2025
Thesis 2

DIAGRAMS

iteration cycle of an Agile project

Agile DevOps Process


THS 2 NOTES 1st Semester 2024-2025
Thesis 2

Diagram of V-Model

Diagram of Prototyping

You might also like