1-3 | Scope, normative references and terms | 0 |
4 | Declare the conformance claim: full conformance to outcomes or to tasks, or tailored conformance | 0 |
5 | Key concepts: software systems, organisations and projects, life cycle stages, processes and their use | 0 |
6.1.1 | Acquisition process: obtain a product or service that meets the acquirer's requirements | 0 |
6.1.2 | Supply process: provide an acquirer with a product or service that meets the agreed requirements | 0 |
6.2.1 | Life Cycle Model Management process: define, assess and improve the organisation's life cycle policies, processes, models and procedures | 0 |
6.2.2 | Infrastructure Management process: provide and maintain the infrastructure and services projects need | 0 |
6.2.3 | Portfolio Management process: initiate, sustain, redirect and close projects against the organisation's strategy | 0 |
6.2.4 | Human Resource Management process: identify, develop and provide the skills projects need | 0 |
6.2.5 | Quality Management process: set quality policy, objectives and procedures and improve them from results | 0 |
6.2.6 | Knowledge Management process: build and share the knowledge, skills and knowledge assets the organisation can reuse | 0 |
6.3.1 | Project Planning process: produce and coordinate workable plans and activate them | 0 |
6.3.2 | Project Assessment and Control process: assess progress and performance and direct corrective action | 0 |
6.3.3 | Decision Management process: analyse alternatives objectively and record the decision and its rationale | 0 |
6.3.4 | Risk Management process: identify, analyse, treat and monitor risks continually | 0 |
6.3.5 | Configuration Management process: identify, baseline, control, account for, audit and release configuration items | 0 |
6.3.6 | Information Management process: generate, maintain and provide information to designated stakeholders | 0 |
6.3.7 | Measurement process: collect, analyse and report objective data to support management and show quality | 0 |
6.3.8 | Quality Assurance process: evaluate products, services and processes and treat incidents and problems | 0 |
6.4.1 | Business or Mission Analysis process: define the problem or opportunity and select the solution class | 0 |
6.4.10 | Transition process: move the system into its operational or other target environment ready for use | 0 |
6.4.11 | Validation process: provide objective evidence that the system in use meets stakeholder requirements and its intended use | 0 |
6.4.12 | Operation process: use the system to deliver its services and support the customer | 0 |
6.4.13 | Maintenance process: sustain the system's capability to provide its service | 0 |
6.4.14 | Disposal process: end the use of a system or element and handle retired elements, data and waste properly | 0 |
6.4.2 | Stakeholder Needs and Requirements Definition process: turn stakeholder needs into agreed stakeholder requirements | 0 |
6.4.3 | System/Software Requirements Definition process: specify a measurable technical solution view | 0 |
6.4.4 | Architecture Definition process: develop, assess and select an architecture expressed in consistent views | 0 |
6.4.5 | Design Definition process: give enough detail about each element to implement it consistently with the architecture | 0 |
6.4.6 | System Analysis process: provide rigorous data and analysis to support technical decisions | 0 |
6.4.7 | Implementation process: realise each specified software system element | 0 |
6.4.8 | Integration process: assemble implemented elements into a system that meets requirements, architecture and design | 0 |
6.4.9 | Verification process: provide objective evidence that the system or element meets its specified requirements | 0 |
A | Run the tailoring process when processes are adapted to the project or organisation | 0 |
B-I | Informative annexes: information items, process reference model, process constructs and views, architecture modelling, systems of systems, agile, mapping from the 2008 edition | 0 |