Due: Thursday 11th NovemberDistributed Information Systems

Detailed SpecificationThe scenarioThe scenarioYou have been approached to design and implement a prototype of a distributed informationsystem for a national car part retail outlet chain. The company comprises of numerous garageretail outlets that each keep their own stock and sell parts to various customers. A centralwarehouse despatches parts to the various garages according to their individual stockmanagement requirements. At present stock is managed individually at the many retailoutlets. Likewise sales, customers, orders are all managed locally. As the new IT expert, youhave suggested an integrated distributed information system that will provide better stockmanagement and reporting.The prototype system functionalityLocal garage outlets1. Local staff will have the capabilities to sell parts from local stock.2. Local staff will have the capabilities to order parts from the warehouse or from othergarage.3. Local staff are able to recording customer details and take payments.4. Re-order levels should be automated.5. Emergency query a local garage for an item of stock.Note: emergency deliveries are dispatched for express overnight delivery.The warehouse1. Maintain a level of stock sufficient to meet the needs of the numerous local garageoutlets.2. Set national prices for products.3. Set national discounts and offers for products.4. Dispatch stock to the local garage outlets.Note: deliveries to each garage occur once every week.Managers1. Have all of the functionality of Local managers and the warehouse.2. Can view summary of national sales.3. Can view summary of local sales.4. Can view summary of national stock.5. Can view summary of local stock.All information used in your system should as a minimum be stored at the warehouseYour taskPage 3 of 4Based on the above requirements it is necessary to build the prototype as a distributed system with anumber of different user interfaces, one for each of the users. You should implement a 3-tierarchitecture.The system should persistently save data in a database. The choice of technology is yours.Likewise the user interfaces can be built using any technology of your choosing. Careshould be taking to achieve a 3-tier architecture.You should produce and submit a document of your UML design for the proposed system

along with screen shots of your implementation and a brief description of your implementedproduct. You should also produce a ZIP file containing your software code and a brief reportdescribing what you have achieved.DeliverablesBased on the above requirements it is necessary to build the prototype as a distributed system witha number of different user interfaces, one for each of the users identified in your design. Youshould 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 ofappropriate technology for your centre will be determined by your local tutor, this includes thetechnology for distribution1 (middleware, RMI, web services, etc.), the database (Oracle, SQLserver, MYSQL, Postgres, MS Access, etc.) and also the application/user interface technology(Java, Java Servlets, .NET, ASP.NET, VB.NET, etc.).Specific DeliverablesYou 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 functionsand users of the system.D4: UML Design 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 theapplication functionalities.NOTE: No software code is to be submitted in the report (code is submitted as aseparate ZIP file)NOTE: Accompanying text should be kept to key assumptions of any designs and briefexplanations of the software functionality.You will be required to demonstrate your software prototype to your tutor. Lack of a demonstrationwill be classed as a non-attempt at implementation and thus will fail the course work.Page 4 of 4Deliverables & Grading CriteriaThe 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. Local capabilities implemented,h. Warehouse capabilities implemented,i. National manager capabilities implemented.Grading Criteria70% and above (distinction)A very well written and professionally presented piece of work which shows a completemodel and matches the implementation of the required system.All deliverables must be covered to a high standard and quality that warrants a distinction

to be awarded.Critical evaluation shows insight and a thorough grasp of DIS concepts.Between 60 and 69 (merit)The work lacks some detail but shows a complete design model and a workingimplementation of the system.All deliverables must be covered to a standard & quality that warrants a merit to beawarded.The design and implementation is of a good standard but missing some detail and orincomplete in some areas.Your critical evaluation of your system is good, but lacking some detail and insight.Between 50 and 59The work lacks some details but demonstrates a fair degree of understanding of bothdesign and implementation issues.The critical evaluation is mainly factual but shows some reflection.Between 40 and 49The work lacks some details in either section but the design model and implementationdemonstrate a pass level understanding of the core principles in distributed systems.The design is incomplete but shows a basic understanding of the scenario and how itcould be realised as a DIS.Critical evaluation is factual but ultimately unable to reference the design orimplementation.Below 40 - FAILA poor submission with an inadequate implementation which fails to demonstrate basicunderstanding of the principles involvedLack of implementation.