Objective: To develop a web server to help reduce phone call time for Doctors, Nurses and Administrative Personnel and to increase patient satisfaction by providing easier access to standard information.

The Cardiologist Group has hired you to develop Systems Requirements for a proposed web site that will perform the functions described above, including providing patients with the ability to schedule their own appointments. Patients will access the module by using their Social Security Number (SSN), which means that you need to access a database that has patient information including SSN and insurance information. First, the firm wants you to check to see if the patient has paid all his bills. If so, the patient can proceed, otherwise the patient should be given a message to call the billing department. Second, if the patient has insurance, a screen should appear presenting him with the insurance policy information and to ask the patient to verify it. If it is not verified, the patient should be asked to call the billing department. If the patient has no insurance, a screen should appear asking the patient how the bill will be paid. This verification or indication of payment method should be recorded in a database. If verification or indication is provided, the patient should be presented with a screen asking what type of procedure (stress test, EKG, ultra-sound, consult with doctor, etc. database with procedures) they are scheduling. After the patient selects one, a screen should present a calendar with open dates and times for a specified appointment (calendar database). Once the patient selects a time, a screen should appear asking the patient to verify the selected date and time, and to provide a phone number where they can be reached in case the appointment is cancelled or to remind the patient the day before the scheduled appointment. When the patient accepts the appointment and the transaction is recorded in the database.

1. Write a Systems Requirements Document

Use the Requirements Template to write your document.

Include all the key elements and functions of the web site. While the template suggests categories that you need to fill in or change, you do not have to use every one of them. (Delete the categories you will not use.) Be sure to use function numbers based upon the Traceability procedures specified in the document. Begin your own Revisions Table. If you use the template, the Table of Contents and other WORD tables will update automatically as you add or delete categories that are named and formatted similarly. Otherwise, include a Table of Contents that you develop. Use short, simple sentences to describe the function. This is a not a novel!

Mostly, make sure that the requirements you write make sense. Someone should be able to read them, understand what the web site will do. A web site developer should be able to create the web site based upon your document without needing to ask questions.

Your requirements document should include the following diagrams and flow charts (see Chapter 5 in your textbook for examples) to describe the web appointment module:

Context Diagram for the Web appointment module

Data Flow Diagram for module

Process Flow Diagram

Decide what databases you need to support the transaction and draw them in your diagrams. Use PowerPoint for the diagrams. While you dont have to use exactly the same symbols as the text book, you need to be consistent and indicate what symbol you are using for what purpose.

Using This Template

This and other PDM tools are available. All Sections are required to be addressed, however if a section or subsection is not needed, that section/subsection of the document can be marked as Not Applicable but as explanation must be provided as to why it does not apply. Please also reference the Lessons Learned section in the Appendix for additional information that may assist.

To create a deliverable from this template:

Delete the template title page (previous page) and this page.

Replace [bracketed text] on the cover page (next page) with your project and agency information.

Replace [bracketed text] in the tool header area at the top of Page i (Contents page) with the same project and agency information as on the cover page.

Note: Please do not remove or modify content in the footer area.

Complete the entire template. Each section contains abbreviated instructions, shown in italics, and a content area. The content area is marked with a placeholder symbol () or with a table. Relevant text from other project deliverable may be pasted into content areas.

Note: Please do not remove the italicized instructions.

Update the table of contents by right-clicking and selecting Update Field, then Update entire table.

Template Revision History

Version	Date	Name	Description
1.0	2/5/2012	PDM Project team	Initial Creation
2.0	6/28/2012		Reformatted document template; Renamed template to System Requirements. Added Initial Technical Architecture Specifications
2.1	1/14/2013		Revised system requirements instructions section
2.1	5/17/2013		Correct typos

Project Delivery Methodology (PDM)

System Requirements

[Functional Office(s) Name]

[PROJECT NAME]

VERSION: [Version Number] REVISION DATE: [Date]

Approval of the System Requirements indicates an understanding of the purpose and content described in this deliverable. By signing this deliverable, each individual agrees with the content contained in this deliverable.

Approver Name

Contents

Section 1 Purpose. 3

Section 2 General System Requirements. 3

2.1 Major System Capabilities. 3

