Clearing House

Index
Problem Statement Software Requirements Specification
1. Introduction 7 8 9

1.1 Purpose 1.2 Document Conventions 1.3 Intended audience and Reading suggestions 1.4 Project Scope 1.5 References 1.6 Definitions and Acronyms 2. Overall Description of proposed system 2.1 Product Perspective 2.2 Product Features 2.3User Characteristics 2.4 Design and Implementation constraints 2.5 Operating Environment 2.6 User Documentation 3. Functional Requirements 4. Other Non-functional requirements 4.1 Usability 4.2 Reliability 4.3 Supportability 4.4 Performance Requirements 4.5 Security requirements 4.6 Software Quality Attributes 5. Interfaces
1

9 9 9 9 9 10 11 11 11 11 11 12 12 13 15 15 15 15 15 15

ANITS-CSE

Clearing House

5.1 User Interfaces 5.2 Hardware Interfaces 5.3 Software Interfaces 6. Use case model 6.1 Identifying Actors 6.2 Identifying Use cases

16 16 16 17 18 18

Analysis Document
7. Sequence Diagrams 8. Collaboration Diagrams 9. State Chart Diagram

21 22 42 46 48 49 55 74 78 79 84 91

System Design Document
10. Class Diagram 11. Database Design 12. Component Diagram 13. Deployment Diagram

Screen Shots Test Cases

Conclusion
Appendix A: Glossary

91 91

Bibliography

2

ANITS-CSE

Clearing House

Problem Statement
The main aim of this project is to automate the process of identification of Insurance to the In/out patients who are treated by the hospitals and to develop convenient user interface using the DBMS and User Interface design tools so that atomicity, durability of the system is achieved when compared to the file management systems. The Project deals with identification of Insurance to the in/out patients who are treated by the hospitals. The System identifies the patient, the insurance details and the responsible party. The responsible party is the person who admits the patient. The patient details are collected and stored. The Insured party deals with the details of the insurance. Multiple insurances are also associated. Ailment deals with the illness details of the patient. It also keeps track of the attorney and organization details. The hospital also keeps track of facility and client details. The various payment codes, type of service and place of service are also kept track of. The information is then sent to the insurance companies for collection of expenditure met by the hospital for the treatment of the patient. None of the patient pays to the hospital for treatment. Instead of the payment by the patient his insurer is identified and the bills submitted to collect the payment.

3

ANITS-CSE

Clearing House Software Requirement specification Introduction Overall Description of proposed system System features Other Non-functional requirements Interfaces Use case model 4 ANITS-CSE .

3 Intended Audience and Reading Suggestions This document is intended and suggested reading for the developer and project managers who may add new features to the proposed project. Marketing staff who markets the project need to know the features of the project to market it. The claim is then referred to the insurance company who then verify the claim before releasing the payment. 4. undergoes the treatment without making any direct payments . Regular paragraph writing in font size 12 1.The public identifies a hospitals/clinics for treatment.Clearing House 1. Main headings with font size 26 in bold with underline.2 1. Sub headings with font size 16.4 Project Scope The intended purpose of this product is to book tickets for the customers both online by providing a convenient user interface. 3. The benefits obtained from the project are that the convenient user interface online and ease of ticket booking online attracts more number of customers to book ticket online and reduces the queues and the inconvenience caused to the customers due to the long queues at the railway station gets reduced.Instead they surrender the policy that would make up the cost of the treatment. Document Conventions The topographical conventions followed in the document are: Font used is Times New Roman. 1. The hospitals in turn perform the business logic that would compute the payments to be claimed based on the treatment to the patient. 1. those who actually uses of the product. different database designers designing the interfacing databases to the have to go through this document.5 References 5 ANITS-CSE . The project users or the customers. 1.1 Introduction Purpose The system deals with bridging the public who are treated by hospitals /clinics where they are treated and the insurance companies who will bare the cost of the treatment . 2. testers those who test the product. 1.

Clearing House The references used in designing this project are studying the way the hospital manages the data manually. 1. 3.2 Product Features The hospital keeps track of facility and client details. He must have knowledge in medical field. ID: Identification 2. The hospital maintains information about all patients as this helps them to meet history requirements later when required. type of service and place of service are also kept track of. None of the patient pays to the hospital for treatment. According to the role of the users of the database are classified as 6 ANITS-CSE . He must have basic knowledge of English too. 1.3 User Classes and Characteristics Every User should be: 1. All information about the physician and reference physician are stored in the databases. and studying the various insurance policies available their characteristics. This helps them understand the links of references and treatment made. HTML: Hypertext Markup Language 2. Whenever a new company is identified it is added to the existing list of companies. The various payment codes. The hospital also stores information about all the insurance companies identifying them and related details.1 Overall Description of Proposed System Product Perspective Earlier maintenance systems demanded high amount of time for managing the information as the data in the fields increased. 2. Comfortable of working with the computer. Data updating was a tough task and retrieval also had the same effect. The origin of the product is to address all kinds of drawbacks or problems that are being encountered in the latter maintenance systems.6 Definitions and Acronyms Some of the following are the acronyms used in this project. 2. The data is supported with backup and recovery options. The information is then sent to the insurance companies for collection of expenditure met by the hospital for the treatment of the patient. 2. The hospital also maintains information about physicians and reference physicians. Various reports are generated later to the requirement of the end user. Instead of the payment by the patient his insurer is identified and the bills submitted to collect the payment. 2.

