4,000
edits
Changes
mLine 4:
Line 4: − + − − ==Goals== Line 13:
Line 11: − + − + + − *Engages in contract negotiation + + + + + + − + − + − + − Conduct analyses to determine risk and to develop risk mitigation strategies + − Conduct assessments of technical maturity, process health and stability, and risk to communicate progress to stakeholders and authorities at key decision points + − + − Advise the PM regarding the technical readiness of the program to proceed to the next phase of effort − Obtain independent subject matter experts as appropriate for reviews and audits − + + + + + + + + + + + + + + + + + + − + − + − + − + − + − + − − + − + − + − + − + − *Risk Management focal points+ + Line 73:
Line 92: − The Configuration Management process allows technical insight into all levels of the system design and is the principal methodology for establishing and maintaining consistency of a system’s functional, performance, and physical attributes with its requirements, design, and operational information throughout the system's life cycle. + − + − + − Configuration Management consists of five interrelated functions that, when collectively applied, allow the program to maintain consistency between product configuration information and the product throughout its life cycle. + − + − The following are the five Configuration Management functions: + − + − Configuration Management Planning and Management is a formal document and plan to guide the Configuration Management program that includes items such as:+ − + − Personnel + − + − Training requirements + − + − + − + − + − + − + − − − Configuration Verification and Audit − 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.+ − − ==Integration Plan== − The PM and SE are responsible for planning, managing, and executing the Integration process. − − Programs that develop an integration plan are more successful. − − This plan defines the stages of integration, during which system elements are successively integrated to form higher level elements, and eventually the finished product. − − The integration plan should include a description of the required teams, test standards, testing methods, and integration schedule.
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}}
==Core Competency==
==Core Competency==
*Critical thinking and problem solving
*Critical thinking and problem solving
*Excels at decision-making
*Excels at decision-making
*Primary Leadership and Planning (leader of leaders)
*Primary consultant to Leadership and Planning
*Leads Conflict resolution
*Recommends Conflict resolution
*Engages in negotiation
*High Degree of Adaptability
*High Degree of Adaptability
*Stress Tolerant
*Stress Tolerant
==Goals==
===Integration Design, Build, and Test Plan===
*The Project Management(PM) and Systems integrator (SI) are responsible for planning, managing, and executing the Integration process.
*Projects that develop an integration plan have a high degree of success.
*The plan defines the stages of integration, during which system elements are successively integrated to form higher level elements, and eventually the finished RobotX platform.
*The integration plan includes descriptions of the required teams, test standards, testing methods, and integration schedule.
==Technical Assessment responsibilities==
==Technical Assessment responsibilities==
Establish event-driven technical planning
*Establish event-driven technical planning
Identify appropriate measures and metrics
*Identify Test measures and Metrics assessing design success
Identify performance measures to assess program health and technical progress
*Identify performance measures and Metrics assessing technical progress
*Determine risk and develop mitigation strategies
*Propose changes in the technical approach to address risk mitigation
Propose changes in the technical approach to address risk mitigation activities
*Continually measure technical readiness of the RobotX platform
== Primary Roles and Responsibilities ==
====Integrated Test Plan====
*includes design baseline evaluation
*# identifying critical design parameters
*# setting performance threshholds
*individual Subsystems test plans
*# interface tests
*# functional tests
*# effectiveness tests
*platform performance test plan
*# MOE (measures of effectiveness)
*#* maximum time on range without operation intervention
*#* hardware operational goal accomplishment
*#* AI operational goal accomplishment
*# MOF (measures of functionality)
*#*subsystems Interoperability
*#*mean time between Interoperability failure
== 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.
'''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.
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 these 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 subsystem integration and system performance
*thoughtful analysis and management of requirements insuring for system sustainability
*synchronization with the program’s Configuration Management process to mitigate unintended consequences due to project change
*synchronization with the program’s Configuration Management process to mitigate unintended or unanticipated consequences due to 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===
*prioritize identified technical risks and developing mitigation actions
*prioritize identified technical risks and developing mitigation actions
*provide risk mitigation plan to PM for review and approval
*provide risk mitigation plan to PM for review and approval
'''Risk Management focal points'''
{| {{Table}}
{| {{Table}}
! Activity !! Intent Is to Answer the Question
! Activity !! Intent Is to Answer the Question
Configuration management is the means by which the results of the systems engineering effort are documented and tracked as changes occur.
Configuration management is the means by which the results of the systems engineering effort are documented and tracked as changes occur.
Configuration Management process
*has a formal document and plan to guide the Configuration Management
*allows technical insight into all levels of the system design
*principal methodology for establishing and maintaining consistency of subsystem’s attributes
**design
**functional
**performance
**physical
*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
#Baselining processes
Administrative meeting guidelines including a definition of procedures and tools
#Configuration control and Configuration status accounting
Baselining processes
#Naming conventions
Configuration control and Configuration status accounting
#Audits and Reviews
Naming conventions
#Configuration Identification
Audits and Reviews
#Configuration Change Management
Configuration Identification
#Configuration Status Accounting
Configuration Change Management
Configuration Status Accounting
===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