SPM Hotel Managemenet System Updated

ADDIS ABABA SCIENCE AND TECHNOLOGY UNIVERSITY
College of Electrical & Mechanical Engineering

Department of Software Engineering
Undergraduate Program
Software Project Management
Hotel Management System planning Document
Submitted By:
Name ID
1. Adisu Negash ETS 0078/09
2. Denber Esubalew ETS 0322/09
3. Garoma Aga ETS 0444/09
4. Natnael Temesgen ETS 0784/09
5. Zelalem Shiferaw ETS 1075/09
6. Tesema Kenow ETS 1077/08
Submitted To: Instructor Amsalu T. May 17, 2019 G.C

Project Plan Paper
Client: Minilik Hotel.
Project Name : Hotel Management System.
Project Manager : Zelalem Shiferaw .
Version: Final V1.0.
Issue Date: 5/17/2019
Prepared by: Group Members.
Authorized by: Zelalem Shiferaw.

Table of Contents
1.
Introduction.......................................................................
........................................................1
1.1. Document
Purpose............................................................................
...................................1
1.2. Background information/Available Alternatives/Associated

Documents...........................1
1.3. Project
PlanMaintenance....................................................................
..................................1
2. Project
Scope….............................................................................
.............................................2
2.1. Outline of Client’s Objectives/ Business Goals and

Objectives..........................................2
2.1.1.
Objectives.........................................................................
..........................................2
2.1.2. Success
Criteria...........................................................................
.............................. 3
2.1.3.
Risks..............................................................................
.............................................3
2.2. Outline of Organization Objectives / Project Goals and

Objectives...................................3
2.2.1.
Objectives.........................................................................
...........................................4
2.2.2. Success
Criteria...........................................................................
................................4
2.2.3.
Risks..............................................................................
..............................................5
2.3. Definitive Scope

Statement..........................................................................
..............…….5
3. Project Infrastructure, Standard and

Procedures……………………....................................….6
3.1. Installation Standard and

Procedures…….......................................................................
.. 6
3.2. Infrastructures Governance

Strategy………...................................................................…6
4. Project
Approach...........................................................................
................................………..6
4.1. Project lifecycle

processes..........................................................................
.........………....6
4.2. Project Management

Processes..........................................................................
.....……….7
4.3. Project Support

Processes….........................................................................
.............……11
4.4.
Organization.......................................................................
.........................................…..11
4.4.1. Project
Team...............................................................................
................................11
4.4.2. Mapping between Organization and

Client................................................................12
5. Communications
Plan…..............................................................................
.....................……14
6.
Deliverables.......................................................................
................................................……15
6.1. To
Client.............................................................................
...........................................….15
6.2. From
Client.............................................................................
......................................…..16
7. Work
Plan...............................................................................
..........................................……16
7.1. Work Breakdown

Structure….........................................................................
...........…….16
7.2.
Resources..........................................................................
........................................……...19
8.
Milestones.........................................................................
..............................................……..19
9. Performance and
Metrics/Efforts ...................................................................
………………..20
10. Risk
Assessment.........................................................................
..............................………...22
11. Allocate
Resources..........................................................................
...................…………….24
12.
Appendix ..........................................................................
...........................................……...24
Document title: Project Plan Project name: Hotel Management System
Version: Final Version V1.0 Project number: 01
Issue date: 5/16/2019
1. Introduction
This Hotel management planning document consists of project purpose, scope, project
infrastructure, project approach, communication plan, deliverables, work plan,
milestones
performance and metrics, risk assessment, and allocating resources of the system.
1.1 Document Purpose

The Hotel Management System Project Plan will provide a definition of the project,
including
the project’s goals and objectives. Additionally, the Plan will serve as an
agreement between the
following parties: Project Sponsor, Steering Committee, Project Manager, Project
Team, and
other personnel associated with and/or affected by the project. It prevents
obstacles that arises in the
project such as : changes in projects or organization’s objectives , no
availability of resources and so on.
It also helps in better utilization of resources and optimal usages of the allotted
time for the project. This
plan also helps a project manager to understand, monitor, and control the
development of software
project.
1.2 Background Information/Available Alternatives
MINILIK remains one of the most preferable Hotels in Central parts of Ethiopia,
meaning more
customers flow in everyday and the numbers keep increasing day by day. Work load
has also
increased and expectations of customers flowing in the hotel are so high. They
expect super
quality service from the Hotel. Due to this it has come to the realization that in
order to maintain
the high standards of the hotel and its reputation, there must be adoptions of a
system that will
help the hotel maintain a healthy competition in the market. A hotel management
system in place
would ensure that the hotel survives in the market very comfortably. The existing
system uses
manual method for Customer registration and allocation and record keeping by
filling up the forms
provided by the Hotel Staff and then the filled forms are kept in file-folders. For
the hotel staff to know
which rooms are free and available they would have to check through their various
files or keys and this
system is a bit cumbersome and even more so for a business that is trying to
expand.
1.3 Project Plan Maintenance
The following is an explanation of how the participating stakeholders will

