Geographical Information System (GIS) in Environmental Impact Assessment

NB: We do not resell your papers. Upon ordering, we do an original paper exclusively for you.

NB: All your data is kept safe from the public.

Table of Contents

Introduction
Statement of Work
User Interface Design
Database Design
Project Management and Alternatives
Discussion
Bibliography

Introduction

The use of Geographical Information System (GIS) is prevalent in environmental impact assessment. Specifically, GIS serves as a mechanism in detecting outcomes of flooding and devising strategies to prevent further damages. Basically, GIS has been proposed to be used in mitigating the flood hazard at the Manawatu River in Foxton Beach. Technically, GIS is a computer system packed with multiple capabilities and designed to display information referenced to geography. (Chang, 2005) GIS enables users to create interactive queries, analyze spatial information, and edit the gathered data. Aside from the mentioned use, the system has been extensively employed in other fields.

The nature of the GIS suggests that it requires a system to function with efficiency. Therefore, discussing GIS necessitates the focus of systems design. Significantly, systems designs refer to the process of defining the hardware and software architecture, components, modules, interfaces, and data needed for the GIS to meet a specific requirement. According to Booch (1994), the object-oriented analysis designed is often preferred to analyze systems requirements. Indeed, systems design is a critical stage that contributes to the feasibility of GIS in the project and eventually the capability of the project to mitigate flood hazards.

During the course of the discussion, this presentation attempts to define the elements of systems design. The ultimate goal of the research is to formulate a systems design using the capabilities of GIS. In particular, the interfaces and other design options will be analyzed. Several frameworks and diagrams will be included to fully grasp the idea of systems design in the project. The processes will be thoroughly illustrated and details will be comprehensively explained.

Statement of Work

It has been well-documented that tsunamis are unpredictable in nature. Constant movements beneath the earth have caused jolts and negatively affect seas and oceans. Although there is a quality instrument to detect such movements, the unpredictability of such occurrences has made tsunami detection hard for local authorities. When the world witnessed the tsunami that swept Indonesia, Thailand, and other countries, the aim of providing systems that accurately detect tsunami has intensified. Efforts coming from local authorities and concerned private groups have also been improved because resistance to tsunami effects has become highly imperative.

Tsunami detection is a demanding task. It requires expertise both on the technical side and the management of components. Using the GIS in the mainstream of activities is highly valuable. The use of GIS will restore order in the manner in which tasks are undertaken. The presence of GIS will improve the efficiency of entities involved in such endeavors. Time is a vital element it requires to be consumed efficiently in all activities involving GIS. The main argument used by GIS users is that the mechanism can store information. GIS through the database recognizes vital information and records the data.

The unprecedented changes in GIS coupled with the emphasis on the use of such mechanisms continue to gain recognition. Applying GIS in mitigating tsunami hazards has been observed in different places. This realization has paved the way for the authorities in Foxton Beach to employ GIS as its core mechanism in preventing damages caused by the tsunami. This concern has been considered as immediate and requires rigorous planning before being implemented. The process is critical because success is based on proper planning and foresight.

The project is expected to be implemented in the long term. Installing the GIS system is geared towards permanency. The process starts with the initial canvassing of cost. Since the public sector will implement the project, bidding will be followed. After the contractor has been commissioned, the system will be tested before being installed. To provide a target, the project is expected to be completed 90 days after the bidding process is completed. A total of 6 months is allotted for the implementers to ensure that the GIS is installed and maintained.

There are certain aspects that need to be assessed and obtained to ensure success. In the project process, there are fundamental considerations that have to be made. GIS will be primarily embedded in software and be used in preliminary activities in particular data gathering. GIS will be the primary source of information as well as the mechanism used to store data. It is best that the Foxton Beach authorities use upgraded GIS including all necessary equipment. The process of installing GIS involves several changes. This will allow the authorities to shape GIS according to the prescribed use.

The authorities have to determine the person who will be involved with the study. The process requires human intervention that will check and maintain the infrastructures and instruments needed for the project. There are two basic kinds of personnel needed. The management personnel will be tasked to oversee the needs of the project including acquisition and support. The second group composes the technical team. Technical personnel is directly in charge of the manifestation of the project. It is important to address the need for cooperation in the process of undertaking the project.

The authorities have to determine the budget allocated for the project. Financial flexibility is a vital necessity for the project. For the authorities, identifying the costs of components is imperative. It allows the person to map their activities to efficiently use the equipment. In addition, the budget enables the personnel in-charge in different activities to discuss possible changes and improvements that need to be emphasized after the performance is evaluated.

User Interface Design

The experience and interaction of users are vital in creating innovations. Thus, the user interface design was created to address such needs. Actually, user interface design is procedural and consists of several processes. The first stage pertains to the functionality requirements gathering, which assembles a list of the functionality required to achieve the aims of the project and to satisfy the needs of the users. User analysis refers to the possible users of the system. This is undertaken through the discussion with individuals working with the users or directly with the users. In the discussions, several questions are raised to further promote the use of the system.

