8.4.3.1 Change Request/Problem Report (CReq)

  Änderungsantrag/Problemmeldung

Contents		Introduction Document Structure

Introduction

Document Structure

• identification
  • number of the Change Request/Problem Report
  • brief description of the problem
  • identification of the project
  • identification of the concerned configuration
  • date
  • author
• classification
  • urgency
  • requested date of completion
  • category (error [in specification, design, code, procedure], problem, modification, addition, improvement, etc.)
• object of Change Request/Problem Report
  • identification of products concerned
    products to be changed with their version/configuration identification, if possible to be separated into products directly concerned, and subsequent (in consequence) products to be changed
  • representation of the actual status
    information for reconstruction of a problem (system status, environment conditions, user and system actions, effects, etc.)
  • representation of the planned state
    explanation of and reason for the desired reactions, states, conditions, etc.
• remark
  e. g. about relations to already submitted Change Requests/Problem Reports

No.	Change Date	Changed by (Departement), at (Date)	Signature