Software Design Change Procedure
The purpose of the Software Design Change Procedure is to ensure that any design changes occurring during software development are managed, controlled and communicated efficiently and effectively.
Software source code is developed in accordance with design inputs, requirements, and specifications defined by the systems analyst. Appropriate version control processes are followed to ensure proper source code change control and to maintain the integrity of the developed software code.
The Software Design Change Procedure applies to all company’software development projects. (6 pages, 923 words).
Software Design Change Responsibilities:
The Project Manager is responsible for reviewing design change requests/proposals, to determine the appropriate actions to take, and for updating the project schedule accordingly.
The Software Designer is responsible for reviewing design changes and updated system requirements, determining the parts of the system affected by the change, and designing system changes to achieve the new software requirements.
The Systems Analyst is responsible for reviewing design changes, determining the parts of the system affected by the changes, and updating the system requirements.
User Management is responsible for reviewing design specifications and, if necessary, submitting change requests in a timely and efficient manner.
Software Design Change Procedure Activities
- Software Design Changes
- Software Design Change Review
- Software Design Change Implementation
Software Design Change Procedure References
- ISO/IEC 12207:1995-Information Technology-Software Life-Cycle Processes
- IEEE/EIA 12207.0-Standard Industry Implementation of International Standard ISO/EIC 12207.0:1995
Software Design Change Procedure Forms