Bahir Dar University

Bahir Dar Institute of Technology

Faculty of Computing
Department of Software Engineering
Software Project and Process Management
Naky Hotel Reservation System Project Charter
Prepared By:

No Name ID Email Addressee

1. Amare Lakew BDU1207395 amareinformation@gmail.com

2. Samuel Demie BDU1207802 samueldemie9@gmail.com

Submitted to: Seffi Gebeyehu (Ass. Prof), Ph.D. Student

July/2021
Project Name: Naky Hotel Reservation System
Department: ALSD Website Developer
Focus Area: Naky Hotel Reservation system website
Product/Process: Website

I
Table of Contents

1 INTRODUCTION ..................................................................................................................... 1
1.1 Purpose ............................................................................................................................................................................................ 1
1.2 Scope ............................................................................................................................................................................................... 1
1.3 Definitions and Abbreviations ......................................................................................................................................................... 2
1.4 References ....................................................................................................................................................................................... 2
1.5 Overview of Contents of Document ................................................................................................................................................ 3
1.5.1 Section 2: Project Sponsor ............................................................................................................................................................ 3
1.5.2 Section 3: Management Proposal................................................................................................................................................. 3
1.5.3 Section 4: Contributors ................................................................................................................................................................. 4
1.5.4 Appendix A: Deliverables .............................................................................................................................................................. 4
1.5.5 Appendix B: Cost Estimate............................................................................................................................................................ 4

2 PROJECT OVERVIEW ........................................................................................................... 5

2.1 Project Sponsor............................................................................................................................................................................5

2.2 Business .......................................................................................................................................................................................5

2.3 Project Description ......................................................................................................................................................................6

2.3.1 Problem Statement ...................................................................................................................................................................... 6
2.3.2 Vision ............................................................................................................................................................................................ 6
2.3.3 Goals ............................................................................................................................................................................................. 6
2.3.4 Constraints.................................................................................................................................................................................... 6
2.3.5 Conditions and Limitations ........................................................................................................................................................... 7

3 MANAGEMENT PROPOSAL ................................................................................................ 7

3.1 Methodology Overview ...............................................................................................................................................................8
3.1.1 Benefits ......................................................................................................................................................................................... 9
3.1.2 Risks and Challenges ..................................................................................................................................................................... 9

3.2 Schedule .................................................................................................................................................................................... 10

3.3 Roles .......................................................................................................................................................................................... 11

3.4 Processes ................................................................................................................................................................................... 11

3.4.1 First Iteration .............................................................................................................................................................................. 12
3.4.2 Planning ...................................................................................................................................................................................... 12
3.4.2.1 Research .................................................................................................................................................................................. 12
3.4.2.2 Prototyping .............................................................................................................................................................................. 12
3.4.2.3 Requirements Engineering ................................................................................................................................................. 12
3.4.3 Modeling ..................................................................................................................................................................................... 13
3.4.3.1 Design ................................................................................................................................................................................. 13
3.4.3.2 Test Specification .............................................................................................................................................................. 13
3.4.4 Construction ............................................................................................................................................................................... 13
3.4.4.1 Implementation ................................................................................................................................................................. 13
3.4.4.2 Testing ................................................................................................................................................................................ 13

II
 3.4.4.3 Integration .......................................................................................................................................................................... 13
3.4.5 Delivery ....................................................................................................................................................................................... 14
3.4.5.1 Retrospective Analysis ....................................................................................................................................................... 14

3.5 Resources .................................................................................................................................................................................. 14

3.6 Quality Assurance ...................................................................................................................................................................... 14

3.6.1 Performance Metrics .................................................................................................................................................................. 14
3.6.1 Testing ........................................................................................................................................................................................ 15
3.6.2 Development Standards ............................................................................................................................................................. 16
3.6.3 Formal Review ............................................................................................................................................................................ 16

3.7 Change Management ................................................................................................................................................................. 17

we implement the following change management to control our changes .................................................................................. 17

3.7.1 Schedule Control ........................................................................................................................................................................ 17
3.7.2 Requirements Change ................................................................................................................................................................ 18
3.7.3 Change Negotiation .................................................................................................................................................................... 18

3.8 Risk Management ...................................................................................................................................................................... 18

3.9 Technical Methods ..................................................................................................................................................................... 19

3.9.1 Methods, Tools, and Techniques ................................................................................................................................................ 19
3.9.2 Software Documentation ........................................................................................................................................................... 20