Clearing House 1. Processor --. Each doctor is given a unique id and we have to record the reference physicians for every patient. win-XP or any other higher versions : Backend--. Receptionist: The receptionist is the one who is responsible for maintaining the overall system in the hospital. Login and Password is used for identification of user and there is no facility for guest. It comprises of vital information regarding the distribution of the access. Others: the personnel at the diagnostic center. If the patient has aarogyasri card then we need to record the details of the policy. the E-R diagrams used in construction. Some other restrictions are 1. The developer cannot provide a uniform access to all the user groups to maintain a friendly environment As a primary measure they restrict the access to particular group to reduce the illegal access and security intrusion.5 Design and Implementation Constraints Certain issues limit the options available to the developers. If patient doesn’t have an aarogyasri card then the patient pays the bill directly to the hospital 7 ANITS-CSE . Due to the vast advantages the back end is maintained by the Oracle10g. medical store can also interact with the system to update to the user details 2. Doctor: The doctor is responsible for maintain his patient details in the database. 2.Pentium II and above or its equivalent. : 256 MB and above Main Memory Hard disk Capacity .40GB or more. 2. 3. 1. 2. All the expenditures for the patient will be logged to the database.Oracle10g. Operating System Software Requirements Hardware Platform : Win98. key constraints and the general interface module prototypes. the mappings.e. 2. Each patient is given a unique id pid. GUI is in English only 2. 4. 5. backend information i. 3.6 User Documentation A complete user manual is provided with the end product to troubleshoot any problems that occur during the lifecycle of the tool. Functional Requirements The maintenance of the in/out patients and to automate the process of insurance clearance the following functional requirements have been identified.4 Operating Environment Front end of the application is developed using the Java Servlets.

4.5 Security Requirements Secure access of confidential data (user’s details) and constrained access of information to the regular NetUsers who can only book tickets. A druggist can supply the medicines to the patient and can update the medicines cost into the patient account details.3 Supportability Supportability is our ability to provide cost effective technical support. Each and every schema is normalized to the maximum normal form that can be attained to get better performance and low redundancy. Difficulty depends on the number of steps. 4. Each Receptionist is given a unique id rid. 10. 7. Only database administrator has the total access to the system and requires authentication by the system. Each Technician is given a unique id tid.4 Performance Requirements There is a better component design to get better performance at peak time. the knowledge that the user must have at each step. and the mechanics of each step. the decisions that the user must make at each step. 8.2 Reliability The product’s automatic upgrade feature will help us easily deploy defect fixes to the end-users. 12. 11.1 Other Nonfunctional Requirements Usability Our main criteria for making the system usable is the difficulty of performing each high frequency use case. 4. 13. A Receptionist can maintain details about the patient and account details about the patient. A technician can perform tests to the patients and he can update the diagnosis cost into the patient account details.Clearing House 6. 4. 8 ANITS-CSE . A Receptionist can also check whether the patient has paid the bill or not. Each Druggist is given a unique id dgid. The user guide and product website will include troubleshooting guide and checklist of information to have at hand before contacting technical support. 4. 4. 9. If the patient had an aarogyasri card then the hospital claims for the insurance on behalf of the respective patient. The user interface should be as familiar as possible to users who have used other web applications and Windows desktop applications.

The keyboard will input data into the active area of the database. Mouse – the software shall interact with the movement of the mouse and the mouse buttons. 5. The project offers different menus to the user to select from the given options. The mouse shall activate areas for data input.2 Hardware Interfaces Monitor screen – the software shall display information to the user via the monitor screen.1 Interfaces User Interfaces The project provides GUI forms to the users for easy understanding and application. 6.Clearing House 4. a pattern of behavior the system exhibits 2. Use cases focus on the behavior of the system from an external point of view. a use case can be described as a specific way of using the system from a user’s (actor’s) perspective. Use cases describe the 1. delivering something of value to the actor Use cases provide a means to 9 ANITS-CSE . command buttons and select options from menus. 5.6 Software Quality Attributes The project is designed based on a flexible service based architecture which will be helpful for future extension 5. a sequence of related transactions performed by an actor and the system 3. Use case Model Use cases are used during the requirements elicitation and analysis to represent functionality of the system. 5.3 Software Interfaces Windows is the operating system employed in this project as a software interface. In its simplest form. Keyboard – the software shall interact with the keystrokes of the keyboard. The screens are designed in JAVA.

classes or interfaces. test the system Use cases are best discovered by examining the actors and defining what the actor will be able to do with the system. Subclass Superclass 3. If two objects are usually considered independently. Generalization Relationship A generalize relationship is a relationship between a more general class or use case and a more specific class or use case. capture system requirements 2. The tip or a generalization is a large hollow triangle pointing to the more general element. the relationship is an association 2. Extend Relationship An extend relationship is a stereotyped relationship that specifies how the functionality of one use case can be inserted into the functionality of another use case. Since all the needs of a system typically cannot be covered in one use case. Extend relationships between use cases are modeled as dependencies by using the Extend stereotype. Together this use case collection specifies all the ways of using the system. In a use case diagram there can be two kinds of relationships 1.Clearing House 1. The communication can be between use cases. actors. communicate with the end users and domain experts 3. it is usual to have a collection of use cases. Associations are the most general of all relationships and consequentially the most semantically weak. 10 ANITS-CSE . Association Relationship An association provides a pathway for communication. A generalization is shown as a solid-line path from the more specific element to a more general element.

