University Report: Information System Development for Tourism Business

This report details the development of an information system for a private tourism business in Australia. It begins with a letter of transmittal and table of contents, followed by an introduction outlining the need for a new system to address inefficiencies in the current manual processes. The report covers assumptions, limitations, and the background of the project, including the business's goals of increasing efficiency, improving customer service, and adapting to changes. The scope of the project is clearly defined, specifying in-scope and out-of-scope factors. The project outcome focuses on the benefits of the new system, such as improved information access and reduced operational costs. Resource requirements are detailed, including skill levels, materials, and associated tasks. The report includes a project schedule with a Gantt chart, work breakdown structure, milestones, deliverables, and a cost estimate. Finally, recommendations and a conclusion are provided, along with a bibliography.

Running head: DEVELOPMENT OF INFORMATION SYSTEM
Development of Information System for Private Tourist Business
Name of the Student:
Name of the University:

1DEVELOPMENT OF INFORMATION SYSTEM
Letter of transmittal
To
Helen Anthony
JC Tourism
Unit 5, Business Park
Australia
Date: 4th September, 2017
Subject: Request to give fund for development of information system into private tourism
business
Respected Mrs. Anthony,
Our tourism business aims to provide different tourism destinations to the tourists. The
management board of the private tourist business identified some of the issues such as the
process for the customers to gain of entry into the business is slow. The customers are not getting
proper information about their tourist business. Even the cost of printing brochures as well as
maps to inform the customers about various attractions are rising and the tourist attraction
brochures are out of data as it is not upgraded and maintained about various attractions. There is
manual facility management and all the problems are manually tracked as well as assigned to the
technicians. The manual process is very time consuming and therefore the business decides to
develop a core information system that would provide full services to the customers through
latest handheld wireless devices. In order to develop the system, we need funding of $7000. If
you are interested to provide us fund and become sponsor for our business, then please fill free to
contact us. I will pursue up via phone within a week to see if you have any questions that I can
respond about the proposal.
Thanking you,
Sincerely,
(Please enter your name)
Project Manager
Australian Tourism

2DEVELOPMENT OF INFORMATION SYSTEM
Table of Contents
Introduction......................................................................................................................................3
1.0 Assumptions and limitations with justifications based on project requirements.......................3
2.0 Background of the project.........................................................................................................4
3.0 Scope of the project...................................................................................................................5
4.0 Description of project outcome.................................................................................................7
5.0 Description of resource requirements........................................................................................8
6.0 Scheduling Tasks and WBS.....................................................................................................10
6.1 Project Schedule..................................................................................................................10
6.2 Gantt chart on project plan..................................................................................................13
6.3 Work breakdown structure (WBS)......................................................................................14
6.4 Project Milestones...............................................................................................................14
6.5 Project Deliverables.............................................................................................................15
6.6 Slack....................................................................................................................................15
7.0 Initial cost estimate on development of information system...................................................17
Recommendation and Conclusion.................................................................................................20
Bibliography..................................................................................................................................21

3DEVELOPMENT OF INFORMATION SYSTEM
Introduction
The report is based on developing a business case for tourist attraction into major
Australian highway. The private tourist business decides to develop business information system
to attract domestic as well as international customers. The proposed core information system
should accommodate fixed as well as wireless devices. Currently, the approach for tourist
attraction, updating and managing of information are manual, error prone as well as time
consuming. It deals with various huge quantities of information that are generated from hundreds
of sources across the tourist business. The existing system for managing of data is inefficient for
the tourists as it is not providing access to information in timely way. The implementation of
proposed system will provide efficiency, improve over communication and increase accuracy of
tourist attraction. The system provided support to staff and management towards tourist
attraction. The project manager develops this particular business report for CEO to provide the
management board with complete project plan for outlining the project plan.
The project plan develops the financial modeling aspects, human resource requirements,
scheduling tasks and customer interface requirements. It also summarizes the assumptions and
limitations of the project and provides a scope statement respond to the problem that the tourist
business faces due to its existing system. Scheduling tasks, work breakdown structure and
project milestones are deploying the project work. Initial project cost is estimated to meet with
business requirements within project scope. Finally, recommendations and conclusion are
provided based on the development of proposed system into private tourist business.
1.0 Assumptions and limitations with justifications based on project
requirements
Following are the assumptions of the project plan:
a) After the implementation of core information system is developed, there is no
requirement of use of InDesign software for implementation.
b) Completion of development of information system for tourist business will no longer
required of longer printing of supply of paper and manual brochures as well as catalogs.

