Practical Examination
You are working on a project to develop Lab Management application. This application
is to help students to improve their programming skills. It would include the following
capabilities:
Allow students to register for university-sponsored Lab classes such as C++
programming, Java Programming, Java Desktop Programming, Java Web
Programming, .NET Programming, Python programming classes.
Allow students to submit their work in the Lab class and to track their progress.
Allow teacher to manage his classes and to evaluate his students submitted
work, to approve or to reject the work.
Allow teacher to generate the final report of his classes at the end of the
semester.
Request 1 - Work Breakdown Structure
Develop a WBS for the project. Break down the work to Level 3 or Level 4, as appropriate.
Assume that the Level 1 category is called Software Project, and that the Level 2 categories are
Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Under the Executing
section, include Level 3 categories of Analysis, Design, Prototyping, Testing, Implementation,
and Support. The Support category includes Level 4 items for Training, Documentation, User
Support, and Enhancements
Lab Management (level 1)
a. Initiating (level 2)
1. Create Project Charter (level 3)
2. Define Scope (level 3)
a. Goal
b. Deliverable
c. Budget
d. Schedule
e. Constraints
3. Identify Project Objective (level 3)
4. Invite the Right Stake Holder (level 3)
5. Set Expectation
b. Planning (level 2)
1. Create Scope Management Plan (level 3)
2. Create Time Management Plan (level 3)
3. Create Cost Management Plan (level 3)
4. Create Risk Management Plan (level 3)
5. Create Resource Management Plan (level 3)
6. Meeting with team to discuss about plans (level 3)
7. Deliver Project Management Plan (level 3)
c. Executing (level 2)
1. Analysis (level 3)
i. Create User Requirement (level 4)
ii. Create System Requirement
iii. Identify detailed data requirements
a. Input and output data requirements
iv. Perform Requirement validation (level 4)
v. Perform Requirement management (level 4)
2. Design (level 3)
i. Create System and Software Design
a. Architectural Design
i. Select Design Pattern for system and modules
b. Detailed Design
i. Select Algorithm and data structures for modules
ii. Determine data flows.
ii. Create Interface Design
iii. Design Database
a. Define logical data relation
b. Design data structure
c. Validate
iv. Review Design
3. Prototyping (level 3)
i. Design interactive screens prototype
ii. Review Prototyping
4. Implementing (level 3)
a. Develop program modules
b. Code review
5. Testing (level 3)
i. Perform unit testing (level 4)
ii. Perform integration testing (level 4)
iii. Perform system testing (level 4)
iv. Perform acceptance testing (level 4)
6. Support (level 3)
i. Training (level 4)
ii. Documentation (level 4)
iii. User support (level 4)
iv. Enhancements (level 4)
d. Monitoring and Controlling (level 2)
1. Control scope (level 3)
2. Track progress (level 3)
3. Perform Cost control (level 3)
4. Monitor and control Risk (level 3)
e. Closing (level 2)
1. Create Lesson learn (level 3)
2. Create Project Final Report (level 3)
3. Create Project Archive (level 3)
4. Close Project Ceremony (level 3)
Request 2 - Deliverables
Identify at least five milestones mapped to the main deliverables for the project. For each
milestone, write a short explanation of how to measure its status completed or not
No Milestone Deliverable Explanation Due Date
1 Complete Approved Project + Specific: this milestone is 01/02/2021
Initiating Charter specified for initiating
Stage Kick-off Meeting process
Minutes + Measurable: it’s
Stakeholder measurable by tracking the
Register completion of 3 deliverable
+ Attainable: it’s attainable
when 3 deliverables are
completed
+ Relevant: yes, it’s
relevant
+ Time-bound: yes, it has 1
week to complete
2 Complete Project + Specific: this milestone is 2/3/2021
Planning Management Plan specified for planning
Stage process
+ Measurable: it’s
measurable by tracking the
completion of project
management plan
+ Attainable: it’s attainable
when project management
plan is completed and it
includes Scope, Time, Cost,
Risk, Resource
Management Plan and the
meeting with team has been
done
+ Relevant: yes, it’s
relevant
+ Time-bound: yes, it has 1
week to complete
3 Complete User Requirement + Specific: this milestone is 3/4/2021
analysis System specified for analysis
Stage Requirement process
Data Requirement + Measurable: it’s
measurable by tracking the
completion of 3 deliverable
+ Attainable: it’s attainable
when 3 deliverables are
completed
+ Relevant: yes, it’s
relevant
+ Time-bound: yes, it has 2
weeks to complete
4 Complete Design for System + Specific: this milestone is 4/5/2021
design stage Design for module specified for design process
Design for DB + Measurable: it’s
Design for measurable by tracking the
interface completion of 4 deliverable
+ Attainable: it’s attainable
when 4 deliverables are
completed
+ Relevant: yes, it’s
relevant
+ Time-bound: yes, it has 2
weeks to complete
5 Complete Lesson Learn + Specific: this milestone is 5/6/2021
closing Stage Final Report specified for closing
Project Archive process
+ Measurable: it’s
measurable by tracking the
completion of 3 deliverable
+ Attainable: it’s attainable
when 3 deliverables are
completed
+ Relevant: yes, it’s
relevant
+ Time-bound: yes, it has 1
week to complete
Request 3 – Project Scheduling
Assume that you have defined and estimated project schedule with activities as below
Activity Preceding Activity Duration in
Weeks
Start None 0
A Start 3
B A 2
C A 3
D A 2
E C, B 9
F B 10
G D 3
H E, F, G 6
I G 2
J H, I 8
End J 0
Draw a network diagram and identify the project duration by applying critical path analysis
List of Paths in the network
Path 1: Start -> A -> B -> F -> H -> J -> End with duration: 3 + 2 + 10 + 6 + 8 = 29 weeks
Path 2: Start -> A -> B -> E -> H -> J -> End with duration: 3 + 2 + 9 + 6 + 8 = 28 weeks
Path 3: Start -> A -> C -> E -> H -> J -> End with duration: 3 + 3 + 9 + 6 + 8 = 29 weeks
Path 4: Start -> A -> D -> G -> H -> J -> End with duration: 3 + 2 + 3 + 6 + 8 = 22 weeks
Path 5: Start -> A -> D -> G -> I -> J -> End with duration: 3 + 2 + 3 + 2 + 8 = 18 weeks
Critical Paths are Path 1 and path 3. And project duration is 29 weeks
Request 4 – Schedule Updating & Tracking
From the schedule on request 3, after 5 weeks, your manager/sponsor inform you that he would
like to receive the product of your project earlier than your planned schedule for 2 weeks.
Therefore, you have to find the solutions so that your project could finish 2 weeks sooner.
Define at least two solutions ordered by the choosing priority and include relevant explanation
how it will help your project to be developed faster to accomplish on time.
Fast tracking: Arrange task H so that it overlaps over tasks E and F on 2 weeks. This may
increase risk, so that require more attention to communication.
Crashing:
Add people to join project to complete task H earlier than 2 weeks
Force team to work overtime on task H to complete it earlier than 2 weeks
Reward team if they can complete task H earlier than 2 weeks
Crashing will increase cost.
