Sahil Dmis Project

PROJECT ON
DISASTER MANAGEMENT
INFORMATION TECHNOLOGY
BABA BANDA SINGH BAHADUR POLYTECHNIC COLLEGE

FATEHGARH SAHIB
SUBMITTED TO: SUBMITTED BY:

Lect:- Er. Shweta verma SAHIL JHANJI
Reg No.007829006885
lakhvir Singh
Red No.007829007904
Karamjeet Singh
Reg No.007829006868
OBJECTIVE OF THE PROJECT
The objective of the project is to develop a Disaster Management
Information System (DMIS) .Disaster management has recently
increased in importance because of the growing awareness of costs
associated with disasters, both natural and man-made .It can provide
accurate information document on internet using HTML ,CSS &
Adobe Dreamweaver. This will help you to be aware of natural
calamities , man made disasters & also provide information on hazards,
vulnerability, and risk mapping, monitor, assess, forecast, and predict
natural .
Disaster management is a typically multi-disciplinary endeavor,

requiring various types of data with spatial and temporal attributes. It
cuts across many boundaries, including organizational, political,
geographic, professional, topical, sect oral and sociological. Lack of
critical and timely information for natural disasters is characteristic of
developing countries particularly those emerging from decades of war
and civil conflict; Afghanistan is not an exception. The Government of
Afghanistan is very much under-resourced; it relies heavily on the
humanitarian community particularly the UN in responding and
managing natural disasters. The country, like most other developing
countries does not have a disaster risk information management
capability to documents hazards, vulnerability, & risks at whatever
scale, including their characteristics, impacts, or related historical data.
Related data exists within some Government Departments in fragmented
formats, not in any structured computerized format, and not shared
amongst departments. This Pilot project aims at developing a Disaster
Management Information System (DMIS) for Afghanistan together with
building the capacity of DDP to maintain, update and disseminate
information to stakeholders and users for decision-making at multiple
levels.
The success of disaster management largely depends on
availability, dissemination and effective use of information. The
information needs will include current information on weather, climate,
infrastructure (roads, hospital, markets, administrative boundaries),
socio-economic data etc to use in assessing natural hazards. Currently,
such data are being generated by multiple users; government
departments, NGOs, the UN Agencies, and the private sectors. Data is
fragmented, stored in multiple locations, and formats, making it difficult
to bring together to support disaster management activities. In addition,
there is a need to assess the disaster in terms of location, extend and
likely impact so as plan relief and recovery actions.
Due to the limited duration of this pilot project, and the complex data
requirements of modeling most of the natural hazards such as
earthquakes, landslides, avalanches, and mudslides, this project will
focus on floods, erosion and drought.
Disaster management being a multi-disciplinary Endeavour would
require working with multiple stakeholders and users each with its own
interests. To be able to model the information needs of all stakeholders
and users in this pilot project would require a much longer time to
accomplish, thus this project will focus on key government ministries
such as Planning, Health, Agriculture etc.
Once the pilot project is successfully implemented, the need to develop a
National Disaster Management Information System covering all disaster
prone districts and provinces in the country becomes imperative.
Government is then able to reliable take action decisions based on
accurate and timely decisions. Information relating to the spatial and
temporal aspect of natural hazards, their characteristics, impacts and
frequencies of occurrence becomes common knowledge to a resilient
knowledge based communities.
Early Warning System
Cyclone Forecasting
Tropical Cyclones are intense low pressure systems which develop over
warm sea. They are capable of causing immense damage due to strong
winds, heavy rains and storm surges. The frequency of the TC in the Bay
of Bengal is 4 to 5 times more than in the Arabian Sea. About 35% of
initial disturbances in the north Indian ocean reach TC stage of which
45% become severe.
Flood Forecasting
Flooding is caused by the inadequate capacity within the banks of the
rivers to contain the high flow brought down from the upper catchments
due to heavy rainfall. It is also caused by accumulation of water
resulting from heavy spells of rainfall over areas, which have got poor
drainage characteristics
The following workflow hypotheses are made in respect of this project:

• Natural hazards may or may not occur in a community or district,
• There may be more than one natural hazards affecting a district,
• How much a district would loose as a result of the occurrence of a
natural hazard of a given
magnitude would depend on its vulnerability,
• Population, properties, and economic activities are at risk in any given
area,
• Many Ministries have specific units that deal with disaster
management,
• Disaster management information is required by multiple levels of
users,
• Natural hazards become disasters when they occur in areas with
population, properties, or
economic activities,
• When a major disaster occurs, lives, properties, economic activities
may be lost, damaged or
disrupted,
• Hazard connation maps are crucial information when considering
development projects
Disaster management is the process of

