design template 3

25
For instructions on using this template, please see Notes to Author/Template Instructions on pa Reference source not found. Notes on accessibility: This template has been tested and is best a ith !A"# $$.% or higher. For &uestions about using this template, please contact '(# IT )o*ern To re&uest changes to the template, please submit an + ' -rocess 'hange Re&uest 'R . Centers for Medicare & Medicaid Serv CMS eXpedited Life Cycle (XLC) <Project Name / Acronym System !esi"n !oc#ment $ersion X%X MM/!!/ !oc#ment N#m'er <document’s configuration item control number> Contract N#m'er <current contract number of company maintaining document>

Upload: suneel-jagan

Post on 04-Nov-2015

217 views

Category:

Documents


0 download

DESCRIPTION

design exaple

TRANSCRIPT

System Design Document

CMS XLCError! No text of specified style in document.Additional Appendices

For instructions on using this template, please see Notes to Author/Template Instructions on page 21. Notes on accessibility: This template has been tested and is best accessible with JAWS 11.0 or higher. For questions about using this template, please contact CMS IT Governance. To request changes to the template, please submit an XLC Process Change Request (CR).

Centers for Medicare & Medicaid ServicesCMS eXpedited Life Cycle (XLC)

System Design DocumentVersion X.XMM/DD/YYYYDocument Number: Contract Number: CMS XLCError! No text of specified style in document.

System Design DocumentiiError! Use the Home tab to apply Version Number to the text that you want to appear here.MM/DD/YYYYMM/DD/YYYYCMS eXpedited Life Cycle (XLC)IntroductionInstructions: Provide the purpose of the System Design Document. This document should be tailored to fit a particular projects needs.The System Design document documents and tracks the necessary information required to effectively define architecture and system design in order to give the development team guidance on architecture of the system to be developed. Design documents are incrementally and iteratively produced during the system development life cycle, based on the particular circumstances of the IT project and the system development methodology used for developing the system. Its intended audience is the project manager, project team, and development team. Some portions of this document such as the user interface (UI) may on occasion be shared with the client/user, and other stakeholder whose input/approval into the UI is needed.General Overview and Design Guidelines/ApproachThis section describes the principles and strategies to be used as guidelines when designing and implementing the system.General Overview