1.  Task Name:  Perform Application Modification

2.  Purpose:  Rapid Application Modification (RAM) encompasses requirements definition, design, construction or development, and unit testing.  Each of these activities is performed continuously with new and changed requirements moving iteratively through each of the four activities.  The leader for the Maintenance Integrated Product Team (IPT) controls the cyclical flows, ensures continuous and productive contact with the customer to extract requirements, and reports any conditions which adversely impact cost and schedule to the Systems Manager and Technical Project Officer.  The customer participation is continuous, starting with the communication and recording of requirements, assisting with the design of user interfaces, and immediately reviewing test results.  The review of test results may reveal design flaws or the need for changed requirements which will cause the initiation of another cycle.  The Maintenance IPT employs the tools selected and installed to support RAM.  The product of RAM is the tested software ready for functional integration/acceptance testing with information provided for all necessary documentation and approvals as a by-product.  Software quality assurance is attained through daily review of products and results and day-to-day communications among members of the IPT under the guidance of a software quality assurance analyst.

3.  Roles:  Functional Analyst, Software Engineer, Database Administrator, Architecture Engineer, Web Engineer, Network Engineer, Quality Assurance Analyst, User

4.  References:  None

5.  Entrance Criteria:

     a.  Software Development Plan (SDP) (Word 38KB)
     b.  System Requirements Specification (SRS) (Word 80KB)
     c.  Program Quality Assurance (QA) Plan (Word 35KB)
     d.  Software Configuration Index Record (SCIR) Standard (Word 33KB)
     e.  Review Checklist Standard (Word 40KB)
     f.   Review Report Standard (Word 31KB)
     g.  Test Script Standard (Word 75KB)
     h.  Program Unit/Module Test Checklist Standard (Word 34KB)
     i.   System Change Requests (SCRs) (Approved) (Word 35KB)
     j.   Release Plan

6.  Procedures:

     a.  Define software change requirements
     b.  Modify systems architecture design
     c.  Modify software architecture and software components design
     d.  Modify database design
     e.  Modify user/system interfaces (web pages, reports, screens) design
     f.   Design conversion/initiation processes
     g.  Generate software databases and screens or pages
     h.  Write code
     i.   Perform software requirements, design, and code peer reviews
     j.   Prepare test scripts
     k.  Test database and software

7.  Exit Criteria:

     a.  Software Configuration Index Record (SCIR) (Word 33KB)
     b.  Detailed Requirements Changes
     c.  Software Design Changes
     d.  Database Design Changes
     e.  Architecture Design Changes
     f.   Web Design Changes
     g.  Review Checklists (Software Requirements Peer Review, Design Peer
          Review, Code Peer Review) (Word 40KB)
     h.  Review Reports (Software Requirements Peer Review, Design Peer Review,
          Code Peer Review) (Word 31KB)
     i.   Test Scripts (Word 75KB)
     j.   Program Unit/Module Test Checklist (Word 34KB)

8.  Estimation Criteria:

9.  Measures: