|
|
SDLC Checklist
|
Y,
N,
NA
|
Comments
|
|
|
Phase 1: System Analysis
|
|
|
|
1
|
Is the office Records officer included from the earliest starting point in the framework plan process?
|
|
|
|
2
|
Are records recognized that support the business process?
|
|
|
|
3
|
a. Do current record plans apply to the new framework?
b. Is another record plan required in light of changes in the records?
|
|
|
|
4
|
Are all records-related requirements distinguished and joined into the last CoNoPS Report and Business Requirements Document?
|
|
|
|
5
|
Are new records calendars being drafted, if necessary?
|
|
|
|
6
|
Is the organization Records officer mark on the prerequisites report?
|
|
|
|
|
Phase 2: Design
|
|
|
|
7
|
Are all records administration necessities consolidated into the framework outline report?
|
|
|
|
8
|
Is the office Records officer mark on the framework outline report?
|
|
|
|
9
|
Is the office records administration staff incorporated into project status gatherings as required?
|
|
|
|
10
|
Are proposed records plans submitted to the NARA?
|
|
|
|
|
Phase 3: Implementation
|
|
|
|
11
|
Are records administration necessities consolidated into the framework?
|
|
|
|
12
|
Is the office Records officer mark on the Systems Test Report
|
|
|
|
13
|
Is the office records administration staff incorporated into task status gatherings as required?
|
|
|
|
14
|
Is the office Records officer mark on the archive affirming organization of the framework?
|
|
|
|
|
Phase 4: Evaluation
|
|
|
|
15
|
Is the Mid-Cycle Review complete? (Survey to happen 3 years in the wake of going to generation to approve records administration necessities and records plans.)
|
|
|
|
16
|
Are attitude powers being actualized as per proper demeanours?
|
|
|
|
17
|
Is the Mid-Cycle Review report sent to the office records administration staff for survey?
|
|
|
|
18
|
Is the office Records officer mark on the Mid-Cycle Review affirmation archive?
|
|
|
SDLC checklist for records management and recordkeeping
|
|
Phase 5: Maintenance
|
|
|
|
19
|
At the time of retirement or rollover of the system, are records preserved, retained, and fully accessible for the full retentions in accordance with appropriate dispositions?
|
|
|
|
20
|
At the time of retirement or rollover of the system, are temporary records destroyed in accordance with appropriate dispositions?
|
|
|
|
21
|
At the time of retirement or rollover of the system, are permanent records transferred to NARA in accordance with the appropriate dispositions?
|
|
|
The System Development Life Cycle (SDLC) process applies to information system development projects guaranteeing that all functional and client prerequisites and organization key objectives and destinations are met. The SDLC gives an organized and institutionalized procedure for all periods of any framework advancement exertion. These stages track the improvement of a framework through a few advancement stages from plausibility investigation, framework arranging and idea advancement; to securing and necessities definition; plan; advancement; combination and testing; organization and acknowledgment; however sending and generation; lastly to system retirement. (Chemuturi, 2012)
The Records Management (RM) Profile prescribes that organizations install records administration necessities in the most punctual phases of the SDLC. The agenda (Introduction to Software Development Life Cycle Documentation)distinguishes certain focuses in the SDLC process where the office might propose to set up records administration survey and endorsement to guarantee that sound RM practices are fused into the improvement of its proposed IT frameworks.(Introduction to Software Development Life Cycle Documentation)
The agenda gives three to five essential inquiries regarding records administration and recordkeeping for every period of the SDLC lifecycle process. The agenda inquiries are expected to start a more point by point examination with organization records chiefs, IT and CPIC staff, and program administrators and staff that will recognize recordkeeping prerequisites in every stage, with an extraordinary accentuation on distinguishing records administration necessities at the soonest phases of undertaking arranging, start and necessities gathering. Since individual office SDLC procedures and arrangements differ broadly, the agenda is not intended to be utilized as the main agenda an organization may require, or even a "one size fits all" way to deal with distinguishing recordkeeping necessities inside of an individual office's SDLC approaches. Maybe, the agenda exhibits a broadly utilized strategy to arrange and grow new IT frameworks that can be utilized as a model or layout that individual offices can update or tailor to their own particular one of a kind SDLC procedure, IT and frameworks advancement strategies and systems to distinguish their exceptional records administration and recordkeeping prerequisites. Case in point, a few organizations utilize a five-stage SDLC procedure, and others utilize a ten-stage procedure, and they ought to re-examine or alter agenda to meet their particular SDLC strategy and business needs.
PHASE ONE – SYSTEM ANALYSIS
The primary stage incorporates however is not constrained to characterize the extent of the business process, grouping records connected with the business process, displaying the procedure, deciding framework necessities, taking the choice whether to purchase or assemble, acquiring the innovation, achieving official purchase in, reporting business process, getting-together specialized prerequisites, and sorting out the task. (Chemuturi, 2012)
PHASE TWO – DESIGN
Outline steps incorporate arranging the centre undertaking group, fit-gap investigation, creating process (and perceiving process changes), and building up a data movement arrangement. A few components to consider amid this stage include:
• Have records creation needs been known as a "fit" or 'gap'?
• Have the records made amid this period of the task themselves been very much kept up? Typically the documentation at the investigation and outline stage is key for comprehension the way the framework is shaped as it seems to be, and the key suspicions are useful for the execution of future activities.
• As data work process is demonstrated in the new framework, has the potential requirements for records maintenance been displayed as a part of the life cycle of information in the new framework?
• Are strategies set up to demonstrate the honesty of the records?
• Are there a security arrangement set up to check access to private data and an accessibility plan to make open data effectively available?
PHASE THREE – IMPLEMENTATION
Once the Analysis and Design stage is finished, this stage starts with making thorough configuration records, information change, producing point by point project execution arrangements, documenting problems or risks, creating programming and making test arrangements and scripts for all business forms. This places the framework into a live, creating environment; training is complete (or progressing), and risk factors are assessed in the new environment. Possibility/reinforcement arrangements are evaluated for the need to perform different alternatives. Any remaining concerns are determined. (Al-Zahrani, 2006) A few records administration inquiries to consider amid this stage include:
• Have information segments containing the records been perceived?
• Has fitting metadata been created and endorsed? Metadata ought to incorporate the suitable maintenance time.
• What are the capacity and recovery choices? Stockroom? Archive?
• What are the long haul safeguarding plans for all records?
PHASE FOUR – EVALUATION
The Testing stage includes stacking preparatory information to test recently characterized business forms in readiness for slice over to generation. This stage includes testing new business works on, acquiring client gathering, affirming that information speaking to and transformation compositions are finished, trying the go-live change, and preparing end-clients. (Al-Zahrani, 2006) A few inquiries to consider amid this stage include:
• Does the venture have reported preparing plans, client acknowledgment testing for usefulness, and testing of vital use cases?
• Will there be change reviews and taunt transformations preceding generation cutover?
• Is there form control, for rollback to a past testing environment? This stage includes testing new business works on, acquiring client gathering, affirming that information speaking to and transformation compositions are finished, trying the go-live change, and preparing end-clients. (Chemuturi, 2012) A few inquiries to consider amid this stage include:
• Does the venture have reported preparing plans, client acknowledgment testing for usefulness, and testing of vital use cases?
• Will there be change reviews and taunt transformations preceding generation cutover?
• Is there form control, for rollback to a past testing environment?
PHASE FIVE – MAINTENANCE
The Maintenance stage is the profitable part of the data framework. Typically, intermittent upgrades to the system are desirable; significant ones experience a large number of the same steps diagrammed above and present comparable records administration tests. The Review is done to assess the new business forms and the general arrangement. The new framework ought to be evaluated for any execution tuning. Documentation created amid this stage incorporates proposals to venture supporters and administration, "lessons scholarly", and readiness contemplations for future periods of this task or comparative future activities.(Al-Zahrani, 2006) Exceptional records administration inquiries to consider at the Production stage include:
• What components will control the requirement for changes to the framework?
• Does the rebuilt programming for framework overhauls and fixes additionally take after to the records administration necessities of the early framework improvement stages?
• How will changes after some time to approval/verification be recorded?
Reference:
1. Chemuturi, M. (2012). Requirements Management Through SDLC. Requirements Engineering and Management for Software Development Projects, 169-175.
2. Al-Zahrani, S. (2006). An Information Management System Model for the Industrial Incidents in Saudi Arabia: A Conceptual Framework Based on SDLC Methodology. J. of Computer Science Journal of Computer Science, 2(5), 447-454.
3. Introduction to Software Development Life Cycle Documentation. (n.d.). Retrieved March 03, 2016, from https://www.sdlcforms.com/UnderstandingSDLC.html