D04CE128,03CE72 PROJECT MANAGEMENT

2. PROJECT MANAGEMENT

2.1 PROJECT PLANNING

2.1.1 Project Development & Justification

After understanding the objectives of the project we decided to use Prototype Model
for the development of the system. The main reason behind going for this model is that
the changing requirements can easily be covered first by building up the prototype and
then making further additions to it.
2.1.2 Project Duration

The duration of our academic session of the 6th semester was meant to complete the
project.
Before starting the actual work on the project we have studied the actual process done in
the store to manage hotel manually, then we have visited some hotels to see the system
like our system to understand their functionality then started the work of preparing
synopsis.
The work was divided into different phases: like analysis of the project, requirement
gathering, designing and implementation and finally testing phase.

2.1.3 Roles and Responsibilities

 Requirement Analysis: Both

 Database design :Both
 Screen design : Both
 Implementation : Both
 Testing : Both
 Documentation : Both

CITC(CE) 4
D04CE128,03CE72 PROJECT MANAGEMENT

2.2 PROJECT SCHEDULING

Activity Duration in days

Project definition analysis 2

Preliminary investigation 4
Identifying scope 2
Feasibility study 2
Requirement gathering 10
Requirement analysis 7
Requirement specification 2
System analysis 10
Design 10
Implementation 7
Testing 2

2.3 RISK MANAGEMENT

2.3.1 Risk Identification

a) Performance Risk:
 It is possible that project doesn’t satisfy the needs of the user.
 The user may not get the details he/she intends to see and the result may be
displayed in some other form. This is the major risk that needs to be considered
when developing this project.

b) Cost Risk:
 This is one risk that occurs in each and every project. And hence it must be solved
because cost of the project is very important for any organisation.

CITC(CE) 5
D04CE128,03CE72 PROJECT MANAGEMENT

c) Support Risk:
 This risk involves the continuous updating of the software and any correction that
are made to the software in case there is a serious bug.

d) Requirement risk:
 They are deriving from the changes to the user requirement & the process of
managing the requirements & the process of managing the requirements change.

e) Schedule Risk:
 This is one risk that occurs in each and every project and hence this can be
considered as general risk.
 Even though we had initially developed a timeline chart of the project, it so
happened that we were no able to comply the schedule at all times.

2.3.2 Risk Analysis

Table 2.3 Risk Analysis

Risk Type Probability Impact

Performance 50% Critical
Cost 15% Marginal
Support 10% Marginal
Requirement 10% Marginal
Schedule 15% Marginal

2.3.3 Risk Planning

 To overcome the performance risk, we followed the prototype method.

 The prototype method involves developing working models and allows the users
to work with the system and give suggestions on the model.

CITC(CE) 6
D04CE128,03CE72 PROJECT MANAGEMENT

 The next risk that was encountered was the support risk. The support risk
involves performing testing operations and to correct any bugs that are
encountered during the phase.
 The next risk is requirement risk. The project may not fulfil all requirement of the
user. But we try our best to fulfil it.
 The final risk that is encountered is the schedule risk. It is very common among
software developers to either fall behind or move ahead of the time schedule. We
in developing the project have tried our level best to adhere to the time schedule
that we have developed at the beginning of the project.
 Even if we fell back we adjusted to the time schedule by working a little bit of
more hours on that particular phase.

CITC(CE) 7