Druggist: He is the one who gives medicines to the patient prescribed by the doctor and passes the bill to the receptionist. Doctor: He is the one who prescribes medicines and suggests test to the patient. 5. Rational Rose allows you to place crop marks on printed diagrams. register: In this the user is provided to get registered on the system in order to become a legitimate user and access the services provided by the system.Clearing House Extend relationships are important because they show optional functionality or system behavior. Druggist_Login: Login for druggist in order to give medicines to the patient. 11 ANITS-CSE . For example. Receptionist_Login: Login for receptionist in order to view the patient details. 3. An include relationship specifies how behavior in the inclusion use case is used by the base use case. Receptionist: He is the one who maintains the details of the patient. Include relationships are important because they represent that the inclusion use case functionality is used by the base use case. He also need to get registered with a valid user-ID and Password to login into his account. Technician: He is the one who performs the required tests to the patient and passes the bill to the receptionist. Technician_Login: Login for technician in order to perform test to the patient. Doctor_Login: Login for doctor in order to treat the patient. Include Relationship An include relationship is a stereotyped relationship that connects a base use case to an inclusion use case. 3.1 Identifying Actors 1. 2. 6. 4. 4.2 Identifying Usecases 1. In order to get registered a user has to provide the details necessary for the registration as asked by the system. 6. 2. 4. In order to do that he need to get registered with a valid user-ID and Password to login into his account.

A user can anonymously check his PNR status by providing the PNR number in the column provided. 9. requests by passenger: A passenger traveling by can make the following requests to the Netuser a) requestForReservation b) requestForCancellation c) requestForEnquiry 12 ANITS-CSE . 7. 11. enquiry: A user can perform the following enquiries on the system. a) Availability Enquiry: Enquiring regarding the availability of berths in a particular train. 8. 10.Clearing House 6. delete account: A user can delete his account if he wishes to. check PNR status: This functionality is the only operation provided to the anonymous users. destination and source directly to get the cost of travel. of the ticket and his account number to which the cancellation amount is to be credited. cancellation: A user can cancel a ticket booked by him on the website by providing the PNR No. bookTicket: A user can book ticket online by providing his credit card number.. b) Cost Enquiry: User can provide the train no.

Clearing House <<include>> login Verify Create patient acoount Receptionist Delete patient account Delete Patient acc details Update Add View <<include>> Login_doctor Verify_doctor Patient Details <<include>> Doctor Prescribe Medicines <<include>> Suggests Tests Update Patient acc details Use Case Diagram for Receptionist and Doctor 13 ANITS-CSE .

Clearing House <<include>> Login_druggist verify_druggist <<include>> Druggist Deliver medicines View Patient Prescription Update Patient Acc Details <<include> Login _Tech <<include>. Technician Peform Tests View Patient Prescription_d Verify_tech Update patient acc Details Use Case Diagram for Druggist and Technician 14 ANITS-CSE .

Clearing House Analysis Document Sequence Diagrams Collaboration Diagrams State Chart Diagram 15 ANITS-CSE .

the modeler should keep in mind that interactions between actors and the system are of a different nature than interactions among objects. Each column represents an object that participates in the interaction. Messages are shown by solid arrows. When describing all possible interactions. these actors are represented on the right hand side and can receive messages. Repetitive invocation of a message is denoted by a “*” before the message name. Although for simplicity. Activations are depicted by the vertical rectangles. Labels on solid arrows represent message names and may contain arguments.Clearing House 7. sequence diagrams also provide notations for conditionals and iterations. Sequence Diagrams Sequence diagrams represent the objects participating in the interaction horizontally and time vertically. If the expression is true the message is sent. These diagrams can be used to describe either an abstract sequence or concrete sequences. If other actors communicate with the system during the use case. A condition on a message is denoted by an expression in brackets before the message name. interactions among objects and actors are uniformly represented as messages. The actor who initiates the interaction is shown in the use case diagrams. 16 ANITS-CSE .

1 Create Patient Account: C reate P atien A t ccou t n :P atien t :R eception ist :S stem y 1: Approach es 2: O s page pen 3: En n e.Clearing House 7.psw ter am d 4: R am _n e.**** 5: Validates 6: Loginsu ccessfu l 7: O s P pen atien details form t 8: D isplay form s 9: A sks details 10: G es details iv 11: Fills form 12: V erifies an u d pdates 13: D isplay P s atien acc form t 14: G es form iv 17 ANITS-CSE .

Clearing House 7. Delete Patient Account: :Patient :Receptionist 1: Approaches 2: Opens page 3: Enter name.**** :System 5: Verifies 6: Login successful 7: Opens patient form 8: Displays form 9: Asks patient id 10: P_id 11: Delete patient account 12: VerifiesPatient acct details 13: Successfully deleted 18 ANITS-CSE .2.pswd 4: R_name.

Doctor: :patient :doctor :system 1: patient approaches doctor 2: asks for id 3: gives id 4: logins 5: login successful 6: enter patient id 7: enters patient id 8: shows patient account 9: prescribes medicines 10: updated medicines 11: tells how to use medicines 19 ANITS-CSE .3.Clearing House 7.

4.Clearing House 7. Druggist: :patient 1: patient approaches druggist :druggist :system 2: asks for id 3: gives id 4: logins 5: login successful 6: enter patient id 7: enters patient id 8: shows patient account 9: show medicines 10: shows medicines 11: gives medicines 12: update account 13: updated 20 ANITS-CSE .

Clearing House :patient 1: patient approaches druggist :druggist :system 2: asks for id 3: gives id 4: logins 5: login successful 6: enter patient id 7: enters patient id 8: shows patient account 9: show medicines 10: shows medicines 11: gives medicines 12: update account 13: updated 21 ANITS-CSE .

