Exer1

I’m Team

DBH

DataBase for hospital

Sarsenbayeva Aiymgul

Almaty, 2014

Requirements checklists

1. The system should maintain information about the entire patients in a database.

2. The system should have function index card.

3. System must contain information about each user. Each user must have own status (for example, data base administrator, patients and employer).

4. System should maintain “news”. They could be added only by company’s workers(not customer).

5. The system should include a graphical user interface that allows the user to browse patients, and view specific information about patients they want.

6. The system should count the total cost that the user should pay for services his or her want to buy automatically.

8. System should maintain type of payment( online, cash, etc.)

9. The system should allow user to send each other messages.

10. The system should allow user to view their previous queue.

11. . The user interface should be implemented as a Java application.

13. The order database can be implemented using a suitable database system.

14. The database connectivity should be provided via separate objects coded using the JDBC package.

Developer scope statement

Client-side:

1. Hardware platform: A PC connected to the internet not less than 100 Mb/s.

2. Software platform: JVM 1.7.

3. Software requirement: any web browser.

Server-side:

1. Hardware platform: A PC connected to the internet.

2. OS: Windows(32-bit, 64-bit), Linux.

3. Software platform: JVM 1.7.

4. DB: Oracle, MySQL, MS SQL.

5. Software requirement: MySQL 5.6 and over, Apache 2.4.9 and over, MS SQL 2012.

6. Service requirement: The host should be always on for the end-user may need to access the server database at any time.

7. Transactions per second: 500(users).

8. Response time: 1-2 s.

9. RAM: not less than 2 Gb.

Development model

This project has a high degree of potential software reuse, since it can incorporate the existing classes from the Java Class Libraries for JDBC and the graphical user interface (AWT or Swing). The software development effort will therefore involve gaining mastery of these classes, through studying the API documentation and writing client classes for them.

Since this project does not need to worry about a large number of performance and robustness concerns, it can only represent an initial iteration in the development of a real e-commerce shopping application. Therefore it fits best into a development model that supports iterative and/or incremental development, such as the Spiral Model or the Incremental Model. This initial system could also be thought of as a result of a Rapid Prototyping phase.

An organization planning to build such a system should take a conservative approach, since accommodating the demands of high performance and robustness can result in dramatic changes in software architecture. The need to re-evaluate this risk at each incremental step in development motivates a choice of the Spiral Model.