addressing an event that has the potential to seriously disrupt the social
fabric of the community. Disaster management is similar to disaster
mitigation, however it implies a whole-of-government approach to using
community resources to fight the effects of an event and assumes the
community will be self-sufficient for periods of time until the situation
can be stabilized. Through disaster management, we cannot completely
counteract the damage but it is possible to minimize the risks through
early warning, provide developmental plans for recuperation from the
disaster, generate communication and medical resources, and aid in
rehabilitation and post-disaster reconstruction.
The exchange of correct information following the event is important, in

order to ensure the resources necessary to support response and recovery
activities. The 72 hours following a major event is the most difficult
time because of a lack of coordination among relief organizations.
Problems that interrupt rather than coordinate the rescue efforts of all
groups involved often occur because of hasty decision-making under
complicated circumstances and the large number of organizations, which
are unsure of their roles during operations.
Disaster management is essentially a development problem and thus

any preparedness and mitigation planning will have to be taken up in
tandem with environmental concerns that the country is facing
today.The Government of India has set up a National Committee on
Disaster Management (NCDM) under the Chairmanship of the Prime
Minister. The recommendations of this National Committee would form
the basis of national disaster risk management programme and
strengthening the natural disaster management and response
mechanisms. The High Powered Committee [HPC] on Disaster
Management Plans was earlier constituted in August 1999. The mandate
of the HPC was to prepare Disaster Management Plans at national, State
and district level and also suggest strengthening of existing
arrangements. The recommendations of the HPC relating to the
distribution of relief and human resource development that primarily
concerns the States have been communicated to the States for
appropriate action. The Ministry of Home Affairs in the National
Government is the new nodal ministry for disaster management.
Disaster management is deemed to be a ‘state subject’ and different

states have initiated efforts to strengthen their agencies responsible for
disaster management. Orissa State Disaster Mitigation Authority and
Gujarat State Disaster Management Authority are constituted after two
major disasters that the respective states have experienced.
Feasibility Study
Feasibility study is conducted on the basis of initial study of the system. It is
the second phase of system development life cycle. It is basically the test of
the proposed system in the light of its workability, meeting user’s
requirements, and effective use of resources and the cost effectiveness of
system. The main purpose of feasibility study is not to solve the problem but
to achieve the scope. In the process of feasibility study, the cost and benefits
are estimated with greater accuracy.
The feasibility study focuses on three main questions:

1. What are the user demonstrable needs and how does a proposed system
them?
2. What resources are available for the system under consideration? Is the
problem worth solving?
3. What are the likely impact of the system under consideration on the
organization? How well the system under consideration will fit within the
organization’s management information system plan?
The feasibility study must answer these questions carefully. They revolve
around evaluation and investigation of the problem. This investigation may
propose one or more systems. The best system is selected as proposed system
depending upon the specification of performance and cost of the system.
A Feasibility Study is the analysis of a problem to determine if it can be

solved effectively. The results determine whether the solution should be
implemented. This activity takes place during the project initiation phase
and is made before significant expenses are engaged.
Use this template to:
• Perform a preliminary study to determine a project's viability.

• Analyze an existing system to see if it is worth upgrading.
• Determine if there is sufficient time to build the new system, when
it can be built, whether it interferes with operations, type and
amount of resources required, dependencies, etc.
• Establish the cost-effectiveness of the proposed system.
• Determine if the system conflicts with legal requirements.
A feasibility study is an evaluation of a proposal designed to determine

the difficulty in carrying out a designated task. Generally, a feasibility
study precedes technical development and project implementation. In
other words, a feasibility study is an evaluation or analysis of the
potential impact of a proposed project.
Five common factors (TELOS)
Technology and system feasibility
The assessment is based on an outline design of system requirements in