4 CONTRIBUTORS ................................................................................................................... 20
4.1 Comments ................................................................................................................................................................................. 20

4.2 Version History .......................................................................................................................................................................... 20

4.3 Approvals................................................................................................................................................................................... 20

5 APPENDICES.......................................................................................................................... 21
Appendix A: Deliverables ................................................................................................................................................................. 21

Appendix B: Cost Estimate ............................................................................................................................................................... 21

Appendix C: Partnership Guidelines ................................................................................................................................................ 22

REFERENCES ........................................................................................................................... 24

III
 LIST OF TABLES

Table 1:Contributors .................................................................................................................................................... 4

Table 2: Deliverable...................................................................................................................................................... 4
Table 3:Activity cost estimation .................................................................................................................................. 4
Table 4:Human resource cost estimation ................................................................................................................... 5
Table 5: specific responsibilities of risk management ............................................................................................. 10
Table 6:Development Schedule ................................................................................................................................. 10
Table 7:Project Roles Summary................................................................................................................................ 11
Table 8: Estimated Level of Effort for Development Activities ............................................................................. 12
Table 9:performance metrics checklist ..................................................................................................................... 15
Table 10:Test case for the system .............................................................................................................................. 16
Table 11: Sample risk management plan ................................................................................................................. 19
Table 12: Version and Revision History ................................................................................................................... 20
Table 13: Project Deliverables................................................................................................................................... 21
Table 14: Estimation Developer cost......................................................................................................................... 22
Table 15: Estimated Project Costs ............................................................................................................................ 22

LIST OF FIGURES

Figure 1: incremental Iteration model for system development .............................................................................. 8

IV
1 Introduction
Automation is the use of control systems and information technologies to reduce the need for human work in the
production of goods and services. The main advantages of automation are replacing human operators in tasks
that involve hard physical or monotonous work, Economy improvement, Automation may improve in the
economy of organizations, society or most of humanity, reduces operation time and work handling time
significantly, provides higher-level jobs in the development, deployment, maintenance and running of the
automated processes.

There is an effort to automate the NAKY HOTEL room reservation system so that the reservation system of
NAKY Hotel will be automated or computerized which will reduce the problem existing today and customers
can interact easily with the system the customer can access resources from the new system. As a result, the
customer will be more comfortable. Automation has a principal effect on the customer reservation process.

1.1 Purpose
Now Naky hotel works a manual system for managing customer booking, reserve rooms, etc., due to these reasons
we are motivated to work on this project to change the manual system into a computerized system.

1.2 Scope
even the hotel gives several services like, generate report employee payments, making a reservation, and give
guaranty hotel services our scope mainly focuses on making a room reservation, update room information,
introduce hotel services, and register customers.

The functional requirements of our proposed system include:

✓ The system should make a reservation

✓ Users can open hotel information to know the service
✓ The system should register customer information
✓ The system should retrieve customer information
✓ The system should give clear information for the manager and the customer
✓ The system should check availability
❖ Checking in, check out:
✓ Managers display the system to check the information of customers when they check-in (out).
✓ Allows customers to check-in (out) when somebody else has reserve rooms for them.
✓ Allows customers to change or cancel the reservation after their checking in.

1
Project Charter 2021
 ❖ Allows customers to post their feedback on a webpage
✓ Manager can reply to feedbacks
✓ Show the information about the hotel
✓ Modify and update information

A Non-Functional Requirement is usually some form of constraint or restriction that must be

considered when designing the solution. Such as:

❖ Performance requirement: the system that we proposed has a wide access time and its response time is
quick. It is also easy to use
❖ user interface: the system interface that will be developed must be interactive and understandable.
❖ Accuracy: the system is accurate, meaning if the user wants to search or login into the
the system, they can get the correct or real information.
❖ Reliability: Since the system is web-based where the connection is available, it is always reliable
❖ Response time: the response time of the system should be short
❖ Security: updating, retrieving of information must be only for the manager of the hotel. To make the
proposed system more secured both username and password as well session is going to be used in this
system.

1.3 Definitions and Abbreviations

ALSD- is our project team name that takes from our First name first letter and our father’s name

first latter where, A=Amare, L= Lakew, S= Samuel, D= Demie.

SDLC- Software development life cycle

FMEA- Failure Mode and Effect Analysis

FTA- Fault Tree Analysis ()

