The objective of this document is to define the approach and overall framework for software developments and the way they are implemented within the Company.
The result of software development activity is an application or application module referred subsequently as Product.
A Product can be developed starting from a set of business requirements:
a. as a change request for a new/modified functionality of an existing application
b. as a customization – based on an existing software package which is adapted to match the existing requirements and business model
c. as a totally new application – when a customized solution does not cover specific business requirements, no alternative solution exists or from cost efficiency considerations
According to applicability domains, Products can be used inside a department (for specific, particular use) or over more than one department.
CONTENT
1. OVERVIEW
1.1 PROCEDURE OWNER
1.2 CLASSIFICATION
1.3 APPLICABLE REGULATIONS
1.4 RELATED [COMPANY] NORMS AND PROCEDURES
1.5 OBJECTIVES
1.6 AUDIENCE AND SCOPE
1.7 DOCUMENT SUPPORT
2. DEFINITIONS & ABBREVIATIONS
3. RESPONSIBILITY MATRIX / TASKS DETAILS
3.1 REQUIREMENTS ANALYSIS
3.2 NEW CONTRACT
3.3 CHANGE REQUEST
3.4 FUNCTIONAL ANALYSIS
3.5 PLANNING
3.6 TECHNICAL AND DESIGN ANALYSIS
3.7 ACCEPTANCE TESTS DESIGN
3.8 IMPLEMENTATION
3.9 DOCUMENTATION
3.10 TRAINING
3.11 CONDITIONAL ACCEPTANCE TESTING
3.12 ERROR FIX
3.13 IMPLEMENTATION IN PRODUCTION ENVIRONMENT
3.14 LAUNCH AND RUN IN PRODUCTION ENVIRONMENT
3.15 FINAL ACCEPTANCE
4. EXCEPTIONS
5. FINAL CONSIDERATIONS
5.1 DISCIPLINARY ACTIONS AGAINST PROCEDURE VIOLATION
5.2 DOCUMENT REVISION
Pages: 13
Review Change Management and Testing Procedure.