Online Movie Ticket Sale Ordering: System Development Project

This project report details the development of an online movie ticket sale ordering system, focusing on project management principles. It begins with a comparison of the Modified Waterfall Model and Extreme Programming, outlining their advantages and disadvantages in the context of software development. The report then presents a Work Breakdown Structure (WBS) for the first iteration, detailing tasks, durations, and dependencies. A Gantt chart visually represents the project timeline, illustrating the critical path and assumptions made during planning. Finally, the report includes an economic cost feasibility analysis, calculating the break-even period, Net Present Value (NPV), and Return on Investment (ROI) to assess the project's financial viability. The analysis considers both one-time and recurring costs, along with projected revenues over a five-year period, providing a comprehensive overview of the project's economic feasibility and potential profitability.

Running head: PROJECT MANAGEMENT
Online Movie Ticket Sale Ordering
[unit name]
[unit code]
[student full name]
[student ID]
[campus]
[lecturer]

1
PROJECT MANAGEMENT
Table of Contents
Task 1. System Development Methodology....................................................................................1
1.1. Waterfall Model and Extreme Programming Description....................................................1
1.2. Comparison between Modified Waterfall Model and Extreme Programming.....................3
Task 2. Work Breakdown Structure................................................................................................4
2.1. WBS for First Iteration.........................................................................................................4
Task 3. Project Gantt Chart.............................................................................................................6
3.1. Gantt Chart............................................................................................................................6
3.2. Explanation and Assumptions..............................................................................................7
Task 4. Economic Cost Feasibility/ Project Budgeting...................................................................8
4.1. Cost Benefit Analysis...........................................................................................................8
4.1.1. Break Even Period.........................................................................................................8
4.1.2. Net Present Value and ROI............................................................................................9
4.2. Explain Breakeven Period..................................................................................................11
4.3. Explain Return on Investment........................................................................................11
Bibliography..................................................................................................................................13

2
PROJECT MANAGEMENT
List of Figures
Figure 1: Modified Waterfall Model...............................................................................................3
Figure 2: Extreme Programming.....................................................................................................3
Figure 3: Gantt Chart developed for the project..............................................................................7
Figure 4: Payback Period of the Project........................................................................................10

3
PROJECT MANAGEMENT
Task 1. System Development Methodology
1.1. Waterfall Model and Extreme Programming Description
Modified Waterfall Model: The limitation of the traditional waterfall model has been
eliminated with the introduction of the modified waterfall mode. Kumar and Bhatia (2014)
illustrated that the modified waterfall model enables task overlapping and going back to the
previous task if any modification were required providing flexibility in the software development
project. Further, modified waterfall model focuses on the proper documentation thus promoting
discipline within the software development process. In addition to that, the modified waterfall
model uses the same phases as the traditional waterfall model but allows the project team to
divide the project into sub-projects for reducing the complexity of the development.
Figure 1: Modified Waterfall Model
(Source: Stoica, Mircea & Ghilic-Micu 2013, p.64)

4
PROJECT MANAGEMENT
Extreme Programming: Extreme Programming is often defined as advanced
methodology used for software project development. Turk, France and Rumpe (2014) have
showed extreme programming as one of the methods of agile development focusing on the
adaptability of process and events rather than predictability. The significant aim of extreme
programming is to include the changes and modification in the customer requirement for
improving the overall quality and standard of the software. Furthermore the application of
extreme programming enhances the responsiveness in regards to the changes in requirement
within the software.
Figure 2: Extreme Programming
(Source: Estler et al., 2014, p. 1224)

5
PROJECT MANAGEMENT
1.2. Comparison between Modified Waterfall Model and Extreme Programming
The comparison of Modified Waterfall Model and Extreme Programming based on their
advantages and disadvantages are discussed in the section below:
Criterion Extreme Programming Modified Waterfall Model Advantage in
Sequence of
Task
In Extreme Programming, the
activities required in software
developed are done in smaller
portion with each iteration.
In Modified waterfall model, each
phase is being completed at a time
after proceeding to next one.
Extreme
Programming
Pattern Due to the incorporation of changes
within the project, revisit of phases
is possible in any time.
Being sequential in nature,
revisiting of any phase is only
possible after completion of one
phase.
Extreme
Programming
Developmen
t time
Due to unlimited number of
feedback and modification
incorporation there exists no
constrain in completion time.
The development time provided
for modified waterfall model is
limited.
Modified
Waterfall
Model
Feed Back Extreme Programming is customer
centric therefore incorporates
feedback after completion of each
iteration.
Customer feedback is considered
only after the completion of the
entire project.
Extreme
Programming
Quality Quality is the vital feature of the
process. Extreme Programming
methods aim at improving the
software quality with customer
Quality is provided in the project
based on the initial requirement of
the customer.
Extreme
Programming

