PE.V3-Decision
Candidate solutions delivered by the V3.Logical Design are evaluated in terms of the feasibilities investigated in V1.Decision , V2.Decision with in addition specific attention for ICT-related:
- Technical feasibility: Is the solution technically practical? Does our staff or the contractor's staff have the technical expertise to design and build this solution?
- Operational feasibility: Will the solution fulfill the users’ requirements? To what degree? How will the solution change the users’ work environment? How do users feel about such a solution?
- Economic feasibility:Is the solution cost-effective?
- Schedule feasibility: Can the solution be designed and implemented within an acceptable time?
- Risk feasibility: What is the probability of a successful implementation using the technology and approach?
The common project workflow is that V3.Decision concludes to continue the project. In that case additional resources will be needed to perform V3.Physical Design and Integration. Alternative outcomes of V3.Decision is that the project is suspended, that it is merged with another project with a similar scope, or that it is split into sub-projects. In all these case, project data in Repository/Portfolio will be modified accordingly.
Description
| Name1 | name | ||||||||||||
| Domain | |||||||||||||
| Target Outcome | outcome | ||||||||||||
| Social actors and roles | roles | ||||||||||||
| Trigger or preceding interaction | prec | ||||||||||||
| Interfaces and services | services | ||||||||||||
| Inputs and outputs | i/o | ||||||||||||
| Stores and tools |
Regarding Content that is Accurate and Reliable, this will be part of Repository for partnerships (wikiworx). tools |
||||||||||||
| Other characteristics |
|
||||||||||||
| Further reading | ref |
- Questions, answers, comments
- "PE.V3-Decision" among the interactions
- All interactions
- All events
- On the template
Add a New Comment