DBMS (MySQL)- Database management system -my standard query language

EMPID – Employ Identification number

1.4 References
We have used different related works and we list the references at the end page of this document.

2
Project Charter 2021
1.5 Overview of Contents of Document
Naky hotel reservation system is a web-based system that supports all operating systems and
android versions to deploy and run the system. our system will be sponsored by the holder of
Naky hotel to complete the development and support us by giving the information about the
current working environments.

1.5.1 Section 2: Project Sponsor

To developed the Naky hotel reservation system we focused for find a sponsor to cover all the costs that require
for the system development and ask the hotel holder and hotel manager and they are offered to support us
according to our estimated cost with the schedule.

1.5.2 Section 3: Management Proposal

We identify many potential projects as a part of their strategic planning processes and they often rely on the
experienced project manager to help them make a project selection.

To identify or select our project we use the following five common techniques:

Focusing the organization needs: Naky hotel needs many activities performed by
computerized system example food ordering, room reservation, generate reported.
Categorizing of IT project: it is the method of selecting the project based on various
categorization such as the project motivation, time Table, and general priority. the motivation for the
project is often to respond to a problem.
Problems: Naky hotel has many limitations for example all activities can perform
manually.
Opportunity: there is an opportunity to works computerized system
Directive: the government can influence the Naky hotel to generate the reports
by computerized and announce the hotel.
Performing net value analysis: net value analysis is the method of calculating the expected net monetary
gain or losses from the project by discounting all expected future cash inflows and outflows to the present
point in time.

3
Project Charter 2021
1.5.3 Section 4: Contributors
Herewith are our team members and our contribution to developing this Naky hotel reservation system.

NO Name Contribution
1. Amare Lakew Project manager
Builder
2. Samuel Demie Prototyper

Table 1:Contributors

1.5.4 Appendix A: Deliverables

Milestone Deliverable

Project Charter Identifies project needs, such as budget and time frame
Creates acceptance to begin the project

Project Management Plan Provides stakeholders with potential issues and risks
Allows stakeholders with information relating to the project

Project Schedule Provides stakeholders and project team with an understanding of the
different tasks that must be met by the requirements

Table 2: Deliverable

1.5.5 Appendix B: Cost Estimate

We Estimating costs involves developing Naky hotel reservation system an approximation or estimate of the
Costs of the resources needed to complete.

Activity Price in Birr

Feasibility study 20,000.00
Requirement analysis 25,000.00
System analysis 15,000.00
System design 150,000.00
Implementation 200,000.00
Testing 150,000.00
Maintenance 150,000.00

Total 710,000

Table 3:Activity cost estimation

4
Project Charter 2021
Human resource cost

Human Resource Price in Birr

Manager 100,000.00

Member 11,000.00

Programmer 150,000.00

System designer 130,000.00

Training 17,000.00

System tater 20,000.00

Total 428,000

Table 4:Human resource cost estimation

2 Project Overview
The system will be developed using a java programming language. This system will indeed help the hotel
reservation system and the esteemed staff members to manage and steer the hotel’s functionality and transactions
to realize its maximum potential in addition to its competence in the hotel business field.

2.1 Project Sponsor

The project sponsor for the Naky hotel reservation system is the holder of the hotel or the manager of the hotel
will fund our project. Naky hotel reservation system is web-based in Bahir dar. Ethiopia.

Naky Hotel Manager

nakyhotel@gmail.com

+251 91 876 0075

Bahir Dar, Ethiopia

2.2 Business
Naky Hotel Reservation system minimizes human power, cost, time and provides online reservation and booking
for the customers. Naky hotel reservation is a web-based system and system developed by Java programming

5
Project Charter 2021
language. Naky hotel reservation system is also cross-platform, with support for development on Windows and
Android.

2.3 Project Description

Naky Hotel is one of the newly established found in Bahir dar, Ethiopia. Construction of the hotel was started in
around 2006 E.C in Keble 05 of Bahir Dar town. It is found in the northern part of Ethiopia, 322 kilometers far
from Addis Ababa. The Naky hotel consists of more than 42 employees. Naky hotel offers many services for the
customer such as bed, cafe, and restaurant and meeting hall, spa. Naky hotel uses a manual system for managing
customer booking. The reservation system offers registration of customer information, in a web-based system.
Its objective is to do effectively with a minimum employee, saving time, simplicity; to ensure that the hotel
delivers information to who it belongs to the customer e.g., by telephoning or email.

