between 3000 to 4000 words Tasks 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). 
Time (When) Motivation (Why)
Objectives / Scope
Model of the Information
CI7230 Modelling Enterprise Architectures 3
Case Study Title: Disaster Relief Coordination System (DRCS) for a Small Island
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 Methodology for the last 10 years and they are very competent in using
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.
What you are getting yourself into:
As mentioned earlier, your firm has been commissioned by the government of Lazarus Island to design and build a specialised
system for them. The island has been subjected to a number of natural disasters such as cyclones, hurricanes and recently an
earthquake. The government receives a lot of offers of assistance, donations and actual resources such as food, clean water, medical
supplies, temporary shelters etc. whenever disaster struck but their approach to handling relief (and the disasters in general) has
been poorly coordinated.
To add some perspective, dealing with disasters is a complex process and managing a disaster is usually done in 2 stages:
You can learn more about Disaster Relief and Coordination from various resources such as: the Emergency Management UK portal
Also there are some useful articles on Disaster Management e.g. DEC, which brings together several UK charities, and Red Cross:
http://www.dec.org.uk/ and https://www.ifrc.org/en/
You should carry out further literature review to help you understand the requirements in more detail.
The System that needs to be created:
The system that needs to be created would be used in the response stage of disaster management, specifically the part that deals
with ensuring the basic needs of people affected by the disaster are met by government agencies and humanitarian organisations.
This is a crucial stage in response to a disaster as people are cut off from basic supplies and left in exposed, substandard living
conditions can fall foul of disease and malnutrition.
Your role is to draw up a specification for a system that will help them to better coordinate their relief effort. This system should be
web based so computers and mobile devices can access it. The system needs to be secure and only people authorised to use the
system should be able to access it. The disaster relief coordination system (code-named Aegis) should be designed to enable
government and non-government organisations to coordinate efforts in the relief phase following a natural (or man-made) disaster.
The system should be made up of a number of modules that enable these organisations to work together and share information on
the disaster so that resources can be deployed in the most effective way possible.
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.
Part of the requirements for the system is that it will need to incorporate a submit/approve process whereby a non-governmental
organisation can submit information that needs to be approved by the appropriate government agency. 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 typical ‘situation’ as being the discovery of local(s) directly affected by the disaster
and 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.
Government Agency Administrator: They would be using the system to enrol and manage Non-Government Orgainsations
(NGO) e.g. Red Cross, Oxfam.
The government agency administrators would setup/confirm requests for resources as well as manage and allocate resources to
NGOs. Resources are stored at resource hubs and are then despatched to places that are requesting them. Resources are never
requested or allocated individually. They are bundled up into resource packages that contain essential resources.
The administrator would also identify situations from information provided by the national and local emergency services. They
would also have to approve situations proposed by NGOs. Both would result in a request for assistance being generated that they
could allocate to an NGO to deal with. A situation will only be approved by a government admin as soon as one of the emergency
services (police, ambulance, fire brigade etc.) have visited the situation and confirmed that it is real.
NGO Administrator: These individuals act as the main contact and coordinator between government administrators and the NGO.
They identify their main base camps, update worker lists and profiles and also ensure that the last known locations of workers have
been updated. They also identify and build teams from their worker lists to deal with requests for support.
They can identify situations for approval by government admin and offer to respond to requests for assistance.
An NGO admin can request resources for teams that are dealing with support requests. They can also offer to provide resources and
set up the NGO resource hubs from where their resources would be despatched.
NGO Worker: They are the ones who are out in the field providing the relief work. Workers in the field can keep their profile up
to date ensuring that their correct skills and expertise are stored. Workers can also update their current location so that NGO
administrators know where they are and how far they are from areas that need assistance.
CI7230 Modelling Enterprise Architectures 5
Workers can request resource packages for use in situations that they are providing assistance for. They can also suggest certain
configurations for resource packages so that they better suit the situation that they are supporting.
As the workers are operating in the areas affected by the disaster they may spot situations that have not been set up on the Aegis
system. NGO workers can then declare the situation that they have identified via the system.
Example of system use – Responding to a request for support
This example describes an indicative, not comprehensive use of the system. It involves more than one of the Aegis sub-systems but
does not cover all of them.
An NGO administrator notices a support request that requires the construction of emergency shelters and the provision of
desalinated water for a group of around 200 locals that are cut off from travelling to the nearest refugee camp some 25 miles away.
The administrator looks through their NGO worker lists and identifies a number of individuals who are currently available with the
required skills to meet the request. She narrows and adjusts the list by specifying the maximum distance that the last known
location of the NGO workers should be. She does this so that workers can get to the area and administer relief as soon as possible.
The administrator accepts the support request and the system is updated with the information that the request is being handled by
her organisation. This makes the support request unavailable to other NGOs. The administrator then creates a team by adding
suitable workers from the worker list and then assigns the team to the request. The workers who have been added to the team
receive a text message via their mobile phone letting them know they have been tasked and advising them to access the Aegis
system for more details. The message also includes the location information required to get to the affected locals.
Steve, and NGO worker uses the location information to head directly to the area. He arrives just as a government truck is bringing
in some resources to construct temporary shelters. The other NGO workers are already on the scene installing the desalination
equipment and giving out essential items such as food and fresh water. There are reports that some of the people have got malaria
but no malaria medicine was included in any of the resources they received. Steve calls one of the NGO administrators who is
supporting the team to request a supply of malaria pills. The administrator does a search on the NGO inventory and finds that they
have got some, and then she allocates this resource to