Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
SYSTEM BOUNDARY DOCUMENT SYSTEM BOUNDARY DOCUMENT Overview The System Boundary Document (SBD) provides guidance on how to establish the boundaries of an information technology (IT) project. It establishes a formal agreement between the Executive Program Sponsor and the Agency CIO on the high-level requirements, costs and schedule for an IT project. It records management decisions to mitigate and to accept a level of risk in the business, technological and project management environments. System development projects frequently experience cost overruns and schedule slippages due to a variety of reasons, including changing requirements and poor resource and schedule estimating. While requirements, schedule and resource changes will occur at times, these changes must be managed and controlled. Documented system boundaries provide a tool for Agency management to use to provide this control. The SBD is applicable to all State IT projects. The Project Manager prepares the SBD for approval by the Agency Program Sponsor, Agency CIO, and the State CIO. The SBD captures the business functions, goals and objectives that the IT project will satisfy. It also captures critical success factors, assumptions and constraints for the IT project as well as performance measures that provide criteria to judge whether the IT satisfied the business goals and objectives. The SBD shall be approved by the Agency Program Sponsor, Agency CIO, and the State CIO. The primary criteria are: Do the requirements meet the business need? Is it technically feasible to meet the requirements? Are the cost and schedule estimates realistic? 1 OVERVIEW The SBD records the essential properties of the envisioned system early in its development and provides guidance on its achievement. 1.1 Purpose Identify the system / project to which this SBD applies and the strategic goals and missions it will support. 1.2 Background The SBD is meant to help senior executives communicate between themselves and reach consensus on what they intend to achieve by pursuing this effort, and why. Provide information in this section on previous decisions or previous system development projects that are relevant to understanding the current project. 2 MISSION The strategic planning information in this section should refer to Agency strategic planning documents, such as the MFR Plans, the IT Master Plan, and the Enterprise Architecture.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
SYSTEM BOUNDARY DOCUMENT 2.1 System Mission Describe the mission for this system. Convey why this system is necessary for your organization. Relate the system mission to the State and/or Agency mission. The system mission will be discussed in terms of how it addresses the opportunities and deficiencies identified in the Concept Proposal. 2.2
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 05/30/2011 for the course SYS 302 taught by Professor Dr.hager during the Spring '11 term at Embry-Riddle FL/AZ.

Page1 / 12


This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online