Home
Print 
Contact 
Impressum 
Help
Deliverables

Select here the expected work product items
1.0 Configuration Item    [Checklist] 
 
An entity within a configuration that satisfies an end use function and that can be uniquely identified at a given reference point. [ISO 12207]
 
SuppliersReceivers
 
  
SUP.8 Configuration Management
SUP.10 Change Request Management
SPL.2 Product Release
SUP.8 Configuration Management
SUP.10 Change Request Management

1.1 Product Configuration [Spec]  [Checklist] 
 
SuppliersReceivers
 
SPL.3 Product Acceptance Support
  
SUP.8 Configuration Management
  
  
ENG.3 System Architectural Design
SUP.8 Configuration Management
SUP.10 Change Request Management

1.2 Reusable Object    [Checklist] 
 
SuppliersReceivers
 
REU.1 Asset Management
REU.3 Domain Engineering
  
REU.3 Domain Engineering

1.3 Software Item    [Checklist] 
 
1Integrated software consisting of:
1.1  source code
1.2  software elements
1.3  executable code
1.4  configuration files
2Documentation, 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
 
SuppliersReceivers
 
ENG.7 Software Integration
ENG.7 Software Integration

1.4 Knowledge Item    [Checklist] 
 
1Explicit piece of experience:
1.1  documented for sharing
1.2  controlled and maintained
 
SuppliersReceivers
 
RIN.3 Knowledge Management
  

2.0 Contract    [Checklist] 
 
1Defines what is to be purchased or delivered
2Identifies time frame for delivery or contracted service dates
3Identifies any statutory requirements
4Identifies monetary considerations
5Identifies any warranty information
6Identifies any copyright and licensing information (patent, copyright, confidentiality, proprietary, usage, ownership, warranty and licensing rights associated with all relevant work products)
7Identifies any customer service requirements
8Identifies service level requirements
9References to any performance and quality expectations / constraints / monitoring
10Standards and procedures to be used
11Evidence of review and approval by authorised signatories
12As 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
 
SuppliersReceivers
 
ACQ.3 Contract Agreement
  
  
SPL.1 Supplier Tendering
  
  
  
  
  
  
ACQ.4 Supplier Monitoring
ACQ.5 Customer Acceptance
  
SPL.3 Product Acceptance Support
OPE.2 Customer Support
SUP.4 Joint Review
MAN.3 Project Management
MAN.4 Quality Management

2.1 Commitment / Agreement    [Checklist] 
 
1Signed off by all parties involved in the commitment / agreement
2Establishes what the commitment is for
3Establishes the resources required to fulfill the commitment, such as:
3.1  time
3.2  people
3.3  budget
3.4  equipment
3.5  facilities
4Demonstrates sponsorship and acceptance of the resulting change
 
SuppliersReceivers
 
ACQ.2 Supplier Selection
ACQ.3 Contract Agreement
ACQ.4 Supplier Monitoring
  
SPL.1 Supplier Tendering
  
MAN.1 Organisational Alignment
PIM.3 Process Improvement
RIN.1 Human Resource Management
  
  
ACQ.4 Supplier Monitoring
ACQ.5 Customer Acceptance
  
ENG.1 Requirements Elicitation
  
  
  

3.0 Data    [Checklist] 
 
1Result of applying a measure
2Available to those who need to know within defined timeframe
 
SuppliersReceivers
 
  
SUP.5 Audit

3.1 Assessment Data    [Checklist] 
 
1Identifies the objective evidence gathered
2Rationale for the attribute achievement ratings
3The set of process profiles resulting from the assessment (i.e. one profile for each process assessed with attributes ratings)
4The identification of any additional information collected during the assessment that was identified in the assessment input to support process improvement or process capability determination
 
SuppliersReceivers
 
  
  
PIM.2 Process Assessment
MAN.4 Quality Management
MAN.6 Measurement
PIM.2 Process Assessment

3.2 Asset Use Data    [Checklist] 
 
1Identifies used times and dates
2Identifies the description of the asset, name of the asset or a unique identifier
 
SuppliersReceivers
 
RIN.3 Knowledge Management
REU.1 Asset Management
  
  
  
REU.2 Reuse Program Management

3.3 Benchmarking Data    [Checklist] 
 
1Results of measurement of current performance that allow comparison against historical or target values
2Relates to key goals / process / product / market need criteria and information to be benchmarked
 
SuppliersReceivers
 
SUP.6 Product Evaluation
  
  
MAN.6 Measurement
  
  
SUP.6 Product Evaluation
MAN.2 Organisation Management
MAN.4 Quality Management
MAN.6 Measurement
PIM.1 Process Establishment
PIM.3 Process Improvement

3.4 Customer Satisfaction Data    [Checklist] 
 
1Relates to levels of customer satisfaction with products and services
2Results of applying field measures
3Results of customer satisfaction survey
4Interview notes
5Meeting minutes from customer meetings
 
SuppliersReceivers
 
