Reference no: EM131934998

Assignment

Resource:

"User Stories" document

Continue your work using the scenario presented in Week One.

The Director of Software Engineering and the Product Manager for the company visited the client and collected the User Stories as depicted in the User Stories document provided. In addition the Chief Financial Officer of the Hospital gave the Director a complete breakdown of the charges for surgeries, hospital stays, and prescription drugs.

Part 1:

The Director has asked you to read through the stories and help with the Functional Requirements Document (FRD) which is a formal statement of the program's functional requirements. The FRD serves the same purpose as a contract. Your company agrees to provide the capabilities specified. The client agrees to find the product satisfactory if it provides the capabilities specified in the FRD. The Director has asked you to identify any specific user interface, compliance, security, data, and data access requirements identified in the stories. The Director also wants to know which of the requirements you identify are functional or non-functional. The Director has determined that you will use an Agile approach to the development of the program.

Create a 1- to 2-page list using Microsoft Word of the current requirements the FRD will need. First, list five requirements that are functional, then list five non-functional requirements. The FRD will be refined as the development proceeds, so this list is a starting point.

Part 2:

Your intern is struggling to understand the differences between Data Flow Diagrams (DFDs) and Entity-Relationship Diagrams (ERDs).

To help your intern understand the difference, create a 1-page comparison table using Microsoft Word showing the similarities and differences between a Data Flow Diagram (DFD) and an Entity-Relationship Diagram (ERD). The table should depict at least three points of comparison, as well as a justification of why you would use one approach over the other.

Cite all sources using APA guidelines.

User Stories

The Director of Software Engineering and the Product Manager for the company visited the client and collected the User Stories below:

• From the Chief Financial Officer: In order to meet HIPAA requirements, I have to be able to provide detailed records of all bills. Your program needs to be very accurate; there should be ways you can prove to me the bills you produce are correct.

• From the Data Entry Clerk: I have red-green color blindness. Your program needs to have an interface that is easy for me to interpret. If you use a warning in a program, it cannot come up in red; I will not be able to read it.

• From the Discharge Clerk: Patients often do not understand their bill when I give it to them. It would be so helpful if the bill also described the medications they are given. The bill is sometimes bad news for the patient, so I would like the printed bill to use soft, calming colors and include a happy face.

• From the Pharmacist: Accuracy is very important to me. If the bill states the medication inaccurately, I can be sued.

• From the Compliance Manager: HIPAA gives me headaches every day. Your program needs to meet all of the requirements to protect PII. My Security Team Manager said that our PHI Policy prohibits the use, storage, and discloser of Personal Health Information (PHI) and Electronic Personal Heal information (EPHI), except as specifically permitted or required by HIPAA regulation.

• From the Data Entry Supervisor: All of my clerks are very young. They are going to want your user interface to look like an iPhone or Facebook or they will not be able to use it. The user interface and the bill should have our logo on it.

• From the Surgery Supervisor: I feel very strongly that program usage should be restricted to those who"need to know." Some of the software around here is not locked down; even the janitor knows the username and password sometimes.