02-03-2013, 10:06 AM
SEDATIVE SLEUTHHAUND
[attachment=52367]
Objective:
Every hospital needs an online system whereby it can accommodate the patients comfortably and avoid any confusion to the doctors regarding their work. There should be a system where the patients are categorized under insurance policy and non policy holders and the system helps the hospital management to claim the bills from concerned insurance companies. All these needs and much more are fulfilled in SedativeSleuthhaund. SedativeSleuthhaund is useful to record patient’s details along with the compliant. It also records the inpatient details and outpatient details and arranges the appointment of doctors. SedativeSleuthhaund also provides the management reports like schedules, appointments of doctors, inpatients, insurances and discharges. And also used to generate bills dynamically for the discharged patients etc.
Existing System:
The following are the disadvantages of current system
1. It is difficult to maintain important information in books
2. More manual hours need to generate required reports
3. It is tedious to manage historical data which needs much space to keep all the previous years ledgers, books etc
4. Daily admissions of patients are to be entering into different books
immediately to avoid conflicts which are very difficult.
Proposed System:
Proposed system is a software application which avoids more manual hours that need to spend in record keeping and generating reports. This application keeps the data in a centralized way which is available to all the users simultaneously. It is very easy to manage historical data in database. No specific training is required for the employees to use this application. They can easily use the tool that decreases manual hours spending for normal things and hence increases the performance. As the data is centralized it is very easy to fix an appointment of doctor with a patient immediately.
Feasibility Report:
Preliminary investigation examines project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All systems are feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Economical Feasibility
Discharges & Insurance Module:
This module deals with major and crucial part that includes discharges of inpatients and updates the rooms’ status as empty after discharge of the patient. And also it can give all the information related to the insurance of the inpatient.
Input Design:
Input design is a part of overall system design. The main objective during the input design is as given below:
• To produce a cost-effective method of input.
• To achieve the highest possible level of accuracy.
• To ensure that the input is acceptable and understood by the user.
SDLC Methodology:
This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
Business Logic Layer:
This layer encapsulates the Business rules or the business logic of the encapsulations. To have a separate layer for business logic is of a great advantage. This is because any changes in Business Rules can be easily handled in this layer. As long as the interface between the layers remains the same, any changes to the functionality/processing logic in this layer can be made without impacting the others. A lot of client-server apps failed to implement successfully as changing the business logic was a painful process.
[attachment=52367]
Objective:
Every hospital needs an online system whereby it can accommodate the patients comfortably and avoid any confusion to the doctors regarding their work. There should be a system where the patients are categorized under insurance policy and non policy holders and the system helps the hospital management to claim the bills from concerned insurance companies. All these needs and much more are fulfilled in SedativeSleuthhaund. SedativeSleuthhaund is useful to record patient’s details along with the compliant. It also records the inpatient details and outpatient details and arranges the appointment of doctors. SedativeSleuthhaund also provides the management reports like schedules, appointments of doctors, inpatients, insurances and discharges. And also used to generate bills dynamically for the discharged patients etc.
Existing System:
The following are the disadvantages of current system
1. It is difficult to maintain important information in books
2. More manual hours need to generate required reports
3. It is tedious to manage historical data which needs much space to keep all the previous years ledgers, books etc
4. Daily admissions of patients are to be entering into different books
immediately to avoid conflicts which are very difficult.
Proposed System:
Proposed system is a software application which avoids more manual hours that need to spend in record keeping and generating reports. This application keeps the data in a centralized way which is available to all the users simultaneously. It is very easy to manage historical data in database. No specific training is required for the employees to use this application. They can easily use the tool that decreases manual hours spending for normal things and hence increases the performance. As the data is centralized it is very easy to fix an appointment of doctor with a patient immediately.
Feasibility Report:
Preliminary investigation examines project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All systems are feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Economical Feasibility
Discharges & Insurance Module:
This module deals with major and crucial part that includes discharges of inpatients and updates the rooms’ status as empty after discharge of the patient. And also it can give all the information related to the insurance of the inpatient.
Input Design:
Input design is a part of overall system design. The main objective during the input design is as given below:
• To produce a cost-effective method of input.
• To achieve the highest possible level of accuracy.
• To ensure that the input is acceptable and understood by the user.
SDLC Methodology:
This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
Business Logic Layer:
This layer encapsulates the Business rules or the business logic of the encapsulations. To have a separate layer for business logic is of a great advantage. This is because any changes in Business Rules can be easily handled in this layer. As long as the interface between the layers remains the same, any changes to the functionality/processing logic in this layer can be made without impacting the others. A lot of client-server apps failed to implement successfully as changing the business logic was a painful process.