SDLC, Phases and task ownership – Post Construction / Development Phase (5)
Continuing the previous articles:
SDLC, Phases and task ownership – Inquiry / Investigation Phase (1) and SDLC, Phases and task ownership – Inception / Initiation Phase (2) and SDLC, Phases and task ownership – Pre-Construction Phase / Design Phase (3) and SDLC, Phases and task ownership – Construction / development Phase (4) the next phase is post construction / post development phase. This phase starts when the team has delivered the first complete version to the customer. Complete means that the deliverable contains all required parts. It could happen that the deliverable still contains undesired issues (called technical bugs). The customer does an acceptance test for any deliverable using either the delivered test procedure or ad-hoc testing. In case the acceptance test fails, the development team has to fix the bugs and this phase repeats.
Step 1: Acceptance test
Do the acceptance test using either delivered test procedure or ad-hoc testing
Customer
Step 2: Submit Issue
Submit problem with enough information which allow the development team to reproduce the issue, including the following:
-
Detail description of the problem
-
Reproduction scenario
-
Environment of the test system
-
Any other valuable information
Ownership / Responsibility: Customer / Support
Step 3: Enter Issue
Enter the issue into the test track system
Ownership / Responsibility: Software Tester
Step 4: Reproduction
Reproduce the problem on development environment, update the test procedure document if appropriate
Ownership / Responsibility: Software Tester / Software Engineer
Step 5: Fix Bug
Involves multiple steps:
-
Fix the reported problem
-
Execute engineering test to ensure the problem is fixed correctly
-
Code review must applied to ensure consistency of the whole product
-
Mark the reported issue as fixed in the test track (Talman CC) system
-
Issue a new build and notify tester about the availability of the new build
Ownership / Responsibility: Software Engineer / Development Manager
Step 6: Verify Fix
Verify the fix, notify the software engineer and team leader about the status of the new build
Ownership / Responsibility: Software Tester
Step 7: New delivery
Send the customer
-
the newly available and verified build
-
the engineering release order document which protocols the change and fix made to the build
Ownership / Responsibility: Development Manager / Support
The outputs to this phase : Updated Test Procedure Document (TP), Binary version of the new software, Engineering Release Order (ERO).
November 7, 2007
· Rahul Desai · No Comments
Posted in: Project Management, Software Engineering
Leave a Reply
You must be logged in to post a comment.