User interface design also involves information architecture that refers to the development of the system information flow. Moreover, prototyping entails the devising of wireframes through paper prototypes or simple interactive screens. Also, usability testing requires testing of the prototype to the actual user and often involves users talking about their experiences. The graphic interface design details the actual look and feel of the final graphic user interface based on the results developed during the usability testing. The last premise is tackled separately by a graphic designer who has knowledge in interface design.

Before making the final user interface design, it is imperative to consider some fundamental principles to achieve efficacy. Constantine and Lockwood (1999) provide some important considerations to produce quality user interface design. Holistically, the different principles involve the structure principle; the simplicity principle; the visibility principle; the feedback principle; the tolerance principle; and the reuse principle. These are vital considerations that contribute to the efficiency of the system design.

User interface prototyping is an iterative analysis technique in which users are actively involved in the mocking-up of the user interface for a system. (Ambler, 2001) The specific purpose of the use prototype interface includes an analysis artifact that enables you to explore the problem space with your stakeholders; a design artifact that enables you to explore the solution space of your system; a vehicle for you to communicate the possible user interface design of your system; and a potential foundation from which to continue developing the system. The development of a prototype involves procedures. Initially, the user interface needs of the users. This is followed by the creation of the prototype and eventually the evaluation of the prototype.

The final user interface prototype involves the different attributes that the system aims to have. Basically, the system has to enable users to navigate the area concerned. In this situation, users are allowed to view the Manawatu River in three levels. First, users can view the entire river through aerial navigation. The base-level provides a clearer view of the major parts of the river. The third level is the most specific as details of river components can be observed. Information is also present in the prototype, which includes satellite pictures, videos of the river, statistics on flooding, and texts on past projects.

Aside from the physical appearance, the prototype uses several software and applications. This will enable the system to be accessed on the Internet. It is important for the users to have a varied view of the parts of the river. Also, the available information will supplement the findings of the users after observations are made. The GIS is crucial in providing the basis for users to recommend certain projects such as constructions of dikes to mitigate flooding effects in the Manawatu River.

Database Design

In creating systems design, databases are fundamental. The process of producing a detailed data model of a database is referred database design. The model has all necessary logical and physical and physical design choices and physical storage parameters that will produce a design in the Data Definition Language. Usually, database design is described as the logical design of the base data structures used to store the data. Database design, however, is applicable in the entire process of designing that covers base data structures and forms and queries used as part of the overall database application.

Database design follows procedures that are divided into stages. All phases are, however, used depending on the requirement of the objectives. Generally, database design has to identify the data to be stored in the database, ascertain the relationships among the various data elements, and superimpose as logical structure upon the data based on the determined relationships. Database design has to ensure that the universal functions of databases include: the retrieval of all data to match in different criteria; updating of records in bulk; cross-referencing records in different tables; and performing complex aggregate calculations.

The Entity-Relationship Diagram (ERD) appears to be a useful instrument in developing database design for the project. Accordingly, ERD is used to create quality database structures and for efficiency in storing and retrieving information. The process is simple as the entities involved in the project have to be identified. Then, the designer of the database will determine the level of relationships between entities. The ERD is drawn and subsequent stages are undertaken.

Table 1: Entity Relationship Matrix

	LGU	Lead Agency	Residents	NGOs	Project
LGU		Supervise	Assigns	Works with	Heads the
Lead Agency	Under the		Supervise	Works with	Works on
Residents	Assigned by	Under the		Works with	Works on
NGOs	Under the	Works with	Works with		Works on
Project	Heads the	Uses	Uses	Uses

In the project, the following entities are considered as major and minor contributors: the local government, the implementing agency; the non-government organizations, and the residents affected by flooding. These entities are related and a relationship matrix (see Table 1) details the actual relationship of each entity. The ERD (see figure below) links all the entities and provides a clear picture of the manner in which these entities contribute to the database design. Then, key-based ERD is drawn, which is crucial in identifying the attributes. Map attributes are created and the combined illustrations will show the fully attributed ERD. It is important to note that the results are evaluated and checked.

Chapple (2006) provided several options in normalizing the database. The normalization of databases is referred to as the normal form and is numbered from one, which is the lowest form of normalization to four, which is the highest. The first part eliminates duplicate columns in the same table. The second stage removes the subsets of data that apply to multiple rows of a table and place them in separate tables. The third stage removes the columns that are not dependent upon the primary key. In the final stage there has to be no multi-valued dependencies and requirements from the third stage have all been satisfied.

In developing a database for the GIS, it is imperative to determine the sources of data. The information has to be accurate and requires less spending when transferred to the database. Moreover, the conceptual design of the database is to be converted to a logical design. In addition, the designers have to define the procedures in creating the database structure. Lastly, the procedures for managing and maintaining the database have to be clearly defined.