implement the
updated plan, and continue to evaluate and enhance it over time. In order to ensure
that the Plan
remains current and relevant the following plan maintenance procedures will be
addressed:
 Monitoring and Evaluating the Plan
 Updating the Plan
Page | 1
 Incorporating the Plan into other Planning Mechanisms

At any time, minor technical changes may be made to the Plan to keep it current.
However, any
Changes by participating stakeholders to modifications in the overall direction of
the Plan will be
subject to clients’ requirements. Once the amendment is approved it will be
transmitted to the
MINILIK hotel managers.
In determining whether to recommend approval or denial of a plan amendment request,

the
following factors will be considered:
 Errors or omissions made in the identification of issues or needs during the
preparation of the
Plan;
 New issues or needs that were not adequately addressed in the Plan; and
 Changes in information, data or assumptions from those on which the Plan was
based.
The Plan will be thoroughly reviewed by each planning team member at the end of
three years
from the date of adoption. Following the review, any revisions deemed necessary
will be
summarized and utilized according to the reporting procedures and plan amendment
process
outlined herein. Upon completion of the review and update/amendment process and
after being
approved by the project board, the revised plan will be submitted to the project
steering
committees for final review and approval in coordination with clients.
2. Project Scope
2.1 Outline of Client’s Objectives/ Business Goals and Objectives
2.1.1 Objectives
 Reduce overall budget costs by 10% by 20xx

 Increase market share by 5% by 20xx
 Increase revenues by 20% by 20xx.
 Increase customer satisfaction by 5 pts. by 20xx
The client objectives from the major subsystems are:

1. From the Room reservation
The Reservation System is to keep track in room and hall reservation and
check availability.
The Room Management System is for manage all room types room services.
The system must able to record detail information about the customer.
Page | 2
The System allows the customers to reserve the rooms online, SMS and face to
face.
2. From the Human resource / Employee information

The system must have attendance forms.
The system must have a platform for controlling the salary.
The system must able to handle the statistics of the human resource.
3. From the Inventory management
The Inventory Control System will keep track in all inventories of the
hotel.
Control the status of materials in the stock.
4. From the Restaurant management
Catering.
Liquor.
The system must provide a way to control the expenditure and income from
the restaurant.
2.1.2 Success Criteria
 Quality of the System

 Time used
 Cost consumed
 Profitability of the new system
 Sustainability
 Reliability of the System
 Whether or not best utilization of resource is occurred.
2.1.3 Risks
In the previous years there have been cases of malpractice in the hotel. Accounting
Files are
easily accessible to anyone which is very sensitive since if in the wrong hands one
can commit
fraud. This affects the management directly, in that avoidable losses do occur.
Security will be a
priority while coming up with the system. If the problem is not solved, it would
lead to severe
losses. The current manual system in place gives room for such undesirable outcomes
and should
be updated.
The Hotel management system is a system that aids the management of the Customers’
data, Hotel staff
data, customers’ registration, Customer accommodation or allocation into specific
rooms, room
reservation and Personnel staff management.
2.2 Outline of MINILIK Hotel management System Objectives / Project Goals and
Objectives
Page | 3
2.2.1 Objectives
The system should have interactive user interface , it must be easily

maintainable , reliable and
secure.
1. Create food menu items.
2. Create a desktop application that will generate orders.
3. To generate bill slips.
4. Create receipts and store them in a database.
5. Generate routine statement reports.
2.2.2 Success Criteria
The success of the project is measured through:
 The quality of the system.

 The time spent.
 The amount budget the system used .
The Investment Portfolio
Are we analyzing all the projects across the investment portfolio regularly?
Success criterion Check/Uncheck

Planned investment are on target
Capital costs are on target
Expense costs are on target
Table 2.2.2.1 analyzing table across investment portfolio
Financial Planning and Management
Do we have access to financial information related to those investments and are we

