Visio and Visual Basic

Case Study: Bula Book Retail The Bula Book Retail allows its users to sell or buy books within Fiji. To sell books, a person must register with valid email address, residential address, name and phone contact. A seller may list many books as he/she wishes. A seller can list books by providing the following information: - Book title - Book Author - Category - Condition of the Book - Asking price. Buyers can search for the books using title, author, category, and keyword. When they decide to buy, they must open an account with a credit card to pay for the book(s). When a purchase is made, Book status changes to "Sold" and Bula Book Retail sends an e-mail notice to the seller. After the seller receives notice that a listed book has been sold, the seller must notify the buyer via e-mail that the purchase is noted. Also, the seller notifies the buyer and Bula Book Retail when the shipment is made. After receiving the notice of shipment, Bula Book Retail maintains the order in a shipped status. The buyers enter a rating for the seller based on the experience with the seller on sale of the book and can also notify of problems. A check is mailed to each seller for the book orders that have remained in a shipped status for 7 days or have issues noted from buyer. Proposal Document Template 1.0 Project Title 2.0 Revision History 3.0 Table of Contents 4.0 Introduction 5.0 Analysis Artifacts 5.1 Functional requirements 5.2 Non-Functional requirements 5.3 Use Case Diagram 5.4 Class Diagram 5.5 Sequence Diagram 6.0 System Design 6.1 User Interface 7.0 Recommendation 8.0 References 9.0 Appendix How to create this document? The following sections will explain what artifacts to include in the documentation. 4.0 Introduction Explain the purpose of this documentation. 5.0 Analysis Artifacts 5.1 Functional requirements List it based on Actors. 5.2 Non-Functional requirements List only 3 non-functional requirements that is Security, Operational and Usability. 5.3 Use Case Diagram Create the use case diagram for the system. 5.4 Class Diagram Illustrate the system structure through entities. 5.5 Sequence Diagram Draw the sequence diagram for Add a seller use-cases. 6.0 Systems Design 6.1 User Interface Create a prototype form for Add a seller use-case using VB.net (no coding required) 7.0 Recommendation State which SDLC model is best choice for the development of the scenario given and explain your answer. 8.0 References Reference any material that you have used using IEEE format. 9.0 Appendix Include at least 1 supporting document or diagram. Case Study: Bula Book Retail The Bula Book Retail allows its users to sell or buy books within Fiji. To sell books, a person must register with valid email address, residential address, name and phone contact. A seller may list many books as he/she wishes. A seller can list books by providing the following information: - Book title - Book Author - Category - Condition of the Book - Asking price. Buyers can search for the books using title, author, category, and keyword. When they decide to buy, they must open an account with a credit card to pay for the book(s). When a purchase is made, Book status changes to "Sold" and Bula Book Retail sends an e-mail notice to the seller. After the seller receives notice that a listed book has been sold, the seller must notify the buyer via e-mail that the purchase is noted. Also, the seller notifies the buyer and Bula Book Retail when the shipment is made. After receiving the notice of shipment, Bula Book Retail maintains the order in a shipped status. The buyers enter a rating for the seller based on the experience with the seller on sale of the book and can also notify of problems. A check is mailed to each seller for the book orders that have remained in a shipped status for 7 days or have issues noted from buyer. Proposal Document Template 1.0 Project Title 2.0 Revision History 3.0 Table of Contents 4.0 Introduction 5.0 Analysis Artifacts 5.1 Functional requirements 5.2 Non-Functional requirements 5.3 Use Case Diagram 5.4 Class Diagram 5.5 Sequence Diagram 6.0 System Design 6.1 User Interface 7.0 Recommendation 8.0 References 9.0 Appendix How to create this document? The following sections will explain what artifacts to include in the documentation. 4.0 Introduction Explain the purpose of this documentation. 5.0 Analysis Artifacts 5.1 Functional requirements List it based on Actors. 5.2 Non-Functional requirements List only 3 non-functional requirements that is Security, Operational and Usability. 5.3 Use Case Diagram Create the use case diagram for the system. 5.4 Class Diagram Illustrate the system structure through entities. 5.5 Sequence Diagram Draw the sequence diagram for Add a seller use-cases. 6.0 Systems Design 6.1 User Interface Create a prototype form for Add a seller use-case using VB.net (no coding required) 7.0 Recommendation State which SDLC model is best choice for the development of the scenario given and explain your answer. 8.0 References Reference any material that you have used using IEEE format. 9.0 Appendix Include at least 1 supporting document or diagram