These all relate to the description of Disaster Relief Co-ordination (DRCS) system given below. This description should not be regarded as complete but can be regarded as accurate (in other words you can expand upon it but your answer should not contradict it). You may want to investigate similar dating agency websites for ideas! Please note that there are no absolutely definitive (or correct) answers to these. You will be assessed on your ability to present the requirements in a clear and logical manner, the way you have addressed the description of the system provided, and the quality of your discussion of the issues arising.
Note that you are required to present requirements and models for the new system at DRCS – much of the discussion below relates to the current system. It is important to draw the diagrams using a UML case tool. For each section some marks will be given for some explanation and design choices.
1. Draw a use case diagrams and produce 2 overall Activity Diagrams including swim-lanes and the transitions of use cases. 
2. Produce 4 Prototypes presented as a storyboard 
3. Using the MVC pattern, produce 4 Sequence Diagrams corresponding to the 4 Prototypes 
4. Draw a class diagram and consider 1 class and from that draw a state-chart diagram 
5. Consider the class diagram in point 4 above and via object relational mapping develop an entity relationship diagram ERD. 
6. Consider 1 sequence diagram from 3 above and your class diagram write the basic Java code including the name of the class, attributes (including the relationships with other classes). Also include the method name but not the method details. 
7. Redraw the Zachman Framework and complete it further considering where all the diagrams drawn in this coursework would be presented and show where the component and deployment diagrams would be presented as well. (Please note: you don’t need to actually draw a component or deployment diagram for this coursework). 
Who you are:
You are part of a team of systems analysts working for an IT consulting firm that have been hired to develop a specialised system for the government of Lazarus Island. The IT consulting firm has its own staff with skills of Agile Project Management, business analysis, system development, programming and testing.
The island is located in the South Pacific, about 350 miles from Ecuador and has a population of 80,000. Your team have been developing systems using an Agile the DSDM Agile Project Management Framework and the SCRUM methodology. The team have decided that this particular project will adopt the DSDM Agile Project Management framework to develop the system.
The Aegis System is made up of the following sub-systems:
§ Mapping and Geo-location System (using the Google Maps API or a more reliable mapping API)
§ Resource Management System (for cataloguing and tracking inventory such as medicines, equipment, etc.)
§ Organisation Management System (where staff are associated with organisations)
§ Situation Management System (allowing situations to be ‘raised’ that list requirements)
All organisations can add markers onto an interactive map highlighting areas of need, current locations of relief workers, camps, supply points, last location of missing/found people etc. These different marker groups can be activated and deactivated as needed to improve readability and focus of the map. Organisations will be able to communicate with one another through messaging services and can add workers’ mobile numbers so that they can send/receive status updates.
This only applies to certain requests such as medical supplies, desalination equipment, shelter construction and support request that go beyond basic grain, milk, water and emergency shelter provision. The process is also used in confirming situations raised by workers from NonGovernment Organisations. You can consider a in need of resources that will provide for their basic needs and health. There have been occasions in the past where workers for NGOs invented situations so that they could get resources that were not needed in order to sell them on privately. Who are the users:
A number of people will be stakeholders regarding the development of the Aegis system. Only the hands on users, those that directly use the system as a core part of their job are listed here along with their basic use of the system. It is likely that there are other users of the system that have not been listed below.