reconciling,
reallocating, and justifying overages regularly?

Compare real time actual forecast
Compare operational and finical planning
Identify high performing and low performing
Table 2.2.2.2. Financial planning criteria table
Page | 4
Resource Capacity and Demand
Do we know what our resources are working on and where they are spending their
time? Can we
visualize that information in real time?

Resources are working on a right projects
Priority projects staffed effectively
Shift as things change and anticipate needs for
future planning
Table 2.2.2.3 resource capacity success criteria table
Measuring Planned vs. Actuals
Are we taking the time to understand and share the difference between what was
planned versus what
happened related to the portfolio of projects?

Visualize planned vs. actual ongoing
Share reports with stakeholders
Table 2.2.2.4 measuring planned vs. Actuals
2.2.3 Risks
Among the many reasons that will hinder this research one of them would include
users of the newly
proposed system not being conversant with computers. This means for the system to
be in place and
work effectively and efficiently, the end users must be compacted with basic
knowledge on
Computers and how the system works.
 If any accident happens on team members.

 If there is a shortage of cost before completing the project.
 The time required to develop the software is under estimated.
 The rapid change of technology.
 Security hole.
2.3 Definitive scope statement
Hotel management system is performs the following tasks:-
 Food serving and food preparation, both of which are handled by the MINILIK
hotel
employees
 By keeping track of which quality and quantities of different food items for
customers
 Placements of employees
 Scheduling system
Page | 5
 There will be harmonious of work.

 Keep track in room and hall reservation and check availability.
3. Project infrastructure, standard and procedures

Project Infrastructure refers to the organizational structure, processes, tools,
techniques and
training an organization puts in place to make projects more successful.
3.1 Installation standard and procedures
The installation standards and procedures that we follow with the concerned
government rules and
regulations of software deployment.
 First we have to get recognition from the government.

 Fulfill the copy right standards or intents.
 Check the project that we want to deploy is completely functional.
 Install the software for the specified client.
3.2 Infrastructures governance strategy
 Server is needed to hold or save the whole data that the hotel needs to
store.
 All networking tools including router, modem and internet cables.
 The whole computer system including PC, Barcode scanner, POS machine and
the
like.
 And finally we must gave training for the assigned person to run the
system about
how to run the system and how to configure it properly
4. Project Approach
4.1 Project Lifecycle Processes
The project management life cycle describes high-level processes for delivering a
successful
project. For every $1 million invested in projects by hotel, $1000 was wasted due
to lacking
project performance, according to project manager research. Wasted money and
resources can be
prevented with effective project management. In the phases of the project
management life cycle,
Page | 6
you come up with the idea for a project, define its goals, plan for its execution,
and guide it to
completion.
The process model to be used in the project is the Iterative process model. This
model allows the
system to be developed in a number of iterations making change on the various
development
ages very easy. Furthermore, it ensures the delivery of the product in a short
period of time. This
model is suitable for this project since new requirements can be incorporated in
the successive
iterations and the delivery of the system on schedule can be made more possible.
Figure 4.1.1 Iterative model
4.2 Project Management Processes
The 4 Phases of the Project Management process used to manage a project.
1. Initiation
Accounting Files are easily accessible to anyone which is very sensitive.
The current
manual system in place gives room for such undesirable outcomes and should
be updated.
Our specific goal is to provide automated, quality management with time
saving manner
management system. We have already enough resource to develop the project.
2. Planning Phase
The purpose of our project to prevent system from security matter and to
automate the
system. We can adequately schedule and budget high level milestones.
3. Execution phase
Page | 7
Are all resources being tracked? yes
Is the project on budget and on time? yes
Can resource planning be optimized? yes
Are there major roadblocks that require yes

change management?
4. Closure
In the project termination phase we will ask question in a table below.
Are the project’s completion criteria met?
Is there a project closure report in progress?
Have all project artifacts been collected and

archived?
Has a project postmortem been planned?
We will use Questionnaire & Meeting to collect requirements of various stakeholders

because it
provides flexibility to stakeholders to take part as per their ease.
To expose faults in the interaction between integrated units we will use

integration and
testing where individual units are combined and tested as a group.
Acceptance testing
System testing Integration testing