5 Technician: :patient :technician :system 1: patient approaches technician 2: asks for id 3: gives id 4: logins 5: login successful 6: enter patient id 7: enters patient id 8: shows patient account 9: views tests 10: perform tests 11: updates account 12: updated 22 ANITS-CSE .Clearing House 7.

functionality and behavior of individual objects as well as the overall operation of the system in real time. :system 23 ANITS-CSE . Objects are shown as rectangles with naming labels inside.password 5: opens new patient's form 8: enters patient details :receptio nist 4: login successful 10: gives id no. These labels are preceded by colons and may be underlined.1 Doctor: 1: patient approaches doctor 3: gives id :patient 2: asks for id 11: tells how to use medicines :doctor 5: login successful 6: enter patient id 8: shows patient account 10: updated medicines 4: logins 7: enters patient id 9: prescribes medicines :system 8. As the number of objects and messages grow. They are best suited to the portrayal of simple interactions among relatively small numbers of objects.Clearing House 8. Collaboration Diagrams A collaboration diagram also called a commutation diagram is an illustration of the relationships and interactions among software objects in the unified modeling language (UML). This concept although more than a decade old.2 Receptonist: 3: verifies 9: verifies and upates 1: approaches 7: gives details :patient 6: asks details 11: gives id no 2: enters username. A collaboration diagram resembles a flowchart that portrays the roles. 8. has been refined as a model paradigm and evolved. The relationships between the objects are shown as arrows connecting the relevant rectangles along with labels that define message sequencing. a collaboration diagram can become difficult to read.

3 Druggist: 4: logins 7: enters patient id 9: show medicines 12: update account :system 1: patient approaches druggist 3: gives id :druggist :patient 2: asks for id 11: gives medicines 5: login successful 6: enter patient id 8: shows patient account 10: shows medicines 13: updated 8.Clearing House 8.4Technician: 4: logins 7: enters patient id 9: views tests 11: updates account :system 5: login successful 6: enter patient id 8: shows patient account 12: updated 1: patient approaches technician 3: gives id :patient :technici an 2: asks for id 10: perform tests 24 ANITS-CSE .

the text after the '/' which defines the objects response to the transition between states.oblong boxes which indicate the stable states of the object between events 2. Actions .a Boolean statement in square brackets which qualifies the event 5. State chart diagrams represent the behavior of entities capable of dynamic behavior by specifying its response to the receipt of event in stances. as opposed to sequence and collaboration diagrams which are a use casecentric view of functionality.1 Create account take details creates account gives id 25 ANITS-CSE . show for a class. Purpose • • • • To model dynamic aspect of a system. To model life time of a reactive system. They are a class-centric view of system functionality. 4. State charts. Components of State Chart Diagrams 1.the solid arrows which show possible changes of state 3. Extra syntax which defines state centric functionality. To define a state machine to model states of an object. Describe different states of an object during its life time. States . the order in which incoming calls to operations normally occur and the conditions under which the operations respond and the response. State Chart Diagrams A state chart diagram is a graph that represents a state machine. Transitions .Clearing House 9. Events .the text on the transitions before the '/' showing the incoming call to the object interface which causes the change of state. 9. 6. Conditions . often used more in real-time embedded systems than in information systems.

Clearing House

9.2 View details
opens form selects option views details closes form

9.3 Update details
opens form selects option updates details closes form

9.4 Delete account
opens form selects option deletes account close

9.5 Update medicine details
opens form collects money updates details close

9.6 Doctor views patient details
a k id ss ta e id ks oes pn ac ut con s le ts e c o tio p n

c ss lo e ac ut con

v w ie s d ta e ils

9.7 Doctor suggests medicines
asks id takes id opens account selects option

closes account

suggests medi...

26

ANITS-CSE

Clearing House

9.7 Doctor suggests medicines
asks id takes id opens account selects option BM

closes account

9.8 Druggist supplies medicines
asks id takes id opens account selects option view medicinesrequired

closes account

gives medicines required

9.9 Technician performs tests
asks id takes id opens account closes account selects option updates account views tests to be done performs tests

27

ANITS-CSE

Clearing House

System Design Document
Class Diagram Database Design Activity Diagram Component Diagram Deployment Diagram

28

ANITS-CSE

Inheritance A very important concept in object-oriented design. Classes are abstractions that specify the attributes and behavior of set of objects. and then add new functionality of its own. inheritance. At either end of the line. When attributes types are not essential to the definition of the system. a solid line is drawn from the child class (the class inheriting the behavior) with a closed arrowhead (or triangle) pointing to the super class. Each object is distinguishable from others. refers to the ability of one class (child class) to inherit the identical functionality of another class (super class). A bi-directional association is indicated by a solid line between the two classes. By convention. attribute type decisions can be delayed until object design. class name starts with uppercase letter and object name starts with lowercase letter. The type of an attribute is used to specify the valid range of the values the attribute can take. Class Diagram Class diagrams describe the structure of the system in terms of classes and objects. The centre compartment displays its attributes and the bottom compartment displays the functions performed by it. The top compartment displays the name of the class or object. Associations are assumed to be bidirectional -. Association There are 5 types of associations Bi-directional (standard) association An association is a linkage between two classes. we place a role same and a multiplicity value Unidirectional association 29 ANITS-CSE . Classes and objects are depicted by the boxes composed of three components.Clearing House 10. Objects are entities that encapsulate state and behavior. A class is a collection of objects that share a set of attributes that distinguish the objects as members of the collection.in other words. both classes are aware of their relationship and of the other class -unless you qualify the association as some other type of association. To model inheritance on a class diagram. The object names are underlined to indicate that they are instances.

