Enterprise Spice Scope
- 1. Enterprise SPICE Scope Linda Ibrahim
- 2. First Technical Decisions We need to decide Enterprise SPICE scope. This entails the following: What disciplines will Enterprise SPICE address? What standards will be integrated into Enterprise SPICE regarding those agreed disciplines?
- 3. Scope Determination Process Steps to determine Enterprise SPICE initial scope: Develop criteria for additional disciplines and source standards Receive approval from Advisory Board on criteria Request and receive stakeholder inputs on suggested disciplines and source standards Review stakeholder inputs on suggested disciplines and source standards and provide recommendations to Advisory Board Receive approval from Advisory Board on disciplines and source standards to be included (in initial baseline model, in subsequent releases, etc according to prioritization discussions/decisions) Suggest this be accomplished within ~3 months Upon completion of scope determination, Technical Author Team and Authors will develop plan for product development
- 4. Discipline Scope Current discipline scope for Enterprise SPICE, based on disciplines addressed in the iCMM and its extensions, includes: full lifecycle software engineering, full lifecycle systems engineering, acquisition, quality management, enterprise leadership and strategic processes, integrated process/product development, safety and security Examples of additional disciplines that might be considered: service management, human resource management, financial/ investment management, supply chain management, marketing, manufacturing, or other broad enterprise processes (etc) Discipline selection will be determined by Enterprise SPICE Advisory Board based on recommendations of collaborators and stakeholders. Criteria for discipline selection might include: relevance to stakeholder enterprises, perceived need for assessing processes in these disciplines in stakeholder enterprises, value of including these disciplines in enterprise assessments, etc. It is recommended disciplines be broad in focus, not industry-specific . It is recommended disciplines be prioritized in terms of criticality or need for inclusion.
- 5. Discipline Scope Discussion Questions What criteria should be used to decide Enterprise SPICE discipline scope? What disciplines might be included in Enterprise SPICE?
- 6. Source Material Sources: Once discipline scope is decided, source documents and reference documents need to be selected for agreed discipline scope Source documents are documents from which Enterprise SPICE practices are derived. Mapping of Enterprise SPICE practices to source practices is required and coverage of source documents, at an appropriate level of detail, will be demonstrated. Reference documents are documents identified as useful in developing best practice in certain areas, but full coverage and detailed mapping is not required. Source material will be determined by Enterprise SPICE Advisory Board based on recommendations of Enterprise SPICE collaborators and stakeholders. Criteria recommended for source material selection: only major, essential, widely-recognized standards/models be selected as source documents number of sources for a discipline limited to 3 to 5 for a given area.
- 7. Current Source Material Current Source Material, based on disciplines in iCMM and its extensions, includes 18 sources : Four ISO Standards: ISO 9001:2000 Quality Management Systems ISO/IEC 12207* Software life cycle processes (ISO/IEC 15504-5) ISO/IEC 15288 ** System Life Cycle Processes (ISO/IEC 15504-6) ISO/IEC 15504 ** Process assessment Performance Excellence Criteria: Malcolm Baldrige National Quality Award/President’s Quality Award Criteria ** Five Capability Models: EIA 731 Systems Engineering Capability CMMI CMM Integrated SW-CMM CMM for Software SA-CMM Software Acquisition CMM SE-CMM Systems Engineering CMM * Need to address 12207 amendments ** selected aspects of human resource management not currently in iCMM scope
- 8. Current Source Material (continued) Four Safety Sources: MIL-STD-882C: System Safety Program Requirements MIL-STD-882D: Standard Practice for System Safety IEC 61508: Functional Safety of Electrical/ Electronic/ Programmable Electronic Systems DEF STAN 00-56: Safety Mgmt Requirements for Defence Systems Four Security Sources: ISO 17799: Information Technology - Code of practice for information security management ISO 15408: The Common Criteria - Mapping of Assurance Levels and Families ISO/IEC 21827: SSE-CMM: Systems Security Engineering CMM NIST 800-30: Risk Mgmt Guide for Information Technology Systems
- 9. Source Material Discussion Questions What criteria should be used to decide Enterprise SPICE source standards? What source standards might be included in Enterprise SPICE?
- 10. Scope Prioritization Phases: Enterprise SPICE may evolve through phases to address broadening scope or evolving needs over time, and based on experience in enterprise assessments, e.g., Phase 1: Enterprise SPICE scope initially includes the baseline disciplines and standards/models (latest versions) addressed in the iCMM and extensions. Phase 2: Enterprise SPICE scope additionally includes service management plus any other high priority discipline. Phase 3: Enterprise SPICE scope addresses next highest priority set of disciplines.