Window 2 World

------------------
A) Proposal STAGE
------------------
1) proposal

2) Estimation [can use functional point estimation] [consider fixed bid , time and management]

-------------------------------------------------------
B) Once Proposal/Estimation is approved start Analysis
-------------------------------------------------------

1) prepare the document for project [called as PDSP] , which contains details about harware requirements,
configuration management tool , Quaility person ,Quality audit frequencey, other trimmings for the quality
policy of the company in specific to the project

2) should start maintaining the Trancebility matrix [horizantal , vertical tracebility matrix]
horizantal will contain functional points against deliverables [HLD,SRS,LLDs,UTCs,ITCs,STCs]
Vertical will contain functional points against functional points to get an idea of impact of change
in one functionality on other

3) preparing check lists for variuos artifacts

4) Software requirement specification [SRS]

----------------------------------------------
C) Once architecture is approved start Design
----------------------------------------------

1) High Level Document [Architecture] [HLD]

2) If one have to choose between technologies one has to prepare a sheet for comparing them for taking a decision

the reoport is called Decision Analysis Report [DAR]

3) Low Level Document [should be done for all the use cases]

4) Unit Test Cases

5) Integration Test Cases[integrating modules or with other projects]

6) System Test Cases [functionality test cases]

----------------------------------------------
D) Once Design is approved start Construction
----------------------------------------------

1) coding , code review

2) unit testing , capturing unit test results


------------------------------------------
D) Once construction is done start testing
------------------------------------------

1) integration testing , capture results , raise defects , fix and release

2) system testing , capture results , raise defects , fix and release

3) user acceptance testing , capture results , raise defects , fix and release


Each one of the above should follow the following steps

i) Preparation

ii) each artifcat will have a check list, the check list has to be filled with self review

iii)external Review [in some cases it will goto SME (System Mater Expert) review ]

iv) all the review/testing defects should be captured and fixed

v) Rework [again goes back to review/testing until every thing is ok]

vi) Each deliverable should go after FIR (Final Inspection Report) from Quality person

Vii) after each page there will be a casual analysis meeting for discussing where more
defects are coming and how to reduce them [training or adding items to check lists etc]
and the strategy for the upcoming phase

Viii) every discussion either with customer or internal should have Minutes of Meeting and open items for action captured

ix) every artifact , evidence (like customer mail , Minutes of meeting) should be in configuration management tool

x) In the above Phases one should ensure to get the best practices , resuable components.

-------------------------------------------------------
E) Once UAT (user acceptence) is done start Maintanance
-------------------------------------------------------

1) raising tickets , closing , tracking time