2.2 Major System Conditions. 3

2.3 System Interfaces. 3

2.4 System User Characteristics. 3

Section 3 Policy and Regulation Requirements. 4

3.1 Policy Requirements. 4

3.2 Regulation Requirements. 4

Section 4 Security Requirements. 4

Section 5 Training Requirements. 4

Section 6 Initial Capacity Requirements. 4

Section 7 Initial System Architecture. 5

Section 8 System Acceptance Criteria. 5

Section 9 Current System Analysis. 5

Section 10 References. 6

Section 11 Glossary. 6

Section 12 Document Revision History. 6

Section 13 Appendices. 6

Section 1 Purpose

The purpose of the System Requirements document is to specify the overall system requirements that will govern the development and implementation of the system. The document will also establish initial security, training, capacity and system architecture requirements, as well as, system acceptance criteria agreed upon be the project sponsor and key stakeholders.

Section 2 General System Requirements

2.1 Major System Capabilities

Specify the major system capabilities in terms of availability, target deployment environment(s), device accessibility, and/or technical capability.

For example:

System must be available on the Internet

System must be available 24 hours per day

System must be accessible by mobile devices

System must be able to accept electronic payments

2.2 Major System Conditions

Specify major system assumptions and/or constraints (aka conditions). The conditions may limit the options available to the designer/developer. For example:

- System must use the FDOT Enterprise GIS Framework

- System must use FDOT Enterprise Document Management System

- System must interface with Bank of America credit card payment system

2.3 System Interfaces

Describe the dependency and relationship requirements of the system to other enterprise/external systems. Include any interface to a future system or one under development. For clarity, a graphical representation of the interfaces should be used when appropriate.

2.4 System User Characteristics

Identify each type of user of the system by function, location, and type of device. Specify the number of users in each group and the nature of their use of the system.

Section 3 Policy and Regulation Requirements

Specify relevant applicable laws, regulations, policies, and standards that will affect the operation and performance of the system, as well as any relevant external regulatory requirements, or constraints imposed by normal business practices.

3.1 Policy Requirements

3.2 Regulation Requirements

Section 4 Security Requirements

Specify security requirement for users of the system.

Section 5 Training Requirements

Specify Training requirements for the system.

Section 6 Initial Capacity Requirements

Specify the initial capacity requirements for the system. An initial estimation can be established using current data amounts, planned number of users, and estimated number of transactions.

Identifies the highest and lowest estimated number of transactions and processing frequency expected usage (including any seasonal peaks) for capacity planning for storage and memory requirements for the application or project. Identifies the highest and lowest estimated number of transactions and processing frequency expected usage (including any seasonal peaks) for capacity planning for storage and memory requirements for the application or project.

Section 7 Initial System Architecture

Specify the data platform, hardware, software, programming languages, tools and operating system requirements for the application or project.

Identify any specialized hardware requirements that must be purchased or upgraded prior to development, or in support of the implementation, of the application or project.

Identify any specialized software requirements that must be purchased or upgraded prior to development, or in support of the implementation, of the application or project.

Identify any programming languages and tools selected for the development of the application or project.

Identify any network/operating system or combination of network/operating systems that will be used for the development of the application of project.

Section 8 System Acceptance Criteria

Specify the general system acceptance criteria specified and agreed upon by the project sponsor and key stakeholders that will be used to accept the final end product. For example:

New system must run in parallel with current production system for x months

3 years of data must be in system (conversion implied) on day one

Section 9 Current System Analysis

If a current system exists, perform analysis on the system and describe how the current system is used by the business. Specify data conversion requirements, relevant data flows, system interfaces to existing systems, reporting capability, etc.

Section 10 References

Provide a list of all documents and other sources of information referenced in this document and utilized in its development. Include for each the document number, title, date, and responsible office/author.

Document No.	Document Title	Date	Author

Section 11 Glossary

Define of all terms and acronyms required to properly interpret the requirements contained within this document.

Section 12 Document Revision History

Identify revisions to the document starting with initial creation. This section should be updated when an approval is required (i.e. initial creation, change request, new mandated change, etc)

Version	Date	Name	Description

Section 13 Appendices

Include any relevant appendices.