4DEVELOPMENT OF INFORMATION SYSTEM
c) After development of proposed system into the business, there is no acceptance of paper
and manual process.
d) The project plan should complete with time as well as budget.
e) The implementation of information system should consist of required human resources
and equipments to complete it within schedule time.
f) All the project stakeholders should be present into the weekly meeting to discuss the
project related issues. The key stakeholders on project and client terms should perform
sufficiently.
g) The project deliverables submitted for the approval will return into 10 working days.
Following are the limitations of the project plan:
a) The key staff resources are available on the part time basis only. The key client
resources are to be available on restricted basis.
b) The deliverables which are submitted for the approval will require at least of 5
working days for purpose of review.
c) The order lead time of the equipments and raw materials are not specified with priper
precision.
d) The project plan does not consist of executive sponsor as well as steering committee.
e) The development of the system is new and the components are not successfully
incorporated.
2.0 Background of the project
The success of tourism business in Australia is based on capability of the country to
develop, manage as well as marketing of tourism facilities in the country. The project is based on
developing a project case on major tourist attraction along the highway of Australia. The
management board of the private tourist business identified some of the issues such as the
process for the customers to gain of entry into the business is slow. The customers are not getting
proper information about their tourist business. Even the cost of printing brochures as well as
maps to inform the customers about various attractions are rising and the tourist attraction
brochures are out of data as it is not upgraded and maintained about various attractions. There is
manual facility management and all the problems are manually tracked as well as assigned to the

5DEVELOPMENT OF INFORMATION SYSTEM
technicians. The manual process is very time consuming and therefore the business decides to
develop a core information system that would provide full services to the customers through
latest handheld wireless devices. The management board likes to develop an integrated and up-
to-date system for developing of staffs as well as management towards tourist attraction. The
objectives of this project study are:
 To increase efficiency and effective operations of private tourist business
 To improve the customer service and attract domestic and international customers
 To provide better capability to adjust of expansion and changes
 To install and implement of core information management system
 To modify and simplify of administrative processes with reliable capabilities of
the software
3.0 Scope of the project
The scope of this particular project plan is to implement of core information system for
private tourist business that combines with online and integrated catalog system. The “Tourist
information database management system” will help the employees to improve their tourism.
The main scope is to develop of information system related to tourism and leveraging of employ
as well as profits for common people of Australia. The system consists of fixed as well as
wireless devices. The work of management as well as employees becomes easier. The tourist
business maintains of accurate database for the tourism personnel increases the safety. A digital
database is required to be prepared for the tourist destinations.
In-scope statement:
Following are the in-scope factors of the project plan:
a. Providing of online information to the customers on the tourist spots and time
b. The proposed infrastructure consists of support of mobile devices such as
Smartphone and tablets.
c. Upgradation and maintenance of brochures for various tourist attractions
d. The system is efficient to prepare of management reports.

6DEVELOPMENT OF INFORMATION SYSTEM
e. It includes of project guidelines for the project manager and business analyst to
follow and conduct the assigned activities.
f. It does not consist of mandatory requirements.
g. The project related framework, guidelines as well as tools are developed and it is
implemented by October 2017.
h. It includes of recognition activities for all the project departments.
i. Electronically tracking of the tourist attractions and manage of changes from
preliminary request throughout final authorization.
j. Review of the current printed as well as online brochures to be revised.
k. Development of detailed requirements of proposed system
l. Documentation of project goals, budget and project deliverables
Out of scope statement:
It is not in the scope to implement of recommend information system solution. Following
are the out of scope factors of the project plan:
a. Automated updates of changes that are made into information system
b. Automated updates of the audit requirement system when the system is updated.
c. Publishing the past issues of the current core information system.
d. Managing as well as tracking of the learning project outcomes
e. Development of training materials to be offered to the system users
f. Implementation of accurate methods for design, development purpose and also
for quality control
g. The proposed information system will support of operational activities needed
for processing of tourist registration
h. A follow up of the implementation project is created and includes of
implementation of wireless technology
i. Development of maintenance plan for use of the technology at private tourist
business
Completion of the upgrade of information system will provide with a dependable as well
as secured high speed networking environment for the tourists to gain access to the information