terms of Input, Processes, Output, Fields, Programs, and Procedures.
This can be quantified in terms of volumes of data, trends, frequency of
updating, etc. in order to estimate whether the new system will perform
adequately or not. Technological feasibility is carried out to determine
whether the company has the capability, in terms of software, hardware,
personnel and expertise, to handle the completion of the project.
Economic feasibility
Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as cost/benefit
analysis, the procedure is to determine the benefits and savings that are
expected from a candidate system and compare them with costs. If
benefits outweigh costs, then the decision is made to design and
implement the system. An entrepreneur must accurately weigh the cost
versus benefits before taking an action.
Cost Based Study: It is important to identify cost and benefit factors,
which can be categorized as follows: 1. Development costs; and 2.
Operating costs. This is an analysis of the costs to be incurred in the
system and the benefits derivable out of the system.
Time Based Study: This is an analysis of the time required to achieve a

return on investments. the benefits derived from the system. The future
value of a project is also a factor.
Legal feasibility
Determines whether the proposed system conflicts with legal

requirements, e.g. a data processing system must comply with the local
Data Protection Acts.
Operational feasibility
Is a measure of how well a proposed system solves the problems, and

takes advantages of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements
analysis phase of system development.[1]
Schedule feasibility
A project will fail if it takes too long to be completed before it is useful.

Typically this means estimating how long the system will take to
develop, and if it can be completed in a given time period using some
methods like payback period. Schedule feasibility is a measure of how
reasonable the project timetable is. Given our technical expertise, are the
project deadlines reasonable? Some projects are initiated with specific
deadlines. You need to determine whether the deadlines are mandatory
or desirable...
Other feasibility factors

Market and real estate feasibility
Market Feasibility Study typically involves testing geographic locations

for a real estate development project, and usually involves parcels of real
estate land. Developers often conduct market studies to determine the
best location within a jurisdiction, and to test alternative land uses for
given parcels. Jurisdictions often require developers to complete
feasibility studies before they will approve a permit application for
retail, commercial, industrial, manufacturing, housing, office or mixed-
use project. Market Feasibility takes into account the importance of the
business in the selected area.
Resource feasibility
This involves questions such as how much time is available to build the
new system, when it can be built, whether it interferes with normal
business operations, type and amount of resources required,
dependencies, etc. Contingency and mitigation plans should also be
stated here.
Cultural feasibility
In this stage, the project's alternatives are evaluated for their impact on
the local and general culture. For example, environmental factors need
to be considered and these factors are to be well known. Further an
enterprise's own culture can clash with the results of the project.
Output
The feasibility study outputs the feasibility study report, a report

detailing the evaluation criteria, the study findings, and the
recommendations.[2]
Software requirement Specification
The system requirements specify what is expected by the users of the system
from the system itself. The system requirements specify the functioning and
properties of the system to be developed. There are two types of system
requirements:
1. Functional Requirements: System requirements that specify what the

information system must do are frequently referred to as functional
requirements. In other words, the requirements related to the functioning of
the system are called functional requirements. The example of functional
requirement may be” the system should print the invoice of each sale
transaction.”
2. Non-functional Requirements: System requirements that specify

properties or qualities, which must be contain in the system, are called non-
functional requirements. The example of non-functional requirements may
be” The system should increase the number of invoices generated in a
working day”.
Purpose of Requirements Discovery
The main purpose of requirement discovery and management is to correctly

identify the knowledge, process and communication requirements for the
usres of the new system. Failure to correctly identify system requirements
may result in one or more of the following:
1. The system may cost more than projected .

2. The system may be delivered later than promised.
3. The system may not meet the users expectations.
4. The system may be reliable and prone to errors and downtime.
The process of requirements discovery consists of the following activities:
1. Problem discovery and analysis.

2. Requirement discovery
3. Documenting and analyzing requirements.
4. Requirements management.
Here's the scenario: You're finishing up your latest HTML Help

project...no more late nights or weekends...back to a "normal" 50-hour
work week. That's when the development team lead strolls into your
office and says she just got your manager's okay for you to help the
development team "put together the functional requirements
specification template for the next major project."
"A what?" you ask with a look of semi-shock. Panic sets in. "What did I
do to deserve this? I don't even know where to start! Maybe someone on
the TECHWR-L list can help...."
For technical writers who haven't had the experience of designing

