Professional Documents
Culture Documents
ABSTRACT
1.INTRODUCTION
2.SYSTEM ANALYSIS
2.1 Existing System
3. SYSTEM SPECIFICATION
3.1 Hardware Requirements
4. SYSTEM DESIGN
4.1 Module Description
5.2 Testing
6. CONCLUSION
The National Disaster Management Authority (NDMA), headed by the Prime Minister of
India, is the apex body for Disaster Management in India. Setting up of NDMA and the creation
of an enabling environment for institutional mechanisms at the State and District levels is
mandated by the Disaster Management Act, 2005.
1.1. Objectives
1) To present the architectural structure and working mechanism of Disaster Management
System, this can provide guidance and assistance for the construction of similar service-based
systems.
2) To propose an efficient heuristic algorithm for service request scheduling, this is
crucial to the success of the system and can be useful for many other service scheduling
problems.
3) To present simulation results and real-world applications of the system, the lessons
learned from which can benefit both the system developers and the disaster managers.
4) To maintain the summarized content of any particular disaster with lot of pictures
posted by different means.
1.2. STATEMENT OF THE PROBLEM
As it has being observed that the conventional method used in preparing and managing disaster
report has resulted to the following problems:
5. Lack of security.
The aim of this project work is to design an online disaster report management system for
NEMA.
The scope of this research work is strictly on the design of an online disaster report management
system.
2. Limited fund
4 PHP: (recursive acronym for PHP: Hypertext Pre-processor) is a widely-used open source
general-purpose scripting language that is especially suited for web development and can be
embedded into HTML.
5 HTML: Hypertext Mark-up Language, a standardized system for tagging text files to
achieve font, colour, graphic, and hyperlink effects on World Wide Web pages.
8 SQL: Structured Query Language, basically used in querying the database to retrieve,
updates, and review database.
10 WEBBASED: Is any program that is accessed over a network connection, rather than
existing or quitting within a devices memory.
The disaster report management system will be designed in such a way that the
information will be accessible online through the internet by uploading all the necessary
documents, the report will be automatically processed online . HTML, CSS, and some JavaScript
for the front end to make the application interactive; in the backend, PHP will be used to create a
connection between the application portal and the MySQL database.
The method used in planning this project is the waterfall model. This model is a linear sequential
design approach for software development, in which progress flows in one direction downward
like water waterfall.
For this project the system runs through the phase of conception, initiation, analysis, design,
testing, deployment and maintenance.
REQUIREMENT
PRODUCT
DESIGN
IMPLEMENTATION
VERIFICATION
MAINTENANCE
Chapter-2-SYSTEM ANALYSIS
2.1 Existing System
A lot of weakness are associated with the existing system, involves the use of
traditional method . The system has proved defective as the objective of the system has also
failed. Among the weakness associated with the existing system include the following:
Lack of security.
Developing countries suffer the greatest costs when a disaster hits – more than 95 percent of all
deaths caused by disasters occur in developing countries, and losses due to natural disasters are
20 times greater (as a percentage of GDP) in developing countries than in industrialized
countries.
Types of DISASTERS
There is no country that is immune from disaster, though vulnerability to disaster varies. There
are four main types of disaster.
Natural disasters. These disasters include floods, hurricanes, earthquakes and volcano
eruptions that can have immediate impacts on human health, as well as secondary impacts
causing further death and suffering from floods causing landslides, earthquakes resulting in
fires, tsunamis causing widespread flooding and typhoons sinking ferries
All aspects of disaster management deal with the processes used to protect populations or
organizations from the consequences of disasters, wars and acts of terrorism. This can be seen
through government publications such as the National Strategy for Homeland Security which
detail how individuals and varying levels of government respond during the different phases of a
disaster.
Emergency management can be further defined as “the discipline and profession of applying
science, technology, planning and management to deal with extreme events that can injure or kill
large numbers of people, do extensive damage to property, and disrupt community life” (Drabek,
1991a, p. xvii).
An ‘emergency’ is ‘an unplanned event that can cause deaths or significant injuries to
employees, customers or the public; or that can shut down your business, disrupt operations,may
cause physical or environmental damage, or threaten the facility’s financial standing or public
image’ (FEMA, 1993).
Emergency events can include terrorist attacks, industrial sabotage, fire, natural disasters (such
as earthquakes, severe weather, etc.), public disorder, industrial accident, communications failure
and loss, or corruption of critical information. Some examples of catastrophic incidents are:
1. The 1995 Kobe, Japan, earthquake, which killed more than 6000 people and left another
30,000 injured.
2. The 1994 Northridge, California, earthquake, which resulted in approximately $33 billion
in damages.
These individual events are significant enough, but the losses are even more dramatic when
accumulated over time. Between 1989 and 1999, the average natural disaster loss in the US was
$1 billion each week.
Disaster management does not necessarily avert or eliminate the threats themselves, although the
study and prediction of the threats are an important part of the field. The basic levels of
emergency management also include the various kinds of search and rescue activity.
‘Disaster management can be defined as the organization and management of resources and
responsibilities for dealing with all humanitarian aspects of emergencies, in particular
preparedness, response and recovery in order to lessen the impact of disasters’.
1. Preparedness:
It involves measure to insure that communities and services are capable of coping with
the effect of disaster.
Example of preparedness:
a. Community Awareness and Education
b. Proper warning system
c. Mutual Aid arrangement
d. Mock Drill, Training Practices
2. Disaster Response:
It involves measures taken in anticipation of during and immediately after a disaster to
ensure the effects are minimized.
Example of Response:
a. Implementing the Disaster Management Plan
b. Setting up Medical Camps and Mobilizing Resources
c. Providing adequate shelter and sanitary facilities
3. Disaster Recovery:
It involves measures, in which support emergency affected areas in reconstruction of the
physical infrastructure and restoration of economic and emotional well-being.
Examples of Recovery:
a. Counselling programmes for those who lost the near ones.
b. Restoring services like roads, communication link.
c. Providing Financial support employment
d. Reconstructing damaged buildings and surroundings
Hardware Requirements:-
1. Computer system
5. Ups
Software Requirements: -
1. Window 7 operating system
5. Hypertext preprocessor(PHP)
HTML elements form the building blocks of HTML pages. HTML allows images and other
objects to be embedded and it can be used to create interactive forms. It provides a means to
create structured documents by denoting structuralsemantics for text such as headings,
paragraphs, lists, links, quotes and other items. HTML elements are delineated bytags, written
using angle brackets. Tags such as <img /> and <input /> introduce content into the page
directly. Others such as <p>...</p> surround and provide information about document text and
may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to
interpret the content of the page.
HTML can embed scripts written in languages such as JavaScript which affect the
behavior of HTML web pages. HTML markup can also refer the browser to Cascading Style
Sheets (CSS) to define the look and layout of text and other material
CSS is a style sheet language used for describing the presentation of a document written in
a markup language. Although most often used to set the visual style of web pages and user
interfaces written in HTML and XHTML, the language can be applied to any XML document,
including plain XML, SVG andXUL, and is applicable to rendering in speech, or on other media.
Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to
create visually engaging webpages, user interfaces for web applications, and user interfaces for
many mobile applications.
CSS is designed primarily to enable the separation of document content from document
presentation, including aspects such as the layout, colors, and fonts. This separation can improve
content accessibility, provide more flexibility and control in the specification of presentation
characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS
in a separate .css file, and reduce complexity and repetition in the structural content, such
as semantically insignificant tables that were widely used to format pages before consistent CSS
rendering was available in all major browsers. CSS makes it possible to separate presentation
instructions from the HTML content in a separate file or style section of the HTML file. For each
matching HTML element, it provides a list of formatting instructions. For example, a CSS rule
might specify that "all heading 1 elements should be bold", leaving pure semantic HTML
markup that asserts "this text is a level 1 heading" without formatting code such as a<bold> tag
indicating how such text should be displayed.
This separation of formatting and content makes it possible to present the same markup page in
different styles for different rendering methods, such as on-screen, in print, by voice (when read
out by a speech-based browser orscreen reader) and on Braille-based, tactile devices. It can also
be used to display the web page differently depending on the screen size or device on which it is
being viewed. Although the author of a web page typically links to a CSS file within the markup
file, readers can specify a different style sheet, such as a CSS file stored on their own computer,
to override the one the author has specified. If the author or the reader did not link the document
to a style sheet, the default style of the browser will be applied. Another advantage of CSS is that
aesthetic changes to the graphic design of a document (or hundreds of documents) can be applied
quickly and easily, by editing a few lines in one file, rather than by a laborious (and thus
expensive) process of crawling over every document line by line, changing markup.
The CSS specification describes a priority scheme to determine which style rules apply if more
than one rule matches against a particular element. In this so-called cascade, priorities
(or weights) are calculated and assigned to rules, so that the results are predictable.
6.4 PHP
PHP is a server-side scripting language designed for web development but also used as
a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the
PHP reference implementation is now produced by The PHP Group. PHP originally stood
for Personal Home Page, but it now stands for therecursive backronym PHP: Hypertext
Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management system and web frameworks. PHP code
is usually processed by a PHPinterpreter implemented as a module in the web server or as
a Common Gateway Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including images, with the
generated web page. PHP code may also be executed with a command-line interface(CLI) and
can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web servers
on almost every operating system andplatform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014,
leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to
create a formal PHP specification.
Disaster Management System consists of two generally independent systems. The first is
a regular web application, which provides a number of web pages containing documents,
pictures and other materials that have been picked up from every medium as a summarization
can be accessed through mobile browsers of the clients. After becoming registered members, the
client users can also upload and maintain their personal information, receive customized
information, and participate in forum discussions.
In the life of the software development, problem analysis provides a base for design and
development phase. The problem is analyzed so that sufficient matter is provided to design a
new system. Large problems are sub-divided into smaller once to make them understandable
and easy for finding solutions. Same in this project all the task are sub-divided and
categorized.
System Modules
ADMIN
Login
View Disaster Queries
Post Solution
Maintain Summary
USER
Register
Login
Post Query
View solution
PUBLIC
Post Query
View solution
Summary Review
4.4. MODULES
ADMIN
Login
Admin can login this system after they can view home page.
Maintain Summary
Admin will extract all the related posts of the disaster in every site and
then maintain summary of the disaster with the real pictures and content.
USER
Register
Login
User can login this system after they can view home page.
Post Query
User can login this system after they can post their own queries about
escape of this situation.
View solution
User can login this system after they can view solution.
PUBLIC
Post Query
Public can directly post their own queries about escape of this situation.
View solution
Public can access this system so that they can view solution.
Summary Review
Public can this give their review about the summary given if there is any
correction in the information provided after viewing the solution.
Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are required
to build and verify the software.
The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software design is
conducted in two steps. Preliminary design is concerned with the transformation of requirements
into data.
4.1.UML Diagrams
UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product after
analysis. The goal from this is to produce a model of the entities involved in the project which
later need to be built. The representation of the entities that are to be used in the product being
developed need to be designed.
Use case diagrams model behavior within a system and helps the developers understand
of what the user require. The stick man represents what’s called an actor. Use case diagram can
be useful for getting an overall view of the system and clarifying who can do and more
importantly what they can’t do.
Login
Disaster Type
<<include>>
View Query Escape Root
<<include>>
Admin
<<include>>
Alternate solution
<<include>>
Post Solution
<<include>>
Palce
Disaster Range
Register
login
User
Post Query
View Solution
Post query
view Solution
Public
Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.
The purpose is to show the interactions between the use case and actor.
To represent the system requirements from user’s perspective.
An actor could be the end-user of the system or an external system.
1 : login()
3 : post queries()
4 : view solution()
5 : post queries()
6 : view solution()
7 : view queries()
8 : post solution()
Queries Query
Solution solution
View Queries
post Queries
System implementation is the construction of the new system and the delivery
of the new system to the Directorate for petroleum Resources.
a. PROGRAM DEVELOPMENT
Cost of maintenance
Users needs.
SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
TESTCASE
OUTPUT
1 User register Email and All the user details Register successfully
Password register successfully
Or
Register
unsuccessfully
3 Post Query User will enter all If all the post Query Created successfully or
post Query “Created created unsuccessfully
Successfully”
5 View Disaster Admin will check Admin view All View all Disaster
Queries All Disaster Disaster Queries Queries
Queries
7 View Solution User will check User view All View all Solution
All Solution Solution
“Login
unsuccessfully”
9 Post Query Public will enter If all the post Query Created successfully or
all post Query “Created created unsuccessfully
Successfully”
10 View Solution Public will check Public view All View all Solution
All Solution Solution
Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.
Integration testing
Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of components is
correct and consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.
System Test
System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.
Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.
Test objectives
All field entries must work properly.
Pages must be activated from the identified link.
The entry screen, messages and responses must not be delayed.
Features to be tested
Verify that the entries are of the correct format
No duplicate entries should be allowed
All links should take the user to the correct page
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
5.3 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
SCREEN SHOTS
CHAPTER 6 - CONCLUSIONS
[1] A. Weiser and A. Zipf, “Web service orchestration of OGC web services for disaster
management,” in Geomatics Solutions for Disaster Management, ser. Lecture Notes in
Geoinformation and Cartography, J. Li, S. Zlatanova, and A. Fabbri, Eds. Springer Berlin
Heidelberg, 2007, pp. 239–254.
[2] M. Gloria, V. Lersi, G. Minei, D. Pasquariello, C. Monti, and A. Saitto, “A semantic Web
services platform to support disaster and emergency management,” in 4th Biennial Meeting of
International Environmental Modelling and Software Society, 2008, pp. 1524– 1532.
[3] D. Rosenkrantz, S. Goel, S. Ravi, and J. Gangolly, “Resilience metrics for service-oriented
networks: A service allocation approach,” IEEE Transactions on Services Computing, vol. 2, no.
3, pp. 183–196, 2009.
Index.html
<!DOCTYPE html>
<html ng-app="myapp">
<head>
<meta charset="utf-8">
<script src="vendor/modernizr/modernizr.js"></script>
<!--[if IE]>
<![endif]-->
<script src="vendor/respond/respond.js"></script>
<script src="vendor/excanvas/excanvas.js"></script>
<![endif]-->
<style>
.container {
background-color: #6b1991;
position:relative;
margin-top:100px;
.row{
margin-left:50px;
margin-right:50px;
text-align:center;
.login p{
position:relative;
text-align:center;
font-size:30px;
color:#ffffff;
p{
position:relative;
text-align:center;
font-family:'Quicksand';
font-size:35px;
color:#ffffff;
font-weight:200;
h2{
position:relative;
text-align:center;
font-size:30px;
color:#ffffff;
font-weight:200;
h3{
text-align:center;
font-size:80px;
color:#ffffff;
font-weight:200;
img{
align:middle;
</style>
<script src="cordova.js"></script>
<script>
function onLoad()
}
function deviceReady()
function backButtonCallback()
navigator.app.exitApp();
</script>
</head>
<script src="js/angular-1.3.js"></script>
<script src="js/angular_cookies.js"></script>
<body >
<div class="container">
<div class="row">
<div class="col-md-12">
<img style="width:450px;height:450px;margin-left:300px;"
class="img-responsive" src="images/wall.png">
</div>
</div>
<div class="login">
<a href="user_login.html">
<p>User Login</p>
</a>
</div>
<div class="login">
<a href="user_register.html">
<p>User Register</p>
</a>
</div>
<div class="login">
<a href="admin_login.html">
<p>Admin Login</p>
</a>
</div>
</div>
<script src="vendor/jquery/jquery.js"></script>
<script src="vendor/bootstrap/bootstrap.js"></script>
<script src="vendor/jquery.validation/jquery.validation.js"></script>
<script src="vendor/owlcarousel/owl.carousel.js"></script>
<script src="vendor/flexslider/jquery.flexslider-min.js"></script>
<script src="vendor/countdown/countdown.min.js"></script>
<script src="vendor/chosen/chosen.jquery.min.js"></script>
<script src="vendor/pricefilter/jquery.pricefilter.js"></script>
<script src="vendor/masonry/imagesloaded.pkgd.min.js"></script>
<script src="vendor/masonry/masonry.pkgd.min.js"></script>
<script src="vendor/uikit/uikit.js"></script>
<script src="vendor/magnific-popup/jquery.magnific-popup.js"></script>
<script src="js/theme.js"></script>
</body>
</html>
User_login.php
<?php
$response = array();
$data = json_decode(file_get_contents("php://input"));
$get_empid = ($data->email);
$get_password = ($data->password);
if(empty($get_empid) || empty($get_password))
$response["success"] = 2;
echo json_encode($response);
else
if (mysqli_num_rows($result))
$Allresponse = mysqli_fetch_array($result);
$response = array();
$response = $Allresponse;
$response["success"] = 1;
echo json_encode($response);
else
// success
$response["success"] = 0;
echo json_encode($response);
?>