diff --git a/.gitattributes b/.gitattributes
deleted file mode 100644
index 0633fc04bf91a234e096abcd5a8d369ea141fe3b..0000000000000000000000000000000000000000
--- a/.gitattributes
+++ /dev/null
@@ -1,37 +0,0 @@
-*.7z filter=lfs diff=lfs merge=lfs -text
-*.arrow filter=lfs diff=lfs merge=lfs -text
-*.bin filter=lfs diff=lfs merge=lfs -text
-*.bz2 filter=lfs diff=lfs merge=lfs -text
-*.ckpt filter=lfs diff=lfs merge=lfs -text
-*.ftz filter=lfs diff=lfs merge=lfs -text
-*.gz filter=lfs diff=lfs merge=lfs -text
-*.h5 filter=lfs diff=lfs merge=lfs -text
-*.joblib filter=lfs diff=lfs merge=lfs -text
-*.lfs.* filter=lfs diff=lfs merge=lfs -text
-*.mlmodel filter=lfs diff=lfs merge=lfs -text
-*.model filter=lfs diff=lfs merge=lfs -text
-*.msgpack filter=lfs diff=lfs merge=lfs -text
-*.npy filter=lfs diff=lfs merge=lfs -text
-*.npz filter=lfs diff=lfs merge=lfs -text
-*.onnx filter=lfs diff=lfs merge=lfs -text
-*.ot filter=lfs diff=lfs merge=lfs -text
-*.parquet filter=lfs diff=lfs merge=lfs -text
-*.pb filter=lfs diff=lfs merge=lfs -text
-*.pickle filter=lfs diff=lfs merge=lfs -text
-*.pkl filter=lfs diff=lfs merge=lfs -text
-*.pt filter=lfs diff=lfs merge=lfs -text
-*.pth filter=lfs diff=lfs merge=lfs -text
-*.rar filter=lfs diff=lfs merge=lfs -text
-*.safetensors filter=lfs diff=lfs merge=lfs -text
-saved_model/**/* filter=lfs diff=lfs merge=lfs -text
-*.tar.* filter=lfs diff=lfs merge=lfs -text
-*.tar filter=lfs diff=lfs merge=lfs -text
-*.tflite filter=lfs diff=lfs merge=lfs -text
-*.tgz filter=lfs diff=lfs merge=lfs -text
-*.wasm filter=lfs diff=lfs merge=lfs -text
-*.xz filter=lfs diff=lfs merge=lfs -text
-*.zip filter=lfs diff=lfs merge=lfs -text
-*.zst filter=lfs diff=lfs merge=lfs -text
-*tfevents* filter=lfs diff=lfs merge=lfs -text
-id-iso15288-model/images/id-f1ed0a3ba3885350a21f8c28a6cac4a9.png filter=lfs diff=lfs merge=lfs -text
-id-iso15288-model/images/id-0c610db7a2e54be2a6bbe18c69aa5eff.png filter=lfs diff=lfs merge=lfs -text
diff --git a/INCOSE Handbook v 5.archimate b/INCOSE Handbook v 5.archimate
deleted file mode 100644
index 684c9795a9ec920d3a64da5d96ae187324e694da..0000000000000000000000000000000000000000
--- a/INCOSE Handbook v 5.archimate
+++ /dev/null
@@ -1,5017 +0,0 @@
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.1.1] The purpose of the Business or Mission Analysis process is to define the business or mission problem or opportunity, characterize the solution space, and determine potential solution class(es) that could address a problem or take advantage of an opportunity. See detailed description in the INCOSE Handbook v.5, page 103
-
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.2.1] The purpose of the Stakeholder Needs and Requirements Definition process is to define the stakeholder requirements for a system that can provide the capabilities needed by users and other stakeholders in a defined environment. See detailed description in the INCOSE Handbook v.5, page 107
-
-
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.3.1] The purpose of the System Requirements Definition process is to transform the stakeholder, useroriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user. See detailed description in the INCOSE Handbook v.5, page 112
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.4.1] The purpose of the Architecture Definition process is to generate system architecture alternatives, to select one or more alternative(s) that frame stakeholder concerns and meet system requirements, and to express this in a set of consistent views. See detailed description in the INCOSE Handbook v.5, page 118
-
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.5.1] The purpose of the Design Definition process is to provide sufficient detailed data and information about the system and its elements to enable the imple- mentation consistent with architectural entities as defined in models and views of the system architecture. See detailed description in the INCOSE Handbook v.5, page 124
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288, [6.4.6.1] The purpose of the System Analysis process is to provide a rigorous basis of data and information for technical understanding to aid decision-�making across the life cycle. See detailed description in the INCOSE Handbook v.5, page 129
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.7.1] The purpose of the Implementation process is to realize a specified system element. See detailed description in the INCOSE Handbook v.5, page 132
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.8.1] The purpose of the Integration process is to synthesize a set of system elements into a realized system (product or service) that satisfies system requirements* architecture, and design. See detailed description in the INCOSE Handbook v.5, page 134
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.9.1] The purpose of the Verification process is to provide objective evidence that a system or system element fulfils its specified requirements and characteristics. See detailed description in the INCOSE Handbook v.4, page 138
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.10.1] The purpose of the Transition process is to establish a capability for a system to provide services specified by stakeholder requirements in the operational environment. See detailed description in the INCOSE Handbook v.5, page 143
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.11.1] The purpose of the Validation process is to provide objective evidence that the system, when in use, fulfills its business or mission objectives and stakeholder requirements, achieving its intended use in its intended operational environment. See detailed description in the INCOSE Handbook v.5, page 146
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.12.1] The purpose of the Operation process is to use the system to deliver its services. See detailed description in the INCOSE Handbook v.5, page 152
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.13.1] The purpose of the Maintenance process is to sustain the capability of the system to provide a service. See detailed description in the INCOSE Handbook v.5, page 154
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.4.14.1] The purpose of the Disposal process is to end the existence of a system element or system for a specified intended use, appropriately handle replaced or retired elements, and to properly attend to identified critical disposal needs. See detailed description in the INCOSE Handbook v.5, page 156
-
-
-
-
-
- Identifies and describes the classes of solutions that may address the problem or opportunity.
-
-
- Analyses that arise from any stakeholder. Can originate from any life cycle process.
-
-
- Approaches, schedules, resources, and specific considerations required to perform business or mission analysis.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the business or mission analysis activities.
-
-
- Permanent, readable form of data, information, or knowledge related to business or mission analysis.
-
-
- Identified information needs of the decision makers with respect to system-of-interest expectations.
-
-
- Data provided for the identified system-of-interest measurement needs.
-
-
- Externally imposed limitation on the system, its design, or implementation or on the process used to develop or modify a system. (ISO/IEC/IEEE 29148, 2018).
-
-
- Approaches, schedules, resources, and specific considerations required to perform design definition.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the design definition activities.
-
-
- Permanent, readable form of data, information++ or knowledge related to design definition.
-
-
- Approaches, schedules, resources, and specific considerations required to perform disposal.
-
-
- Presents an ordered series of steps to perform disposal.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the disposal activities.
-
-
- Permanent, readable form of data, information, or knowledge related to disposal.
-
-
- Approaches, schedules, resources, and specific considerations required to perform implementation.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the implementation activities.
-
-
- Permanent++ readable form of data, information, or knowledge related to implementation.
-
-
- Approaches, schedules, resources++ and specific considerations required to perform integration.
-
-
- Presents an ordered series of steps to perform integration.
-
-
- Permanent, readable form of data, information, or knowledge related to integration.
-
-
- Presents an ordered series of steps to perform transition.
-
-
- System or system element (product or service) that has been aggregated from system elements.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the integration activities.
-
-
- System (product or service) that has been installed in its operational environment.
-
-
- Articulation and refinement of the various life cycle concepts consistent with the stakeholder needs. Typical concepts include: acquisition concept; deployment concept; operational concept (OpsCon); support concept; retirement concept.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the maintenance activities.
-
-
- System (product or service) that has been maintained for use in its operational environment.
-
-
- Approaches, schedules, resources, and specific considerations required to perform maintenance.
-
-
- Presents an ordered series of steps to perform maintenance.
-
-
- Permanent, readable form of data, information, or knowledge related to maintenance.
-
-
- System (product or service) being used in its operational environment.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the operation activities.
-
-
- Artifacts that are validated
-
-
- Approaches, schedules, resources, and specific considerations required to perform operation.
-
-
- Presents an ordered series of steps to perform operation.
-
-
- Permanent, readable form of data, information, or knowledge related to operation.
-
-
- Artifacts that are verified
-
-
- Description of the problem or opportunity. Should be derived from the organization strategy and provide enough detail to understand the gap or new capability that is being considered
-
-
- Identified requirements for enabling systems of the system-of-interest.
-
-
- Approaches, schedules, resources, and specific considerations required to perform stakeholder needs and requirements definition.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the stakeholder needs and requirements definition activities.
-
-
- Permanent, readable form of data, information, or knowledge related to stakeholder needs and requirements definition.
-
-
- List of individuals or organizations having a right++ share, claim, or interest in a system or in ist possession of characteristics that meet their needs and expectations. (Adapted from ISO/IEC/IEEE 15288, 2023)
-
-
- Structured collection of the requirements [characteristics, context, concepts, constraints and priorities] of the stakeholder and the relationship to the external environment. (ISO/IEC/IEEE 29148, 2018)
-
-
- Approaches, schedules, resources, and specific considerations required to perform system analysis.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the system analysis activities.
-
-
- Permanent, readable form of data, information, or knowledge related to system analysis.
-
-
- The fundamental conception of a system-of-interest in terms of its purpose, system qualities (such as feasibility, performance, safety, and interoperability), constraints, and design decisions and rationale. Identification of the architecture’s stakeholders and the stakeholders’ architecture-related concerns. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Approaches, schedules, resources, and specific considerations required to perform system architecture definition.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the system architecture definition activities.
-
-
- Provides results of system architecture assessments. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Permanent, readable form of data, information, or knowledge related to system architecture definition.
-
-
- Rationale for architecture selection, technological/technical system element selection, and allocation between system requirements and architectural entities.
-
-
- Describes the design of a system or element. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
- Rationale for design selection, system element selection, and allocation between system requirements and system elements. Includes rationale of major selected implementation options and enablers.
-
-
- Provides results of system design assessments. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Design attributes or distinguishing features that pertain to a measurable description of a product or service. (ISO/IEC/IEEE 15288, 2023)
-
-
- Description of the interfaces between systems and system elements. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
- Applies the system architecture description to the low-level system configuration items and elements. It is at a level of detail to permit design, implementation, and test. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- System element (product or service) implemented consistent with its system element requirements.
-
-
- Structured collection of the requirements [functions, performance, design constraints, and other attributes] for the system and its operational environments and external interfaces. (ISO/IEC/IEEE 29148, 2018)
-
-
- Approaches, schedules, resources, and specific considerations required to perform system requirements definition.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the system requirements definition activities.
-
-
- Permanent, readable form of data, information, or knowledge related to system requirements definition.
-
-
- Definitions of viewpoints to document the procedures for creating, interpreting, analyzing, and evaluating architectural data. One or more views of the system. Each architectural view is a representation of the complete system from the perspective of one or more system concerns, for its stakeholders. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Records the relationship between two or more artifacts of the development process (e.g., requirements, functions, system elements, verifications, and validations, tasks). (Adapted from ISO/IEC/IEEE 24765++ 2017)
-
-
- Materials for the provision of formal and informal learning activities. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
- Trained individuals or organizations that perform the operation, maintenance, or other functions of or for a system.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the transition activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform transition.
-
-
- Permanent, readable form of data, information, or knowledge related to transition.
-
-
- Approaches, schedules, resources, and specific considerations required to perform verification.
-
-
- Presents an ordered series of steps to perform verification.
-
-
- Set of system requirements that have been verified.
-
-
- System architecture and design that has been verified.
-
-
- The verification criteria (the measures to be assessed), who will perform verification activities, and the verification environments of the system-of-interest.
-
-
- System (product or service) that has been verified.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the verification activities.
-
-
- Permanent, readable form of data, information, or knowledge related to verification.
-
-
- Approaches, schedules, resources, and specific considerations required to perform validation.
-
-
- Presents an ordered series of steps to perform validation.
-
-
- Permanent, readable form of data, information, or knowledge related to validation.
-
-
- Set of stakeholder needs and requirements that have been validated.
-
-
- System architecture and design that has been validated.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the validation activities.
-
-
- The validation criteria (the measures to be assessed), who will perform validation activities++ and the validation environments of the system-of-interest.
-
-
- System (product or service) that has been validated.
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.1.1] The purpose of the Project Planning process is to produce and coordinate effective and workable plans. See detailed description in the INCOSE Handbook v.5, page 70
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.2.1] The purpose of the Project Assessment and Control process is to assess if the plans are aligned and feasible, determine the status of the project, technical and process performance, and direct execution to ensure that the performance is according to plans and schedules, within projected budgets, to satisfy technical objectives.
-
-See detailed description in the INCOSE Handbook v.5, page 75
-
-
-
-
-
- As defined by ISO/IEC/IEEE 15288:2023, [6.3.3.1] The purpose of the Decision Management process is to provide a structured, analytical framework for objectively identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life cycle and select the most beneficial course of action. See detailed description in the INCOSE Handbook v.5, page 78
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.4.1] The purpose of the Risk Management process is to identify, analyze, treat and monitor the risks continually. See detailed description in the INCOSE Handbook v.5, page 81
-
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.5.1] The purpose of the Configuration Management process is to manage and control system elements and configurations over the life cycle. CM also manages consistency between a product and its associated configuration definition. See detailed description in the INCOSE Handbook v.5, page 87
-
-
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.6.1] The purpose of the Information Management process is to generate, obtain, confirm, transform, retain, retrieve, disseminate and dispose of information, to designated stakeholders. Information management plans, executes, and controls the provision of information to designated stakeholders that is unambiguous, complete, verifiable, consistent, modifiable, traceable, and presentable. Information includes technical, project, organizational, agreement, and user information. Information is often derived from data records of the organization, system, process, or project. See detailed description in the INCOSE Handbook v.5, page 91
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.7.1] The purpose of the Measurement process is to collect, analyze, and report objective data and information to support effective management and demonstrate the quality of the products, services, and processes. See detailed description in the INCOSE Handbook v.5, page 93
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.3.8.1] The purpose of the Quality Assurance process is to help ensure the effective application of the organization's Quality Management process to the project. See detailed description in the INCOSE Handbook v.5, page 98
-
-
-
-
-
-
-
- Identified need that cannot be met within the organization encountering the need or a need that can be met in a more economical way by a supplier.
-
-
- Hierarchical representations of project aspects into smaller components providing the necessary frameworks to accomplish the project objectives and create the required deliverables.
-
-
- Risks and opportunities that arise from any stakeholder. Can originate from any life cycle process.
-
-
- Items for configuration control. Can originate from any life cycle process.
-
-
- Items for information control. Can originate from any life cycle process.
-
-
- Configuration information formally designated at a specific time during the life of a product, product component, service, or service component. (Adapted from ISO/IEC/IEEE 24765, 2017).
-
-
- Approaches, schedules, resources, and specific considerations required to perform configuration management.
-
-
- System used to support and enable configuration management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the configuration management activities.
-
-
- Provides results of configuration management verifications and audits to ensure adequate traceability, control, and visibility. It includes evaluation criteria.
-
-
- Permanent, readable form of data, information, or knowledge related to configuration management.
-
-
- Decisions that arise from any stakeholder. Can originate from any life cycle process.
-
-
- A repository that supports the availability for use and communication of all relevant decision information in a timely, complete, valid, and, if required, confidential manner.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the decision management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform decision management.
-
-
- Permanent, readable form of data++ information, or knowledge related to decision management.
-
-
- System (product or service) that has been deactivated, disassembled, and removed from operations and been properly disposed.
-
-
- Approaches, schedules, resources, and specific considerations required to perform information management.
-
-
- A repository that supports the availability for use and communication of all relevant project information artifacts in a timely, complete, valid, and, if required, restricted manner.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the information management activities.
-
-
- Permanent, readable form of data, information, or knowledge related to information management.
-
-
- Measurement needs from all applicable life cycle processes, including: critical performance measurement needs, organizational measurement needs, and project measurement needs.
-
-
- Measurement data from all applicable life cycle processes, including: critical performance measurement data, organizational measurement data, and project measurement data.
-
-
- Approaches, schedules, resources, and specific considerations required to perform measurement.
-
-
- A repository that supports the availability for use and communication of all relevant measures in a timely, complete, valid, and, if required, confidential manner.
-
-
- An account prepared for interested parties in order to communicate the status, results++ and outcomes of the measurement activities.
-
-
- Permanent, readable form of data++ information, or knowledge related to measurement.
-
-
- Approaches, schedules, resources, and specific considerations required to perform project assessment and control.
-
-
- Permanent, readable form of data, information++ or knowledge related to project assessment and control.
-
-
- Request from the project to the organization to authorize the project.
-
-
- Estimate of the costs associated with a particular project. Includes labor, infrastructure, acquisition, and enabling system costs along with reserves for risk management.
-
-
- Externally imposed limitation on the project developing or modifying a system. (ISO/IEC/IEEE 29148, 2018)
-
-
- Project directives based on action required due to deviations from the project plan. If assessments are associated with a decision gate, a decision to proceed or not to proceed, is taken.
-
-
- Decision gate and review artifacts that are expected through conduct of the decision gate or technical review and that can be considered elements of exit criteria. (Adapted from ISO/IEC/IEEE 24748–8, 2019)
-
-
- Project-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
-
-
- Identified human resource needs of the project. Project infrastructure Resources, facilities, personnel, and/or services that support the project.
-
-
- Identified infrastructure needs of the project.
-
-
- Identified information needs of the decision makers with respect to project expectations. Project objectives The objectives or goals for the project.
-
-
- Data provided for the identified project measurement needs.
-
-
- Identified information needs of the decision makers with respect to project expectations. Project objectives The objectives or goals for the project.
-
-
- Permanent, readable form of data, information, or knowledge related to project planning.
-
-
- Procedures from all applicable life cycle processes, including:
-
-integration procedure,
-
-verification procedure,
-
-installation procedure,
-
-validation procedure,
-
-operation procedure,
-
-maintenance and logistics procedure, and
-
-disposal procedure.
-
-
- Reports from all applicable project life cycle processes, including:
-
-acquisition report
-
-supply report,
-
-decision management report,
-
-risk management report,
-
-configuration management report,
-
-configuration verification and audit report,
-
-information management report,
-
-measurement report,
-
-quality assurance report,
-
-quality assurance evaluation report,
-
-business or mission analysis report,
-
-stakeholder needs and requirements
-
-definition report,
-
-system requirements definition report,
-
-system architecture definition report,
-
-system architecture assessment report,
-
-design definition report,
-
-system design assessment report,
-
-system analysis report,
-
-implementation report,
-
-integration report,
-
-verification report,
-
-transition report,
-
-validation report,
-
-operation report
-
-maintenance and logistics report, and
-
-disposal report.
-
-
- A linked list of a project milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
-
-
- A linked list of a project’s milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
-
-
- Strategies/approaches for all applicable project life processes, including:
-
-acquisition strategy/approach,
-
-supply strategy & approach,
-
-project assessment and control strategy/approach,
-
-decision management strategy/approach,
-
-risk management strategy/approach,
-
-configuration management strategy/approach,
-
-information management strategy/approach,
-
-measurement strategy/approach,
-
-quality assurance strategy/approach,
-
-business or mission analysis strategy/approach,
-
-stakeholder needs and requirements definition strategy/approach,
-
-system requirements definition strategy/approach,
-
-system architecture definition strategy/approach,
-
-design definition strategy/approach,
-
-system analysis strategy/approach,
-
-implementation strategy/approach,
-
-integration strategy/approach,
-
-verification strategy/approach,
-
-transition strategy/approach,
-
-validation strategy/approach,
-
-operation strategy/approach,
-
-maintenance and logistics strategy/approach, and
-
-disposal strategy/approach.
-
-
- Action to eliminate the cause or reduce the likelihood of recurrence of a detected project nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1, 2017)
-
-
- Provides results of quality assurance evaluations. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Permanent, readable form of data, information, or knowledge related to quality assurance.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the quality assurance activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform quality assurance.
-
-
- System used to support and enable quality assurance.
-
-
- Approaches, schedules, resources, and specific considerations required to perform risk management.
-
-
- A repository that supports the availability for use and communication of all relevant risk information in a timely, complete, valid, and, if required, confidential manner.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the risk management activities.
-
-
- Permanent, readable form of data, information, or knowledge related to risk management.
-
-
- Presents how the project processes and activities are executed to assure the project’s successful completion, and the quality of the deliverable product or service. (Adapted from ISO/IEC/ IEEE 15289, 2019)
-
-
- A request to conduct a system analysis.
-
-
- Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017).
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.1.1] The purpose of the Life Cycle Model Management process is to define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures for use by the organization with respect to the scope of [ISO/IEC/IEEE 15288:2023]. See detailed description in the INCOSE Handbook v.5, page 51
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.2.1] The purpose of the Infrastructure Management process is to provide the infrastructure and services to projects to support organization and project objectives throughout the life cycle. See detailed description in the INCOSE Handbook v.5, page 54
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.3.1] The purpose of the Portfolio Management process is to initiate and sustain necessary, sufficient and suitable projects in order to meet the strategic objectives of the organization. See detailed description in the INCOSE Handbook v.5, page 57
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.4.1] The purpose of the Human Resource Management process is to provide the organization with necessary human resources and to maintain their competencies, consistent with business needs. See detailed description in the INCOSE Handbook v.5, page 60
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.5.1] The purpose of the Quality Management process is to assure that products, services and implementations of the quality management process meet organizational and project quality objectives and achieve customer satisfaction. See detailed description in the INCOSE Handbook v.5, page 63
-
-
-
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.2.6.1] The purpose of the Knowledge Management process is to create the capability and assets that enable the organization to exploit opportunities to re-�apply existing knowledge. See detailed description in the INCOSE Handbook v.5, page 67
-
-
-
-
-
-
- Permanent, readable form of data, information, or knowledge related to human resource management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the human resource management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform human resource management.
-
-
- Permanent, readable form of data, information, or knowledge related to infrastructure management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the infrastructure management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform infrastructure management.
-
-
- Permanent, readable form of data, information, or knowledge related to knowledge management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the knowledge management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform knowledge management.
-
-
- System used to support and enable knowledge management.
-
-
- Permanent, readable form of data, information, or knowledge related to life cycle model management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the life cycle model management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform life cycle model management. (--> required for LCMM itself))
-
-
- Framework of processes and activities concerned with the life cycle that can be organized into stages, acting as a common reference for communication and understanding. (ISO/IEC/IEEE 15288, 2023)
-
-
- Resources, facilities, personnel, and/or services that support the organization.
-
-
- Identified organizational infrastructure needs.
-
-
- Organizational-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
-
-
- High-level direction at the organizational level consistent with the organization's strategies. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Presents an ordered series of steps to perform a process, activity, or task for an organization. (Adapted from ISO/IEC/IEEE 15289++ 2019)
-
-
- Set of interrelated or interacting activities that transform inputs into outputs for an organization. (Adapted from ISO/IEC/IEEE 15288, 2023)
-
-
- Data provided for the identified organizational measurement needs.
-
-
- Identified information needs of the decision makers with respect to organizational expectations.
-
-
- Permanent, readable form of data, information, or knowledge related to portfolio management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the portfolio management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform portfolio management.
-
-
- Authorization from the organization to proceed per the agreed-to project plan.
-
-
- Organizational direction to the project. Includes sustainment of projects meeting objectives and redirection or termination of projects not meeting objectives.
-
-
- Identified human resource needs of the project. Project infrastructure Resources, facilities, personnel, and/or services that support the project.
-
-
- Collection of projects that addresses the strategic objectives of the organization. (ISO/IEC/IEEE 12207, 2017)
-
-
- Individuals equipped to perform duties on behalf of the organization, including officers, employees, and contractors. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
- Action to eliminate the cause or reduce the likelihood of recurrence of a detected organizational nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1++ 2017)
-
-
- Rules on which a judgment or decision can be based, or by which an organization can be evaluated. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Provides results of quality management evaluations. It includes evaluation criteria. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Permanent, readable form of data, information, or knowledge related to quality management.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the quality management activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform quality management.
-
-
- System used to support and enable quality management.
-
-
- Records from all applicable life cycle processes, including:
-
-acquisition records/artifacts,
-
-supply records/artifacts,
-
-life cycle model management records/artifacts,
-
-infrastructure management records/artifacts,
-
-portfolio management records/artifacts,
-
-human resource management records/artifacts,
-
-quality management records/artifacts,
-
-knowledge management records/artifacts,
-
-project planning records/artifacts,
-
-project assessment and control records/artifacts,
-
-decision management records/artifacts,
-
-risk management records/artifacts,
-
-configuration management records/artifacts,
-
-information management records/artifacts,
-
-measurement records/artifacts,
-
-quality assurance records/artifacts,
-
-business or mission analysis records/artifacts,
-
-stakeholder needs and requirements definition records/artifacts,
-
-system requirements definition records/artifacts,
-
-system architecture definition records/artifacts,
-
-design definition records/artifacts,
-
-system analysis records/artifacts,
-
-implementation records/artifacts,
-
-integration records/artifacts,
-
-verification records/artifacts,
-
-transition records/artifacts,
-
-validation records/artifacts,
-
-operation records/artifacts,
-
-maintenance and logistics records/artifacts,
-
-disposal records/artifacts,
-
-tailoring records/artifacts.
-
-
- System or system element (product or service) reused by an organization consistent with ist system element requirements.
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.1.1.1] The purpose of the Acquisition process is to obtain a product or service in accordance with the acquirer's requirements. See detailed description in the INCOSE Handbook v.5, page 45
-
-
- See detailed description in the INCOSE Handbook v.5, page 140
-
-
- See detailed description in the INCOSE Handbook v.5, page 141
-
-
- See detailed description in the INCOSE Handbook v.5, page 141
-
-
- See detailed description in the INCOSE Handbook v.5, page 141
-
-
- See detailed description in the INCOSE Handbook v.5, page 142
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [6.1.2.1] The purpose of the Supply process is to provide an acquirer with a product or service that meets agreed requirements. See detailed description in the INCOSE Handbook v.5, page 48
-
-
- See detailed description in the INCOSE Handbook v.5, page 49
-
-
- See detailed description in the INCOSE Handbook v.5, page 49
-
-
- See detailed description in the INCOSE Handbook v.5, page 49
-
-
- See detailed description in the INCOSE Handbook v.5, page 49
-
-
- See detailed description in the INCOSE Handbook v.5, page 49
-
-
- System or system element (product or service) accepted by an acquirer from a supplier consistent with the delivery conditions of the supply agreement.
-
-
- System or system element (product or service) delivered to the acquirer from a supplier consistent with the delivery conditions of the acquisition agreement.
-
-
- Mutual acknowledgment of terms and conditions under which a working relationship is conducted between an acquirer and a supplier. (Adapted from ISO/IEC/IEEE 15288, 2023).
-
-
- Payments or other compensations for an acquired system.
-
-
- Permanent, readable form of data, information, or knowledge related to acquisition.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the acquisition activities.
-
-
- Approaches, schedules, resources, and specific considerations required to perform acquisition.
-
-
- Acquirer’s request for information and commitments needed from the supplier that are required to be included in the potential supplier’s proposal. It announces the acquirer’s intention to potential bidders to acquire a specified system or system element (product or service). (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- System or system element (product or service) delivered from a supplier to an acquirer consistent with the delivery conditions of the supply agreement.
-
-
- Mutual acknowledgment of terms and conditions under which a working relationship is conducted between a supplier and an acquirer. (Adapted from ISO/IEC/IEEE 15288++ 2023)
-
-
- Permanent, readable form of data, information, or knowledge related to supply.
-
-
- An account prepared for interested parties in order to communicate the status, results, and outcomes of the supply activities.
-
-
- Prepared by a potential supplier to support the offer of a contract bid, including cost, schedule, risk statements, methodology to satisfy the request for supply, experiences and capabilities, any recommendations to tailor the request for supply or contract, and the signature of the supplier's approving authority. Informally, may be prepared within an organization. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
- Approaches, schedules, resources, and specific considerations required to perform supply.
-
-
- Request, temporary or permanent, to accept a configuration item or other designated item which, during production or after having been submitted for inspection, is found to depart from specified requirements, but is nevertheless considered suitable for use as is or after rework by an approved method. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
- As stated in ISO/IEC/IEEE 15288:2023, [Annex A.2.1] The purpose of the tailoring process is to adapt the life cycle processes included in this document [i.e. ISO/IEC/IEEE 15288:2023] to satisfy particular circumstances or factors that:
-
-a) surround an organization that is employing ISO/IEC/IEEE 15288 in an agreement;
-
-b) influence a project that is required to meet an agreement in which ISO/IEC/IEEE 15288 is referenced;
-
-c) reflect the needs of an organization in order to supply products or services.
-
-See detailed description in the INCOSE Handbook v.5, page 215
-
-
-
-
-
-
-
- Organization specific strategy and approach to tailoring required to incorporate new or updated external standards.
-
-
- Project specific strategy and approach to tailoring required to incorporate new or updated life cycle models.
-
-
- Permanent, readable form of data, information, or knowledge related to tailoring.
-
-
- Agreements from all applicable life cycle processes, including: acquisition agreement and supply agreement.
-
-
- External represents those typical inputs and outputs that come from, or go to, beyond the set of system life cycle processes (i.e., they do not come from, or go to, another system life cycle process).
-
-Note that these can be either
-
-internal (e.g., Organization strategic plan) or
-
-external (e.g., Applicable laws and regulations) to the organization.
-
-
- The overall organization strategy, including the business mission or vision and strategic goals and objectives.
-
-
- International, national, or local laws or regulations.
-
-
- This handbook and relevant industry, country, military, acquirer, and other specifications and standards. Includes new knowledge from industry sponsored knowledge networks.
-
-
- External systems that facilitate the life cycle activities of the SoI but are not a direct element of the operational environment.
-
-
- Payments or other compensations for the supplied system.
-
-
- External documents relevant to the particular stage of the system of interest.
-
-
- At the organization level, addresses the leadership's intended way of operating the organization (ISO/IEC/IEEE 29148, 2018).
-
-
- Organization direction and constraints related to the project portfolio.
-
-
- The overall organization business plan, including the business objectives.
-
-
- Responses to customer satisfaction surveys or other instruments.
-
-
- Reports from all applicable organization life cycle processes, including: life cycle model management report, infrastructure management report, portfolio management report, human resource management report, quality management report, and knowledge management report. (INCOSE Handbook v.5, p. 327)
-
-
- This process represents a class to which every other system life cycle process belongs. Every other life cycle proccess inherits relationships to inputs and outputs of this process.
-Rationale: p. 42 (controls, enablers), pp. 317, 318 (situational) of INCOSE Handbook v. 5.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/README.md b/README.md
deleted file mode 100644
index 26a13ffbf72bc7914bce97e6d3b83e567a3ce795..0000000000000000000000000000000000000000
--- a/README.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: TestSEHTML
-emoji: 📊
-colorFrom: red
-colorTo: pink
-sdk: static
-pinned: false
----
-
-Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference
diff --git a/css/i18n.css b/css/i18n.css
deleted file mode 100644
index 7b482f6c4f2363d26a99a377d5ad774d57508e11..0000000000000000000000000000000000000000
--- a/css/i18n.css
+++ /dev/null
@@ -1 +0,0 @@
-@import url('i18n/en.css');
diff --git a/css/i18n/en.css b/css/i18n/en.css
deleted file mode 100644
index 82c77edcd3a4bacbbf69193f6dfc1343a35ea12b..0000000000000000000000000000000000000000
--- a/css/i18n/en.css
+++ /dev/null
@@ -1,164 +0,0 @@
-/* View pages */
-:lang(en) .i18n-content:after {content: "Content"}
-:lang(en) .i18n-documentation:after {content: "Documentation"}
-:lang(en) .i18n-purpose:after {content: "Purpose"}
-:lang(en) .i18n-properties:after {content: "Properties"}
-:lang(en) .i18n-analysis:after {content: "Analysis"}
-:lang(en) .i18n-used-in-views:after {content: "Used in Views"}
-:lang(en) .i18n-model-relations:after {content: "Model Relations"}
-:lang(en) .i18n-elements:after {content: "Elements"}
-:lang(en) .i18n-relationships:after {content: "Relationships"}
-:lang(en) .i18n-key:after {content: "Key"}
-:lang(en) .i18n-value:after {content: "Value"}
-:lang(en) .i18n-name:after {content: "Name"}
-:lang(en) .i18n-type:after {content: "Type"}
-:lang(en) .i18n-source:after {content: "Source"}
-:lang(en) .i18n-target:after {content: "Target"}
-:lang(en) .i18n-query:after {content: "Query"}
-
-/* element panel */
-:lang(en) .i18n-empty_element_message:after {content: "Select an element in the model tree or in a view to show its details here"}
-:lang(en) .i18n-relation-source:after {content: "Source:"}
-:lang(en) .i18n-relation-target:after {content: "Target:"}
-:lang(en) .i18n-specialization:after {content: "Specialization:"}
-
-/* ViewPoints (com.archimatetool.editor.model.viewpoints.IViewpoint) */
-:lang(en) .i18n-viewpoint:after {content: "Viewpoint"}
-:lang(en) .i18n-viewpoint-:after {content: "No Viewpoint"}
-:lang(en) .i18n-viewpoint-application_cooperation:after {content: "Application Cooperation"}
-:lang(en) .i18n-viewpoint-application_usage:after {content: "Application Usage"}
-:lang(en) .i18n-viewpoint-application_structure:after {content: "Application Structure"}
-:lang(en) .i18n-viewpoint-business_process_cooperation:after {content: "Business Process Cooperation"}
-:lang(en) .i18n-viewpoint-capability:after {content: "Capability"}
-:lang(en) .i18n-viewpoint-goal_realization:after {content: "Goal Realization"}
-:lang(en) .i18n-viewpoint-implementation_deployment:after {content: "Implementation and Deployment"}
-:lang(en) .i18n-viewpoint-implementation_migration:after {content: "Implementation and Migration"}
-:lang(en) .i18n-viewpoint-information_structure:after {content: "Information Structure"}
-:lang(en) .i18n-viewpoint-layered:after {content: "Layered"}
-:lang(en) .i18n-viewpoint-migration:after {content: "Migration"}
-:lang(en) .i18n-viewpoint-motivation:after {content: "Motivation"}
-:lang(en) .i18n-viewpoint-organization:after {content: "Organization"}
-:lang(en) .i18n-viewpoint-outcome_realization:after {content: "Outcome Realization"}
-:lang(en) .i18n-viewpoint-physical:after {content: "Physical"}
-:lang(en) .i18n-viewpoint-product:after {content: "Product"}
-:lang(en) .i18n-viewpoint-project:after {content: "Project"}
-:lang(en) .i18n-viewpoint-requirements_realization:after {content: "Requirements Realization"}
-:lang(en) .i18n-viewpoint-resource:after {content: "Resource"}
-:lang(en) .i18n-viewpoint-service_realization:after {content: "Service Realization"}
-:lang(en) .i18n-viewpoint-stakeholder:after {content: "Stakeholder"}
-:lang(en) .i18n-viewpoint-strategy:after {content: "Strategy"}
-:lang(en) .i18n-viewpoint-technology:after {content: "Technology"}
-:lang(en) .i18n-viewpoint-technology_usage:after {content: "Technology Usage"}
-:lang(en) .i18n-viewpoint-value_stream:after {content: "Value Stream"}
-
-
-/* Elements (Class.SimpleName from com.archimatetool.model) */
-:lang(en) .i18n-elementtype-ArchimateModel:before {content: "Model"}
-:lang(en) .i18n-elementtype-AccessRelationship:before {content: "Access"}
-:lang(en) .i18n-elementtype-AggregationRelationship:before {content: "Aggregation"}
-:lang(en) .i18n-elementtype-ApplicationCollaboration:before {content: "Application Collaboration"}
-:lang(en) .i18n-elementtype-ApplicationComponent:before {content: "Application Component"}
-:lang(en) .i18n-elementtype-ApplicationEvent:before {content: "Application Event"}
-:lang(en) .i18n-elementtype-ApplicationFunction:before {content: "Application Function"}
-:lang(en) .i18n-elementtype-ApplicationInteraction:before {content: "Application Interaction"}
-:lang(en) .i18n-elementtype-ApplicationInterface:before {content: "Application Interface"}
-:lang(en) .i18n-elementtype-ApplicationProcess:before {content: "Application Process"}
-:lang(en) .i18n-elementtype-ApplicationService:before {content: "Application Service"}
-:lang(en) .i18n-elementtype-Artifact:before {content: "Artifact"}
-:lang(en) .i18n-elementtype-Assessment:before {content: "Assessment"}
-:lang(en) .i18n-elementtype-AssignmentRelationship:before {content: "Assignment"}
-:lang(en) .i18n-elementtype-AssociationRelationship:before {content: "Association"}
-:lang(en) .i18n-elementtype-BusinessActor:before {content: "Business Actor"}
-:lang(en) .i18n-elementtype-BusinessCollaboration:before {content: "Business Collaboration"}
-:lang(en) .i18n-elementtype-BusinessEvent:before {content: "Business Event"}
-:lang(en) .i18n-elementtype-BusinessFunction:before {content: "Business Function"}
-:lang(en) .i18n-elementtype-BusinessInteraction:before {content: "Business Interaction"}
-:lang(en) .i18n-elementtype-BusinessInterface:before {content: "Business Interface"}
-:lang(en) .i18n-elementtype-BusinessObject:before {content: "Business Object"}
-:lang(en) .i18n-elementtype-BusinessProcess:before {content: "Business Process"}
-:lang(en) .i18n-elementtype-BusinessRole:before {content: "Business Role"}
-:lang(en) .i18n-elementtype-BusinessService:before {content: "Business Service"}
-:lang(en) .i18n-elementtype-Capability:before {content: "Capability"}
-:lang(en) .i18n-elementtype-CommunicationNetwork:before {content: "Communication Network"}
-:lang(en) .i18n-elementtype-CompositionRelationship:before {content: "Composition"}
-:lang(en) .i18n-elementtype-Constraint:before {content: "Constraint"}
-:lang(en) .i18n-elementtype-CourseOfAction:before {content: "Course of Action"}
-:lang(en) .i18n-elementtype-Contract:before {content: "Contract"}
-:lang(en) .i18n-elementtype-DataObject:before {content: "Data Object"}
-:lang(en) .i18n-elementtype-Deliverable:before {content: "Deliverable"}
-:lang(en) .i18n-elementtype-Device:before {content: "Device"}
-:lang(en) .i18n-elementtype-DistributionNetwork:before {content: "Distribution Network"}
-:lang(en) .i18n-elementtype-Driver:before {content: "Driver"}
-:lang(en) .i18n-elementtype-Equipment:before {content: "Equipment"}
-:lang(en) .i18n-elementtype-Facility:before {content: "Facility"}
-:lang(en) .i18n-elementtype-FlowRelationship:before {content: "Flow"}
-:lang(en) .i18n-elementtype-Gap:before {content: "Gap"}
-:lang(en) .i18n-elementtype-Goal:before {content: "Goal"}
-:lang(en) .i18n-elementtype-Grouping:before {content: "Grouping"}
-:lang(en) .i18n-elementtype-ImplementationEvent:before {content: "Implementation Event"}
-:lang(en) .i18n-elementtype-InfluenceRelationship:before {content: "Influence"}
-:lang(en) .i18n-elementtype-Junction:before {content: "Junction"}
-:lang(en) .i18n-elementtype-Location:before {content: "Location"}
-:lang(en) .i18n-elementtype-Material:before {content: "Material"}
-:lang(en) .i18n-elementtype-Meaning:before {content: "Meaning"}
-:lang(en) .i18n-elementtype-Node:before {content: "Node"}
-:lang(en) .i18n-elementtype-Outcome:before {content: "Outcome"}
-:lang(en) .i18n-elementtype-Path:before {content: "Path"}
-:lang(en) .i18n-elementtype-Plateau:before {content: "Plateau"}
-:lang(en) .i18n-elementtype-Principle:before {content: "Principle"}
-:lang(en) .i18n-elementtype-Product:before {content: "Product"}
-:lang(en) .i18n-elementtype-RealizationRelationship:before {content: "Realization"}
-:lang(en) .i18n-elementtype-Representation:before {content: "Representation"}
-:lang(en) .i18n-elementtype-Requirement:before {content: "Requirement"}
-:lang(en) .i18n-elementtype-Resource:before {content: "Resource"}
-:lang(en) .i18n-elementtype-ServingRelationship:before {content: "Serving"}
-:lang(en) .i18n-elementtype-SpecializationRelationship:before {content: "Specialization"}
-:lang(en) .i18n-elementtype-Stakeholder:before {content: "Stakeholder"}
-:lang(en) .i18n-elementtype-SystemSoftware:before {content: "System Software"}
-:lang(en) .i18n-elementtype-TechnologyCollaboration:before {content: "Technology Collaboration"}
-:lang(en) .i18n-elementtype-TechnologyEvent:before {content: "Technology Event"}
-:lang(en) .i18n-elementtype-TechnologyFunction:before {content: "Technology Function"}
-:lang(en) .i18n-elementtype-TechnologyInteraction:before {content: "Technology Interaction"}
-:lang(en) .i18n-elementtype-TechnologyInterface:before {content: "Technology Interface"}
-:lang(en) .i18n-elementtype-TechnologyObject:before {content: "Technology Object"}
-:lang(en) .i18n-elementtype-TechnologyProcess:before {content: "Technology Process"}
-:lang(en) .i18n-elementtype-TechnologyService:before {content: "Technology Service"}
-:lang(en) .i18n-elementtype-TriggeringRelationship:before {content: "Triggering"}
-:lang(en) .i18n-elementtype-Value:before {content: "Value"}
-:lang(en) .i18n-elementtype-ValueStream:before {content: "Value Stream"}
-:lang(en) .i18n-elementtype-WorkPackage:before {content: "Work Package"}
-
-/* Other Graphical Objects */
-:lang(en) .i18n-elementtype-DiagramModelGroup:after {content: "Group"}
-:lang(en) .i18n-elementtype-DiagramModelNote:after {content: "Note"}
-:lang(en) .i18n-elementtype-SketchModel:after {content: "Sketch"}
-:lang(en) .i18n-elementtype-SketchModelActor:after {content: "Actor"}
-:lang(en) .i18n-elementtype-SketchModelSticky:after {content: "Sticky"}
-:lang(en) .i18n-elementtype-CanvasModel:after {content: "Canvas"}
-:lang(en) .i18n-elementtype-CanvasModelBlock:after {content: "Block"}
-:lang(en) .i18n-elementtype-CanvasModelSticky:after {content: "Sticky"}
-:lang(en) .i18n-elementtype-CanvasModelImage:after {content: "Image"}
-
-
-/* Model Tree */
-:lang(en) .i18n-modeltree:after {content: "Model Tree"}
-:lang(en) .i18n-model_content:after {content: "Model Content"}
-:lang(en) .i18n-strategy:after {content: "Strategy"}
-:lang(en) .i18n-business_layer:after {content: "Business"}
-:lang(en) .i18n-application_layer:after {content: "Application"}
-:lang(en) .i18n-technology_layer:after {content: "Technology & Physical"}
-:lang(en) .i18n-motivation:after {content: "Motivation"}
-:lang(en) .i18n-implementation:after {content: "Implementation & Migration"}
-:lang(en) .i18n-connectors:after {content: "Other"}
-:lang(en) .i18n-relations:after {content: "Relations"}
-:lang(en) .i18n-views:after {content: "Views"}
-
-/* Modal Dialogs */
-:lang(en) .i18n-hint:after {content: "Hint"}
-:lang(en) .i18n-close:after {content: "Close"}
-:lang(en) .i18n-about:after {content: "About"}
-:lang(en) .i18n-about-pluginname:after {content: "Archi HTML Report plugin"}
-:lang(en) .i18n-about-pluginversion:after {content: "Version 1.3.1"}
-:lang(en) .i18n-about-plugintext1:after {content: "This plugin has been developed by Jean-Baptiste Sarrodie, Quentin Varquet and Phil Beauvoir."}
-:lang(en) .i18n-about-plugintext2:after {content: "This document has been created using Archi®. Archi® is a free, open source, cross-platform tool to create ArchiMate models and is targeted toward all levels of Enterprise Architects and Modellers. It provides a low cost to entry solution to users who may be making their first steps in the ArchiMate modelling language, or who are looking for a free, cross-platform ArchiMate modelling tool for their company or institution and wish to engage with the language within a TOGAF® or other Enterprise Architecture framework."}
-:lang(en) .i18n-about-plugintext3:after {content: "is a registered trademark of Phillip Beauvoir."}
diff --git a/css/model.css b/css/model.css
deleted file mode 100644
index 7e916c7e6fd6d6b66d4e8e3f89d3df62563f5f00..0000000000000000000000000000000000000000
--- a/css/model.css
+++ /dev/null
@@ -1,229 +0,0 @@
-/* Setup html pages */
-html {
- height: 100%; /* Needed for 'empty-element.html' */
-}
-
-html.model > body {
- background:#ddd;
- padding: 0;
-}
-
-html.frame > body {
- height: 100%;
- background:#ddd;
- /* padding: 15px; */
-}
-
-/* ModelTree */
-ul, li {
- list-style-type: none;
- cursor: default;
-}
-li.tree-element, ul{
- padding-left: 15px;
-}
-
-/* jQuery UI Layout style */
-.ui-layout-pane {
- padding: 0px;
- overflow: hidden;
- border: 0px solid #ddd;
- background: #ddd;
-}
-.ui-layout-resizer {
- border: 2px solid #ddd;
-}
-
-/* Force panels width/height */
-.root-panel {
- height: 100%;
- overflow: hidden;
- background: #FFF;
-}
-.root-panel-body {
- /* height will be set though jQuery */
- overflow: auto;
-}
-.no-padding {
- padding: 0px;
-}
-.no-margin {
- margin: 0px;
-}
-.documentation {
- padding-top: 15px;
- padding-bottom: 15px;
-}
-.navbar {
- height: 100%;
-}
-
-/* iFrames are inside panel-body */
-iframe {
- margin: 0px;
- padding: 0px;
- border: none;
- width: 100%;
- height: 100%;
-}
-
-p.centered {
- position: relative;
- top: 50%;
- transform: translateY(-50%);
- text-align: center;
-}
-
-.table-condensed th,td {
- font-size: 14px;
-}
-
-img.diagram {
- max-width: 100%;
-}
-
-xmp {
- font-family: "Helvetica Neue",Helvetica,Arial,sans-serif;
-}
-
-/* Alasql console */
-#myconsole td {
- white-space: pre-wrap;
-}
-
-/* Changing Navbar color can be done by uncommenting and adapting what follows */
-/*
-.navbar {
- background-color: #017a54;
-}
-
-.navbar .navbar-nav>li>a:hover {
- background-color: rgb(255 255 255 / 20%);
-}
-
-.navbar .navbar-nav>li>a:focus {
- background-color: rgb(255 255 255 / 0%);
-}
-*/
-
-/* Image Zoom Slider */
-.root-panel-heading {
- position: relative;
-}
-
-#btnZoomIn, #btnZoomOut {
- cursor: pointer;
- padding: 0;
-}
-
-#zoomSlider {
- width: 150px;
- position: absolute;
- top: 50% !important;
- right: 0;
- transform: translateY(-50%);
-}
-
-#zoomRange {
- padding: 0;
-}
-
-/* Internet Explorer input range theming thanks to https://brennaobrien.com/blog/2014/05/style-input-type-range-in-every-browser.html */
-input[type=range]::-ms-track {
- width: 300px;
- height: 5px;
-
- /*remove bg colour from the track, we'll use ms-fill-lower and ms-fill-upper instead */
- background: transparent;
-
- /*leave room for the larger thumb to overflow with a transparent border */
- border-color: transparent;
- border-width: 6px 0;
-
- /*remove default tick marks*/
- color: transparent;
-}
-input[type=range]::-ms-fill-lower {
- background: #777;
- border-radius: 10px;
-}
-input[type=range]::-ms-fill-upper {
- background: #ddd;
- border-radius: 10px;
-}
-input[type=range]::-ms-thumb {
- border: none;
- height: 16px;
- width: 16px;
- border-radius: 50%;
- background: #767676;
-}
-input[type=range]:focus::-ms-fill-lower {
- background: #888;
-}
-input[type=range]:focus::-ms-fill-upper {
- background: #ccc;
-}
-
-
-/* Firefox input range theming thanks to https://brennaobrien.com/blog/2014/05/style-input-type-range-in-every-browser.html */
-input[type=range]{
- background: transparent;
-}
-
-input[type=range]::-moz-range-track {
- /*width: 300px;*/
- height: 5px;
- background: #ddd;
- border: none;
- border-radius: 3px;
-}
-
-input[type=range]::-moz-range-thumb {
- border: none;
- height: 16px;
- width: 16px;
- border-radius: 50%;
- background: #767676;
-}
-
-
-/* Search Box */
-#tree-search {
- width: 5px;
- box-sizing: border-box;
- border: transparent;
- border-radius: 20px;
- background-color: transparent;
- background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAMAAABg3Am1AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAADNQTFRFU1NT9fX1lJSUXl5e1dXVfn5+c3Nz6urqv7+/tLS0iYmJqampn5+fysrK39/faWlp////Vi4ZywAAABF0Uk5T/////////////////////wAlrZliAAABLklEQVR42rSWWRbDIAhFHeOUtN3/ags1zaA4cHrKZ8JFRHwoXkwTvwGP1Qo0bYObAPwiLmbNAHBWFBZlD9j0JxflDViIObNHG/Do8PRHTJk0TezAhv7qloK0JJEBh+F8+U/hopIELOWfiZUCDOZD1RADOQKA75oq4cvVkcT+OdHnqqpQCITWAjnWVgGQUWz12lJuGwGoaWgBKzRVBcCypgUkOAoWgBX/L0CmxN40u6xwcIJ1cOzWYDffp3axsQOyvdkXiH9FKRFwPRHYZUaXMgPLeiW7QhbDRciyLXJaKheCuLbiVoqx1DVRyH26yb0hsuoOFEPsoz+BVE0MRlZNjGZcRQyHYkmMp2hBTIzdkzCTc/pLqOnBrk7/yZdAOq/q5NPBH1f7x7fGP4C3AAMAQrhzX9zhcGsAAAAASUVORK5CYII=);
- background-size: 20px;
- background-position: right 5px center;
- background-repeat: no-repeat;
- padding: 5px 15px 5px 15px;
- cursor: pointer;
-}
-
-#tree-search:focus {
- width: 100%;
- cursor: auto;
- background-color: #FFF !important;
- border: 1px solid #ddd;
- border-radius: 2px;
-}
-
-#tree-search.filtered {
- background-color: #ddd;
-}
-
-/* To remove cross symbol in input field */
-#tree-search::-ms-clear {
- display: none;
-}
-
-#searchBox {
- position: absolute;
- top: 50% !important;
- right: 0;
- transform: translateY(-50%);
- padding-right: 5px;
-}
diff --git a/elements/empty-element.html b/elements/empty-element.html
deleted file mode 100644
index b38a7fe3425d26be558cc493ea94272c869860f0..0000000000000000000000000000000000000000
--- a/elements/empty-element.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
The Access Relationship represents the ability of behavior and active structure elements to observe or act upon passive structure elements.
-
-
Category:
-
Dependency.
-
-
Examples:
-
Create a new object, Read data from an object, Write or modify object data, Delete an object.
- The “Create Invoice” sub-process writes/creates the “Invoice” business object; the “Send Invoice” sub-process reads that object
-
-
-
\ No newline at end of file
diff --git a/hints/aggregation.html b/hints/aggregation.html
deleted file mode 100644
index 1249959f4481cc1a281f855db99ae4d0dad0c510..0000000000000000000000000000000000000000
--- a/hints/aggregation.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Aggregation Relationship
-
-
-
-
The Aggregation Relationship represents that an element combines one or more other concepts.
-
-
Category:
-
Structural.
-
-
Examples:
-
A Car Insurance Business Product aggregates a Business Contract and some Business Services. "Customer File" aggregates an "Insurance Policy" and "Insurance Claim".
-
-
\ No newline at end of file
diff --git a/hints/application_collaboration.html b/hints/application_collaboration.html
deleted file mode 100644
index e83669bbb005b0bc3d346e776b02a7297f4eec03..0000000000000000000000000000000000000000
--- a/hints/application_collaboration.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Collaboration
-
-
-
-
An Application Collaboration represents an aggregate of two or more application internal active structure elements that work together to perform collective application behavior.
-
-
Category:
-
Application. Active Structure.
-
-
Examples:
-
Two Application Components collaborate in transaction administration: an Accounting component and a Billing component. This collaboration performs the task "Administrate transactions".
-
-
\ No newline at end of file
diff --git a/hints/application_component.html b/hints/application_component.html
deleted file mode 100644
index 80136c063ae9e03e6ef2fec3108e9762d2310df7..0000000000000000000000000000000000000000
--- a/hints/application_component.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Component
-
-
-
-
An Application Component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
-
-
Category:
-
Application. Active Structure.
-
-
Examples:
-
CRM System, Web portal, Financial Application, Customer Data Access.
-
-
\ No newline at end of file
diff --git a/hints/application_event.html b/hints/application_event.html
deleted file mode 100644
index 866f15333f522e3f71b336655cf53e8fe218a7e8..0000000000000000000000000000000000000000
--- a/hints/application_event.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Event
-
-
-
-
An Application Event represents an application state change.
-
-
Category:
-
Application. Behavioural.
-
-
Examples:
-
Claim received, Request for quotation.
-
-
\ No newline at end of file
diff --git a/hints/application_function.html b/hints/application_function.html
deleted file mode 100644
index fc7febfcebcccfafdf694b468a6ecdbc9e6352a8..0000000000000000000000000000000000000000
--- a/hints/application_function.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Function
-
-
-
-
An Application Function represents automated behavior that can be performed by an application component.
-
-
\ No newline at end of file
diff --git a/hints/application_interaction.html b/hints/application_interaction.html
deleted file mode 100644
index baa4f050cc5341c9bda817a555cb6891aff23587..0000000000000000000000000000000000000000
--- a/hints/application_interaction.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Application Interaction
-
-
-
-
-
An Application Interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components.
-
-
Category:
-
Application. Behavioural.
-
-
Examples:
-
Administrate transactions, Client profile creation, Update customer records
-
-
\ No newline at end of file
diff --git a/hints/application_interface.html b/hints/application_interface.html
deleted file mode 100644
index d9550e6d84ecda8db4818620ad7acc90837bf510..0000000000000000000000000000000000000000
--- a/hints/application_interface.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Interface
-
-
-
-
An Application Interface represents a point of access where application services are made available to a user, another application component, or a node.
-
-
Category:
-
Application. Active Structure.
-
-
Examples:
-
Transaction data exchange, Web services
-
-
\ No newline at end of file
diff --git a/hints/application_process.html b/hints/application_process.html
deleted file mode 100644
index 464e016a8d4c378b115d2527d108591b39730e07..0000000000000000000000000000000000000000
--- a/hints/application_process.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Process
-
-
-
-
An Application Process represents a sequence of application behaviors that achieves a specific result.
-
-
Category:
-
Application. Behavioural.
-
-
Examples:
-
Claims adjudication process, General ledger update job.
-
-
\ No newline at end of file
diff --git a/hints/application_service.html b/hints/application_service.html
deleted file mode 100644
index 94774fb5865e993b9ce497c4da2898235d6cc430..0000000000000000000000000000000000000000
--- a/hints/application_service.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Application Service
-
-
-
-
An Application Service represents an explicitly defined exposed application behavior.
-
-
\ No newline at end of file
diff --git a/hints/assignment.html b/hints/assignment.html
deleted file mode 100644
index 7f16fd81009a43e6c70ec4d9a8d5d283951a1b88..0000000000000000000000000000000000000000
--- a/hints/assignment.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Assignment Relationship
-
-
-
-
The Assignment Relationship represents the allocation of responsibility, performance of behavior, storage, or execution.
-
-
Category:
-
Structural.
-
-
Examples:
-
A Business Actor assigned to a Business Role. A Business Role assigned to a Business Process or Function. An Application Component assigned to an Application Function.
-
-
\ No newline at end of file
diff --git a/hints/association.html b/hints/association.html
deleted file mode 100644
index b319238c17ad5d19d992439ffd0d7e986548fea8..0000000000000000000000000000000000000000
--- a/hints/association.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Association Relationship
-
-
-
-
The Association Relationship represents an unspecified relationship, or one that is not represented by another ArchiMate relationship.
-
-
Category:
-
Dependency.
-
-
Examples:
-
Some Business Objects and a Business Contract are all associated with each other.
-
-
\ No newline at end of file
diff --git a/hints/business_actor.html b/hints/business_actor.html
deleted file mode 100644
index 13b641ba47306455c0743c43a1a5cacb9db11c84..0000000000000000000000000000000000000000
--- a/hints/business_actor.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Business Actor
-
-
-
-
A Business Actor represents a business entity that is capable of performing behavior.
-
-
Category:
-
Business. Active Structure.
-
-
Examples:
-
A Customer, Marketing & Communications department, Director of Finance, Secretary, Admissions Department, Product Development.
-
-
\ No newline at end of file
diff --git a/hints/business_collaboration.html b/hints/business_collaboration.html
deleted file mode 100644
index 3b2ea3e51e63930ca0cbe6afa04c2c099c283680..0000000000000000000000000000000000000000
--- a/hints/business_collaboration.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Business Collaboration
-
-
-
-
A Business Collaboration represents an aggregate of two or more business internal active structure elements that work together to perform collective behavior.
-
-
-
Category:
-
Business. Active Structure.
-
-
Examples:
-
The Business Roles of Sales Department and Advertising may form a temporary Business Collaboration in order to push a product to market. The Business Roles of Home Insurance Seller and Travel Insurance Seller may form a temporary Business Collaboration in order to form combined Insurance Selling service.
-
-
\ No newline at end of file
diff --git a/hints/business_event.html b/hints/business_event.html
deleted file mode 100644
index bfd0d905249a0cf87a4a65ec0505d1c9311b4c7e..0000000000000000000000000000000000000000
--- a/hints/business_event.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Business Event
-
-
-
-
A Business Event represents a business-related state change.
-
-
Category:
-
Business. Behavioural.
-
-
Examples:
-
Request for Insurance, Claim Received, Application Form Received, Send Product Portfolio.
-
-
\ No newline at end of file
diff --git a/hints/business_function.html b/hints/business_function.html
deleted file mode 100644
index b633f85f838b921a6613e438ebf14684afea9482..0000000000000000000000000000000000000000
--- a/hints/business_function.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Business Function
-
-
-
-
A Business Function represents a collection of business behavior based on a chosen set of criteria such as required business resources and/or competencies, and is managed or performed as a whole.
-
-
-
\ No newline at end of file
diff --git a/hints/business_interaction.html b/hints/business_interaction.html
deleted file mode 100644
index f02f96cf49b6c6be38188286ca1099d56886e235..0000000000000000000000000000000000000000
--- a/hints/business_interaction.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Business Interaction
-
-
-
-
A Business Interaction represents a unit of collective business behavior performed by (a collaboration of) two or more business actors, business roles, or business collaborations.
-
-
Category:
-
Business. Behavioural.
-
-
Examples:
-
Formalise Request, Check and Sign Contract, Take out Combined Insurance.
-
-
-
\ No newline at end of file
diff --git a/hints/business_interface.html b/hints/business_interface.html
deleted file mode 100644
index 338bf6e70601e0b4a1627391e24e5cbad225e440..0000000000000000000000000000000000000000
--- a/hints/business_interface.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Business Interface
-
-
-
-
A Business Interface represents a point of access where business services are made available to the environment.
-
-
Category:
-
Business. Active Structure.
-
-
Examples:
-
Telephone, Email, Call centre, Web Chat, Help Desk.
-
-
\ No newline at end of file
diff --git a/hints/business_role.html b/hints/business_role.html
deleted file mode 100644
index 4ddd1114a59ea12ca6784882a839051b936bb270..0000000000000000000000000000000000000000
--- a/hints/business_role.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Business Role
-
-
-
-
A Business Role represents the responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event.
-
-
-
\ No newline at end of file
diff --git a/hints/business_service.html b/hints/business_service.html
deleted file mode 100644
index 1d01066f75e2d3974173d16566a7e1822f841a80..0000000000000000000000000000000000000000
--- a/hints/business_service.html
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
-
-
- Business Service
-
-
-
A Business Service represents explicitly defined behavior that a business role, business actor, or business collaboration exposes to its environment.
-
-
Category:
-
Business. Behavioural.
-
-
Examples:
-
Customer Information Service, Claims Payment Service, Enrolment Service.
-
-
\ No newline at end of file
diff --git a/hints/canvas_block.html b/hints/canvas_block.html
deleted file mode 100644
index 700009c64056b3abc86029c4b73c007afc0d4e53..0000000000000000000000000000000000000000
--- a/hints/canvas_block.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- Canvas Block
-
-
-
-
A Block Object is a container area that can contain text and an icon. You can also provide your own Help Hints. You can lock the Block if you want to make it read-only.
-
A typical scenario is to create a number of container Blocks on the Canvas, arrange them into the desired framework, lock them, and then save the Canvas as a template.
-
-
\ No newline at end of file
diff --git a/hints/canvas_connection.html b/hints/canvas_connection.html
deleted file mode 100644
index e4f3c9ccc615c36cd5b93cb7ffcd65902b6af172..0000000000000000000000000000000000000000
--- a/hints/canvas_connection.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- Canvas Connection
-
-
-
-
A connection between two objects with no explicit semantic meaning.
-
You can lock the Connection if you want to make it read-only.
-
-
\ No newline at end of file
diff --git a/hints/canvas_diagram.html b/hints/canvas_diagram.html
deleted file mode 100644
index 747101b62e99290d6014662e124dabbdedfe5d43..0000000000000000000000000000000000000000
--- a/hints/canvas_diagram.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
-
-
- Canvas
-
-
-
-
A Canvas to hold Blocks, Images, Stickies and Connections. You can also provide your own Help Hints.
-
A typical scenario is to create a number of container Blocks and Stickies on the Canvas, arrange them into the desired framework, lock them, and then save the Canvas as a template.
-
You can drag and drop image files from the desktop to create Images on the Canvas.
-
-
\ No newline at end of file
diff --git a/hints/canvas_image.html b/hints/canvas_image.html
deleted file mode 100644
index 7fe0e579f3a5043f98d0e0f75d808296a01b11ca..0000000000000000000000000000000000000000
--- a/hints/canvas_image.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- Canvas Image
-
-
-
-
A Canvas Image. Choose your own image to add to the area.
-
You can lock the Image if you want to make it read-only.
-
-
\ No newline at end of file
diff --git a/hints/canvas_sticky.html b/hints/canvas_sticky.html
deleted file mode 100644
index 93bd562552e963ab59af790b2c627acfaa936057..0000000000000000000000000000000000000000
--- a/hints/canvas_sticky.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
-
-
- Canvas Sticky
-
-
-
-
A Sticky element for the Canvas.
-
Add text and an icon to the Sticky. You can lock the Sticky if you want to make it read-only.
-
Any Notes will appear in the tooltip for the Sticky.
-
-
\ No newline at end of file
diff --git a/hints/capability.html b/hints/capability.html
deleted file mode 100644
index 074fefec8b25a2c4997b6237b7cae757e2a11003..0000000000000000000000000000000000000000
--- a/hints/capability.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Capability
-
-
-
-
A Capability represents an ability that an active structure element, such as an organization, person, or system, possesses.
-
-
Category:
-
Strategy. Behaviour.
-
-
Examples:
-
Digital Customer Management, Data Analysis, Product Management, Productise Open Source Software.
-
-
\ No newline at end of file
diff --git a/hints/communication_network.html b/hints/communication_network.html
deleted file mode 100644
index ef2f2f7f5896f4954a074ef4ab1f54c0460917ad..0000000000000000000000000000000000000000
--- a/hints/communication_network.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Communication Network
-
-
-
-
A Communication Network represents a set of structures that connects devices or system software for transmission, routing, and reception of data.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
LAN. Wireless. Wide Area Network.
-
-
\ No newline at end of file
diff --git a/hints/composition.html b/hints/composition.html
deleted file mode 100644
index 7849207d46aba7583259200d270f795c44ee5031..0000000000000000000000000000000000000000
--- a/hints/composition.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Composition Relationship
-
-
-
-
The Composition relationship represents that an element consists of one or more other concepts.
-
-
Category:
-
Structural.
-
-
Examples:
-
An Application Component may be composed of two or more sub-components.
-
-
\ No newline at end of file
diff --git a/hints/connection.html b/hints/connection.html
deleted file mode 100644
index 4bdd799483070a106fb84439c08b56027e80029a..0000000000000000000000000000000000000000
--- a/hints/connection.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
-
-
- Connection
-
-
-
-
A plain connection between two objects with no explicit semantic meaning.
-
-
\ No newline at end of file
diff --git a/hints/constraint.html b/hints/constraint.html
deleted file mode 100644
index 6d0b5375230816598e25c5f2dd3b376cf3b0d232..0000000000000000000000000000000000000000
--- a/hints/constraint.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Constraint
-
-
-
-
A Constraint represents a limitation on aspects of the architecture, its implementation process, or its realization.
-
-
Category:
-
Motivation
-
-
Examples:
-
"Application should be realised in Java", "Cost should be below budget", "iPad only version", "Must use MIT license"
-
-
\ No newline at end of file
diff --git a/hints/contract.html b/hints/contract.html
deleted file mode 100644
index 439bf8a0c1a9ae686e3e898e9d461a5a5ac70364..0000000000000000000000000000000000000000
--- a/hints/contract.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Contract
-
-
-
-
A Contract represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product and establishes functional and non-functional parameters for interaction.
-
-
Category:
-
Business. Passive Structure.
-
-
Examples:
-
Travel Insurance Policy.
-
-
\ No newline at end of file
diff --git a/hints/course_of_action.html b/hints/course_of_action.html
deleted file mode 100644
index fb2d84b3904d12b88714095e74f79ef56a4de02d..0000000000000000000000000000000000000000
--- a/hints/course_of_action.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Course of Action
-
-
-
-
A Course of Action represents an approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.
-
-
Category:
-
Strategy. Behaviour.
-
-
Examples:
-
Acquire company, Merge organizations, Provide repository support.
-
-
\ No newline at end of file
diff --git a/hints/data_object.html b/hints/data_object.html
deleted file mode 100644
index 47db28a4693d09ae46e2946fccffc39c5bdc5ace..0000000000000000000000000000000000000000
--- a/hints/data_object.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Data Object
-
-
-
-
A Data Object represents data structured for automated processing.
-
-
\ No newline at end of file
diff --git a/hints/deliverable.html b/hints/deliverable.html
deleted file mode 100644
index adb37ffba7335f228a66f1ac2bd42f06dc125f58..0000000000000000000000000000000000000000
--- a/hints/deliverable.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Deliverable
-
-
-
-
A Deliverable represents a precisely-defined result of a work package.
-
-
Category:
-
Implementation and Migration
-
-
Examples:
-
Software, Hardware, CRM System, Report, Paper
-
-
\ No newline at end of file
diff --git a/hints/device.html b/hints/device.html
deleted file mode 100644
index 1aec3a94c8b26f1bff6c4c2f74acc8158b2a0ec1..0000000000000000000000000000000000000000
--- a/hints/device.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Device
-
-
-
-
A Device represents a physical IT resource upon which system software and artifacts may be stored or deployed for execution.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
File Server, Router, Mainframe, Desktop PC, IBM System Z.
-
-
\ No newline at end of file
diff --git a/hints/diagram_image.html b/hints/diagram_image.html
deleted file mode 100644
index 7d9d3a82dd2a219d74fd6d8b1e2af7740b0c18b6..0000000000000000000000000000000000000000
--- a/hints/diagram_image.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
-
-
- Image
-
-
-
-
A diagram image.
-
-
\ No newline at end of file
diff --git a/hints/distribution_network.html b/hints/distribution_network.html
deleted file mode 100644
index 1f771adf297ec2797518c71f9e5880a0fe6a5177..0000000000000000000000000000000000000000
--- a/hints/distribution_network.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Distribution Network
-
-
-
-
A Distribution Network represents a physical network used to transport materials or energy.
-
-
Category:
-
Physical. Active Structure.
-
-
Examples:
-
Local Trucking, Overseas Shipping.
-
-
\ No newline at end of file
diff --git a/hints/driver.html b/hints/driver.html
deleted file mode 100644
index cb511ee61f8bbe242ff4feb6fd92d6d6a88f5436..0000000000000000000000000000000000000000
--- a/hints/driver.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Driver
-
-
-
-
A Driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.
-
-
Category:
-
Motivation
-
-
Examples:
-
"Customer satisfaction", "Compliance to legislation", "Profitability", "Economic changes", "Changing legislation"
-
-
\ No newline at end of file
diff --git a/hints/equipment.html b/hints/equipment.html
deleted file mode 100644
index d452a9925999d4140e44c2bf78ea41eaf6b81f53..0000000000000000000000000000000000000000
--- a/hints/equipment.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Equipment
-
-
-
-
Equipment represents one or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
-
-
Category:
-
Physical. Active Structure.
-
-
Examples:
-
MRI scanner, Assembly line.
-
-
\ No newline at end of file
diff --git a/hints/facility.html b/hints/facility.html
deleted file mode 100644
index 46931b59cb3f994f78adcd15d57efb7af406b6ba..0000000000000000000000000000000000000000
--- a/hints/facility.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Facility
-
-
-
-
A Facility represents a physical structure or environment.
-
-
\ No newline at end of file
diff --git a/hints/flow.html b/hints/flow.html
deleted file mode 100644
index cef62b282bec270027a2fc31a000fecd055bfdb3..0000000000000000000000000000000000000000
--- a/hints/flow.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Flow Relationship
-
-
-
-
The Flow Relationship represents transfer (e.g. of information, goods or money) from one element to another.
-
-
Category:
-
Dynamic.
-
-
Examples:
-
A "Claim assessment" Business Function forwards decisions about the claim to the "Claim settlement" Business Function.
-
-
\ No newline at end of file
diff --git a/hints/folder.html b/hints/folder.html
deleted file mode 100644
index bb682f6c37021e58a5624a2c2d130f5179dcc3a0..0000000000000000000000000000000000000000
--- a/hints/folder.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- Folder
-
-
-
-
A folder to contain elements.
-
Note that the root folders cannot be deleted.
-
-
\ No newline at end of file
diff --git a/hints/gap.html b/hints/gap.html
deleted file mode 100644
index cab679085133eca1d71fc49799f50f5797e382ed..0000000000000000000000000000000000000000
--- a/hints/gap.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Gap
-
-
-
-
A Gap represents a statement of difference between two plateaus.
-
-
Category:
-
Implementation and Migration
-
-
Examples:
-
"Gap between the Baseline and Target infrastructure", "Knowledge of how to address customer needs".
-
-
\ No newline at end of file
diff --git a/hints/goal.html b/hints/goal.html
deleted file mode 100644
index d47ac0e7b8e137aa7c50d45f63ab2d9b9ada2b02..0000000000000000000000000000000000000000
--- a/hints/goal.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Goal
-
-
-
-
A Goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.
-
-
Category:
-
Motivation
-
-
Examples:
-
Increase profit, reduce waiting times at the helpdesk, introduce on-line portfolio management, more sales
-
-
\ No newline at end of file
diff --git a/hints/group.html b/hints/group.html
deleted file mode 100644
index cc068a8cf03d361157cc4f47c8bbb9f37de218c7..0000000000000000000000000000000000000000
--- a/hints/group.html
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
-
-
- Group
-
-
-
-
The Group box denotes a collection of objects that belong together but are not aggregated or composed as with the Grouping element.
-
-
The Group provides a convenient visual collection of elements, without any semantic relationships.
-
-
Examples:
-
Group Roles and Actors, Business Layers, Application Layers.
-
-
\ No newline at end of file
diff --git a/hints/grouping.html b/hints/grouping.html
deleted file mode 100644
index 453dea68d159dc38202b47f03809b475bd6bd54b..0000000000000000000000000000000000000000
--- a/hints/grouping.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Grouping
-
-
-
-
The Grouping element aggregates or composes concepts that belong together based on some common characteristic.
-
-
Category:
-
Other. Composite.
-
-
Examples:
-
Aggregate two Processes and an Object that together Realize a Service
-
-
\ No newline at end of file
diff --git a/hints/implementation_event.html b/hints/implementation_event.html
deleted file mode 100644
index 37dfe7c5c17037f97afc31db1d6371ff44fe1d13..0000000000000000000000000000000000000000
--- a/hints/implementation_event.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Implementation Event
-
-
-
-
An Implementation Event represents a state change related to implementation or migration.
-
-
Category:
-
Implementation and Migration
-
-
Examples:
-
"Release to production", "Project initiation phase completed".
-
-
\ No newline at end of file
diff --git a/hints/influence.html b/hints/influence.html
deleted file mode 100644
index a609d1d8f8f236662cbd9ec5e51e7592f93d9b89..0000000000000000000000000000000000000000
--- a/hints/influence.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Influence Relationship
-
-
-
-
The Influence Relationship represents that an element affects the implementation or achievement of some motivation element.
-
-
Category:
-
Dependency.
-
-
Examples:
-
The degree in which the goal to increase customer satisfaction is realized may be represented by the percentage of satisfied customers that participate in a market interview.
-
-
\ No newline at end of file
diff --git a/hints/junction.html b/hints/junction.html
deleted file mode 100644
index f39c91da7700740b8dc0a42f7ff4c7790a215b37..0000000000000000000000000000000000000000
--- a/hints/junction.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
-
-
- Junction
-
-
-
-
A Junction is used to connect relationships of the same type.
-
-
There are two types - And and Or.
-
-
Category:
-
Other.
-
-
Examples:
-
An "assess application" Business Process can lead to a choice Junction (split) to accept or reject the client application and route to alternative processes for each case.
-
-
\ No newline at end of file
diff --git a/hints/legend.html b/hints/legend.html
deleted file mode 100644
index f25333ebe081d90ff3281fb80d0344f2c3b1a614..0000000000000000000000000000000000000000
--- a/hints/legend.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
-
-
- Legend
-
-
-
-
A Legend can be included in an ArchiMate View to show all icons and names of the concepts within it.
-
-
\ No newline at end of file
diff --git a/hints/location.html b/hints/location.html
deleted file mode 100644
index 386e4d896a7fbff25679f6b489b7a75419bc0db8..0000000000000000000000000000000000000000
--- a/hints/location.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Location
-
-
-
-
A Location represents a conceptual or physical place or position where concepts are located (e.g., structure elements) or performed (e.g., behavior elements).
-
-
Category:
-
Other. Composite.
-
-
Examples:
-
Main Office, Local Office, Room.
-
-
\ No newline at end of file
diff --git a/hints/material.html b/hints/material.html
deleted file mode 100644
index 80a36073b371357e1d82d6062aa9916962f6a66c..0000000000000000000000000000000000000000
--- a/hints/material.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Material
-
-
-
-
Material represents tangible physical matter or energy.
-
-
Category:
-
Physical. Passive Structure.
-
-
Examples:
-
Plastic Case, Internal Antenna, Speedometer.
-
-
\ No newline at end of file
diff --git a/hints/meaning.html b/hints/meaning.html
deleted file mode 100644
index fbddfeb0d33aa6c60a43ce5be59db97051dc05e5..0000000000000000000000000000000000000000
--- a/hints/meaning.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Meaning
-
-
-
-
Meaning represents the knowledge or expertise present in, or the interpretation given to, a concept in a particular context.
A Node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
Mainframe, Unix Server Farm, Application Server, Firewall.
-
-
\ No newline at end of file
diff --git a/hints/note.html b/hints/note.html
deleted file mode 100644
index 319ab02b4889f68b38fc8dc1392b8c1165db057d..0000000000000000000000000000000000000000
--- a/hints/note.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- Note
-
-
-
-
A Note is simply a place to add user annotations to a diagram.
-
A Note has no semantic meaning in the ArchiMate language.
-
-
\ No newline at end of file
diff --git a/hints/outcome.html b/hints/outcome.html
deleted file mode 100644
index d82a805c1384f001466d7823298980a2f74441c6..0000000000000000000000000000000000000000
--- a/hints/outcome.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Outcome
-
-
-
-
An Outcome represents an end result, effect, or consequence of a certain state of affairs.
-
-
Category:
-
Motivation
-
-
Examples:
-
"First-place ranking achieved", "Key supplier partnerships in place", "2015 quarterly profits rose 10%"
-
-
\ No newline at end of file
diff --git a/hints/path.html b/hints/path.html
deleted file mode 100644
index 8507c39cf29b5b0d44199f0cc2544de05d50590a..0000000000000000000000000000000000000000
--- a/hints/path.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Path
-
-
-
-
A Path represents a link between two or more technology internal active structure elements, through which these elements can exchange data, energy, or material.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
Message Queuing, Data Replication Path.
-
-
\ No newline at end of file
diff --git a/hints/plateau.html b/hints/plateau.html
deleted file mode 100644
index 82bdd6199dc7f3fffda4b582f6e39b3c67d8cd11..0000000000000000000000000000000000000000
--- a/hints/plateau.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
-
-
- Plateau
-
-
-
-
-
-
A Plateau represents a relatively stable state of the architecture that exists during a limited period of time.
-
-
Category:
-
Implementation and Migration
-
-
Examples:
-
Baseline, Transition 1, Strategic Plan complete, Services in place.
-
-
\ No newline at end of file
diff --git a/hints/principle.html b/hints/principle.html
deleted file mode 100644
index 4085e11799a3884978a6e294ac37cf9496644796..0000000000000000000000000000000000000000
--- a/hints/principle.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Principle
-
-
-
-
A Principle represents a statement of intent defining a general property that applies to any system in a certain context in the architecture.
-
-
Category:
-
Motivation
-
-
Examples:
-
"Systems should be customer facing", "Customers should have a great experience", "Colleagues should be informed", "Open Source Software should be used"
-
-
\ No newline at end of file
diff --git a/hints/product.html b/hints/product.html
deleted file mode 100644
index 35aa902e1a7d5647b358548605259615cfc67170..0000000000000000000000000000000000000000
--- a/hints/product.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Product
-
-
-
-
A Product represents a coherent collection of services and/or passive structure elements, accompanied by a contract, which is offered as a whole to (internal or external) customers.
-
-
Category:
-
Business. Composite.
-
-
Examples:
-
A Travel Insurance Product consisting of Insurance Services and a Contract.
-
-
\ No newline at end of file
diff --git a/hints/realization.html b/hints/realization.html
deleted file mode 100644
index 96dd61834496169ef6d33952edde48d345b74149..0000000000000000000000000000000000000000
--- a/hints/realization.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
- Realization Relationship
-
-
-
-
The Realization Relationship represents that an element plays a critical role in the creation, achievement, sustenance, or operation of a more abstract element.
-
-
-
Category:
-
Structural.
-
-
Examples:
-
An Application Component, "Financial Application", realizes a "Billing" Service. A "Billing" Data Object realizes the Business Object, "Invoice".
-
-
\ No newline at end of file
diff --git a/hints/representation.html b/hints/representation.html
deleted file mode 100644
index b57cca2dffdb69cd8174e8f2874e93a4afbf1f2c..0000000000000000000000000000000000000000
--- a/hints/representation.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Representation
-
-
-
-
A Representation represents a perceptible form of the information carried by a business object.
-
-
Category:
-
Business. Passive Structure.
-
-
Examples:
-
Paper Bill, Request Form, Claim Form, Online Form.
-
-
\ No newline at end of file
diff --git a/hints/requirement.html b/hints/requirement.html
deleted file mode 100644
index edc01f70b50d92d6a9d22bceaa260791db34a7c6..0000000000000000000000000000000000000000
--- a/hints/requirement.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Requirement
-
-
-
-
A Requirement represents a statement of need defining a property that applies to a specific system as described by the architecture.
-
-
Category:
-
Motivation
-
-
Examples:
-
"Assign personal assistant", "Provide on-line portfolio service", "Provide on-line information service", "Use open source software"
-
-
\ No newline at end of file
diff --git a/hints/resource.html b/hints/resource.html
deleted file mode 100644
index 408d39b79b577d955ce65a94bda208edd29b2016..0000000000000000000000000000000000000000
--- a/hints/resource.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Resource
-
-
-
-
A Resource represents an asset owned or controlled by an individual or organization.
-
-
\ No newline at end of file
diff --git a/hints/sketch_sticky.html b/hints/sketch_sticky.html
deleted file mode 100644
index a3137c6df6a3a4695955a9594869565c2b9979b0..0000000000000000000000000000000000000000
--- a/hints/sketch_sticky.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
-
-
- Sticky
-
-
-
A "Sticky" figure for your Sketch.
-
-
\ No newline at end of file
diff --git a/hints/specialization.html b/hints/specialization.html
deleted file mode 100644
index ed86259fc5d7da0a44a9f8042ee990d7afda3375..0000000000000000000000000000000000000000
--- a/hints/specialization.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Specialization Relationship
-
-
-
-
The Specialization Relationship Represents that an element is a particular kind of another element.
-
-
Category:
-
Other.
-
-
Examples:
-
A "Take out travel insurance" and a "Take out luggage insurance" process are a specialization of a more generic "Take out insurance" process.
-
-
\ No newline at end of file
diff --git a/hints/stakeholder.html b/hints/stakeholder.html
deleted file mode 100644
index f4bd5d36f38917bcaa5daeddb3223bbc9d85e67f..0000000000000000000000000000000000000000
--- a/hints/stakeholder.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Stakeholder
-
-
-
-
A Stakeholder represents the role of an individual, team, or organization (or classes thereof) that represents their interests in the effects of the architecture.
-
-
Category:
-
Motivation
-
-
Examples:
-
CEO, the board of directors, shareholders, customers, business, and application architects
System Software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
DBMS, DB2 System Software, Message Queuing, Operating System, J2EE Application Server
-
-
\ No newline at end of file
diff --git a/hints/technology_collaboration.html b/hints/technology_collaboration.html
deleted file mode 100644
index 8e0a35270203168cc5d668a9952d12fbab44516f..0000000000000000000000000000000000000000
--- a/hints/technology_collaboration.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Collaboration
-
-
-
-
A Technology Collaboration represents an aggregate of two or more technology internal active structure elements that work together to perform collective technology behavior.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
E-Commerce Hosting.
-
-
\ No newline at end of file
diff --git a/hints/technology_event.html b/hints/technology_event.html
deleted file mode 100644
index 2e6009b68a10c95583baf17932d4b927569ac035..0000000000000000000000000000000000000000
--- a/hints/technology_event.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Event
-
-
-
-
A Technology Event represents a technology state change.
-
-
Category:
-
Technology. Behavioural.
-
-
Examples:
-
Message received, Database update.
-
-
\ No newline at end of file
diff --git a/hints/technology_function.html b/hints/technology_function.html
deleted file mode 100644
index 3d425d7e33f58a460dea5f919772b2cd51d18716..0000000000000000000000000000000000000000
--- a/hints/technology_function.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Function
-
-
-
-
A Technology Function represents a collection of technology behavior that can be performed by a technology internal active structure element.
-
-
Category:
-
Technology. Behavioural.
-
-
Examples:
-
Providing Data Access, Managing Data.
-
-
\ No newline at end of file
diff --git a/hints/technology_interaction.html b/hints/technology_interaction.html
deleted file mode 100644
index 457060d3c58e23b693f53d0cb992750cc708e7c7..0000000000000000000000000000000000000000
--- a/hints/technology_interaction.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Interaction
-
-
-
-
A Technology Interaction represents a unit of collective technology behavior performed by (a collaboration of) two or more technology internal active structure elements.
-
-
Category:
-
Technology. Behavioural.
-
-
Examples:
-
Client profile creation, Update customer records.
-
-
\ No newline at end of file
diff --git a/hints/technology_interface.html b/hints/technology_interface.html
deleted file mode 100644
index 8f4136263b74ff30cd0491b53d6607f2862cf56c..0000000000000000000000000000000000000000
--- a/hints/technology_interface.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Interface
-
-
-
-
A Technology Interface represents a point of access where technology services offered by a technology internal active structure element can be accessed.
-
-
Category:
-
Technology. Active Structure.
-
-
Examples:
-
Client software, Management Interface.
-
-
\ No newline at end of file
diff --git a/hints/technology_process.html b/hints/technology_process.html
deleted file mode 100644
index 5a657c304ff6277d6db98d7ea750a021ca9c9d40..0000000000000000000000000000000000000000
--- a/hints/technology_process.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Process
-
-
-
-
A Technology Process represents a sequence of technology behaviors that achieves a specific result.
-
-
Category:
-
Technology. Behavioural.
-
-
Examples:
-
Boot up system, Replicate database
-
-
\ No newline at end of file
diff --git a/hints/technology_service.html b/hints/technology_service.html
deleted file mode 100644
index 1c1985bcfbc25f5328cf9980308a453a5ef1ad13..0000000000000000000000000000000000000000
--- a/hints/technology_service.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Technology Service
-
-
-
-
A Technology Service represents an explicitly defined exposed technology behavior.
-
-
\ No newline at end of file
diff --git a/hints/view.html b/hints/view.html
deleted file mode 100644
index 371c7607caf0610458ae901abb3afce02df0956f..0000000000000000000000000000000000000000
--- a/hints/view.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
-
-
- View
-
-
-
-
A View is a part of an Architecture Description that addresses a set of related concerns and is tailored for specific stakeholders.
-
A View is specified by means of a Viewpoint, which prescribes the concepts, models, analysis techniques, and visualizations that are provided by the View.
-
The same elements from the Model Tree can be re-used multiple times in the same or different View.
-
-
\ No newline at end of file
diff --git a/hints/view_ref.html b/hints/view_ref.html
deleted file mode 100644
index 1b7597ef5b95358d10fb5d4be8f6786cc99dd6ad..0000000000000000000000000000000000000000
--- a/hints/view_ref.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
-
-
- View Reference
-
-
-
-
A View Reference is simply a shortcut to another View in the same model.
-
Add a View Reference to a View if you wish to create a link to another View of the model. Double-click on it to jump to the View it references.
-
-
\ No newline at end of file
diff --git a/hints/vp_application_cooperation.html b/hints/vp_application_cooperation.html
deleted file mode 100644
index 201f5c503e1aa9b3de5b9e78592560673eb1a70b..0000000000000000000000000000000000000000
--- a/hints/vp_application_cooperation.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Application Cooperation Viewpoint
-
-
-
-
The Application Cooperation viewpoint describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization. This viewpoint is also used to express the (internal) cooperation or orchestration of services that together support the execution of a business process.
-
-
Stakeholders:
-
Enterprise, process, application, and domain architects
-
-
Concerns:
-
Relationships and dependencies between applications, orchestration/choreography of services, consistency and completeness, reduction of complexity
-
-
Purpose:
-
Designing
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_application_structure.html b/hints/vp_application_structure.html
deleted file mode 100644
index 64f13fb9b9488a9aeb2a1fac45e7aaf7a80a4ade..0000000000000000000000000000000000000000
--- a/hints/vp_application_structure.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Application Structure Viewpoint
-
-
-
-
The Application Structure viewpoint shows the structure of one or more applications or components. This viewpoint is useful in designing or understanding the main structure of applications or components and the associated data; e.g., to break down the structure of the system under construction, or to identify legacy application components that are suitable for migration/integration.
-
-
Stakeholders:
-
Application and solution architects
-
-
Concerns:
-
Application structure, consistency and completeness, reduction of complexity
-
-
Purpose:
-
Designing
-
-
Scope:
-
Single layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_application_usage.html b/hints/vp_application_usage.html
deleted file mode 100644
index 736ca84176a2800cd08be4d9c65b94b85fc4f240..0000000000000000000000000000000000000000
--- a/hints/vp_application_usage.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Application Usage Viewpoint
-
-
-
-
The Application Usage viewpoint describes how applications are used to support one or more business processes, and how they are used by other applications. It can be used in designing an application by identifying the services needed by business processes and other applications, or in designing business processes by describing the services that are available. Furthermore, since it identifies the dependencies of business processes upon applications, it may be useful to operational managers responsible for these processes.
-
-
Stakeholders:
-
Enterprise, process, and application architects, operational managers
-
-
Concerns:
-
Consistency and completeness, reduction of complexity
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_business_process_cooperation.html b/hints/vp_business_process_cooperation.html
deleted file mode 100644
index d0c8b6de640081dc912cf47d8e3658c9dd91b37a..0000000000000000000000000000000000000000
--- a/hints/vp_business_process_cooperation.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
- Business Process Cooperation Viewpoint
-
-
-
-
The Business Process Cooperation viewpoint is used to show the relationships of one or more business processes with each other and/or with their environment. It can both be used to create a high-level design of business processes within their context and to provide an operational manager responsible for one or more such processes with insight into their dependencies. Important aspects of business process cooperation are:
-
-
Causal relationships between the main business processes of the enterprise
-
Mapping of business processes onto business functions
-
Realization of services by business processes
-
Use of shared data
-
-
Each of these can be regarded as a "sub-viewpoint" of the business process cooperation viewpoint.
-
-
Stakeholders:
-
Process and domain architects, operational managers
-
-
Concerns:
-
Dependencies between business processes, consistency and completeness, responsibilities
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_capability.html b/hints/vp_capability.html
deleted file mode 100644
index bcbac819331629da3ac0dd9a3fded0bb22fa81a8..0000000000000000000000000000000000000000
--- a/hints/vp_capability.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Capability Viewpoint
-
-
-
-
The Capability map viewpoint allows the business architect to create a structured overview of the capabilities of the enterprise. A capability map typically shows two or three levels of capabilities across the entire enterprise. It can, for example, be used as a heat map to identify areas of investment. In some cases, a capability map may also show specific outcomes delivered by these capabilities.
-
-
Stakeholders:
-
Business managers, enterprise and business architects
-
-
Concerns:
-
Architecture strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Strategy
-
-
\ No newline at end of file
diff --git a/hints/vp_goal_realization.html b/hints/vp_goal_realization.html
deleted file mode 100644
index 489611ffb64d83c39a7a8da82bf362aa079b7ff6..0000000000000000000000000000000000000000
--- a/hints/vp_goal_realization.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
- Goal Realization Viewpoint
-
-
-
-
The Goal Realization viewpoint allows a designer to model the refinement of (high-level) goals into more tangible goals, and the refinement of tangible goals into requirements or constraints that describe the properties that are needed to realize the goals. The refinement of goals into sub-goals is modeled using the aggregation relationship. The refinement of goals into requirements is modeled using the realization relationship.
-
-
In addition, the principles may be modeled that guide the refinement of goals into requirements.
-
-
Stakeholders:
-
Stakeholders, business managers, enterprise and ICT architects, business analysts, requirements managers
-
-
Concerns:
-
Architecture mission, strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Motivation
-
-
\ No newline at end of file
diff --git a/hints/vp_implementation_deployment.html b/hints/vp_implementation_deployment.html
deleted file mode 100644
index c92c23201ff567b1242a994bfd76e2fa328ab6be..0000000000000000000000000000000000000000
--- a/hints/vp_implementation_deployment.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Implementation and Deployment Viewpoint
-
-
-
-
The Implementation and Deployment viewpoint shows how one or more applications are realized on the infrastructure. This comprises the mapping of applications and components onto artifacts, and the mapping of the information used by these applications and components onto the underlying storage infrastructure.
-
-
Stakeholders:
-
Application and domain architects
-
-
Concerns:
-
Structure of application platforms and how they relate to supporting technology
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_implementation_migration.html b/hints/vp_implementation_migration.html
deleted file mode 100644
index 03dbed019cc9b8a53b53b8b15865b69eae02208d..0000000000000000000000000000000000000000
--- a/hints/vp_implementation_migration.html
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
-
-
- Implementation and Migration Viewpoint
-
-
-
-
The Implementation and Migration viewpoint is used to relate programs and projects to the parts of the architecture that they implement. This view allows modeling of the scope of programs, projects, project activities in terms of the plateaus that are realized or the individual architecture elements that are affected. In addition, the way the elements are affected may be indicated by annotating the relationships.
-
-
Furthermore, this viewpoint can be used in combination with the programs and projects viewpoint to support portfolio management:
-
-
The programs and projects viewpoint is suited to relate business goals to programs and projects. For example, this makes it possible to analyze at a high level whether all business goals are covered sufficiently by the current portfolio(s).
-
The implementation and migration viewpoint is suited to relate business goals (and requirements) via programs and projects to (parts of) the architecture. For example, this makes it possible to analyze potential overlap between project activities or to analyze the consistency between project dependencies and dependencies among plateaus or architecture elements.
-
-
-
Stakeholders:
-
(Operational) managers, enterprise and ICT architects, employees, shareholders
-
-
Concerns:
-
Architecture vision and policies, motivation
-
-
Purpose:
-
Deciding, informing
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_information_structure.html b/hints/vp_information_structure.html
deleted file mode 100644
index 61defe2dd5bb7705c4af9ced2cf04bf8addadb3a..0000000000000000000000000000000000000000
--- a/hints/vp_information_structure.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Information Structure Viewpoint
-
-
-
-
The Information Structure viewpoint is comparable to the traditional information models created in the development of almost any information system. It shows the structure of the information used in the enterprise or in a specific business process or application, in terms of data types or (object-oriented) class structures. Furthermore, it may show how the information at the business level is represented at the application level in the form of the data structures used there, and how these are then mapped onto the underlying technology infrastructure; e.g., by means of a database schema.
-
-
Stakeholders:
-
Domain and information architects
-
-
Concerns:
-
Structure and dependencies of the used data and information, consistency and completeness
-
-
Purpose:
-
Designing
-
-
Scope:
-
Multiple layer/Single aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_layered.html b/hints/vp_layered.html
deleted file mode 100644
index 4034e324137da5fb0449919e5ccc7c02043b5fae..0000000000000000000000000000000000000000
--- a/hints/vp_layered.html
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
-
-
- Layered Viewpoint
-
-
-
-
The Layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram.
-
-
There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the "grouping" relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the "realization" relationship, a layer of services, which are further on "serving" the next dedicated layer.
-
-
Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes.
-
-
The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.
-
-
Stakeholders:
-
Enterprise, process, application, infrastructure, and domain architects
-
-
Concerns:
-
Consistency, reduction of complexity, impact of change, flexibility
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_migration.html b/hints/vp_migration.html
deleted file mode 100644
index cfa456724f29a019eed27421a109bdbd9706775e..0000000000000000000000000000000000000000
--- a/hints/vp_migration.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Migration Viewpoint
-
-
-
-
The Migration viewpoint entails models and concepts that can be used for specifying the transition from an existing architecture to a desired architecture. Since the plateau and gap elements have been quite extensively presented in Section 13.2, here the migration viewpoint is only briefly described and positioned by means of the table below.
-
-
Stakeholders:
-
Enterprise architects, process architects, application architects, infrastructure architects and domain architects, employees, shareholders
-
-
Concerns:
-
History of models
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Implementation and Migration
-
-
\ No newline at end of file
diff --git a/hints/vp_motivation.html b/hints/vp_motivation.html
deleted file mode 100644
index c8fa9b9ecc94405f919c1f52a1a449d7eae0e175..0000000000000000000000000000000000000000
--- a/hints/vp_motivation.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Motivation Viewpoint
-
-
-
-
The Motivation viewpoint allows the designer or analyst to model the motivation aspect, without focusing on certain elements within this aspect. For example, this viewpoint can be used to present a complete or partial overview of the motivation aspect by relating stakeholders, their primary goals, the principles that are applied, and the main requirements on services, processes, applications, and objects.
-
-
Stakeholders:
-
Enterprise and ICT architects, business analysts, requirements managers
-
-
Concerns:
-
Architecture strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Motivation
-
-
\ No newline at end of file
diff --git a/hints/vp_organization.html b/hints/vp_organization.html
deleted file mode 100644
index a79576b2d1b8689da37a4f726002543574854a93..0000000000000000000000000000000000000000
--- a/hints/vp_organization.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Organization Viewpoint
-
-
-
-
The Organization viewpoint focuses on the (internal) organization of a company, department, network of companies, or of another organizational entity. It is possible to present models in this viewpoint as nested block diagrams, but also in a more traditional way, such as organizational charts. The Organization viewpoint is very useful in identifying competencies, authority, and responsibilities in an organization.
-
-
Stakeholders:
-
Enterprise, process and domain architects, managers, employees, shareholders
-
-
Concerns:
-
Identification of competencies, authority, and responsibilities
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Single layer/Single aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_outcome_realization.html b/hints/vp_outcome_realization.html
deleted file mode 100644
index 1a9040d0228d3f6fbf4c0f614e50e22b62c22b77..0000000000000000000000000000000000000000
--- a/hints/vp_outcome_realization.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Outcome Realization Viewpoint
-
-
-
-
The Outcome Realization viewpoint is used to show how the highest-level, business-oriented results are produced by the capabilities and underlying core elements.
-
-
Stakeholders:
-
Business managers, enterprise and business architects
-
-
Concerns:
-
Business-oriented results
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Strategy
-
-
\ No newline at end of file
diff --git a/hints/vp_physical.html b/hints/vp_physical.html
deleted file mode 100644
index 8b9301eafbf3560c262544779ac870cbe35d2c53..0000000000000000000000000000000000000000
--- a/hints/vp_physical.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Physical Viewpoint
-
-
-
-
The Physical viewpoint contains equipment (one or more physical machines, tools, or instruments) that can create, use, store, move, or transform materials, how the equipment is connected via the distribution network, and what other active elements are assigned to the equipment.
-
-
Stakeholders:
-
Infrastructure architects, operational managers
-
-
Concerns:
-
Relationships and dependencies of the physical environment and how this relates to IT infrastructure
-
-
Purpose:
-
Designing
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_product.html b/hints/vp_product.html
deleted file mode 100644
index e1c3df24f69ddb00ba5d055fd120a14d97ce2597..0000000000000000000000000000000000000000
--- a/hints/vp_product.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Product Viewpoint
-
-
-
-
The Product viewpoint depicts the value that these products offer to the customers or other external parties involved and shows the composition of one or more products in terms of the constituting (business, application, or technology) services, and the associated contract(s) or other agreements. It may also be used to show the interfaces (channels) through which this product is offered, and the events associated with the product. A product viewpoint is typically used in product development to design a product by composing existing services or by identifying which new services have to be created for this product, given the value a customer expects from it. It may then serve as input for business process architects and others that need to design the processes and ICT realizing these products.
-
-
Stakeholders:
-
Product developers, product managers, process and domain architects
-
-
Concerns:
-
Product development, value offered by the products of the enterprise
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_project.html b/hints/vp_project.html
deleted file mode 100644
index 3ce76c10c40c1dc3bcba717849a46e6ee2ba8598..0000000000000000000000000000000000000000
--- a/hints/vp_project.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
- Project Viewpoint
-
-
-
-
A Project viewpoint is primarily used to model the management of architecture change. The “architecture” of the migration process from an old situation (current state Enterprise Architecture) to a new desired situation (target state Enterprise Architecture) has significant consequences on the medium and long-term growth strategy and the subsequent decision-making process. Some of the issues that should be taken into account by the models designed in this viewpoint are:
-
-
Developing a fully-fledged organization-wide Enterprise Architecture is a task that may require several years.
-
All systems and services must remain operational regardless of the presumed modifications and changes of the Enterprise Architecture during the change process.
-
The change process may have to deal with immature technology standards (e.g., messaging, security, data, etc.).
-
The change has serious consequences for the personnel, culture, way of working, and organization.
-
-
Furthermore, there are several other governance aspects that might constrain the transformation process, such as internal and external cooperation, project portfolio management, project management (deliverables, goals, etc.), plateau planning, financial and legal aspects, etc.
-
-
Stakeholders:
-
(Operational) managers, enterprise and ICT architects, employees, shareholders
-
-
Concerns:
-
Architecture vision and policies, motivation
-
-
Purpose:
-
Deciding, informing
-
-
Scope:
-
Implementation and Migration
-
-
\ No newline at end of file
diff --git a/hints/vp_requirements_realization.html b/hints/vp_requirements_realization.html
deleted file mode 100644
index cf1d05435908d04fddf132817b33091e1fc4a6e8..0000000000000000000000000000000000000000
--- a/hints/vp_requirements_realization.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
- Requirements Realization Viewpoint
-
-
-
-
The Requirements Realization viewpoint allows the designer to model the realization of requirements by the core elements, such as business actors, business services, business processes, application services, application components, etc. Typically, the requirements result from the goal refinement viewpoint.
-
-
In addition, this viewpoint can be used to refine requirements into more detailed requirements. The aggregation relationship is used for this purpose.
-
-
Stakeholders:
-
Enterprise and ICT architects, business analysts, requirements managers
-
-
Concerns:
-
Architecture strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Motivation
-
-
\ No newline at end of file
diff --git a/hints/vp_resource.html b/hints/vp_resource.html
deleted file mode 100644
index 7111fc67f303e42876ea0b39d197dd71d7d646f7..0000000000000000000000000000000000000000
--- a/hints/vp_resource.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Resource Map Viewpoint
-
-
-
-
The Resource map viewpoint allows the business architect to create a structured overview of the resources of the enterprise. A resource map typically shows two or three levels of resources across the entire enterprise. It can, for example, be used as a heat map to identify areas of investment. In some cases, a resource map may also show relationships between resources and the capabilities they are assigned to.
-
-
Stakeholders:
-
Business managers, enterprise and business architects
-
-
Concerns:
-
Architecture strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Strategy
-
-
\ No newline at end of file
diff --git a/hints/vp_service_realization.html b/hints/vp_service_realization.html
deleted file mode 100644
index 6255f10fbebcf129c4140b60cc06bdb300a371c2..0000000000000000000000000000000000000000
--- a/hints/vp_service_realization.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Service Realization Viewpoint
-
-
-
-
The Service Realization viewpoint is used to show how one or more business services are realized by the underlying processes (and sometimes by application components). Thus, it forms the bridge between the business products viewpoint and the business process view. It provides a "view from the outside" on one or more business processes.
-
-
Stakeholders:
-
Process and domain architects, product and operational managers
-
-
Concerns:
-
Added-value of business processes, consistency and completeness, responsibilities
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Multiple layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_stakeholder.html b/hints/vp_stakeholder.html
deleted file mode 100644
index 3530e2179b34c432b2413078ca8e2466fe6a58cd..0000000000000000000000000000000000000000
--- a/hints/vp_stakeholder.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Stakeholder Viewpoint
-
-
-
-
The Stakeholder viewpoint allows the analyst to model the stakeholders, the internal and external drivers for change, and the assessments (in terms of strengths, weaknesses, opportunities, and threats) of these drivers. Also, the links to the initial (high-level) goals that address these concerns and assessments may be described. These goals form the basis for the requirements engineering process, including goal refinement, contribution and conflict analysis, and the derivation of requirements that realize the goals.
-
-
Stakeholders:
-
Stakeholders, business managers, enterprise and ICT architects, business analysts, requirements managers
-
-
Concerns:
-
Architecture mission and strategy, motivation
-
-
Purpose:
-
Designing, deciding, informing
-
-
Scope:
-
Motivation
-
-
\ No newline at end of file
diff --git a/hints/vp_strategy.html b/hints/vp_strategy.html
deleted file mode 100644
index 36fe1cdc6b819f08b6be9944d4c13a205a9c2157..0000000000000000000000000000000000000000
--- a/hints/vp_strategy.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Strategy Viewpoint
-
-
-
-
The Strategy viewpoint allows the business architect to model a high-level, strategic overview of the strategies (courses of action) of the enterprise, the capabilities and resources supporting those, and the envisaged outcomes.
-
-
Stakeholders:
-
CxOs, business managers, enterprise and business architects
-
-
Concerns:
-
Strategy development
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Strategy
-
-
\ No newline at end of file
diff --git a/hints/vp_technology.html b/hints/vp_technology.html
deleted file mode 100644
index 0152b85c9f98cd73df948c8a72302cdbc97e3fee..0000000000000000000000000000000000000000
--- a/hints/vp_technology.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Technology Viewpoint
-
-
-
-
The Technology viewpoint contains the software and hardware technology elements supporting the Application Layer, such as physical devices, networks, or system software (e.g., operating systems, databases, and middleware).
-
-
Stakeholders:
-
Infrastructure architects, operational managers
-
-
Concerns:
-
Stability, security, dependencies, costs of the infrastructure
-
-
Purpose:
-
Designing
-
-
Scope:
-
Single layer/Multiple aspect
-
-
\ No newline at end of file
diff --git a/hints/vp_technology_usage.html b/hints/vp_technology_usage.html
deleted file mode 100644
index 471c0ae82ed216c2a8e64b63523cdd0faa861883..0000000000000000000000000000000000000000
--- a/hints/vp_technology_usage.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Technology Usage Viewpoint
-
-
-
-
The Technology Usage viewpoint shows how applications are supported by the software and hardware technology: the technology services are delivered by the devices; system software and networks are provided to the applications. This viewpoint plays an important role in the analysis of performance and scalability, since it relates the physical infrastructure to the logical world of applications. It is very useful in determining the performance and quality requirements on the infrastructure based on the demands of the various applications that use it.
-
-
\ No newline at end of file
diff --git a/hints/vp_value_stream.html b/hints/vp_value_stream.html
deleted file mode 100644
index 97b87f81848e60c1205ee0396a85c15f5109217a..0000000000000000000000000000000000000000
--- a/hints/vp_value_stream.html
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
- Value Stream Viewpoint
-
-
-
-
The Value Stream viewpoint allows the Business Architect to create a structured overview of a value stream, the capabilities supporting the stages in that value stream, the value created, and the stakeholders involved.
-
-
Stakeholders:
-
Business managers, enterprise and business architects
-
-
Concerns:
-
Architecture strategy and tactics, motivation
-
-
Purpose:
-
Designing, deciding
-
-
Scope:
-
Strategy
-
-
\ No newline at end of file
diff --git a/hints/workpackage.html b/hints/workpackage.html
deleted file mode 100644
index cd6767dee28707770a72543c5febd1052afea994..0000000000000000000000000000000000000000
--- a/hints/workpackage.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
- Work Package
-
-
-
-
A Work Package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints.
-
-
Category:
-
Implementation and Migration
-
-
Examples:
-
"Program to sustain implementation", "Project to secure funding", "Project for CRM system integration"
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html b/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html
deleted file mode 100644
index c2b0e846f9dd819f4793111fa8ab0069e8254560..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html
+++ /dev/null
@@ -1,214 +0,0 @@
-
-
-
-
- Transition
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Transition
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.10.1] The purpose of the Transition process is to establish a capability for a system to provide services specified by stakeholder requirements in the operational environment. See detailed description in the INCOSE Handbook v.5, page 143
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html b/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html
deleted file mode 100644
index 661ca0fbe00d9a56c2d8d7e03c2181290514ff25..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html
+++ /dev/null
@@ -1,185 +0,0 @@
-
-
-
-
- Quality Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Quality Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.5.1] The purpose of the Quality Management process is to assure that products, services and implementations of the quality management process meet organizational and project quality objectives and achieve customer satisfaction. See detailed description in the INCOSE Handbook v.5, page 63
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html b/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html
deleted file mode 100644
index fe73526c2e3dbca231abcca00a9b830660822ab7..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Life cycle models
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Life cycle models
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Framework of processes and activities concerned with the life cycle that can be organized into stages, acting as a common reference for communication and understanding. (ISO/IEC/IEEE 15288, 2023)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html b/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html
deleted file mode 100644
index 72f646884a96f07289d11163962fd2b463d38acc..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-
-
- Measurement needs
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Measurement needs
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Measurement needs from all applicable life cycle processes, including: critical performance measurement needs, organizational measurement needs, and project measurement needs.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html b/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html
deleted file mode 100644
index 6c1c8cfc0609de6cfb8bee11772dc9578aef2cd4..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Request for supply
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Request for supply
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Acquirer’s request for information and commitments needed from the supplier that are required to be included in the potential supplier’s proposal. It announces the acquirer’s intention to potential bidders to acquire a specified system or system element (product or service). (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html b/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html
deleted file mode 100644
index 98534725c28132c7231c101e39d98ae7502af7cd..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html
+++ /dev/null
@@ -1,147 +0,0 @@
-
-
-
-
- System architecture description
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System architecture description
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
The fundamental conception of a system-of-interest in terms of its purpose, system qualities (such as feasibility, performance, safety, and interoperability), constraints, and design decisions and rationale. Identification of the architecture’s stakeholders and the stakeholders’ architecture-related concerns. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html b/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html
deleted file mode 100644
index f64fccbac8488acd6c69b2f961217431c434d1a9..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html
+++ /dev/null
@@ -1,150 +0,0 @@
-
-
-
-
- Measurement
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Measurement
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.7.1] The purpose of the Measurement process is to collect, analyze, and report objective data and information to support effective management and demonstrate the quality of the products, services, and processes. See detailed description in the INCOSE Handbook v.5, page 93
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html b/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html
deleted file mode 100644
index c1d1de100dcc19c4fbda56f0e8bd23a426b29d10..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html
+++ /dev/null
@@ -1,230 +0,0 @@
-
-
-
-
- Constraints on solution
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Constraints on solution
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Externally imposed limitation on the system, its design, or implementation or on the process used to develop or modify a system. (ISO/IEC/IEEE 29148, 2018).
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html b/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html
deleted file mode 100644
index 2ae934451dcb3982cf6c229a2b31ec78ee868d7b..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html
+++ /dev/null
@@ -1,254 +0,0 @@
-
-
-
-
- Validation
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Validation
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.11.1] The purpose of the Validation process is to provide objective evidence that the system, when in use, fulfills its business or mission objectives and stakeholder requirements, achieving its intended use in its intended operational environment. See detailed description in the INCOSE Handbook v.5, page 146
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html b/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html
deleted file mode 100644
index e56e343e1913d8d2f6c234b88bb587b45703e327..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html
+++ /dev/null
@@ -1,227 +0,0 @@
-
-
-
-
- Life cycle concepts
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Life cycle concepts
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Articulation and refinement of the various life cycle concepts consistent with the stakeholder needs. Typical concepts include: acquisition concept; deployment concept; operational concept (OpsCon); support concept; retirement concept.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html b/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html
deleted file mode 100644
index 5452fdf833a43873c9be1375b62b4aef9df133da..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html
+++ /dev/null
@@ -1,229 +0,0 @@
-
-
-
-
- Integration
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Integration
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.8.1] The purpose of the Integration process is to synthesize a set of system elements into a realized system (product or service) that satisfies system requirements* architecture, and design. See detailed description in the INCOSE Handbook v.5, page 134
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html b/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html
deleted file mode 100644
index ea284ab3c30e09d92c7d679b281f3bc9008e61f2..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html
+++ /dev/null
@@ -1,185 +0,0 @@
-
-
-
-
- Quality Assurance
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Quality Assurance
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.8.1] The purpose of the Quality Assurance process is to help ensure the effective application of the organization's Quality Management process to the project. See detailed description in the INCOSE Handbook v.5, page 98
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html b/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html
deleted file mode 100644
index 87ac4713e332d43082623b70b36817bc02e4df8a..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html
+++ /dev/null
@@ -1,155 +0,0 @@
-
-
-
-
- Information Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Information Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.6.1] The purpose of the Information Management process is to generate, obtain, confirm, transform, retain, retrieve, disseminate and dispose of information, to designated stakeholders. Information management plans, executes, and controls the provision of information to designated stakeholders that is unambiguous, complete, verifiable, consistent, modifiable, traceable, and presentable. Information includes technical, project, organizational, agreement, and user information. Information is often derived from data records of the organization, system, process, or project. See detailed description in the INCOSE Handbook v.5, page 91
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html b/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html
deleted file mode 100644
index 79e1187b411e6354e23305ea7cbb3006c4257726..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html
+++ /dev/null
@@ -1,200 +0,0 @@
-
-
-
-
- Life Cycle Model Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Life Cycle Model Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.1.1] The purpose of the Life Cycle Model Management process is to define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures for use by the organization with respect to the scope of [ISO/IEC/IEEE 15288:2023]. See detailed description in the INCOSE Handbook v.5, page 51
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html b/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html
deleted file mode 100644
index 24665145957ddac629bbeae9cefe5884fdf47244..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Project direction
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project direction
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Organizational direction to the project. Includes sustainment of projects meeting objectives and redirection or termination of projects not meeting objectives.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html b/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html
deleted file mode 100644
index 7d000fa1ec960f7b750b207c4a530966276354c2..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
-
- Project status report or dashboard
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project status report or dashboard
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A linked list of a project’s milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
Action to eliminate the cause or reduce the likelihood of recurrence of a detected project nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1, 2017)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html b/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html
deleted file mode 100644
index b7886726f4d20af166dc826833e6f5034323fb47..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Problem or opportunity statement
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Problem or opportunity statement
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Description of the problem or opportunity. Should be derived from the organization strategy and provide enough detail to understand the gap or new capability that is being considered
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html b/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html
deleted file mode 100644
index 37994ad036a483b164467824dabc66c48065c9d3..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
-
- System element description
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System element description
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Applies the system architecture description to the low-level system configuration items and elements. It is at a level of detail to permit design, implementation, and test. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html b/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html
deleted file mode 100644
index 2326bce45a1694c1bfa7944e7eef97c72e2301bc..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html
+++ /dev/null
@@ -1,147 +0,0 @@
-
-
-
-
- System architecture rationale
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System architecture rationale
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Rationale for architecture selection, technological/technical system element selection, and allocation between system requirements and architectural entities.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html b/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html
deleted file mode 100644
index f91ba84b8542f01e3fff9343771ba4eaa889af65..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-
-
- Acquired system or system element
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Acquired system or system element
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
System or system element (product or service) delivered to the acquirer from a supplier consistent with the delivery conditions of the acquisition agreement.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html b/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html
deleted file mode 100644
index ee22dd639baf580e1261e953a7caeecff2af05c2..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Breakdown structures
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Breakdown structures
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Hierarchical representations of project aspects into smaller components providing the necessary frameworks to accomplish the project objectives and create the required deliverables.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html b/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html
deleted file mode 100644
index a88e97b786b6f5324d2e0f18603b1ac7070eca23..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html
+++ /dev/null
@@ -1,168 +0,0 @@
-
-
-
-
- Tailoring
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Tailoring
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [Annex A.2.1] The purpose of the tailoring process is to adapt the life cycle processes included in this document [i.e. ISO/IEC/IEEE 15288:2023] to satisfy particular circumstances or factors that:
-
-a) surround an organization that is employing ISO/IEC/IEEE 15288 in an agreement;
-
-b) influence a project that is required to meet an agreement in which ISO/IEC/IEEE 15288 is referenced;
-
-c) reflect the needs of an organization in order to supply products or services.
-
-See detailed description in the INCOSE Handbook v.5, page 215
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html b/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html
deleted file mode 100644
index 3fedb49fbafd3e4fb43120be56391d781319ea91..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Qualified personnel
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Qualified personnel
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Individuals equipped to perform duties on behalf of the organization, including officers, employees, and contractors. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html b/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html
deleted file mode 100644
index 2066745ad2f812078b3c67c3696ecbd87cfb8d54..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Project decision gate or review result
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project decision gate or review result
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Decision gate and review artifacts that are expected through conduct of the decision gate or technical review and that can be considered elements of exit criteria. (Adapted from ISO/IEC/IEEE 24748–8, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html b/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html
deleted file mode 100644
index 977f7482d75a1c7c019c308a03e3c5474ea49618..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Stakeholder identification
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Stakeholder identification
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
List of individuals or organizations having a right++ share, claim, or interest in a system or in ist possession of characteristics that meet their needs and expectations. (Adapted from ISO/IEC/IEEE 15288, 2023)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html b/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html
deleted file mode 100644
index 481d2e34144c991280c5ea6ea92fad15eaa8558d..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html
+++ /dev/null
@@ -1,137 +0,0 @@
-
-
-
-
- Situational
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Situational
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Situational represents those typical inputs and outputs that are situational with respect to the execution of the system life cycle processes (i.e., they are invoked when needed).
-
-They can come from any life cycle process.
-
-They go into a select number of system life cycle processes, specifically:
-
-Decision Management,
-
-Risk Management,
-
-Configuration Management,
-
-Information Management, and
-
-System Analysis.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html b/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html
deleted file mode 100644
index a4ddf355693ab792532ec9474b5ef614a325f33a..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html
+++ /dev/null
@@ -1,254 +0,0 @@
-
-
-
-
- System Architecture Definition
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System Architecture Definition
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.4.1] The purpose of the Architecture Definition process is to generate system architecture alternatives, to select one or more alternative(s) that frame stakeholder concerns and meet system requirements, and to express this in a set of consistent views. See detailed description in the INCOSE Handbook v.5, page 118
Project-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html b/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html
deleted file mode 100644
index 858d4292c98fb921d636317d7363cc33c4c242c8..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-
-
- Measurement data
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Measurement data
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Measurement data from all applicable life cycle processes, including: critical performance measurement data, organizational measurement data, and project measurement data.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html b/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html
deleted file mode 100644
index 4e75f1d9b7e34994d8b95f51fd8db7c7fc5867e4..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html
+++ /dev/null
@@ -1,210 +0,0 @@
-
-
-
-
- Portfolio Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Portfolio Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.3.1] The purpose of the Portfolio Management process is to initiate and sustain necessary, sufficient and suitable projects in order to meet the strategic objectives of the organization. See detailed description in the INCOSE Handbook v.5, page 57
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html b/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html
deleted file mode 100644
index aa040529d37e30ec55c9fe502c94ea58bda59d89..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html
+++ /dev/null
@@ -1,185 +0,0 @@
-
-
-
-
- Configuration Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Configuration Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.5.1] The purpose of the Configuration Management process is to manage and control system elements and configurations over the life cycle. CM also manages consistency between a product and its associated configuration definition. See detailed description in the INCOSE Handbook v.5, page 87
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html b/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html
deleted file mode 100644
index f0d9f419ce42697c2587ff29602c144b24b95c04..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html
+++ /dev/null
@@ -1,220 +0,0 @@
-
-
-
-
- Supply
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Supply
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.1.2.1] The purpose of the Supply process is to provide an acquirer with a product or service that meets agreed requirements. See detailed description in the INCOSE Handbook v.5, page 48
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html b/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html
deleted file mode 100644
index b666512958ab2de7886b208e45a4408b96eab016..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html
+++ /dev/null
@@ -1,230 +0,0 @@
-
-
-
-
- Project Planning
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project Planning
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.1.1] The purpose of the Project Planning process is to produce and coordinate effective and workable plans. See detailed description in the INCOSE Handbook v.5, page 70
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html b/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html
deleted file mode 100644
index 0141ef94ab04730706276839f64812bc88dd2510..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Supply agreement
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Supply agreement
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Mutual acknowledgment of terms and conditions under which a working relationship is conducted between a supplier and an acquirer. (Adapted from ISO/IEC/IEEE 15288++ 2023)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html b/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html
deleted file mode 100644
index 7594ba41586689db794bb1851275cafe12798ad2..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Supplied system or system element
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Supplied system or system element
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
System or system element (product or service) delivered from a supplier to an acquirer consistent with the delivery conditions of the supply agreement.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html b/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html
deleted file mode 100644
index 89314dc883a2f3bac42d3879f93d3371795ba311..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html
+++ /dev/null
@@ -1,219 +0,0 @@
-
-
-
-
- System Requirements Definition
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System Requirements Definition
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.3.1] The purpose of the System Requirements Definition process is to transform the stakeholder, useroriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user. See detailed description in the INCOSE Handbook v.5, page 112
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html b/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html
deleted file mode 100644
index 2bcc5841326698c8fa51522bd7364e4307135eea..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html
+++ /dev/null
@@ -1,168 +0,0 @@
-
-
-
-
- Decision Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Decision Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As defined by ISO/IEC/IEEE 15288:2023, [6.3.3.1] The purpose of the Decision Management process is to provide a structured, analytical framework for objectively identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life cycle and select the most beneficial course of action. See detailed description in the INCOSE Handbook v.5, page 78
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html b/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html
deleted file mode 100644
index 2a363055e4a7eade4ae91bb6620cb4bb92b02057..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Standards
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Standards
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
This handbook and relevant industry, country, military, acquirer, and other specifications and standards. Includes new knowledge from industry sponsored knowledge networks.
As stated in ISO/IEC/IEEE 15288:2023, [6.4.2.1] The purpose of the Stakeholder Needs and Requirements Definition process is to define the stakeholder requirements for a system that can provide the capabilities needed by users and other stakeholders in a defined environment. See detailed description in the INCOSE Handbook v.5, page 107
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html b/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html
deleted file mode 100644
index dae456b23cad296ee26ad155181881cf0173a1fa..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html
+++ /dev/null
@@ -1,222 +0,0 @@
-
-
-
-
- Traceability mapping
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Traceability mapping
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Records the relationship between two or more artifacts of the development process (e.g., requirements, functions, system elements, verifications, and validations, tasks). (Adapted from ISO/IEC/IEEE 24765++ 2017)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-7faacad3e03ed1ec60459a1f43f289b4.html b/id-iso15288-model/elements/id-7faacad3e03ed1ec60459a1f43f289b4.html
deleted file mode 100644
index daef83d8f02ca012dfafc7ce95062939156682c6..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-7faacad3e03ed1ec60459a1f43f289b4.html
+++ /dev/null
@@ -1,100 +0,0 @@
-
-
-
-
- Controls
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Controls
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Controls represent those typical inputs and outputs that control, or limit, the execution of the system life cycle processes. They either come in as an external (EXT) typical input or from one or more life cycle processes.
-
-They go into every system life cycle process and are shown in Figure 2.11.
-
---> Not Used in the model, <<enables>> dependency used on BusinessObject (similar to InputTo).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-7fc6a22c8bb16978236ecdd0da8cbb66.html b/id-iso15288-model/elements/id-7fc6a22c8bb16978236ecdd0da8cbb66.html
deleted file mode 100644
index 4f14df053d2abf48fbbd6bbb21e1d51faaa2e9a6..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-7fc6a22c8bb16978236ecdd0da8cbb66.html
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html b/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html
deleted file mode 100644
index db64e242bd3cf54a18735425dffb4dcff180d525..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html
+++ /dev/null
@@ -1,184 +0,0 @@
-
-
-
-
- System Analysis
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System Analysis
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288, [6.4.6.1] The purpose of the System Analysis process is to provide a rigorous basis of data and information for technical understanding to aid decision-�making across the life cycle. See detailed description in the INCOSE Handbook v.5, page 129
Structured collection of the requirements [characteristics, context, concepts, constraints and priorities] of the stakeholder and the relationship to the external environment. (ISO/IEC/IEEE 29148, 2018)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html b/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html
deleted file mode 100644
index 9428ccdd65abc967c0d4933b14251006caf4b33b..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Project budget
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project budget
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Estimate of the costs associated with a particular project. Includes labor, infrastructure, acquisition, and enabling system costs along with reserves for risk management.
Provides results of configuration management verifications and audits to ensure adequate traceability, control, and visibility. It includes evaluation criteria.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html b/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html
deleted file mode 100644
index fae9860063043ef9f83b20d96c743d128a6cbcc5..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Verification criteria
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Verification criteria
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
The verification criteria (the measures to be assessed), who will perform verification activities, and the verification environments of the system-of-interest.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html b/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html
deleted file mode 100644
index ba85a680962c85571881dd257a3c5d43eca7f77f..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html
+++ /dev/null
@@ -1,160 +0,0 @@
-
-
-
-
- Human Resource Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Human Resource Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.4.1] The purpose of the Human Resource Management process is to provide the organization with necessary human resources and to maintain their competencies, consistent with business needs. See detailed description in the INCOSE Handbook v.5, page 60
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html b/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html
deleted file mode 100644
index ae889fbd706b4959e6ae852a9e0633c578e37a48..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Risk register
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Risk register
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A repository that supports the availability for use and communication of all relevant risk information in a timely, complete, valid, and, if required, confidential manner.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9a84ecacbb7b444a8493074eedf1f0af.html b/id-iso15288-model/elements/id-9a84ecacbb7b444a8493074eedf1f0af.html
deleted file mode 100644
index 52fd3f2197e6919b80da96f3ec7fb0e00221bdb5..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-9a84ecacbb7b444a8493074eedf1f0af.html
+++ /dev/null
@@ -1,385 +0,0 @@
-
-
-
-
- Process Blueprint
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Process Blueprint
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
This process represents a class to which every other system life cycle process belongs. Every other life cycle proccess inherits relationships to inputs and outputs of this process.
-Rationale: p. 42 (controls, enablers), pp. 317, 318 (situational) of INCOSE Handbook v. 5.
-
Organizational-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html b/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html
deleted file mode 100644
index aca4fc36940e4321841b7e02dc7541cf1e76e699..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html
+++ /dev/null
@@ -1,155 +0,0 @@
-
-
-
-
- System viewpoints views and models
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System viewpoints views and models
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Definitions of viewpoints to document the procedures for creating, interpreting, analyzing, and evaluating architectural data. One or more views of the system. Each architectural view is a representation of the complete system from the perspective of one or more system concerns, for its stakeholders. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html b/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html
deleted file mode 100644
index e931bfbe17cf107f16f281781a6e44e41394e6c1..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Acquisition agreement
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Acquisition agreement
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Mutual acknowledgment of terms and conditions under which a working relationship is conducted between an acquirer and a supplier. (Adapted from ISO/IEC/IEEE 15288, 2023).
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html b/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html
deleted file mode 100644
index 2e7c81c68d1faabad4a0e1896e433c087091e6a5..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html
+++ /dev/null
@@ -1,200 +0,0 @@
-
-
-
-
- Acquisition
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Acquisition
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.1.1.1] The purpose of the Acquisition process is to obtain a product or service in accordance with the acquirer's requirements. See detailed description in the INCOSE Handbook v.5, page 45
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html b/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html
deleted file mode 100644
index 1ef0857259b361e55c328ab8294936a3265f4c3b..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html
+++ /dev/null
@@ -1,224 +0,0 @@
-
-
-
-
- Implementation
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Implementation
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.7.1] The purpose of the Implementation process is to realize a specified system element. See detailed description in the INCOSE Handbook v.5, page 132
An account prepared for interested parties in order to communicate the status, results, and outcomes of the stakeholder needs and requirements definition activities.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html b/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html
deleted file mode 100644
index 1c73aea728de09a2e8dafd7b327e7b2fe68d333e..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Decision register
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Decision register
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A repository that supports the availability for use and communication of all relevant decision information in a timely, complete, valid, and, if required, confidential manner.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html b/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html
deleted file mode 100644
index b4e489bb64094dc39dfec8562a97850722388c61..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html
+++ /dev/null
@@ -1,219 +0,0 @@
-
-
-
-
- Business or Mission Analysis
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Business or Mission Analysis
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.1.1] The purpose of the Business or Mission Analysis process is to define the business or mission problem or opportunity, characterize the solution space, and determine potential solution class(es) that could address a problem or take advantage of an opportunity. See detailed description in the INCOSE Handbook v.5, page 103
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html b/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html
deleted file mode 100644
index 0123135396ee8c23e55347eeeb403e681cece9ca..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html
+++ /dev/null
@@ -1,204 +0,0 @@
-
-
-
-
- Disposal
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Disposal
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.14.1] The purpose of the Disposal process is to end the existence of a system element or system for a specified intended use, appropriately handle replaced or retired elements, and to properly attend to identified critical disposal needs. See detailed description in the INCOSE Handbook v.5, page 156
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html b/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html
deleted file mode 100644
index 9799e25d983c1cd943a7194b521e4a8b370cacee..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Validation criteria
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Validation criteria
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
The validation criteria (the measures to be assessed), who will perform validation activities++ and the validation environments of the system-of-interest.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-bad4fe0468b4414299ff5323f611b026.html b/id-iso15288-model/elements/id-bad4fe0468b4414299ff5323f611b026.html
deleted file mode 100644
index c2427021bca690f399130ed29731dc74e67f9f50..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-bad4fe0468b4414299ff5323f611b026.html
+++ /dev/null
@@ -1,140 +0,0 @@
-
-
-
-
- Organization Reports
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Organization Reports
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Reports from all applicable organization life cycle processes, including: life cycle model management report, infrastructure management report, portfolio management report, human resource management report, quality management report, and knowledge management report. (INCOSE Handbook v.5, p. 327)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html b/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html
deleted file mode 100644
index 0a516f4c0ad30b705a784725d026a96ec72aa5e3..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Project schedule
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project schedule
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A linked list of a project milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html b/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html
deleted file mode 100644
index 42eedac762b4cf0e92c140e73c9714c3844c878e..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html
+++ /dev/null
@@ -1,147 +0,0 @@
-
-
-
-
- System design rationale
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System design rationale
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Rationale for design selection, system element selection, and allocation between system requirements and system elements. Includes rationale of major selected implementation options and enablers.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html b/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html
deleted file mode 100644
index a358dc5cb786c277f2626ab599e0323e782b68cf..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
-
- System requirements
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- System requirements
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Structured collection of the requirements [functions, performance, design constraints, and other attributes] for the system and its operational environments and external interfaces. (ISO/IEC/IEEE 29148, 2018)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html b/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html
deleted file mode 100644
index 26c97e61f5411f0540ccfcfc944dafd0b36dc836..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html
+++ /dev/null
@@ -1,175 +0,0 @@
-
-
-
-
- Knowledge Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Knowledge Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.6.1] The purpose of the Knowledge Management process is to create the capability and assets that enable the organization to exploit opportunities to re-�apply existing knowledge. See detailed description in the INCOSE Handbook v.5, page 67
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html b/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html
deleted file mode 100644
index 126970292236181f5658b61177dd8165df54f5da..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Supply response
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Supply response
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Prepared by a potential supplier to support the offer of a contract bid, including cost, schedule, risk statements, methodology to satisfy the request for supply, experiences and capabilities, any recommendations to tailor the request for supply or contract, and the signature of the supplier's approving authority. Informally, may be prepared within an organization. (Adapted from ISO/IEC/IEEE 15289, 2019)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html b/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html
deleted file mode 100644
index 20b00a4a45873c3ae5d54a17728cd9a16adfeebd..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html
+++ /dev/null
@@ -1,204 +0,0 @@
-
-
-
-
- Operation
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Operation
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.12.1] The purpose of the Operation process is to use the system to deliver its services. See detailed description in the INCOSE Handbook v.5, page 152
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html b/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html
deleted file mode 100644
index cd1c44d5d57da58f00560135451290303523754f..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Measurement register
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Measurement register
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A repository that supports the availability for use and communication of all relevant measures in a timely, complete, valid, and, if required, confidential manner.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html b/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html
deleted file mode 100644
index e5ce0afc30996d7aa734f85a7911d3be74cfee08..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Systems engineering management plan (SEMP)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Systems engineering management plan (SEMP)
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Presents how the project processes and activities are executed to assure the project’s successful completion, and the quality of the deliverable product or service. (Adapted from ISO/IEC/ IEEE 15289, 2019)
Action to eliminate the cause or reduce the likelihood of recurrence of a detected organizational nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1++ 2017)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html b/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html
deleted file mode 100644
index 920eaa5b691a1d3647631941f97bbc9cacd5df54..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html
+++ /dev/null
@@ -1,254 +0,0 @@
-
-
-
-
- Design Definition
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Design Definition
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.5.1] The purpose of the Design Definition process is to provide sufficient detailed data and information about the system and its elements to enable the imple- mentation consistent with architectural entities as defined in models and views of the system architecture. See detailed description in the INCOSE Handbook v.5, page 124
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html b/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html
deleted file mode 100644
index 188bde6e7dc72f744622586fe1ed0304dc7eceb4..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html
+++ /dev/null
@@ -1,232 +0,0 @@
-
-
-
-
- Project Assessment and Control
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project Assessment and Control
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.2.1] The purpose of the Project Assessment and Control process is to assess if the plans are aligned and feasible, determine the status of the project, technical and process performance, and direct execution to ensure that the performance is according to plans and schedules, within projected budgets, to satisfy technical objectives.
-
-See detailed description in the INCOSE Handbook v.5, page 75
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html b/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html
deleted file mode 100644
index 4b7aa45ad0d144d4f73745feaa5af8ea74491fb5..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html
+++ /dev/null
@@ -1,179 +0,0 @@
-
-
-
-
- Change request
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Change request
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017).
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html b/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html
deleted file mode 100644
index 1e743b900a8e744334bdf65a61c5cee0878be1ed..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html
+++ /dev/null
@@ -1,244 +0,0 @@
-
-
-
-
- Verification
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Verification
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.9.1] The purpose of the Verification process is to provide objective evidence that a system or system element fulfils its specified requirements and characteristics. See detailed description in the INCOSE Handbook v.4, page 138
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html b/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html
deleted file mode 100644
index 309e908350a54f3dfda0a7127d4cb4c7b9ec953d..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html
+++ /dev/null
@@ -1,160 +0,0 @@
-
-
-
-
- Risk Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Risk Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.3.4.1] The purpose of the Risk Management process is to identify, analyze, treat and monitor the risks continually. See detailed description in the INCOSE Handbook v.5, page 81
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html b/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html
deleted file mode 100644
index a9b2164c5d937add96edfa9fca293fac5a78c949..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html
+++ /dev/null
@@ -1,160 +0,0 @@
-
-
-
-
- Infrastructure Management
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Infrastructure Management
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.2.2.1] The purpose of the Infrastructure Management process is to provide the infrastructure and services to projects to support organization and project objectives throughout the life cycle. See detailed description in the INCOSE Handbook v.5, page 54
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html b/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html
deleted file mode 100644
index a87631f5e57e5458b399944aa1c0207a033ce113..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html
+++ /dev/null
@@ -1,201 +0,0 @@
-
-
-
-
- External
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- External
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
External represents those typical inputs and outputs that come from, or go to, beyond the set of system life cycle processes (i.e., they do not come from, or go to, another system life cycle process).
-
-Note that these can be either
-
-internal (e.g., Organization strategic plan) or
-
-external (e.g., Applicable laws and regulations) to the organization.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html b/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html
deleted file mode 100644
index a5605630c4f1daa678e6075d8a2590f48666d99e..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Variance or deviation or waiver request
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Variance or deviation or waiver request
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Request, temporary or permanent, to accept a configuration item or other designated item which, during production or after having been submitted for inspection, is found to depart from specified requirements, but is nevertheless considered suitable for use as is or after rework by an approved method. (Adapted from ISO/IEC/IEEE 24765, 2017)
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ed76e7916d4ef81a816657d6bd431667.html b/id-iso15288-model/elements/id-ed76e7916d4ef81a816657d6bd431667.html
deleted file mode 100644
index 89314f6c5419395044e230687d17c65d581d9b6b..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-ed76e7916d4ef81a816657d6bd431667.html
+++ /dev/null
@@ -1,100 +0,0 @@
-
-
-
-
- Enabler
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Enabler
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Enablers represent those typical inputs and outputs that enable, or assist in, the execution of the system life cycle processes. They either come in as an external (EXT) typical input or from one or more life cycle processes.
-
-They go into every system life cycle process and are shown in Figure 2.11.
-
---> Not Used in the model, <<enables>> dependency used on BusinessObject (similar to InputTo).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ed98a9a6fccdaf23b58564d9d0a017d3.html b/id-iso15288-model/elements/id-ed98a9a6fccdaf23b58564d9d0a017d3.html
deleted file mode 100644
index 6c78ad3f65df86da9773c7613c9896abe1c833d5..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-ed98a9a6fccdaf23b58564d9d0a017d3.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html b/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html
deleted file mode 100644
index bc5981f0e0f23e0307e402a92610b173a9776e9f..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html
+++ /dev/null
@@ -1,199 +0,0 @@
-
-
-
-
- Maintenance
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Maintenance
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
As stated in ISO/IEC/IEEE 15288:2023, [6.4.13.1] The purpose of the Maintenance process is to sustain the capability of the system to provide a service. See detailed description in the INCOSE Handbook v.5, page 154
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html b/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html
deleted file mode 100644
index 1b7d5067091780d5d4b0829ac8404b01706eaa0d..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
- Configuration baseline
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Configuration baseline
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Configuration information formally designated at a specific time during the life of a product, product component, service, or service component. (Adapted from ISO/IEC/IEEE 24765, 2017).
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html b/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html
deleted file mode 100644
index 80792cae3a61dc495b9d6fc91b981a24ff42c69c..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
-
- Project control request
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Project control request
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Project directives based on action required due to deviations from the project plan. If assessments are associated with a decision gate, a decision to proceed or not to proceed, is taken.
-
-
-
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html b/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html
deleted file mode 100644
index cccee3dcc8dd7477c682c968e9649c1a93078973..0000000000000000000000000000000000000000
--- a/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-
-
- Information register
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Information register
-
-
- ()
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
A repository that supports the availability for use and communication of all relevant project information artifacts in a timely, complete, valid, and, if required, restricted manner.