IT 118 - SIA - Module 2

Bicol University College of Science
CS/IT Department IT 118 - System Integration and Architecture

Legazpi City Module 2: Project Phase and Life Cycle
Module 2
Project Phase and Life Cycles
Project Phase
A project phase is a collection of activities within a project. Each project phase is goal-oriented and
ends at a milestone. It concludes when one or all objectives of the project are achieved. A project could
be divided into any number of phases and each phase can be divided into sub-phases. Project phases
are required when the work to be performed is unique to a piece of the project and are typically linked
to the development of a particular major deliverable.
Types of Phase-to-Phase Relationships
In cases where projects have two or more phases, the phases are considered part of a sequential
process. However, in some situations, the project might benefit from overlapping or concurrent phases.
The phase-to-phase relationships can be of three types:
1. Sequential Relationship
In a sequential relationship, a new phase starts only when the preceding phase is complete. In the
figure given below, you can see an example of a project with three entirely sequential phases. The
step-by-step nature of this approach decreases uncertainty, but may also remove options for reducing
the overall schedule.
2. Overlapping Relationship
In an overlapping relationship, as the name suggests, the next phase starts before the completion of
the previous one. Overlapping phases sometimes need additional resources because work has to be
done in parallel. It may increase risk or could lead to rework if a succeeding phase progresses before
correct information is gathered from the previous phase.
3. Iterative Relationship
This kind of relationship is a cross between sequential and overlapping relationships. This is typically
used for Agile software development. As opposed to the overlapping relationship, this has only 1 team
working on both phases. What that basically means is for one phase the project team could be working
on Initiation/Planning while for another phase they could be working on Execution/Closure.
Project Life Cycle

The project life cycle are the steps required for project managers to successfully manage a project from
start to finish. It is used to gain better control over a large project and a clearer focus on the deliverables
Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Page 1 of 14
required to complete it. It is a five-step framework planned to assist project managers in completing
projects successfully.
This is done through the splitting up of the project into several phases, each of which can be considered
a sort of mini-project in itself which involve all five process groups. The handoff or transfer from one
phase to another is done at a stage or phase.
Phases of Project Life Cycle
1. Project Initiation: Defining What Needs To Be Done
Project initiation is the first project life cycle phase, where the project starts. It provides an overview of
the project, along with the strategies required to attain desired results. It is the phase where the
feasibility and business value of the project are determined. The goal of the initiation phase is to take
the (sometimes) loose brief of a project and understand what the project needs to do and achieve in
order to be successful.
That usually necessitates identifying the project stakeholders and making sure they all share the same
perception of what the project is and the business case—the problem that the project is trying to solve.
Project manager will need to conduct adequate research to determine the goals of the project, and then
propose a solution to achieve them.
The project manager kicks off a meeting to understand the client and stakeholders’ requirements, goals,
and objectives. It is essential to go into minute details to have a better understanding of the project.
Upon making a final decision to proceed, the project can move on to the next step: that is, assembling
a project team. One of the key steps in project initiation is creating a project charter. The Project Charter
is considered to be the most important document of any project as it comprises:
 Business vision and mission

 Project goals and benefits
 List of stakeholders
 Scope of the Project
 Project deliverables
 Risks associated with the project
 Project budget and resources
Key Steps during Project Initiation
a. Undertake a Feasibility Study
In the initial stage, it is essential to understand the feasibility of the project. See if the project is viable
from the economic, legal, operational, and technical aspects. Identifying problems will help you analyze
whether you can solve issues with appropriate solutions.
b. Identify the Project Scope

