4,000
edits
Changes
mLine 4:
Line 4: − + Line 51:
Line 51: − + − + − + − + − + − + − + − + − + − + Line 100:
Line 100: − + − #Personnel − #Training requirements − + − + − #Configuration Verification and Audit − +
no edit summary
<br>
<br>
{{Tree chart/start|align=center|summary= Combined RobotX Team}}
{{Tree chart/start|align=center|summary= Combined RobotX Team}}
{{Tree chart| | | | | | | |SI| | | | |SI=[[File:Male-2.jpg|center|124px]]<big>'''Marine Science'''<br>[[Subsystems Integrator]]</big>}}
{{Tree chart| | | | | | | |SI| | | | |SI=[[File:Male-2.jpg|center|124px]]<big>'''[[Marine Science & Technology | Marine Science]]'''<br>[[Subsystems Integrator]]</big>}}
{{Tree chart/end}}
{{Tree chart/end}}
== Primary Management Roles and Responsibilities ==
== Primary Management Roles and Responsibilities ==
===Requirements Management===
===Requirements Management===
Requirements are the foundation of the program and requirements management process helps ensure delivery of capability that meets intended mission performance objectives.<br>
'''Requirements''' are the foundation of the project and requirements management process helps ensure delivery of capability that meets intended mission performance objectives.<br>
Performance objectives are identified in operational terms at the system level during implementation of the Requirements Definition and Requirements Analysis processes.<br>
Performance objectives are identified in operational terms at the system level during implementation of the '''Requirements''' Definition and '''Requirements''' Analysis processes.<br>
The Subsystems Integrator has these '''Requirements Management''' responsibilities:
The Subsystems Integrator has these '''Requirements Management''' responsibilities:
*maintain a current and approved set of requirements
*maintain a current and approved set of '''Requirements'''
*thoughtful analysis and management of requirements insuring for system sustainability
*thoughtful analysis and management of '''Requirements''' insuring for subsystem integration and system performance
*synchronization with the program’s Configuration Management process to mitigate unintended or unanticipated consequences due to change
*synchronization with the program’s Configuration Management process to mitigate unintended consequences due to project change
*rigorous documentation of changes to the system performance specification
*rigorous documentation of changes to the system performance specification
===Process Responsibilities===
===Process Responsibilities===
*tracks requirements changes and maintains traceability of the system performance specification and delivered capability
*tracks '''Requirements''' changes and maintains traceability of the system performance specification and capabilities
*traces the high-level requirements down to the system elements through the lowest level of the design as the system design evolves to lower levels of detail
*traces the high-level '''Requirements''' down to the system elements through the lowest level of the design as the system design evolves to lower levels of detail
*establishes and maintains a Requirements Traceability Matrix (RTM)
*establishes and maintains a '''Requirements''' Traceability Matrix (RTM)
*#capturing all requirements in the system performance specification
*#capturing all '''Requirements''' in the system performance specification
*#documenting their decomposition/derivation and allocation history
*#documenting their decomposition/derivation and allocation history
*#document rationale for all entries and changes
*#document rationale for all entries and changes
*work with PM to track cost, schedule, and performance impacts associated with requirement changes and/or growth
*work with Project Management Team to track cost, schedule, and performance impacts associated with '''Requirements''' changes
===Risk Management===
===Risk Management===
**performance
**performance
**physical
**physical
*consists of interrelated functions that maintain consistency between product configuration information
*consists of interrelated functions that maintain consistency between project configuration information
#Responsibilities and Resources
#Responsibilities and Resources
#Administrative meeting guidelines including a definition of procedures and tools
#Administrative meeting guidelines including a definition of procedures and tools
#Baselining processes
#Baselining processes
#Configuration control and Configuration status accounting
#Configuration control and Configuration status accounting
#Naming conventions
#Naming conventions
#Audits and Reviews
#Audits and Reviews
#Configuration Identification
#Configuration Identification
#Configuration Change Management
#Configuration Change Management
#Configuration Status Accounting
#Configuration Status Accounting
===Interface Management===
===Interface Management===
*careful interface documentation ensures proper '''function''' and '''interoperability'''
*careful interface documentation ensures proper '''function''' and '''interoperability'''
*ensures that all the development teams document all internal and external interface requirements
*ensures that all the development teams document all internal and external interface requirements
*documents Requirements changes in accordance with the Configuration Management Plan
*documents '''Requirements''' changes in accordance with the Configuration Management Plan
*communicates interface information to team counterparts responsible for affected systems and system elements
*communicates interface information to team counterparts responsible for affected systems and system elements
*drives coherent testing to verify expected performance and eventually operational performance
*drives coherent testing to verify expected performance and eventually operational performance