Attributes: 1) did : string 2) dpassword : string 3) dusername : string Functions: 1) patientdetails() 2) prescrbemedicines() 3) suggesttests() 30 ANITS-CSE . there are times when you need to include another class because it includes valuable information about the relationship.Clearing House A unidirectional association shows that two classes are related. A unidirectional association is drawn as a solid line with an open arrowhead (not the closed arrowhead. Association class In modeling an association. Description of various classes present in the project: 1). Aggregation Aggregation is a special type of relationship used to model a "whole to its parts" relationship. Class Name: Doctor—can prescribe medicines and suggest tests. Composition aggregation The composition aggregation relationship is just another form of the aggregation relationship. An association class (also called a drop class by my former professor) is represented like a normal class. or triangle. used to indicate inheritance) pointing to the known class. the lifecycle of a part class is independent from the whole class's lifecycle. For this you would use an association class that you tie to the primary association. The difference is that the association line between the primary classes intersects a dotted line connected to the association class. but the child class's instance lifecycle is dependent in the parent class's instance lifecycle. In basic aggregation relationships. but only one class knows that the relationship exists.

Class Name: Techniciant—performs tests to the patient and passes bills to the receptionist. Class Name: Druggist—gives medicines to the patient and sends the bill to the receptionist. Class Name: Receptionist—maintains patient account details and patient details. Attributes: 1) dgid : string 2) dgpassword : string 3) dgusername : string Functions: 1) addpatientmedicinedetails() 2) updatepatientmedicinedetails() 3). Attributes: 1) rid : string 2) rpassword : string 3) rusername : string Functions: 1) patientdetails() 2) patientaccountdetails() 4). Attributes: 1) tid : string 2) tpassword : string 3) tusername : string Functions: 1) addpatientdiagnosisdetails() 2) updatepatientdiagnosisdetails() 31 ANITS-CSE .Clearing House 2).

Clearing House 10.1 Doctor: doctor name password login() operation operation name select operation() patient details patient name patient id select() prescribe medicians patient id medician name read() suggest tests patient id test name read() view patient id display() add patient id patient name add() delete patient id delete() update patient id update() 10.2 Druggist: 32 ANITS-CSE .

3 Receptionist: 33 ANITS-CSE .Clearing House druggist name password login() operation operation name select operation() add patient med details patient id patient name med name add() delete patient med details patient id med name delete() update patient id med name update() 10.

4 Technician: 34 ANITS-CSE .Clearing House receptionist name password login() operation operation names select operation() patient details pd operation name select pd() patient account details pad operation name select pad() add patient patient id patient name add() update patient id update() add patient patient id patient name add() update patient id update() View patient id display() delete patient patient id delete() view patient id display() delete patient patient id delete() 10.

Database Design 11. Entity-Relationship diagram is just an approximate description of the data. The E-R. constructed through a subjective evaluation of the information collected during requirement analysis.1 Entity-Relation Ship Model To start-off with the back end the essential structure that is to be considered is the ER diagram. 35 ANITS-CSE .Clearing House technician name password login() operation operation name select operation() add patient diag details patient id patient name diag name add() update patient diag details patient id diag name update() delete patient diag details patient id diag name delete() 11. The E-R diagram is constructed by the usage of the following symbols.

Doctor-id : Unique for given doctor. In order to do that he need to get registered with a valid user-ID and Password to login into his account. Doctor: He is the one who prescribes medicines and suggests test to the patient.Clearing House 11. 36 ANITS-CSE .2 Description of Entity sets 1.

: Gives the name of the patient. Druggist: He is the one who gives medicines to the patient prescribed by the doctor and passes the bill to the receptionist. It has the following attributes. He also needs to get registered with a valid user-ID and Password to login into his account. 5. Technician: : Unique for the given receptionist. : Personal identification for the given technician id. Technician-id T-Password Primary key is t-id.Clearing House D-Password: Personal identification for the given doctor id. Primary Key is d-id. Druggist-id Dg-Password Primary Key is dg-id. Patient details: It is an entity set which has the following attributes. : Gives the age of the patient. 37 ANITS-CSE . : Personal identification for the given druggist id. It has the following attributes. 3. : Unique for the given technician. Receptionist: He is the one who maintains the details of the patient. pid Pname Page : Unique number for patient. : Personal identification for the given receptionist id. Receptionist-id R-Password Primary key is r-id. 4. : Unique for given druggist. 2. He is the one who performs the required tests to the patient and passes the bill to the receptionist.

pid Mname Mnum Date1 : Unique number for patient. : Gives the total tests cost of the patient. : Tells about when the patient has joined in the hospital. : Gives the total cost of the patient. : Unique number for doctor. Patient medicines details: It is an entity set which has the following attributes. : Gives the total medicines cost of the patient. 38 ANITS-CSE . : Gives the number of medicines taken by the patient. Foreign key is pid. : Tells whether the patient has aarogyasri card or not. : Gives the phone number of the patient. Foreign keys are pid and did. Primary key is pid. 6. : Gives the name of the medicines. 8. pid did disease mcost hcost tcost Aarogyasri Paid : Unique number for patient.Clearing House Psex Paddress Pphoneno pdoj : Gives the sex of the patient. : Gives the address of the patient. Patient medicines details: It is an entity set which has the following attributes. 7. Patient account details: It has additional attributes. : Gives the name of the disease of the patient. : Tells about whether the patient has paid the bill or not. : Gives the date when the patient has taken the medicines.

