A4 - 1
A4 - 1
projects
· SDLC Documentation
· Testing Standards
Introduction:
Establish written standards and procedures for systems development and maintenance
for the systems to be developed, acquired, implemented, and maintained. Review SDLC
methodology to ensure that its provisions reflect current generally accepted techniques
and procedures.
• Appropriate strategic planning for projects within the IT short- and long-term plans,
including authorization and reporting requirements from senior management to the
board;
SDLC Documentation
Develop and maintain a well-documented SDLC for all system and application
development processes. At a minimum, the SDLC documentation will include:
• System design;
• System development;
• Testing;
Testing Standards
• A restriction of the use of live files in testing to prevent destruction or alteration of live
data;
• Simulated error conditions to ensure that the program effectively handles all
situations; and
• Specification of change;
• Request and approval to move source code into the test environment;
Document the process for modifying information systems programs. Change Control
documentation includes:
• Person(s) requesting;
• A form used to identify the change, indicate the reason(s) for the emergency change,
identify who made the change, record the date the change was made, and document
the authorization signature(s); and
Reason: Occasionally the need for program change arises that must bypass normal
change procedures. Such a change might be required to restore production processing.
These immediate (emergency) changes are usually called patches, quick fixes, program
temporary fixes, or temporary program changes. The use of such techniques should be
strictly controlled to prevent unauthorized changes and to ensure that approved
changes are made correctly.
1. Change requests should be prioritized based on their impact on the system and the
business.
4. Changes to the software should be tracked and managed using a version control
system to ensure that changes can be easily rolled back if necessary.
7. The name of the person or team requesting the change and their contact information.
10. Impact analysis, including any potential risks or drawbacks of the proposed change.
11. Change requests are typically reviewed and approved by a designated group or
individual before being implemented.
These standards help ensure that changes to software systems are well-planned,
coordinated, and thoroughly evaluated before being implemented.
For the change request we will follow the below mentioned steps.