Professional Documents
Culture Documents
Work Breakdown Structure
Work Breakdown Structure
Start
Req
(Feb 4
Feb
10)
(Feb 10
Feb
15)
Analy
sis
(Feb 15
Feb
20)
Design
Implementation
Testing
(Feb 20
February
29)
(March
20
-March
25)
Deploym
ent
Conclusio
n
(March 25
April 9)
(April 9
End of
Semester)
II.
Start
a. First-hand Planning
b. Establish Case Study
c. Project Meeting
d. Finalize Proposal
e. Wait for approval
Requirements
a. Requirements Gathering
b. Software Requirements
Specification (SRS)
III.
Analysis
a. Barriers
b. Code Scheduling
c. Project Tracking
IV.
Design
a. Designing Framework
b. Design Model
c. Design Documentation
d. GUI Design
V.
Implementation
a. Setting-Up Database
Systems
VI.
Testing
a. Develop Test Case
b. Integrate Test
c. User Test
d. Review and Approve
Testing
e. User Acceptance Test
VII.
Deployment
a. Develop System Manual
b. Develop User Manual
c. Develop Training Material
and Documents
d. Review and Approve
Material Documents
e. Train Users
f. User Acceptance Training
g. Preliminary Oral Defense
h. Final Oral Defense
i. Project Approval for
Conclusion
VIII.
Project Conclusion
a. Project Conclusion
Meeting
b. Conclude Approval From
Dean