Unit testing
Meetings
Different meetings will be held, with timely for effective communication,
between the project
manager, team leaders and team members to discuss the status of project, to
ensure a stable strategy
and secure commitment from all parties and to review, report what has been
performed and for
making decisions. Including:
- Management Meeting
- Team Members meeting
Monitoring and Controlling
Page | 8
The project is managed by means of an established Work Breakdown Structure

(WBS) and
different reports. This WBS shall be the basis for establishing project
schedule and for
definition of project tasks and deliverables. The project manager collects
actual completion
and resource utilization data from the team members in order to calculate
actual performance
against predicted cost and schedule.
Monitoring and controlling of the project is done by the Project manager using
the following
means:
•By making sure that team meetings are being held on schedule.
• The team leader of a team may not be able to hold meetings between his/her
staffs due to
different reasons.
• As it is the teams who are actually working the project, team meetings are
very essential.
• Weekly report, the work done by the members’ needs to be administrated and a
couple of
Items have to be reported to Project Manager.
• Progress reports, at any time the progress of the project is reported to team
leader and
Project Manager
Change control
The change control process helps avoid unnecessary changes that might disrupt
our project
and also ensures the efficient use of resources. We will use the following five
Change
control stages:
1. Proposing a Change
This process gives the ability for anyone in the project team (managers,
waiter, waitress,
accountant, customers, and assistants) to suggest a change to the project.
The proposal
must include a description of the change and expected benefits or other
reason for the
change. The change is presented using the Change Request Form and added to
the
Change Log for the project.
2. Summary of Impact
This process is carried out by the project manager, who will consider the
overall effect on
the project, covering the following items:
 Quantifiable cost savings and benefits
 Legal, regulatory or other unquantifiable reason for change
 Estimated cost of the change
After this assessment, the project manager recommends whether to carry out the
change.
3. Decision
This process involves a review of the change request by an approved authority
who will
consider all the information provided by the project manager and person making
the request.
The decision will usually be:
 Accept
Page | 9
 Accept with comments and special conditions

 Reject
 Defer (change is not approved, but is left for consideration later)
4. Implementing a Change
If the change is approved it is planned, scheduled and executed at a time
agreed with the
stakeholders. As part of the planning, a regression test plan is needed in case
the change
needs to be backed out. After implementation, it is usual to carry out a post-
implementation
review.
5. Closing a Change
Once implemented, the requester checks and agrees on the change, and it is
closed in the
Change Log by the project manager.
Risk management process
The will use effective steps in a risk management plan are outlined here:
1. Risk Identification
Risk management ideally begins with risk identification. We will identify risks
through
techniques such as, brainstorming, document reviews, and interviews.
2. Risk Assessment
Risk assessment follows risk identification in the risk management plan. Categorize
the risks as
internal or external risks. Internal risks are those that can be controlled
including project
assumptions that may be invalid and organizational risks. External risks are events
over which
we have no direct control. It may also be dependent on natural conditions such as
death of
stakeholders.
3. Risk Action Plan or Risk Resolution
In this process, we will take details of action when a risk is identified. For this
section review
the risk items with high rankings from Section 3 and determine if the significant
risks will be
accepted, transferred, or mitigated.
The following components should be included in the final performance report.
 Current deliverables status with reference to the schedule progress and

costs incurred.
Page | 10
 Comparisons between actual and planned values related to technical

performance, cost
performance and schedule performance.
 Performance report formats and templates.
 Policies and rules applied to creation of the performance report.
 Measures and indicators to be used in the report.
4.3 Project Support Processes
Configuration management
The phase lead is responsible for tracking the changes to the work product and
maintaining
the update version numbers. He is also responsible for maintaining a backup for
the
complete work on an optical disk. The backup must be done regularly, preferably
on daily
Basis. The individual team members are also responsible for maintaining a
backup of their
most recent version on an optical disk.
Setting up the release schedule
Taking each deliverable and breaking it down to determine the tasks needed to
produce each
one.
deliverable description Planned priority

status owner
released
date
Hotel A web based online hotel 2019-08-13 High
New Group six
management management system that
system(web) automates the whole process of
management.
Table 4.2.1 release schedule
4.4 Project Organization
4.4.1 Project Team

This team has five team members: a project manager, architect/technical
writer,
requirements engineer/tester, a developer, and a database builder. All
positions are
considered lateral and all team members are able to interact with each
other. The
organizational structure of a Team is best described in the following
diagram:
Client MINILIK HOTEL
Page | 11
Project Manager
( Zelalem shiferaw)
Designer Developer L. Requirement E.

