Question 1 Student Bookstore At Pleasant Creek Community Col

Question 1student Bookstore At Pleasant Creek Community College Situa

The bookstore staff at Pleasant Creek Community College works to satisfy students, instructors, and the school’s business office. Instructors specify textbooks for courses, and the bookstore orders and sells these books to students. You are asked to develop an object-oriented model for a new bookstore information management system, including identifying objects with attributes and methods, potential use cases and actors, creating a sequence diagram for one use case, and designing an object relationship diagram that illustrates how textbooks are selected by instructors, approved by department heads, and sold to students.

Paper For Above instruction

The development of an object-oriented model for a bookstore management system involves a thorough understanding of the entities involved and their interactions within the system. The primary objects include Book, Instructor, DepartmentHead, Student, and Bookstore. Each object has specific attributes and methods that define its behavior and state within the system.

The Book object embodies attributes such as ISBN, title, author, publisher, price, and stock quantity. Its methods may include orderBook(), updateStock(), and displayDetails(). The Instructor object contains attributes like instructorID, name, department, and courses_taught, with methods such as specifyTextbooks() and approveTextbook(). The DepartmentHead oversees textbook approvals, with attributes like headID, name, department, and methods such as approveBookRequisition(). The Student object, with attributes such as studentID, name, major, and enrolledCourses, interacts primarily during the purchase process, which involves methods like selectBook(), purchaseBook(), and viewAvailableBooks(). Lastly, the Bookstore object manages overall operations, including inventory management, order processing, and sales transactions, through methods like processOrder(), sellBook(), and generateSalesReport().

Key use cases for this system include instructors specifying textbooks, department heads approving requisitions, bookstore staff processing orders and sales, and students purchasing textbooks. Actors involved are Instructor, DepartmentHead, BookstoreStaff, and Student. These actors interact with the system to perform their respective tasks, which can be modeled within use cases such as 'Specify Textbooks,' 'Approve Textbook Requisition,' 'Order Books,' 'Sell Books,' and 'Purchase Textbooks.'

For the sequence diagram, consider the use case 'Student Purchases Textbook.' The sequence begins with the Student searching for available books, selecting a desired textbook, the system verifying stock, proceeding with the payment transaction, and updating the stock quantity upon completion. Messages flow between the Student, Bookstore, and Book objects to represent this process, illustrating the temporal sequence of interactions that fulfill the use case.

The object relationship diagram (also known as a class diagram) depicts relationships among the key objects. In this diagram, Instructor is associated with Course, which in turn relates to specific Book requisitions. The DepartmentHead reviews and approves these requisitions, establishing a dependency or association with the Book requisition object. The Book object is linked to the bookstore's inventory and sales system. Students are associated with purchase transactions, and the Bookstore manages the overall control, maintaining collections of Books, Instructors, Students, and Transactions. These relationships provide an overall view of how textbooks are requested, approved, and sold within the system.

References

  • Object-Oriented Analysis and Design with Applications, Grady Booch, Robert A. Maksimchuk, et al., Addison-Wesley, 2007.
  • Use Case Driven Object Modeling with UML, Doug Rosenberg, Kendall Scott, Addison-Wesley, 2006.
  • Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, Craig Larman, Pearson, 2004.
  • Design Patterns: Elements of Reusable Object-Oriented Software, Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Addison-Wesley, 1994.
  • Software Modeling and Design: UML, Use Cases, Patterns, and Software Architecture, Michael Blaha, James Rumbaugh, Wiley, 2005.
  • Object-Oriented Software Engineering, Ivar Jacobson, Visual Paradigm, 2007.
  • UML Distilled: A Brief Guide to the Standard Object Modeling Language, Martin Fowler, Addison-Wesley, 2004.
  • Clean Architecture: A Craftsman's Guide to Software Structure and Design, Robert C. Martin, Prentice Hall, 2017.
  • Prioritizing Use Cases in Requirements Engineering, Alistair B. G. D. Cathro, IEEE Software, 2004.
  • Modeling Software Systems, Richard M. Starr, Prentice Hall, 2005.

Related Assignments