Essay: Report On Information System Design For Crown's Hotel.

Using the same chosen organisation in Assignment 1 and building upon the work you have already completed you need to undertake the following tasks:

TASK 1: Time Management Plan

Students are required to provide an effective time management plan that will lead to successful submission of your assignment 2 (Report), and the completion of the required activities that included in this assignment.

Develop a work breakdown structure (WBS) for your project with date, and summary of project activities. Use a table with columns for activity number, start date, finish date, activity name, activity description, plann edaction, status, and any other notes. The purpose of WBS is to identify each task in your project and include an estimated duration.

TASK 2: “TO BE” Process

Develop a “TO BE” process diagram by using Business Process Modelling Notation (BPMN) or Unified Modelling Language (UML). The “TO BE” diagram should show the improvement of the process flow of your chosen organisation.

TASK 3: Comparing “AS IS” and “TO BE” Process

Compare the “AS IS” process diagram that you provided in the assignment 1, and “TO BE” process diagram to assess the impact of change and prepare a briefing note for the organisational change management team regarding the anticipated impact of the system. You should make recommendations to the team on how these impacts can be managed.

TASK 4: Physical and Logical Network

Based on “TO BE” process diagram from Task 2, what physical and logical network topology would you recommend for your chosen organisation to execute the entire process?

TASK 5: Testing

What types of testing should be performed? What types of test data should be used? The testing in relation to the new Information Systems developed to automate the organisation process? Please clarify this.

TASK 6: Training

Identify the specific groups of people who need training on the new system. For each group, describe the type of training you would recommend and list the topics you would cover.

TASK 7: System Changeover

Develop a plan for system changeover for your chosen organisation. Discuss the method that should be used for systems changeover to enable “TO BE” process in the organisation.

TASK 8: Report to Top Management

Assume you have completed the design and implementation phases of your project for your chosen organisation. Write a report to the top management (CEO). This report at a minimum should include the objectives, background, processes undertaken, scope, and recommendations to the top management (CEO).

In this report the attention is on actualizing information system in Crown's Hotel which gives lodging administration in Australia and has a scope of hotels all through the nation. The review is being directed to determine the issues inside the association and suggest another information system plan with the assistance of "TO BE" business prepare show. The time administration plan is likewise being set up to complete this review and improvement of this paper. The "AS May be" and "TO BE" Process is additionally looked at in area 3 of the paper to separate the proposed changes that could be made in the Crown's Hotel by actualizing a information system. The physical and coherent system topology has likewise been set up for the association with the goal that they can execute the whole procedure. In segment 5 of this paper the talks are done on the particular gathering of individuals who will oblige preparing to work the new framework. The later segment is taken after to exhibit an arrangement for framework changeover with the goal that it empowers the joining of the "TO BE" process in the association. A report has been set up in area 8 for writing about the proposed information system and how it can be utilized to inspire the business forms inside the association.

In this area, an arrangement for conduction of the review to propose the outline of a information system to support the business forms inside the association have been readied. A Work Breakdown Structure (WBS) is intended to give an arrangement to oversee time adequately and guarantee fruitful culmination of this review. The WBS gives an abnormal state itemized portrayal of the exercises with legitimate dates and courses of events that must be taken after to guarantee effective finish of any project. In setting to the instance of Crown's Hotel for recommending another information system plan, the WBS has been set up as underneath:

WBS	Task Name	Duration	Start	Finish	Predecessors	Resource Names
0	Information system design for Crown's Hotel	37 days	Mon 4/10/17	Tue 5/30/17
1	Initiation phase	8 days	Mon 4/10/17	Wed 4/19/17
1.1	Choose organization	1 day	Mon 4/10/17	Mon 4/10/17		Researcher
1.2	Identifying the existing issues in the organization	2 days	Tue 4/11/17	Wed 4/12/17	2	Researcher
1.3	Identifying the stakeholders associated with the organization	1 day	Thu 4/13/17	Thu 4/13/17	3	Researcher
1.4	Feasibility study of the project	2 days	Fri 4/14/17	Mon 4/17/17	4	Researcher
1.5	Analyzing risks associated with the project	2 days	Tue 4/18/17	Wed 4/19/17	5	Researcher
2	Second phase	10 days	Thu 4/20/17	Wed 5/3/17
2.1	Developing the plan for time management	2 days	Thu 4/20/17	Fri 4/21/17	6	Researcher
2.2	Designing of diagram for "TO BE" process	2 days	Mon 4/24/17	Tue 4/25/17	8	Researcher
2.3	Comparing the "AS IS" process with designed "TO BE" process diagram	1 day	Wed 4/26/17	Wed 4/26/17	9	Researcher
2.4	Selecting the physical as well as logical network topology for the organization	2 days	Thu 4/27/17	Fri 4/28/17	10	Researcher
2.5	Third phase	3 days	Mon 5/1/17	Wed 5/3/17
2.5.1	Identifying the types of testing to be implemented	2 days	Mon 5/1/17	Tue 5/2/17	11	Researcher
2.5.2	Identifying the types of data to be used for testing	1 day	Wed 5/3/17	Wed 5/3/17	13	Researcher
3	Fourth phase	16 days	Thu 5/4/17	Thu 5/25/17
3.1	Determination of the people to be trained for the new system	3 days	Thu 5/4/17	Mon 5/8/17	14	Researcher
3.2	Determining the type of training to be provided	4 days	Tue 5/9/17	Fri 5/12/17	16	Researcher
3.3	Recommendations on the topics to be covered during training	4 days	Mon 5/15/17	Thu 5/18/17	17	Researcher
3.4	Development of plan for management of system changeover	5 days	Fri 5/19/17	Thu 5/25/17	18	Researcher
4	Closeout phase	3 days	Fri 5/26/17	Tue 5/30/17
4.1	Developing report for top management level	2 days	Fri 5/26/17	Mon 5/29/17	19	Researcher
4.2	Concluding the study	1 day	Tue 5/30/17	Tue 5/30/17	21	Researcher

