Methodologies in it projects
NOTE: You can use the navigation to select topics easily. To view the link, ctrl and click on the link.
Methodologies in IT Projects
This provides an overview of various characteristics
found in IT project methodologies. It also includes a
comparison of the listed methodologies, giving a
summary of which one should be utilized for a specific IT
project. Here is a compilation of methodologies
commonly employed in IT projects; Rapid Application
Development (RAD), Waterfall and Agile.
Before we move on, let’s take a quick look at Software
Development Life Cycle (SDLC).
Software Development Life Cycle
(SDLC)
What is SDLC?
This is the cost-effective, high-quality software
design and development approach used by
development teams. SDLC's purpose is to reduce
project risks via proactive planning so that software
satisfies customer expectations during production
and beyond. This approach describes a sequence of
stages for breaking down the software
development process into activities that can be
assigned, completed, and measured.
Benefits of SDLC:
To increase the visibility of development process for
the stakeholders involved.
For the management of software development risk.
Also, to reduce development and production cost.
Efficient estimation, planning, and scheduling.
Systematic software delivery and better customer
satisfaction
Stages of SDLC
, PLANNING- This is the first stage in which
developers define their project's goals and objectives,
which include cost analysis, scheduling, resource
estimation, and allocation. To develop the software
requirement specification document, these duties are
gathered from stakeholders such as clients, internal or
external specialists, and managers.
DEFINING- During this phase, the broad
development plan is refined into specific criteria. This
involves defining the specific program that needs to be
developed. Additionally, the development team may
determine the programming language that will be used
to build the application.
DESIGNING- The user interface is created at this
stage to establish how the programme will work. A DDS
(Design Document Specification) is then prepared, which
is then reviewed and authorised before real work
begins.
Design Document Specification (DDS): This is a
comprehensive document that outlines the design and
architecture of a software system or application, which
provides detailed information about the structure,
components, functionality, and interactions of the
system.
BUILDING- This stage often contains most of the
software development process, which involves writing
the source code, designing visuals, and assembling the
assets into an executable programme. For example, one
team may create the user interface while another
creates the source code. Individual teams may be
assigned to multiple platforms for multiplatform apps.
TESTING- The testing process is critical since it
helps the developer to identify undiscovered issues and
solve any flaws that may appear in the programme.
Internal testing may occur, while a beta version of the
programme may be sent to a small number of users for
public testing.
, DEPLOYMENT- After successfully completing the
testing phase, the program is prepared for deployment.
During this stage, the software is made available to the
public. It can be distributed either through electronic
downloads or in the form of boxed software, which is
typically stored on a CD or DVD.
MAINTENANCE- Users may report further defects or
feature requests after a software programme has been
published. The development team must keep the
programme up to date by correcting issues and
introducing new features. Technical help is frequently
included with commercial software programmes.
NOTE: The reason the above stages are referred to as a
cycle is because these stages are repeated each time a
new major version of the software is released. While the
maintenance stage may encompass minor updates, most
software companies stay in business by regularly
releasing paid updates (version 2, version 3, etc).
Before embarking on a new major version, the
development team must first create a plan (stage 1) and
then continue through the other stages of the SDLC.
Here I will explain the 3 methodologies mention in the
introduction above.
References for SDLC:
What is SDLC? - Software Development Lifecycle Explained - AWS (amazon.com)
SDLC (System Development Lifecycle) Definition (techterms.com)
WATERFALL
The Waterfall method is a standard project management
strategy that was created in the 1950s. Tasks and
phases are accomplished in a linear, sequential order,
and each step of the project must be finished before
moving on to the next.
However, much like a genuine waterfall, this may rapidly
become perilous. Because everything is planned out at
NOTE: You can use the navigation to select topics easily. To view the link, ctrl and click on the link.
Methodologies in IT Projects
This provides an overview of various characteristics
found in IT project methodologies. It also includes a
comparison of the listed methodologies, giving a
summary of which one should be utilized for a specific IT
project. Here is a compilation of methodologies
commonly employed in IT projects; Rapid Application
Development (RAD), Waterfall and Agile.
Before we move on, let’s take a quick look at Software
Development Life Cycle (SDLC).
Software Development Life Cycle
(SDLC)
What is SDLC?
This is the cost-effective, high-quality software
design and development approach used by
development teams. SDLC's purpose is to reduce
project risks via proactive planning so that software
satisfies customer expectations during production
and beyond. This approach describes a sequence of
stages for breaking down the software
development process into activities that can be
assigned, completed, and measured.
Benefits of SDLC:
To increase the visibility of development process for
the stakeholders involved.
For the management of software development risk.
Also, to reduce development and production cost.
Efficient estimation, planning, and scheduling.
Systematic software delivery and better customer
satisfaction
Stages of SDLC
, PLANNING- This is the first stage in which
developers define their project's goals and objectives,
which include cost analysis, scheduling, resource
estimation, and allocation. To develop the software
requirement specification document, these duties are
gathered from stakeholders such as clients, internal or
external specialists, and managers.
DEFINING- During this phase, the broad
development plan is refined into specific criteria. This
involves defining the specific program that needs to be
developed. Additionally, the development team may
determine the programming language that will be used
to build the application.
DESIGNING- The user interface is created at this
stage to establish how the programme will work. A DDS
(Design Document Specification) is then prepared, which
is then reviewed and authorised before real work
begins.
Design Document Specification (DDS): This is a
comprehensive document that outlines the design and
architecture of a software system or application, which
provides detailed information about the structure,
components, functionality, and interactions of the
system.
BUILDING- This stage often contains most of the
software development process, which involves writing
the source code, designing visuals, and assembling the
assets into an executable programme. For example, one
team may create the user interface while another
creates the source code. Individual teams may be
assigned to multiple platforms for multiplatform apps.
TESTING- The testing process is critical since it
helps the developer to identify undiscovered issues and
solve any flaws that may appear in the programme.
Internal testing may occur, while a beta version of the
programme may be sent to a small number of users for
public testing.
, DEPLOYMENT- After successfully completing the
testing phase, the program is prepared for deployment.
During this stage, the software is made available to the
public. It can be distributed either through electronic
downloads or in the form of boxed software, which is
typically stored on a CD or DVD.
MAINTENANCE- Users may report further defects or
feature requests after a software programme has been
published. The development team must keep the
programme up to date by correcting issues and
introducing new features. Technical help is frequently
included with commercial software programmes.
NOTE: The reason the above stages are referred to as a
cycle is because these stages are repeated each time a
new major version of the software is released. While the
maintenance stage may encompass minor updates, most
software companies stay in business by regularly
releasing paid updates (version 2, version 3, etc).
Before embarking on a new major version, the
development team must first create a plan (stage 1) and
then continue through the other stages of the SDLC.
Here I will explain the 3 methodologies mention in the
introduction above.
References for SDLC:
What is SDLC? - Software Development Lifecycle Explained - AWS (amazon.com)
SDLC (System Development Lifecycle) Definition (techterms.com)
WATERFALL
The Waterfall method is a standard project management
strategy that was created in the 1950s. Tasks and
phases are accomplished in a linear, sequential order,
and each step of the project must be finished before
moving on to the next.
However, much like a genuine waterfall, this may rapidly
become perilous. Because everything is planned out at
