1.1 Phases of the project 1.1 Advantages of the project life cycle
life cycle Initiation: Starting point
Evaluation: The
where questions are ● Provides a structured approach which allows ever
answered. The questions are
product is released Initia
with a user tion
based on if the project is the project to see how it is progressing
feasible or not by looking at
documentation
the requirements and ● Defined inputs and outputs for each phase
which will include
constraints
user guides and Eval ● Roles and responsibilities of each member is clear
installation uatio Plan
n ning each person knows what they are working on
● Resources can be allocated in advance so any issu
Planning: Detailed plans are
Execution: The longest Exec created of the product as well in the beginning rather than during the task
part of the project where it
is made and tested
ution as test plans. The project is ● End of phase reviews are carried out to make sure
broken up into tasks to be
completed in allocated time meeting the success criteria
1.2 The interaction and iteration between the phases 1.3 The inputs and outputs of each phase
Inputs
User requirements, User constraints
Initia Interaction: How Initiation Outputs
tion the phases link Feasibility report, Legislation
together Inputs implications
Planning Outputs
Evalu Plan Iteration: The
ation ning repeating of a phase Project plan, Test plan, Constraints lis
Inputs
Execution
Exec Outputs
Deliverable product, Test results
ution
Inputs
Evaluation Outputs Release of deliverable product, User
Final evaluation report
, Initiation
Planning
User requirements- They define what the client wants the product to achieve
Project plan- This includes a breakdown of all tasks, the time a
User constraints- These restrictions include Timescale, Budget, Hardware,
allocated to each other. It will also include milestones and e
Software
project as well as how the tasks link together where some t
Feasibility report- It includes the answer to all the questions asked in the
concurrent or dependent
initiation phase which could include solutions. It will also consider if the
Test plan- This is mainly concerned with testing the user requi
requirements and constraints are realistic and if the project should go
sure they have been met but could also be the tested of a p
ahead
Constraints list- It provides detailed information about each o
Legislation implications- Depending on the type of product being created,
so that it can be met
legislation and regulations will need to be considered
Phase review- This considers the completed plan,test plan and
Phase review- It considered the feasibility report where the project manager
It will make sure nothing is left out and if found the plannin
and the client decide whether or not to carry on the project
have to be done again.
Evaluation
Execution Release of deliverable product- When the product has been c
Deliverable product- The product is created and if any bugs or errors are be fully checked against the constraints list and the require
found then they are corrected delivering to the client
Test results- The product is tested and results of every part is recorded. This User documentation- This make take from of a user guide sho
will be used from the test plan in the planning phase the product, an installation guide which could be used in th
Phase review- It will consider everything in the execution phase where the product needs to be reinstalled. Test plans showing the res
project manager will have monitored the time to make sure it fits with its and security detail which will show the built in security and
deadline. Any issues that have been identified will have been resolved Final evaluation report- It considers all aspects of the project
the phases. The final review will need to measure against t
criteria, review deviations from original plans, evaluate the
processes and resources on delivering solutions and assess
maintainability
life cycle Initiation: Starting point
Evaluation: The
where questions are ● Provides a structured approach which allows ever
answered. The questions are
product is released Initia
with a user tion
based on if the project is the project to see how it is progressing
feasible or not by looking at
documentation
the requirements and ● Defined inputs and outputs for each phase
which will include
constraints
user guides and Eval ● Roles and responsibilities of each member is clear
installation uatio Plan
n ning each person knows what they are working on
● Resources can be allocated in advance so any issu
Planning: Detailed plans are
Execution: The longest Exec created of the product as well in the beginning rather than during the task
part of the project where it
is made and tested
ution as test plans. The project is ● End of phase reviews are carried out to make sure
broken up into tasks to be
completed in allocated time meeting the success criteria
1.2 The interaction and iteration between the phases 1.3 The inputs and outputs of each phase
Inputs
User requirements, User constraints
Initia Interaction: How Initiation Outputs
tion the phases link Feasibility report, Legislation
together Inputs implications
Planning Outputs
Evalu Plan Iteration: The
ation ning repeating of a phase Project plan, Test plan, Constraints lis
Inputs
Execution
Exec Outputs
Deliverable product, Test results
ution
Inputs
Evaluation Outputs Release of deliverable product, User
Final evaluation report
, Initiation
Planning
User requirements- They define what the client wants the product to achieve
Project plan- This includes a breakdown of all tasks, the time a
User constraints- These restrictions include Timescale, Budget, Hardware,
allocated to each other. It will also include milestones and e
Software
project as well as how the tasks link together where some t
Feasibility report- It includes the answer to all the questions asked in the
concurrent or dependent
initiation phase which could include solutions. It will also consider if the
Test plan- This is mainly concerned with testing the user requi
requirements and constraints are realistic and if the project should go
sure they have been met but could also be the tested of a p
ahead
Constraints list- It provides detailed information about each o
Legislation implications- Depending on the type of product being created,
so that it can be met
legislation and regulations will need to be considered
Phase review- This considers the completed plan,test plan and
Phase review- It considered the feasibility report where the project manager
It will make sure nothing is left out and if found the plannin
and the client decide whether or not to carry on the project
have to be done again.
Evaluation
Execution Release of deliverable product- When the product has been c
Deliverable product- The product is created and if any bugs or errors are be fully checked against the constraints list and the require
found then they are corrected delivering to the client
Test results- The product is tested and results of every part is recorded. This User documentation- This make take from of a user guide sho
will be used from the test plan in the planning phase the product, an installation guide which could be used in th
Phase review- It will consider everything in the execution phase where the product needs to be reinstalled. Test plans showing the res
project manager will have monitored the time to make sure it fits with its and security detail which will show the built in security and
deadline. Any issues that have been identified will have been resolved Final evaluation report- It considers all aspects of the project
the phases. The final review will need to measure against t
criteria, review deviations from original plans, evaluate the
processes and resources on delivering solutions and assess
maintainability
