Internal Structure
Project Requirements
Project Lead
Documentation
Testing
Coding
Design
Figure .1 Group 3 Project Team
Roles and Responsibilities
The project team consists of the following work roles and responsibilities.
Project Lead
The project lead coordinates with all team members to ensure the deliverable is
completed on time and in accordance with all specifications. Furthermore, the project lead
organizes all group chat session, phase reports and student professor communications.
Requirements Lead
Writes documentation for system and requirements specifications. The
requirements lead also assists with data needed for project and test plan. Lastly, the requirements
lead is responsible for end user documentation.
Design Lead
Responsible for the GUI design that brings all the games together. Assists with
user guide and project plan. Collaborates with project lead to establish interconnectivity between
GUI and games.
Coding Lead
Works to bring all the developer’s games together to create a uniform appearance
for the game suite. Additionally, assists other developers in creation of games. Serves as liaison
between development team and other project work groups.
Testing Lead
Creates, executes, and documents testing results of games in accordance with
IEEE 829-1998, IEEE Standard for Software Test Documentation.
Documentation Lead
Responsible for the gathering, organizing and the documentation of all required
project documents from the team and passed it to the team lead for inclusion in the final project
deliverable.
Managerial Process Plan
The managerial process plan highlights the team work schedule and task break
down to meet the agreed upon project goals.
Work Plan
The following section details both the work breakdown structure for the project schedule
for project team.
Work Activities
The following table lists the breakdown of tasks according to its Software Development
Life Cycle task.
Task name
Category
Subtask
Project Plan
Analysis
Business analysis
Test Plan
Design
Test Design
Project Design
Design
Software Analysis
Phase 1 Source
Code
GUI interface
Phase 2 Source
Code
70 lottery Number Game
Phase 3 Source
Code
Game Code Integration
Final Deliverable
Code/ test plan/ documentation
Software Build
Figure 1 Work Breakdown Schedule
Schedule Allocation
The figure below illustrates the project schedule in a Gantt chart view. This chart
highlights the dependency mapping between tasks. The chart shows the major project milestones
1
2
3
4
5
6
7
21-May
3-Jun
11-Jun
18-Jun
25-Jun
2-Jul
9-Jul
12
7
7
21
7
7
7
31-Dec
1-Jan
2-Jan
3-Jan
4-Jan
5-Jan
6-Jan
Lottery Number Game Project Timeline
Axis Title
along
with delivery due dates for each project deliverable.
Figure 2 Project timeline
Risk Management Plan
Addresses all risk involved with the project. Its purpose is to identify, analyze, and
prioritize risk factors associated with the development and testing of the lottery number game.