2.3.1 Problem Statement

The current manual system needs extra-human power and costs to handle the reservation. Because, the current
system of reserving new customers has been done manually, implying that there is time and space consumption.
so that the reservation system of Naky Hotel will be automated or computerized which will reduce the problem
existing today and customers can interact easily with the system the customer can access resources from the new
system.

2.3.2 Vision
Our project aims to use a Computerized work environment to save time and human power effort as well as cost
minimization for reservation of customers. Finally, the system will reduce the problem existing today and
customers can interact easily with the system the customer can access resources from the new system.

2.3.3 Goals
1. To develop and deliver a hotel reservation web-based system that solves the problems identified and
achieves the vision of the Naky hotel.
2. To provide the team with practical experience in formal software and web-best system development.
3. To minimize the human resource number and save time to reserve and booking.
4. To change the manual reservation system into a computerized system.

2.3.4 Constraints
Naky hotel reservations will be implemented in java. A compatible on multiple platforms, like operating
system and android system. therefore, the system must be implemented in portable java.

6
Project Charter 2021
 Naky hotel reservation system will not be covering all services that provide in the hotel. Wings
Naky hotel reservation system is a web-based system that deploys on the server and is accessible by the
internet.
Our project must be complete by the end of the second semester and we made maintenance after
deployment by our team.
The project manager must have access to the Naky hotel reservation system. Source code access may be
required for the development. The project sponsor will decide upon the terms and means of providing
access.

2.3.5 Conditions and Limitations

The limitations are sometimes referred to in project management as the triple constraint.

❖ Scope: in our project there is a limitation that we don’t cover in our project like,
✓ Guaranty for the customer property
✓ Security for the garden
✓ Employee payment
✓ Employee selection
❖ Time: the time is too short to work on the project effectively
❖ Cost: in our project there is no enough budget to complete the project

2.3.6 Success Criteria

Naky hotel reservation system will provide the following features to achieve the vision of the project.

Approach: to change the manual file handling system into the advanced method of a computerized system.
✓ To reserve bedroom and other services
✓ To access the hotel information
✓ To save complicated problems that faced to record the manual system
✓ To create a user-friendly environment
✓ To keep data security and reliability
3 Management Proposal
This section proposes a formal development methodology for adoption to the Wings project. The proposed
methodology is discussed in terms of schedule, roles, and processes.

7
Project Charter 2021
3.1 Methodology Overview
We propose an iterative and incremental methodology incorporating rapid prototyping techniques for the
development of the Naky hotel reservation system project.
There are five different phases of project management to be followed on the success of the
project.
A. Initiation phase: n this stage we need to accomplish the feasibility study of the project, assemble
the project team along with the resource provided to accomplish the project, and the working
environment is set up in the initiation phase.
B. Planning: During this phase that a project management plan is developed all comprehensive of
individual plans for – cost, scope, time, quality, communication, risk, and resources.
C. Execution: In the execution phase the project deliverable is developed and completed, adhering to
the plan as developed in the previous phase.
D. monitoring and control: This phase mostly deals with measuring the project performance and
progression concerning the project management plan.
E. Closure: A project is formally closed in this phase.
Iteration is composed of processes and is repeated several times for all phases, with each iteration incrementally
contributing to the documentation, the design, and the functionality of the system.

Initiation Planning

Closure
SDLC

monitoring Execution
and control
Figure 1: incremental Iteration model for system development
The proposed development methodology is modeled in Figure 1. The processes within each iteration are
expanded between the incremental phase.

8
Project Charter 2021
3.1.1 Benefits
The iterative model is implemented during the earlier stages of the software development process, which allows
developers and testers to find functional or design-related flaws as early as possible, which further allows them
to take corrective measures on a limited budget. Other benefits or advantages of this model are:

We select This model because of the following appropriate benefits

Some working functionality can be developed and early in the software development life cycle (SDLC).

It is easily adaptable to the ever-changing needs of the project as well as the client.

It is best suited for agile organizations.

It is more cost-effective to change the scope or requirements in the Iterative model.

Parallel development can be planned.

Testing and debugging during a smaller iteration is easy.

Risks are identified and resolved during iteration, and each iteration is easily managed.

3.1.2 Risks and Challenges