From the developed plan for management of time it has been found that this review required 37 days for fruitful consummation beginning from 10 April 2017 to finish on 30 May 2017.

Figure 1: “TO BE” process diagram designed for Crown’s Hotel

(Source: Created by Author)

From the "AS IS" process being outlined in setting to the current data arrangement of Crown's Hotel, it has been distinguished that there is no procedure of discovering accessibility of rooms and correspondence with the clients. Consequently in the "TO BE" process being produced in this review, a call centre have been included to speak with the clients so they can undoubtedly discover rooms and book in a specific lodging. The "AS IS" process additionally does not gives affirmation to the clients about their booking status and when room will be accessible in a specific hotel. The "TO BE" process includes the prerequisite of recognizing each progression by the clients preceding booking of rooms in a hotel.

Figure 2: Entity Relationship diagram for the Crown’s Hotel information system

(Source: Created by Author)

TO BE Process

Customer

Attribute	Data Type
Cust ID (PK)	int (20)
Cust Name	Varchar (20)
Cust Address	Varchar (20)
Cust Contact	int (20)

Call Center

Attribute	Data Type
RC ID (PK)	int (20)
CC Contact	int (20)
CC staff	Varchar (20)

Reception staff

Attribute	Data Type
CC ID (PK)	int (20)
RC Name	int (20)
RC Address	Varchar (20)
RC Contact	Varchar (20)

Hotel system

Attribute	Data Type
Module ID (PK)	int (20)
Module Name	Varchar (20)
Description	Varchar (20)

The testing that have to be performed on the Crown’s Hotel information system are listed as below:

Usability Testing - This testing predominantly focuses on the customer's straightforwardness to use the application, flexibility in managing controls and limit of the system to meet its objectives.

Regression Testing - This testing incorporates testing done to guarantee none of the movements made through the traverse of the headway system have brought on new bugs (Tsui, Karam and Bernal 2016). It in the same manner guarantees no old bugs appear from the extension of new programming modules after some time.

Recovery Testing - This testing is done to demonstrate an item course of action is strong, solid and can successfully recoup from possible mischances (Mall 2014).

Migration Testing - This testing is done to ensure that the item can be moved from more settled structure establishments to current system establishments without any issues.

Functional Testing - Otherwise called helpful zenith testing, utilitarian testing incorporates endeavoring to consider any possible missing limits (Jorgensen 2016). Analyzers may make a summary of additional functionalities that a thing could need to improve it in the midst of utilitarian testing.

The people that will require training on the new information system have been identified as underneath:

• System Administrators: The system administrator is responsible to ensure the system is working properly according to the requirements and maintenance. Further, this person must be aware of the procedure for backup of data on a regular basis as well as recovery in case of any fault or error within the system.
• Call center: This entity involved in the system will be responsible to conduct communications with the customers for facilitating the entire hotel booking procedure. Hence, this person must be aware of the message flow within the system.
• Reception staff: The reception staff will be notified whenever there is a request from customers to book a room in the hotel. This person has to carry out the entire process of room booking with the help of the system. Hence, this person have to be made aware on the various modules being existing in the system.

As the name recommends it is the way toward changing the old information system. Framework changeover is the way toward putting the new information system on the web and resigning the old framework (De Lemos et al. 2013). The pilot operation changeover strategy incorporates executing the aggregate new system at a picked region of the association. The get-together that uses the new system at first is known as the pilot site. The old system continues working for the entire affiliation including the pilot site. After the system shows compelling at the pilot site, it is completed in the straggling leftovers of the affiliation, as a rule using direct cutover technique (Kumar and Alencar 2016). Pilot operation is mix of parallel operation and direct cutover systems.

