<<Project Name>>

Conceptual Design


Customer Name




Directions for using template:

Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within <<Begin text here>> with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used.


Some templates have four levels of headings.  They are not indented, but can be differentiated by font type and size:

You may elect to indent sections for readability.







Author Position








Version: 1.0





Ó 2002 Microsoft Corporation. All rights reserved.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.



Revision & Sign-off Sheet

Change Record




Change Reference
































Version Approved
































Document Properties



Document Title

Conceptual Design



Creation Date


Last Updated




Table of Contents

 TOC \o "1-3" \h \z

Conceptual Design Summary. PAGEREF _Toc13579342 \h 3

Business Situation. PAGEREF _Toc13579343 \h 3

Overview of Conceptual Solution Alternatives. PAGEREF _Toc13579344 \h 3

Solution Architecture. PAGEREF _Toc13579345 \h 3




[Introduction to the Template


Description: The Conceptual Design is a strategic statement of how the solution will provide value to the collection of usage scenarios. The usage scenarios describe all the participants and activities within a business environment that require a solution. The Conceptual Design addresses that need by describing one or more alternative solutions. This design statement is expressed in the context of the solution users (customer, external services, etc), and describes what the solution will do to support their activities. 


Visuals make a great impact and increase readers’ understanding of the Conceptual Design. This can be accomplished using UML diagrams, Microsoft Visio diagrams, or Application and Database modeling tools, and other types of graphics.

The Conceptual Design document should be brief. The audience for this document is likely to include parties outside the development team who do not have deep technical knowledge. In that context, this document is a powerful communication tool.


Justification: Developing a Conceptual Design ensures: 1) the breadth of usage scenarios are analyzed and an overall, business-oriented solution response is developed and 2) the team considers more than one alternative based not only on the usage scenarios but on all other business objectives and constraints that are part of the project.


{Team Role Primary: Program Management is responsible for ensuring that the Conceptual Design document is completed. Development has the primary responsibility for creating the document’s content.


Team Role Secondary: Product Management will review and understand the Conceptual Design in order to convey it to parties external to the team and to ensure that it aligns with initial project sponsor requirements. User Experience will review the design to ensure user requirements are met. Release Management will participate both in content creation and review along with development to ensure operational, deployment, migration, interoperability and support needs are addressed within the designs.}]



Conceptual Design Summary

[Description: Provide an overall summary of the contents of this document. This should include the criteria by which the design was established and how it was validated.


Justification: Some project participants may need to know only the document’s highlights, and summarizing creates that user view. It also enables the full reader to know the essence of the document before they examine the details.]

<<Begin text here>>


Business Situation

[Description: The Business Situation section restates in summary fashion the business opportunity and other relevant information contained in the Vision/Scope document.


Justification: This information frames the context for the Conceptual Design.]

<<Begin text here>>


Overview of Conceptual Solution Alternatives

[Description: The Overview of Conceptual Solution Alternatives section identifies and describes the solution design alternatives. These are described using business language and state “what” each solution alternative brings to the enterprise. This section should include evaluations of alternatives (advantages and disadvantages), a recommendation for a specific conceptual solution, and the rationale for that recommendation. Graphics are very appropriate for this section.


Justification: Key stakeholders closest to the business situation to be resolved by a solution should be presented with this information in order to make an informed decision. Considering and documenting alternatives preempts the question “Did you consider this alternative?” As a solution is developed, if the team encounters difficulties, they can return to the documented alternatives to reconsider them.]

<<Begin text here>>


Solution Architecture

[Description:  The architectural design describes how features and functions will operate together to form the solution. It identifies the specific components of the solution and their relationships. A diagram illustrating these components and relationships is an excellent communication device.


Justification: This section describes “how” the conceptual design(s) will work. The architectural design provides a description of the features and functions in a fully functional, integrated environment. This information enables the customer to visualize the solution in its environment. This architecture is not expressed in technical detail, but in a manner that portrays how all of the solution pieces will fit together technically.]

<<Begin text here>>