There are many risks are there whenever the project starting One of the high-level risks to the successful outcome
of the project is financial risks. Money is the important starting upending of the project. If cost estimating is higher
than the project doing and also lower the produce the risk has occurred.
Risk management plan
Risk management is the process of identifying risk, assessing risk, and taking steps to reduce risk to an acceptable
level. The risk management approach determines the processes, techniques, tools, and team roles and
responsibilities for a specific project. The risk management plan describes how risk management will be
structured and performed on the project.

9
Project Charter 2021
 the following tables detail specific responsibilities for the different aspects of risk management.

Risk Activity Responsibility

Risk Identification All project stakeholders.

Risk Registry Project Manager.

Risk Assessment All project stakeholders.

Risk Response Options Identification All project stakeholders.

Risk Contingency Planning Project Manager

Risk Response Management Project Managers.

Risk Reporting Project Manager.

Table 5: specific responsibilities of risk management

3.2 Schedule
The iterative development methodology results in the incremental completion of products. At the delivery
deadline for each iteration, incremental products will be ready for review. At the project completion, the
integrated products will be ready for delivery. Four iterations are planned, with an extended first iteration.

The development schedule is provided in Table below.

Process Products (Deliverables) Dates

Initiation Meet, discuses, Charter 04/07/2021 – 06/12/2021

Iteration I 06/13/3021 - 07/17/2021

Planning Requirements, cost, time 06/14/2021 – 06/25/2021

execution Start coding 06/26/2021 - 07/13/2021

Monitoring and Control project performance and progression 04/07/2021 – 06/12/2021

control
Closure Close the project phase 07/17/2021

Completion Naky Hotel reservation system Final, User Documentation, 07/19/2021 - 07/29/2021
SRS, SDS, STS, Project Log, Final Presentation
Table 6:Development Schedule

10
Project Charter 2021
 3.3 Roles
The hotel reservation system project will be undertaken by a team of two students on behalf of the project
manager, Prototyper, and Builder. The team consists of Amare Lakew and Samuel Demie. We give an official
name for our Team as ALSD where it indicates we select our first name first later and our father’s name first
Later. The project sponsor will Naky Hotel.

No Name Role Description Contact information

1 Amare Lakew Project facilitates and coordinates the Email:amareinformation@gmail.com

manager actions of the workgroups
Phone: +251912370992
conducts modeling and
Builder construction activities

2 Samuel Demie prototyper performs planning and analysis Email:samueldemie9@gmail.com

activities
Phone: +251928524984

Table 7:Project Roles Summary

3.4 Processes
Each development iteration consists of five processes: Initiation, planning, execution, monitoring and control,
and Closer. Within each process, team members or workgroups will have specific responsibilities.
The five processes will incrementally develop and document the project.

Activity Estimated Effort (days or Hours) Responsible

initiation 12 Hours Team

planning 4 days Team

Execution 15 days Team

Monitoring and control Start to end Team

Modeling 10 days Team

Design 10 days Team

11
Project Charter 2021
 Test Specification 2 days Taster

Construction 2 days Team

Implementation 15 days Team

Testing 4 days Test manager

Integration 10 days Tester

Delivery 4 days Project manager

Iteration Total 68 days and 12 hours Team

Table 8: Estimated Level of Effort for Development Activities

3.4.1 First Iteration

We used an Incremental iteration model for doing our project and the first iteration will cheek a starting from
the initiation phase up to the closure phase for sure the functionality and the flow of the project s defect-free or
not.

3.4.2 Planning
We initiated a planning phase for developing Naky hotel reservation system project. and Planning will be
managed by our project manager and passed out mainly by the prototyper workgroup.

3.4.2.1 Research
We review different researches related to our project charter and use the templates for Naky Hotel reservation
systems. The research helps us for references or guidelines to corporate our projects. All the team member has
the responsibility to review the related works.

3.4.2.2 Prototyping
We use an experimental process where design teams implement ideas into tangible forms from paper to
digital. Teams build prototypes of varying degrees of fidelity to capture design concepts and test on users. With
prototypes, you can refine and validate your designs so your brand can release the right products.

3.4.2.3 Requirements Engineering

We follow the Requirements engineering process to eliciting stakeholder needs and desires and developing them
into an agreed-upon set of detailed requirements that can serve as a basis for all subsequent development activities.
12
Project Charter 2021
The purpose of we used requirements engineering methodologies is to make the problem that is being stated clear
and complete, and to ensure that the solution is correct, reasonable, and effective.

