The System Boundary Document (SBD) is used to establish the boundaries of an information technology (IT) project.
The System Boundary Document captures the goals and objectives that the IT project is intended to satisfy. It also captures critical success factors and performance measures that provide the criteria to judge whether the deliverables have satisfied the business’ goals and objectives.
Tags:Acceptable Alternatives·Acquisition·Alternative Descriptions·Alternative Evaluation·Alternative Model·Benefit Analysis·Conclusion·Cost Analysis·Cost Benefit Analysis·Cost Categories·Critical Success Factors·Evaluation Criteria·Existing Methods and Procedures·F R E E·Feasibility Analysis·Impact Analysis·Impact of Automation·Impact on Technical Framework·Intangible Benefits·Interface Requirements·Key Benefits·Legal·Lifecycle Cost Estimate·Network Requirements·Organizational Structure·Organizational Support·Other Projects·Performance·Performance Measures·Project Cost·Project Cost Analysis·Recommendation·Required Capabilities·Requirements Statement·Results·Return on Investment·Risks·Schedule·Security·Sensitive Information·Sensitivity Analysis·Summary of Intangible Benefits·Summary of Tangible Benefits·System Assumptions and Constraints·System Boundary·System Boundary Document·system boundary template·System Upgrade·Tangible Benefits·User Information Needs·User Requirements
 |
 |
 |
 |
 |
 |
 |
 |
|
You can connect with me at Twitter, BusinessWeek, Delicious, Digg, Disqus, Facebook, Flickr, Google Reader, & LinkedIn, StumbleUpon You can email me here |
© 2006–2007 Free Templates, Checklists, Forms for Microsoft Office — Sitemap — Cutline by Chris Pearson