|
The Process Matrix shown bellow applies both to new software and to upgrades of existing software. All software development, including web applications, is expected to follow these steps..
Work Plan and Methodology :
| |
|
Process Matrix
Process Table Key: X = Responsibility; R = Review; A = Approval required |
| Software Development Process |
Project Manager |
Corporate Software Quality |
Software Developer |
User |
Schedule (fill in your dates) |
| Step 1: Concept Development |
|
|
|
|
|
| Determine User Requirements |
X |
|
|
R |
|
| Software Contract Package |
X |
RA |
|
|
|
| Developer Qualifications Review |
RA |
RA |
X |
|
|
| Step 2: Defining Requirements |
|
|
|
|
|
| Software Requirements Document & Review |
RA |
RA |
R |
X |
|
| Functional Specification & Review |
RA |
RA |
R |
X |
|
| Software Development Project Plan & Review |
RA |
RA |
X |
|
|
| Step 3: Design |
|
|
|
|
|
| Software Prototype & Review (optional) |
RA |
|
X |
R |
|
| Detailed Design Document (optional) |
RA |
RA |
X |
|
|
| Step 4: Implementation |
|
|
|
|
|
| Project Plan Status |
RA |
R |
X |
|
|
| Review(s) |
|
|
|
|
|
| Create Solved Examples |
RA |
R |
X |
|
|
| Create Solved Examples |
|
|
X |
|
|
| Step 5: Test & Integration |
|
|
|
|
|
| Alpha Test |
RA |
RA |
X |
|
|
| Draft Documentation |
RA |
RA |
X |
|
|
| Beta Review by |
RA |
RA |
X |
|
|
| Beta Test |
RA |
|
X |
R |
|
| Submit Final Software |
RA |
|
X |
|
|
| Step 6: Acceptance |
|
|
|
|
|
| Prescreen & Begin Acceptance Testing |
RA |
X |
|
|
|
| Complete Software & Documentation |
|
X |
|
|
|
| Software Release |
|
XRA |
|
|
|
| Step 7: Distribution & Maintenance |
|
|
|
|
|
| Set up Software Distribution |
X |
|
|
|
|
| Support & Maintenance Releases |
RA |
RA |
X |
|
|
| Process Table Key: X = Responsibility; R = Review; A = Approval required |
|
|
The project manager is responsible for driving the software development process, following the general timeline shown above. Project steps are completed in the order shown, starting at the top of the Process Table, and ending at the bottom. Assign dates for your project to each process step and task.
The software developer, who may be either within or an outside contractor to , is responsible for creating the software application. All developers need to complete the steps shown in the Process Table above.
Corporate Software Quality is responsible for the development process quality checkpoints and for software acceptance testing. The required Corporate Software Quality reviews and documents for your project are listed on your Software Contract Deliverables Form.
The users are the persons who will use the completed software. Involving users as shown in the Process Table above helps to make sure the software will meet their needs when it is released.
Contact us for more information.
|
