6450 - DEVELOPMENT - PROJECTS
Records relating to the development of all ministry information system
projects in accordance with information resource management policies. Includes business
area analyses, feasibility studies, application and
data requirements, application and data design, test plans, results and
analysis, maintenance plans (including computer applications access control),
and documentation development such as operations manuals, user manuals,
training manuals, source listings of program code, data set names, backup
file names (at time of implementation) and quality assurance reports. Also includes
control bulletins.
For approved documentation, see primary 358.
For audits not related to development projects, see primary 975.
For business area analysis not related to development projects, see primary
400.
For change management approvals, see primary 6840.
For committees and commissions, see primaries 200 (general), 201 (cabinet), 202 (ministerial), 204 (inter-ministerial), 205
(international) and 206
(inter-provincial/federal).
For contracts resulting from requests
for proposal/information, see primary 1070.
For local application development, see primary 6820.
For maintenance of
systems, see primary 6820.
For Treasury Board submissions, see primary 1250.
For Y2K
project documentation and test data, see Special Records Schedule
112916.
non-OPR NOTE: Offices will retain non-OPR
copies of records for: SO nil DE
Primary-
Secondary |
Records Series |
|
OPR |
|
PIB/PUR |
| | |
A |
SA |
FD |
|
| 6450-00 |
Policy and procedures |
|
SO |
5y |
SR |
|
| 6450-01 |
General |
|
CY+2y |
5y |
DE |
|
| 6450-20 |
Projects - individual
(arrange by project name)
SO = when project has been reviewed/audited
NOTE: For ease of retrieval, all files relating to one project may
be arranged together physically, first by project name and then by primary
number and secondary number.
NOTE: Ministries have the option of filing projects in chronological
order using secondary -20 and then the project name or, if volume warrants,
using the secondaries listed below. However, ministries must be consistent
and use only one method or the other for projects in this primary. |
|
SO |
5y |
SR |
|
Primary-
Secondary |
Records Series |
|
OPR |
|
PIB/PUR |
| | |
A |
SA |
FD |
|
| 6450-25 |
Projects - individual - project management |
|
SO |
5y |
SR |
|
| 6450-30 |
Projects - individual - planning and initiation |
|
SO |
5y |
SR |
|
| 6450-35 |
Projects - individual - requirements definition |
|
SO |
5y |
DE |
|
| 6450-40 |
Projects - individual - design |
|
SO |
5y |
DE |
|
| 6450-45 |
Projects - individual - development |
|
SO |
5y |
DE |
|
| 6450-50 |
Projects - individual - test implementation |
|
SO |
5y |
DE |
|
| 6450-55 |
Projects - individual - implementation |
|
SO |
5y |
DE |
|
| 6450-60 |
Projects - individual - maintenance plans |
|
SO |
5y |
DE |
|
| 6450-65 |
Projects - individual - post implementation audits/reviews |
|
SO |
5y |
SR |
|
| 6450-70 |
Projects - individual - documentation development |
|
SO |
5y |
DE |
|
| 6450-80 |
User documentation
SO = when documentation has been updated or is no longer needed to support
a system
NOTE: Use this secondary to classify all approved/final versions of
user documentation such as operations manuals, systems manuals, user manuals
and training manuals arising from secondary 6450-70, as well as maintenance
plans arising from secondary 6450-60. |
|
SO |
nil |
DE |
|