CIS 510 Week 10 Term Paper final project plan A++ TUTORIAL.docx
CIS 510 Week 10 Term Paper final project plan A++ TUTORIAL.docx PRG211
Popular in Computer Programming
This 13 page Study Guide was uploaded by Topseller Notetaker on Friday November 13, 2015. The Study Guide belongs to PRG211 at Ashford University taught by in Fall 2015. Since its upload, it has received 49 views. For similar materials see in Computer Programming at Ashford University.
Reviews for CIS 510 Week 10 Term Paper final project plan A++ TUTORIAL.docx
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 11/13/15
Running head: RPS FINAL PROJECT PLAN Reliable Pharmaceutical Service Final Project Plan Strayer University CIS 510 – Technical Paper Entity Relational Diagram (ERD) Running head: RPS FINAL PROJECT PLAN Domain Model Diagram Running head: RPS FINAL PROJECT PLAN Activity Diagram Running head: RPS FINAL PROJECT PLAN User Case Name: Enter new order Scenario: Enter new order Triggering Event: Health care organization calls with new patient order Brief Description: Actors: HC clerk Stakeholders: Staff Manager Preconditions: HC organization must exits HC unit must exist Drug must exist Drug item must exist Drug item package may possibly exit Prescription may possibly exist Patient may possibly exist Postconditions: Order exists Order item exists Prescription exists Patient exist Flow of Activities: Staff Member System 1. Begins new order (for secure login, enter employee 1.1 Finds and verifies employee ID). Create a new order 2. Enter HCOrg name and unit name. 2.1 Finds HCOrg and unit. Display information. 3. For each patient. 3a.1 Finds Patient. Displays information. 3a. Enter patient name. 3b.1 If not found. Displays new patient screen (Enter New Patient use case) 4. For each order item (prescription order item). 4a.1 Finds and displays prescription information. 4a. Enter prescription identifier. 4b.1 If not found. Displays new prescription screen 4c. Enters order item details for this prescription. (Enter New Prescription use case). 5. End order. 5.1 Finalizes order for HC unit Running head: RPS FINAL PROJECT PLAN Exception Conditions: 1.1 Employee ID is invalid Activity Diagram User Case Name: Create case manifest Scenario: Create case manifest Triggering Event: Staff is ready to create a case manifest to fulfill orders Brief Description: This use case prints a case manifest for an existing HC unit for all orders that were selected during this time period. Invoke the use case for each HC organization or for all organizations Actors: Employee Stakeholders: Employee Manager Preconditions: Order must exist Order item must exist HC organization must exist HC unit must exist Postconditions: Order updated Flow of Activities: Staff Member System 1. Enter HCOrganization identifier. 1.1 Finds and displays HC organization. Displays all HC units. 2. For each HC unit: 2.1 Displays selected unit information. Displays all 2a. Selects an HC unit open orders for this time period. 3. Selects orders, or selects all. 3.1 Prints case manifests for selected orders Exception Conditions: 1.1 HCOrganization is not found. 2.1 No open orders for an HC unit. Running head: RPS FINAL PROJECT PLAN Activity Diagram User Case Name: Record order fulfillment Scenario: Record order fulfillment Triggering Event: Pharmacist fulfills order Brief Description: Actors: Pharmacist or Assistant Stakeholders: Pharmacist Manager Preconditions: All objects must exist, including HCOrganization, HCUnit, Patient, Order, OrderItem, Prescription, Drug, DrugItem, Pharmacist (Employee). Postconditions: OrderItem is updated Flow of Activities: Staff Member System 1. Enter employee identifier. 1.1 Finds pharmacist. Displays information. Displays order fulfillment screen. 2. For each completed order: 2.1 Finds and displays HCOrg, HCUnit, order 2a. Enters order number (from case manifest) information, and order items 3. For each order item fulfilled: 3a.1Displays order item, prescription and patient 3a. Selects orders item details. 3b. Enters fulfillment information. 3b.1 Updates order item with fulfillment information. 4.1 Updates order. 4. Ends the order. Exception Conditions: 1.1 Employee is not found. Running head: RPS FINAL PROJECT PLAN System Sequence Diagram Running head: RPS FINAL PROJECT PLAN System Sequence Diagram State Machine Diagram Running head: RPS FINAL PROJECT PLAN ThreeLayer Architecture Menu Hierarchies Menu hierarchy for Reliable employee is as follows: Order Fulfillment 1. Check order 2. Record fulfillment 3. Record back order 4. Create return Menu hierarchy for nursing home employees is as follows: Order Entry 1. Check availability 2. Create new order 3. Updates order Running head: RPS FINAL PROJECT PLAN Steps of the dialog for use case new order Use case name: Place Order Actors: Nursing home employee 1. Nursing home employee connects to the RPS home page and then links to the order page. 2. Customer logs on. 3. The system starts a new order and patient names 4. Customer searched for patient they are placing order for. 5. When correct patient is found, employee searches patient’s file for drug item to order. 6. If new prescription, then the appropriate data must be entered to request a filling of this new drug prescription. 7. Employee requests refill or new prescription drug order and system displays a summary of the ordered items 8. Changes can be made at this time 9. Employee submits order and prints out a receipt for order. Necessary input controls In order to ensure that there are no mistakes made when prescriptions are filled, certain input controls must be completed and not left blank. These inputs with require a response and the user will not be able to move forward in the system until all required fields are completed. These inputs would be the drug name, the strength, the form of the drug being ordered, the NDC number, the trade name, the quantity being ordered, dosage instructions, patient’s name and ID#. Other strategy to prevent mistakes is to ensure that all drug orders are reviewed by the pharmacist for accuracy. Pharmacy tech can fill the orders, but each order should be verified by actual pharmacist as to the proper strength, dosage, and any interactions that could occur in the patient due to other drugs being used. Work Breakdown Structure Running head: RPS FINAL PROJECT PLAN Memorandum To: Senior Executive Team From: Oluwatoyin Adegoroye Date: 6/16/2013 Re: New Order system We are ready to provide you with the necessary documentation of the new order and fulfillment system that we have designed for Reliable Pharmaceutical Services. This new system will consist of a data warehouse containing all nursing home information, along with patient data, all drugs stocked or ordered by your company, manufacturer data, inventory, and the accounting program. The system will cut down on time spent taking phone orders and manually entering them into an antiquated system for fulfilling such orders. Running head: RPS FINAL PROJECT PLAN We have designed the system to meet all of your company’s requests and feel that there are a few other suggestions we would like to tell you about for future growth. As you expand into other areas of the country, you will want to move your data to a development server system for expansion of your databases. The drug database will be a huge undertaking and it will be something that you might want a knowledgeable pharmacist to work with the data analyst when inputting drug information into it. Accuracy is going to be a large undertaking and will require someone with a pharmacy background to verify that the database contains accurate information about each drug. You will also want to expand your security team in order to maintain control over patient information due to the HIPPA laws that are now in effect. As the business grows, you will also want to keep all information in one centralized location and not on servers at each of your facilities. This will provide better control and maintenance of the databases as your client list increases. We would like to set up a meeting with your team at your convenience. Please contact our team for availability. Thank you Running head: RPS FINAL PROJECT PLAN References Satzinger, J., Jackson, R., & Burd, S. (2011). Systems Analysis & Design in a Changing World. Macon, Ohio: Cengage Learning Sehlhorst, S.(2007). Sample Use Case example. Retrieved June 16, 2013, from http://tynerblain.com/blog/2007/04/09/sample-use-case- example/ Enterprise PM. The
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'