13-xx#

13-06 Delivery evidence
status: valid
status: valid
links incoming: std_req__aspice_40__SPL-2-BP3, std_req__aspice_40__SPL-2-BP6, std_req__aspice_40__SPL-2-BP7, std_req__aspice_40__SPL-2-BP8

Delivery evidence may have the following characteristics:

  • Evidence of items shipped/delivered electronically to customer

  • Identification of:

    • to whom it was sent

    • address, where delivered

    • delivery date

    • receipt of delivered product
std_req__aspice_40__iic-13-06
Standard Requirement
13-07 Problem
status: valid
status: valid
links incoming: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP3, std_req__aspice_40__SUP-9-BP4, std_req__aspice_40__SUP-9-BP5, std_req__aspice_40__SUP-9-BP6

Problem may have the following characteristics:

  • Identifies the submitter of the problem

  • Identifies the group/person(s) responsible for providing problem resolution

  • Includes a description of the problem

  • Identifies classification of the problem (criticality, urgency, relevance etc.)

  • Identifies the status of the problem - States such as “open”, “in review”, “in implementation”, “closed”, “rejected”, “cancelled”, … - Transitions between states with conditions and authorities

  • Identifies the expected closure date
std_req__aspice_40__iic-13-07
Standard Requirement
13-08 Baseline
status: valid
status: valid
links incoming: std_req__aspice_40__SUP-8-BP5, std_req__aspice_40__SUP-8-BP7, std_req__aspice_40__gp-223

Baseline may have the following characteristics:

  • Identifies a state of one or a set of work products and artifacts which are consistent and complete

  • Basis for next process steps and/or delivery

  • Is unique and may not be changed

Note

This should be established before a release to identify consistent and complete delivery
std_req__aspice_40__iic-13-08
Standard Requirement
13-09 Meeting support evidence
status: valid
status: valid

Meeting support evidence may have the following characteristics:

  • Agenda and minutes that are records that define:

    • purpose of meeting

    • attendees

    • date, place held

    • reference to previous minutes

    • what was accomplished

    • identifies issues raised

    • any open issues

    • next meeting if any
std_req__aspice_40__iic-13-09
Standard Requirement
13-13 Product release approval
status: valid
status: valid
links incoming: std_req__aspice_40__SPL-2-BP5, std_req__aspice_40__SPL-2-BP6, std_req__aspice_40__SPL-2-BP7, std_req__aspice_40__SPL-2-BP8

Product release approval support evidence may have the following characteristics:

  • Content information of what is to be shipped or delivered

  • Identification of:

    • for whom it is intended

    • the address where to deliver

    • the date released

    • Evidence of supplier approval
std_req__aspice_40__iic-13-13
Standard Requirement
13-14 Progress status
status: valid
status: valid
links incoming: std_req__aspice_40__gp-215

Progress status may have the following characteristics:

Status of a plan(s) (actual against planned) such as: - status of actual activities/work packages against planned activities/work package - status of actual results against established objectives/goals - status of actual resources allocation against planned resources - status of actual cost against budget estimates - status of actual time against planned schedule - status of actual quality against planned quality Record of any deviations from planned activities and reason why
std_req__aspice_40__iic-13-14
Standard Requirement
13-16 Change request
status: valid
status: valid
links incoming: std_req__aspice_40__MAN-3-BP4, std_req__aspice_40__MAN-3-BP5, std_req__aspice_40__MAN-3-BP6, std_req__aspice_40__MAN-3-BP7, std_req__aspice_40__MAN-3-BP8, std_req__aspice_40__MAN-3-BP9, std_req__aspice_40__MAN-3-BP10, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__SUP-10-BP1, std_req__aspice_40__SUP-10-BP2, std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__SUP-10-BP6

Change request may have the following characteristics:

  • Identifies purpose of change

  • Identifies requester contact information

  • Impacted system(s)

  • Impact to operations of existing system(s) defined

  • Impact to associated documentation defined

  • Criticality of the request, due date

  • Information supporting the tracking of change requests to closure

    • progress status attribute (e.g., open, allocated, implemented, closed)

    • time stamp of status change

    • person who changed a status

    • rationale for changing a status
std_req__aspice_40__iic-13-16
Standard Requirement
13-18 Quality conformance evidence
status: valid
status: valid
links incoming: std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6

Quality conformance evidence may have the following characteristics:

  • Identifies what tasks/activities/process produce the information

  • Identifies when the data was collected

  • Identifies source of any associated data

  • Identifies the associated quality criteria

  • Identifies any associated measurements using the information