7DEVELOPMENT OF INFORMATION SYSTEM
online. It makes the entire process into timely manner and there is reduction of operational cost.
The scope of this particular project study is dependent on initial survey on the benefits of
information system to assure that all project assumptions are precise.
4.0 Description of project outcome
The project plan is based on development as well as resolve of issues related to its current
information system. The project outcomes are to identify the impact of information technology
into performance of private tourist business. The management board of the business wants to
implement an integrated and up-to-date system mainly developed for the staff as well as
management team of tourist attraction. The propped system provides latest handheld wireless
devices. Project management software such as Ms Project is used to control design,
implementation, testing and final closure of this project plan efficiently. There is proper
estimation of project budget and schedule and then regulate of project variables.
The integrated information system provides the customers information related to
different tourism destinations and their respective offers and prices. The custom format of the
information system makes it efficient as the data are easier to use. It provides with real time
information to the customers that help to function of business operations quickly. The benefit of
this system is that it provides with instant data conversion into functional information. The
proposed information system is flexible and it is programmed for efficient growth and
profitability of tourist business of Australia. The individual parts of the system is upgraded as
well as installed with no distraction of the entire system.
The proposed information system is a cost effective solution of the business as it reduces
the time and cost of entire project plan. The project team members communicate with each other
having exactly similar information accessible to them at every time. It saves mis-matching
among the system as well as departments. As the entire tourist’s personal data are kept secured
within information system, therefore proper data are easier for the employees to access it. All the
project stakeholders should be present into the weekly meeting to discuss the project related
issues. The key stakeholders on project and client terms should perform sufficiently. The tourist
business maintains of correct database for the tourism workers increases the safety. A digital
database is necessary to be ready for the tourist destinations.

8DEVELOPMENT OF INFORMATION SYSTEM

9DEVELOPMENT OF INFORMATION SYSTEM
5.0 Description of resource requirements
Resource
Skill level/ Material
required Associated tasks
Duration
required
Available time
period
Cost
Level of risk
Project Team Members
Project
Manager
Project management, hands
on experience with technical
writing
1. Review the project documentation
2. Plan, manage and approve the entire project plan 3 months
8 hours a day
excluding Saturday
and Sunday
$15/hr Medium
Project
Sponsor Cost estimation
1. Estimate the project cost
2. Review the funding requirements 1 month
8 hours a day
excluding Saturday
and Sunday
$10/hr Medium
IT Staff
Technical project
management and
implementation of
information system
1. Development of hardware documentation
specifications
2. Installation of hardware 3 months
8 hours a day
excluding Saturday
and Sunday
$9/hr Low
Functional
lead
Knowledge on functional
requirements of information
system for tourist attraction
1. Accurately represents of the business needs of
tourism
2. Providing and sharing of feedbacks on the
project deliverables
3. Providing of testing support
2 1\2
months
8 hours a day
excluding Saturday
and Sunday
$7/hr Medium
Business
Analyst
Analyzing the business
needs
1. Analyzing and developing of understanding of
current state of the business
2. Development of present and future needs of the
2 months 8 hours a day
excluding Saturday
and Sunday
$9/hr Low

10DEVELOPMENT OF INFORMATION SYSTEM
business
Equipments used for development of information system
Hardware
Input/output devices,
operating system, external
hard drive
1. The hardware devices are used to do daily
business management as well as administrative
tasks.
2. External hard drives are required to store various
types of information into PC or laptop 3 months -----------
$ 200 Medium
Software Programs and systems
1. Ensure of successful completion of maintenance
and monitoring tasks
2. Security of the data and information 3 months -----------
$400 Medium
Network
Hubs, network devices as
well as communication
medias
1. The network devices are required to
communicate and interact between the devices on
the computer network.
2. Hubs are used to connect of Ethernet devices to
act as single networking segment 3 months -----------
$150 Medium
Facilities for development of information system
Mechanized
warehouse Storage room
1. Designed for storage as well as handling of
project materials
2. Unload and stored of receiving of goods 3 months -----------
$70 Low