Database B.
Architect
Leader
(Dinberu) (Natnael) Writer
(Garoma)
(ADISU) (Tesema)
Team Team Team

Team
Team
(Zelalem) (Adisu) (Diniberu)
(Natnael)
(Diniberu)
Figure 4.3.1: Organizational Structure of the Project
4.4.2 Mapping between clients and Organization
In the following table, the roles and contact information of the members are
given in table.
Table 1: Members, roles and contact information
Name Roles E-mail

Phone
Hotel manager client min@gmail.com

0911234577
Zelalem Shiferaw Project manager zelalemaastu@gmail.com

0938289960
Developer team
Adisu Negash Designer Leader negashadisu@gmail.com

0938266623
Requirement team
Diniberu Esubalew Developer diniberu@gmail.com

0929092343
Page | 12
Tesema Kenow Architect tesema@gmail.com 090899312o
Garoma Database builder gar@gmail.com

0939809887
Natnael Temesgen Requirement gz@gmail.com

0948038612
Engineer
Table 2: Roles and Responsibilities
Project Manager Identify and assign tasks as (and if) needed
Zelalem Works with team members to determine estimated time needed

for tasks
and creates internal timelines
Monitors progress of team members and provides status

reports
Keeps the project moving according to the specified

guidelines and
solicits help (if needed) to meet required deadlines
Submits all project deliverables to the appropriate parties

in the
appropriate file format
Requirements Performs client liaison duties including, but not limited

to: determining
Engineer/Tester the user interface of the product, determining the product
requirements,
and with the help of the writer, creating the user
documentation
Natnael
Verifies at each iteration that the product is meeting
customer needs
Determines necessary and unnecessary features based on

customer
desires
Creates a test plan and run tests to ensure that the final
product works
correctly
Determines the overall design and architecture of the

product
Architect /Writer Maintains change and version control of product and

documentation
Tesema Receives the submitted documentation and follows

documentation
guidelines
Page | 13
Assists all other positions with their documentation
Keeps documentation consistent
Developer Develop the design and implementation of the product
Diniberu Selects the programming language and mode of implementation
Creates the documentation of the code
Database Builder Works with the developer to coordinate -and implement the
database
Garoma elements of the project
Assists the developer with other implementation needs, if

necessary
Works with the writer on any database documentation needs
5. Communications Plan
Disseminating knowledge about the project is essential to the project’s
success. Project
participants desire knowledge of what the status of the project is and how they
are affected.
Furthermore, they are anxious to participate. The more that people are educated
about the
progress of the project and how it will help them in the future, the more they
are likely to
participate and benefit.
This plan provides a framework for informing, involving, and obtaining buy-in
from all
participants throughout the duration of the project.
Audience This communication plan is for the following audiences:

Project Sponsor
Steering Committee
Project Manager
User Group Participants
Subject Matter Experts
Communications Outreach The following is a list of communication events that

are
established for this project:
Page | 14
Monthly Status Reports The Project Manager shall provide monthly written status
reports
to the Steering Committee. The reports shall include the following information
tracked
against the Project Plan:
Summary of tasks completed in previous month
Summary of tasks scheduled for completion in the next month
Summary of issue status and resolutions
Monthly Steering Committee Meeting These status meetings are held at least once
per
month and are coordinated by the Project Manager. Every member of the Steering
Committee participates in the meeting. The Project Manager sends the status
report to each
member of the team prior to the meeting time so everyone can review it in
advance.
Bi-Monthly Project Team Status Meeting These status meetings are held every
other
month. Every member of the Project Team will be invited to participate in the
meeting.
Project Manager sends the status report to each member of the team prior to the
meeting so
everyone can review it in advance.
Website Use User Group Participants and Subject Matter Experts may be updated
monthly
at the discretion of the Project Manager. Information will be posted to the
project’s website.
6. Deliverables
These are the products or services that the project produces and “delivers” to
the customer or
client and the products or services to the project development team. They
should be spelled
out in detail within the project management plan, together with applicable
details about their
quality, length, size, or any other standards that apply.
6.1 To client
Deliverable Due Date

