Question 1

Develop proposal for an information system of your choice using Object-oriented (O-O) analysis and
design as an approach that is intended to facilitate the development of systems that must change
rapidly in response to dynamic business environments. These should include the following where
necessary:

1. Topic

Library Management System

2. Background

Libraries serve as a vital resource for knowledge and learning in educational institutions and
communities. However, traditional library management systems are often paper-based or outdated,
leading to inefficiencies in managing book records, member information, and borrow/return
transactions. A modern, digital system is needed to streamline operations.

3. Problem Statement

The manual handling of library records leads to:

- Inefficient tracking of books and member activity.

- Time-consuming processes for borrowing and returning books.

- Increased risk of data errors and loss of records.

4. System Context-Level Diagram

- External Entities:

- Library Administrator

- Library Members

- Publishers (for book acquisitions)

- System:

- Library Management System

5. Data Flow Diagram (DFD)

Level 0 (High-Level View):

- Members request to borrow or return books.

- Administrator manages book inventory and member records.

- The system generates reports for overdue books and stock levels.
 USER SEARCH FOR BOOKS BOOK DATABASE

ISSUE BOOKS UPDATE RECORDS

LIBRARIAN SYSTEM

Level 1 (Detailed View):

- Member requests are processed and recorded.

- Book inventory is updated upon each borrow/return.

- Notifications are sent for overdue books.

USER
LIBRARY MANAGEMENT
(Borrower) BOOK DATABASE
SYSTEM

LIBRARIAN

Request update

6. Entity Relationship Diagram (ERD)

Entities:

- Book

- Member
- Administrator

- Borrow Record

Relationships:

- A member can borrow multiple books.

- A book can have multiple borrow records.

- An administrator manages the books and members.

Members Transactions Books

Member ID PK TransactionsID
PK BookID PK
Name
MemberID Pk Title
Address
BookID FK Author
PhoneNumber
IssueDate ISBN
Email
ReturnDate CopiesAvailable
Membership
Status

Librarians

LibrarianID PK Handles Transactions

Name
LibrarianID FK
EmployeeID
TransactionID Fk
PhoneNumber

Email

7. Basic Software Requirements

- Programming Language: Java or Python.

- Database: MySQL or PostgreSQL.

- IDE: Eclipse or IntelliJ IDEA.

- APIs: Email API for notifications about overdue books.

8. Basic Hardware Requirements

- A server or computer with at least 8 GB RAM and 500 GB storage for hosting the system.

- Client machines with internet access for web-based systems or Android devices for mobile apps.

Question 2:

Differentiating Requirements and Characteristics

1. Differentiate Between URD and System Requirements

User Requirements Document (URD): Describes what the end user needs from the system. It is typically
written in plain language for stakeholders who may not be technically proficient.

Example: "The system must allow users to add and categorize expenses."

System Requirements: Define the technical specifications and functionalities the system must meet to
fulfill the URD.

Example: "The system must store expense data in a SQLite database and allow CRUD operations."

2. Three Types of User Requirements (with Examples)

Functional Requirements

Example: "The system must allow users to set financial goals and track progress."

Non-functional Requirements

Example: "The app must load data in under 3 seconds on devices with 4 GB RAM."

User Interface Requirements

Example: "The app must provide a dashboard view summarizing income, expenses, and goals."

3. Characteristics of Good System Output

Accuracy

The system should produce correct and reliable results, ensuring that financial reports reflect actual
income and expenses.

User-Friendliness

The output should be visually appealing and easy to interpret, such as using graphs and charts to
represent spending habits.
ST LAWRENCE UNIVERSITY

NAME: MUGISHA ABBAS

REG NO: BAIT/23D/R/J0114

FACULTY: SCIENCE AND TECHNOLOGY

COURSE: INFORMATION TECHNOLOGY

COURSE UNIT: SYSTEM ANALYSIS AND DESIGN

LECTURER: TOMUSANGE ISAAC

YEAR; TWO

SEMESTER: TWO