1.2 + 1.3 interaction + iteration/ inputs + outputs of each phase of the…
1.2 + 1.3 interaction + iteration/ inputs + outputs of each phase of the project life cycle
- Repetition of a phase when amendments are made.
- how phase are linked.
Evaluation + initiation stage does not interact because after the evaluation phase the project has been completed.
+ there are no stages after the Evaluation phase.
with planning and
Planning + Evaluation
Initiation + Execution
iteration with initiation.
Iteration with Execution
Carried out during the creation and after completed.
Results are checked + recorded to ensure that every part of the product has been tested.
Results of retests are recorded.
The product is created + tested.
Bugs + errors found are corrected.
Retests are carried out to ensure that the product as intended and meets the user requirements
Release deliverable product
Final review report
Release of deliverable product
Product is fully checks + against the constraints lists + defined requirements
Product is installed on to the client's computer
Checked again to see if it work as intended.
When the project team is happy, it is then released to the client.
created before the product is released to the client.
type of user documentation depends on the type of the product.
. User guide showing how to use a product.
An installation guide, in the future if the products wants to be reinstalled.
Test plan showing all the testing carried out.
Security Details, which show how the built in security + e.g. how to set up new users with access details.
Answers the questions during the initiation stage.
Include different proposed solutions for the client.
Considers the client-defined constraints and requirements that have been set.
Depend on type of product being created and assets being used.
May need to revisit the project to make sure if the legislation has not been updated.
Gather user requirements and constraints
Define what the client wants the product to achieve.
can be created between the client and the project manager.
Can be general or specific
Are given to the project manager by the client.
Are restrictions must be adhered to during the creation of the project.
Are compromised of four constraints - timescale,budget,hardware,software.
Created by the project manager.
Forms the basis for completion of the project.
Include tasks, resources needed, milestones,contingency time, workflow and end date.
To check if the user requirements are carried out.
could be produced based on the type of product to be used on the execution phase
Created from the client-defined constraints provided in the initiation phase.
Provide detail information about each constraints.
Constantly referred during the project life cycle.
Referred during the phase review to make sure if the constraints have been met.
Initiation Phase Review Tasks
Consider the feasibility Report
Decide if the project is to carry on.
If omissions in information is found, the stage is repeated.
Planning Phase Review Tasks
consider project plan, test plan + constraint list.
Check for omissions in the document.
If omissions + issues are resolved, or return to initiation stage.
Project plan,test plan, + constraint list checked + agreed by the client
Execution Phase Review Tasks
Consider all aspects of the project.
Measure success against criteria/objectives.
Review deviations from original plan.
Evaluate the effect of process + resources on delivering solutions.(software selected,tools,techniques used,compatibility of software + systems).
Asses the maintainability of the product(development of system in the future, emerging technologies, adapting to a changed environment.)
Evaluation Phase Review Tasks
consider the completed product.
Review product against test results +user requirements + constraint lists.
If omissions + issues resolved or phase repeated to resolve these.
Correct product signed off because the best is released to the client.