Page 2 of 14
Identifying the project scope involves defining the length, breadth, and depth of the project. On the
other hand, it’s equally essential to outline functions, deadlines, tasks, features, and services.
c. Identify the Project Deliverable
Upon identifying the project scope, the very next step is to outline the project deliverables. The project
deliverables include defining the product or services needed.
d. Identification of Project Stakeholders
A thorough identification of project stakeholders is essential. It is better to have meetings with team
members and experts to identify project stakeholders. Documentation of relevant information on
stakeholders and their impact on the successful completion of the project is required.
e. Develop a Business Case
Before developing a business case, check whether the essential pillars of the project such as feasibility,
scope, and identification of stakeholders are in place. The very next step is to come up with a full-
fledged business case.
2. Project Planning: Defining How To Do What Needs To Be Done
After receiving approval to proceed in the initiation phase, you can begin project planning. This is arguably the
most critical project phase in the life cycle. Planning is where you define all the work to be done and create the
roadmap that you follow for the remainder of the project. This is when you figure out how you’re going to perform
the project and answer these questions:
 What exactly are we going to do?

 How are we going to do it?
 When are we going to do it?
 How will we know when we’re done?
The planning phase frames a set of plans which help to guide the team through the implementation phase and
closing phase. The program created at this point will surely help you to manage cost, quality, risk, changes, and
time.
The project plan developed should include all the essential details related to the project goals and objectives and
should also detail how to achieve them. It is the most complex phase in which project managers take care of
operational requirements, design limitations, and functional requirements.
The project planning phase includes the following components:
a. Creating a Project Plan
A project plan is a blueprint of the entire project. A well-designed project plan should determine the list of
activities, the time frame, dependencies, constraints involved, and potential risks. It assists the project manager
to streamline operations to meet the end objective and track progress by taking appropriate decisions at the right
time.

Page 3 of 14
b. Creating a Resource Plan
The resource plan provides information about various resource levels required to accomplish a project. A well-
documented plan specifies the labor and materials to complete a project. Resources used should have relevant
Project Management expertise. Experience in the concerned domain is a priority.
c. Budget Estimation
Framing a financial plan helps you to set the budget and deliver project deliverables without exceeding it. The
final budget plan lists expenses on material, labor, and equipment. Creating a budget plan will help the team and
the project managers to monitor and control the costs throughout the Project Management life cycle.
d. Gathering Resources
Gathering resources is an essential part of project planning as it helps to monitor the quality level of the project.
It is not enough to assemble a well-balanced team from internal and external resources. Resources like
equipment, money, software solutions, and the workplace should be given to complete the assigned tasks.
e. Anticipating Risks and Potential Quality Roadblocks
The risk plan will help you identify risks and mitigate them. It will comprise all the potential risks, the order of
severity, and preventive actions to track it. Once threats are under control, it is possible to deliver the project on
time adhering to quality.
3. Project Execution: Making A Project Happen
Project execution is the phase where project-related processes are implemented, tasks are assigned, and
resources are allocated. The method also involves building deliverables and satisfying customer requirements.
Project managers or team leaders accomplish the task through resource allocation and by keeping the team
members focused.
The team involved will start creating project deliverables and seek to achieve project goals and objectives as
outlined in the project plan. This phase determines whether your project will succeed or not. The success of the
project mainly depends on the project execution phase. The final project, deliverable also takes shape during
the project.
4. Project Monitoring & Controlling: Keeping A Project On Track
The project monitoring and control phase is all about measuring the performance of the project and tracking
progress. It is implemented during the execution phase. The main goal of this phase is to check whether
everything aligns with the Project Management plan, especially concerning financial parameters and timelines.
It is the responsibility of the project manager to make necessary adjustments related to resource allocation and
ensure that everything is on track. To aid this, a project manager may conduct review meetings and get regular
performance reports.

Page 4 of 14
Monitoring project activity after the project execution phase will allow the project manager to take corrective
actions. Meanwhile, considering the quality of work will also help to make the necessary improvements. Keeping
an eye on the budget will help to avoid unnecessary expenses resources.
Key For Project Monitoring And Controlling:
 Cost & time management: Review timesheets and expenses to record, control, and track against the
project’s budget, timeline, and tasks
 Quality management: Reviewing deliverables and ensuring they meet the defined acceptance criteria
 Risk management: Monitor, control, manage, and mitigate potential risks and issues
 Acceptance management: Conduct user acceptance testing and create a reviewing system, ensuring
that all deliverables meet the needs of the client
 Change management: When the project doesn’t go to plan, managing the process of acceptable changes