3.4.3 Modeling

We use Project Modeling for the sales and initiation phase of a project. It allows us to develop more accurate
plans in less time, accelerate the sales process, and ultimately, drive better outcomes for your customers.

3.4.3.1 Design
The project team design the system structure and start execution to achieve the goal. Based on the design phase
the next SDLC will run accordingly.

3.4.3.2 Test Specification

According to our design specification, the team workgroup will generate a set of unit and integration test cases
to validate the implementation. The prototyper workgroup may also contribute by using test cases and test
scenarios for system tests during this process to validate the design and requirements.

3.4.4 Construction
The team will construct the project to integrate and test all the functionality to satisfy the customer and
maintain if the defect will have occurred in the developed project.

3.4.4.1 Implementation
We Implement all the project consists of the process of actual programming and the software specified by the
SDLC.

3.4.4.2 Testing
We use Software testing for an investigation conducted to provide stakeholders with information about the
quality of the software product or service under test.

3.4.4.3 Integration
The team members take the task and do the project based on the customer requirements and taste each phase if
there will the defect and make exciting for fixing the defect to free. Then all team member has meat and integrates
all the projects.

13
Project Charter 2021
3.4.5 Delivery
Finally, we pass the process within each development increment is delivery. And the project manager will
forward to the sponsor to deliver and activate and deploy to start the system.

3.4.5.1 Retrospective Analysis

we evaluating all steps and trace back steps what we have done and what we have not. Mainly we looking at the
following three aspects of the project.

✓ Functionality
✓ Time
✓ cost

3.5 Resources
All procurement activities must be performed and managed with current personnel. No
additional personnel will be hired or re-allocated to support the procurement activities on this
project.

Technology:
Parts specifications have already been determined and will be included in the statement of
work. While proposals may include suggested alternative material or manufacturing processes, parts
specifications must match those provided in the statement of work exactly.

3.6 Quality Assurance

To promote the quality and consistency of the project we will implement four types of quality assurance:
performance metrics, testing, development standards, and formal review.

Basic Tasks of Quality Assurance

Plan quality management,

Control quality,
Perform quality assurance

3.6.1 Performance Metrics

Performance metrics are a key component of an effective quality management plan and are the measurements
used in ensuring customers receive acceptable products or deliverables. We prepare a performance metrics
checklist, including sales, profit, return on investment, customer happiness, customer reviews, personal

14
Project Charter 2021
reviews, overall quality, and reputation in a marketplace. Then collect from our Metrix and decide our project
performance.

Quality checklist

Project: Naky hotel reservation system Date: July

07/22/2021 G.C

ID Performance Item Verification

yes No Date Comment

0001 Sales

0002 profit

0003 return on investment

0004 customer happiness

0005 customer reviews

0006 personal reviews

0007 overall quality

0008 reputation in a marketplace

Table 9:performance metrics checklist

3.6.1 Testing
We identify test cases and test scenarios to website test specifications. A test case describes a single functional
behavioral test, the expected result, and the actual result.

15
Project Charter 2021
Test case:

Project Name: Naky Hotel Reservation system

Test Case_01

Test case ID: TC_UI_1 A test designed by: Amare Lakew

Test priority: Low Test designed Date: 07/17/2021

Module name: Home page, About Test executed by: Samuel Demie
us,

Test title: User interface Test execution date: 07/18/2021

Pre-condition: the interface should be easy to use

Step Test step Test Data Expect result Actual result Status(pass/fail) Remark

1. Use url: home Open the home page Open properly Pass
page of the website

2. Use the About us Open user interface open Pass

URL

Table 10:Test case for the system

3.6.2 Development Standards

Development standards and process guidelines will establish basic conference standards, such as coding,
documentation formatting standards, to promote consistency between the work products of each team member.

3.6.3 Formal Review

We follow the Formal reviews for the formal process to communicate with each other with teams and sponsors
of our project.

16
Project Charter 2021
As we review the researches formal review process consists of six main steps and we also apply all those
processes to achieve our goals and satisfy our users.

1. Planning: the first phase of the formal review is the Planning phase.
2. Kick-off: this kick-off meeting is an optional step in a review procedure.
3. Preparation: the reviewers review the document individually using the related documents, procedures,
rules, and checklists provided.
4. Review meeting: review all phases and identify the defect and success criteria
5. Rework: the number of defects found per page exceeds a certain level then the document has to be
reworked.