software requirements specifications (SRSs, also known as software
functional specifications or system specifications) templates or even
writing SRSs, they might assume that being given the opportunity to do
so is either a reward or punishment for something they did (or failed to
do) on a previous project. Actually, SRSs are ideal projects for technical
writers to be involved with because they lay out the foundation for the
development of a new product and for the types of user documentation
and media that will be required later in the project development life
cycle. It also doesn't hurt that you'd be playing a visible role in
contributing to the success of the project.
This article will describe what an SRS is and why it's important, discuss
how and why technical writers should be involved with them, and
discuss the critical elements for writing an SRS. Although this article
does not attempt to address all aspects of developing SRSs, it aims to
help you determine the scope for such a project, to provide some
guidelines for writing SRSs, and to provide additional resources.
Hopefully with this information, you'll not be asking, "Why me?" but
proclaiming "Why not me?"
What is a Software Requirements Specification?

An SRS is basically an organization's understanding (in writing) of a
customer or potential client's system requirements and dependencies at a
particular point in time (usually) prior to any actual design or
development work. It's a two-way insurance policy that assures that both
the client and the organization understand the other's requirements from
that perspective at a given point in time. The SRS document itself states
in precise and explicit language those functions and capabilities a
software system (i.e., a software application, an eCommerce Web site,
and so on) must provide, as well as states any required constraints by
which the system must abide. The SRS also functions as a blueprint for
completing a project with as little cost growth as possible. The SRS is
often referred to as the "parent" document because all subsequent project
management documents, such as design specifications, statements of
work, software architecture specifications, testing and validation plans,
and documentation plans, are related to it. It's important to note that an
SRS contains functional and nonfunctional requirements only; it doesn't
offer design suggestions, possible solutions to technology or business
issues, or any other information other than what the development team
understands the customer's system requirements to be. A well-designed,
well-written SRS accomplishes four major goals:
• It provides feedback to the customer. An SRS is the

