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 |
|
|
Author Position |
|
|
Date |
|
Ó 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
Change
Record
|
Date |
Author |
Version |
Change
Reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Version
Approved |
Position |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
|
|
Document
Properties
|
Item |
Details |
|
Document
Title |
System
Requirements |
|
Author |
|
|
Creation
Date |
|
|
Last
Updated |
|
Systems and Services Dependencies
Versioning/Life-Cycle Impact to Systems and Environment
[Introduction to the
Template:
Description:
The System Requirements define the current state of the IT infrastructure
(cable, routers, bridges, etc. that provide a service) and how that current
state will be impacted by the new solution. It identifies how the new solution will
interact with the existing system and where critical dependencies exist that
must be carefully managed.
Justification:
The
nature of the current infrastructure must be understood so that a solution can
be developed and deployed with a minimum of negative
impact.
{Team
Role Primary: Program Management
is responsible for ensuring that the system requirements are completed. Development has the primary
responsibility for creating the content of the system requirements. Release will participate with
Development both in content creation and review to ensure operational,
deployment, migration, interoperability and support needs are addressed within
the system requirements document.
Team
Role Secondary:
Product Management will review and
understand the system requirements in order to convey those requirements to
parties external to the team. Test and
User Experience will review the system requirements to understand their
content and have context for developing their plans.}]
[Description:
Provide an overall summary of the contents of this document. This should include
the criteria by which the system requirements were established and how they were
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>>
[Description: The Systems and Services Dependencies
section identifies and describes in detail each service/feature dependency. Is should also describe the processes
that need to be in place to ensure that the solution’s design (and ultimately
the deployment) doesn’t improperly impact an existing
system/service.]
<<Begin text
here>>
[Description:
The Interoperability Requirements section identifies all external systems and
services with which the solution will interact. It should also describe the nature of
the interaction.]
[Description:
The Network Impact Assessment section describes how the solution will impact the
existing network environment. It should describe the changes required to the
existing network environment in order for the solution to be accepted into
production.
It should also describe the processes
that must be in place to minimize disruption of existing infrastructure
services.]
<<Begin text
here>>
[Description: The
Versioning/Life-Cycle Impact to Systems and Environment section describes
the
processes that must be in place to ensure that future solution versions will not
impact the existing environment.]