with the client to ensure they’re happy with necessary changes
5. Project Closure: Ending A Project
The project closure phase represents the final phase of the project life cycle, which is also known as the “follow-
up” phase. Around this time, the final product is ready for delivery. Here the main focus of the project manager
and the team should be on product release and product delivery. In this stage, all the activities related to the
project are wrapped up. The closure phase is not necessarily after a successful completion phase alone.
Sometimes a project may have to be closed due to project failure.
Upon project completion and timely delivery to clients, it is the role of the project manager to highlight strengths,
list the takeaways of the project, identify the ambiguities and suggest how they could be rectified for future
projects. Taking time to recognize the strengths and weaknesses will help to handle projects with more
dedication; this, in turn, builds the project manager’s credibility.
Once the product is handed to the customers, the documentation is finalized, the project team is disbanded, and
the project is closed.
Key Steps for Project Closure:
 Project performance analysis: This is an overall look at how well the project was managed, and whether
the initial estimates of costs and benefits were accurate. Were there unforeseen risks? What issues arose
and how well were they dealt with? Has the project plan been changed, and how?
 Team analysis: Did everyone do what they were assigned to do? Were they passionate and motivated
enough? Did they stay thorough and accountable? Was the communication within the project team
healthy and constructive?
 Project closure: Document the tasks needed to bring the project to an official end. This includes closing
supplier agreements, signing off contracts, and handing in all the necessary project documentation.
 Post-implementation review: Write down a formal analysis of successes and failure, resulting lessons
learned, and suggestions for the future. At the end of every successful project, you will learn that room
for improvement always remains.

Page 5 of 14
System Development Life Cycle (SDLC)

The system development life cycle (SDLC) is a conceptual model used in project management that describes
the stages involved in an information system development project, from an initial feasibility study through
maintenance of the completed application. SDLC can apply to technical and non-technical systems. It includes
policies and procedures for developing or altering systems throughout their life cycles.
7 Phases of SDLC
1. Planning
This is the first phase in the systems development process. It identifies whether or not there is the need for a
new system to achieve a business’ strategic objectives. This is a preliminary plan (or a feasibility study) for a
company’s business initiative to acquire the resources to build on an infrastructure to modify or improve a service.
The purpose of this step is to find out the scope of the problem and determine solutions. Resources, costs, time,
benefits and other items should be considered at this stage.
Planning can also include feedback from stakeholders. Stakeholders are anyone who stands to benefit from the
application. Try to get feedback from potential customers, developers, subject matter experts, and sales
representative. Planning plots the course and provisions the team to effectively create the software. It also sets
boundaries to help keep the project from expanding or shifting from its original purpose.
2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their problem or the need for a change. In the
event of a problem, possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s)
of the project. This is where teams consider the functional requirements of the project or solution. It is also where
system analysis takes place—or analyzing the needs of the end users to ensure the new system can meet their
expectations. Systems analysis is vital in determining what a business’ needs are, as well as how they can be
met, who will be responsible for individual pieces of the project, and what sort of timeline should be expected.
3. Systems Design and Prototyping
The third phase describes, in detail, the necessary specifications, features and operations that will satisfy the
functional requirements of the proposed system which will be in place. This is the step for end users to discuss
and determine their specific business information needs for the proposed system. It’s during this phase that they
will consider the essential components (hardware and/or software) structure (networking capabilities),
processing and procedures for the system to accomplish its objectives.
The Design phase models the way a software application will work. Some aspects of the design include:
 Architecture – Specifies programming language, industry practices, overall design, and use of any
templates or boilerplate
 User Interface – Defines the ways customers interact with the software, and how the software responds
to input
 Platforms – Defines the platforms on which the software will run, such as Apple, Android, Windows
version, Linux, or even gaming consoles

Page 6 of 14
 Programming – Not just the programming language, but including methods of solving problems and
performing tasks in the application
 Communications – Defines the methods that the application can communicate with other assets, such
