Programming Assign.
Unit 3
Structured Analysis of a Library
Management System
Introduction
Structured analysis is a method used to study a problem and design an information system in
an organized and logical way. It focuses on understanding what the system must do before
deciding how it will be built. In this paper, a Library Management System is selected as the
problem to be analyzed. The goal of the system is to automate book borrowing and returning
activities, manage member records, and help librarians maintain accurate data. The structured
analysis process includes identifying system boundaries, building a context diagram, creating
a series of Data Flow Diagrams (DFDs), and developing a data dictionary.
Steps Involved in Structured Analysis
The first step in structured analysis is problem definition. This involves understanding the
purpose of the system and identifying the users who will interact with it. For the Library
Management System, the main users are library members and librarians.
The second step is requirements gathering. Information is collected about how books are
borrowed, how records are stored, and what outputs the system must produce. This ensures
that all needed functions are clearly identified.
The third step is system modeling. Diagrams are created to show how information moves
through the system. These include a context diagram and multiple levels of DFDs.
The final step is documentation using a data dictionary. The data dictionary explains every
data flow, data store, and external entity so that there is no confusion about what each item
means.
Context Diagram
The context diagram gives a high-level view of the entire system by showing it as one main
activity and illustrating how information is exchanged with outside users.
Level-0 Data Flow Diagram
The Level-0 DFD expands the system into its main internal processes and data stores.
This diagram is balanced with the context diagram because it uses the same external entities
and shows the same major data inputs and outputs.
Level-1 Data Flow Diagram
The Level-1 DFD breaks down one major process into smaller steps. In this scenario, the
“Handle Borrow/Return” process is further elaborated.
This diagram remains balanced with Level-0 because it only expands one process without
adding new external entities.
Data Dictionary
The data dictionary defines all entities, data flows, and data stores used in the system.
Name Type Description Contents
Library Member External Entity Person who borrows Member ID, Name
books
Librarian External Entity Staff managing the Staff ID, Name
system
Borrow/Return Data Flow Request to borrow or Member ID, Book
Request return a book ID, Action
Book Status Data Flow Response to member Availability, Due
request Date
Member File Data Store Stores member Member ID,
information Address, Phone
Book File Data Store Stores book details Book ID, Title,
Author, Status
Transaction File Data Store Stores borrowing Transaction ID, Date
history
Confirmation Data Flow Message sent to user Approval or Denial
Message
Conclusion
Structured analysis provides a clear and organized way to understand system requirements
before development begins. By identifying system boundaries and creating a context
diagram, the overall purpose of the Library Management System becomes clear. The Level-0
and Level-1 DFDs further explain how information moves through the system and how
processes are connected. The data dictionary ensures that every data item is clearly defined.
Together, these tools create a complete and understandable model of the system, reducing
errors and improving communication among developers and users.
References
Pressman, R. S., & Maxim, B. R. (2020). Software engineering: A practitioner’s approach
(9th ed.). McGraw-Hill Education.
Sommerville, I. (2021). Software engineering (11th ed.). Pearson.
Purdue Online Writing Lab. (n.d.). APA style guide. [Link]