PDA

Click to See Complete Forum and Search --> : A nice .PDF talking about System Development Standards.


t34b4g5
December 2nd, 2007, 02:36 AM
greetings.

I only minutes ago noticed this new area, so i thought i would make a quick thread and share a .pdf document that i have read in the past.

http://www.ucop.edu/ucophome/policies/bfb/is10.pdf

It's a long read, so grab some cookies, and some beer and get comfy and enjoy the read.

Here is the Table of contents from the .PDF


Systems Development and Maintenance Standards
University of California.
May 18, 2001
University of California Systems Development Standards
Table of Contents

1.1 When Do These Standards Apply.............................................................................8
1.2 Simplification of Business Processes......................................................................10
1.3 Systems Development Tracks.................................................................................11
Three Development Tracks................................................................................11
How to Choose the Right Track..........................................................................12
Prototyping Track.....................................................................................12
Traditional Life Cycle Track.....................................................................13
Vendor Package Purchase and Installation Track...................................13
Selection of One or More Tracks.............................................................14
1.4 Roles and Responsibilities......................................................................................16
Functional Office and Administrative Computing Department Responsibilities...16
Steering Committee and Project Team...............................................................17
Internal Audit......................................................................................................18
Office of the President Review...........................................................................18
Campus Responsibility............................................................................18
Implementation Procedures.....................................................................18
Hardware and Software Acquisition by Functional Offices.................................19
1.5 Project Planning and Management.........................................................................20
Project Plan........................................................................................................20
Staff Time Estimates..........................................................................................20
Project Scope.....................................................................................................21
Project Status Reporting.....................................................................................21
Employee Time Reporting..................................................................................22
2.1 Project Proposal......................................................................................................24
Purpose..............................................................................................................24
Project Proposal Document................................................................................24
Internal Audit Notification....................................................................................25
Review and Approval..........................................................................................25
2.2 Request for Information (Purchase Track only).......................................................26
Purpose..............................................................................................................26
Request for Information Document.....................................................................27
Process for Issuing a Request for Information....................................................27
Review of Responses.........................................................................................28
2.3 System Definition (Prototyping Track only).............................................................29
University of California Systems Development Standards
Purpose..............................................................................................................29
System Definition Document..............................................................................29
Data Elements....................................................................................................35
Review and Approval..........................................................................................35
2.4 Prototyping (Prototyping Track only)......................................................................37
Purpose..............................................................................................................37
When to Use Prototyping....................................................................................37
Programming......................................................................................................37
Testing Each Prototype......................................................................................38
External Interface Specifications........................................................................38
Data Elements....................................................................................................39
Review and Approval..........................................................................................39
2.5 Requirements Definition (Traditional or Purchase Tracks)......................................40
Purpose..............................................................................................................40
Requirements Definition Document....................................................................40
Data Elements....................................................................................................44
Review and Approval..........................................................................................45
2.6 Request for Proposal (Purchase Track only)...........................................................46
Purpose..............................................................................................................46
Request for Proposal Document.........................................................................46
Process for Issuing a Request for Proposal.......................................................49
Review of Responses.........................................................................................50
2.7 Feasibility Study (required for Purchase Track)......................................................51
Purpose..............................................................................................................51
Feasibility Study Document................................................................................51
Review and Approval..........................................................................................54
2.8 Vendor Contract and Installation Plan (Purchase Track only).................................56
Purpose..............................................................................................................56
Vendor Contract.................................................................................................56
Development of Interfaces and Customization of the Package..........................57
Installation Plan..................................................................................................57
Coordination with Vendor Staff...........................................................................58
University of California Systems Development Standards
2.9 General Design (Traditional Track only)..................................................................59
Purpose..............................................................................................................59
General Design Document.................................................................................59
Data Elements....................................................................................................63
Review and Approval..........................................................................................63
2.10 Detail Design (Traditional Track only)...................................................................65
Purpose..............................................................................................................65
Detail Design Document.....................................................................................65
External Interface Specifications........................................................................68
Data Elements....................................................................................................69
Review and Approval..........................................................................................69
Sample Program Specifications for COBOL.......................................................70
2.11 Programming and Unit Testing (Traditional Track only)........................................76
Purpose..............................................................................................................76
Programming......................................................................................................76
Unit Testing........................................................................................................76
Review and Approval..........................................................................................77
2.12 System Testing......................................................................................................78
Purpose..............................................................................................................78
System Test Plan...............................................................................................78
System Testing...................................................................................................78
Conversion Testing..................................................................................79
Parallel Testing........................................................................................79
Interface Testing......................................................................................80
Acceptance Testing.................................................................................80
2.13 Implementation......................................................................................................81
Purpose..............................................................................................................81
Description..........................................................................................................81
2.14 Documentation Standards.....................................................................................82
Overview of Written Documentation...................................................................82
Training..............................................................................................................82
Operations Manual.............................................................................................84
Purpose of the Operations Manual..........................................................84
Contents of the Operations Manual.........................................................84
Part 1 - General Information...............................................................................84
Part 2 - Running the Jobs...................................................................................89
Systems Manual.................................................................................................92
University of California Systems Development Standards
Purpose...................................................................................................92
Code as Documentation..........................................................................92
Contents of the Systems Manual.............................................................92
Application Description.......................................................................................92
Technical Environment.......................................................................................92
Databases..........................................................................................................93
System Flowcharts.............................................................................................93
Glossary of Terms..............................................................................................93
Application Interfaces.........................................................................................93
Security and Authorization..................................................................................93
General Technical Approach..............................................................................94
Ad-Hoc Access to Data......................................................................................94
User Documentation...........................................................................................95
Purpose...................................................................................................95
Contents of the User Documentation.......................................................95
Overview of the Application................................................................................96
General Technical Environment.........................................................................96
Online Update.....................................................................................................96
Batch Processing................................................................................................96
Data Integrity......................................................................................................97
Retrieval of Data.................................................................................................97
Data Element Dictionary.....................................................................................98
Authorization Levels...........................................................................................98
Problem Resolution............................................................................................98
2.15 Post-Implementation Review.................................................................................99
Purpose..............................................................................................................99
Description..........................................................................................................99
3.1 Data Retention......................................................................................................101
Overview..........................................................................................................101
Definition of Data Retention...................................................................101
Reasons for Keeping Data.....................................................................101
Description of Offsite Storage................................................................101
Data Retention for Application Processing and Recovery Purposes................101
Onsite Data Storage..............................................................................101
Offsite Data Storage for Disaster Recovery...........................................102
University of California Systems Development Standards
Data Retention for Functional Purposes...........................................................103
Onsite Data Storage..............................................................................103
Offsite Data Storage for Data Preservation............................................104
Summary..........................................................................................................104
3.2 Privacy..................................................................................................................106
Introduction.......................................................................................................106
Privacy Requirements......................................................................................106
The CART requirement..........................................................................106
Disclosure..............................................................................................107
Access...................................................................................................107
Amendment...........................................................................................108
Identification of Authorized Users..........................................................108
Notices...................................................................................................108
System Notice..................................................................................................108
Individual Notice...............................................................................................109
4.1 Introduction...........................................................................................................114
4.2 Maintenance Standards for Small Modifications to Low Risk Applications............114
4.3 Maintenance Standards for Modifications requiring more than 1 month or $15,000 to complete or non-Low Risk Applications............................................................114
4.3.1 Source Control.........................................................................................114
4.3.2 User Participation....................................................................................115
4.4 Maintenance Standards for Large Modifications...................................................116

sec_ware
December 2nd, 2007, 12:01 PM
Hi

Thanks for sharing the paper. It is a nice compilation
of points to think of, thus defining a standard :)

To be a bit picky:
We are talking here about systems thaat cost >150k$
(15k$ maintenance a year) or are high risk.

In order to simplify life of university staff and to bring even
more structure to the process (and thus potential to reduce
costs), I would not just ask for some kind of software/system
architecture (Ch 2.3), but for a certain type of approach
(Kruchten, Hofmeister et al./Siemens Four View,...). Otherwise,
you will get an inconsistent bunch of self-defined views on
system/software architecture.

One then can say "Yes, we have that document" (thus be compliant)
but whether it can be used or not does not matter (see our recent
discussion about BCM and other standards in the DR and BCM forum :) )

Cheers