University Project: RALS Ticketing System Development and Management

This project management assignment focuses on the development of a RALS ticketing system for Virtuecon. It includes a Measurable Organization Value (MOV) analysis, defining areas of impact such as customer service and profit making, with associated metrics and timeframes. The project scope is clearly defined, outlining roles, responsibilities, and a detailed Work Breakdown Structure (WBS) covering planning, requirement analysis, design, development, testing, and go-live phases. A comprehensive project schedule, including task durations, start and finish dates, predecessors, resources, and costs, is provided. The assignment also includes a risk analysis identifying potential risks during different SDLC phases and a quality management plan to ensure project success. Furthermore, the project incorporates an evaluation research section with an annotated bibliography and a closure checklist. The project demonstrates a solid understanding of project management principles and their application in a real-world scenario.

Running head: ASSIGNMENT 3: RALS
Assignment 3: RALS
Name of the Student
Name of the University

1ASSIGNMENT 3: RALS
Table of Contents
1. Measurable Organization Value:.................................................................................................2
2. Scope and Scope Management Plan:...........................................................................................5
3. Project Schedule:.........................................................................................................................8
4. Project Risk Analysis:................................................................................................................15
5. Quality Management Plan:........................................................................................................17
6. Evaluation Researching:............................................................................................................18
6.1 Annoyed Bibliography:.......................................................................................................18
6.2 Closure Checklist:................................................................................................................19
Bibliography:.................................................................................................................................20

2ASSIGNMENT 3: RALS
1. Measurable Organization Value:
Area of Impact Rank Values Appropriate Metric Time Frame
Customer
service
2 Better: The customer (or
visitor) of RALS
Event are very
much interested in
having a system
that can improve
the service quality
.
10 Days after
project
completion
Faster: The pace of work
of the system will
determine how
happy (an aspect of
customer service)
are the customers
are actually
Business
Operations
4 Cheaper The cost of
operating the
procedures of
Two months
after project

3ASSIGNMENT 3: RALS
business will get
reduced
significantly,
approximately, 40
percent.
completion
Better The quality of the
business operations
will enhance which
will cause in better
internal procedures
Management
decision making
1 Better The management
must be taking
decisions that are
eighty percent
accurate. The stored
data in the system
will allow the
management to
understand the
situation better
One year after
project
completion
Do More The management
want the system to
be hundred percent

4ASSIGNMENT 3: RALS
accurate in decision
making
Resource
allocation
6 Faster The system will be
assisting the
management to
determine which
resource is required
in which place and
in what quantity
Two years
after project
completion
Do more Virtuecon wants the
system to produce a
report that can
allow the
management to rely
on system
completely on
resource allocation
process
Profit making 3 Faster The organization
will selling tickets
faster than ever and
better customer
service will allow
After
completion of
project

5ASSIGNMENT 3: RALS
more profit
Do more The system will be
capable of
contacting the
customers so that
customer loyalty
remains intact
2. Scope and Scope Management Plan:
Scope of project:
1) An information system capable of generating and checking ticket
2) Developing the system within budget
3) Providing profit to Virtuecon
4) Communicating with the stakeholders
5) Generating a plan for development
6) Taking approval for major decisions
Roles and Responsibility:
Role Responsibility
Project Sponsor Agree or refute scope change requests as
suitable
Project Manager Handling overall project in-scope

6ASSIGNMENT 3: RALS
Analyst Gathering requirements
Designers Designing system outline
Development Team Developing system
Testing Team Testing system unit
Work Breakdown Structure:
WBS Task Name
0 RALS Ticketing System Development
1 Project Planning
1.1 Defining Project
1.2 Employing Team Members
1.3 System Requirement Identification
1.4 Deliverables
1.5 Scope Defining
1.6 Scheduling
1.7 End of Planning Phase
2 Requirement Analysis Phase
2.1 Requirement gathering

7ASSIGNMENT 3: RALS
2.2 Requirement Evaluating
2.3 Determining System Functionalities
2.4 Functional Requirement
2.5 Non Functional Requirement
2.6 End of Requirement Analysis Phase
3 Designing Phase
3.1 System Architecture Development
3.2 System UML Designing
3.3 ERD Generating
3.4 Network Planning
3.5 End of Designing Phase
4 Development
4.1 Develop Programs
4.2 Develop Database
4.3 Develop Network
5 Testing Phase
5.1 Black Box testing

8ASSIGNMENT 3: RALS
5.2 Unit Testing
5.3 Database Testing
6 Go Live
6.1 Connect Database with System
6.2 Connect System with Network
6.3 Deploy System in RALS Environment
Scope Verification: The project manager checks that the project scope are suitable as per
the project deliverables or not. In case, the project scope is found able to meet the requirements
defend in project plan, then the scope are considered as verified.
3. Project Schedule:
WBS Task Name Duration Start Finish Predecessors Resource Names Cost
0
RALS
Ticketing
System
Developme
nt
55 days
Mon
10/12/
09
Fri
12/25/0
9
$19,544.00
1 Project
Planning
8 days Mon
10/12/
Wed
10/21/0
$2,592.00

9ASSIGNMENT 3: RALS
09 9
1.1
Definin
g Project
1 day
Mon
10/12/
09
Mon
10/12/0
9
Project manager $352.00
1.2
Employi
ng Team
Members
2 days
Tue
10/13/
09
Wed
10/14/0
9
2 Project manager $704.00
1.3
System
Requiremen
t
Identificatio
n
2 days
Thu
10/15/
09
Fri
10/16/0
9
3 Analysts $480.00
1.4
Delivera
bles
1 day
Mon
10/19/
09
Mon
10/19/0
9
4 Project manager $352.00
1.5
Scope
Defining
1 day
Tue
10/20/
09
Tue
10/20/0
9
5 Project manager $352.00
1.6 Schedul
ing
1 day Wed
10/21/
Wed
10/21/0
6 Project manager $352.00

10ASSIGNMENT 3: RALS
09 9
1.7
End of
Planning
Phase
0 days
Wed
10/21/
09
Wed
10/21/0
9
7 $0.00
2
Require
ment
Analysis
Phase
8 days
Thu
10/22/
09
Mon
11/2/09
$1,920.00
2.1
Require
ment
gathering
2 days
Thu
10/22/
09
Fri
10/23/0
9
8 Analysts $480.00
2.2
Require
ment
Evaluating
3 days
Mon
10/26/
09
Wed
10/28/0
9
10 Analysts $720.00
2.3
Determi
ning System
Functionalit
ies
1 day
Thu
10/29/
09
Thu
10/29/0
9
11 Analysts $240.00
2.4 Functio
nal
Requiremen
1 day Fri
10/30/
Fri
10/30/0
12 Analysts $240.00

11ASSIGNMENT 3: RALS
t 09 9
2.5
Non
Functional
Requiremen
t
1 day
Mon
11/2/0
9
Mon
11/2/09
13 Analysts $240.00
2.6
End of
Requiremen
t Analysis
Phase
0 days
Mon
11/2/0
9
Mon
11/2/09
14 $0.00
3
Designing
Phase
10 days
Tue
11/3/0
9
Mon
11/16/0
9
$3,040.00
3.1
System
Architectur
e
Developme
nt
2 days
Tue
11/3/0
9
Wed
11/4/09
15 Designing Team $480.00
3.2
System
UML
Designing
3 days
Thu
11/5/0
9
Mon
11/9/09
17
Designing Team,
Development
Environment
$960.00
3.3 ERD 2 days Tue Wed 18 Designing Team, $640.00