Practical no.1: SPMP document of “Hospital Management System”.

1. Purpose:

The purpose of this document is to specify the project plan to develop the
Hospital Management System. This document outlines a brief plan about
the project is to shaped and also include the milestones and deliverables.
Updates of this document will serve to record the progress of the project.

2. Introduction: “Hospital Management System”

a) Objective :

The objectives of the projects are as follow:

• Complete the project by project due date.

• Complete the project within the budget.

• Provide all deliverable feature by project due date.

• Fulfill all stated requirements as in the SRS of software project

deliverable.

b) Major function :

• Maintaining Patient details.

• Providing Prescription, Precautions and Diet advice.

• Providing and maintaining all kinds of tests for a patient.

• Billing and Report generation.

1 Amarpreet Kaur

80909107003
 c) Performance issues :

• No constraints on storage information of patients.

• The prescription of diet can be varying with the area or climate
changes or doctor advice.

d) Management and technical constraints

• GUI is only in English.

• Login and password is used for identification of doctors and there is
no facility for guest.

3. Project Estimation :

a) Historical data used:

Data used in this project is collected from the

• Study of various patients records.

• Internet.

• Interviewing the specialized doctors.

b) Estimation technique used: COCOMO model is used for organic.

c) Efforts resources ,cost and project duration estimation:

• Cost estimated is 50,000.

• Duration: 6 months.
• Extra resources can be availed on demand.

4. Scheduling :

a) Work breakdown structure:

2 Amarpreet Kaur

80909107003
 This project is dividing into various activities such as patient records,
diet chart, Providing Prescription and Precautions, Diet advice, Providing
and maintaining all kinds of tests for a patient, Billing and Report
generation.

b) Task network:

This shows the graphical relationship among the various activities.

c) Gantt charts
The main objective of a Gantt chart is to assess how long a project
should take and to establish the order in which tasks need to be carried
out by the ending of the project.

d) PERT charts

Generate PERT chart from Gantt chart.

5. Project resources:

a) People ,hardware ,software :

The hardware resource is a 2GHz Pentium computers running Windows

XP Operating System. Computer should have at least 512 MB RAM and
a minimum of 1 GB of disk space. This project adapts the system for use
on a Personal Computer using a Visual Interface that would be built
using ASP.NET, and Microsoft SQL as its database management system.

b) Special resources:

Based on the Demand

3 Amarpreet Kaur

80909107003
6. Staff organization:

a) Team Structure:

The medical staff is composed of licensed physicians and may include

other licensed professionals who are permitted to provide patient care
services in the hospital. The medical staff has the overall responsibility
for the quality of professional services provided to patients by those with
clinical privileges. So we prefer the team work in this type of project.

7. Risk management plan:

a) Risk analysis

b) Risk identification

c) Risk estimation

8. Project tracking and control plan

9. Miscellaneous plan

a) Project tailoring

b) Configuration management plan (CMP)

c) Quality assurance plan (QAP)

d) Validation and verification

e) System testing plan

f) Delivering installation and maintenance plan

4 Amarpreet Kaur

80909107003
Practical no.2: Familiarity with JSP and JSD.

JSP (Jackson Structured Programming) was the first software development that
Michael Jackson developed. It is a program design method and was described in
his book “Principles of Program Design”. JSP covers the design of individual
programs, but not systems.

JSP Method:

JSP uses semi-formal steps to capture the existing structure of a program’s inputs
and outputs in the structure of the program itself. The intend is to create programs
which was easy to modify over their lifetimes. Jackson’s major insight was that
requirement changes are usually minor tweaks to the existing structure. For a
program constructed using JSP, the inputs, the outputs and the internal structure of
the program all matched. So small changes to the inputs and outputs should
translate into small changes to the program.

JSP structures programs in terms of four component types:

• Fundamental operations
• Sequences
• Iterations
• Selections

JSP uses a diagramming notation to describe the structure of inputs, outputs and
programs, with diagram elements for each of the fundamental component types.

• A simple operation is drawn as a box.

An operation

5 Amarpreet Kaur

80909107003
• A sequence of operations is represented by boxes connected with lines. In the
example below, operation A consists of the sequence of operations B, C and D.

A Sequence

• Iteration is again represented with joined boxes. In addition the iterated

operation has a star in the top right corner of its box. In the example below,
operation A consist of an iteration of zero or more invocations of operation B.

Iteration

• Selection is similar to a sequence, but with a circle drawn in the top right hand
of each optional operation. In the example, operation A consists of one and
only one of operations B, C or D.

A selection

6 Amarpreet Kaur

80909107003
JSD (Jackson System Development) was the second software development method
that Michael Jackson developed. John Cameron was a major contributor to the
development of JSD.JSD is a system development method met just for individual
programs, but for entire systems.JSD is most readily applicable to information
system, but it can easily be extended to the development of real-time embedded
systems.JSD was described in his book System Development.

JSD Method

JSD: The Modeling Stage

In the modeling stage the developers make a description of the aspects of the
business or organization that the system will be concerned with. To make this
description they must analyze their business, choosing what is relevant and
ignoring what is not. They have to consider the organization as it will be, not as it
is now.

The result of the modeling stage is a set of tables, definitions and diagrams that
describe:

• In user terms exactly what happens in the organization and what has to be
recorded about what happens, and
• In the implementation terms, the contents of the database, the integrity
constraints and the update rules.

JSD: The Network Stage

In the network stage we build up a precise description of what the system has to
do, including the outputs that are to be produced and the way the system is to
appear to the user. This description is in terms of a network of programs. More
precisely, it is a network of Communicating Sequential Processes (CSP), a concept
developed by Tony Haoare.Start this network by making one program for each of
the entities that was defined during the modeling stage. The network is then built
up incrementally by adding new programs and connecting them up to the existing
network. New programs are added for the following reasons:

7 Amarpreet Kaur

80909107003
 • To collect inputs for actions, check them for errors, and pass them to the
entity programs. In this way entity programs are kept up-to-date with what’s
happening outside.
• To generate inputs for actions those do not correspond to external events.
Such actions are substitutes for real world events, perhaps because those
events cannot be detected.
• To calculate and produce outputs.

JSD: The Implementation Stage

The result of the implementation stage is the final system. This stage is the only
one directly concerned with the machine and the associated software on which the
system is to run.Therefore, as well as producing and testing code, the
implementation stage covers physical design issues. In particular it covers:

• Physical data design, and

• Reconfiguring the network by combining programs.

8 Amarpreet Kaur

80909107003