An overview of Implementation stage of System Development Life Cycle(SDLC) from perspective of an entry level programmer

1. Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
Planning
Analysis
Design
Implementation
Testing
Deployment
By CY L.
https://github.com/cyl337
CY L.
Development Flow from
Perspective of
an Entry Level Programmer

2. • I.T. graduates must have learnt about
Software Development Life Cycle (SDLC)
By CY L.
https://github.com/cyl337 2

3. Typical SDLC
Planning
Analysis
Design
Implementation
Testing
Deployment
By CY L.
https://github.com/cyl337 3

4. • As an entry level programmer,
most of development work focus on
Implementation stage
By CY L.
https://github.com/cyl337 4

5. Focus on Implementation
Planning
Analysis
Design
Implementation
Testing
Deployment
By CY L.
https://github.com/cyl337 5

6. • This stage can be further refined into multiple
phases
• Teams that adopt different methodologies will
have different development flow
• The following work flow partially reflects
development process of teams in which I had
worked in previous years
By CY L.
https://github.com/cyl337 6

7. 5 phases of Development flow
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 7

8. External Input Process by
Coder
Minor OutputProcess by
other party
Major Output
By CY L.
https://github.com/cyl337 8
Diagram Legend

9. User
Requirement
Specification
Specification
Study
Specification
Revision
Request
Spec.
Revision Req.
Review
URS
Understanding
Unit Test Plan
Effort
Estimation
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 9

10. Requirement Study
• Have a thorough understanding on User
Requirement Specification
• Identify requirements that need clarification and
request for revision if necessary
• Prepare unit test plan
• Estimate effort
By CY L.
https://github.com/cyl337 10

11. URS Under-
standing
Solution Design
+
Impact Analysis
Specification
Revision Request
Solution
Review
Final SolutionEffort
Estimation
Solution
+
Impact Area
Existing Code
Solution Review
Feedback
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 11

12. Design & Impact Analysis
• Study code to understanding existing system
logic
• Analyze changes necessary for potential
solutions and their impact on existing system
• Discuss the solution with System Analyst (SA)
and revise its design
• Revise effort estimation
• Request for URS revision if necessary
By CY L.
https://github.com/cyl337 12

13. Final Solution Implementation
Solution Revision
Effort
Estimation
Code Change
Solution Design
+
Impact Analysis
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 13

14. Implementation
• Implement the code change for final solution
• Sometimes programmer may only find the
solution defective / infeasible during coding;
in that case, revise the solution and go
through last phase of impact analysis again
• Revise effort estimation if necessary
By CY L.
https://github.com/cyl337 14

15. Code Change Unit Test
Test Result
Review
Code to be
reviewed
Unit Test Plan
Defect
Test Result
Implementation
Solution Design
+
Impact Analysis
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 15

16. Unit Testing
• Execute unit test plan prepared in
Requirement Study phase
• Fix any defects found
– Bug -> Back to Implementation phase
– Design Flaw -> Back to Impact Analysis phase
By CY L.
https://github.com/cyl337 16

17. Code to be
reviewed
Code
Review
Demo
Evaluation
Unit Test Plan Defect
Code Review
Comment
Implementation
Solution Design
+
Impact Analysis
Prepare DemoTest Result
Demo
Code ready
for SIT
Requirement Study
Design &
Impact Analysis
Implementation Unit Testing Internal Review
By CY L.
https://github.com/cyl337 17

18. Internal Review
• Assure quality before marking the code
change as ready for System Integration Test
• System Analyst reviews code change to assure
it conforms with convention and best practice
• Business Analyst, System Analyst and Tester
evaluate demo to early spot defects or test
cases the programmer overlooked
By CY L.
https://github.com/cyl337 18

19. The whole picture
By CY L.
https://github.com/cyl337 19

20. Rqmt Spec Spec
Study
Spec
Rev Req
Spec Rev
Req
Review
URS
Under-
standing
Unit Test
Plan
Effort Est
Design
+
Impact
Analysis
Solution
Review
Final
Solution
Solution
+
Impact
Area
Existing
Code
Solution
Review
Feedback
Implement
Solution
Rev
Code
Change
Unit Test
Test Result
Review
Code to be
reviewed
Defect
Test Result
Code
Review
Demo
Eval
Code
Review
Comment
Prepare
Demo
Demo
Code ready for SIT
By CY L.
https://github.com/cyl337 20