Systems Engineering Process Model
-
-
-
-
-
-
- System Thinking
- General Engineering
- Critical Thinking
- System Modelling and Analysis
- Lifecycles
- Capability Engineering
- Requirements Definition
- System Architecting
- Integration
- Interfaces
- Operation and Support
- Decision Management
- Concurrent Engineering
- Information Management
- Configuration Management
- Explains what “systems thinking” is and explains why it is important
- Explains what “emergence” is, why it is important, and how it can be “positive” or negative” in its effect upon the system as a whole
- Explains what a “system hierarchy” is and why it is important
- Explains what “system context” is for a given system of interest and describes why it is important
- Explains why it is important to be able to identify and understand what interfaces are
- Explains why it is important to recognize interactions amongst systems and their elements
- Explains why it is important to understand purpose and functionality of a system of interest
- Explains how business, enterprise and technology can each influence the definition and development of the system and vice versa
- Explains why it may be necessary to approach systems thinking in different ways, depending on the situation, and provides examples
- Defines the properties of a system
- Explains how system behavior produces emergent properties
- Uses the principles of system partitioning within system hierarchy on a project
- Defines system characteristics in order to improve understanding of need
- Explains why the boundary of a system needs to be managed
- Identifies the influence of wider enterprise on a project
- Uses systems thinking to contribute to enterprise technology development activities
- Develops their own systems thinking insights to share thinking across the wider project (e.g. working groups, other teams)
- Develops own understanding of this competency area through Continual Professional Development (CPD)
- (in addition to those at Supervised Practitioner level)
- Uses analysis of a system functions and parts to predict resultant system behavior
- Identifies the context of a system from a range of viewpoints including system boundaries and external interfaces
- Identifies the interaction between humans and systems, and systems and systems
- Identifies enterprise and technology issues affecting the design of a system and addresses them using a systems thinking approach
- Uses appropriate systems thinking approaches to a range of situations, integrating the outcomes to get a full understanding of the whole
- Identifies potential enterprise improvements to enable system development
- Guides team systems thinking activities in order to ensure current activities align to purpose
- Develops existing case studies and examples of systems thinking to apply in new situations
- Guides new or supervised practitioners in System thinking techniques in order to develop their knowledge, abilities, skills or associated behaviors
- Maintains and enhances own competence in this area through Continual Professional Development (CPD) activities
- Creates enterprise-level policies, procedures, guidance and best practice for systems thinking, including associated tools
- Judges the suitability of project-level systems thinking on behalf of the enterprise, to ensure its validity
- Persuades key enterprise-level stakeholders across the enterprise to support and maintain the technical capability and strategy of the enterprise
- Adapts existing systems thinking practices on behalf of the enterprise to accommodate novel, complex or difficult system situations or problems
- Persuades project stakeholders across the enterprise to improve the suitability of project technical strategies in order to maintain their validity
- Persuades key stakeholders to address enterprise-level issues identified through systems thinking
- Coaches or mentors practitioners across the enterprise in Systems thinking in order to develop their knowledge, abilities, skills or associated behaviors
- Promotes the introduction and use of novel techniques and ideas in systems thinking across the enterprise, to improve enterprise competence in this area
- Develops expertise in this competency area through specialist Continual Professional Development (CPD) activities
- Communicates own knowledge and experience in systems thinking in order to improve best practice beyond the enterprise boundary
- Influences individuals and activities beyond the enterprise boundary to support the systems thinking approach of their own enterprise
- Advises organizations beyond the enterprise boundary on the suitability of their approach to systems thinking
- Advises organizations beyond the enterprise boundary on complex or sensitive systems thinking issues
- Champions the introduction of novel techniques and ideas in systems thinking beyond the enterprise boundary, in order to develop the wider Systems Engineering community in this competency
- Coaches individuals beyond the enterprise boundary in systems thinking techniques, in order to further develop their knowledge, abilities, skills or associated behaviors
- Maintains expertise in this competency area through specialist Continual Professional Development (CPD) activities
-
-
-
-
(System Requirements Definition - System requirements traceability)
-
(Operation - Validated system)
-
(Transition - Verified system)
-
(Architecture Definition - Architecture traceability)
-
(Business or Mission Analysis - Problem or opportunity statement)
-
(Project Planning - SEMP)
-
(Disposal - Disposal procedure)
-
(Project Assessment and Control - Project assessment and control strategy)
-
(Transition - Final RVTM)
-
(Infrastructure Management - Project infrastructure)
-
(Architecture Definition - Life cycle constraints)
-
(Acquisition - Acquisition reply)
-
(Project Planning - Strategy documents)
-
(Design Definition - System architecture rationale)
-
(Acquisition - Enabling system requirements)
-
(Project Planning - Project schedule)
-
(Business or Mission Analysis - Business or mission analysis strategy)
-
(Portfolio Management - Organization lesson learned)
-
(Integration - System architecture description)
-
(Supply - Supply agreement)
-
(Measurement - Measurement record)
-
(Architecture Definition - Architecture definition record)
-
(Quality Management - Quality assurance evaluation report)
-
(Verification - Final RVTM)
-
(Stakeholder Needs and Requirements Definition - System function identification)
-
(Infrastructure Management - Infrastructure management report)
-
(System Requirements Definition - Final RVTM)
-
(Design Definition - Design traceability)
-
(Verification - Updated RVTM)
-
(System Analysis - Life cycle concepts)
-
(System Requirements Definition - Stakeholder requirements traceability)
-
(Business or Mission Analysis - Business requirements)
-
(Transition - Transition report)
-
(Verification - Verification procedure)
-
(System Requirements Definition - System requirements definition strategy)
-
(Stakeholder Needs and Requirements Definition - Major stakeholder identification)
-
(Operation - Operation enabling system requirements)
-
(Human Resource Management - Qualified personnel)
-
(Architecture Definition - System requirements)
-
(Design Definition - Design definition record)
-
(Business or Mission Analysis - Project constraints)
-
(Infrastructure Management - Organization infrastructure)
-
(Quality Assurance - Quality assurance record)
-
(Knowledge Management - Organization lesson learned)
-
(Decision Management - Decision situation)
-
(Project Planning - Project budget)
-
(Architecture Definition - Interface definition update identification)
-
(Project Planning - Quality assurance plan)
-
(Maintenance - Maintenance record)
-
(Verification - Verification constraints)
-
(Quality Management - Quality assurance report)
-
(Infrastructure Management - Infrastructure management plan)
-
(Disposal - Maintenance report)
-
(Project Assessment and Control - Procedures)
-
(Architecture Definition - Updated RVTM)
-
(Acquisition - Accepted system or system element)
-
(Operation - Life cycle concepts)
-
(Implementation - System design description)
-
(System Requirements Definition - Updated RVTM)
-
(Integration - Integration procedure)
-
(Portfolio Management - Organization strategic plan)
-
(Project Planning - Documentation tree)
-
(Project Assessment and Control - Project lessons learned)
-
(Information Management - Information management strategy)
-
(Architecture Definition - Preliminary interface definition)
-
(Implementation - System elements)
-
(Quality Assurance - Quality management report)
-
(Integration - Integration enabling system requirements)
-
(Human Resource Management - Project human resources needs)
-
(System Requirements Definition - Life cycle concepts)
-
(Quality Management - Quality assurance plan)
-
(Measurement - Measurement report)
-
(System Requirements Definition - Architecture traceability)
-
(Supply - Disposed system)
-
(Maintenance - Wartungsstrategie)
-
(Stakeholder Needs and Requirements Definition - Life cycle constraints)
-
(Design Definition - TPM data)
-
(Acquisition - Acquisition payment)
-
(Implementation - System element description)
-
(Verification - Verified system)
-
(Architecture Definition - System requirements traceability)
-
(Knowledge Management - Knowledge management report)
-
(Information Management - Candidate information items)
-
(Business or Mission Analysis - Preliminary MOE needs)
-
(Stakeholder Needs and Requirements Definition - System requirements traceability)
-
(Business or Mission Analysis - Business requirements traceability)
-
(Project Assessment and Control - Validated requirements)
-
(Integration - Accepted system or system element)
-
(Implementation - Implementation report)
-
(Supply - Supply strategy)
-
(Portfolio Management - Project direction)
-
(Stakeholder Needs and Requirements Definition - Validated requirements)
-
(Quality Management - Quality management evaluation report)
-
(Measurement - Measurement needs)
-
(Life Cycle Model Management - QM corrective actions)
-
(Stakeholder Needs and Requirements Definition - Business requirements traceability)
-
(Life Cycle Model Management - Organization strategic plan)
-
(Supply - Supply payment)
-
(System Analysis - System analysis record)
-
(Integration - Interface definition)
-
(Project Planning - Supply response)
-
(Design Definition - TPM needs)
-
(Maintenance - Operation report)
-
(Architecture Definition - System architecture rationale)
-
(Integration - Interface definition update identification)
-
(Operation - Operation constraints)
-
(Project Planning - Project lessons learned)
-
(Architecture Definition - Preliminary TPM needs)
-
(Portfolio Management - Organization portfolio direction and constraints)
-
(Supply - Validated system)
-
(Verification - Verification criteria)
-
(Portfolio Management - Portfolio management report)
-
(Project Planning - Acquisition need)
-
(System Requirements Definition - System function definition)
-
(Integration - Implementation traceability)
-
(Design Definition - Life cycle concepts)
-
(Measurement - Measurement data)
-
(Verification - Integration report)
-
(Project Planning - Organization strategic plan)
-
(Quality Assurance - Quality assurance report)
-
(Verification - Integrated system or system elements)
-
(Project Planning - Qualified personnel)
-
(Validation - Validation strategy)
-
(Disposal - Disposal enabling system requirements)
-
(Business or Mission Analysis - Preliminary validation criteria)
-
(Maintenance - Maintenance report)
-
(Integration - System elements)
-
(Risk Management - Risk record)
-
(Quality Management - QM corrective actions)
-
(Acquisition - Acquisition agreement)
-
(Stakeholder Needs and Requirements Definition - Preliminary validation criteria)
-
(Integration - Life cycle concepts)
-
(Project Planning - Life cycle models)
-
(Validation - Validated system)
-
(Integration - Integrated system or system elements)
-
(Quality Management - Customer satisfaction inputs)
-
(Configuration Management - Candidate configuration items)
-
(Knowledge Management - Knowledge management system)
-
(Risk Management - Risk management strategy)
-
(Business or Mission Analysis - Alternative solution classes)
-
(System Requirements Definition - Stakeholder requirements)
-
(Transition - Transition constraints)
-
(Maintenance - Life cycle concepts)
-
(Life Cycle Model Management - Life cycle model management plan)
-
(Stakeholder Needs and Requirements Definition - Stakeholder needs and requirements definition strategy)
-
(Quality Management - Organization strategic plan)
-
(Knowledge Management - Organization strategic plan)
-
(Architecture Definition - Life cycle concepts)
-
(Supply - Request for supply)
-
(Stakeholder Needs and Requirements Definition - Alternative solution classes)
-
(Architecture Definition - Preliminary TPM data)
-
(Transition - Trained operators and maintainers)
-
(Risk Management - Candidate risks and opportunities)
-
(Project Planning - Project constraints)
-
(Implementation - Transition enabling system requirements)
-
(Stakeholder Needs and Requirements Definition - MOE data)
-
(Stakeholder Needs and Requirements Definition - Initial RVTM)
-
(Maintenance - Validated system)
-
(Implementation - Interface definition)
-
(Business or Mission Analysis - Concept of operations (ConOps))
-
(Disposal - Disposal report)
-
(Acquisition - Acquisition need)
-
(Portfolio Management - Portfolio management record)
-
(Project Assessment and Control - Project budget)
-
(Implementation - Implementation strategy)
-
(Infrastructure Management - Project infrastructure needs)
-
(Acquisition - Acquisition record)
-
(Verification - Verification record)
-
(Project Planning - Project tailoring strategy)
-
(Business or Mission Analysis - Stakeholder requirements traceability)
-
(Project Assessment and Control - Reports)
-
(Disposal - Validated system)
-
(Design Definition - Life cycle constraints)
-
(Quality Assurance - Quality assurance evaluation report)
-
(Business or Mission Analysis - Major stakeholder identification)
-
(Validation - Final RVTM)
-
(Verification - Verification enabling system requirements)
-
(Knowledge Management - Records)
-
(Architecture Definition - System functional interface identification)
-
(System Requirements Definition - Verification criteria)
-
(Disposal - Disposal constraints)
-
(Implementation - System architecture rationale)
-
(Business or Mission Analysis - Organization strategic plan)
-
(Acquisition - Acquisition report)
-
(Project Planning - Project planning record)
-
(Disposal - Disposal strategy)
-
(Validation - Validation criteria)
-
(Information Management - Project change requests)
-
(Stakeholder Needs and Requirements Definition - Life cycle concepts)
-
(Life Cycle Model Management - Life cycle model management report)
-
(Maintenance - Trained operators and maintainers)
-
(System Requirements Definition - System requirements definition record)
-
(Operation - Operation record)
-
(Acquisition - Acquisition strategy)
-
(Integration - Integration constraints)
-
(Stakeholder Needs and Requirements Definition - Project constraints)
-
(System Requirements Definition - Bedarf an Leistungsmessungen)
-
(System Requirements Definition - System functional interface identification)
-
(Configuration Management - Configuration baselines)
-
(Architecture Definition - Design traceability)
-
(Quality Assurance - Quality assurance plan)
-
(Verification - System requirements)
-
(Project Assessment and Control - Project performance measures needs)
-
(Stakeholder Needs and Requirements Definition - Stakeholder requirements traceability)
-
(Maintenance - Validation report)
-
(Validation - Life cycle concepts)
-
(Project Planning - Project human resources needs)
-
(Implementation - Implementation traceability)
-
(Transition - Transition strategy)
-
(Acquisition - Request for supply)
-
(Validation - Validated requirements)
-
(System Requirements Definition - System function identification)
-
(System Analysis - Analysis situations)
-
(Quality Assurance - QM corrective actions)
-
(Supply - Supplied System)
-
(Portfolio Management - Organizational infrastructure needs)
-
(Transition - Installation procedure)
-
(Quality Management - Quality management plan)
-
(Supply - Supply response)
-
(Project Assessment and Control - Project assessment and control record)
-
(Stakeholder Needs and Requirements Definition - Validation criteria)
-
(Portfolio Management - Project portfolio)
-
(Business or Mission Analysis - Life cycle constraints)
-
(Life Cycle Model Management - Quality management evaluation report)
-
(Design Definition - Preliminary TPM needs)
-
(Acquisition - Acquired system)
-
(Supply - Supply record)
-
(Project Assessment and Control - Project change requests)
-
(Decision Management - Decision record)
-
(Risk Management - Risk report)
-
(Configuration Management - Configuration management record)
-
(Integration - Integration report)
-
(Infrastructure Management - Organizational infrastructure needs)
-
(System Analysis - System analysis strategy)
-
(System Requirements Definition - Life cycle constraints)
-
(Integration - Integration strategy)
-
(Implementation - System element documentation)
-
(Disposal - Life cycle concepts)
-
(Validation - Validation procedure)
-
(Measurement - Measurement strategy)
-
(Design Definition - System functional interface identification)
-
(Design Definition - Interface definition update identification)
-
(Portfolio Management - Supply strategy)
-
(System Analysis - System analysis report)
-
(Design Definition - System design rationale)
-
(Project Planning - Source documents)
-
(Configuration Management - Configuration management report)
-
(Design Definition - Design definition strategy)
-
(Disposal - Disposed system)
-
(Business or Mission Analysis - Preliminary life cycle concepts)
-
(Implementation - Design traceability)
-
(Maintenance - Operator/maintainer training material)
-
(Stakeholder Needs and Requirements Definition - Problem or opportunity statement)
-
(Implementation - Implementation constraints)
-
(Project Assessment and Control - QM corrective actions)
-
(Disposal - Operation report)
-
(Project Assessment and Control - Work Breakdown Structure, WBS)
-
(Validation - Installed system)
-
(Portfolio Management - Project status report)
-
(Design Definition - System element description)
-
(Implementation - Operator/maintainer training material)
-
(Information Management - Information management record)
-
(Project Assessment and Control - Measurement repository)
-
(Verification - Verification strategy)
-
(Project Assessment and Control - Configuration baselines)
-
(Design Definition - Preliminary interface definition)
-
(Stakeholder Needs and Requirements Definition - MOE needs)
-
(Operation - Trained operators and maintainers)
-
(Supply - Supply report)
-
(Business or Mission Analysis - Preliminary MOE data)
-
(Human Resource Management - Project portfolio)
-
(Project Assessment and Control - Quality assurance evaluation report)
-
(Design Definition - Interface definition)
-
(Stakeholder Needs and Requirements Definition - Stakeholder needs and requirements definition record)
-
(Stakeholder Needs and Requirements Definition - Preliminary life cycle concepts)
-
(Implementation - System architecture description)
-
(Information Management - Information management strategy)
-
(Information Management - Information repository)
-
(Operation - Maintenance report)
-
(Validation - Stakeholder requirements)
-
(Operation - Validation report)
-
(Life Cycle Model Management - Organizational policies, procedures, and assets)
-
(Configuration Management - Project change requests)
-
(Portfolio Management - Portfolio management plan)
-
(Transition - Transition record)
-
(Stakeholder Needs and Requirements Definition - Stakeholder requirements)
-
(Project Assessment and Control - Project status report)
-
(Architecture Definition - Documentation tree)
-
(Stakeholder Needs and Requirements Definition - Preliminary MOE data)
-
(Architecture Definition - Architecture definition strategy)
-
(Design Definition - System requirements)
-
(Business or Mission Analysis - Business or mission analysis record)
-
(Project Assessment and Control - Information repository)
-
(Project Assessment and Control - Project control requests)
-
(Supply - Organization strategic plan)
-
(Validation - Validation record)
-
(Stakeholder Needs and Requirements Definition - Source documents)
-
(Business or Mission Analysis - Source documents)
-
(Design Definition - System architecture description)
-
(Human Resource Management - Human resource management plan)
-
(Operation - Operation report)
-
(Human Resource Management - Human resource management record)
-
(Operation - Operation strategy)
-
(Verification - Life cycle concepts)
-
(Verification - Interface definition)
-
(System Requirements Definition - System requirements)
-
(Integration - System element documentation)
-
(Project Planning - Work Breakdown Structure, WBS)
-
(Configuration Management - Configuration management strategy)
-
(Maintenance - Maintenance enabling system requirements)
-
(Human Resource Management - Organization strategic plan)
-
(Decision Management - Decision management strategy)
-
(Design Definition - Implementation traceability)
-
(Knowledge Management - Project lessons learned)
-
(System Requirements Definition - MOP data)
-
(Decision Management - Decision report)
-
(Design Definition - Preliminary TPM data)
-
(Knowledge Management - Knowledge management plan)
-
(Project Assessment and Control - Project schedule)
-
(Project Planning - QM corrective actions)
-
(Design Definition - Architecture traceability)
-
(Stakeholder Needs and Requirements Definition - Stakeholder needs)
-
(System Analysis - Life cycle constraints)
-
(System Requirements Definition - Initial RVTM)
-
(Infrastructure Management - Organization strategic plan)
-
(Operation - Operator/maintainer training material)
-
(Implementation - Life cycle concepts)
-
(Transition - Life cycle concepts)
-
(Project Planning - Project infrastructure needs)
-
(Stakeholder Needs and Requirements Definition - Preliminary MOE needs)
-
(Acquisition - Organization strategic plan)
-
(Life Cycle Model Management - Organizational process performance measures needs)
-
(Integration - Integration record)
-
(Human Resource Management - Human resource management report)
-
(Life Cycle Model Management - Organization tailoring strategy)
-
(Maintenance - Maintenance constraints)
-
(Validation - Validation enabling system requirements)
-
(Verification - Verification report)
-
(Implementation - Implementation record)
-
(Transition - Transition enabling system requirements)
-
(Transition - Verification report)
-
(Architecture Definition - System function definition)
-
(Design Definition - System design description)
-
(Quality Assurance - Quality management plan)
-
(Maintenance - Maintenance procedure)
-
(Implementation - System design rationale)
-
(Transition - Installed system)
-
(Life Cycle Model Management - Organizational process performance measures data)
-
(Validation - Validation report)
-
(Quality Management - Quality management guidelines)
-
(Life Cycle Model Management - Life cycle models)
-
(Project Planning - Project portfolio)
-
(Transition - Operator/maintainer training material)
-
(Project Planning - Project direction)
-
(Quality Management - Quality management record)
-
(Project Assessment and Control - Project performance measures data)
-
(Disposal - Disposal record)
-
(Validation - Transition report)
-
(Design Definition - System function definition)
-
(Quality Management - Quality management report)
-
(Architecture Definition - System architecture description)
-
(Life Cycle Model Management - Life cycle model management record)
-
(Quality Assurance - Quality management guidelines)
-
(Validation - Validation constraints)
-
(Measurement - Measurement repository)
-
(Decision Management - Prepare for decisions)
-
(Business or Mission Analysis - Manage the business or mission analysis)
-
(Operation - Support the customer)
-
(Quality Assurance - Treat incidents and problems)
-
(Portfolio Management - Define and authorize projects)
-
(Quality Management - Plan quality management)
-
(Stakeholder Needs and Requirements Definition - Transform stakeholder needs into stakeholder requirements)
-
(Transition - Manage results of transition)
-
(Project Planning - Activate the project)
-
(Architecture Definition - Relate the architecture to design)
-
(Verification - Perform verification)
-
(Design Definition - Manage the design)
-
(Decision Management - Analyze the decision information)
-
(Acquisition - Monitor the agreement)
-
(Design Definition - Assess alternatives for obtaining system elements)
-
(Architecture Definition - Develop models and views of candidate architectures)
-
(Project Planning - Define the project)
-
(Disposal - Perform disposal)
-
(Supply - Respond to a tender)
-
(Maintenance - Perform maintenance)
-
(Configuration Management - Pefrorm configuration evaluation)
-
(Architecture Definition - Prepare for architecture definition)
-
(Knowledge Management - Manage knowledge, skills and knowledge assets)
-
(Architecture Definition - Develop architecture viewpoints)
-
(Quality Assurance - Manage QA records and reports)
-
(Maintenance - Perform logistics support)
-
(Life Cycle Model Management - Improve the process)
-
(System Requirements Definition - Manage system requirements)
-
(Operation - Perform operation)
-
(Stakeholder Needs and Requirements Definition - Define stakeholder needs)
-
(Quality Assurance - Perform product or service evaluation)
-
(Life Cycle Model Management - Assess the process)
-
(Project Assessment and Control - Assess the project)
-
(Information Management - Perform information management)
-
(Verification - Manage results of verification)
-
(Stakeholder Needs and Requirements Definition - Analyze stakeholder requirements)
-
(Disposal - Prepare for disposal)
-
(Design Definition - Prepare for design definition)
-
(Quality Assurance - Perform process evaluations)
-
(Risk Management - Treat risks)
-
(Disposal - Finalize the disposal)
-
(Integration - Manage results of integration)
-
(Validation - Prepare for validation)
-
(Configuration Management - Perform configuration status accounting)
-
(Verification - Prepare for verification)
-
(System Requirements Definition - Define system requirements)
-
(Risk Management - Plan risk management)
-
(Implementation - Prepare for implementation)
-
(Risk Management - Monitor risks)
-
(Configuration Management - Perform configuration change management)
-
(Information Management - Prepare for information management)
-
(Business or Mission Analysis - Prepare for business or mission analysis)
-
(Portfolio Management - Terminate projects)
-
(Risk Management - Analyze risks)
-
(Configuration Management - Plan configuration management)
-
(Stakeholder Needs and Requirements Definition - Prepare for stakeholder needs and requirements definition)
-
(Transition - Perform the transition)
-
(Human Resource Management - Identify skills)
-
(Supply - Establish and maintain an agreement)
-
(Project Assessment and Control - Control the project)
-
(Maintenance - Manage results of maintenance and logistics)
-
(Knowledge Management - Plan knowledge management)
-
(Integration - Prepare for integration)
-
(Risk Management - Manage the risk profile)
-
(Quality Assurance - Prepare for quality assurance)
-
(System Analysis - Prepare for system analysis)
-
(Acquisition - Accept the product or service)
-
(System Requirements Definition - Prepare for system requirements definition)
-
(Acquisition - Advertise the acquisition and select the supplier)
-
(Business or Mission Analysis - Evaluate alternative solution classes)
-
(Integration - Perform integration - Successively integrate system element configurations until the complete system is synthesized)
-
(Implementation - Manage results of implementation)
-
(Acquisition - Establish and maintain the agreement)
-
(Project Planning - Plan project and technical management)
-
(Human Resource Management - Develop skills)
-
(Operation - Manage results of operation)
-
(Quality Management - Perform quality management corrective action and preventive action)
-
(Supply - Prepare for supply)
-
(Life Cycle Model Management - Establish the process)
-
(System Requirements Definition - Analyze system requirements)
-
(Architecture Definition - Assess architecture candidates)
-
(Portfolio Management - Evaluate the portfolio of projects)
-
(Configuration Management - Perform release control)
-
(Stakeholder Needs and Requirements Definition - Develop the operational concept and other lifecycle concepts)
-
(Acquisition - Prepare for the acquisition)
-
(Supply - Deliver and support the product or service)
-
(System Analysis - Perform system analysis)
-
(Transition - Prepare for transition)
-
(Architecture Definition - Manage the selected architecture)
-
(Business or Mission Analysis - Define the problem or opportunity space)
-
(Maintenance - Prepare for maintenance)
-
(Knowledge Management - Share knowledge assets throughout the organization)
-
(Design Definition - Establish design characteristics and design enablers related to each system element)
-
(Infrastructure Management - Maintain the infrastructure)
-
(Validation - Manage results of validation)
-
(Business or Mission Analysis - Characterize the solution space)
-
(Project Assessment and Control - Plan for project assessment and control)
-
(Human Resource Management - Acquire and provide skills)
-
(Supply - Execute the agreement)
-
(Configuration Management - Perform configuration identification)
-
(Knowledge Management - Share knowledge and skills throughout the organization)
-
(Stakeholder Needs and Requirements Definition - Manage the stakeholder needs and requirements definition)
-
(Decision Management - Make and manage decisions)
-
(Infrastructure Management - Establish the infrastructure)
-
(System Analysis - Manage system analysis)
-
(Implementation - Perform implementation)
-
(Measurement - Perform measurement)
-
(Measurement - Prepare for measurement)
-
(Quality Management - Assess quality management)
-
(Validation - Perform validation)
-
(Operation - Prepare for operation)
-
(Enabling system requirements - Transition enabling system requirements)
-
(Enabling system requirements - Operation enabling system requirements)
-
(Enabling system requirements - Disposal enabling system requirements)
-
(Enabling system requirements - Integration enabling system requirements)
-
(Enabling system requirements - Validation enabling system requirements)
-
(Enabling system requirements - Verification enabling system requirements)
-
(Enabling system requirements - Maintenance enabling system requirements)
-
(Enabling system requirements - Transition enabling system requirements)
-
(Reports - Risk report)
-
(Reports - Disposal report)
-
(Reports - Project status report)
-
(Reports - Integration report)
-
(Reports - Quality management report)
-
(Reports - Supply report)
-
(Reports - Transition report)
-
(Reports - Quality management evaluation report)
-
(Reports - Implementation report)
-
(Reports - Knowledge management report)
-
(Reports - Acquisition report)
-
(Reports - Information management strategy)
-
(Reports - Quality assurance report)
-
(Reports - Life cycle model management report)
-
(Reports - Human resource management report)
-
(Reports - Measurement report)
-
(Reports - Maintenance report)
-
(Reports - Operation report)
-
(Reports - Quality assurance evaluation report)
-
(Reports - Quality assurance evaluation report)
-
(Reports - Portfolio management report)
-
(Reports - Configuration management report)
-
(Reports - System analysis report)
-
(Reports - Decision report)
-
(Reports - Verification report)
-
(Reports - Validation report)
-
(Reports - Infrastructure management report)
-
(Measurement needs - MOE needs)
-
(Measurement needs - Bedarf an Leistungsmessungen)
-
(Measurement needs - Preliminary TPM needs)
-
(Measurement needs - Preliminary MOE needs)
-
(Measurement needs - TPM needs)
-
(Measurement data - Organizational process performance measures data)
-
(Measurement data - Project performance measures data)
-
(Measurement data - TPM data)
-
(Measurement data - MOE data)
-
(Measurement data - Preliminary MOE data)
-
(Measurement data - MOP data)
-
(Measurement data - Preliminary TPM data)
-
(Life cycle constraints - Integration constraints)
-
(Life cycle constraints - Maintenance constraints)
-
(Life cycle constraints - Implementation constraints)
-
(Life cycle constraints - Transition constraints)
-
(Life cycle constraints - Verification constraints)
-
(Life cycle constraints - Validation constraints)
-
(Life cycle constraints - Operation constraints)
-
(Life cycle constraints - Disposal constraints)
-
(Records - Business or mission analysis record)
-
(Records - Quality assurance record)
-
(Records - System analysis record)
-
(Records - Supply record)
-
(Records - Project planning record)
-
(Records - Risk record)
-
(Records - Life cycle model management record)
-
(Records - Quality management record)
-
(Records - Validation record)
-
(Records - Maintenance record)
-
(Records - Implementation record)
-
(Records - Stakeholder needs and requirements definition record)
-
(Records - Verification record)
-
(Records - System requirements definition record)
-
(Records - Project assessment and control record)
-
(Records - Transition record)
-
(Records - Information management record)
-
(Records - Portfolio management record)
-
(Records - Operation record)
-
(Records - Design definition record)
-
(Records - Acquisition record)
-
(Records - Configuration management record)
-
(Records - Integration record)
-
(Records - Decision record)
-
(Records - Measurement record)
-
(Records - Architecture definition record)
-
(Records - Human resource management record)
-
(Records - Disposal record)
-
(Strategy documents - Acquisition strategy)
-
(Strategy documents - Configuration management strategy)
-
(Strategy documents - Organization tailoring strategy)
-
(Strategy documents - Design definition strategy)
-
(Strategy documents - Project tailoring strategy)
-
(Strategy documents - Decision management strategy)
-
(Strategy documents - Architecture definition strategy)
-
(Strategy documents - Operation strategy)
-
(Strategy documents - Information management strategy)
-
(Strategy documents - Integration strategy)
-
(Strategy documents - Measurement strategy)
-
(Strategy documents - Disposal strategy)
-
(Strategy documents - System requirements definition strategy)
-
(Strategy documents - Implementation strategy)
-
(Strategy documents - Validation strategy)
-
(Strategy documents - Supply strategy)
-
(Strategy documents - Transition strategy)
-
(Strategy documents - Risk management strategy)
-
(Strategy documents - Business or mission analysis strategy)
-
(Strategy documents - Project assessment and control strategy)
-
(Strategy documents - Organization strategic plan)
-
(Strategy documents - Wartungsstrategie)
-
(Strategy documents - Stakeholder needs and requirements definition strategy)
-
(Strategy documents - System analysis strategy)
-
(Strategy documents - Verification strategy)
-
(Procedures - Disposal procedure)
-
(Procedures - Installation procedure)
-
(Procedures - Integration procedure)
-
(Procedures - Validation procedure)
-
(Procedures - Verification procedure)
-
(Procedures - Maintenance procedure)
-
(Architecture Definition - System Thinking)
-
(Architecture Definition - General Engineering)
-
(Architecture Definition - Critical Thinking)
-
(Architecture Definition - System Modelling and Analysis)
-
(Architecture Definition - Lifecycles)
-
(Architecture Definition - Capability Engineering)
-
(Architecture Definition - System Architecting)
-
(Architecture Definition - Operation and Support)
-
(Architecture Definition - Requirements Definition)
-
(Architecture Definition - Integration)
-
(Architecture Definition - Interfaces)
-
(Architecture Definition - Decision Management)
-
(Architecture Definition - Concurrent Engineering)
-
(Architecture Definition - Information Management)
-
(Architecture Definition - Configuration Management)
-
(System Thinking - Awareness - Explains what “system context” is for a given system of interest and describes why it is important)
-
(System Thinking - Awareness - Explains why it is important to be able to identify and understand what interfaces are)
-
(System Thinking - Awareness - Explains what “systems thinking” is and explains why it is important)
-
(System Thinking - Awareness - Explains how business, enterprise and technology can each influence the definition and development of the system and vice versa)
-
(System Thinking - Awareness - Explains what “emergence” is, why it is important, and how it can be “positive” or negative” in its effect upon the system as a whole)
-
(System Thinking - Awareness - Explains why it is important to recognize interactions amongst systems and their elements)
-
(System Thinking - Awareness - Explains why it may be necessary to approach systems thinking in different ways, depending on the situation, and provides examples)
-
(System Thinking - Awareness - Explains why it is important to understand purpose and functionality of a system of interest)
-
(System Thinking - Awareness - Explains what a “system hierarchy” is and why it is important)
-
(System Thinking - Awareness - System Thinking)
-
(System Thinking - Supervised Practitioner - Identifies the influence of wider enterprise on a project)
-
(System Thinking - Supervised Practitioner - Develops own understanding of this competency area through Continual Professional Development (CPD))
-
(System Thinking - Supervised Practitioner - Defines the properties of a system)
-
(System Thinking - Supervised Practitioner - Develops their own systems thinking insights to share thinking across the wider project (e.g. working groups, other teams))
-
(System Thinking - Supervised Practitioner - Defines system characteristics in order to improve understanding of need)
-
(System Thinking - Supervised Practitioner - Uses systems thinking to contribute to enterprise technology development activities)
-
(System Thinking - Supervised Practitioner - Explains how system behavior produces emergent properties)
-
(System Thinking - Supervised Practitioner - Explains why the boundary of a system needs to be managed)
-
(System Thinking - Supervised Practitioner - Uses the principles of system partitioning within system hierarchy on a project)
-
(System Thinking - Supervised Practitioner - System Thinking)
-
(System Thinking - Practitioner - Identifies enterprise and technology issues affecting the design of a system and addresses them using a systems thinking approach)
-
(System Thinking - Practitioner - Identifies the interaction between humans and systems, and systems and systems)
-
(System Thinking - Practitioner - Identifies the context of a system from a range of viewpoints including system boundaries and external interfaces)
-
(System Thinking - Practitioner - Uses analysis of a system functions and parts to predict resultant system behavior)
-
(System Thinking - Practitioner - (in addition to those at Supervised Practitioner level))
-
(System Thinking - Practitioner - Uses appropriate systems thinking approaches to a range of situations, integrating the outcomes to get a full understanding of the whole)
-
(System Thinking - Practitioner - Identifies potential enterprise improvements to enable system development)
-
(System Thinking - Practitioner - Guides team systems thinking activities in order to ensure current activities align to purpose)
-
(System Thinking - Practitioner - Develops existing case studies and examples of systems thinking to apply in new situations)
-
(System Thinking - Practitioner - Guides new or supervised practitioners in System thinking techniques in order to develop their knowledge, abilities, skills or associated behaviors)
-
(System Thinking - Practitioner - Maintains and enhances own competence in this area through Continual Professional Development (CPD) activities)
-
(System Thinking - Practitioner - System Thinking)
-
(System Thinking - Lead Practitioner - Persuades key stakeholders to address enterprise-level issues identified through systems thinking)
-
(System Thinking - Lead Practitioner - Creates enterprise-level policies, procedures, guidance and best practice for systems thinking, including associated tools)
-
(System Thinking - Lead Practitioner - Judges the suitability of project-level systems thinking on behalf of the enterprise, to ensure its validity)
-
(System Thinking - Lead Practitioner - Coaches or mentors practitioners across the enterprise in Systems thinking in order to develop their knowledge, abilities, skills or associated behaviors)
-
(System Thinking - Lead Practitioner - Promotes the introduction and use of novel techniques and ideas in systems thinking across the enterprise, to improve enterprise competence in this area)
-
(System Thinking - Lead Practitioner - Persuades key enterprise-level stakeholders across the enterprise to support and maintain the technical capability and strategy of the enterprise)
-
(System Thinking - Lead Practitioner - Adapts existing systems thinking practices on behalf of the enterprise to accommodate novel, complex or difficult system situations or problems)
-
(System Thinking - Lead Practitioner - Develops expertise in this competency area through specialist Continual Professional Development (CPD) activities)
-
(System Thinking - Lead Practitioner - Persuades project stakeholders across the enterprise to improve the suitability of project technical strategies in order to maintain their validity)
-
(System Thinking - Expert - Champions the introduction of novel techniques and ideas in systems thinking beyond the enterprise boundary, in order to develop the wider Systems Engineering community in this competency)
-
(System Thinking - Expert - Communicates own knowledge and experience in systems thinking in order to improve best practice beyond the enterprise boundary)
-
(System Thinking - Expert - Coaches individuals beyond the enterprise boundary in systems thinking techniques, in order to further develop their knowledge, abilities, skills or associated behaviors)
-
(System Thinking - Expert - Advises organizations beyond the enterprise boundary on complex or sensitive systems thinking issues)
-
(System Thinking - Expert - Advises organizations beyond the enterprise boundary on the suitability of their approach to systems thinking )
-
(System Thinking - Expert - Influences individuals and activities beyond the enterprise boundary to support the systems thinking approach of their own enterprise)
-
(System Thinking - Expert - Maintains expertise in this competency area through specialist Continual Professional Development (CPD) activities)
-
(System Thinking - Lead Practitioner - System Thinking)
-
(System Thinking - Expert - System Thinking)
-
(Procedures - Organizational policies, procedures, and assets)
-
- Process Descriptions
- 03 - Agreement Processes
- 01 - Technical Processes
- 02 - Technical Management Processes
- 04 - Organizational Project-Enabling Processes
- 05 - Artifacts Details (Interpretation)
- Competencies Mapping (Prototype)
- C-01 - Technical Processes
- Competencies (Prototype)
- 01 - System Life-Cycle Processes