6
PROJECT MANAGEMENT
Criterion Extreme Programming Modified Waterfall Model Advantage in
feedback in each phase.
Risk Factor Due to the customer involvement
and iterative process, risks have
less impact on the project.
Risks involved based due to
change in customer requirement
and feedback at the end of the
product delivery.
Extreme
Programming
Task 2. Work Breakdown Structure
2.1. WBS for First Iteration
Task ID Task Description
Duration
(effort in
Days)
Predecessors Tasks
IDs
0 Online Movie Ticket Sale Ordering 99 days
1 start project 0 days
2
first iteration for movie date, time and
ticket selection
25 days
2.1
requirement analysis for time, date and ticket
selection
3 days 1
2.2 developing design 5 days
2.2.1 design for date selection 4 days 3

7
PROJECT MANAGEMENT
Task ID Task Description
Duration
(effort in
Days)
Predecessors Tasks
IDs
2.2.2 design for time selection 3 days 3
2.2.3 design for ticket selection 5 days 3
2.3 implementation 9 days
2.3.1 coding for date selection 9 days 5,6,7
2.3.2 coding for time selection 3 days 5,6,7
2.3.3 coding for ticket selection 6 days 5,6,7
2.4 testing 7 days
2.4.1 black box testing 5 days 9,10,11
2.4.2 unit testing 2 days 13
2.5 Customer feedback 1 day 14
2.6 end of first iteration 0 days 15

8
PROJECT MANAGEMENT
Task 3. Project Gantt Chart
3.1. Gantt Chart
ID Task Name Duration Start Finish Predecessors Resource Names
0 Online Movie Ticket Sale
Ordering
99 days Tue 8/15/17 Fri 12/29/17
1 start project 0 days Tue 8/15/17 Tue 8/15/17 member 1
2 first iteration for movie date,
time and ticket selection
25 days Tue 8/15/17 Mon 9/18/17
3 requirement analysis for time,
date and ticket selection
3 days Tue 8/15/17 Thu 8/17/17 1 member 2
4 developing design 5 days Fri 8/18/17 Thu 8/24/17
5 design for date selection 4 days Fri 8/18/17 Wed 8/23/17 3 member 4
6 design for time selection 3 days Fri 8/18/17 Tue 8/22/17 3 member 1
7 design for ticket selection 5 days Fri 8/18/17 Thu 8/24/17 3 member 2
8 implementation 9 days Fri 8/25/17 Wed 9/6/17
9 coding for date selection 9 days Fri 8/25/17 Wed 9/6/17 5,6,7 member 4
10 coding for time selection 3 days Fri 8/25/17 Tue 8/29/17 5,6,7 member 1
11 coding for ticket selection 6 days Fri 8/25/17 Fri 9/1/17 5,6,7 member 2
12 testing 7 days Thu 9/7/17 Fri 9/15/17
13 black box testing 5 days Thu 9/7/17 Wed 9/13/17 9,10,11 member 3
14 unit testing 2 days Thu 9/14/17 Fri 9/15/17 13 member 4
15 Customer feedback 1 day Mon 9/18/17 Mon 9/18/17 14 member 2
16 end of first iteration 0 days Mon 9/18/17 Mon 9/18/17 15 member 1
17 second iteration for developing
payment and contact details
38 days Tue 9/19/17 Thu 11/9/17
18 requirement analysis for
contact and payment
3 days Tue 9/19/17 Thu 9/21/17 16 member 3
19 developing design 7 days Fri 9/22/17 Mon 10/2/17
20 design for contact details
selection
4 days Fri 9/22/17 Wed 9/27/17 18 member 1
21 design for payment process 7 days Fri 9/22/17 Mon 10/2/17 18 member 2
22 implementation 17 days Tue 10/3/17 Wed 10/25/17
23 coding for contact details 5 days Tue 10/3/17 Mon 10/9/17 20,21 member 3
24 coding for payment process 17 days Tue 10/3/17 Wed 10/25/17 20,21 member 4
25 testing 10 days Thu 10/26/17 Wed 11/8/17
26 black box testing 6 days Thu 10/26/17 Thu 11/2/17 23,24 member 1
27 unit testing 4 days Fri 11/3/17 Wed 11/8/17 26 member 2
28 Customer feedback 1 day Thu 11/9/17 Thu 11/9/17 27 member 3
29 end of second iteration 0 days Thu 11/9/17 Thu 11/9/17 28 member 4
30 iteration three for receipt
generation
35 days Fri 11/10/17 Thu 12/28/17
31 requirement analysis for
receipt generation
5 days Fri 11/10/17 Thu 11/16/17 29 member 1
32 developing design 3 days Fri 11/17/17 Tue 11/21/17
33 design for generating reciepts3 days Fri 11/17/17 Tue 11/21/17 31 member 2
34 implementation 17 days Wed 11/22/17 Thu 12/14/17
35 coding for receipt generation17 days Wed 11/22/17 Thu 12/14/17 33 member 3
36 testing 9 days Fri 12/15/17 Wed 12/27/17
37 black box testing 4 days Fri 12/15/17 Wed 12/20/17 35 member 1
38 unit testing 5 days Thu 12/21/17 Wed 12/27/17 37 member 2
39 Customer feedback 1 day Thu 12/28/17 Thu 12/28/17 38 member 3
40 end of second iteration 0 days Thu 12/28/17 Thu 12/28/17 39 member 3
41 software hand over 1 day Fri 12/29/17 Fri 12/29/17 40 member 4
42 stop project 0 days Fri 12/29/17 Fri 12/29/17 41 member 1
8/ 15
member 2
member 4
member 1
member 2
member 4
member 1
member 2
member 3
member 4
member 2
9/ 18
member 3
member 1
member 2
member 3
member 4
member 1
member 2
member 3
11/ 9
member 1
member 2
member 3
member 1
member 2
member 3
12/28
member 4
12/ 29
11 14 17 20 23 26 29 1 4 7 10 13 16 19 22 25 28 1 4 7 10 13 16 19 22 25 28 31 3 6 9 12 15 18 21 24 27 30 3 6 9 12 15 18 21 24 27 30 2 5
August 2017 September 2017 October 2017 November 2017 December 2017 January 2018
Figure 3: Gantt Chart developed for the project
(Source: Created by Author in MS Project)

