KatDC Software Development

KatDC Software Product Development Model

(start) -> 1
1. Get User Requirements -> 2.1
2.1 Refine Requirements Spec. (R1, R2, R3 ...) -> 2.2
2.2 Spec. Verification Procedure -> 7.1 -> 13 and 2.3
2.3 Mapping Requirements to Use Cases Diagrams (USC1, USC2, ...) -> 3.1 and 3.2
3.1 Attached Activity Diagrams to Those Use Cases Diagrams (AD1, AD2, ...) -> 4.1 and 4.2
3.2 Estimate Schedule, Check Points and Cost -> 13 and (the flow end).
4.1 UI workflow diagram (UWD1, UWD2 ...) -> 5.1 and 6.1
4.2 Software Analysis -> 5.2
5.1 UI Art Designs. -> 8
5.2 Software Class Diagrams + Database Design->6.2
6.1 UI Prototyping -> 8.2
6.2 Units Coding -> 7.2
7.1 Create Test Items. -> 9.1  and 13.
7.2 Unit Tests->8.2
8.1 Integrate Units to Applications-> 9.1 and 10
8.2 Integrate Applications with final UI Designs -> 9.2 and 14.1 and 14.2
9.1 Create Test Procedures for each Test Item -> 9,2
9.2 Features Tests -> 11.
10. Spec. and Customer Verification-> 11.

11. QA Tests & Reviews Meeting -> 11.1. and 13.
11.1 If not pass QA Testing and accepted by Review Team members -> go to 11.3
11.2 Otherwise, -> 12.
11.3 Debug -> 11.
12. Product Release Procedure. -> 12.1
12.1 Customer Acceptance Test -> 13.
13. Issue documents to the Document Center
14.1 Manual & User Guide Design -> 12.
14.2 Product Packaging. -> 12.
13 -> (end)


Remarks: 1. The bold item is another complete activity.
               2. This is only for reference. You can change any action, flow, object if you want.