Technical Constraints

Description:
Defines technological constraints that the solution will have to adhere to. For example, while both CORBA and MQ Series are available in the computing environment, MQ series should be used for the solution.
Risk & Impact:
Since this task implies requirements, inadequate specification could lead to missed requirements, resulting in a solution that does not meet the customer needs.
Inputs:
Upstream Tasks:
Downstream Tasks:
Questions Asked:
1.Are all tools, platforms, operating systems, etc., currently in the environment candidates for use on this project?
2.Are new tools, platforms, operating systems, etc., permitted for use on this project?
Deliverables:
Technical Constraint Document A list of constraints with narrative explanation