Scribd
Upload
7 views4 pages

Practical 1

The document outlines a project plan for a Hospital Management System, detailing its objectives, requirements, project approach, and maintenance strategies. It emphasizes the importance of tracking staff, patients, treatments, and medications while providing a structured methodology for project execution, including design, implementation, testing, and deployment. Additionally, it addresses cost estimates, roles and responsibilities, and project constraints that need to be considered for successful completion.

Uploaded by

nomadslord
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views4 pages

Practical 1

The document outlines a project plan for a Hospital Management System, detailing its objectives, requirements, project approach, and maintenance strategies. It emphasizes the importance of tracking staff, patients, treatments, and medications while providing a structured methodology for project execution, including design, implementation, testing, and deployment. Additionally, it addresses cost estimates, roles and responsibilities, and project constraints that need to be considered for successful completion.

Uploaded by

nomadslord
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

PRACTICAL - 1

Aim: - To draft the project plan for Hospital Management System.

1. Objective: -

• The objective of "Hospital Management System" is to simply track the


knowledge of all the staffs, patients, treatment provided, doctors and the
medicines.
• The main objective of the Hospital Management System is to use the time taken
through manual system so as to take care of all the records.
• Hospital Management System is a software system that can store, update, and
retrieve the information through Databases.

2. Requirement Analysis :-

2.1 Software Requirement


• NetBeans 8.2 IDE.
• Google Chrome.
• Xampp.

2.2 Hardware Requirement


• Computer.
• Windows 10.
• Power Supply.

3. Project Approach :-

3.1 Project Initiation

3.1.1 Planning

Project planning is a part of project management, which relates to the use of


schedules such as Gantt charts to plan and subsequently report progress
within the project environment.
Planning a project mainly consist of 3 steps :
1. Have a vision.
2. Make a timeline.
3. Build the team.
3.1.2 Resource Allocation

• Project Staff resources will be available when and as they will be


needed.
• Required hardware resources will be available when and as they will
be needed.
• Required customer resources will be available when and as they will
be required.
• Access to industry experts and specialized skills will occur as needed.

3.2 Project Execution

3.2.1 Designing

This part contains how the project will be designed. Mainly it is based upon
the requirements of the user, the programmer have to do as the client says.

What kind of things he need in the project, what kind of appearance he needs.

3.2.2 Implementation

Implementation contains all the coding part of the project. If it’s a large
project, a team is required to accomplish it otherwise a single person can also
complete the project according to the need of client.

3.2.3 Testing

This phase contains the testing of the project before handling it to the client.
All the aspects of the project are check, whether the project is working fine or
there is any error, if any then it can be removed before handling the project to
the client.

3.3 Project Deployment

• Deliverables will be subject to no more then a specific numbers of review


cycles.
• Software and equipment order lead times are known and can be expected to be
met.
3.3.1 Installation

Installation contains all the steps like the installation of all the needs of the
software as required by the project. We have to provide everything to the user
even the software and also teach them how to use the project and what to
enter where.

3.3.2 Documentation

Documentation contains all the documents of the project, how to use it, what
are the software and hardware requirements to run the project. Even the
introduction to project and the build team.

3.3.3 Training

In this the client is trained on how to use the project and what to enter where.

4. Maintenance :-

4.1 Updates

We will provide all the updates for the project to fix all the issues and bugs etc.
All the new things will be added to the product with the update.

The update can be optional as well as mandatory. The Updates will contain all the
new things added to product and fix any problem.

4.2 Fixing Bugs

In this the bugs in the project are fixed, they can either be fixed with update or either
with the help of any software developer.

Mainly the updates fix all the bugs, because they are released to fix all the bugs and
problems of the product.
5. Rules And Responsibility :-

Name Role and Position Contact info.

Sudhanshu Gupta Software Developer [email protected]

Sahil Rana Programmer [email protected]

6. Cost Estimate :-

• The statistics used in preparing the estimates are accurate within a given percent.

• Outsourced consulting will be limited to a specified number of days at a specified


rate per day.

• The cost estimate will depend upon the work of project and the staff.

7. Project Constraints :-

The project should have been modified a bit more, like all details should be shown
somewhere about the doctors, patients and other details.
The details of the doctor should be displayed on the screen when diagnosing the patient.

The overall project got so many constraints that need to be solved.

You might also like