Project Macro Plan May 17,2019
Baseline Requirements Document May 24,2019
Project Plan May 30,2019
Technology Prototype June 05,2019
Customer-Approved User Interface June 12,2019
Architecture Document June 15,2019
First Iteration of the Product (Group June 18,2019
Review)
First Iteration of the Product (User June 23,2019
Review)
Testing Document June 25,2019
Page | 15
Second Iteration of the Product (Group June 28,2019
Review)
Second Iteration of the Product (User June 30,2019
Review)
User Guide and System Documentation July 02,2019
Final Product (Group Review) July 04,2019
Final Product (Class Review) July 08,2019
Final Product Presentation to User July 13,2019
6.2 From client

These are products or services the project requires from the
clients.
Deliverable Due Date
review documents May 17,2019
Requirement data May 24,2019
Test results July 13,2019
feedback June 14,2019
7. Work Plan
A work plan is an outline of a set of goals and processes by which a team and/or
person can accomplish
those goals, and offering the reader a better understanding of the scope of the
project
7.1 Work Breakdown Structure
The following is a list of deliverables and the activities required to produce the
deliverable. The actual
task breakdown to produce the first iteration product can be found in Section 5.4.
Deliverables Activities
Requirements  Meet with client to discuss requirements

Document  Analyze necessary requirements
 Create use cases and modeling diagrams for list
of features
 Write the document
Project Plan  Based on Requirements, determine detailed task

list to carry project to
first iteration
 Assign staff, estimate time needed
 Analyze schedule and timeline to determine
feasibility
 Make allowance and reprioritize as necessary
 Write the document
Page | 16
Technology Prototype  Learn the development language/environment
 Create a prototype of the website for user review
 Analyze the workability of the features
 Write technology prototype document
Architecture  Determine architecture of the project

Document  Create UML models showing data flow
 Write document
First Iteration  Best software system to date is shown to client

 Client analysis of software is gathered
 Changes needed to requirements, design, and code are
determined
 New documentation of requirements and design are
written as needed
Second Iteration  Best software system to date is shown to client

 Client analysis of software is gathered
 Changes needed to requirements, design, and code are
determined
 New documentation of requirements and design are
written as needed
 All changes at this time should be considered final
tweaks
User Guide and  Key features are identified

System  Instructions on usage are documented
Documentation
Final Product  Final product is presented to client
Page | 17
Page | 18
Diagram 7.1.1 Hotel Management System WBS
7.2 Resource
Staff resource requirements are 5 team members including developers,
requirements
engineers, technical writers, and project managers. All of the team members
will need at a
minimum computer access with basic programs such as MS Office. In addition to
this, all
members except for the requirements engineer should have the .NET environment
on their
computers so that they can help with development needs.
8. Milestones
Milestone Title criteria Start date End
date
number
1 Project kickoff When budget May 20,2019 May
21,2019
release
2 Project scope defined SRS reviewed, June 17,2019
June 24,2019
stakeholders
identified
Impl. Proposal
reviewed
3 Project planning Scope and June 25,2019
June 26,2019
concept
described
4 Project design Requirement June 27,2019
June 27,2019
agreed ,
project plan
reviewed
5 Project execution Architecture June 28,2019
June 28,2019
reviewed
Page | 19
and fulfilled
6 Project testing Coding of all June 30,2019
June 30,2019
functionality
finished
7 Project prototype release Unit testing June 30,2019
June 30,2019
and
integration
testing
fulfilled
8 User acceptance testing Project July 14,2019
July 15,2019
delivered
9 Production readiness The project July 17,2019
July 18,2019
testing
10 Product Release Product July 27,2019 July
29,2019
system tested
And
documentation
reviewed
11 Close project The whole August 12,2019
August 12,2019
contract is
fulfilled
Table 8.1 Hotel Management System Milestones
9. Performance and Metrics/ Efforts
Performance requirement
It is a simple fact that if performance is not a stated criterion of the system
requirements then the
system designers will generally not consider performance issues. While loose or
incorrectly defined
performance specifications can lead to disputes between clients and suppliers.
In order to avoid these
disputes and to assess the performance of the system we specified the following
performance
requirements:
Response time: It is the time required to perform some action when we use our
system. It includes
the waiting time and the service time. We are planned to reduce the service
time as much as possible.
Work load: is often described as the scenarios that the users are likely to
execute. The performance
of the system is dependent on how the load is delivered to the system. Now it
is difficult for us to
know the work load peak since the system we would like to develop is new for
the proposed hotel.
So to specify the peak that can support many customers at a time we have to see
the day to day
workloads and we will make a constant workload peak.
Scalability: In one respect scalability is simply specified as the increase in
the system’s workload
Page | 20
that the system should be able to process. The scalability required is often
driven by the lifespan and
the maturity of the system. We plan to scalable our system to satisfy our
customers by considering
the tradeoff.
Platform Consideration: A platform is defined as the underlying hardware and
software
(operating system and software utilities) which will house the system. This is
decided when our
project designer design the project.
Project Metrics
The phase lead is also responsible to maintain the quality standards of the
product. For this,
it is expected to ensure that
 There is no deviation from the requirements
 The modularity of the models is maintained