: Gives the date when the patient has taken the tests. It is also a 1: N cardinality relationship having one receptionist and N number of patients. 6.Clearing House pid Dname Date2 : Unique number for patient. Prescibes_medicines is a relationship between the entities Doctor and patient medicine details. It is a 1: N cardinality relationship with one Druggist and multiple patient account details. 5. Foreign key is pid. It is a 1: N cardinality relationship with one Technician and multiple patient account details. Update_diagnosisdetails is a relationship between the entities Technician and the Patient account details. Update_medicinedetails is a relationship between the entities Druggist and the Patient account details. It is a 1: N cardinality relationship with one technician and multiple patient diagnosis details. 11. It is a 1: N cardinality relationship with one druggist and multiple patient medicine details. It is a 1: N cardinality relationship having one receptionist and may have N patient account details. Supplies_medicines is a relationship between the entities Druggist and the Patient medicine details. Performs_tests is a relationship between the entities Technician and the Patient diagnosis details. 4. 2. Holds_details is a relationship between Receptionist and patient details.3 Description of Relationship sets 1. It is 1: N cardinality relationship with one Doctor and many patient medicine details. 3. : Gives the name of the diagnosis. 7. 39 ANITS-CSE . 8. It is a 1: N cardinality relationship with one Doctor with many patient diagnosis details. Holds_acctdetails is a relationship between Receptionist and the Patient account details. Suggests_Tests is a relationship between the entities Doctor and Patient diagnosis details.

