4,000
edits
Changes
Jump to navigation
Jump to search
mLine 97:
Line 97: − The Interface Management process helps ensure that developers document all internal and external interface requirements and requirements changes in accordance with the program’s Configuration Management Plan. + − + − Developers also should communicate interface information to their counterparts responsible for affected systems and system elements, and should plan for coherent testing to verify expected performance and ultimately operational performance. + − Interface management is an iterative process. As knowledge of the system and system elements increases during design activities, verifiable lower-level requirements and interfaces are defined and refined. + − + − Developers should assess impacts of the originally defined capabilities and interfaces, performance parameter thresholds and objectives, and the overall system when defining and modifying interfaces.+ − + − important that the nature of the interfaces be carefully documented to ensure proper function and interoperability.+
→Interface Management
===Interface Management===
===Interface Management===
*careful interface documentation ensures proper '''function''' and '''interoperability
'''*ensures that all the development teams document all internal and external interface requirements
*documents Requirements changes in accordance with the Configuration Management Plan
*communicates interface information to team counterparts responsible for affected systems and system elements
*drives coherent testing to verify expected performance and eventually operational performance
*an iterative process
*as knowledge of the system and system elements becomes more defined during design activities, verifiable lower-level requirements and interfaces are defined and refined
*consider impacts of the originally defined capabilities and interfaces, and the overall system when defining and modifying interfaces
==Integration Plan==
==Integration Plan==