ENVISIONING THE SOLUTION

  1. Create a problem statement and get it approved by the stakeholders.

  2. Create a vision/scope document and get it approved by the stakeholders. This document outlines the major function points (features) required by the solution.

  3. Any proposed solution should allow for delivering a quality product on time, on budget, with the agreed-on scope.

  4. Solutions should be verified as being feasible in three areas: business, technological, and resources. If constraints prevent the proposed solution, alter the solution accordingly.

  5. Well-formed teams have the following roles: product management, program management, development, testing, logistics management, and user education.

  6. Risks should be identified, analyzed, planned for, tracked, and controlled.

  7. A risk's probability of occurring, multiplied by some measure of its impact on the project, is a way to more objectively quantify a risk and compare it to others.

  8. A versioned release strategy is one way to mitigate risk.



Analyzing Requirements and Defining. Net Solution Architectures (Exam 70-300)
MCSD Self-Paced Training Kit: Analyzing Requirements and Defining Microsoft .NET Solution Architectures, Exam 70-300: Analyzing Requirements and ... Exam 70-300 (Pro-Certification)
ISBN: 0735618941
EAN: 2147483647
Year: 2006
Pages: 175

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net