Post on 10-Apr-2018
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 1/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
VIRTUAL JUKEBOX SYSTEM
Project Plan
Group ID: CMU-113
Code: VJS.PP.1.2
Date: Jul, 1st
2010
Version: 1.2
Created by Man Nguyen Duc
Team members
Man Nguyen Duc, Vu Truong Tien, Nhu Nguyen Gia, Thi Nguyen T. Minh, Huy
Nguyen D. Quang, Chung Le Van, Anh Nguyen Quang, Thi Trinh S. Truong
Client: Anthony Lattanze
Mentor: Cliff Huff
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 2/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
RECORD OF CHANGES
*A - ADDED M - MODIFIED D – DELETED
VERSIONNUMBER
DATE
NUMBER OF
FIGURE, TABLEOR PARAGRAPH
A*
MD
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUESTNUMBER
1.0 12jun2010 Draft
1.1
1.2
21jun10
1-jul-10
All
Schedule
M
M
Modified for delivering draft
version to customer
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 3/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
Document Approvals: The following signatures are required for approval of this
document.
Anthony J. Lattanze
Carnegie Mellon University/ISR faculty,
Client
Date
Clifford Huff
Studio Mentor
Date
Man Nguyen Duc
Project Manager
Date
Vu Truong Tien
Product Manager
Date
Nhu Nguyen Gia
Domain Expert
Date
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 4/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
TABLE OF CONTENTS
DEFINITION OF TERMS .................................................... 6
1 PURPOSE ............................................................. 6
2 BACKGROUND .......................................................... 6
3 PROJECT GOALS AND OBJECTIVES ........................................ 6
4 SCOPE DEFINITION .................................................... 6
5 ASSUMPTIONS AND CONSTRAINTS ......................................... 7
6 TECHNICAL PROBLEMS .................................................. 7
7 KEY STAKEHOLDERS .................................................... 8
8 PROCESS MODEL ....................................................... 8
9 ROLES AND RESPONSIBILITIES .......................................... 9
10 COMMUNICATION, TRACKING, AND REPORTING PLAN ...................... 11
11 PROJECT TEAM INFORMATION ......................................... 11
12 INTERNAL TRAINING ................................................ 12
13 TECHNICAL APPROACH ............................................... 12
14 TESTING DESIGN ................................................... 13
15 RISKS AND RISK MANAGEMENT ........................................ 13
16 QUALITY ASSURANCE PROCESS ........................................ 15 Quality Objectives ........................................................................................................15
Metrics .........................................................................................................................15
Tests and Reviews .......................................................................................................15
Problem Report and Corrective Action .........................................................................16
Record Collection and Maintenance .............................................................................16
17 CONFIGURATION MANAGEMENT ......................................... 17
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 5/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
Products supplied by customer.....................................................................................17
Configuration Items ......................................................................................................17
Naming Convention ......................................................................................................17
18 TOOLS, AND TECHNIQUES ............................................ 18
19 MASTER SCHEDULES ................................................. 18
20 WORK BREAKDOWN STRUCTURE ......................................... 18
21 REFERENCES ....................................................... 19
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 6/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
DEFINITION OF TERMS
XP: eXtreme Programming
SRS: software requirement specification
TDD: Test – Driven Development
TFD: Test-First Development
VJS: Virtual jukebox System
PM: Project manager
1 PurposeThe Virtual Jukebox Project Plan will provide a definition of the project, including the
project’s goals and objectives. Additionally, the Plan will serve as an agreement between
the following parties: Client, mentor, Project Manager, Project Team, and other personnel
associated with and/or affected by the project.
2 BackgroundA traditional jukebox is a semi-automated music-playing machine.
coin-operated machines that allow users to select songs from self-contained media.
large box with a rounded top and has colored lighting on the front of the machinecommonly located in restaurants and pubs.
some were floor model stand up devices others they could be distributed at the
table-side
3 Project Goals and Objectives Building an virtual music jukebox distributed application, and stand-alone.
Building a database and manage the connections within the server, can local or
remote access by admin.
Creating a friendly user interface , easy to use and pleasing which allows uploading
files to the database, combined with playing audio files to the clients.
User can use credit card for paying and play music
4 Scope DefinitionThe Project will deploy distributed application and stand-alone; including the
following:
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 7/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
- Using db bank card account to demonstration
- Using keyboard for development and testing
- Deploy on PC and or Laptop
- Using MP3 digital format
5 Assumptions and constraints- PC client have to stereo devices
- End User devices have enough performance to process audio function in real
time.
- Network is available
6 Technical ProblemsThere exists no current convenient and inexpensive technology for storing vast
libraries of digital audio for use in a home stereo environment, pay with a credit card rather
than by coin from their account. The system shall support two different configurations:
stand-alone and distributed table-side, local and/or remote adminstration.
Available solution must
- Record and centrally store audio files into the MP3 digital audio format.
Play audio stored in the MP3 digital audio format.
- Store a sufficient quantity of music.
- Be able to seek through tracks during play.
- Have a large face-mounted display showing the current song name,time, and other standard display information.
- The display must facilitate browsing the stored music library and
creating play lists.
- Not be damaged by unexpected loss of power. Continue playing next
song
Note: see details in VJS.UserStories v1.1 and VJS.Architecture v1.1
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 8/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
7 Key Stakeholders
- Customer
- Project Manager
- Product manager
- Programmers
- Testers
- Tracker
- Interaction Designer
- Users
8 Process ModelThis project we use XP model to develop the software.
Based on requirements of customer, on-site customer, product management will
adjust user stories, estimate time and extract into core tasks, project manager create
release planning and iteration planning after that, tester write unist test (Test first
development) and assign tasks to programmer in pairs, pairs programmer write code
and execute unit test parallelly. After finish code, tester and product manager, onsite
customer will do acceptance test and deliver to customer the first release and move
to refactoring or next iteration.
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 9/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
In this project we have 2 iteration.
9 Roles and ResponsibilitiesThe following list of responsibilities of roles is taken from XP.
Role Responsibilities Participant(s)
Project
Manager
Schedules meetings (e.g.
Iteration Plan, Release
Plan), makes sure the
meeting process is
followed, records results
of meeting for futurereporting, and passes to
the Tracker.
Make sure plan is being
followed.
Improve planning process.
Maintain the plan.
Goes to meetings, brings
back useful information
Man
Product
Manager
Keep the architecture and
detailed design up to date.
Ensure architectural
drivers are met.
Maintain the Test
Specification.
Maintain the development
checklists.
Make decisions about
changes in thearchitecture.
Vu, Nhu, Huy
Interaction
Designer
Write and clarify use
cases and other
requirements with the
customer.
Lead usability tests, and
analyze results.
Define and refine the user
interface.
Huy, Nhu
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 10/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
Programmer Estimate tasks.
Detailed design
Write code and tests.
Gradually improve thedesign.
.
M.Thi, Chung
Customer/
On-site
customer
Writes User Stories and
specifies Functional Tests
Sets priorities, explains
stories
May or may not be an
end-user
Has authority to decide
questions about the stories
Anthony
Man, Vu
Mentor/Coach Watches everything, sends
obscure signals, makes
sure the project stays on
course
Helps with anything
Applies “Rolled Up
Newspaper” as required
Cliff
Tracker Monitors Programmers’
progress, takes action if things seem to be going
off track.
Actions include setting up
a meeting with Customer,
asking Coach or another
Programmer to help
Man
Tester Implements and runs
Functional Tests (not Unit
Tests!)
Graphs results, and makessure people know when
test
results decline
T.Thi, Anh
Other roles:
User Guide/
installation
Write user’’s guide,
Installation Release for
customers, user’s training
T.Thi, Anh
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 11/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
10 Communication, Tracking, and Reporting PlanThe regular reports and communications expected of the project, such as weekly
status reports, regular reviews, and as-needed communication. The exact types of communication vary between groups at the start of the project. Specify the reporting
mechanisms, report contents, and information flows used to communicate the status
of requirements, schedule, budget, quality, risks, and other status indicators both
within the project and to external stakeholders. A table such as that below is a
convenient way to describe the communication expectations.
11 PROJECT TEAM INFORMATION
NAME E-MAIL ADDRESS NOTE
MAN NGUYEN DUC mannd@duytan.edu.vn Team lead
VU TRUONG TIEN vudalat@yahoo.com
NHU NGUYEN GIA nguyengianhu@gmail.com
Type of Communication
CommunicationSchedule
TypicalCommunication
MechanismWho Initiates Recipient
Status Report every Friday team meeting ProjectManager
Project Team
Schedule andEffort TrackingReport
weekly Email/ Googledocs
ProjectManager
Project Team
Project Review weekly face to face ProjectManager
Project Team
Risk MitigationStatus as mitigationactions arecompleted
Email responsibleteam member Project Manager
RequirementChanges
as changes areapproved
email and changecontrol tool
client affected ProjectParticipants
Project Review,ask problems
Every Thursday Team meetingwith Mentor
PM Project Team,Mentor
Ask, reviewproblems
Weekly (if yes) Email / face toface
Member /individual
Mentor and Teammember
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 12/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
HUY NGUYEN D. QUANG nguyendangquanghuy@yahoo.com
THI NGUYEN T. MINH thimtnguyen2005@yahoo.com
ANH NGUYEN QUANG quanganhsdtu@gmail.com
CHUNG LE VAN chunglvcit@gmail.com
THI TRINH S. TRUONG trinhsutruongthi@gmail.com
Project Team Mentor: Clifford Huff, c2huff@gmail.com, cch@sei.cmu.edu ; Project Client: Anthony Lattanze, attanze@cs.cmu.edu
12 Internal trainingDesign tools
Microsoft Project 2007: development leader
Development tools
Coding convention and tools introduction: overall members
Java Media
Test tools
Junit: test team
Process
XP Process: all team
13 TECHNICAL APPROACHThis system will be implemented on Windows OS, including stand-alone
system and/or distributed system. Using configuration parammeter to config
stand-alone or distributed. System should be client/server application.
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 13/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
14 TESTING DESIGNSoftware will be written and debugged in environment: an emulator on a Windows
computer to test the data and a fully functional version of the Jukebox. Eachportion of the code will be tested at least twice in each environment, in the design
and one linking stages. Design refers to the compilation and running of the code
before the completion of the encapsulated object. One linking refers to the
attachment of two independent pieces of encapsulated code. As each piece links,
the whole product subsequently becomes tested. Extensive piecewise testing is
required due to the huge size of the total code and the many threading problems that
may arise. We use TDD methodology.
This is cycle of test.
See details in VJS.Test plan document and VJS.Test cases document.
15 RISKS AND RISK MANAGEMENTThe team leader will generate a separate Risk Management Plan document.
Risks will be identified at the beginning of each phase and the team leader
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 14/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
will assemble them into a prioritized risks list. During the weekly status meeting,
the team members will raise risks and reassess the prioritized risks and if necessary,
revise the list. The team will use a “Risk Statement.” Team members will determinemitigation plans for all identified risks and tasks that need to be completed and then
these risks and tasks will be assigned as action items. The team will monitor high
priority risks every week. All risks will be documented by the team.
Initial Project Risk Assessment
Risk Risk Level
L/M/H
Likelihood
of Event
Mitigation Strategy
Estimated Project
Schedule
L Likely Created comprehensive
project timeline with
frequent baseline reviews
Available
documentation clouds
establishment of
baseline
M: More than 75%
complete/current
Likely Balance of information to
be gathered by consultant
Number of Team
Members
Unknowledgeable of
Business
L: Team well
versed in business
operations impacted
by technology
Unlikely Project Manager and
Mentor to identify
knowledge gaps and
provide training, as
necessary
Project Team’s Shared
Work Experience
creates poor working
relationship
M: Some have
worked together
before
likely Comprehensive
Communications Plan
Procurement
Methodology Used
foreign to team
H: Procurement
Methodology not
familiar to team
Certainty PM trains to team
members, Individual can
contact to mentor for
advices, coach.
Team’s experiences in
java progamming
M: few members
can program in java
Likely N/A
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 15/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
16 Quality assurance process
Quality Objectives
The quality objectives for the project are given below. These will be intermittently checked
with the clients and additional objectives may be added based on client perception for
quality.
No
.
Factor Description
1 TimelinessDeliver products on time
2 FunctionalityShould meet all requirements as specified in user
stories
3 ReliabilityShould meet the following criteria:
- No major defects.
- (Number of errors found in acceptance test phase) /
(Effort of project) <= 1
Metrics
The software metrics planned to be utilised during this assignment are listed in Table
below.
Type Metric Unit of
Measures
Estimation Frequency
Timeliness Product % >= 90% At final
release
Effort Product Man-Day (30 MD) Weekly
Correctnes
s
Product Total defects No major defects.
(Number of errors found
in acceptance test phase)
/ (Effort of project) <= 1
At final
release
Elapsed
time
Project day 36days At final
release
Tests and Reviews
Phase Qualified item No. &
Type of
review
Estimated
effort (person
days)
Exit criteria
Start-Up Project Plan
Review
External(2
)
1 Approved by PM
Internal review Internal(3) 1 Total Fatal = 0
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 16/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
Phase Qualified item No. &
Type of
review
Estimated
effort (person
days)
Exit criteria
PP Total Serious = 0
Analysis &
Design
Internal System
Design Review
Internal(3) 1 Approved by PL
Review System
Design
External(3
)
1 Approved by PM
Coding Review Source
Code
Internal(3) As Needed (4) Total Fatal = 0
Total Serious = 0
Approved by PL
System Test System Test planreview
Internal(3) 1 Approved by PL
Updated System
test plan review
Internal(3) As Needed Approve by PL
Final Inspection
of all deliverables
Internal(3) 1 Fatal = 0
Cosmetic < 10
TOTAL person days
Problem Report and Corrective Action
These aspects of quality assurance are covered by FPT project quality procedures.
No
.
Activity Frequency Template No
1 Review reporting & defect
logging
Weekly and
on demand
(Test Plan)
2 Program code review Weekly and
on demand
3 Problem reporting On demand
Record Collection and Maintenance
Quality records will be collected and maintained during the project
implementation. Quality records include (this section can link to the list of
Project Quality Records)
No
.
Activity References
1 Review Records
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 17/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
2 Progress Reports
4 Meeting Minutes
5 Test Plan6 Changes Reports
7 Changes Analysis Reports
17 Configuration management
Products supplied by customer
Item No. Item Name Description
1 User’s Requirements
2 Stories
Configuration Items
Item No. Item Name
1. Project Plan2. User stories
3. Coding Convention
4. System Analysis and Design
5. Source code
6. Test Plan
7. Time log (using google spreadsheet)
8. Test case
9.
Naming Convention
The naming convention followed will be specified in the Code Standards and
Guidelines Documents (Coding Standard v1.1)
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 18/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
18 Tools, and Techniques
The hardware, OS, and network environments for development, test, and
operation: PC OS Windows XP, Vista for client, Vista or Windows 7 for server.
Software tools including those for requirements management, design modeling,
source code and document version control: Java Media, StarUML, MS Project
2007, Google spreadsheet.
19 Master Schedules
Milestone Deliverable Finish Date
1 Project Plan 20-jun-2010
2 User stories 28-jun-2010
3 System Design 10-jul-2010
4 Coding & integrated test 25-jul-2010
5 Acceptance Test 27-jul-2010
6 Final Release & Delivery 30-jul-2010
Details in Iteration Planning document, Schedule document
20 WORK BREAKDOWN STRUCTURE
Planning – Project Management
• Project Scope/High Level Requirements
• Project Plans
• Commit Decision
– Release Planning
• Release Planning Session
• Deliverables
• Risk Assessment
• Story List
• Stories Prioritization
• Stories Estimate
• Story Tests
• Conceptual Data Model
• Reqs Traceability Matrix
8/8/2019 VJS Project Plan v1.2
http://slidepdf.com/reader/full/vjs-project-plan-v12 19/19
Virtual JukeBox System
SEGVietnam Program
Master Project Plan
Jun, 21st
2010
• Release Planning Baseline
• Development 1
– Iteration Planning & Execution
• Iteration Planning
• Story List Maintenance
• Story Tests Maintenance
• Environments Set Up
• Unit Test Code
• Code
• Unit Test Execution
• Architectural Designs
• Detailed Designs
• Detailed Iteration Task List
• Iteration Planning Baseline
– Implementation
• Release Documentation
• Post Implementation Support Documentation
• User Documentation
• Technical Implementation Guide
• Day 1Testing
• Deployment 2
– Project Management
• Project Plan Maintenance and Execution
• Team Performance Feedback
• Team Celebration / Recognition
• Closure Decision
– Implementation
• Training Execution
• Technical Implementation Guide Execution
• Production System Checkout
• Release of Planned Deliverable
• Implementation Stabilization
• Implementation Baseline
21 References