Project Management and Alternatives

Class diagrams are part of the object-oriented analysis and design. Basically, class diagrams show the classes of the system, their interrelationships, and the operations and attributes of the classes. Class diagrams are used for a wide variety of purposes, including both conceptual and domain modeling and detailed design modeling. Rumbaugh (1991) stated that class diagrams depict the classes within a model. Normally, classes have attributes, operations, and relationships, with other classes. A class icon represents the fundamental element of the class diagram. Class icons are divided into compartments each with a unique and useful purpose.

In developing class diagrams, the following concepts have to be considered: classes, responsibilities; associations; inheritance relationship; composition association; and interfaces. The class is resenting the object being and the template for its creation. Objects have responsibilities to fulfill and subsequent associations for affiliations. This establishes the relationships among objects discussed. Inheritance relationship shows that similar attributes of objects that contribute to the reduction of task performed. It is also possible that objects are made of other objects. In this situation, composition association comes into the picture. (Ambler, 2001).

Sequence diagrams model the flow of logic within the system visually; thus, enabling users to both documents and validate logic. This is commonly used for both analysis and design purposes. Sequence diagrams are the most popular UML artifact for dynamic modeling, which focuses on identifying the behavior within the system. Other dynamic modeling techniques include activity diagramming, communication diagramming, timing diagramming, and interaction overview diagramming.

A sequence diagram normally illustrates the interaction between objects over the progression of time. Hence, the first symbol required is that to represent an object. A lifeline is drawn which appears in a vertical dashed line indicating the instance and class names in the standard UML format. In order to display interaction, messages are used. These are horizontal arrows with the message name written above them. Solid arrows with full heads are synchronous calls, solid arrows with stick heads are asynchronous calls, and dashed arrows with stick heads are return messages. A message sent from outside the diagram can be represented by a message originating from a filled-in circle. (Ambler, 2001)

A data flow diagram (DFD) is a graphical representation of the flow of data through an information system. A data flow diagram can also be used for the visualization of data processing Data flow diagram (DFD) is one of the three significant perspectives of SSADM. (DeMarco, 1978) The initiator of a project and the end-users will need to be briefed and consulted throughout all stages of a system’s evolution. With a data flow diagram, users can visualize all the elements needed in a system. Moreover, DFD can be used to provide the end-user with a physical idea of the location where data is inputted. This eventually affects the structure of the whole system.

The components of DFD are composed of the following; external entities that are outside of the system; processes, which modify the inputs to obtain the desired outputs; data stores where the information comes to rest; and data flows that show the movement of the information between the other components. Developing DFD comes in different approaches. The top-down approach is commonly used, although the event partitioning approach has become a prominent alternative.

Discussion

The goal of the project is to use the GIS as a tool that will help in mitigating flood hazards. In doing so, the project requires the development of a system that will define the specific functions of the GIS. The users have to use the GIS in acquiring the information needed to recommend some concrete actions related to flood control. The user interface model using the GIS enables the users to access the4 general and specific details related to the river. The gathered information will be processed and inputted into a database.

Before creating the database, the different entities have to be identified. In the previous discussions, it was mentioned that there are four entities involved in the project. These are expected to relate as the project commences. The relationship established is crucial between entities will determine the extent of database usefulness. It has to be noted that the entities produce the information needed. Also, the harmony between entities is critical for the success of the project. In creating databases, the use of software and other applications is important. This will ensure that systems are efficient and function with high reliability.

The process and code designs specifically outline the tasks that the system will perform. To determine the role of the system, diagrams have to be provided. It is indeed important to secure the relationship, logic, and interaction of the various components of the system. The diagrams show the capacity of the system to succeed and the areas where improvements have to be made. This vital process culminates with the completion of the systems design and the next step involves the GIS implementation.

Bibliography

Ambler, S. (2001) The Object Primer, 3^rd edition. Cambridge, UK: Cambridge University Press.

Booch, G. (1994). Object-oriented analysis and design with applications. Redwood, CA: Benjamin-Cummings.

Chang, K.S. (2005). Introduction to Geographic Information System. New Jersey: Prentice- Hall.

Chapple, M. About Magazine. “Database normalization basics.” New York: New York Times Company.

Constantine, L. and Lockwood, L. (1999). Software for Use: A Practical Guide to the Models and Methods of Usage Centered Design. Boston, MA: Addison-Wesley.

DeMarco, T. (1978). Structured Analysis of System Specification. Englewood Cliffs, NJ: Yourdon, Inc.

Rumbaugh et al. (1991) Object Oriented Modeling and Design. New Jersey: Prentice-Hall.

Yourdon, E. (2006) Just Enough Structured Analysis. “Dataflow diagrams.” Englewood Cliffs, NJ: Yourdon, Inc.

Click Here To Order Now!