|
SPiCE Work Products
|
|
|
 1 Configuration Item
|
| 1 | Item which is maintained under configuration control | | 1.1 | | may include modules, subsystems, libraries, test cases, compilers, data, documentation, physical media, and external interfaces | | 2 | Version identification is maintained | | 3 | Description of the item is available including: | | 3.1 | | type of item | | 3.2 | | associated configuration management library, file, system | | 3.3 | | responsible owner | | 3.4 | | date when placed under configuration control | | 3.5 | | status information (i.e. development, baselined, released) | | 3.6 | | relationship to lower level configured items | | 3.7 | | identification of the change control records | | 3.8 | | identification of change history | | 3.9 | | relationship to previous versions and/or baselines (for recovery, if necessary) | | 3.10 | | approval status information (i.e. development, baselined, released) | | 3.11 | | revision status information (i.e. checked in, checked out, read only) | | |
|
1.1 Product Configuration
|
 1.1 Product Configuration
|
[Spec] [Checklist] |
| |
| 1 | Overview of the system's configuration | | 2 | Defines each element and their position in the architecture of the system | | 3 | Defines the key system interfaces | | 4 | Defines any network considerations | | 5 | Defines the hardware configuration | | 6 | Defines any system performance / parameter settings |
| |
|
|
1.2 Reusable Object
|
|
1.2 Reusable Object
|
[Checklist] |
| |
| 1 | Developed to be | | 1.1 | | reliable | | 1.2 | | data encapsulated | | 2 | An asset and elementary component | | 3 | Designed for interoperability | | 4 | Versions traceable to point of usage | | 5 | Contains status and classification | | 6 | Modification controlled | | 7 | Modifications are downward compatible | | 8 | Specification for usage defined | | 9 | Specification for tailoring defined |
| |
|
|
1.3 Software Item
|
|
1.3 Software Item
|
[Checklist] |
| |
| 1 | Integrated software consisting of: | | 1.1 | | source code | | 1.2 | | software elements | | 1.3 | | executable code | | 1.4 | | configuration files | | 2 | Documentation, which: | | 2.1 | | describes and identifies source code | | 2.2 | | describes and identifies software elements | | 2.3 | | describes and identifies configuration files | | 2.4 | | describes and identifies executable code | | 2.5 | | describes software life-cycle status | | 2.6 | | describes archive and release criteria | | 2.7 | | describes compilation of software units | | 2.8 | | describes building of software item |
| |
|
|
1.4 Knowledge Item
|
|
1.4 Knowledge Item
|
[Checklist] |
| |
| 1 | Explicit piece of experience: | | 1.1 | | documented for sharing | | 1.2 | | controlled and maintained |
| |
|
|
|
|
2 Contract
|
| 1 | Defines what is to be purchased or delivered | | 2 | Identifies time frame for delivery or contracted service dates | | 3 | Identifies any statutory requirements | | 4 | Identifies monetary considerations | | 5 | Identifies any warranty information | | 6 | Identifies any copyright and licensing information (patent, copyright, confidentiality,
proprietary, usage, ownership, warranty and licensing rights associated with all
relevant work products) | | 7 | Identifies any customer service requirements | | 8 | Identifies service level requirements | | 9 | References to any performance and quality expectations / constraints / monitoring | | 10 | Standards and procedures to be used | | 11 | Evidence of review and approval by authorised signatories | | 12 | As appropriate to the contract the following are considered: | | 12.1 | | references to any acceptance criteria | | 12.2 | | references to any special customer needs (i.e., confidentiality requirements, security, hardware, etc.) | | 12.3 | | references to any change management and problem resolution procedures | | 12.4 | | identifies any interfaces to independent agents and subcontractors | | 12.5 | | identifies customer's role in the development and maintenance process | | 12.6 | | identifies resources to be provided by the customer | | |
|
2.1 Commitment / Agreement
|
|
2.1 Commitment / Agreement
|
[Checklist] |
| |
| 1 | Signed off by all parties involved in the commitment / agreement | | 2 | Establishes what the commitment is for | | 3 | Establishes the resources required to fulfill the commitment, such as: | | 3.1 | | time | | 3.2 | | people | | 3.3 | | budget | | 3.4 | | equipment | | 3.5 | | facilities | | 4 | Demonstrates sponsorship and acceptance of the resulting change |
| |
|
|
|
|
3 Data
|
| 1 | Result of applying a measure | | 2 | Available to those who need to know within defined timeframe | | |
|
3.1 Assessment Data
|
|
3.1 Assessment Data
|
[Checklist] |
| |
| 1 | Identifies the objective evidence gathered | | 2 | Rationale for the attribute achievement ratings | | 3 | The set of process profiles resulting from the assessment (i.e. one profile for each process assessed with attributes ratings) | | 4 | The identification of any additional information collected during the assessment that was identified in the assessment input to support process improvement or process capability determination |
| |
|
|
3.2 Asset Use Data
|
|
3.2 Asset Use Data
|
[Checklist] |
| |
| 1 | Identifies used times and dates | | 2 | Identifies the description of the asset, name of the asset or a unique identifier |
| |
|
|
3.3 Benchmarking Data
|
|
3.3 Benchmarking Data
|
[Checklist] |
| |
| 1 | Results of measurement of current performance that allow comparison against
historical or target values | | 2 | Relates to key goals / process / product / market need criteria and information to be benchmarked |
| |
|
|
3.4 Customer Satisfaction Data
|
|
3.4 Customer Satisfaction Data
|
[Checklist] |
| |
| 1 | Relates to levels of customer satisfaction with products and services | | 2 | Results of applying field measures | | 3 | Results of customer satisfaction survey | | 4 | Interview notes | | 5 | Meeting minutes from customer meetings |
| |
|
|
3.5 Personnel Performance Data
|
|
3.5 Personnel Performance Data
|
[Checklist] |
| |
| 1 | Determines attributes of personnel performance to be measured | | 2 | Mechanism to collect data on personnel performance: | | 2.1 | | results of task performance data | | 2.2 | | results of internal customer satisfaction survey | | 2.3 | | interview notes | | 2.4 | | meeting minutes from meetings with personnel |
| |
|
|
3.6 Process Performance Data
|
|
3.6 Process Performance Data
|
[Checklist] |
| |
| 1 | Appropriate to compare process performance against expected values | | 2 | May include records, such as: | | 2.1 | | meeting minutes | | 2.2 | | change records | | 2.3 | | quality records | | 3 | May include data on: | | 3.1 | | resource usage | | 3.2 | | process adherence | | 3.3 | | extent to which quality criteria are met | | 3.4 | | extent to which task completion criteria are met |
| |
|
|
3.7 Test Data
|
|
3.7 Test Data
|
[Checklist] |
| |
| 1 | Set of input values that are associated with a set of test cases or test procedures | | 2 | Indicate scope of validity | | 3 | Identifies associated test cases |
| |
|
|
|
|
4 Design
|
| 1 | Describes the overall product / system structure | | 2 | Identifies the required product / system elements | | 3 | Identifies the relationship between elements | | 4 | Consideration is given to: | | 4.1 | | any required performance characteristics | | 4.2 | | any required interfaces | | 4.3 | | any required security characteristics | | |
|
4.1 Database Design
|
|
4.1 Database Design
|
[Spec] [Checklist] |
| |
| 1 | Definition of design characteristics: | | 1.1 | | database management system used | | 1.2 | | type of system (relational, hierarchical, object oriented, networked) | | 1.3 | | format of records, tables, objects | | 1.4 | | database access mode | | 1.5 | | associated software (programs, user screen formats, reports) | | 1.6 | | supported database language | | 2 | Definition of logical and physical views, models: | | 2.1 | | records (data layouts, fields, tables, structures) | | 2.2 | | field names and definitions | | 2.3 | | data definitions, classes, structure, etc. | | 2.4 | | entity / relationships | | 2.5 | | classes, inheritance scheme | | 3 | Definition of user views: | | 3.1 | | screen layouts | | 3.2 | | field access | | 3.3 | | data access | | 3.4 | | commands | | 4 | Input / output interface considerations | | 5 | Database usage information (contents, application systems, usage restrictions, etc.) | | 6 | Identifies constraints | | 6.1 | | security considerations | | 6.2 | | data access considerations | | 6.3 | | back-up and recovery considerations | | 6.4 | | system restart considerations | | 6.5 | | system generations considerations | | 6.6 | | performance considerations |
| |
|
|
4.2 Domain Architecture
|
|
4.2 Domain Architecture
|
[Checklist] |
| |
| 1 | Identifies domain model(s) tailored from | | 2 | Identifies asset specifications | | 3 | Definition of boundaries and relationships with other domains (Domain Interface Specification) | | 4 | Identifies domain vocabulary | | 5 | Identifies the domain representation standard | | 6 | Provide an overview of the functions, features capabilities and concepts in the domains |
| |
|
|
4.3 Domain Model
|
|
4.3 Domain Model
|
[Checklist] |
| |
| 1 | Must provide a clear explanation and description, on usage and properties, for reuse purposes | | 2 | Identifies the management and structures used in the model | | 3 | Includes features, capabilities, concepts and functions |
| |
|
|
4.4 High Level Software Design
|
|
4.4 High Level Software Design
|
[Spec] [Checklist] |
| |
| 1 | Describes the overall software structure | | 2 | Identifies the required software elements | | 3 | Identifies the relationship between software elements | | 4 | Consideration is given to: | | 4.1 | | any required software performance characteristics | | 4.2 | | any required software interfaces | | 4.3 | | any required security characteristics required | | 4.4 | | any database design requirements | | 4.5 | | any required error handling and recovery attributes |
| |
|
|
4.5 Low Level Software Design
|
|
4.5 Low Level Software Design
|
[Spec] [Checklist] |
| |
| 1 | Provides detailed design (could be represented as a prototype, flow chart, entity relationship diagram, pseudo code, etc.) | | 2 | Provides format of input / output data | | 3 | Provides specification of data storage needs | | 4 | Establishes required data naming conventions | | 5 | Defines the format of required data structures | | 6 | Defines the data fields and purpose of each required data element | | 7 | Provides the specifications of the program structure |
| |
|
|
4.6 System Architecture Design
|
|
4.6 System Architecture Design
|
[Spec] [Checklist] |
| |
| 1 | Provides an overview of all system design | | 2 | Describes the interrelationship between system elements | | 3 | Describes the relationship between the system elements and the software | | 4 | Specifies the design for each required system element, consideration is given to things like: | | 4.1 | | memory / capacity requirements | | 4.2 | | hardware interfaces requirements | | 4.3 | | user interfaces requirements | | 4.4 | | external system interface requirements | | 4.5 | | performance requirements | | 4.6 | | commands structures | | 4.7 | | security / data protection characteristics | | 4.8 | | system parameter settings | | 4.9 | | manual operations | | 4.10 | | reusable components | | 5 | Mapping of requirements to system elements |
| |
|
|
4.7 Organisational Structure
|
|
4.7 Organisational Structure
|
[Checklist] |
| |
| 1 | Describes an organisation: | | 1.1 | | structure | | 1.2 | | roles | | 1.3 | | responsibilities |
| |
|
|
|
|
5 Goals
|
| 1 | Identifies the objective to be achieved | | 2 | Identifies who is expected to achieve the goal | | 3 | Identifies any incremental supporting goals | | 4 | Identifies any conditions / constraints | | 5 | Identifies the timeframe for achievement | | 6 | Are reasonable and achievable within the resources allocated | | 7 | Are current, established for current project, organisation | | 8 | Are optimised to support known performance criteria and plans | | |
|
5.1 Assessment Goals
|
| Remarks |
| No Requirements additional to Goals (Generic) |
|
5.2 Business Goals
|
|
5.2 Business Goals
|
[Checklist] |
| |
| 1 | Contains a description of the goal | | 2 | Identifies a requirement specification for the business need | | 3 | Identifies association and interfaces to other goals | | 4 | Identifies the level of degree of the need and effect on the business of not having
that need |
| |
|
|
5.3 Core Values Statement
|
|
5.3 Core Values Statement
|
[Checklist] |
| |
| 1 | Defines the values that govern the relationships between internal and external stakeholders | | 2 | Is authorised at the highest level |
| |
|
|
5.4 Mission Statement
|
|
5.4 Mission Statement
|
[Checklist] |
| |
| 1 | Identifies the reasons for the existence of the enterprise | | 2 | Informs the development of the core values and vision statement | | 3 | Is authorised at the highest level |
| |
|
|
5.5 Vision Statement
|
|
5.5 Vision Statement
|
[Checklist] |
| |
| 1 | Identifies the main objectives to be achieved | | 2 | Provides information on the overall strategy for the organisational unit, organisation or business | | 3 | Is authorised at the highest level |
| |
|
|
|
|
6 User Documentation
|
| 1 | Identifies: | | 1.1 | | external documents | | 1.2 | | internal documents | | 1.3 | | current site distribution and maintenance list maintained | | 2 | Documentation kept synchronised with latest product release | | 3 | Addresses technical issues | | |
|
6.1 Customer Manual
|
|
6.1 Customer Manual
|
[Checklist] |
| |
| 1 | Takes account of: | | 1.1 | | audience and task profiles | | 1.2 | | the environment in which the information will be used | | 1.3 | | convenience to users | | 1.4 | | the range of technical facilities, including resources and the product, available for developing and delivering on-screen docu-mentation | | 1.5 | | information characteristics | | 1.6 | | cost of delivery and maintainability | | 2 | Includes information needed for operation of the system, including but not limited to: | | 2.1 | | product and version information | | 2.2 | | instructions for handling the system | | 2.3 | | initial familiarisation information | | 2.4 | | non-trivial examples of the use | | 2.5 | | structured reference material, particularly for advanced features of the software | | 2.6 | | checklists | | 2.7 | | guides to use input devices |
| |
|
|
6.2 Handling and Storage Guide
|
|
6.2 Handling and Storage Guide
|
[Checklist] |
| |
| 1 | Defines the tasks to perform in handling and storing products including: | | 1.1 | | providing for master copies of code and documentation | | 1.2 | | disaster recovery | | 1.3 | | addressing appropriate critical safety and security issues | | 2 | Provides a description of how to store the product including: | | 2.1 | | storage environment required | | 2.2 | | the protection media to use | | 2.3 | | packing materials required | | 2.4 | | what items need to be stored | | 2.5 | | assessments to be done on stored product | | 3 | Provides retrieval instructions |
| |
|
|
6.3 Installation Guide
|
|
6.3 Installation Guide
|
[Checklist] |
| |
| 1 | Tasks for loading / installing product sequentially order by execution requirements: | | 1.1 | | downloading of software from delivery files | | 1.2 | | up-loading to appropriate software to files, folders, libraries, etc. | | 1.3 | | partial or upgrade installation instructions, where applicable | | 1.4 | | initialisation procedures | | 1.5 | | conversion procedures | | 1.6 | | customisation / configuration procedures | | 1.7 | | verification procedures | | 1.8 | | bring-up procedures | | 1.9 | | operations instructions | | 2 | Installation requirements identified: | | 2.1 | | associated hardware, software, customer documentation | | 2.2 | | conversion programs and instructions | | 2.3 | | initialisation programs, system generation information | | 2.4 | | components and descriptions | | 2.5 | | minimum configuration of hardware / software required | | 2.6 | | backup / recovery instructions | | 2.7 | | validation programs | | 2.8 | | configuration parameters (e.g. size requirements, memory) | | 3 | Customer / technical support contacts | | 4 | Troubleshooting guide | | 5 | Rollback plan |
| |
|
| Remarks |
| Merg with Product Operation Guide |
|
6.4 Training Material
|
|
6.4 Training Material
|
[Checklist] |
| |
| 1 | Updated and available for new releases | | 2 | Coverage of system, application, operations, maintenance as appropriate to the application | | 3 | Courses listings and availability |
| |
|
|
6.5 Product Operation Guide
|
|
6.5 Product Operation Guide
|
[Spec] [Checklist] |
| |
| 1 | Criteria for operational use | | 2 | Provides a description of how to operate the product including: | | 2.1 | | operational environment required | | 2.2 | | supporting tools and material (e.g. user manuals) required | | 2.3 | | possible safety warnings | | 2.4 | | start-up preparations and sequence | | 2.5 | | frequently asked questions (FAQ) | | 2.6 | | sources of further information and help to operate the product | | 3 | Certification and safety approvals | | 4 | Warranty and replacement instructions |
| |
|
| Remarks |
| ALIAS: System Administrator Manual |
|
|
|
7 Measure
|
| 1 | Quantitative or qualitative attribute for a product or process | | 2 | Defines the method for collecting data | | 3 | Understood by those expected to use them | | 4 | Provides value to the organisation / project | | 5 | References any relevant goals | | 6 | Non-disruptive to the work flow | | 7 | Appropriate to the process, life cycle model, organisation | | 8 | Has appropriate analysis and commentary to allow meaningful interpretation by users | | |
|
7.1 Customer Satisfaction Survey
|
|
7.1 Customer Satisfaction Survey
|
[Checklist] |
| |
| 1 | Mechanism to collect data on customer satisfaction | | 2 | Identifies customers to be contacted | | 3 | Identifies the data to be collected from the customer | | 4 | Target date for responses | | 5 | Identifies products/services under investigation | | 6 | Methods to analyse feedback |
| |
|
|
7.2 Field Measure
|
|
7.2 Field Measure
|
[Checklist] |
| |
| 1 | Identifies attributes of system's operation at field locations, such as: | | 1.1 | | field defects | | 1.2 | | performance against defined service level measures | | 1.3 | | system ability to meet defined customer requirements | | 1.4 | | support time required | | 1.5 | | user complaints (may be third party users) | | 1.6 | | customers requests for help | | 1.7 | | performance trends | | 1.8 | | problem reports | | 1.9 | | enhancements requested |
| |
|
|
7.4 Process Measure
|
| | |
