Scribd
Upload
174 views

DMS Design Document

The document outlines the design of a Disaster Management System aimed at centralizing information for effective disaster response, particularly in scenarios like COVID-19. It includes various components such as entity relationship diagrams, sequence diagrams, architecture design, and test cases to ensure the system's functionality. The system will facilitate the identification of affected zones and enable government organizations to take necessary actions during disasters.

Uploaded by

guardianadvance65
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
174 views

DMS Design Document

The document outlines the design of a Disaster Management System aimed at centralizing information for effective disaster response, particularly in scenarios like COVID-19. It includes various components such as entity relationship diagrams, sequence diagrams, architecture design, and test cases to ensure the system's functionality. The system will facilitate the identification of affected zones and enable government organizations to take necessary actions during disasters.

Uploaded by

guardianadvance65
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 18

< Disaster (like COVID-19) Management

System >
Design Document

Version 1.0

Group Id: <S2002E6DA1 (MC190200653)>

Supervisor Name :< Komal Saleem>


Revision History

Date VDMSion Description Author


(dd/mm/yyyy)
There is no central information
07/19/2020 1.0 system for the government to be MC190200653
used for any disaster
management. The aim of this
project is to develop a Disaster
Management System which will
maintain a central repository in
case of any disaster like recent
outbreak of COVID-19. Using
this system, read zones (the areas
badly affected by the disaster)
could be identified. The system
will provide the important
information to the Government
and its organizations to take
effective measures in the needing
areas in case of disaster. System
should be designed to in such a
way that it can collect/receive
and consolidate the information
from different sources/systems.
The integration can be done
using REST API to get data from
existing systems.
Table of Contents

1. Introduction of Design Document

2. Entity Relationship Diagram (ERD)

3. Sequence Diagrams

4. Architecture Design Diagram

5. Class Diagram

6. Database Design

7. Interface Design

8. Test Cases
Introduction of Design Document

This phase contains following data:

Entity Relationship Diagram is a data model for describing a database in an abstract model. It contains entities
and their relationships. An entity may be defined as a thing which is recognized as being capable of an
independent existence and which can be uniquely identified. An entity is an abstraction from the complexities of a
domain.

Sequence Diagram is an interaction diagram that shows how processes operate with each other.
A sequence diagram shows interaction of diagram according to the time division. It is also called event diagram.

Architecture Design Diagram used to represent data in the form of layDMS. It contains three layDMS data link
layer, application layer and business layer.

Class Diagram in this design document describes the structure of system by showing the system's classes, their
attributes, operations or methods and relationships between classes. The classes in a class diagram represent both
the main objects and interactions in the applications and the objects to be programmed.

Database Design is a process of producing a detailed data model of a database. It can be taken as the logical
design of the base data structures to store the data. In the relation model these are the tables and views.

Interface Design is a GUI view of main software. It shows how our program will look like. Interface design deals
with the process of developing a method for two (or more) modules in a system to connect and communicate.

Test cases A test case in software engineering is a set of conditions or variables under which a tester will
determine whether an application or software system is working correctly or not. It is a detailed procedure that
fully tests a feature or an aspect of a feature.
1. Entity Relationship Diagram (ERD)
2. Sequence Diagram
3. Architecture Design Diagram
5. Class Diagram
6. Database Design
7. Interface Design
8. Test Cases

Title Sign In

Abbreviated Sign In
Use Case Id DMS -01
Actors Admin
Description
User/Admin can login after entering correct information.
Pre-Conditions:
User must have access to the system.
Actions
1. System show Login Screen
2. Fill in required information
3. Enter username and password
4. System acknowledge entry
Exception
Invalid Credentials/Database exceptions.
Use Case Title Hospital Management

Abbreviated Hospital Management


Use Case Id DMS -02
Actors User
Description: Admin can manage all hospital records like add, update, delete.
Pre-Conditions:
User must have to access the system.
Task Sequence
1. Clicks add hospitals.
2. Adds details of hospitals
3. Clicks delete hospitals

Exception
Invalid Credentials/Database exceptions.
Use Case Title Manage Patient Details

Abbreviated Manage Patient Details


Use Case Id DMS -03
Actors User
Description:
Admin can manage patient details like add, update, delete.
Pre-Conditions:
User must have to access the system.
Task Sequence
1. Clicks add patient
2. Adds details of patient
3. Clicks delete patient

Exception
Invalid Credentials/Database exceptions.
Use Case Title Use Testing Tool

Abbreviated Use Testing Tool


Use Case Id DMS -04
Actors User
Description: Admin can use testing tools like postman for testing API.
Pre-Conditions:
User must have to access the system.
Task Sequence
1. Clicks to use testing tools

Exception
Invalid Credentials/Database exceptions.
Use Case Title Declaring Red Zone

Abbreviated Declaring Red Zone


Use Case Id DMS -05
Actors User
Description: Admin can declare any area in red zone any time.
Pre-Conditions:
User must have to access the system.
Task Sequence
1. Clicks declaring red zone.

Exception
Invalid Credentials/Database exceptions.
Title: Log Out

Abbreviated: Log Out


Id: DMS -06
Actors: Admin
Description:
Receptionist can Log out by clicking the sign out button.
Pre-Conditions: Customer/Mechanic must have accessed the system.
Actions:
1. System show Logout/ sign-out button
2. user clicks log out button
3. user will be signed out

Exceptions:
Invalid Credentials/Database exceptions.

You might also like