Question

You are asked to develop a proposal for any product of your choice. Your proposal should contain the following steps. Project Development Proposal Part #1 A) Specification only Statement of Work & Requirements • Functional Requirements Spec & UI . Budget Team member selections and qualifications Part#2 B) Design only • Interaction Diagrams • Class Diagram, and System Architecture Part#3 C) Product Part #4 D) Conclusions

Answer 1

As per the given question, let us consider that we are going to create a proposal for the Restaurant. As in the restaurant all criteria are to be defined like its specification, about the budget and many more. So at the very first step we need to proceed as follows.

Project Name: Hospital Management Date: 26.04.2020

Objective: This section describes the Software Development Methodology being used by the Hospital team members, while executing their Software Projects / Applications. It further identifies the phases of the lifecycle, the entry and exit criteria of each phase and the quality control tasks related to each phase.

Scope: It is the next phase which is used to build the objective get fullfilled. here the team is allowed to follow a slightly modified version of the Waterfall model (to facilitate Rapid Application Development) in the Software Development projects.The phases of the scope is discussed as below.

Phases:

The execution phases is basically identified inn three stages such as,

1. start up

2. Execution, and

3. Windup.

Startup: The start up stages is used to provide the following specific points such as, Project Acquisition Estimation, Requirement Analysis, Project Management Planning, and Project QC Planning.

Execution stage: This is the next stage which defines the Design of the product, Development of the respective module,  and Integration Testing for the respective module.

Windup: This is the last stage which describe the User Acceptance and Sign-Off and Project Closure process.

The detailed phases start with the Abstract where we need to define the most basic mission , Vision and theme for the respective Hospital in details. We also need to provide the keyword also so that the reader can find proper text for him/her.

1.Software Requirement Specification

A Software requirements specification (SRS), a requirements specification for a software system, is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

1.1 Introduction

The following subsections of Software Requirement Specifications Document should facilitate in providing the entire overview of the Information system “Hospital Management System” under development. This document aims at defining the overall software requirements for admin. Efforts have been made to define the requirements of the Information system exhaustively and accurately.

         1.2 Purpose

The main purpose of Software Requirement Specifications Document is to describe in a precise manner all the capabilities that will be provided by the Software Application “Hospital Management System”. It also states the various constraints which the system will be abide to. This document further leads to clear vision of the software requirements, specifications and capabilities. These are to be exposed to the development, testing team and end users of the software.

1.3 Scope

The proposed software product is the Hospital Management System (HMS). The system will be used in any Hospital, Clinic, Dispensary or Pathology labs in any Hospital, Clinic, Dispensary or Pathology labs to get the information from the patients and then storing that data for future usage.

Functional Requirement and Requirements:

2. Hardware Interfaces

Processor: Pentium IV atleast

RAM: 512MB or above

Hard Disk: 40GB or above

Input Devices: Keyboard, Mouse

Output Devices: Monitor; -14” VGA

Software Interfaces

OPERATING SYSTEM: Windows XP

FRONT END: Microsoft Visual Basic 6.0

BACK END: Microsoft Access

Product Functions

The system will allow access only to authorized users with specific roles (Administrator, Operator). Depending upon the user’s role, he/she will be able to access only specific modules of the system.

A summary of the major functions that the software will perform:

i. A login facility for enabling only authorized access to the system.

ii. When a patient is admitted, the front-desk staff checks to see if the patient is already registered with the hospital. If he is, his/her Name is entered into the computer. Otherwise a new Patient ID is given to this patient.

iii. If a patient checks out, the administrative staff shall delete his patient ID from the system.

iv. The system generates reports on the following information: List of detailed information regarding the patient who has admitted in the hospital.

User Characteristics

1. Educational Level: At least graduate and should be comfortable with English language.

2. Technical Expertise: Should be a high or middle level employee of the organization comfortable with using

general purpose applications on a computer.

System Features

Login module

Description

This module records only user and password of the user.

Patient module

Description

It keeps track of all details about both in-patient and out-patient. Patient id, patient name, address,

admitted date, doctor name, and room no are entered in a form and stored for future reference. Also particular patient details can be viewed in the table using a separate form with an attribute patient id.

Inpatient module

Description

Admission request will be made here. Request for admission is made before patient admitting the hospital.

Outpatient module

Description

This module manages activities related to patient who visits the Hospital or Resident Doctor or Consultant Doctor for Medical Consultations, diagnosis and treatment.

• Pathology module

Description

This module Generates reports which will be done in pathology lab of the Hospital.

• Billing module

Description

This module bills the both inpatient and outpatient who comes to hospital. It also includes Payment details of patients. Depending on the payments bill report is generated.

3. Logical Database Requirements

The proposed information system contains the following data tables in its database collection.

i. Patient Details table

ii. Doctor Details Table

iii. Room Details Table

iv. Bill Details table

The E-R diagram for the basic Hospital Management is as showed below.

E-R Diagram of Hospital Management System Addressy Department Address ( Name Hieronta entre Age Pid Doctor Ph.No Treats M Patient Gender Gender Issued > 1 BILL NO. Assign Doc_Charges Bill Room Charges (Type Room (Room id

Conclusion:

It is the last sectio for any product which defines the strength and weakness about the product. Here it is basically implemented in three steps which are defined as Conclusion, Future Enhancement in the module and Limitations for the product.

The project Hospital Management System (HMS) is for computerizing the working in a hospital. It is a great improvement over the manual system. The computerization of the system has speed up the process. In the current system, the front office managing is very slow. The hospital managing system was thoroughly checked and tested with dummy data and thus is found to be very reliable. The software takes care of all the requirements of an average hospital and is capable to provide easy and effective storage of information related to patients that come up to the hospital.

It generates test reports and also provides the facility for searching the details of the patient. It also provides billing facility on the basis of patient’s status whether it is an indoor or outdoor patient. The system also provides the facility of backup as per the requirement.

FUTURE ENHANCEMENTS

1. The proposed system is Hospital Management System. We can enhance this system by including more facilities like pharmacy system for the stock details of medicines in the pharmacy.
2. Providing such features enable the users to include more comments into the system.

LIMITATIONS:

The size of the database increases day-by-day, increasing the load on the database back up and data maintenance activity.

Training for simple computer operations is necessary for the   users working on the system.