System/Subsystem Specifications - HUD
[pic]
SYSTEM/SUBSYSTEM
SPECIFICATIONS
Project or System Name
U.S. Department of Housing and Urban Development
Month, Year
Revision Sheet
|Release No. |Date |Revision Description |
|Rev. 0 |5/30/00 |System/Subsystem Specifications Template and Checklist |
|Rev. 1 |4/12/02 |Conversion to WORD 2000 format |
| | | |
| | | |
| | | |
| | | |
| | | |
| |System/Subsystem Specifications Authorization Memorandum |
I have carefully assessed the System/Subsystem Specifications for the (System Name). This document has been completed in accordance with the requirements of the HUD System Development Methodology.
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
______ The document is accepted.
______ The document is accepted pending the changes noted.
______ The document is not accepted.
We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based on our authority and judgment, the continued operation of this system is authorized.
_______________________________ _____________________
NAME DATE
Project Leader
_______________________________ _____________________
NAME DATE
Operations Division Director
_______________________________ _____________________
NAME DATE
Program Area/Sponsor Representative
_______________________________ _____________________
NAME DATE
Program Area/Sponsor Director
SYSTEM/SUBSYSTEM SPECIFICATIONS
TABLE OF CONTENTS
Page #
1.0 GENERAL INFORMATION 1-1
1.1 Purpose 1-1
1.2 Scope 1-1
1.3 System Overview 1-2
1.4 Project References 1-2
1.5 Acronyms and Abbreviations 1-2
1.6 Points of Contact 1-3
1.6.1 Information 1-3
1.6.2 Coordination 1-3
2.0 SYSTEM CHARACTERISTICS 2-1
2.1 System/Subsystem Description 2-1
2.2 System/Subsystem Partitions and Functions 2-1
2.3 Accuracy and Validity 2-1
2.4 Timing 2-1
2.5 Adaptability 2-2
2.6 Failure Contingencies 2-2
2.7 System Logical Flow 2-2
3.0 ENVIRONMENT 3-1
3.1 Equipment Environment 3-1
3.1.1 Processors 3-1
3.1.2 Storage Media 3-1
3.1.3 Input/Output Devices 3-1
3.2 Communications Environment 3-2
3.2.1 Network 3-2
3.2.2 Interface Protocol 3-2
3.3 Software Environment 3-3
3.4 Software Interfaces 3-3
3.5 Diagnostics 3-3
3.6 Data and Reports 3-4
3.6.1 Inputs 3-2
3.6.2 Outputs/Reports 3-3
4.0 SECURITY 4-1
4.1 Control Points 4-1
4.2 Vulnerabilities 4-1
4.3 Safeguards 4-1
1.0 GENERAL INFORMATION
NOTE TO AUTHOR: Highlighted, italicized text throughout this template is provided solely as background information to assist you in creating this document. Please delete all such text, as well as the instructions in each section, prior to submitting this document. ONLY YOUR PROJECT-SPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF THIS DOCUMENT.
The System/Subsystem Specifications provides a listing of the specifications of the system and its subsystems, as well as a detailed description of the system/subsystem functions. It also defines in detail the interfaces with other systems and subsystems and the facilities to be used for accomplishing the interfaces. For each subsystem, include such information as timing requirements, equipment needs, communications environment, support software, security, and input and output records.
GENERAL INFORMATION
1 1.1 Purpose
Describe the purpose of the System/Subsystem Specifications.
2 1.2 Scope
Describe the scope of the System/Subsystem Specifications as it relates to the project.
3 1.3 System Overview
Provide a brief system overview description as a point of reference for the remainder of the document. In addition, include the following:
1. Responsible organization
2. System name or title
3. System code
4. System category
1. Major application: performs clearly defined functions for which there is a readily identifiable security consideration and need
2. General support system: provides general ADP or network support for a variety of users and applications
5. Operational status
3. Operational
4. Under development
5. Undergoing a major modification
6. System environment and special conditions
4 1.4 Project References
Provide a list of the references that were used in preparation of this document. Examples of references are:
7. Previously developed documents relating to the project
8. Documentation concerning related projects
9. HUD standard procedures documents
5 1.5 Acronyms and Abbreviations
Provide a list of the acronyms and abbreviations used in this document and the meaning of each.
6 1.6 Points of Contact
1 1.6.1 Information
Provide a list of the points of organizational contact (POCs) that may be needed by the document user for informational and troubleshooting purposes. Include type of contact, contact name, department, telephone number, and E-mail address (if applicable). Points of contact may include, but are not limited to, helpdesk POC, development/maintenance POC, and operations POC.
2 1.6.2 Coordination
Provide a list of organizations that require coordination between the project and its specific support function (e.g., installation coordination, security, etc.). Include a schedule for coordination activities.
2.0 SYSTEM CHARACTERISTICS
SYSTEM CHARACTERISTICS
This section provides an expansion of the information published in the Functional Requirements Document (FRD) and Data Requirements Document (DRD) to reflect additional details.
1 2.1 System/Subsystem Description
Provide a general description of the system/subsystem to establish a reference for the remainder of the document. Within this description, you may include graphics representing the relationship of the user organizations to the major components including networking, communications, and distributed processing.
2 2.2 System/Subsystem Partitions and Functions
Although the descriptions of the system/subsystem functions may be refined and more detailed as a result of the continuing analysis and design effort, they must maintain a direct relationship to the system functions established in the FRD and be described in such a way that the system/subsystem environment can be related to them.
Describe the system/subsystem partitions and functions, documenting the traceability between the functional and data requirements and the defined subsystem.
3 2.3 Accuracy and Validity
Describe the features incorporated in the design of the system/subsystem that meet the accuracy and validity requirements imposed on each system/subsystem level. Accuracy requirements of mathematical calculations and data must be considered.
4 2.4 Timing
Describe the timing requirements imposed on the system/subsystem, if applicable. For example, the following timing requirements may be considered:
10. Throughput time
11. Response time to queries and to updates of the data files
12. Sequential relationship of system/subsystem functions
13. Priorities imposed by types of input and changes in modes of operation
14. Timing requirements for the range of traffic load under varying operating conditions
15. Sequencing and interleaving of software units and systems (including the requirement for interrupting the operation of a software unit without loss of data)
5 2.5 Adaptability
Provide a description of the capability to be incorporated for adapting the system/subsystem to changing requirements, such as anticipated operational changes, interaction with new or improved systems, and planned periodic changes. Components and procedures designed to be subject to change will be identified.
6 2.6 Failure Contingencies
Discuss alternative courses of action that are to be taken to satisfy requirements if the proposed system fails. Include as appropriate:
16. Backup. Alternative requirements for ensuring the continued achievement of system functions.
17. Fallback. Fallback techniques for ensuring the continued satisfaction of the specific requirements of the system. Fallback indicates the use of another system to satisfy the system requirements. For example: the fallback techniques for an automated system might be manual manipulation and recording data.
18. Degraded Modes of Operation. If applicable, state priorities for restoring the essential functional processing steps in the event that full processing capability is not available.
7 2.7 System Logical Flow
Present the logical flow of the system/subsystem. Supplement the representation with a program design language presentation, a narrative presentation, or a combination of the two. Graphics should provide an integrated presentation of the system/subsystem dynamics, entrances and exits, and interfaces with other software units. Represent all modes of operations, priorities, cycles, special handling and general flow of control.
3.0 ENVIRONMENT
ENVIRONMENT
This section provides detailed information on the environment discussed in the FRD and the Capacity Planning Survey (Final Assessment). These changes will be discussed in terms of the impacts on the currently available environmental components (equipment, software) as well as the impacts on estimates and functions that were based on the originally planned environment.
1 3.1 Equipment Environment
Provide a description of the equipment required for the operation of the system/subsystem. Include descriptions of the equipment presently available, as well as a more detailed discussion of the characteristics and impact of any new equipment necessary for system operation.
1 3.1.1 Processors
Include number and type of each online/offline processor, and size of internal storage.
2 3.1.2 Storage Media
Include number and type of storage media.
3 3.1.3 Input/Output Devices
Include number and type of each online/offline device.
2 3.2 Communications Environment
Describe the data communications environment of the system. Additionally, provide detailed schematics of the portions of the communications environment that directly relate to the system or subsystem being documented. If a standard communications environment is being used, reference can be made to it.
1 3.2.1 Network
Describe the network configuration and characteristics if non-HUD standard configuration or Web-based, including, at a minimum, the following:
19. Transmission requirements and technique
20. Data transfer rates (baud rates)
21. Gateways
22. Geographic locations
23. Required system use times, if any
24. Line speed capability
If the system utilizes a non-HUD standard configuration, indicate the date the proposed configuration was approved for this project by the Configuration Change Management Board (CCMB).
2 3.2.2 Interface Protocol
Identify all protocols.
3 3.3 Software Environment
Describe the software with which the system/subsystem must interact. Include both support software and test software, if needed. Provide the correct name, description, and documentation references of each such software system, subsystem, and program. Include a reference to the operating system to be used, the database management system (if any), and the language for the following:
25. compiler
26. assembler
27. program
28. query
If any of the software components used are not currently HUD-approved standards, indicate the date these items were approved for this project by the Configuration Change Management Board (CCMB).
4 3.4 Software Interfaces
Provide a description of the interfaces with other application software units, including those of other operational capabilities and from other government agencies. For each interface, specify the file format (input/output) and delivery media.
5 3.5 Diagnostics
Describe diagnostic procedures that will allow identification and classification of system/subsystem problems.
6 3.6 Data and Reports
1 3.6.1 Inputs
Identify the inputs and provide information about the characteristics of each input to the system/subsystem, such as:
29. file name
30. format and type of data
31. validation criteria
32. volume
33. frequency
34. means of entry
35. source documents and their disposition
36. security and privacy considerations
2 3.6.2 Outputs/Reports
Identify the output data and reports, including information about the characteristics of each output from the system/subsystem, such as:
37. file names
38. report formats
39. selection criteria for displays or outputs
40. types of output media
41. disposition of products
4.0 SECURITY
SECURITY
To control dissemination of sensitive information, all or portions of this chapter may be maintained and distributed separately from the remainder of the document.
4.1 4.1 Control Points
A control point can be located at any interface at which there is movement of data within or between sites.
Describe the points in the system at which there is a known vulnerability that requires specific safeguards.
4.2 4.2 Vulnerabilities
A design, implementation, or operational condition inherent in the application or system that lends itself to error, loss, or compromise of information, or denial of service is a system vulnerability.
Describe the vulnerabilities at each control point.
4.3 4.3 Safeguards
Describe the safeguard requirements at each control point to reduce vulnerabilities.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- 2019 toyota highlander specifications edmunds
- ford v10 specifications motorhome
- windows subsystem for linux 2
- windows subsystem for linux is not enabled
- how to use linux subsystem windows 10
- windows subsystem for linux command line
- how to install windows subsystem linux
- subsystem for linux windows 10
- update windows subsystem for linux
- windows subsystem for linux update setup
- vehicle manufacturer specifications using vin
- icd 705 technical specifications 2019