3.7 Change Management

Changes usually fail for human reasons: the promoters of the change did not attend to the healthy, real, and
predictable reactions of normal people to disturbance of their routines. Effective communication is one of the
most important success factors for effective change management. All involved individuals must understand the
progress through the various stages and see results as the change cascades.

we implement the following change management to control our changes

1. We define the changes.

2. Select the change management team.
3. Identify management sponsorship and secure commitment.
4. Develop an implementation plan including metrics.
5. Implement the change in stages
6. Collect and analyze data.
7. Quantify gaps and understand resistance.
8. Modify the plan as needed and loop back to the implementation step.

3.7.1 Schedule Control

To run our project, we have to control the scheduling process to achieve our project:

✓ capture the current schedule status

✓ determine the variance from the schedule baseline
✓ understand the nature of the variance and its causes

17
Project Charter 2021
 ✓ respond by taking appropriate action.
If changes are required to the schedule, then they must go through the change control process, the change
should be re-evaluated and planned then used to update the schedule baseline.
3.7.2 Requirements Change
We may require changes to communicate a significant change in project scope, deliverables, budget, schedule, or
resourcing, while also documenting the reasons that necessitated the change. we outline the content of project
change requests to be used for our projects.

Specifically, a Project Change Request is required in the following circumstances:

✓ Awe may need additional funding of more than 15% of the approved project budget.
✓ We need additional time if we run out of schedule
✓ Extra project resources will be required
✓ Changes in project scope and/or deliverables will be required to achieve the objectives of the project
✓ Our Project sponsor determines that strategic visibility for a project change or other project decisions
3.7.3 Change Negotiation
We were responsible to do this when the sponsor needs to change the project based on our agreement. Our team
will ultimately be got rough to satisfy the customers and the users. To negotiate the change, we list down the
following criteria to do.

✓ Additional budget if the change is out of our scop

✓ Additional time frame if the change will out of our schedule
✓ Extra budget for the teams and materials

3.8 Risk Management

There are many risks are there whenever the project starting One high-level risk to the successful outcome of
project financial risks. Money is the important starting upending of the project. If cost estimating is
higher than the project doing and also lower the produce the risk has occurred.

18
Project Charter 2021
Sample risk management plan

S. Description of Mitigation Remark

Likelihood Risk owner
No Risk

1 Scop Do with our schedule what we

High Project Team
paled

2 Resource medium Project Use the materials properly

manager

3 Schedule low Project team More hours will be allocated to

each enhance development speed.

4 Budget Compromise can be made to meet

the most critical portions of the
Medium Project team project. Once more funds are made,
more
features may be included.

Table 11: Sample risk management plan

3.9 Technical Methods

3.9.1 Methods, Tools, and Techniques
Methods for Risk Identification

Various risk identification tools exist. The tools and methodologies proposed to be used during
Naky Hotel Reservation system phase of the project are:

Brainstorming sessions
Risk assessment workshops
Work sessions during Technical Design Reviews
External review(s) of risk register/database
Structured or semi-structured interviews with experts
Using knowledge, expertise, and experience of the team
Failure Mode and Effect Analysis (FMEA)
Fault Tree Analysis (FTA)

19
Project Charter 2021
3.9.2 Software Documentation
The software materials are required for the project. java programing language will be used to develop the software
component.
The following software tools are required for the development of our project.
✓ Windows 10 operating system: Development environment
✓ Microsoft Office Word 2016: For documentation (e.g., to specify requirements)
✓ XAMP: Used as a web server (Apache) and DBMS (MySQL).
✓ Google Chrome: For interpreting and executing the admin XAMPP Server and create a database.
4 Contributors
ALSD is Naky Hotel reservation system development team list document in table 12 that shows the
contribution for each section and each title, and approvals from our team members.

4.1 Comments
The following table describes the team members and individual effort for developing the system per the section
or the title with respected days.

4.2 Version History

Date Sections Contributors

7/19/2013 Table of Contents, Headers, 1.1, 1.2 Amare

7/20/2013 2.1, 3.3, 3.4, 3.5, 4.2, 4.3, Appendix B Amare, Samuel

7/21/2013 1.3, 1.5, 2.2, 3.1, 3.2, Appendix A Amare

7/22/2013 2.3, 3.1.2, 3.6, 3.7, 4.1 Samuel

