Case Study- Book Exchange

TextBookExchange.com is a type of electronic business (e-business) exchange that does business entirely on the Internet. The company acts as a clearinghouse for both buyers and sellers of used textbooks.

 To offer books for sale, a person must register with TextBookExchange.com. The person must provide a current physical address and telephone well as a current e-mail address. The system will then maintain an open account for this person. Access to the system is through a secure, authenticated portal.

 A seller can list text 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 title, author, category, and keyword.

 People who want to buy books visit the site and search for what they want. When they decide to buy, they must open an account with a credit card or PayPal account 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, TextBookExchange.com sends an e-mail notice to the seller of the book that was chosen. It also marks the book as sold. The system maintains an open order until it receives notice that the books have been shipped. After the seller receives notice that a listed book has been sold, the seller must notify the buyer via email within 48 hours that the purchase is noted. Shipment of the order must be made within 24 hours after the seller sends the notification e-mail. The seller sends a notification to buyer and TextBook.Exchange.com when the shipment is made.

 After receiving notice of shipment, TextBookExchange.com maintains the order in a shipped status. At the end of each month, a check is mailed to each seller for the book orders that have been in a shipped status for 30 days. The 30 day waiting period exists to buyer to notify TextBookExchange.com if the shipment does not arrive for some reason, or if the book is not in the same condition as advertised.

 If they want, buyers can enter a service code for the seller. The code is an indication of how well the seller is servicing book purchases. Some sellers are very active and use TextBookExchange.com as a major outlet for selling books. So, a service code is an indicator, to potential buyers.

 TextBookExchange.com wants to update their website to eliminate the need for time-consuming manual email messages. This project is called “Auto Messaging Facility”. As part of this new project, they also want the email facility to seamlessly integrate with the emerging mobile channel. In particular, they want tracking of orders and shipments, and notifications through emails and as well as through short messaging services. They also want the major business processes supported by their website to be replicated and/or enhanced on a mobile application which should include mobile payments facility.

 They also want to provide a facility to allow users to find out which institutions (including schools, colleges and universities) are using what textbooks, this project is called the “Who uses What”.

 REQUIREMENTS:

 1. Develop a Context Diagram for your system

 2. Develop a top level Data Flow Diagram (DFD) for your system

This diagram should capture the high level features of your system.

 3. Develop lower level DFDs for the core components of your case

Level 1 and perhaps level 2 diagrams for your system’s core components. The number of levels may vary based on the complexity of your case study and your design decisions. It is also your judgment call.

 4. Design and develop a Data Dictionary for your core system to data elements level

These data dictionary entries should be for your lowest level of DFD diagrams.

 5. Develop Process Specifications for the core components of your system

These specifications should be for lowest level of processes that appear on your DFDs. Use structured English, decision table and decision tree to specify processes. For each of these three pSpec types, you may choose to specify two major processes (totalling six processes for the assignment).

 6. Develop an Entity Relationship Diagram (ERD) for your system

It’s up to you to decide whether you want to attempt normalisation or not.

Use the order calculator below and get started! Contact our live support team for any assistance or inquiry.

[order_calculator]