as a central server or other instances of the application
 Security – Defines the measures taken to secure the application, and may include SSL traffic encryption,
password protection, and secure storage of user credentials
Prototyping can be a part of the Design phase. A prototype is like one of the early versions of software in the
Iterative software development model. It demonstrates a basic idea of how the application looks and works. This
“hands-on” design can be shown to stakeholders. Use feedback o improve the application. It’s less expensive to
change the Prototype phase than to rewrite code to make a change in the Development phase.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer, network engineer and/or
database developer are brought on to do the major work on the project. This work includes using a flow chart to
ensure that the process of the system is properly organized. The development phase marks the end of the initial
section of the process and signifies the start of production.
5. Integration and Testing
The fifth phase involves systems integration and system testing (of programs and procedures)—normally carried
out by a Quality Assurance (QA) professional—to determine if the proposed design meets the initial set of
business goals. Testing may be repeated, specifically to check for errors, bugs and interoperability. This testing
will be performed until the end user finds it acceptable. Another part of this phase is verification and validation,
both of which will help ensure the program’s successful completion.
It’s critical to test an application before making it available to users. Much of the testing can be automated, like
security testing. Other testing can only be done in a specific environment – consider creating a simulated
production environment for complex deployments. Testing should ensure that each function works correctly.
Different parts of the application should also be tested to work seamlessly together—performance test, to reduce
any hangs or lags in processing. The testing phase helps reduce the number of bugs and glitches that users
encounter. This leads to a higher user satisfaction and a better usage rate.
6. Implementation and Deployment
The sixth phase is when the majority of the code for the program is written. Additionally, this phase involves the
actual installation of the newly-developed system. This step puts the project into production by moving the data
and components from the old system and placing them in the new system via a direct cutover. While this can be
a risky (and complicated) move, the cutover typically happens during off-peak hours, thus minimizing the risk.
Both system analysts and end-users should now see the realization of the project that has implemented changes.
In the deployment phase, the application is made available to users. Many companies prefer to automate the
deployment phase. This can be as simple as a payment portal and download link on the company website. It
could also be downloading an application on a smartphone.

Page 7 of 14
Deployment can also be complex. Upgrading a company-wide database to a newly-developed application is one
example. Because there are several other systems used by the database, integrating the upgrade can take more
time and effort.
7. Operations and Maintenance
The seventh and final phase involves maintenance and regular required updates. This step is when end users
can fine-tune the system, if they wish, to boost performance, add new capabilities or meet additional user
requirements.
At this point, the development cycle is almost finished. The application is done and being used in the field. In this
phase, users discover bugs that weren’t found during testing. These errors need to be resolved, which can spawn
new development cycles.
In addition to bug fixes, models like Iterative development plan additional features in future releases. For each
new release, a new Development Cycle can be launched.
SDLC Models & Methodologies

Although the system development life cycle is a project management model in the broad sense, here are some
specific models and methodologies can be leveraged to achieve specific results or provide the greater SDLC
with different attributes.
Waterfall Model
The waterfall model is the oldest of all SDLC methodologies. It’s linear and straightforward and requires
development teams to finish one phase of the project completely before moving on to the next. Each stage has
a separate project plan and takes information from the previous stage to avoid similar issues (if encountered).
However, it is vulnerable to early delays and can lead to big problems arising for development teams later down
the road.

Page 8 of 14
Iterative Model
The iterative model focuses on repetition and repeat testing. New versions of a software project are produced at
the end of each phase to catch potential errors and allow developers to constantly improve the end product by
the time it is ready for market. One of the upsides to this model is that developers can create a working version
of the project relatively early in their development life cycle, so implement the changes are often less expensive
DevOps
DevOps is one of the newest SDLC methodologies and is being adopted by many software companies and IT
organizations. As its name suggests, the premise of DevOps is to bring development teams together with
operational teams in order to streamline delivery and support. The advantages of such an approach are that
changes become more fluid, while organizational risk is reduced. Teams must have flexible resources in order
for a DevOps arrangement to succeed. DevOps optimizes development processes from start to end and engages
the organization in continuous development, resulting in faster delivery times.