9
PROJECT MANAGEMENT
3.2. Explanation and Assumptions
The above Gantt chart represents the time tine and activities that needs to be done for the
completion of Online Movie Ticket Sale Ordering system. In this project Extreme Programming
Methodology has been followed and the entire project has been divided into three iterations
namely the development of “movie time, date and ticket selection”, secondly “payment and
contact details” and thirdly, “the generation of receipts”. The phases of development including
requirement analysis, planning, coding and testing are repeated within each phase. Furthermore
the project has been four months and two weeks. Four team members were included within the
project that has played several roles including coder and system designer within the project. The
red line in the Gantt chart represents the critical path for developing the software for movie ticket
booking.

10
PROJECT MANAGEMENT
Task 4. Economic Cost Feasibility/ Project Budgeting
4.1. Cost Benefit Analysis
4.1.1. Break Even Period
year One time Cost Recurring Cost Total
Investment
Revenue Cumulative cash flow Net Cash Flow Discounted Cash
Flow
Net Discounted
Cash Flow
Break Even
Period
Year 0 $ 15,000.00 $ 15,000.00 $ (15,000.00) $ 15,000.00) $ (15,000.00) $ (15,000.00)
3.276117112
Year 1 $ 5,500.00 $ 5,500.00 $ 12,000.00 $ (8,500.00) $ (23,500.00) $ (7,905.00) $ (22,905.00)
Year 2 $ 5,115.00 $ 5,115.00 $ 15,000.00 $ 1,385.00 $ (22,115.00) $ 1,288.05 $ (21,616.95)
Year 3 $ 4,756.95 $ 4,756.95 $ 18,000.00 $ 14,628.05 $ (7,486.95) $ 13,604.09 $ (8,012.86)
Year 4 $ 4,423.96 $ 4,423.96 $ 21,000.00 $ 31,204.09 $ 23,717.14 $ 29,019.80 $ 21,006.94
Year 5 $ 4,114.29 $ 4,114.29 $ 24,000.00 $ 51,089.80 $ 74,806.94 $ 47,513.51 $ 68,520.45