Software metric is a measure of software characteristics which are quantifiable

or countable.
Software metrics are important for many reasons, including measuring software
performance,
planning work items, measuring productivity, and many other uses. Here are some
software metrics
that can help us to track our progress:
Lead Time: Lead time quantifies how long it takes for ideas to be developed and
delivered as
software.
Lowering lead time is a way to improve how responsive software developers are
to customers.
Cycle Time: Cycle time describes how long it takes to change the software
system and implement
that change in production.
Production: Production metrics attempt to measure how much work is done and
determine the
efficiency of software development teams. The software metrics that use speed
as a factor are
important to managers who want software delivered as fast as possible.
Active Days: Active days are a measure of how much time a software developer
contributes code
to the software development project.
Efficiency: Efficiency attempts to measure the amount of productive code
contributed by a software
developer.
Mean time between failure (MTBF) and mean time to recover/repair (MTTR):
Both metrics measure how the software performs in the production environment.
Since software
failures are almost unavoidable, these software metrics attempt to quantify how
well the software
recovers and preserves data.
Application Crash rate: Application crash rate is calculated by dividing how
many times an
Page | 21
application fails (F) by how many times it is used (U).
ACR = F/U
Security metrics: Security metrics reflect a measure of software quality.
These metrics need to be
tracked over time to show how software development teams are developing
security responses.
10. Risk Assessment

In the development of a hotel management system the following risks may happen and
we have
proposed a mechanism to mitigate the risks.
Number Risk Risk Prob Effect

Risk Reduction
Level abilit
y
1 Inappropriate High Low Unable to complete key
•Clearly
version of the tasks
understand the
tools and
requirement
components.
specifications.
•Verify the version
of tools and
components used
at user’s site.
2 Failure to meet High Low Time-Cost
•Setup milestones
deadlines for
before scheduled
deliverable.
date for each
deliverable.
•If 2 or more
milestones are not
met then seek the
help of project
advisor in the
field.
3 User High Low Time-quality-cost
•Assess the
requirement
amount of work to
change
be changed and
negotiate.
•Assign more
resources to meet
additional
4 Loss to project High Low Unable to complete key tasks
Emphasize
of key staff
importance of
project within and
outside the
Hotel
5 Changes in High Med Removal of resource, lack
Make sure that
priorities of ium Of commitment, change in
senior
senior strategy or closure of
project. management are
Page | 22
management
aware of the
project, its relative
Importance, and its
progress.
6 Lack of team Medi High  Failure to achieve
business •Set the
member’s um benefits.
Professional
commitment  Extended duration.
Standards and
 Scope creep to copy
strictly follow the
today’s
same.
processes
7 Accidental loss High Low Cost-quality-time
•Maintain back-
of valuable
ups for every piece
information
of project work.
•Keep the storage
devices in a safe
place.
8 Poor capture High High Failure to meet minimum
Focus on User
of full User requirements.
Requirements
requirements
Capture at start of
Failure to achieve business
project.
benefits.
Best people with

Need to rework solution
appropriate
after rollout.
knowledge and
authority to
Failed delivery.
decide and time to
be involved
9 Costs could High High The hotel may be unable to
Ensure tight
rise financially support the
control of costs.
significantly project.
during the
Have a ‘pot’ of
course of the
money
project
available in case
risk occurs
10 Inadequate High High Users unable to use the
Ensure training
training – too system properly
staff are
little too late
involved from start
of project
11 Loss of power Low Low Users will not take the
Check for
or internet product seriously if it
scheduled outages
connection at cannot be demonstrated to
key roll-out, Work.
demo or
training
events.
Table 10.1: risk assessment table
Page | 23
11. Allocate resources
11.1 Identify and allocate resources
 Paper, pencil and pen

 Time to finish the project
 Stakeholders
 Computer
 Money
 Sensor(bar code reader)
Managing the overall progress of the project 1 week, 1 computer, 1 pen,

