Prescriptions contain basic information such as ID number, original date of order, drug, unit of dosage (pill, teaspoon, suppository), size of dosage, frequency of dosage, and special instructions (take with food, take before meals). There are several types of prescriptions, each with unique characteristics. Some orders are for a single, one-time-use prescription. Some orders are for a number of dosages. Some orders are for a certain time period. Information about the prescription order must be maintained. An order occurs when the nursing home phones in the needed prescriptions. Because prescriptions may last for an extended period of time, a prescription is a separate entity from the order itself. The system records which employee accepted and entered the original order.
The system has basic data about all drugs. Each drug has generic information such as name, chemical, and manufacturer. More detailed information for each type of dosage, such as the size of the pill, is also kept. A single drug may have many different sizes and types.
Information about the fulfillment of orders must also be maintained. For example, on a prescription for a number of pills, the system must keep a record of each time a pill or number of pills is dispensed. A record is maintained of which pharmacist fulfilled the order. Assume all prescriptions are dispensed only as needed for a 12-hour shift.
1. Develop an activity diagram for each use case related to entering new orders, creating case manifests, and fulfilling orders using Visio or its open source alternative software (at least three (3) total diagrams). Note: The graphically depicted solution may not exceed one (1) page per diagram.
2. Develop a system sequence diagram for each use case using Visio or its open source alternative software. Note: The graphically depicted solution may not exceed one (1) page per diagram.
3. Develop a state machine diagram for an order using Visio or its open source alternative software. Note: The graphically depicted solution may not exceed one (1) page per diagram.
4. Design a three-layer architecture using Visio or its open source alternative software for this new system. Note: The graphically depicted solution may not exceed one (1) page per diagram.
The RPS system has users who process orders in the Reliable offices and users who place orders and monitor order information in the nursing homes.
1. Design two (2) separate menu hierarchies, one (1) for Reliable employees and one (1) for nursing home employees.
2. Write out the steps of the dialog between the user and the system for the use case Place new order for nursing home employees.
3. Review the input form you created for collecting orders from the nursing homes. Identify all of the input controls necessary to ensure the prescriptions are correct. Recommend other procedures or controls to ensure that there are no mistakes with prescriptions.
4. Create a work breakdown structure of your proposed plan. Write a memo to the senior executive team at RPS that includes a summary of the created system and three (3) recommendations for future changes / improvements to the system.
Your assignment must follow these formatting requirements:
• Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
• Include a cover page containing the title of the assignment, the students name, the professors name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.
• Include charts or diagrams created in Visio or Dia. The completed diagrams / charts must be imported into the Word document before the paper is submitted.
The specific course learning outcomes associated with this assignment are:
• Analyze techniques for requirements determination, collection, and organization.
• Summarize effective communication techniques with various organizational stakeholders to collect information using a variety of techniques and to convey proposed solution characteristics to them.
• Explain various systems acquisition alternatives, including the use of packaged systems (such as ERP, CRM, SCM) and outsourced design and development resources.
• Analyze and present methods to initiate, specify, and prioritize information systems projects and determine various aspects of feasibility of these projects.
• Develop a solution to proposed business problem using structured systems analysis and design methods.
• Use technology and information resources to research issues in advanced systems analysis and design.