7/23/2013 1.3, 1.5, 4.1, Appendix B, Review and Revision, Samuel, Amare

7/24/2013 Review and Revision Amare, Samuel

Table 12: Version and Revision History

4.3 Approvals
The criteria for the selection and award of finding contracts and approval of our project under this project will
be based on the following decision criteria.

Ability of the vendor to provide all items by the required delivery date

20
Project Charter 2021
 Quality
Cost
Expected delivery date
Comparison of outsourced cost versus in-sourcing
Past performance
1. Team Members
A. Amare Lakew ________________________
B. Samuel Demie ________________________
2. Advisor
A. Seffi Gebeyehu (ASS. Prof)
5 Appendices
Appendix A: Deliverables

Milestone Deliverable

Project Charter
Project Management Plan
Project Schedule
Project Management Plan
Identifies project needs, such as budget and time frame
Creates acceptance to begin the project
Provides stakeholders with potential issues and risks
Allows stakeholders with information relating to the project
Provides stakeholders and project team with an understanding of the
different tasks that must be met by the requirements
Details the schedule, roles, and processes proposed in the charter.

Table 13: Project Deliverables

Appendix B: Cost Estimate

We are a two-person development team with a total of 68 days and 12 hours to create the final product. Our pay
per individual would correlate to what an intern in the software development industry would make, which is
estimated per month.

21
Project Charter 2021
We estimate resource costs based on their functionality.

EMPID EMP name Position Qualification Salary Contact address

ABC001/13 Amare Lakew Project MSc (SE) 20,000 Birr amareinformation@gmail.com

manager

ABC002/13 Samuel Demie Coordinator MSc (SE) 15,000 Birr samueldemie9@gmail.com

35,000 Birr

Table 14: Estimation Developer cost

Resource Costs

Resource Cost/Birr

Laptop 35,000.00

Office Rent 25,000.00

Development Tools 15,000.00

Total: 75,000.00

Table 15: Estimated Project Costs

Appendix C: Partnership Guidelines

B.1 Requirements Guidelines for Project Sponsors
The project sponsor has the right to:

✓ Ask the developers to support to give training for the user.

✓ Communicate with the team to explain requirements development processes.
✓ Ask the team to treat with respect and to maintain a project.
✓ Give feedback and control the project.
The project sponsor has the responsibility to:

A project sponsor is typically responsible for establishing a series of key aspects about the project, which can be
summed up under categories of vision, governance, and value/benefits realization.

✓ initiating,
✓ ensuring,

22
Project Charter 2021
 ✓ approving, and
✓ Respect developers’ assessments of scope and feasibility.
✓ Know and approve requirements.
✓ Follow-up the team and support by finance

23
Project Charter 2021
References
http://tryqa.com/what-is-formal-review/. (n.d.). Retrieved from http://tryqa.com/what-is-formal-review/

https://asq.org/quality-resources/change-management. (n.d.). Retrieved from https://asq.org/quality-

resources/change-management

https://project-management-knowledge.com/definitions/c/control-schedule/. (n.d.). Retrieved from

https://project-management-knowledge.com/definitions/c/control-schedule/

https://www.pmi.org/learning/library/charter-selling-project-7473. (n.d.). Retrieved from

https://www.pmi.org/learning/library/charter-selling-project-7473

https://www.pmi.org/learning/library/duties-effective-project-sponsor-responsibilities-4469. (n.d.). Retrieved from

https://www.pmi.org/learning/library/duties-effective-project-sponsor-responsibilities-4469

https://www.pmi.org/learning/library/importance-of-project-sponsorship-9946. (n.d.). Retrieved from

https://www.pmi.org/learning/library/importance-of-project-sponsorship-9946

https://www.pm-primer.com/control-schedule/. (n.d.). Retrieved from https://www.pm-primer.com/control-

schedule/

https://www.sciencedirect.com/topics/computer-science/requirement-engineering. (n.d.). Retrieved from

https://www.sciencedirect.com/topics/computer-science/requirement-engineering

https://www.workfront.com/project-management/life-cycle/initiation/project-charter. (n.d.). Retrieved from

https://www.workfront.com/project-management/life-cycle/initiation/project-charter

https://www.wrike.com/project-management-guide/faq/what-is-a-project-charter-in-project-management/. (n.d.).
Retrieved from https://www.wrike.com/project-management-guide/faq/what-is-a-project-charter-in-
project-management/

24
Project Charter 2021