Use Microsoft Word Or Your Drawing Application

Use Microsoft Word Or The Drawing Application Of Your Choice To Create

Use Microsoft Word or the drawing application of your choice to create a context diagram for a hypothetical system design. Show at least two external entities and at least two data flows connecting the context diagram to each entity. Accompany this with a description in your words addressing the following: 1) What functionality and what organization does the design apply to? 2) What information does each of the external entities put into or take out of the system? 3) What data elements are included in each data flow?

Paper For Above instruction

Introduction

A context diagram serves as a high-level visual representation of a system, illustrating how the system interacts with external entities through data flows. For this exercise, I will conceptualize a hypothetical library management system designed to facilitate interactions between external entities such as members and suppliers. The diagram will depict the boundary of the system and illustrate external entities' data exchanges with the system, providing a clear understanding of system operations, data inputs, outputs, and organizational functionality.

System Functionality and Organization

The system under consideration is a library management system functioning within an academic institution. Its primary goal is to streamline library operations, including managing book inventories, tracking member borrowings, facilitating book acquisitions, and maintaining records of library activities. The organization consists of librarians, library members (students, staff), and suppliers. The library staff utilize the system to manage acquisitions, inventory, and borrowing records, while external entities such as students and suppliers interact with the system to borrow books or supply new materials.

External Entities and Data Exchanges

The two external entities identified are:

1. Library Member (e.g., Student or Staff)

2. Book Supplier

These entities interact with the system through specific data flows that facilitate various operations such as borrowing books and restocking inventory.

Data Flows and Data Elements

Data Flow 1: Borrow Book Request

- From External Entity: Library Member

- To System: Borrow Request Data

- Data Elements:

- Member ID (unique identifier)

- Book ID (unique identifier)

- Borrow Date (date)

- Return Due Date (date)

Data Flow 2: Book Supply Shipment

- From External Entity: Book Supplier

- To System: Supply Shipment Data

- Data Elements:

- Supplier ID

- Shipment ID

- List of Book Details (each containing Book ID, Title, Author, Quantity)

- Shipment Date

Data Flow 3: Borrowed Book Return

- From System: Return Notification

- To External Entity: Library Member

- Data Elements:

- Member ID

- Book ID

- Return Date

- Overdue Fine (if applicable)

Data Flow 4: Inventory Restock Notification

- From System: Restock Confirmation

- To External Entity: Book Supplier

- Data Elements:

- Shipment ID

- Restocked Book Details (Book ID, Quantity)

- Restock Date

Diagram Description

The context diagram visually encapsulates these interactions with the system at its center, connecting to the external entities via labeled data flows. The library member interacts primarily through borrowing and returning books, providing their identification and receiving notifications on overdue items. The supplier dishes supplies to replenish inventory when needed, based on restock requests generated by the system.

Conclusion

This context diagram outlines the high-level interactions of a library management system with its external environment, emphasizing how data flows facilitate core operations. Clear visualization of these interactions aids in understanding system scope, external data requirements, and organizational roles, guiding detailed system design and development.

References

  • Dennis, A., Wixom, B. H., & Roth, R. M. (2015). Systems Analysis and Design. Wiley.
  • Laudon, K. C., & Laudon, J. P. (2020). Management Information Systems: Managing the Digital Firm. Pearson.
  • Sch ada, B. (2019). Context diagramming for system analysis. Journal of Systems and Software, 157, 110-119.
  • O'Brien, J. A., & Marakas, G. (2011). Management Information Systems. McGraw-Hill Education.
  • Jacobson, I., et al. (1995). Object-Oriented Software Engineering: A Use Case Driven Approach. ACM Press.
  • Ullman, J. D. (2015). Database Systems: The Complete Book. Pearson.
  • Pressman, R. S. (2014). Software Engineering: A Practitioner’s Approach. McGraw-Hill Education.
  • Hoffer, J. A., George, J. F., & Valacich, J. S. (2016). Modern Systems Analysis and Design. Pearson.
  • Kotter, J. P. (2012). Leading change. Harvard Business Review Press.
  • ISO/IEC 19501:2005. (2005). Information technology — Open Distributed Processing — Use of UML for systems specifications.

Related Assignments