11DEVELOPMENT OF INFORMATION SYSTEM
6.0 Scheduling Tasks and WBS
6.1 Project Schedule
Task Name Duration Start Finish Resource Names
Implementation of core
information system for private
tourism business
70 days Mon 9/4/17 Fri 12/8/17
Initialization project phase 11 days Mon 9/4/17 Mon 9/18/17
Development of business case 2 days Mon 9/4/17 Mon 9/18/17 Project Manager, Project
Sponsor
Business requirements 1 day Mon 9/4/17 Mon 9/4/17 Business Analyst, Project
Manager
Project specification based on
business case 3 days Tue 9/5/17 Thu 9/7/17 Business Analyst, Project
Manager
Meeting with management board 1 day Fri 9/8/17 Fri 9/8/17 Project Manager
Milestone 1: Completion of
initialization phase 0 days Mon 9/4/17 Mon 9/4/17
Vendor selection for project plan 26 days Mon 9/4/17 Mon 10/9/17
Vendor identification based on
business requirements 6 days Mon 9/11/17 Wed 9/20/17 IT Staff, Project Manager
Vendor capability 2 days Thu 9/21/17 Mon 10/9/17 Functional lead, IT Staff
Budget plan 4 days Mon 9/11/17 Fri 9/15/17 Project Manager, Project
Sponsor
Project scheduling 3 days Mon 9/11/17 Wed 9/13/17 Project Manager
Milestone 2: Completion of
vendor selection phase 0 days Mon 9/4/17 Mon 9/4/17
Design phase of information
system 61 days Mon 9/4/17 Mon 11/27/17
Improving labor managing 6 days Mon 9/18/17 Mon 9/25/17 IT Staff
Installation of system process 5 days Fri 10/13/17 Thu 10/19/17 IT Staff

12DEVELOPMENT OF INFORMATION SYSTEM
Hardware installation 7 days Fri 10/20/17 Mon 11/27/17 Functional lead, IT Staff
Software installation 5 days Tue 9/26/17 Mon 10/2/17 Functional lead, IT Staff
Designing of the system 2 days Tue 10/3/17 Wed 10/4/17 IT Staff
Building of the system 1 day Thu 10/5/17 Thu 10/5/17 IT Staff
System requirements
identification 1 day Fri 10/6/17 Fri 10/6/17 Functional lead, IT Staff
Milestone 3: Completion of
Design phase 0 days Mon 9/4/17 Mon 9/4/17
Implementation of system 35 days Mon 9/4/17 Fri 10/20/17
Implement based on project
objectives 1 day Mon 10/9/17 Mon 10/9/17 Project Manager, Project
Sponsor
Modify the implement phase 3 days Tue 10/10/17 Thu 10/12/17 Functional lead, IT Staff
Resource and equipments
requirements 4 days Fri 10/13/17 Wed 10/18/17 Functional lead, Project
Manager
Equipments store 2 days Thu 10/19/17 Fri 10/20/17 Business Analyst,
Functional lead
Milestone 4: Completion of
Implementation phase 0 days Mon 9/4/17 Mon 9/4/17
Testing phase of the system 57 days Mon 9/4/17 Tue 11/21/17
Start to test 9 days Mon
10/23/17 Thu 11/2/17 Functional lead, IT Staff
Review the testing plan 5 days Fri 11/3/17 Thu 11/9/17 Functional lead, IT Staff
Analyzing the test outcomes 6 days Fri 11/10/17 Fri 11/17/17 Functional lead, IT Staff
Compare the outcome with
project scope 2 days Mon
11/20/17 Tue 11/21/17 Business Analyst, Project
Manager
Milestone 5: Completion of
testing phase 0 days Mon 9/4/17 Mon 9/4/17
Risk managing phase 64 days Mon 9/4/17 Thu 11/30/17

13DEVELOPMENT OF INFORMATION SYSTEM
Recognize the risks 2 days Wed
11/22/17 Thu 11/23/17 Project Manager
Address the risks 2 days Fri 11/24/17 Mon 11/27/17 Business Analyst, Project
Manager
Mitigate the risks 2 days Tue 11/28/17 Wed 11/29/17 Business Analyst, Project
Manager
Risk register 1 day Thu 11/30/17 Thu 11/30/17 Business Analyst, Project
Manager
Milestone 6: Completion of risk
management phase 0 days Mon 9/4/17 Mon 9/4/17
Final closure of the plan 70 days Mon 9/4/17 Fri 12/8/17
Evaluation of success criteria 3 days Fri 12/1/17 Tue 12/5/17 Project Manager
Delivery of final documentation 1 day Wed 12/6/17 Wed 12/6/17 Project Manager, Business
Analyst, Project Sponsor
Final review 1 day Thu 12/7/17 Thu 12/7/17 Project Manager, Project
Sponsor
Sign off the project document 1 day Fri 12/8/17 Fri 12/8/17 Project Manager, Project
Sponsor
Milestone 7: Completion of
Final closure phase 0 days Mon 9/4/17 Mon 9/4/17

