1.3-inputs and outputs of each phase
invitation: inputs- user requirments, user constraints
outputs- deliverable product, test results and phase review
outputs- release of deliverable product, user documentation and final evaluation report
outputs- Feasibility report, legislation implications and phase review
Planning: inputs- Feasibility repot, legislation implications
outputs- project plan, test plan, constraints list and phase review
Execution: inputs- project plan, test plan, constraints list
Evaluation: inputs- deliverable product, test result
user requirement- what the client wants the project to achieve.
user constraints- restrictions which the project manager must stick to during the project life cycle
feasibility report- Includes all the answers to the questions that were asked during the initiation phases and will consider constraints and requirements provided by the client
legal implications- These need to be considered at the start of the project. Different legislation will apply to different products being created
phase review- a reflection after each stage to decide whether to continue with the project or to go back and make changes
project plan- s a breakdown of tasks, and the time and resources allocated to each one and the link between the different tasks is also define in the project plan
test plan- is created during the planning phase. This will test to ensure all the requirements have been met.
constraints list- is produced by using the user constraints
deliverable product- is the final product which is made during the execution phase. It is tested thoroughly
test result- outcome from the test and it can see where things went good and where they need to improve
Release of deliverable product- product is provided to the client and installed into computer
user documentation- show clients how to install it and how to add security.
final evaluation- measure success against criteria/objectives