Page 9 of 14
Spiral Model
Spiral models are flexible compared to other methodologies. Projects pass through four main phases again and
again in a metaphorically spiral motion. It’s advantageous for large projects since development teams can create
very customized products and incorporate any received feedback relatively early in the life cycle.

Page 10 of 14
V-Model
The V-model (which is short for verification and validation) is quite similar to the waterfall model. A testing phase
is incorporated into each development stage to catch potential bugs and defects. It’s incredibly disciplined and
requires a rigorous timeline. But in theory, it illuminates the shortcomings of the main waterfall model by
preventing larger bugs from spiraling out of control.
Agile Model
The agile methodology is the opposite of the waterfall approach. Rather than treating requirements, design, and
testing as large sequential steps, an agile model makes them all ongoing processes that require involvement
from developers, management, and customers.
Work is typically broken into 2-4 week segments known as “sprints,” in which the responsible teams tackle the
major needs of their customers and perform testing as they go. Agile tends to work well in small organizations,
especially startups, where speed and flexibility is essential.
The agile model is relatively well-known, particularly in the software development industry. The agile
methodology prioritizes fast and ongoing release cycles, utilizing small but incremental changes between
releases. This results in more iterations and many more tests compared to other models.
Theoretically, this model helps teams to address small issues as they arise rather than missing them until later,
more complex stages of a project.

Page 11 of 14
Prototyping
In the prototyping methodology, the design team's focus is to produce an early model of the new system,
software, or application. This prototype won’t have full functionality or be thoroughly tested, but it will give external
customers a sense of what’s to come. Then, feedback can be gathered and implemented throughout the rest of
the SDLC phases. The prototyping approach works well for companies in emerging industries or new
technologies.
Advantages & Disadvantages of SDLC

The systems development life cycle allows lowering the complexity usual for developing a proposed system from
scratch. Thus, it is critical to implement SDLC since it helps to convert ideas of projects into functional and
completely operational structures. Apart from covering various technical aspects regarding system development,
SDLC is efficient for process development, change management, or user experience. Another great advantage
of SDLC is that it promotes planning ahead of time and allows defining costs and staffing decisions, identifying

Page 12 of 14
goals, measuring system performance, and validating points at all phases of the development life cycle to
improve the quality of the end product.
Also, SDLC provides a number of advantages to development teams that implement it correctly.
 Clear Goal Descriptions - Developers clearly know the goals they need to meet and the deliverables
they must achieve by a set timeline, lowering the risk of time and resources being wasted.
 Proper Testing Before Installation - SDLC models implement checks and balances to ensure that all
software is tested before being installed in greater source code.
 Clear Stage Progression - Developers can’t move on to the next age until the prior one is completed
and signed off by a manager.
 Member Flexibility - Since SDLCs have well-structured documents for project goals and methodologies,
team members can leave and be replaced by new members relatively painlessly.
 Perfection Is Achievable - All SDLC stages are meant to feed back into one another. SDLC models can
therefore help projects to iterate and improve upon themselves over and over until essentially perfect.
 No One Member Makes or Breaks the Project - Again, since SDLCs utilize extensive paperwork and
guideline documents, it’s a team effort and losing one even major member will not jeopardize the project
timeline.
At the same time, there can be some critical cons of systems development life cycle:
 Due to assumptions made at the start of the system development project, if different unexpected
circumstances complicate the development process that can lead to more complications in the future.
For instance, if newly applied hardware is not working appropriately, it can increase the costs and the
time required for the development.
 Several approaches are not flexible.
 It may be hard to estimate the overall costs at the start of the project.
 Performing testing at the end of the development process can slow down development teams.
Difference between Project Life Cycle and Product Life Cycle