14DEVELOPMENT OF INFORMATION SYSTEM
6.2 Gantt chart on project plan
Figure 1: Gantt chart

15DEVELOPMENT OF INFORMATION SYSTEM
(Source: Created by author)
6.3 Work breakdown structure (WBS)
Figure 2: Work breakdown structure
(Source: Created by author)
6.4 Project Milestones
Task Name Start
Milestone 1: Completion of initialization phase Mon 9/4/17
Milestone 2: Completion of vendor selection phase Mon 9/4/17
Milestone 3: Completion of Design phase Mon 9/4/17
Milestone 4: Completion of Implementation phase Mon 9/4/17
Milestone 5: Completion of testing phase Mon 9/4/17

16DEVELOPMENT OF INFORMATION SYSTEM
Milestone 6: Completion of risk management phase Mon 9/4/17
Milestone 7: Completion of Final closure phase Mon 9/4/17
6.5 Project Deliverables
The private tourist business will receive the following mentioned deliverables:
I. Detailed project plan as well as schedule into Ms Project
II. Regularly the scheduled reports detailed on project progress on the plan
III. Upgraded information management system to accommodate of fixed and wireless devices
IV. Wireless solution allows for internet connectivity
V. VPN solutions allow for remote access to the internal network
6.6 Slack
WBS Task Name Duration Slack
0 Implementation of core information system for
private tourism business 70 days 0 days
1 Initialization project phase 11 days 0 days
1.1 Development of business case 2 days 59 days
1.2 Business requirements 1 day 0 days
1.3 Project specification based on business case 3 days 0 days
1.4 Meeting with management board 1 day 0 days
1.5 Milestone 1: Completion of initialization phase 0 days 70 days
2 Vendor selection for project plan 26 days 5 days
2.1 Vendor identification based on business
requirements 6 days 44 days
2.2 Vendor capability 2 days 44 days
2.3 Budget plan 4 days 0 days

17DEVELOPMENT OF INFORMATION SYSTEM
2.4 Project scheduling 3 days 2 days
2.5 Milestone 2: Completion of vendor selection phase 0 days 70 days
3 Design phase of information system 61 days 10 days
3.1 Improving labor managing 6 days 0 days
3.2 Installation of system process 5 days 9 days
3.3 Hardware installation 7 days 9 days
3.4 Software installation 5 days 0 days
3.5 Designing of the system 2 days 0 days
3.6 Building of the system 1 day 0 days
3.7 System requirements identification 1 day 0 days
3.8 Milestone 3: Completion of Design phase 0 days 70 days
4 Implementation of system 35 days 25 days
4.1 Implement based on project objectives 1 day 0 days
4.2 Modify the implement phase 3 days 0 days
4.3 Resource and equipments requirements 4 days 0 days
4.4 Equipments store 2 days 0 days
4.5 Milestone 4: Completion of Implementation phase 0 days 70 days
5 Testing phase of the system 57 days 35 days
5.1 Start to test 9 days 0 days
5.2 Review the testing plan 5 days 0 days
5.3 Analyzing the test outcomes 6 days 0 days
5.4 Compare the outcome with project scope 2 days 0 days
5.5 Milestone 5: Completion of testing phase 0 days 70 days
6 Risk managing phase 64 days 57 days
6.1 Recognize the risks 2 days 0 days

18DEVELOPMENT OF INFORMATION SYSTEM
6.2 Address the risks 2 days 0 days
6.3 Mitigate the risks 2 days 0 days
6.4 Risk register 1 day 0 days
6.5 Milestone 6: Completion of risk management
phase 0 days 70 days
7 Final closure of the plan 70 days 64 days
7.1 Evaluation of success criteria 3 days 0 days
7.2 Delivery of final documentation 1 day 0 days
7.3 Final review 1 day 0 days
7.4 Sign off the project document 1 day 0 days
7.5 Milestone 7: Completion of Final closure phase 0 days 70 days
7.0 Initial cost estimate on development of information system
Task Name Duration Resource Names Cost
Implementation of core information
system for private tourism business 70 days $11,432.00
Initialization project phase 11 days $1,088.00
Development of business case 2 days Project Manager,
Project Sponsor $200.00
Business requirements 1 day Business Analyst,
Project Manager $192.00
Project specification based on business
case 3 days Business Analyst,
Project Manager $576.00
Meeting with management board 1 day Project Manager $120.00
Milestone 1: Completion of
initialization phase 0 days $0.00
Vendor selection for project plan 26 days $1,464.00
Vendor identification based on 6 days IT Staff, Project $576.00

