Academic journal article Journal of Information Systems Education

The Rescue911 Emergency Response Information System (ERIS): A Systems Development Project Case

Academic journal article Journal of Information Systems Education

The Rescue911 Emergency Response Information System (ERIS): A Systems Development Project Case

Article excerpt

1. BACKGROUND

1.1 Introduction

The Rescue911 systems development project case was written for use in a higher level undergraduate systems development project course. The case write-up is based on the guidelines presented by Cappel and Schwager (2002). Firstly, the case is classified as a fictional project-based case, which, according to Cappel and Schwager (2002), requires realism but does not intend to depict an actual organization.

As a project-based or "systems solution" case, it is specifically suited for one or more courses in systems analysis, design and programming. It is particularly useful for team-based projects of between 3 and 4 students. It was designed to allow students the opportunity to apply their knowledge of object-oriented systems analysis and design. In particular, the case provides students an opportunity to produce package diagrams, activity diagrams, use case diagrams, use case descriptions, class diagrams, sequence diagrams, state-machine diagrams, database schema and eventually implementation of the system through code. The case is also helpful in teaching students front-end user interface design skills. In more technical classes, the case provides an opportunity for students to discuss options for systems architecture.

The case context reinforces the timeless issue of service delivery in emergency healthcare and depicts the emergency response dispatch process as an essential component of local emergency medical services (EMS). The authors examined packaged software applications, textbooks with similar case scenarios (Brady and Monk, 2007), websites of emergency services companies and national academies of emergency dispatch, and blended with personal experience to ensure necessary realism and detail (Cappel and Schwager, 2002). The following sections present the learning objectives for the project and an overview of the fictitious Rescue911 business. Then, in the form of a problem statement, the paper presents "the hook" (Cappel and Schwager, 2002). This is intended to grab students' interest by outlining the problems that occur when an organization outgrows its existing information systems. The system requirements and detailed case content are then presented in the format of transcribed interviews with key stakeholders. This format is intended to help students visualize the organization and its operations.

1.2 Learning Objectives

The main objective of the case is to teach the concepts of object-oriented systems analysis and design in a semi-realistic setting. The case provides an opportunity to teach various business, methodological, systems modeling and implementation issues in systems development.

1. Business aspect

a. The case describes a realistic setting with a fictitious emergency response company.

b. The case for action is an increase in business activities resulting in an information technology environment no longer meeting business requirements.

c. The case shows a business centric approach to systems development by focusing on embedding new systems into the company's value chain, business processes and organization structure.

d. The case supports the idea of digitized and integrated business processes.

2. Methodology aspect

a. The case is presenting the situation after some efforts have been spent in a systems investigation phase.

b. The case uses different artifacts which are typical input documents for a systems analysis and design effort (e.g. requirements list and minutes of interviews with the system stakeholders).

3. Modeling aspect

a. The case presents students an opportunity to produce systems analysis and design artifacts using current notations (e.g. BPMN, UML).

b. The project requires students to understand models reflecting different levels of abstraction and to appreciate the value and scope of modeling in a systems development project. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.