customer's assurance that the development organization
understands the issues or problems to be solved and the
software behavior necessary to address those problems.
Therefore, the SRS should be written in natural language
(versus a formal language, explained later in this
article), in an unambiguous manner that may also include
charts, tables, data flow diagrams, decision tables, and so
on.
• It decomposes the problem into component parts. The
simple act of writing down software requirements in a
well-designed format organizes information, places borders
around the problem, solidifies ideas, and helps break down
the problem into its component parts in an orderly
fashion.
• It serves as an input to the design specification. As
mentioned previously, the SRS serves as the parent document
to subsequent documents, such as the software design
specification and statement of work. Therefore, the SRS
must contain sufficient detail in the functional system
requirements so that a design solution can be devised.
• It serves as a product validation check. The SRS also
serves as the parent document for testing and validation
strategies that will be applied to the requirements for
verification.
SRSs are typically developed during the first stages of
"Requirements Development," which is the initial product
development phase in which information is gathered about what
requirements are needed--and not. This information-gathering
stage can include onsite visits, questionnaires, surveys,
interviews, and perhaps a return-on-investment (ROI) analysis
or needs analysis of the customer or client's current business
environment. The actual specification, then, is written after
the requirements have been gathered and analyzed.
Why Should Technical Writers be Involved with Software
Requirements Specifications?
Unfortunately, much of the time, systems architects and
programmers write SRSs with little (if any) help from the
technical communications organization. And when that assistance
is provided, it's often limited to an edit of the final draft
just prior to going out the door. Having technical writers
involved throughout the entire SRS development process can
offer several benefits:
• Technical writers are skilled information gatherers,
ideal for eliciting and articulating customer requirements.
The presence of a technical writer on the
requirements-gathering team helps balance the type and
amount of information extracted from customers, which can
help improve the SRS.
• Technical writers can better assess and plan
documentation projects and better meet customer document
needs. Working on SRSs provides technical writers with an
opportunity for learning about customer needs
firsthand--early in the product development process.
• Technical writers know how to determine the questions
that are of concern to the user or customer regarding ease
of use and usability. Technical writers can then take that
knowledge and apply it not only to the specification and
documentation development, but also to user interface
development, to help ensure the UI (User Interface) models
the customer requirements.
• Technical writers, involved early and often in the
process, can become an information resource throughout the
process, rather than an information gatherer at the end of
the process.
In short, a requirements-gathering team consisting solely of
programmers, product marketers, systems analysts/architects,
and a project manager runs the risk of creating a specification
that may be too heavily loaded with technology-focused or
marketing-focused issues. The presence of a technical writer on
the team helps place at the core of the project those user or
customer requirements that provide more of an overall balance
to the design of the SRS, product, and documentation.
What Kind of Information Should an SRS Include?
You probably will be a member of the SRS team (if not, ask
to be), which means SRS development will be a collaborative
effort for a particular project. In these cases, your company
will have developed SRSs before, so you should have examples
(and, likely, the company's SRS template) to use. But, let's
assume you'll be starting from scratch. Several standards
organizations (including the IEEE) have identified nine topics
that must be addressed when designing and writing an SRS:
1. Interfaces
2. Functional Capabilities
3. Performance Levels
4. Data Structures/Elements
5. Safety
6. Reliability
7. Security/Privacy
8. Quality
9. Constraints and Limitations
But, how do these general topics translate into an SRS
document? What, specifically, does an SRS document include? How
is it structured? And how do you get started? An SRS document
typically includes four ingredients, as discussed in the
following sections:
1. A template
2. A method for identifying requirements and linking sources
3. Business operation rules
4. A traceability matrix
Begin with an SRS Template
The first and biggest step to writing an SRS is to select an
existing template that you can fine tune for your
organizational needs (if you don't have one already). There's
not a "standard specification template" for all projects in all
industries because the individual requirements that populate an
SRS are unique not only from company to company, but also from
project to project within any one company.
HARDWARE REQUIREMENTS
HARDWARE
The term hardware is used to represent physical and

tangible components of the computer. The hardware
component is: -
1 Input unit
Input unit is responsible for feeding instruction and
data in computer. In general, a simple keyboard is used
as input device. The main functions of input unit are
Input instruction to the CPU.
Work as interface between outside world and

computer.
Change instruction given by human in high language to

machine or low language.
2. Central Processing Unit:-
CPU of the computer controls the interpretation and

execution of the instructions. it is called the brain of the
computer. It is divided into three parts. Memory Unit,
Arithmetic And logical Unit, Control Unit.
3.Memory Unit is used for storing any input from

input unit.
All the arthmatrical and logical operations take place

in arithmetic and logical unit.
Control Unit controls all the operations so it is called

Central Nerve of the computer.
3. Output Unit
Output unit device is used for outputting the result to

user. In most of the computer VDU i.e. Visual Display Unit
is used as an output Device. A printer can also be used as
an outside device.
Hardware Requirement For the Project
1. CPU
2. Random Access Memory
3. Monitor
4. Keyboard
5. Mouse
SOFTWARE REQUIREMENTS
1. Operating System
2. Microsoft Word
3. Notepad
4. Internet Explorer
5. Abobe photoshop cs4
LITERATURE SURVEY
HYPERTEXT MARKUP LANGUAGE (HTML) :
HTML is a language used to describe the structure of

web page. A web page has some common attributes like heading,
paragraph text, list bullets, footers, images and lot more. A web page can
have a specific style of using these attributes. In web page, the text can
be marked as header, paragraph, list bullets or footer by using tags.
HTML, which stands for HyperText Markup Language, is the
predominant markup language for web pages. It provides a means to
create structured documents by denoting structural semantics for text
such as headings, paragraphs, lists etc as well as for links, quotes, and
other items. It allows images and objects to be embedded and can be
used to create interactive forms. It is written in the form of HTML
elements consisting of "tags" surrounded by angle brackets within the
web page content. It can include or can load scripts in languages such as
JavaScript which affect the behavior of HTML processors like Web
browsers; and Cascading Style Sheets (CSS) to define the appearance
and layout of text and other material. Tags are used to mark a block of
text in html page. It is language interpreted by browser.
HTML HEADINGS :
Headings are defined with the <h1> to <h6> tags.<h1>

defines the largest heading. <h6> defines the smallest heading.
HTML TABLES :
TABLES
Tables are defined with the <table> tag. A table is divided

into rows (with the <tr> tag), and each row is divided into data cells
(with the <td> tag). The letters td stands for "table data," which is the
content of a data cell. A data cell can contain text, images, lists,
paragraphs, forms, horizontal rules, tables, etc.
<table border="1">
<tr>
<td>row 1, cell 1</td>
</tr>
<tr>
</tr>
</table>
FEATURES OF HTML ARE :
• Document formatting uses various typeface styles, range of

headlines & new features called frames.
• Hyperlinks capability to include hyperlinks that points to other
web documents, multimedia files or services on computer
systems over the internet.
• List layout a wide range of list layout capabilities.
• Tables capability to create tables & preformatted text.
• Images capability to embedded graphics images right in an
html document which can be hyperlinks to other documents.
• Image maps clickable image maps without spots to take you
various places depending on where in the image you are
clicked.
HTML FRAMES :
FRAMES
With frames, you can display more than one HTML document in the
same browser window. Each HTML document is called a frame, and
each frame is independent of the others.
The disadvantages of using frames are:
• The web developer must keep track of more HTML documents

• It is difficult to print the entire page
THE FRAMESET TAG
• The <frameset> tag defines how to divide the window into frames
• Each frameset defines a set of rows or columns
• The values of the rows/columns indicate the amount of screen area
each row/column will occupy
THE FRAME TAG
• The <frame> tag defines what HTML document to put into each
frame
In the example below we have a frameset with two columns. The first
column is set to 25% of the width of the browser window. The second
column is set to 75% of the width of the browser window. The HTML
document "frame_a.htm" is put into the first column, and the HTML
document "frame_b.htm" is put into the second column:
HTML FORMS :
FORMS
A form is an area that can contain form elements.

Form elements are elements that allow the user to enter information (like
text fields, textarea fields, drop-down menus, radio buttons, checkboxes,
etc.) in a form.
A form is defined with the <form> tag.
INPUT
The most used form tag is the <input> tag. The type of input is specified
with the type attribute. The most commonly used input types are
explained below.
Text Fields
Text fields are used when you want the user to type letters, numbers, etc.
in a form.
Coding
Front page coding
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">

<table width="1100" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td width="1100" height="62"
bgcolor="#FFFFFF"> </td>
</tr>
</table>
cellpadding="0">
<tr>
<td width="86" height="37" bgcolor="#FFFFFF"> </td>
<td width="776" height="37" bgcolor="#FFFFFF"><img
src="images/ypper-lnk.jpg" width="776" height="37"
usemap="#Map" border="0"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/ctuys.jpg" width="1026" height="36"
usemap="#Map2" border="0"></td>
</tr>
</table>
cellpadding="00">
<tr>
src="images/uplay.jpg" width="1026" height="106"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/lks.jpg" width="1026" height="40" border="0"
usemap="#Map3"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/ct.jpg" width="1026" height="229"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/rdmr.jpg" width="1026" height="35" border="0"
<td height="35" bgcolor="#FFFFFF"> </td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/cth.jpg" width="1026" height="181"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/rdmh.jpg" width="1026" height="42" border="0"
</tr>
</table>
cellpadding="0">
<tr>
src="images/end.jpg" width="1026" height="158"></td>
</tr>
</table>
<map name="Map">
<area shape="rect" coords="16,7,97,26" href="floog.htm"
target="_parent">
<area shape="rect" coords="636,7,760,25" href="earth.htm"
target="_parent">
</map>
<map name="Map2">
<area shape="rect" coords="822,8,912,29" href="cyus.htm"
target="_parent">
</map>
<map name="Map3"><area shape="rect"

coords="139,10,189,27" href="index.htm" target="_parent"
alt="">
<area shape="rect" coords="211,8,260,27" href="types.htm"
target="_parent">
<area shape="rect" coords="284,11,345,27" href="#"
target="_parent">
target="_parent">
<area shape="rect" coords="450,9,551,30" href="perepad.htm"
target="_parent">
<area shape="rect" coords="575,9,659,27"
href="mitigation.htm">
<area shape="rect" coords="685,6,746,29" href="gallary.htm"
target="_parent">
target="_parent">
</map>
coords="535,5,624,31" href="http://ndmindia.nic.in/"
target="_parent">
</map>
coords="799,2,886,43" href="http://ndmindia.nic.in/"
target="_blank">
</map></body>
</html>
2nd page types coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/ypper-lnk.jpg" width="776" height="37" border="0"
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/ctuys.jpg" width="1026" height="36" border="0"
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/cntrr.jpg" width="1026" height="270"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/cnterd.jpg" width="1026" height="224"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
<map name="Map"><area shape="rect" coords="14,9,95,27"

href="floog.htm" target="_parent">
target="_parent">
</map>
coords="824,9,915,33" href="earth.htm" target="_parent">
</map>
coords="138,8,193,31" href="index.htm" target="_parent">
target="_parent">
<area shape="rect" coords="284,9,344,29" href="causes.htm"
target="_parent">
<area shape="rect" coords="366,9,430,30" href="impact.htm"
target="_parent">
href="perepad.htm" target="_parent">
href="mitigation.htm" target="_parent">
target="_parent">
target="_parent">
</map></body>
</html>
3rd page causes coding
<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/causej.jpg" width="1026" height="272"></td>
</tr>
</table>
cellpadding="0">
<tr>
src="images/cnterf.jpg" width="1026" height="213"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>

target="_parent">
</map>
coords="824,8,915,30" href="#"></map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_top">
</map></body>
</html>
4th page impact coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/impact.jpg" width="1026" height="494"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
coords="822,6,917,33" href="cyus.htm" target="_parent">
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
</map></body>
</html>
5th page preparedness coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/prepaidness.jpg" width="1026"
height="494"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_self">
</map></body>
</html>
6th page mitigation coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/mitigation.jpg" width="1026" height="494"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_blank">
</map></body>
</html>
7th page gallery coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/gallary.jpg" width="1026" height="494"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_blank">
</map></body>
</html>
8th page contact us coding
<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/contcy-us_.jpg" width="1026" height="482"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
</map></body>
</html>
9th page Haiti earthquake

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/hittati.jpg" width="1026" height="490"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
</map></body>
</html>
10th page flood 2009 coding

<html>
<head>
</head>

cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
usemap="#Map"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="00">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
cellpadding="0">
<tr>
src="images/flood.jpg" width="1026" height="529"></td>
</tr>
</table>
cellpadding="0">
<tr>
</tr>
</table>
target="_parent">
</map>
</map>
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
target="_parent">
</map></body>
</html>
Reference
We have collected our precious data from various sources to make a
performance-oriented project.
That sources are following:--
 Internet sites like
http://www..com

Sahil Dmis Project

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sahil Dmis Project

Transféré par

Droits d'auteur :

Formats disponibles

PROJECT ON

BABA BANDA SINGH BAHADUR POLYTECHNIC COLLEGE

SUBMITTED TO: SUBMITTED BY:

Disaster management is a typically multi-disciplinary endeavor,

The following workflow hypotheses are made in respect of this project:

Disaster management is the process of

The exchange of correct information following the event is important, in

Disaster management is essentially a development problem and thus

Disaster management is deemed to be a ‘state subject’ and different

The feasibility study focuses on three main questions:

A Feasibility Study is the analysis of a problem to determine if it can be

Use this template to:

• Perform a preliminary study to determine a project's viability.

A feasibility study is an evaluation of a proposal designed to determine

Five common factors (TELOS)

Technology and system feasibility

The assessment is based on an outline design of system requirements in

Time Based Study: This is an analysis of the time required to achieve a

Determines whether the proposed system conflicts with legal

Is a measure of how well a proposed system solves the problems, and

A project will fail if it takes too long to be completed before it is useful.

Other feasibility factors

Market Feasibility Study typically involves testing geographic locations

The feasibility study outputs the feasibility study report, a report

1. Functional Requirements: System requirements that specify what the

2. Non-functional Requirements: System requirements that specify

Purpose of Requirements Discovery

The main purpose of requirement discovery and management is to correctly

1. The system may cost more than projected .

1. Problem discovery and analysis.

Here's the scenario: You're finishing up your latest HTML Help

For technical writers who haven't had the experience of designing

What is a Software Requirements Specification?

• It provides feedback to the customer. An SRS is the

The term hardware is used to represent physical and

Input instruction to the CPU.

Work as interface between outside world and

Change instruction given by human in high language to

2. Central Processing Unit:-

CPU of the computer controls the interpretation and

3.Memory Unit is used for storing any input from

All the arthmatrical and logical operations take place

Control Unit controls all the operations so it is called

Output unit device is used for outputting the result to

Hardware Requirement For the Project

HYPERTEXT MARKUP LANGUAGE (HTML) :

HTML is a language used to describe the structure of

Headings are defined with the <h1> to <h6> tags.<h1>

Tables are defined with the <table> tag. A table is divided

• Document formatting uses various typeface styles, range of

The disadvantages of using frames are:

• The web developer must keep track of more HTML documents

THE FRAMESET TAG

THE FRAME TAG

A form is an area that can contain form elements.

A form is defined with the <form> tag.

<body bgcolor="#FFFFFF" text="#000000">

<map name="Map3"><area shape="rect"

2nd page types coding

<body bgcolor="#FFFFFF" text="#000000">

<map name="Map"><area shape="rect" coords="14,9,95,27"

3rd page causes coding

<body bgcolor="#FFFFFF" text="#000000">