Codewell Methodology

The principals of Codewell have found that a simple methodology helps the client's staff to understand the process and their part in it.

1. Project Initiation.

Codewell Projects are initiated by its clients.

Codewell personnel interview members of the client's staff who are involved with the current process (if any) and with the project to be done. Be sure to ask about "anomalies"; e.g., what happens when entries are posted wrong, customers dispute bills, etc.

2. Functional Specification.

Codewell personnel write a Functional Specification based on the information received from the client, and review it with the client. This is the definition of the new process, stated in the client's terms. It includes as much as is known about files, file contents, network traffic, etc. Review it with all the people interviewed in the Project Initiation Step. Again, look for anomalies. Review the file and network information with technical staff.

The Functional Specification should contain everything necessary to be the source material for the user's manual and the acceptance test.

It is maintained under the same version control system as the source code.

3. Implementation Specification.

Codewell technical staff write an Implementation Specification. This is the first draft of the final software documentation. It contains definitions of screens, records, files, network packets, and top level functions, plus a top level flow diagram. Review it with the client's technical staff.

The Implementation Specification should contain everything necessary to be the source material for the test plan writers, in addition to the programmers.

It is maintained under the same version control system as the source code.

4. Test Plan Development.

The Test Plan is a written document that defines the tests to be performed by the development group. Any special resources needed are specified.

It is maintained under the same version control system as the source code.

5. Software Implementation.

The source code is written according to the above Specifications. It is compiled and linked using the Codewell standard Make and command files; these processes must run without any errors.

The Specifications and Test Plan are updated as changes occur during implementation.

6. Test Plan Execution (alpha testing).

Testing is performed. Steps from Test Plan Development on are repeated as necessary.

7. Acceptance Test Execution (beta testing).

Testing is performed. Steps from Functional Specification on are repeated as necessary.

8. Delivery.

The "as built" Specifications are delivered as files, and are listed in the Release Memo.

Codewell Methodology / 15 Allen St., No. 2 Arlington, MA 02474-6809 (781) 641-3327 Last Updated: 12 Apr 2007

[ validate ]