Distributed Systems
Design and building a Distributed Information System.
This coursework must be completed individually
Detailed Specification
The scenario
You have been asked to prepare an initial design for enabling a large private medical care service provider with a distributed healthcare solution. The care service providerhas over 100 outlets across the UK offering a wide range of laboratory testing, diagnoses and treatment services. The medical functions are supported by adminstaff that manage appointments and resources (a resource is defined as staff and bookable facilities, i.e. specialized rooms).
There are three categories of user: -
• Administrative staff that need to track patients, staff, resources and book appointments but cannot see their medical history.
• Doctors need access to patient information, their medical history, arrange for lab testing but cannot book appointments.
• Laboratory staff needs to track samples associated with a patient.
You task is to design and implement a prototype 3-tier application for the business.
All information used in your system should as a minimum be stored at a central location -although distribution would be preferred.
Based on the above requirements it is necessary to build the prototype as distributed system with a number of different user interfaces, one for each of theusers. You should implement a 3-tier architecture. Thesystem should persistently save data in a database. The choice of technology isyours.Likewise the user interfaces can be built using any technology of yourchoosing. Care should be taking to achieve a 3-tier architecture.
You should produce and submit a document of your UML design for the proposedsystem along with screen shots of your implementation and a brief description ofyour implemented product. You should also produce a ZIP file containing yoursoftware code and a brief report describing what you have achieved.
Deliverables
Based on the above requirements it is necessary to build the prototype as a distributed system with a number of different userinterfaces, one for each of the users identified in your design. You
Should design and implement a 3-tier architecture.
You should document a UML design for the proposed system.
The implemented prototype system should persistently save data in a database. The choice of appropriate technology for yourcentre will be determined by your local tutor, this includes the technology for distribution1 (middleware, RMI, web services,etc.), the database (Oracle, SQL server, MYSQL, Postgres, MS Access, etc.) and also the application/user interface technology (Java, Java Servlets, .NET, ASP.NET, VB.NET, etc.).
Specific Deliverables
You are expect to submit two items:
A report containing only the following items:
D1: An ERD describing your backend database.
D2: An UML Deployment diagram detailing your system architecture.
D3: UML Use-case diagrams for the scenario, these should distinguish the various functions and users of the system.
D4: UML Conceptual Class diagram for the scenario.
D5: A critical evaluation of the design and implementation.
D6: A short statement of the implemented functionality along with screen shots of the application functionalities.
Accompanying text should be kept to key assumptions of any designs and brief explanations of the software functionality. You will be required to demonstrate your software prototype to your tutor. Lack of a demonstration will be classed as a non-attempt at implementation and thuswill fail the course work.
Deliverables & Grading Criteria
The System design (maximum of 50% will be awarded for your design) to include:
a. An UML use-case diagram documenting the prototype system.(10%)
b. A backend database design- ERD (10%)
c. An UML design class diagram (10%)
d. An UML deployment diagram (10%)
e. Critical evaluation (reflection / limitations / strengths of the work). (10%)
Implementation (Maximum of 50% will be awarded for you implementation) to include:
f. 3-tier implementation with a clear separation between tiers and using appropriate technology,
g. Doctors functionality
h. Laboratory functionalityi. Administrators functionality