Swdevdoc
Swdevdoc
Overview The software development document contains all preparations pertaining to the development of each unit or module, including the software, test cases, test results, approvals, and any other items that will help to explain the functionality of the software. The document is dynamic and is maintained by the system development team and should he constantly updated as the systems development progresses. The software development folder should include the following information for each unit: 1 Description of the units functionality in narrative format Description of development methodologies used Requirements in the functional requirements document allocated to this unit or module Completed trace ability matrix displaying the units test cases satisfying the functional requirements in the test plan Source code listing Controlled libraries/directories/tables All data necessary to conduct unit testing Unit test results and analysis System Technical Lead sign off for design walk-through. approval of code, and completion of each unit Completed Software Development Document Check-Off sheet (attached)
ROLES AND RESPONSIBILITIES The team members have the following roles and responsibilities: The application developer assigned the primary responsibility for the module or unit creates a file folder for the unit, labels it according to the name of the unit, and places it in the appropriate place in the project team file cabinet. The application developer(s) add copies of the indicated documentation to the folder as they are created. The project QA representative reviews the contents of the folder for completeness, and points out discrepancies to the developer assigned primary responsibility for tile module or unit. The developer assigned primary responsibility for the module or unit completes the Software Development Document Check-Off sheet and arranges for the System Technical Lead review and approval when needed. The folder is available to all project team member for review, but if removed from the file cabinet, it must be replaced with a cheek-out card indicating who checked it out, when, and where it will he located.
Functionality Is the functionality of this unit fully described? Is the description in narrative form? Was a design walk-through conducted? Was permission granted to begin programming?
Source Code Is the source code listing of the unit included in this folder?
Libraries, Directories, and Tables Are all coded entities included in the folder?
Development Methodologies Are all development methodologies for the development effort described in the folder?
Test Data Are all data necessary to conduct testing referenced in this folder?
Test Analysis Was the unit thoroughly tested and were all logical paths verified?