Case1: Patient Record System
A clinic with three dentists and several dental hygienists needed a system to help administer patient records. This system does not keep any medical records. It only processes patient administration. Each patient has a record with his/her name, date of birth, gender, date of first visit, and date of last visit. Patient records are grouped together under a household. A household has attributes such as name of head of household, address, and telephone number. Each household is also associated with an insurance carrier record. The insurance carrier record contains name of insurance company, address, billing contact person, and telephone number.
In the clinic, each dental staff person also has a record that tracks who works with a patient (dentist, dental hygienist, x-ray technician). Since the system focuses on patient administration records, only minimal information is kept about each dental staff person, such as name, address, and telephone number. Information is maintained about each office visit, such as date, insurance co-pay amount (amount paid by the patient), paid code, and amount actually paid. Each visit is for a single patient, but, of course, a patient will have many office visits in the system. During each visit, more than one dental staff person may be involved in the visit by doing a procedure. For example, the x-ray technician, dentist, and dental hygienist may all be involved on a single visit. In fact, some dentists are specialists in such things as crown work, and even multiple dentists may be involved with a patient. For each staff person does procedure in a visit combination (many-to-many) detailed information is kept about the procedure. This information includes type of procedure, description, tooth involved, the co-pay amount, the total charge, the amount paid, and the amount insurance denied.
Finally, the system also keeps track of invoices. There are two types of invoices: invoices to insurance companies and invoices to heads of household. Both types of invoices are fairly similar, listing each visit, the procedures involved, the patient gap amount, and the total due. Obviously, the totals for the insurance company are different from the patient amounts owed. Even though an invoice is a report (printed out), it also maintains some information such as date sent, total amount, amount already paid, amount due and also the total received, date received, and total denied. (Insurance companies do not always pay all they are billed.)
Context Diagram
Use Case Diagram
Use cases
Staff
Admin
Management
Use case specification:
Name: Patient Record system
Identifier Patient
Description: This use case defines about the patient details
Goal: To explain about how the patient information system has been maintained.
Preconditions
Patient record contains name, dob, gender, date of first visit, and date of last visit of the patient. Administrator record contains three dentists and several dental hygienists. The household deals with the insurance carrier record contains name of insurance company, address, billing contact person, and telephone number.
Post conditions
This information includes type of procedure, description, tooth involved, the co-pay amount, the total charge, the amount paid, and the amount insurance denied. Finally, the system also keeps track of invoices.
There are two types of invoices: invoices to insurance companies and invoices to heads of household. Both types of invoices are fairly similar, listing each visit, the procedures involved, the patient gap amount, and the total due. Obviously, the totals for the insurance company are different from the patient amounts owed. Even though an invoice is a report, it also maintains some information such as date sent, total amount, amount already paid, amount due and also the total received, date received, and total denied.
Actors
Admin, staff, management
Included Use Cases
Dentists and dental hygienists
Extended Use Case
Patients, staff, and management
Class Diagram
class
|
|
name
Associates
Attrib
|
Constraint delivers
|
|
Serves
connects
us
|
Sequence Diagram
|
|
|
|
Making Records
Checking the patient data in database
Saving
Maintain
Feedback Updating the data
Checking request confirmation and modifying
Output is displaying in the records
State Chart Diagram
Activity Diagram
|
No
yes
|
Case2: University Library System
This case deals with a new system for the University Library. Of course, the library system must keep track of books. Information is maintained about both book titles and the individual book copies. Book titles maintain information about title, author, publisher, and catalogue number. Individual copies maintain copy number, edition, publication year, ISBN, book status (whether it is on the shelf or loaned out), and date due back in.
The library also keeps track of patrons to the library. Since it is a university library, there are several types of patrons, each with different privileges. There are faculty patrons, graduate student patrons, and undergraduate student patrons. Basic information about all patrons is name, address, and telephone number. For faculty patrons, additional information is office address and telephone number. For graduate students, information such as graduate program and advisor information is maintained. For undergraduate students, program and total credit hours are maintained.
The library also keeps information about library loans. A loan occurs when a patron approaches the circulation desk with a stack of books to check out. Over time a patron can have many loans. A loan can have many physical books associated with it. (And a physical book can be on many loans over a period of time. Information about past loans is kept in the data‑ base.)
If a book is checked out that a patron wants, he/she can put that title on reserve. Each reservation is for only one title and one patron. Information such as date reserved, priority, and date fulfilled is maintained. When it is fulfilled, the system associates it with the loan on which it was checked out.
Patrons have access to the library information to search for book titles and to see whether a book is available. A patron can also reserve a title if all copies are checked out. When patrons bring books to the circulation desk, a clerk checks out the books on a loan. Clerks also check books in. When books are dropped in the return slot, they check in the books. Stocking clerks keep track of the arrival of new books.
Context Diagram
|
|
|
|
|
|||||||||
Use Case Diagram
Use case specification:
Name: University Library
Identifier Books
Description: This use case defines about the Library details
Goal: To explain about how the university library system has been maintained.
Preconditions
Information is maintained about both book titles and the individual book copies. Book titles maintain information about title, author, publisher, and catalogue number. Individual copies maintain copy number, edition, publication year, ISBN, book status (whether it is on the shelf or loaned out), and date due back in.
Post conditions
The library also keeps track of patrons to the library. Since it is a university library, there are several types of patrons, each with different privileges. There are faculty patrons, graduate student patrons, and undergraduate student patrons. Basic information about all patrons is name, address, and telephone number. For faculty patrons, additional information is office address and telephone number. For graduate students, information such as graduate program and advisor information is maintained. For undergraduate students, program and total credit hours are maintained.
.
Actors
Admin, staff, management, librarian
Included Use Cases
Customers, library staff
Extended Use Case
Publishers, Loan for books and patrons
Class Diagram
class
|
|
name
Associates
Attrib
|
Constraint delivers
|
|
Serves
connects
user
|
|||||
|
|||||
Sequence Diagram
|
|
|
|
||||||||
Records of books
Checking the data in database
Patrons for students, Graduates n UnderGraduates
Maintain
Feedback Updating the data
Checking request confirmation and modifying
Stock details
Displaying in system records
State Chart Diagram
Activity Diagram
Case3: E-business Exchange System
The Angus.com Book Exchange is a type of eBusiness exchange that does business entirely on the Internet. The company acts as a clearing exchange for both buyers and sellers of used books.
In order for a person to offer books for sale, she must register with Angus. The person must provide a current physical address and telephone number as well as a current email address. The system will then maintain an open account for this person. Access to the system as a seller is through a secure, authenticated portal. A seller can list books on the system through a special Internet form. Information required includes all of the pertinent information about the book, its category, its general condition, and the asking price. A seller may list as many books as desired. The system maintains an index of all books in the system so that buyers can use the search engine to search for books. The search engine allows searches by title, author, category, and keyword.
People desiring to buy books come to sight and search for the books they want. When they decide to buy, they must open an account with a credit card to pay for the books. The system maintains all of this information on secure servers.
When a request to purchase is made, along with the payment, TheAngus.com sends an email notice to the seller of the book that was chosen. It also marks the book as sold. The system maintains this as an open order, until it receives notice that the books have been shipped. Once the seller receives notice that a listed book has been sold, then she must notify the buyer, via email within 48 hours that the purchase is noted. Shipment of the order must be made with 24 hours after the seller sends the notification email. The seller sends a notification to both the buyer and TheAngus.com when the shipment is made.
After receiving notice of shipment, TheAngus.com maintains the order in a shipped status. At the end of each month, a check is mailed to each seller for all of those book orders that are have been in a shipped status for thirty days. The thirty-day wait is to allow the buyer to notify TheAngus.com if for some reason the shipment does not arrive, or if the book is not in the same condition as advertised.
The buyers can, if they desire, enter a service code for the seller. The service code is an indication of how well the seller is servicing book purchases. Some sellers are very active and use TheAngus.com as a major outlet for selling books. So a service code is an important indicator to potential buyers.
Context Diagram
|
|
|
|
|
|||||||||
Use Case Diagram
Angus.com book exchange
Use cases
author
Customer
Users
Publisher
Use case specification:
| Use Case Name | Angus.com Book Exchange |
| Description | Exchange for both buyers and sellers of used books. Seller should register in the website with add, tel no and email address. |
| Actors | Buyers, sellers, visitors, registered users, staff, maintainance. |
| Business Rules | When a request to purchase is made, along with the payment, sends an email notice to the seller of the book that was chosen. It also marks the book as sold.its as an open order, until it receives notice that the books have been shipped. Once the seller receives notice that a listed book has been sold, then she must notify the buyer, via email within 48 hours that the purchase is noted. Shipment of the order must be made with 24 hours after the seller sends the notification email. TheAngus.com when the shipment is made. |
| Pre-Conditions | After receiving notice of shipment, TheAngus.com maintains the order in a shipped status. At the end of each month, a check is mailed to each seller for all of those book orders that are have been in a shipped status for thirty days. The thirty-day wait is to allow the buyer to notify TheAngus.com if for some reason the shipment does not arrive, or if the book is not in the same condition as advertised. |
| Post-Conditions | After receiving notice of shipment, it maintains the order in a shipped status. At the end of each month, a check is mailed to each seller for all of those book orders that are have been in a shipped status for thirty days. The thirty-day wait is to allow the buyer to notify TheAngus.com if for some reason the shipment does not arrive. |
| Extending Use Case | Stocks, services, shipping |
Activity Diagram
Class diagram
|
|
|
getname:string
getname:string
|
Getinfo();
Getinfo();
Sequence diagram
|
|
|
|
||||||||
Records of books
Checking the data in database
Patrons for students, Graduates n UnderGraduates
Maintain
Feedback Updating the data
Checking request confirmation and modifying
Stock details
Displaying in system records
State Chart Diagram
Case4: Order Management System for “Computer Today 4 U”
“Computer Today 4 U” has grown from a small supplier of low-end computer equipment for the local retail market to a national supplier of high-end computer solutions for the national market focused on small to medium enterprises. The sales force is now scattered all over the country and is continually growing. The growth in business revenue and the increase in the sales force of “Computer Today 4 U” now requires a more innovative and efficient approach to the IT systems used by the company.
As a result, a major IT project is to be undertaken to develop an online system for the sales force and company to manage their sales orders, e.g. Place an order for computer equipment, prepare order, and check status of orders. The goal is to reduce costs and improve customer satisfaction by improving the speed of the order process, remove costly errors, and quickly track order status and details.
The system is to be developed by the Software Services Division of “CSIT Technologies Inc”.
The current system has become out-dated and is based on the use of spread sheets created by the Sales person for each customer order. It is a manual process, where the spread sheet is then used by the store personnel to put the order together and ship it. Customer Accounts staff use the spread sheet to invoice/bill the customer. Administrative staff eventually archives the spread sheet in the company’s sales database for historical purposes.
Each order’s spread sheet is based on the current company master file for ordering. The spread sheet includes a list of the product serial number, quantity, description of
computer component, the price, shipping address, customer name, customer identity number, discount, date, status, sales person’s name and special delivery instructions. The master file changes whenever a new product is introduced or removed, or when prices change. The status and process for the order is:-
- quote is prepared (the quote is prepared by the Sales person. The sales person either faxes the spread sheet, telephones a sales administrator or drops it into the office the next time that they are in the office.)
- quote approved (approval of quote is given by the General manger)
- customer accepts quote (the customer informs the sales person or General manager)
- order is prepared (this is performed by store personnel)
- order is shipped (this task is performed by an external courier or shipping agency)
- customer has received goods (this is notified by the external courier or shipping agency )
- customer is billed/invoiced (this is handled by Customer accounts staff)
- customer has paid (this is handled by Customer accounts staff)
- order cancelled (the sales person or General Manager are the only people that can cancel an order and may be due to customer changing their mind or not accepting the quote)
Currently, everything is updated in the spreadsheet by the people mentioned in the above process. The spreadsheets are stored on a network drive for everyone to access (and occasionally delete by accident).
The new computer system will basically support the same process but will be improved with new interfaces to replace the spreadsheets, and store the orders. The main and preferred interface will be web-based for use by all people involved in the process above. The sales people can register orders via the web interface, SMS (for small orders), email or the existing method (i.e. Fax, telephone). Where the sales person sends the order through by SMS, email, fax or telephone, a sales administrator will enter the order via the web-interface. All orders will be electronically stored on the computer system.
The system should be able to perform searches for orders based on criteria such as
computer product serial number, shipping address, customer name and number, date and status.
The General managers would also like to be able to use the system to obtain statistics on how sales orders are proceeding. They are interested in generating reports based on each sales person, each customer, each product or each time period.
People who have been given the correct authority or system privilege to perform these operations can only perform the searches and report generation, i.e. they are not available to everyone to perform.
The owner of Computer Today 4 U would also like to have sales forecasting tool introduced.
Context Diagram
|
|
|
|
|
|||||||||
Use Case Diagram
Customer
user
Publisher
Use case specification:
Name: Management system for Computer Today 4 U “CSIT Technologies Inc”
Identifier equipments
Description: This small supplier of low-end computer equipment for the local retail market to a national supplier of high-end computer solutions for the national market focused on small to medium enterprises. IT project is to be undertaken to develop an online system for the sales force and company to manage their sales orders, e.g. Place an order for computer equipment, prepare order, and check status of orders
Goal: The goal is to reduce costs and improve customer satisfaction by improving the speed of the order process, remove costly errors, and quickly track order status and details.
Preconditions
Includes a list of the product serial number, quantity, description of computer component, the price, shipping address, customer name, customer identity number, discount, date, status, sales person’s name and special delivery instructions
Post conditions
- quote is prepared (the quote is prepared by the Sales person. The sales person either faxes the spread sheet, telephones a sales administrator or drops it into the office the next time that they are in the office.)
- quote approved (approval of quote is given by the General manger)
- customer accepts quote (the customer informs the sales person or General manager)
- order is prepared (this is performed by store personnel)
- order is shipped (this task is performed by an external courier or shipping agency)
- customer has received goods (this is notified by the external courier or shipping agency )
- customer is billed/invoiced (this is handled by Customer accounts staff)
- customer has paid (this is handled by Customer accounts staff)
- order cancelled (the sales person or General Manager are the only people that can cancel an order and may be due to customer changing their mind or not accepting the quote)
.
Actors
Admin, staff, management, Customer
Included Use Cases
Customers, sales man
Extended Use Case
Manufacturers
Class Diagram
class
|
|
name
Associates
Attrib
|
Constraint delivers
|
|
Serves
connects
user
|
|||
Sequence Diagram
|
|
|
|
Making order
Checking data in database
Saving
Maintain
Track details Updating the data
Checking request confirmation and modifying
Output is displaying in the records
State Chart Diagram
Activity Diagram
References:
UML Distilled: A Brief Guide to the Standard Object Modeling Language
Martin Fowler, Kendall Scott
Practical UML — A Hands-On Introduction for Developers
http://www.togethersoft.com/services/practical_guides/umlonlinecourse/
- Bell, Michael. (2008). Service Oriented Modeling: Service Analysis, Design and Architecture. John Wiley & Sons, Inc.
- Bernd Bruegge, Allen H. Dutoit.(2009). Object-Oriented Software Engineering: Using UML, Patterns and Java, 3rd Edition. Prentice Hall
- Whitten, J.L. & Bentley, L.D. (2008). Introduction to Systems Anlysis and Design. McGraw-Hill Inc., New York, USA
LF98
But you can order it from our service and receive complete high-quality custom paper. Our service offers HEALTH essay sample that was written by professional writer. If you like one, you have an opportunity to buy a similar paper. Any of the academic papers will be written from scratch, according to all customers’ specifications, expectations and highest standards.”