19DEVELOPMENT OF INFORMATION SYSTEM
business requirements Manager
Vendor capability 2 days Functional lead, IT
Staff $128.00
Budget plan 4 days Project Manager,
Project Sponsor $400.00
Project scheduling 3 days Project Manager $360.00
Milestone 2: Completion of vendor
selection phase 0 days $0.00
Design phase of information system 61 days $2,288.00
Improving labor managing 6 days IT Staff $432.00
Installation of system process 5 days IT Staff $360.00
Hardware installation 7 days Functional lead, IT
Staff $512.00
Software installation 5 days Functional lead, IT
Staff $640.00
Designing of the system 2 days IT Staff $144.00
Building of the system 1 day IT Staff $72.00
System requirements identification 1 day Functional lead, IT
Staff $128.00
Milestone 3: Completion of Design
phase 0 days $0.00
Implementation of system 35 days $1,544.00
Implement based on project objectives 1 day Project Manager,
Project Sponsor $200.00
Modify the implement phase 3 days Functional lead, IT
Staff $384.00
Resource and equipments
requirements 4 days Functional lead,
Project Manager $704.00
Equipments store 2 days Business Analyst,
Functional lead $256.00

20DEVELOPMENT OF INFORMATION SYSTEM
Milestone 4: Completion of
Implementation phase 0 days $0.00
Testing phase of the system 57 days $2,816.00
Start to test 9 days Functional lead, IT
Staff $1,152.00
Review the testing plan 5 days Functional lead, IT
Staff $640.00
Analyzing the test outcomes 6 days Functional lead, IT
Staff $640.00
Compare the outcome with project
scope 2 days Business Analyst,
Project Manager $384.00
Milestone 5: Completion of testing
phase 0 days $0.00
Risk managing phase 64 days $1,200.00
Recognize the risks 2 days Project Manager $240.00
Address the risks 2 days Business Analyst,
Project Manager $384.00
Mitigate the risks 2 days Business Analyst,
Project Manager $384.00
Risk register 1 day Business Analyst,
Project Manager $192.00
Milestone 6: Completion of risk
management phase 0 days $0.00
Final closure of the plan 70 days $1,032.00
Evaluation of success criteria 3 days Project Manager $360.00
Delivery of final documentation 1 day
Project Manager,
Business Analyst,
Project Sponsor
$272.00
Final review 1 day Project Manager,
Project Sponsor $200.00
Sign off the project document 1 day Project Manager, $200.00

21DEVELOPMENT OF INFORMATION SYSTEM
Project Sponsor
Milestone 7: Completion of Final
closure phase 0 days $0.00
Recommendation and Conclusion
Recommendation:
Following are the suggested recommendation for the project plan:
Development of communication plan: A communication plan is required to transmit of
project related information among project manager and other project team members. The
messages should transmit as well as distribute to the intended audiences.
Risk assessment: The risks are required to identify and mitigate them before it will harm
the business operations of the tourist industry. Risk register should be used to overcome with the
identified risks.
Quality control: The quality of the hardware and software equipments used to develop
the information system should require reviewing on time. Best quality equipments should be
selected for the system.
Conclusion
It is concluded that the plan develops the system within scheduled time and budget. The
project schedule table contains all the project tasks with its respective start and finish date.
Budget will help to estimate the entire cost of the implementation of proper system. Project
outcomes will provide all possible results and benefits due to development of the system for
tourist attractions.

