System Boundary Document | Free Template | Data Dictionary & Use Case Templates | Free Templates, Checklists, Forms for Microsoft Office

System Boundary Document Template

July 9th, 2009 · No Comments · F R E E

System boundary document template word 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.

Use this template to determine:

Business Needs – Ensure that requirements satisfy the business need. Have you highlighted areas that are outside of scope due to budgetary or resource restrictions?
Feasibility – Can requirements be met? Do you have the resources, experience, and budget to deliver this project?
Costs – Are costs realistic? Have we factored in all costs for human resources, consultants, software, training etc?
Schedule – Is the schedule realistic? Are we over-optimistic on the delivery date? Have internal or political issues determined the end date? If so, how can we mitigate against this?

Download Now for only $7.99 – Buy Here!

System Boundary Screenshots

Chapter 1, Introduction

System Mission, Objectives and Goals

Chapter 3, Requirements Statement

Chapter 6, Feasibility Analysis

Chapter 9, Project Cost, Schedule, and Performance

Free Excel Performance Measures Template

Performance Measures

Free Visio Process Flow Template

1 Introduction
1.1 Purpose
1.2 Background

2 Mission
2.1 System Mission
2.2 Objectives
2.3 Goals
2.4 Critical Success Factors
2.5 Performance Measures

3 Requirements Statement
3.1 Existing Methods and Procedures
3.2 Required Capabilities
3.2.1 User Requirements
3.2.2 User Information Needs
3.2.3 Sensitive Information
3.2.4 Network Requirements
3.2.5 Interface Requirements
3.2.6 Impact on Technical Framework

4 Business Assumptions & Constraints
4.1 Organizational Structure
4.2 Impact of Automation
4.3 Legal
4.4 Security
4.5 Facility

5 System Assumptions and Constraints
5.1 Impact Analysis
5.2 Acceptable Alternatives
5.3 System Upgrade

6 Feasibility Analysis
6.1 Evaluation Criteria
6.2 Alternative Descriptions
6.3 Alternative Model
6.4 Description
6.5 Alternative Evaluation
6.6 Recommendation

7 Program Management Assumptions & Constraints
7.1 Organizational Support
7.2 Budget
7.3 Schedule
7.4 Facility
7.5 Acquisition
7.6 Other Projects

8 Cost-Benefit Analysis
8.1 Cost Analysis
8.1.1 Cost Categories
8.1.2 Project Cost Analysis
8.2 Benefit Analysis
8.2.1 Key Benefits
8.2.2 Tangible Benefits
8.2.3 Summary of Tangible Benefits
8.2.4 Intangible Benefits
8.2.5 Summary of Intangible Benefits
8.3 Comparison of Costs and Benefits for Project
8.3.1 Comparison of Tangible Benefits
8.3.2 Comparison of Intangible Benefits
8.3.3 Conclusion
8.4 Sensitivity Analysis
8.5 Results

9 Project Cost, Schedule, & Performance
9.1 Schedule
9.2 Budget
9.3 Lifecycle Cost Estimate
9.4 Performance
9.5 Risks
9.6 Return on Investment

10 References