std_req__aspice_40__iic-13-18
Standard Requirement
13-19 Review evidence
status: valid
status: valid
links incoming: std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6, std_req__aspice_40__gp-224

Review evidence may have the following characteristics:

  • Provides the context information about the review:

    • what was reviewed

    • lists reviewers who attended and their area of responsibility

    • status of the review

  • Provides information about the scope of the review:

    • checklists

    • review criteria

    • requirements

    • compliance to standards

  • Effort information about:

    • preparation time spent for the review

    • time spent in the review

  • Review findings:

    • non-conformances

    • improvement suggestions
std_req__aspice_40__iic-13-19
Standard Requirement
13-25 Verification results
status: valid
status: valid

Verification results may have the following characteristics:

  • Verification data and logs

  • Verification measure passed

  • Verification measure not passed

  • Verification measure not executed, and a rationale

  • Information about the verification execution (date, “object-under-verification”, etc.)

  • Abstraction or summary of verification results
std_req__aspice_40__iic-13-25
Standard Requirement
13-51 Consistency Evidence
status: valid
status: valid
links incoming: std_req__aspice_40__MAN-3-BP2, std_req__aspice_40__MAN-3-BP3, std_req__aspice_40__MAN-3-BP4, std_req__aspice_40__MAN-3-BP5, std_req__aspice_40__MAN-3-BP6, std_req__aspice_40__MAN-3-BP7, std_req__aspice_40__MAN-3-BP8, std_req__aspice_40__MAN-3-BP9, std_req__aspice_40__MAN-3-BP10, std_req__aspice_40__SUP-10-BP4, std_req__aspice_40__SUP-8-BP7, std_req__aspice_40__SWE-1-BP5, std_req__aspice_40__SWE-2-BP4, std_req__aspice_40__SWE-3-BP4, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4

Consistency Evidence may have the following characteristics:

  • Demonstrates bidirectional traceability between artifacts or information in artifacts, throughout all phases of the life cycle, by e.g.,

    • tool links

    • hyperlinks

    • editorial references

    • naming conventions

  • Evidence that the content of the referenced or mapped information coheres semantically along the traceability chain, e.g., by

    • performing pair working or group work

    • performing by peers, e.g., spot checks

    • maintaining revision histories in documents

    • providing change commenting (via e.g., meta-information) of database or repository entries

Note

This evidence can be accompanied by e.g., Definition of Done (DoD) approaches.
std_req__aspice_40__iic-13-51
Standard Requirement
13-52 Communication Evidence
status: valid
status: valid
links incoming: std_req__aspice_40__MAN-3-BP2, std_req__aspice_40__MAN-3-BP3, std_req__aspice_40__MAN-3-BP4, std_req__aspice_40__MAN-3-BP5, std_req__aspice_40__MAN-3-BP6, std_req__aspice_40__MAN-3-BP7, std_req__aspice_40__MAN-3-BP9, std_req__aspice_40__PIM-3-BP8, std_req__aspice_40__REU-2-BP6, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__SWE-1-BP6, std_req__aspice_40__SWE-2-BP5, std_req__aspice_40__SWE-3-BP5, std_req__aspice_40__SWE-4-BP5, std_req__aspice_40__SWE-5-BP7, std_req__aspice_40__SWE-6-BP5, std_req__aspice_40__gp-216

Communication Evidence may have the following characteristics:

  • All forms of interpersonal communication such as

    • e-mails, also automatically generated ones

    • tool-supported workflows

    • meeting, verbally or via meeting minutes (e.g., daily standups)

    • podcast

    • blog

    • videos

    • forum

    • live chat

    • wikis

    • photo protocol
std_req__aspice_40__iic-13-52
Standard Requirement
13-53 Qualification evidence
status: valid
status: valid
links incoming: std_req__aspice_40__REU-2-BP4

Definition not available yet in PAM4.0 document.
std_req__aspice_40__iic-13-53
Standard Requirement
13-55 Process resource and infrastructure documentation
status: valid
status: valid
links incoming: std_req__aspice_40__gp-323

Process resource and infrastructure documentation may have the following characteristics:

  • Information on availability, allocation, and usage of

    • Facilities

    • Tools and corresponding licenses

    • Networks

    • Services

    • Samples

  • for non-standard and critical resources and infrastructure.
std_req__aspice_40__iic-13-55
Standard Requirement