7. Capability Maturity Model Integration (CMMI) - tud.ttu.ee

More documents

Recommendations

Info

CMMI SE/SW/IPPD/SS v1.1 StandardsMapping – EngineeringEngineering• IEEE 1233, Guide for DevelopingSystem Requirements Specifications• IEEE 1362, Guide for Concept ofOperations Document• IEEE 1471, Architectural Descriptionof Software Intensive Systems• IEEE 830, Software RequirementsSpecifications• IEEE 1016, Software DesignDescriptions• IEEE 1012, Software Verification andValidation• IEEE 1008, Software Unit Testing• ISO/IEC 15288, System Life Cycle Processes• IEEE 12207.0, Software Life Cycle Processes• IEEE 12207.1, Guide to Software Life CycleProcesses—Life Cycle Data• IEEE 12207.2, Guide to Software Life CycleProcesses—Implementation Considerations• IEEE 1228, Software Safety Plans• IEEE 1063, Software User Documentation• IEEE 1219, Software Maintenance• IEEE 1320.1,.2, IDEF0, IDEF1X97• IEEE 1420.1, Data Model for Reuse LibraryInteroperability115CMMI SE/SW/IPPD/SS v1.1 StandardsMapping – SupportSupport• IEEE 828, Software ConfigurationManagement Plans• IEEE 730, Software QualityAssurance Plans• IEEE 982.1, Dictionary of Measuresto Produce Reliable Software• IEEE 1045, Software ProductivityMetrics• IEEE 1061, Software Quality MetricsMethodology• IEEE 1219, Software Maintenance• ISO/IEC 15288, System Life CycleProcesses• IEEE 12207.0, Software Life CycleProcesses• IEEE 12207.1, Guide to Software LifeCycle Processes—Life Cycle Data• IEEE 12207.2, Guide to Software LifeCycle Processes—ImplementationConsiderations• IEEE 1465 (ISO/IEC 12119) -Software Packages - QualityRequirements and Testing• IEEE 14143.1 (ISO/IEC 1443-1) -Functional Size Measurement - Part1: Definition of Concepts11658
An Example - RequirementsDevelopment SP 2.1-1 Establish Product andProduct Component Requirements– Establish and maintain, from thecustomer requirements, product andproduct component requirementsessential to product and productcomponent effectiveness andaffordability• ISO/IEC 15288, System Life CycleProcesses– Clause 5.5.3 - Requirements AnalysisProcess• IEEE/EIA 12207.0, Software LifeCycle Processes– Clause 5.3.2 - System RequirementsAnalysis– Clause 5.3.4 - Software requirementsanalysis• IEEE 1233, Guide for DevelopingSystem Requirements Specifications• IEEE 830, Software RequirementsSpecifications117An Example - RequirementsDevelopment SP 2.1-1 Establish Product andProduct Component Requirements– Establish and maintain, from thecustomer requirements, product andproduct component requirementsessential to product and product5.5.3 RequirementscomponentAnalysiseffectivenessProcessandaffordability5.5.3.1 Purpose of the Requirements Analysis ProcessThe purpose of the Requirements Analysis Process is to transform thestakeholder, requirement-driven view of desired services into a technical viewof a required product that could deliver those services.This process builds a representation of a future system that will meetstakeholder requirements and that, as far as constraints permit, does not implyany specific implementation. It results in measurable system requirements thatspecify, from the developer’s perspective, what characteristics it is to possessand with what magnitude in order to satisfy stakeholder requirements.5.5.3.2 Requirements Analysis Process OutcomesAs a result of the successful implementation of the Requirements AnalysisProcess:a) The required characteristics, attributes, and functional and performancerequirements for a product solution are specified.b) Constraints that will affect the architectural design of a system and themeans to realize it are specified.c) The integrity and traceability of system requirements to stakeholderrequirements is achieved.. . .• ISO/IEC 15288, System Life CycleProcesses– Clause 5.5.3 - Requirements AnalysisProcess• IEEE/EIA 12207.0, Software LifeCycle Processes– Clause 5.3.2 - System RequirementsAnalysis– Clause 5.3.4 - Software requirementsanalysis• IEEE 1233, Guide for DevelopingSystem Requirements Specifications• IEEE 830, Software RequirementsSpecifications11859
Page 3 and 4:
The Frameworks Quagmire (present)PS
Page 7 and 8: CMM-i probleemid• Kosemudelil tug
Page 9 and 10: Process Improvement• The improvem
Page 11 and 12: Improvements from AdoptingSW-CMMPer
Page 13 and 14: Enhance customer satisfaction• Me
Page 15 and 16: Gain an industry-wide recognitionfo
Page 17 and 18: The CMMI Product Line ApproachSWIPP
Page 19 and 20: Systems Engineering CapabilityModel
Page 21 and 22: Supplier Sourcing (SS)• Project m
Page 23 and 24: One Model, Two RepresentationsAppen
Page 25 and 26: ExpectedRequiredCMMI Model Structur
Page 27 and 28: Continuous Models• The generic pr
Page 29 and 30: CMMI Model Representations• The C
Page 31 and 32: Continuous Grouping -Process Manage
Page 33 and 34: CMMI Dimensions forMeasuring Improv
Page 35 and 36: Buildingcapability69Maturity Dimens
Page 37 and 38: Content of CMMIBuyer/Supplier Misma
Page 39 and 40: CMMI PAs in PSP and TSPLevel Focus
Page 41 and 42: Specific Goals - RequirementsManage
Page 43 and 44: Expected Materials• The only expe
Page 45 and 46: Specific Practices Associated withS
Page 47 and 48: CMMI Process AreasProcess Areas by
Page 49 and 50: CMMI as an Enterprise Process-Impro
Page 51 and 52: Process Management Process Areas101
Page 53 and 54: CMMI transition project: Schedule
Page 55 and 56: The IEEE/EIA 12207 Software LifeCyc
Page 57: CMMI SE/SW/IPPD/SS v1.1 StandardsM
Page 61 and 62: An Example - RequirementsDevelopmen
Page 63 and 64: Strategy: Establish an Active Measu
Page 65 and 66: Sector Business CaseAdvantagesDoD C
Page 67 and 68: Joint Government / DoD Contractor
Page 69 and 70: SummaryCMMI aids organizations to
show all

7. Capability Maturity Model Integration (CMMI) - tud.ttu.ee

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?