200 birr(coffee),15
paper,1 person
Designer team 2 weeks, 6 computer, 1 pen,
450 birr, 6
persons, graph paper, 1
pencil
Requirements Engineer/Tester team 2 weeks, 6 computer, 2 pen,
350 birr, 6
persons, 20 paper
Architect /Writer 18 days, 6 computer, 2 pen,
350 birr, 6
persons, 20 paper,
Developer team 1 month and 2 weeks, 2
computer, 2 pen, 350
birr, 6 persons, 20 paper
Database builder team 3 weeks, 2 computer, 2 pen,
150 birr, 6
persons, 20 paper
Revise plans and estimates to take into account resource constraints

If the project may not finished in the proposed plan our budget may not fit with
the required
resources that the project needs.
12. APPENDIX
APPENDIX 1: QUESTIONNAIRE
The following form is meant to aid in the collection of data. Kindly fill it.
1. For how long have you worked in the MINILIK Hotel?
Below 3yrs 3-5 yrs over 5 years
Page | 24
2. By introducing a Hotel management system do you think that the Hotel
department will
be at a higher competitive level?
yes No
3. How are orders in MINILIK Hotel taken?

…………………………………………………………………………………………..
4. What measures has the Hotel Department taken to ensure maximization on
securing data
…………………………………………………………………………………………….
5. How is retrieval of records done when needed?
APPEDIX II: PROJECT SCHEDULE.

ACTIVITY TIME
Project Proposal 3 week
Project plan. 2 week
Functional specification Three weeks
Technical specification Two weeks
Project source code Five weeks
User Manual Five weeks
Project presentation 20 minutes
Page | 25
APPENDIX III: REFERENCES

Walker Royce, (1998).Software Project Management. Addison-Wesley
Bob Hughes and Mike, (1999). Software Project Management. McGraw-Hill
Page | 26

SPM Hotel Managemenet System Updated

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPM Hotel Managemenet System Updated

Uploaded by

Copyright:

Available Formats

ADDIS ABABA SCIENCE AND TECHNOLOGY UNIVERSITY

College of Electrical & Mechanical Engineering

1. Adisu Negash ETS 0078/09

2. Denber Esubalew ETS 0322/09

3. Garoma Aga ETS 0444/09

4. Natnael Temesgen ETS 0784/09

5. Zelalem Shiferaw ETS 1075/09

6. Tesema Kenow ETS 1077/08

Submitted To: Instructor Amsalu T. May 17, 2019 G.C

Client: Minilik Hotel.

Project Name : Hotel Management System.

Project Manager : Zelalem Shiferaw .

Version: Final V1.0.

Issue Date: 5/17/2019

Prepared by: Group Members.

Authorized by: Zelalem Shiferaw.

1.2. Background information/Available Alternatives/Associated

2.1. Outline of Client’s Objectives/ Business Goals and

2.2. Outline of Organization Objectives / Project Goals and

2.3. Definitive Scope

3. Project Infrastructure, Standard and

3.1. Installation Standard and

3.2. Infrastructures Governance

4.1. Project lifecycle

4.2. Project Management

4.3. Project Support

4.4.2. Mapping between Organization and

7.1. Work Breakdown

1.1 Document Purpose

1.2 Background Information/Available Alternatives

1.3 Project Plan Maintenance

The following is an explanation of how the participating stakeholders will

 Incorporating the Plan into other Planning Mechanisms

In determining whether to recommend approval or denial of a plan amendment request,

 Reduce overall budget costs by 10% by 20xx

The client objectives from the major subsystems are:

2. From the Human resource / Employee information

2.1.2 Success Criteria

 Quality of the System

The system should have interactive user interface , it must be easily

1. Create food menu items.

2. Create a desktop application that will generate orders.

3. To generate bill slips.

4. Create receipts and store them in a database.

5. Generate routine statement reports.

2.2.2 Success Criteria

The success of the project is measured through:

 The quality of the system.

The Investment Portfolio

Success criterion Check/Uncheck

Financial Planning and Management

Do we have access to financial information related to those investments and are we

Success criterion Check/Uncheck

Resource Capacity and Demand

Success criterion Check/Uncheck

Measuring Planned vs. Actuals

Success criterion Check/Uncheck

 If any accident happens on team members.

2.3 Definitive scope statement

Hotel management system is performs the following tasks:-

 There will be harmonious of work.

3. Project infrastructure, standard and procedures

3.1 Installation standard and procedures