Reference no: EM132899343

Some examples could be: a health care organization, such as a health care insurance company, a major hospital, or medical laboratory; an academic institution, such as a university or a professional institute; a commerce and transportation center, for example a major airport, or maritime port; a transportation carrier, such as an airline company, a railroad company, or even a car transportation service; a network service provider, such as a telecommunications service carrier/provider, an Internet and voice digital service provider, or a cloud service provider; a major media organization, such as television network, or a multimedia service operator; an industry firm that manufactures products, such as a computer products manufacturer, a car manufacturer, or a hardware manufacturer; a major retailer, for example a food retailer, a home maintenance retailer, or clothes outlet; an entertainment complex, such as a hotel, a vacation resort, or a large recreation and entertainment complex; a financial institution, for example a banking system, a credit card service, or an investment trading service.

The above are examples to guide you with your research, but you are not limited to these areas. It is important that you arrive at your own case study, based on your personal interests, and one that is well suited to explore from an information systems analysis for this course. Some criteria that you should consider in arriving at your case study are listed below:

Your case study may be based on an actual company, or organization, using facts from research, or it could be fictional, in the sense that you could entirely define it yourself as a hypothetical case, with your own assumptions.

Your case study must require an underlying information system as an essential element for its operation.

The information system must be reasonably complex. One way to determine whether an information system is reasonably complex is to think in terms of entities and relationships that you will need to model. Even without knowing exactly how the data model will look, having some early notion of how many entities and relationships you should expect to model the information in your case will give you an appreciation for your case's complexity. A reasonable complexity would be at least ten entities and ten relationships.

At some point in your research you must be able to think in terms of use cases for your information system. Think of use cases as transactions that different end users will invoke when interacting with your information system. At the time you select your research area and define your case study, you need not know exactly the use cases you will be working with, but you should have some appreciation for the types of scenarios that you will explore as you progress with your project.

Finally, you must submit your area of study to your instructor via e-mail and have your instructor's approval that you may go ahead with your selection.

Once you have selected your study area and case, and have received approval from your instructor, you may proceed to the next steps described below. Create a report that focuses on the IS used to support the operation of your organization in your case study and answer the following questions.

Create a report that focuses on the current status of your IS. In the report complete the following tasks:

1. Create a scope for your application that you'll design. The scope should consist of the following components:

General project information (name, sponsor, and project manager)

Problem or opportunity statement

Project objective

Project description

Business benefits

Estimated project duration for the whole development cycle of the project, not just the design

2. Identify the stakeholders for your project and identify at least five (5) key stakeholders' needs. For each need, discuss the business problems to be solved

3. From your needs, determine at least seven (7) target-system features.

4. Produce a requirements management plan for your project. This plan will include:

Requirements criteria or categories

Feature request process

Methodology for collecting input into the requirements process

Traceability

Meta-data to track

Deliverables to produce

Processes, policies, and procedures