DGPASSWORD) 3. DCOST. PAGE.DGUSERNAME. RECEPTIONIST (RID.4 Final List of Tables 1. DNAME. DRUGGIST (DGID. DOCTOR (DID. PATIENTMEDICINEDETAILS(PID. PDOJ) 4. MNUM. RPASSWORD). AROGYASRI. PATIENTDIAGNOSISDETAILS (PID. DISEASE. PATIENTACCOUNTDETAILS (PID.DUSERNAME.DPASSWORD ) 2. MNAME.HCOST. RUSERNAME. TCOST.Clearing House ER Diagram for Clearing House 11. PADDRESS. 5. DATE2) 7. PNAME. MCOST. PSEX.DATE1) 40 ANITS-CSE . DID. PAID) 6. PPHONENO. PATIENTDETAILS (PID.

No FIELD NAME DATA TYPE Not Null constraint REMARKS 5 1 RID Number Not Null Used to identify the receptionist Gives the name of the receptionist Gives the password of the receptionist 2 Rusername Varchar2 10 Not Null 3 Rpassword Varchar2 10 Not Null 3. Receptionist: MEMORY ALLOCATION RANGE S. Druggist: 41 ANITS-CSE .Clearing House 11. Doctor: S.No FIELD NAME DATA TYPE MEMORY ALLOCATION RANGE Not Null constraint REMARKS 5 1 DID Number Not Null Used to identify the doctor Gives the name of the doctor Gives the password of the doctor 2 Dusername Varchar2 10 Not Null 3 DPassword Varchar2 10 Not Null 2.5 Prototype Tables 1.

Patient details: 42 ANITS-CSE .No FIELD NAME DATA TYPE MEMORY ALLOCATION RANGE Not Null constraint REMARKS 5 1 DGID Number Not Null Used to identify the druggist Gives the name of the druggist Gives the password of the druggist 2 Dgusername Varchar2 10 Not Null 3 DGpassword Varchar2 10 Not Null 4.Clearing House S.No FIELD NAME DATA TYPE Not Null constraint REMARKS 5 1 TID Number Not Null Used to identify the technician Gives the name of the technician Gives the password of the technician 2 Tusername Varchar2 10 Not Null 3 Tpassword Varchar2 10 Not Null 5. Technician: MEMORY ALLOCATION RANGE S.

Patient account details: MEMORY ALLOCATION RANGE S.Clearing House S. psex Paddress Pphoneno Pdoj Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Date 10 2 20 20 10 Not Null Not Null Not Null Gives the phone number of the patient Gives the date of when the patient has joined in the hospital 6. 7.No FIELD NAME DATA TYPE Not Null constraint REMARKS 1 PID Number 5 Not Null Used to identify the patient Used to identify the doctor Gives the name of the disease 2 3 DID Disease Number Varchar2 5 22 Not Null 43 ANITS-CSE .No FIELD NAME DATA TYPE MEMORY ALLOCATION RANGE Not Null constraint REMARKS 1 PID Number 5 Not Null Used to identify the patient Gives the name of the patient Gives the age of the patient Gives the sex of the patient Gives the address of the patient 2 3 4 5 6. Pname Page.

No Patient diagnosis details: FIELD NAME DATA TYPE MEMORY ALLOCATION 44 Not Null REMARKS ANITS-CSE .No Patient medicine details: FIELD NAME DATA TYPE MEMORY ALLOCATION RANGE Not Null constraint REMARKS 1 PID Number 5 Not Null Used to identify the patient Gives the names of the medicines Gives the number of medicines taken by the patient Gives the date of medicine purchased 2 Mname Varchar2 5 3 Mnum Varchar2 10 4 Date1 Date 8. Paid Varchar2 5 7.Clearing House 4 5 6 7 8. S. S. Mcost Dcost Hcost Tcost Aarogyasri Number Number Number Number Varchar2 5 5 5 5 5 Gives the medicines cost Gives the diagnosis cost Gives the hospital cost Gives the total cost Specifies whether the patient has aarogyasri card or not Specifies whether the patent had paid the bill or not 9.

And the ending of the diagram with an activity final node is on the bottom or on the right. Activity building blocks. In 45 ANITS-CSE . but it is questionable if these diagrams should be called activity diagram. and. with support for choice. activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. consisting of: • • Nodes . and Sometimes activity diagrams also contain building block for decision-making. Components of Activity Diagrams Activity diagrams are constructed with a limited set of building blocks. The starting point of the diagram is the initial node. Activity Diagram Activity diagrams are diagram technique showing workflows of stepwise activities and actions. describing a complicated sequential algorithm. Activity diagrams should be used in conjunction with other modeling techniques such as interaction diagrams and state diagrams The main reason to use activity diagrams is to model the workflow behind the system being designed.Clearing House RANGE constraint Used to identify the patient Gives the names of the diagnosis Gives the date of diagnosis conducted 1 PID Number 5 Not Null 2 Dname Varchar2 5 3 Date2 Date 12.like initial node and activity final node. In the UML. Activity Diagrams are also useful for: analyzing a use case by describing what actions needs to take place and when they should occur. iteration and concurrency. which is mostly located on top or on the left. An activity diagram shows the overall flow of control. and modeling applications with parallel processes.

one or more activity building blocks. Doctor: 46 ANITS-CSE . 12.4.Clearing House between there can be zero. which can be represented by rounded rectangles.

* * * id * * v lid a n o ys e p d p id e te p n r id aa b v ila le n o ys e d p y is la s d ta e ils e tes n r e te n r m d in s e ic e u d te pa d s g e ts ug s s g e t te t ugs s u d te in pa d d ta a e a bs o ea n p r tio c m le d o p te 12. Druggist: 47 ANITS-CSE .Clearing House dc r o to ss m y te dt bs aa a e s r ss m tat y te e te n r n m .p s w rd a e as o o e hm pn o e pg ae d .4.

Clearing House druggist system database start system openhome page enter name.3. Technician: 48 ANITS-CSE .**** no yes pid enter patient id available no yes view patient medicines update patient acc.details updated operation completed 12.password valid dgid.

**** no yes pid enter patient id available no yes view patient tests update patient acc.details updated operation completed 12. Receptionist: 49 ANITS-CSE .password valid tid.4.Clearing House technician system database start system openhome page enter name.

passw ord valid operation s yes n o p_id en p_id ter no available display pid enters enter patient details yes u pdate database pid en pid ter yes delete patient U pdate database P_id Enter p_id avail n o n o u pdate details yes avail uPdate database P_ id enterp_id n o displayPAD Avail yes operation com pleted 50 ANITS-CSE .Clearing House receptionist sy stem data base N Acstart ew the sy stem open h e om page enter nam e and passw ord r_id.

The interface of a component is represented by one or several interface elements that the component provides. and executable components. DLL. A component diagram shows the organizations and dependencies among software components. binary code components. An interface typically specifies only a limited part of the behavior of a class or component. or major pieces of your system. Component packages parallel the role played by logical packages for class diagrams. including source code components.) with a well-defined interface. Components are used to show compiler and runtime dependencies. but they can occur both in class diagrams and in component diagrams Component diagrams contains · · · · Component packages Components Interfaces Dependency relationships Component packages represent clusters of logically related components. They also show which components implement a specific class. etc. as well as interface and calling dependencies among software modules. Component Diagram Component diagrams provide a physical view of the current model. To distinguish different kinds of components from each other. Note that the interfaces actually belong to the logical view. executable. A system may be composed of several software modules of different kinds. They allow you to partition the physical model of the system. 51 ANITS-CSE . A Component represents a software module (source code. Each software module is represented by a component in the model. Calling dependencies among components are shown as dependency relationships between components and interfaces on other components. These diagrams also show the externally-visible behavior of the components by displaying the interfaces of the components.Clearing House 13. stereotypes are used. and has no implementation of its own. An interface specifies the externally-visible operations of a class and/or component. binary code.

a dependency relationship indicates that the operations of the client invoke operations of the supplier. on class diagrams. System database Doctor Technician Patientdetails Receptionist Add patient diagnosis details Update patient diagnosis details Prescribe medicines Suggest tests Patient account details Patient details Druggist Add patient medicine details Update patient medicine details Component Diagram for Clearing House 52 ANITS-CSE .Clearing House A Dependency is a relationship between two model elements in which a change to one model element will affect the other model element. Typically. Use a dependency relationship to connect model elements with the same level of meaning.

Deployment diagrams show "the allocation of Artifacts to Nodes according to the Deployments defined between them.Clearing House 14. Deployment Diagram A deployment diagram in the Unified Modeling Language serves to model the physical deployment of artifacts on deployment targets. For example. Printer mouse keyboard System Deployment Diagram for Clearing House 53 ANITS-CSE ." Deployment of an artifact to a node is indicated by placing the artifact inside the node. Instances of nodes (and devices and execution environments) are used in deployment diagrams to indicate multiplicity of these nodes. multiple instances of an application server execution environment may be deployed inside a single device node to represent application server clustering.

Clearing House Screen Shots Homepage 54 ANITS-CSE .

Clearing House Creating a New patient 55 ANITS-CSE .

Clearing House Login Page for Doctor 56 ANITS-CSE .

Clearing House Viewing Prescribed Medicines 57 ANITS-CSE .

Clearing House Updating the Medicine Bill 58 ANITS-CSE .

Clearing House Updating the patient test bills 59 ANITS-CSE .

Clearing House 60 ANITS-CSE .

Clearing House Test Cases Definition: 61 ANITS-CSE .

A unit is smallest software component 3. Ensures that system meets all functional and business requirements. This allows the developer to detect failures in the system before it is released to the customer. Description: It is a fault detection technique that tries to create failures or erroneous states in a planned way. 2. Performed by programmer and units are tested in isolation. stress. 8. It is done using the integration test design prepared during the architecture design. System testing is an expensive process but it is required in order to achieve a complete system. The system test design is derived from the system design documents and is used in this phase. 7. the most micro scale of testing. 2. Generally the users tend to think that the process of providing that there do not exist. 5. Focus on verifying that specifications are met 3. Objects and methods 4. Testing of more than one (tested) unit together to determine if they function correctly. any errors in the system forms the testing part. ensuring the correct flow of data 5. 6. 4. To determine whether a system satisfies its acceptance criteria and business requirements or not. Procedures and functions 5. module testing Integration Testing: 1. Validating that the system can be used for the intended purpose 4. Also known as component. Types of Testing: Unit Testing: 1. 1. Also called Interface Testing or Assembly Testing. Focuses on interfaces of Communication between units 3. Sometimes testing is automated using testing tools one by Independent testing group Acceptance testing 1. covers all combined parts of a system.Clearing House Testing is the process of finding differences between the expected behavior specified by the system model and the observed behavior of the implemented system. It can involve a number of specialized types of tests to check performance. Done by developers/designers and testers in collaboration 6. Not to be confused with debugging. 62 ANITS-CSE . Ensure that system is working according build design. System Testing: Testing the system as a whole . documentation etc. 2. Helps assembling incrementally a whole system.Black-box type testing that is based on overall requirements specifications.

Module Name Test Case Input Output Name Module Test Case Input Output Module Name Test Case Input Output Login Doctor To log on to the doctors account Valid User name . Test Cases: A test case is a set of input data and expected results that exercises the component with the purpose of causing failures and detecting faults. Done by real business users.password A page showing the Trains available operations that doctor can perform Prescribe Medicines To prescribe Medicines for a patient Patient Id A Page asking the medicine name and quantity fo the medicine Suggest tests To suggest a test for the patient Patient Id A page asking the test name 63 ANITS-CSE . Similar to System testing in that the whole system is checked. but the important difference is the change in focus. Test cases are classified into black box test and white box test. Black box test focuses on input/output behavior of the component. 4. It enables the customer to determine whether to accept the system or not.Clearing House 2. 3. White box test focuses on the internal structure of the components.

arogya sri.Clearing House Module Name Test Case Input Create Patient To create a new patient account Patient Id.address.reference physician id number.phone no. card Output A page Showing that New patient account has been created 64 ANITS-CSE .age sex.complaint.name.

Clearing House Test Case for Login Doctor Module Result For above module 65 ANITS-CSE .

Clearing House Test Case for Prescribe Medicines Module 66 ANITS-CSE .

Clearing House Result for above module when Patient Id is valid Result for above module when Patient Id is invalid 67 ANITS-CSE .

Clearing House Test Case for Suggest tests Module 68 ANITS-CSE .

Clearing House Result for the above module when Patient Id is valid 69 ANITS-CSE .

Clearing House Result for the above module when Patient Id is invalid 70 ANITS-CSE .

Clearing House Test Case for Create Patient Module 71 ANITS-CSE .

Clearing House Test Case for Create Patient Module 72 ANITS-CSE .

Mc Graw Hill Edition. Allen H. 1. Ivar Jacobson. Actually. PNR is a travel record of a person or a group of persons in the database of Computer Reservation System (CRS). Passenger(s) Name Travel Agent's Contact Details Details of Ticket (could be a ticket number or ticketing time limit) Itinerary as a minimum of one segment that should be similar for all passengers listed. 4. Oracle 9i. Second Edition Bernd Bruegge. who makes the booking Bibliography 1. 5. Johannes Gerkhe. 4. The abbreviation PNR stands for Passenger Name Record. 3.Raghu Ramakrishnan. The Unified Modeling Language Reference Manual . Database Management Systems-Third Edition (IE) .Kevin Loney. PNR has five parts that are essential in order to get a booking done.Sudarshan. Patterns and Java. Dutoit. Person's Name.Clearing House Conclusion The project can be applied for any kind of Railway reservation systems with simple modifications and by interfacing with the Railway employee database and corresponding bank database which provide the net banking services by the use of credit cards. S.Navathe. Mc Graw Hill Edition. Database System concepts-Fifth Edition (IE) -Abraham Silberschatz. In practical terms. 6. O’Rielly 73 ANITS-CSE . Kathy Sierra and Bert Bates.Korth. Shamkanth B.James Rumbaugh. The Complete Reference – Oracle Press .Bryan Basham. Tata Mc Graw Hill Edition. 7. 2. The convenient user interface provided is easy to use and increases the scope of use of the railway network making it easy to access and book tickets. Pearson Education. Object Oriented Software Engineering Using UML. Pearson Education 3. The five parts or requisites of PNR number are as follows. Head First Java Servlets and JSP . 5.Addison Wesley 2. Grady Booch. George Koch. Fundamentals of Database Systems-Fifth Edition (IE) – Ramez Elamasri. Henry F. Appendix A: Glossary PNR is an important number that is written on the top left corner of a Rail Ticket.

Sign up to vote on this title
UsefulNot useful