Pilot site ensure the working of new structure and reduces the peril of system disillusionment. This is moreover more reasonable than the parallel operation as exactly at one fragment both structure works for obliged period (Fenton and Bieman 2014). This is more moderate and more secure approach as its mix of both direct cutover and parallel operation. It will save money of prosperity center and moreover protect their data with smooth working.

In the wake of examining the business necessity of the project it has been found that Crown Hotels have circulated their business all through Australia and it incorporates hotel rooms, eatery, upmarket bars, and so on. As of now, if any client needs to book the lodging they can contact utilizing the telephone utility or come physically to book room in the hotel. This abatements the effectiveness of the association and along these lines it has a necessity to execute the online information system utilizing which the client can see the rooms and book the administration they lean toward.

Comparing AS IS and TO BE Process

Background

Crown Melbourne has concentrated on building lodgings and grows their business yet with the expansion in the opposition the organization is confronting issue in regards to the administration of the framework. Right now the gathering staff confront issue with respect to the administration of the records of the pre-booked rooms and administration and therefore the information system is required to be produced to determine the issues confronted in the administration procedure.

Process Undertaken:

• A web interface is made for making a connection between the client and the lodging
• All the records of the lodgings, for example, the taxes, accessibility of the room, benefit gave, and so forth is required to be put away in the database
• The created information system ought to be adaptable as per the requirements of the business.

Scope

The principle objectives and targets of the association are incorporated for the improvement of the extent of the project. The project timetable is set up in the wake of examining the extent of the project. The risk related with the advancement of the project is likewise required to be broke down for building up the project productively.

Recommendations

• A study on feasibility is required to be accomplished for breaking down the necessity and build up the project
• The database of the information system must be secured from any outer get to and ought to be encoded
• The web interface planned must be appealing and simple to use for expanding the client relationship.

Conclusion

From the development of plan to manage time to finish the review it has been recognized that it required 37 days to fulfill this project. The examination between "AS IS" and "TO BE" process it has been distinguished that in the "AS IS" process there was no association of the call centre while booking of rooms in hotel by clients. In any case, the alterations being reflected in the "TO BE' process demonstrates that there is inclusion of call centre at each progression of the lodging booking process. The testing that must be performed alongside the sorts of test information that must be dissected guarantees the fruitful development of the information system.

References

Aurum, A., Jeffery, R., Wohlin, C. and Handzic, M. eds., 2013. Managing software engineering knowledge. Springer Science & Business Media.

Bhatia, M.P.S., Kumar, A. and Beniwal, R., 2016. Ontologies for software engineering: Past, present and future. Indian Journal of Science and Technology, 9(9).

David, O., Ascough, J.C., Lloyd, W., Green, T.R., Rojas, K.W., Leavesley, G.H. and Ahuja, L.R., 2013. A software engineering perspective on environmental modeling framework design: The Object Modeling System. Environmental Modelling & Software, 39, pp.201-213.

De Lemos, R., Giese, H., Müller, H.A., Shaw, M., Andersson, J., Litoiu, M., Schmerl, B., Tamura, G., Villegas, N.M., Vogel, T. and Weyns, D., 2013. Software engineering for self-adaptive systems: A second research roadmap. In Software Engineering for Self-Adaptive Systems II (pp. 1-32). Springer Berlin Heidelberg.

Fenton, N. and Bieman, J., 2014. Software metrics: a rigorous and practical approach. CRC Press.

Fuggetta, A. and Di Nitto, E., 2014, May. Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.

Glinz, M. and Fricker, S.A., 2015. On shared understanding in software engineering: an essay. Computer Science-Research and Development, 30(3-4), pp.363-376.

Hassan, M.M., Afzal, W., Lindström, B., Shah, S.M.A., Andler, S.F. and Blom, M., 2016, April. Testability and software performance: a systematic mapping study. In Proceedings of the 31st Annual ACM Symposium on Applied Computing (pp. 1566-1569). ACM.

Jorgensen, P.C., 2016. Software testing: a craftsman’s approach. CRC press.

Kumar, V.D. and Alencar, P., 2016, December. Software engineering for big data projects: Domains, methodologies and gaps. In Big Data (Big Data), 2016 IEEE International Conference on (pp. 2886-2895). IEEE.

Maher, M.L. and Pu, P., 2014. Issues and applications of case-based reasoning to design. Psychology Press.

Mall, R., 2014. Fundamentals of software engineering. PHI Learning Pvt. Ltd..

Pahl, G. and Beitz, W., 2013. Engineering design: a systematic approach. Springer Science & Business Media.

Spichkova, M., Liu, H., Laali, M. and Schmidt, H.W., 2015. Human factors in software reliability engineering. arXiv preprint arXiv:1503.03584.

Tsui, F., Karam, O. and Bernal, B., 2016. Essentials of software engineering. Jones & Bartlett Learning.

Wasson, C.S., 2015. System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices. John Wiley & Sons.