22DEVELOPMENT OF INFORMATION SYSTEM
Bibliography
Abiteboul, S. 2012. Web data management. New York: Cambridge University Press.
Ahsan, K. and Marufuzzaman, M. 2012. Launching an existing product to a new demographic
area: strategic plans and system reconfiguration. IJISE, 10(1), p.117.
Behman, A., Harfield, T. and Kenley, R., 2016. Construction management scheduling and
control: the familiar historical overview. EDP Sciences-Web of Conferences.
Benard, K., Oketch, O. and Matu, P. 2015. Innovation in the Language of Coca Cola Television
Advertisements. MJSS.
Braglia, M. and Frosolini, M., 2014. An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), pp.18-29.
Burmester, A., Becker, J., van Heerde, H. and Clement, M. 2015. The impact of pre- and post-
launch publicity and advertising on new product sales. International Journal of Research in
Marketing.
Burnett, R., Friedman, M. and Prince, A. 2012. Preparing IT for a new product launch. J. Corp.
Acct. Fin., 23(5), pp.27-32.
Calantone, R., Di Benedetto, C. and Rubera, G. 2012. Launch timing and launch activities
proficiency as antecedents to new product performance. Journal of Global Scholars of Marketing
Science, 22(4), pp.290-309.
Clifton, J. 2012. Discourse Perspectives on Organizational Communication. Journal of Business
Communication, 49(4), pp.377-380.
Dobocan, C. and Blebea, I. 2014. Application of the Optimal Control Problem in New Product
Launching Process. Procedia Engineering, 69, pp.347-350.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.

23DEVELOPMENT OF INFORMATION SYSTEM
Galliers, R.D. and Leidner, D.E., 2014. Strategic information management: challenges and
strategies in managing information systems. Routledge.
Gaspareniene, L. and Remeikiene, R. 2014. Economic Evaluation of New Product Creation and
Launching: The Case of Unstable Rowing Simulator. MJSS.
Gido, J. and Clements, J., 2014. Successful project management. Cengage Learning.
Heagney, J. 2012. Fundamentals of project management. New York: American Management
Association.
Highsmith, J., 2013. Adaptive software development: a collaborative approach to managing
complex systems. Addison-Wesley.
Jensen, D. 2013. Your Personal Marketing Plan. Science.
Kärnä, S., 2014. Analysing customer satisfaction and quality in construction–the case of public
and private customers. Nordic journal of surveying and real estate research, 2.
Kenyon, G.N. and Sen, K.C., 2015. Process Improvement Methods and Tools. In The Perception
of Quality (pp. 119-140). Springer London.
Kerzner, H.R., 2013. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Ladas, S., Kamberoglou, D., Karamanolis, G., Vlachogiannakos, J. and Zouboulis-Vafiadis, I.
2012. Systematic review: Coca-Cola can effectively dissolve gastric phytobezoars as a first-line
treatment. Alimentary Pharmacology & Therapeutics, 37(2), pp.169-173.
Lim, S. 2014. Impact of Information Technology Infrastructure Flexibility on the Competitive
Advantage of Small and Medium Sized-Enterprises. Journal Of Business & Management, 3(1),
1-12.
Marquardt, E. and Dunlap, N. 2012. Compensation Risk Assessments: A Process for Active Plan
Management and Continuous Improvement. Compensation & Benefits Review, 44(1), pp.6-11.

24DEVELOPMENT OF INFORMATION SYSTEM
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Taylor & Francis.
NIENABER, A. and SCHEWE, G. 2014. ENHANCING TRUST OR REDUCING PERCEIVED
RISK, WHAT MATTERS MORE WHEN LAUNCHING A NEW PRODUCT?. Int. J. Innov.
Mgt., 18(01), p.1450005.
Raymond, L. and Bergeron, F., 2015. Impact of Project Management Information Systems on
Project Performance. In Handbook on Project Management and Scheduling Vol. 2 (pp. 1339-
1354). Springer International Publishing.
Stankovic, E. 2013. Public‐private partnership: Coca‐Cola and the University of
Belgrade.International Journal of Public Sector Management, 26(2), pp.146-152.
Tsai, W.H., Lee, P.L., Shen, Y.S. and Lin, H.L., 2012. A comprehensive study of the relationship
between enterprise resource planning selection criteria and enterprise resource planning system
success. Information & Management, 49(1), pp.36-46.
Turker, D. and Altuntas, C., 2014. Sustainable supply chain management in the fast fashion
industry: An analysis of corporate reports. European Management Journal, 32(5), pp.837-849.
Turner, R., 2016. Gower handbook of project management. Routledge.
Tworek, P. 2012. Plan Risk Response as a Stage of Risk Management in Investment Projects in
Polish and U.S. Construction - Methods, Research. Annals of the Alexandru Ioan Cuza
University - Economics, 59(1).
Viio, P. and Nordin, F. 2015. When does implementation of relationship orientation in new
product launch matter?. Industrial Marketing Management, 45, pp.47-48.