OPE.2 Customer Support
  
MAN.6 Measurement
  
  
MAN.4 Quality Management
MAN.6 Measurement
PIM.3 Process Improvement

3.5 Personnel Performance Data    [Checklist] 
 
1Determines attributes of personnel performance to be measured
2Mechanism 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    [Checklist] 
 
1Appropriate to compare process performance against expected values
2May include records, such as:
2.1  meeting minutes
2.2  change records
2.3  quality records
3May 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
 
SuppliersReceivers
 
SUP.1 Quality Assurance
  
MAN.2 Organisation Management
  
  
  
PIM.1 Process Establishment
  
SUP.1 Quality Assurance
MAN.1 Organisational Alignment
  
MAN.3 Project Management
MAN.4 Quality Management
MAN.6 Measurement
  
PIM.3 Process Improvement

3.7 Test Data    [Checklist] 
 
1Set of input values that are associated with a set of test cases or test procedures
2Indicate scope of validity
3Identifies associated test cases
 
SuppliersReceivers
 
ENG.6 Software Construction
ENG.7 Software Integration
  
ENG.9 System Integration
ENG.6 Software Construction
ENG.7 Software Integration
ENG.8 Software Testing
ENG.9 System Integration

4.0 Design    [Checklist] 
 
1Describes the overall product / system structure
2Identifies the required product / system elements
3Identifies the relationship between elements
4Consideration is given to:
4.1  any required performance characteristics
4.2  any required interfaces
4.3  any required security characteristics
 
4.1 Database Design [Spec]  [Checklist] 
 
1Definition 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
2Definition 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
3Definition of user views:
3.1  screen layouts
3.2  field access
3.3  data access
3.4  commands
4Input / output interface considerations
5Database usage information (contents, application systems, usage restrictions, etc.)
6Identifies 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
 
SuppliersReceivers
 
ENG.5 Software Design
  

4.2 Domain Architecture    [Checklist] 
 
1Identifies domain model(s) tailored from
2Identifies asset specifications
3Definition of boundaries and relationships with other domains (Domain Interface Specification)
4Identifies domain vocabulary
5Identifies the domain representation standard
6Provide an overview of the functions, features capabilities and concepts in the domains
 
SuppliersReceivers
 
REU.2 Reuse Program Management
REU.3 Domain Engineering
REU.2 Reuse Program Management
REU.3 Domain Engineering

4.3 Domain Model    [Checklist] 
 
1Must provide a clear explanation and description, on usage and properties, for reuse purposes
2Identifies the management and structures used in the model
3Includes features, capabilities, concepts and functions
 
SuppliersReceivers
 
REU.2 Reuse Program Management
REU.3 Domain Engineering
REU.2 Reuse Program Management
REU.3 Domain Engineering

4.4 High Level Software Design [Spec]  [Checklist] 
 
1Describes the overall software structure
2Identifies the required software elements
3Identifies the relationship between software elements
4Consideration 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
 
SuppliersReceivers
 
ENG.5 Software Design
  
  
  
  
ENG.6 Software Construction
ENG.7 Software Integration
ENG.8 Software Testing

4.5 Low Level Software Design [Spec]  [Checklist] 
 
1Provides detailed design (could be represented as a prototype, flow chart, entity relationship diagram, pseudo code, etc.)
2Provides format of input / output data
3Provides specification of data storage needs
4Establishes required data naming conventions
5Defines the format of required data structures
6Defines the data fields and purpose of each required data element
7Provides the specifications of the program structure
 
SuppliersReceivers
 
ENG.5 Software Design
  
  
ENG.6 Software Construction

4.6 System Architecture Design [Spec]  [Checklist] 
 
1Provides an overview of all system design
2Describes the interrelationship between system elements
3Describes the relationship between the system elements and the software
4Specifies 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
5Mapping of requirements to system elements
 
SuppliersReceivers
 
ENG.3 System Architectural Design
  
  
  
  
  
ENG.4 Software Requirements Analysis
ENG.7 Software Integration
ENG.9 System Integration
ENG.11 Software Installation

4.7 Organisational Structure    [Checklist] 
 
1Describes an organisation:
1.1  structure
1.2  roles
1.3  responsibilities
 
SuppliersReceivers
 
  
MAN.2 Organisation Management
MAN.1 Organisational Alignment
MAN.2 Organisation Management

5.0 Goals    [Checklist] 
 
1Identifies the objective to be achieved
2Identifies who is expected to achieve the goal
3Identifies any incremental supporting goals
4Identifies any conditions / constraints
5Identifies the timeframe for achievement
6Are reasonable and achievable within the resources allocated
7Are current, established for current project, organisation
8Are optimised to support known performance criteria and plans
 
SuppliersReceivers
 
PIM.3 Process Improvement
PIM.3 Process Improvement

5.1 Assessment Goals    [Checklist] 
 
 
Notes: No Requirements additional to Goals (Generic)
 