Product life cycle and project life cycle sound quite similar, but in fact, are very different from one another. A
marketing project can impact a product's life cycle, but otherwise these two concepts are essentially unrelated.
However, understanding what each one is and having some strategies for their use will help you to integrate
both into your business plans with maximum effectiveness.
Project Life Cycle
A project life cycle measures the work that goes into a project from beginning to end. The phases in product life
cycle are initiation, planning, execution, and closure. During initiation, a business case and goals are created,
and resources are assigned. During planning, the team researches solutions to reach the project goals and
creates a plan and timeline to complete the project. Execution involves following each step on the project plan
and adjusting as necessary along the way. Finally, in the closure phase, the project's final details are wrapped
up and deliverable items like final reports are given to the appropriate parties.

Page 13 of 14
Product Life Cycle
The product life cycle represents the amount of revenue a product generates over time, from its inception to the
point where it is discontinued. The five stages of a product's life are development, introduction, growth, maturity,
and decline. In the development stage, the product isn't yet being sold, so there is no revenue. During
introduction, sales are small as people begin to try the product. Sales will increase during the growth phase,
peak during maturity, and eventually decline as the market shifts or better alternatives become available. There
is no set time span for a given stage; the entire cycle may last only months, or a product like the refrigerator may
remain in the maturity phase for decades.
Differences between the Two
A product life cycle is a conceptual map of where a product's sales are and where they may be headed. However,
it has no comment on what to do with the product. If a company believes its product is entering the decline phase,
it will probably create a plan to either rejuvenate the product or cease production, but that is not inherent in the
product life cycle. By contrast, a project life cycle is all about action. A project life cycle maps out the steps
needed to complete a project with specific targeted results.
Remember that the product life cycle concept has limitations. Not every product follows a smooth, predictable
bell curve from introduction to decline. A product may appear to be in the decline phase and enjoy a return to
the maturity phase due to a competitor exiting the market or a successful project rejuvenation strategy. With
regards to project life cycle management, things tend to be much more clearly defined, but watch out for "scope
creep." This is the tendency for projects to continually grow in breadth to the point where they never actually get
completed.
References
https://www.invensislearning.com/blog/5-phases-project-management-lifecycle/
https://www.pmclounge.com/3-types-of-phase-to-phase-relationships/
https://thedigitalprojectmanager.com/project-management-life-cycle/
https://www.techtarget.com/searchsoftwarequality/definition/systems-development-life-cycle
https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-systems/system-development-life-cycle.aspx
https://phoenixnap.com/blog/software-development-life-cycle
https://www.clouddefense.ai/blog/system-development-life-cycle
https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-systems/8-SDLC-models.aspx
https://www.linkedin.com/pulse/difference-between-product-life-cycle-project-mahmoud-omar/

Page 14 of 14

IT 118 - SIA - Module 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IT 118 - SIA - Module 2

Uploaded by

Copyright:

Available Formats

Bicol University College of Science

CS/IT Department IT 118 - System Integration and Architecture

Types of Phase-to-Phase Relationships

Project Life Cycle

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Phases of Project Life Cycle

1. Project Initiation: Defining What Needs To Be Done

 Business vision and mission

Key Steps during Project Initiation

a. Undertake a Feasibility Study

b. Identify the Project Scope

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

c. Identify the Project Deliverable

d. Identification of Project Stakeholders

e. Develop a Business Case

2. Project Planning: Defining How To Do What Needs To Be Done

 What exactly are we going to do?

The project planning phase includes the following components:

a. Creating a Project Plan

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

b. Creating a Resource Plan

e. Anticipating Risks and Potential Quality Roadblocks

3. Project Execution: Making A Project Happen

4. Project Monitoring & Controlling: Keeping A Project On Track

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Key For Project Monitoring And Controlling:

5. Project Closure: Ending A Project

Key Steps for Project Closure:

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

System Development Life Cycle (SDLC)

2. Systems Analysis and Requirements

3. Systems Design and Prototyping

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

5. Integration and Testing

6. Implementation and Deployment

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

7. Operations and Maintenance

SDLC Models & Methodologies

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Advantages & Disadvantages of SDLC

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Difference between Project Life Cycle and Product Life Cycle

Project Life Cycle

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

Product Life Cycle

Differences between the Two

Instructor: Amie Dainne S. Esteves • A.Y. 2023-2024

You might also like