Fill This Form To Receive Instant Help
Homework answers / question archive / This week, you will continue with your application from your W1 Project and complete the following tasks: Describe the mechanisms that you used to solicit input from stakeholders to produce your requirements for your use-case specifications and your declarative requirements
Hotel Management Reservation System Jeshion Johnson Principles of System Development 05/03/2021 1 Table of Contents 1.0 Project Scope ................................................................................................................................... 3 1.1 General Project Information...................................................................................................... 3 1.2 Opportunity statement ............................................................................................................... 3 1.3 Project objective .......................................................................................................................... 3 1.4 Project description ...................................................................................................................... 3 1.5 Business benefits.......................................................................................................................... 4 1.6 Estimated Duration ..................................................................................................................... 4 2.0 Project Stakeholders ....................................................................................................................... 4 2.1 List of Project Stakeholders ....................................................................................................... 4 2.2 Project Stakeholder Needs ......................................................................................................... 5 3.0 Targeted System Features .............................................................................................................. 6 4.0 Requirements management plan ................................................................................................... 7 4.1 Purpose......................................................................................................................................... 7 4.2 Requirement Categories ............................................................................................................. 7 4.3 Feature Request Processes ......................................................................................................... 7 4.4 Methodology for collecting input into the requirements process ........................................... 8 4.5 Traceability.................................................................................................................................. 8 4.6 Meta-data to track ...................................................................................................................... 9 4.7 Deliverables to produce .............................................................................................................. 9 4.8 Processes, policies, and procedures ........................................................................................... 9 2 1.0 Project Scope 1.1 General Project Information Name: Hotel Management Reservation System Sponsor: John Doe Project Manager: Jane Doe 1.2 Opportunity statement The growing development and advancement of technology is enabling flexibility in modern business operations. Besides, online management systems are aiding businesses in the hospitality industry in adhering to COVI9-19 rules by ensuring that it prevents any form of overcrowding in hotels and restaurants. As such, the Hotel Management Reservation System would provide an opportunity for the hotels in the Malibu area in keeping up with the evolving technology, tracking and managing reservations, and developing measures to ensure the safety of guests. 1.3 Project objective The main objective of this project is to develop an application that would enable guests to make reservations in hotels. Besides, this application would also help hotels in the management of reservations to ensure the fulfillment of guests. 1.4 Project description The hotel reservation system is set to enable guests to book the hotel's rooms, schedule length of stay in the hotels, indicate any extras or preferred customized services, and make payment. Besides, the system would also be designed to enable hotels in managing the reservations, tracking the number of reservations, and making any 3 necessary cancellations. The system should allow the guests to make payments for their reservations. 1.5 Business benefits The online reservation system is a great sales and marketing synergy for the hotels. Ideally, the system would allow the hotels to track the various attributes involved in the booking such as names, locations, and age of the guests. As such, the hotels can use this information to develop proper sales and marketing strategies. Besides, the reservation system would help the hotels in boosting their revenue through proper upselling. By enabling fast and effective reservations, the hotels can gain a larger consumer-based hence boosting its revenue. Besides, the system would enable efficient operations, which would mean easier tasks for the hotel employees, hence increasing productivity from employees and enabling reduced turnover. 1.6 Estimated Duration The estimated duration of this project is four (4) months. 2.0 Project Stakeholders 2.1 List of Project Stakeholders i. Project Sponsor ii. Project Manager iii. Team members iv. Owner v. Customer 4 2.2 Project Stakeholder Needs i. Project Sponsor A project sponsor is a group or individual involved in providing resources for the project and supporting the project to ensure that it achieves its full success. Project sponsors need regular updates on the project's progress. The key issue that can be solved by the provision of progress updates is the problem of information withholding. ii. Project Manager The project manager plays a lead role in the planning, executing, controlling, monitoring, and closing of projects. As they are accountable to the entire project scope, the project manager needs proper communication and interpersonal skills, conflict resolution and negation skills, commitment, and team leadership skills. The business problems that can be solved by these needs include; poor communication and collaboration among team members. Besides, the needs can solve any existing conflicts among team members hence ensuring effective project flow. iii. Project Team members The project team members include; designers, developers, testers, analysts, and quality assurance personnel. Essentially, the team needs proper collaboration, communication, and communication skills in the project development. Besides, the team needs support from the management level to complete their assigned tasks. These needs can solve the issues of slow productivity and even prevent the risk of missing deadlines and the development of poor quality products. 5 iv. Project Owner The project owner is the business unit or individual involved in receiving the product. Besides, the project owner is responsible for the successful implementation of the project. The project owner requires a proper understanding of the projects, including their requirements, scope, and stakeholders. A proper understanding of the project owner would prevent cases of scope creeps that can prompt potential delays in the project launch. v. Customers The customers, also identified as the project users, are the beneficiaries of the project results. In this case, the project customers are the hotels. As such, the customers have a responsibility of informing of their demands and requests to ensure effective and efficient functioning of the system. Ideally, this communication would help in the prevention of consumer dissatisfaction, which can eventually lead to system failure. 3.0 Targeted System Features i. The system should have a high rate of availability ii. The system should accommodate scalability iii. The system should ensure maximum security of the users' information iv. The system should be designed with ease of usability v. The system should allow the guests to make reservations vi. The system should allow guests to cancel reservations. vii. The system should allow the hotels to track the number of reservations made and ensure that bookings are approved automatically based on a first-come-firstserved basis. 6 4.0 Requirements management plan 4.1 Purpose The purpose of the requirement management plan is to identify and describe various requirements and activities for the development of the hotel reservation system. This plan focuses on the requirement categories, feature request processes, Methodology for collecting input into the requirements process, traceability, meta-data to track, deliverables, and the processes, policies, and procedures. 4.2 Requirement Categories The development of the requirements framework of the hotel reservation system will involve two categories which include; i. Functional Requirements ii. Non-functional requirements 4.3 Feature Request Processes The feature request process will involve a number of steps. These steps include; a. Submission of the feature idea In this step, the desired or proposed feature is submitted to the team for assessment. During the submission, a proper communication framework will be selected to ensure that the submission reaches the intended recipients. b. Vetting or evaluation The second step entails the evaluation of the proposed feature. Ideally, the submitted idea is assessed to determine whether it can fit and solve various problems in the systems. 7 c. Approval or rejection Upon completion of the vetting process, the next will involve deciding whether to approve or reject the proposed feature. With sufficient research and information from experts, the proposed idea will be accepted or rejected. d. Implementation The final step of the feature request process will involve the implementation of the proposed feature based on the decision made in step three. 4.4 Methodology for collecting input into the requirements process The key methods that will be used in collecting information for the requirements process are brainstorming online research and virtual interview. Ideally, brainstorming will involve engaging in group thinking to identify the various requirements that should be involved in the development of the system. Besides, online research will entail identifying past online case studies that can help in the development of the process. Interviewing requirements specification experts, through virtual applications, is another methodology that will help in the collection of data. 4.5 Traceability The project will employ the Requirement Traceability Matrix (RTM) in tracking and linking each individual project requirement with its origin, throughout the software development process. Essentially, the main chain of the RTM is to ensure that all the proposed system requirements are tested in the test protocols. 8 4.6 Meta-data to track The meta-data that will be tracked will focus on the components of reservations that can help in building a strong requirements speciation document. 4.7 Deliverables to produce The deliverables that will be produced include; i. Project scope statement ii. Project charter iii. Requirement specification document iv. Design documentation 4.8 Processes, policies, and procedures Processes are identified as maps that provide guidance for actions. Essentially, the processes will be used to define patterns of work that will be completed to ensure the fulfillment of the proposed requirements in the system development process. Essentially, the processes are often accompanied by policies and procedures to ensure the success of the development process. The following are the processes, policies, and procedures for the requirements framework. I. Stakeholders with ideas on the systems will be required to submit their requests using the feature request processes II. The requirements analysis team will ensure that all the proposed ideas are analyzed and a fair decision on approval or rejection is provided. III. The project manager should ensure that all the shareholders have information on all the proposed and approved system requirements. 9 IV. All the project stakeholders should study the requirements and in any case make requests or propositions to change particular features. V. All the informed stakeholders must ensure the safety of the requirements from access by unauthorized persons. VI. All the proposed and approved requirements must be documented and well stored ready for submission to the design and the development team of the project. 10