11
PROJECT MANAGEMENT
Figure 4: Payback Period of the Project
(Source: Created by Author in MS Excel)
4.1.2. Net Present Value and ROI
Year Net Economic Benefits Discounted Rate @ 7% PV of Benefits NPV of all Benefits total benefits
Year 0 $ - 1 $ - $ -
Year 1 $ 12,000.00 0.93 $ 11,160.00 $ 11,160.00
Year 2 $ 15,000.00 0.86 $ 12,900.00 $ 24,060.00
Year 3 $ 18,000.00 0.79 $ 14,220.00 $ 38,280.00
Year 4 $ 21,000.00 0.72 $ 15,120.00 $ 53,400.00
Year 5 $ 24,000.00 0.65 $ 15,600.00 $ 69,000.00 $ 69,000.00
One Time Costs
Development Cost $ 15,000.00

12
PROJECT MANAGEMENT
Year Recurring Costs Discount rate @ 7% PV of Recurring Costs NPV of all Benefits total benefits
Year 0 $ - 1 $ - $ 15,000.00
Year 1 $ 5,500.00 0.93 $ 5,115.00 $ 20,115.00
Year 2 $ 5,115.00 0.86 $ 4,398.90 $ 24,513.90
Year 3 $ 4,756.95 0.79 $ 3,757.99 $ 28,271.89
Year 4 $ 4,423.96 0.72 $ 3,185.25 $ 31,457.14
Year 5 $ 4,114.29 0.65 $ 2,674.29 $ 34,131.43 $ 34,131.43
Overall NPV $ 34,868.57
Overall ROI 1.021597094

13
PROJECT MANAGEMENT
4.2. Explain Breakeven Period
Breakeven period for a project is used for representing the period of time required to
taken by the total cash flow required for the project for offsetting the investment cost required for
developing the project. For the project for the development of the Online Movie Ticket sale
system, breakeven period represents the time period required for recovering the one tine
investment for system development and recurring maintenance cost from the benefits earned
from the system implementation.
For the project of “Online Movie Ticket Sale Ordering”, the breakeven period is found to
be 3.27 years.
To the customer, the value represents that the entire investment and recurring cost
required for developing and maintaining the “Online Movie Ticket Sale Ordering” will be
recovered within the period of 3.27 years.
4.3. Explain Return on Investment
ROI or Return on Investment is often used for representing the financial and economic
benefits obtained from any investment put in any project.
ROI can be defined as a measurement used for determining the loss or gain obtained from
a project based on the total investment made for the project.
In this project, for the development of the “Online Movie Ticket Sales” the ROI obtained
is 1.021.

14
PROJECT MANAGEMENT
To the customer, it means that after the end of five years the customer would gain the
benefits of 1.021 % of the total investment made or the development and maintenance of the
system.
In this project, the ROI obtained is positive reflecting that the project worth continuing as
it will yield profitability within five years.

15
PROJECT MANAGEMENT
Bibliography
Choudhari, J., & Suman, U. 2014. Extended iterative maintenance life cycle using eXtreme
programming. ACM SIGSOFT Software Engineering Notes, 39(1), 1-12.
Estler, H. C., Nordio, M., Furia, C. A., Meyer, B., & Schneider, J. 2014. Agile vs. structured
distributed software development: A case study. Empirical Software Engineering, 19(5), 1197-
1224.
Fitzgerald, B., & Stol, K. J. 2014, June. Continuous software engineering and beyond: trends and
challenges. In Proceedings of the 1st International Workshop on Rapid Continuous Software
Engineering (pp. 1-9). ACM.
Goto, T., Tsuchida, K., & Nishino, T. 2014. EPISODE: AN EXTREME PROGRAMMING
METHOD FOR INNOVATIVE SOFTWARE BASED ON SYSTEMS DESIGN AND ITS
PRACTICAL STUDY. International Journal of Software Engineering & Applications, 5(5), 1.
Kaur, R., & Sengupta, J. 2013. Software process models and analysis on failure of software
development projects. arXiv preprint arXiv:1306.1068.
Kazim, A. 2017. A Study of Software Development Life Cycle Process Models. International
Journal of Advanced Research in Computer Science, 8(1).
Khan, M. A., Parveen, A., & Sadiq, M. 2014, February. A method for the selection of software
development life cycle models using analytic hierarchy process. In Issues and Challenges in