|
Checklists
|
|
|
 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
|
[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
|
[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
|
[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
|
[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
|
[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
|
[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
|
|
7.4 Process Measure
|
[Checklist] |
| |
| 1 | Includes 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 |
| 2 | Measures the impact of process change |
| 3 | Measures the efficiency of the process |
| |
|
|
7.5 Project Measure
|
|
7.5 Project Measure
|
[Checklist] |
| |
| 1 | Appropriate to monitor key processes and critical tasks of a project |
| 2 | Includes measures related to the project on: |
| 2.1 | |
project performance against established plan |
| 2.2 | |
resource utilisation against established plan |
| 2.3 | |
time schedule against established plan |
| 2.4 | |
process quality against quality expectations and/or criteria |
| 2.5 | |
product quality against quality expectations and/or criteria |
| 2.6 | |
highlight product performance problems, trends |
| 2.7 | |
amount of work scheduled |
| 2.8 | |
actual cost against tasks completed |
| |
|
|
7.6 Quality Measure
|
|
7.6 Quality Measure
|
[Checklist] |
| |
| 1 | Measures quality attributes of the work products defined, such as: |
| 1.1 | |
functionality |
| 1.2 | |
reliability |
| 1.3 | |
usability |
| 1.4 | |
efficiency |
| 1.5 | |
maintainability |
| 1.6 | |
portability |
| 2 | Measures quality attributes of the "end customer" product quality and reliability |
| |
|
| Remarks |
| Refer ISO/IEC 9126 for detailed information on measurement of product
quality. |
|
7.7 Risk Measure
|
|
7.7 Risk Measure
|
[Checklist] |
| |
| 1 | Identifies the probability of risk occurring |
| 2 | Identifies the impact of risk occurring |
| 3 | Identifies the change in the risk state |
| |
|
|
7.8 Service Level Measure
|
|
7.8 Service Level Measure
|
[Checklist] |
| |
| 1 | Real time measures taken while a system is operational, it measures the system's
performance or expected service level |
| 2 | Identifies things like: |
| 2.1 | |
capacity |
| 2.2 | |
throughput |
| 2.3 | |
operational performance |
| 2.4 | |
operational service |
| 2.5 | |
service outage time |
| 2.6 | |
up time |
| 2.7 | |
job run time |
| |
|
|
|
|
8 Plan
|
| 1 | Identifies the plan owner | | 2 | Includes: | | 2.1 | | the objective and scope of what is to be accomplished | | 2.2 | | assumptions made | | 2.3 | | constraints | | 2.4 | | risks | | 2.5 | | tasks to be accomplished | | 2.6 | | schedules, milestones and target dates | | 2.7 | | critical dependencies | | 2.8 | | maintenance disposition for the plan | | 3 | Method / approach to accomplish plan | | 4 | Identifies: | | 4.1 | | task ownership, including tasks performed by other parties (e.g. supplier, customer) | | 4.2 | | quality criteria | | 4.3 | | required work products | | 5 | Includes resources to accomplish plan objectives: | | 5.1 | | time | | 5.2 | | staff (key roles and authorities e.g. sponsor) | | 5.3 | | materials / equipment | | 5.4 | | budget | | 6 | Includes contingency plan for non-completed tasks | | 7 | Plan is approved | | |
|
8.1 Acceptance Test Plan
|
|
8.1 Acceptance Test Plan
|
[Checklist] |
| |
| 1 | Identified activities to be performed to test 'deliverable' end customer product |
| 2 | Identifies who has responsibility for performance of acceptance test activities (supplier or customer) |
| 3 | Identifies the system configuration requirements for site |
| 4 | Identifies the installation requirements for site |
| 5 | Identifies how to validate installation activities were performed correctly |
| 6 | Identifies how to validate the deliverables (hardware / software / product) satisfied the customer requirements |
| 7 | Identifies associated test scripts / test cases |
| 8 | Identifies actions to be take upon acceptance of product |
| 9 | Refers to Quality Plan |
| |
|
|
8.2 Acquisition Plan
|
|
8.2 Acquisition Plan
|
[Checklist] |
| |
| 1 | Identifies what needs to be acquired |
| 2 | Establishes the approach for acquiring the product or service; options might include: |
| 2.1 | |
off-the-shelf |
| 2.2 | |
develop internally |
| 2.3 | |
develop through contract |
| 2.4 | |
enhance existing product |
| 3 | Establishes the evaluation and supplier selection criteria |
| 4 | Acceptance strategy |
| |
|
|
8.3 Process Assessment Plan
|
|
8.3 Process Assessment Plan
|
[Checklist] |
| |
| 1 | The identity of the sponsor of the assessment and the sponsor's relationship to the organisational unit being assessed |
| 2 | The assessment purpose including alignment with business goals |
| 3 | The assessment scope including: |
| 3.1 | |
the processes to be investigated within the organisational unit |
| 3.2 | |
the highest capability level to be investigated for each process within the assessment scope |
| 3.3 | |
the organisational unit that deploys these processes |
| 4 | The context which, as a minimum, includes: |
| 4.1 | |
the size of the organisational unit |
| 4.2 | |
the demographics of the organisational unit |
| 4.3 | |
the application domain of the products or services of the organisational unit |
| 4.4 | |
the size, criticality and complexity of the products or services |
| 4.5 | |
the quality characteristics of the products |
| 5 | The assessment constraints which may include: |
| 5.1 | |
availability of key resources |
| 5.2 | |
the maximum amount of time to be used for the assessment |
| 5.3 | |
specific processes or organisational units to be excluded from the assessment |
| 5.4 | |
the minimum, maximum or specific sample size or coverage that is desired for the assessment |
| 5.5 | |
the ownership of the assessment outputs and any restrictions on their use |
| 5.6 | |
controls on information resulting from a confidentiality agreement |
| 6 | The identity of the model(s) used within the assessment |
| 7 | The assessment approach or methodology |
| 8 | The identity of the assessors, including the competent assessor with specific responsibilities for the assessment |
| 9 | The criteria for competence of the assessor who is responsible for the assessment |
| 10 | The identity of assessees and support staff with specific responsibilities for the assessment |
| 11 | Any additional information to be collected during the assessment to support process improvement or process capability determination |
| |
|
|
8.4 Configuration Management Plan
|
|
8.4 Configuration Management Plan
|
[Checklist] |
| |
| 1 | Defines or references the procedures to control changes to configuration items |
| 2 | Defines measurements used to determine the status of the configuration management activities |
| 3 | Defines configuration management audit criteria |
| 4 | Approved by the configuration management function |
| 5 | Identifies configuration library tools or mechanism |
| 6 | Includes management records and status reports that show the status and history of controlled items |
| 7 | Specifies the location and access mechanisms for the configuration management library |
| 8 | Storage, handling and delivery (including archival and retrieval) mechanisms specified |
| |
|
|
8.5 Development Environment Plan
|
|
8.5 Development Environment Plan
|
[Checklist] |
| |
| 1 | Floor plan |
| 2 | Environmental safety considerations |
| 3 | Regulatory requirements |
| 4 | Contractual requirements |
| 5 | Security considerations |
| 6 | Facility configuration |
| 7 | Special environmental requirements (e.g. air conditioning, raised floor, power) |
| 8 | Individual workspace needs defined |
| 9 | Workstations requirements |
| 10 | Supporting hardware / software / product |
| 11 | Tools |
| 12 | Communication equipment |
| 13 | Disaster recovery plan |
| |
|
|
8.6 Project Activity Network
|
|
8.6 Project Activity Network
|
[Checklist] |
| |
| 1 | A graphic illustration of a project as a network diagram showing all of the project's activities, their attributes and the relationships between them; the most common form is the PERT chart |
| 2 | Activity attributes include: |
| 2.1 | |
activity name |
| 2.2 | |
estimated duration |
| 2.3 | |
planned and actual start date |
| 2.4 | |
planned and actual completion date |
| 2.5 | |
resource requirements |
| 3 | The relationships between the activities may include: |
| 3.1 | |
predecessor activities |
| 3.2 | |
successor activities |
| 3.3 | |
dependency delays |
| |
|
|
8.7 System Integration Test Plan
|
|
8.7 System Integration Test Plan
|
[Checklist] |
| |
| 1 | Purpose of integration defined: |
| 1.1 | |
validation of the integrated elements of the system |
| 1.2 | |
validation of the integration of the system elements (hardware, support equipment, interfaced system) |
| |
|
|
8.8 Human Resource Management Plan
|
|
8.8 Human Resource Management Plan
|
[Checklist] |
| |
| 1 | Human resource objectives / goals / policies |
| 2 | Satisfaction of human resource needs: |
| 2.1 | |
required skills identified |
| 2.2 | |
required competencies identified |
| 2.3 | |
skills acquisition and retention strategy |
| 2.4 | |
staff availability and project allocation |
| 3 | Human resource management: |
| 3.1 | |
statutory and regulatory requirements |
| 3.2 | |
conditions and benefits |
| 3.3 | |
organisation reporting and communication structure |
| 3.4 | |
staff development |
| 3.5 | |
performance evaluation criteria |
| |
|
|
8.9 Installation and Maintenance Plan
|
|
8.9 Installation and Maintenance Plan
|
[Checklist] |
| |
| 1 | Identifies impacted site locations |
| 2 | Identifies the required components for the installation with appropriate version information (consideration given to at least the following): |
| 2.1 | |
released software |
| 2.2 | |
type of media |
| 2.3 | |
required maintenance fixes |
| 2.4 | |
support software required (conversion programs, validation routines, associated system interfaces, data base management sys-tem) |
| 2.5 | |
required customer documentation |
| 2.6 | |
installation instructions |
| 2.7 | |
required hardware and peripheral equipment |
| 3 | Identifies supporting information or materials required: |
| 3.1 | |
parameter information |
| 3.2 | |
operation and maintenance information |
| 3.3 | |
pre-conversion information, materials or installed equipment |
| 4 | Type of installation (new vs. conversion of existing system, maintenance) |
| 5 | Custody of master and backup copies |
| 6 | Identifies go / no-go decision criteria |
| 7 | Identifies verification process: |
| 7.1 | |
of required tasks to prepare deliverables required |
| 7.2 | |
of components required at site |
| 7.3 | |
of installation procedures |
| 7.4 | |
of pre-installation construction or conversion activities |
| 7.5 | |
of system integration, release builds, etc. |
| 8 | Identifies customer acceptance requirements |
| 9 | Identifies any safety and security requirements |
| |
|
|
8.10 Software Integration Test Plan
|
|
8.10 Software Integration Test Plan
|
[Checklist] |
| |
| 1 | Purpose of integration defined: |
| 1.1 | |
validation of a subset of the system (all programs required to make a sub-system work, a feature work, etc.) |
| 1.2 | |
validation of the integration of software to other system elements (hardware, support equipment, interfaced system) |
| |
|
|
8.11 Logistics Maintenance Plan
|
|
8.11 Logistics Maintenance Plan
|
[Checklist] |
| |
| 1 | Identifies impacted site locations |
| 2 | Identifies backup and recovery procedures |
| 3 | Identifies customer contacts and technical support personnel |
| 4 | Identifies customer acceptance requirements |
| 5 | Identifies any safety and security requirements |
| |
|
|
8.12 Project Plan
|
|
8.12 Project Plan
|
[Checklist] |
| |
| 1 | Defines: |
| 1.1 | |
work products to be developed |
| 1.2 | |
life cycle model and methodology to be used |
| 1.3 | |
customer requirements related to project management |
| 1.4 | |
tasks to be accomplished |
| 1.5 | |
task ownership |
| 1.6 | |
project resources |
| 1.7 | |
schedules, milestones and target dates |
| 1.8 | |
estimates |
| 1.9 | |
quality criteria |
| 2 | Identifies: |
| 2.1 | |
critical dependencies |
| 2.2 | |
required work products |
| 2.3 | |
project risks and risk mitigation plan |
| 2.4 | |
contingency actions for non-completed tasks |
| |
|
|
8.13 Quality Plan
|
|
8.13 Quality Plan
|
[Checklist] |
| |
|
|
| |
| 1 | Objectives / goal for quality |
| 2 | Defines the activities tasks required to ensure quality |
| 3 | References related work products |
| 4 | Method of assessment / assuring quality |
| 5 | References any regulatory requirements, standards, customer requirements |
| 6 | Identifies the expected quality criteria |
| 7 | Specifies the monitoring timeframe and quality checkpoints for the defined life cycle and associated activities planned |
| 8 | Target timeframe to achieve desired quality |
| 9 | Method to achieved goals: |
| 9.1 | |
tasks to be performed |
| 9.2 | |
ownership for tasks |
| 9.3 | |
audit to be performed |
| 9.4 | |
resource commitments |
| 10 | Identifies the quality criteria for work products and process tasks |
| 11 | Specifies the threshold / tolerance level allowed prior to requiring corrective actions |
| 12 | Defines quality measurements and benchmark data |
| 13 | Defines the quality record collection mechanism and timing of the collection |
| 14 | Specifies mechanism to feed collected quality record back into process impacted by poor quality |
| 15 | Approved by the quality responsible organisation / function |
| |
|
|
8.14 Recovery Plan
|
|
8.14 Recovery Plan
|
[Checklist] |
| |
| 1 | Identifies what is to be recovered: |
| 1.1 | |
procedures / methods to perform the recovery |
| 1.2 | |
schedule for recovery |
| 1.3 | |
time required for the recovery |
| 1.4 | |
critical dependencies |
| 1.5 | |
resources required for the recovery |
| 1.6 | |
list of backups maintained |
| 1.7 | |
staff responsible for recovery and roles assigned |
| 1.8 | |
special materials required |
| 1.9 | |
required work products |
| 1.10 | |
required equipment |
| 1.11 | |
required documentation |
| 1.12 | |
locations and storage of backups |
| 1.13 | |
contact information on who to notify about the recovery |
| 1.14 | |
verification procedures |
| 1.15 | |
cost estimation for recovery |
| |
|
|
8.15 Regression Test Plan
|
|
8.15 Regression Test Plan
|
[Checklist] |
| |
| 1 | Plan for validating that existing systems / features-functions have not been impacted by a change |
| 2 | Plan for validating that change has not impacted working elements of the system (interfaces, operations, etc.) |
| 3 | Plan for validating that change is compatible with existing system requirements (downward compatible) |
| 4 | Identifies the requirements for system element not changed |
| 5 | Identifies what system elements are to be regression tested (i.e. features, functions, interfaces, fixes) |
| 6 | Identifies the changes made |
| 7 | Identifies the regression test cases to be executed |
| 8 | Conditions for execution of regression testing |
| |
|
|
8.16 Release Plan
|
|
8.16 Release Plan
|
[Checklist] |
| |
| 1 | Identifies the functionality to be included in each release |
| 2 | Identifies the associated elements required (i.e. hardware, software, documentation etc.) |
| 3 | Mapping of the customer requests, requirements satisfied to particular releases of the product |
| |
|
|
8.17 Reuse Plan
|
|
8.17 Reuse Plan
|
[Checklist] |
| |
| 1 | Defines the policy about what items to be reused |
| 2 | Defines standards for construction of reusable objects: |
| 2.1 | |
defines the attributes of reusable components |
| 2.2 | |
quality / reliability expectations |
| 2.3 | |
standard naming conventions |
| 3 | Defines the reuse repository (library, CASE tool, file, data base, etc.) |
| 4 | Identifies reusable components: |
| 4.1 | |
directory of component |
| 4.2 | |
description of components |
| 4.3 | |
applicability of their use |
| 4.4 | |
method to retrieve and use them |
| 4.5 | |
restrictions for modifications and usage |
| 5 | Method for using reusable components |
| 6 | Establishes goal for reusable components |
| |
|
|
8.18 Review Plan
|
|
8.18 Review Plan
|
[Checklist] |
| |
| 1 | Defines: |
| 1.1 | |
what to be reviewed |
| 1.2 | |
roles and responsibilities of reviewers |
| 1.3 | |
criteria for review (checklists, requirements, standards) |
| 1.4 | |
expected preparation time |
| 1.5 | |
schedule for reviews |
| 2 | Identifies: |
| 2.1 | |
procedures for conducting review |
| 2.2 | |
review inputs and outputs |
| 2.3 | |
expertise expected at each review |
| 2.4 | |
review records to keep |
| 2.5 | |
review measurements to keep |
| 2.6 | |
resources, tools allocated to the review |
| |
|
|
8.19 Risk Management Plan
|
|
8.19 Risk Management Plan
|
[Checklist] |
| |
| 1 | Project risks identified and prioritised |
| 2 | Mechanism to track the risk |
| 3 | Threshold criteria to identify when corrective action required |
| 4 | Proposed ways to mitigate risks: |
| 4.1 | |
risk mitigator |
| 4.2 | |
work around |
| 4.3 | |
corrective actions activities / tasks |
| 4.4 | |
monitoring criteria |
| 4.5 | |
mechanisms to measure risk |
| |
| | | |