SuppliersReceivers
 
PIM.2 Process Assessment
PIM.2 Process Assessment

5.2 Business Goals    [Checklist] 
 
1Contains a description of the goal
2Identifies a requirement specification for the business need
3Identifies association and interfaces to other goals
4Identifies the level of degree of the need and effect on the business of not having that need
 
SuppliersReceivers
 
  
  
MAN.1 Organisational Alignment
  
  
  
  
ACQ.1 Acquisition Preparation
SPL.1 Supplier Tendering
MAN.1 Organisational Alignment
MAN.2 Organisation Management
RIN.3 Knowledge Management
REU.1 Asset Management
REU.2 Reuse Program Management

5.3 Core Values Statement    [Checklist] 
 
1Defines the values that govern the relationships between internal and external stakeholders
2Is authorised at the highest level
 
SuppliersReceivers
 
MAN.1 Organisational Alignment
MAN.1 Organisational Alignment

5.4 Mission Statement    [Checklist] 
 
1Identifies the reasons for the existence of the enterprise
2Informs the development of the core values and vision statement
3Is authorised at the highest level
 
SuppliersReceivers
 
MAN.1 Organisational Alignment
MAN.1 Organisational Alignment

5.5 Vision Statement    [Checklist] 
 
1Identifies the main objectives to be achieved
2Provides information on the overall strategy for the organisational unit, organisation or business
3Is authorised at the highest level
 
SuppliersReceivers
 
MAN.1 Organisational Alignment
MAN.1 Organisational Alignment

6.0 User Documentation [Spec]  [Checklist] 
 
1Identifies:
1.1  external documents
1.2  internal documents
1.3  current site distribution and maintenance list maintained
2Documentation kept synchronised with latest product release
3Addresses technical issues
 
Notes: Merge with Customer Manual
 
6.1 Customer Manual    [Checklist] 
 
1Takes 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
2Includes 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
 
SuppliersReceivers
 
ENG.6 Software Construction
ENG.8 Software Testing
  
  
OPE.1 Operational Use
  
ENG.8 Software Testing
ENG.10 System Testing
ENG.12 Software and System Maintenance
OPE.1 Operational Use

6.2 Handling and Storage Guide    [Checklist] 
 
1Defines 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
2Provides 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
3Provides retrieval instructions
 
SuppliersReceivers
 
SUP.8 Configuration Management
  

6.3 Installation Guide    [Checklist] 
 
1Tasks 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
2Installation 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)
3Customer / technical support contacts
4Troubleshooting guide
5Rollback plan
 
Notes: Merg with Product Operation Guide
 
SuppliersReceivers
 
  
ENG.11 Software Installation
SPL.3 Product Acceptance Support
ENG.11 Software Installation

6.4 Training Material    [Checklist] 
 
1Updated and available for new releases
2Coverage of system, application, operations, maintenance as appropriate to the application
3Courses listings and availability
 
SuppliersReceivers
 
RIN.2 Training
RIN.2 Training

6.5 Product Operation Guide [Spec]  [Checklist] 
 
1Criteria for operational use
2Provides 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
3Certification and safety approvals
4Warranty and replacement instructions
 
Notes: ALIAS: System Administrator Manual  
SuppliersReceivers
 
OPE.1 Operational Use
OPE.1 Operational Use

7.0 Measure    [Checklist] 
 
1Quantitative or qualitative attribute for a product or process
2Defines the method for collecting data
3Understood by those expected to use them
4Provides value to the organisation / project
5References any relevant goals
6Non-disruptive to the work flow
7Appropriate to the process, life cycle model, organisation
8Has appropriate analysis and commentary to allow meaningful interpretation by users
 
SuppliersReceivers
 
  
SUP.5 Audit

7.1 Customer Satisfaction Survey    [Checklist] 
 
1Mechanism to collect data on customer satisfaction
2Identifies customers to be contacted
3Identifies the data to be collected from the customer
4Target date for responses
5Identifies products/services under investigation
6Methods to analyse feedback
 
SuppliersReceivers
 
OPE.2 Customer Support
MAN.6 Measurement
  
MAN.6 Measurement

7.2 Field Measure    [Checklist] 
 
1Identifies 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
 
SuppliersReceivers
 
  
MAN.6 Measurement
OPE.1 Operational Use
MAN.6 Measurement

7.4 Process Measure    [Checklist] 
 
1Includes measures related to the performance of a process, such as:
1.1  size and number of work products produced
1.2  adherence to the process
1.3  time needed to perform process
1.4  effort needed to perform process
1.5  number of defects related to the process
2Measures the impact of process change
3Measures the efficiency of the process
 
SuppliersReceivers
 
  
MAN.2 Organisation Management
MAN.6 Measurement
  
PIM.3 Process Improvement
SUP.1 Quality Assurance
MAN.2 Organisation Management
MAN.6 Measurement
PIM.1 Process Establishment
  

7.5 Project Measure    [Checklist]