SHRI G.P.M.

DEGREE COLLEGE OF

SCIENCE & COMM

 CERTIFICATE
This is to certify Mr/Ms______________________________________________________
In the subject of____________________________________________________________

As prescribed by the UNIVERSITY OF MUMBAI under my supervision during the

Academic year 2023-2024

------------------------------ --------------------------------

Prof.Incharge Principal

-------------------------------- ----------------------------------

External Examiner Course Co-ordinator

Professor Name: Akanksha Mishra Class: SY.BSC- CS
Semester: Sem 4 (2023-2024)

Course Code: USCSP403 Subject: Software Engineering

Sr. Date Index Page. Sign

no. No.
1 Practical 1:
Write down the problem statement for a
Suggested system of relevance

2 Practical 2:
Perform requirement analysis and
develop software requirement
specification sheet (SRS) for suggest
system.
3 Practical -3: Draw the function
oriented diagram:
Data Flow Diagram(DFD) and
structured chart
4 Practical 4: Draw the user’s view
analysis for the suggested system:
Use case Diagram
5 Practical 5: Draw the structural view
diagram for the system:
Class diagram, object diagram.
6 Practical 6: Draw the behavioral view
diagram:
State-chart diagram, Activity diagram
7 Practical 7: Draw the behavioral view
diagram for the suggested system:
Sequence diagram, collaboration
diagram
8 Practical 8: Draw the implementation
and environment view diagram:
Component diagram, Deployment
diagram
9 Practical 9:
Perform Estimation of effect using FP
Estimation
10 Practical 10:
Prepare time line chart/Gantt chart/PERT
chart
Practical 1
Aim: Write down the problem statement for a suggested system of
relevance
Many libraries rely on manual systems for managing books, members,
and borrowing processes. This leads to several problems:
• Inefficiency and Time Consumption: Manual tasks like searching

catalogs, issuing/returning books, and calculating fines are slow

and prone to errors.
• Data Inaccuracy and Loss: Paper-based records are susceptible to

damage, misplacement, and difficulty in maintaining accurate

information.
• Limited Search Capabilities: Finding specific books by title,

author, or subject can be cumbersome with a physical card

catalog system.
• Cumbersome Inventory Management: Tracking loaned-out

books, overdue items, and damaged materials becomes labor-

intensive.
These limitations hinder a library's ability to serve its patrons effectively
and create a frustrating experience for both staff and users.
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 2
Aim: Perform requirement analysis and develop Software
Requirement Specification Sheet (SRS) for suggested system.
Requirement Analysis: Library Management System
Stakeholders:
• Librarians/Administrators
• Library Members
• System Developers
Functional Requirements:
1. Member Management:
o Add, edit, and delete member information (name, contact details,
membership type).
o Search for members by ID or name.
o View member borrowing history and outstanding fines.
2. Book Management:
o Add, edit, and delete book information (title, author, ISBN, genre,
publication details).
o Search for books by title, author, ISBN, or keywords.
o Maintain book categories and subcategories for organization.
3. Circulation Management:
o Issue books to members by scanning member ID and book ISBN.
o Return books and update availability status.
o Calculate and manage overdue fines based on library policies.
o Allow for book renewals (if applicable).
4. Reporting:
o Generate reports on loaned-out books, overdue items, fines
collected, and member activity.
o Export reports in various formats (PDF, CSV).
5. System Administration:
o Manage user accounts and access privileges (librarians,
administrators).
 o Back up and restore system data for disaster recovery.
o Configure system settings (borrowing limits, fine rates, etc.).
Non-Functional Requirements:
• Security: Secure login system with user authentication.
• Data Integrity: Maintain data accuracy and consistency across the system.
• Performance: Respond to user requests quickly and efficiently.
Additional Considerations:
• Barcode Scanning: Integrate with barcode scanners for faster book
processing.
• Email/SMS Notifications: Send email or SMS alerts for overdue notices and
book renewals.
• Mobile App Integration: Develop a mobile app for member self-service
options (optional).
Software Requirement Specification (SRS) Sheet
1. Introduction
• Briefly describe the library management system and its purpose.
• Define the target audience (librarians, members, etc.).
2. Overall Description
• Provide a high-level overview of the system functionalities.
• Describe the system architecture (client-server, web-based, etc.).
3. Specific Requirements
• 3.1 Functional Requirements:
o List each functional requirement as identified in the analysis.
o Clearly define the inputs, outputs, and expected behavior for each
function.
4. System Interfaces
• Describe user interfaces (UI) for librarians, members, and system
administrators.
5. System Design Constraints
• Identify any limitations or constraints on the system design (hardware,
software, budget).
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 3
Aim: Draw the functional oriented diagram: Data Flow
diagram (DFD) and Structured Chart
A Library Management System's DFD visually maps information flow. It
uses symbols: rectangles for external entities (members, librarians),
circles for processes, arrows for data flow, and squares for data stores.
The Context Diagram (Level 0) provides a high-level view. It shows the
entire system as a single process interacting with external entities:
• Members: They provide data like member ID and book ISBN for
borrowing/returning books and receive reports (overdue notices).
• Librarians: They manage members, books, and system settings
(adding entries, generating reports).
Level 1 DFD expands on this. It breaks down the main process into sub-
processes:
• Member Management: Handles member data (adding, editing,
searching).
• Book Management: Deals with book information (adding, editing,
searching, tracking availability).
• Circulation Management: Manages borrowing/returning
processes (data on borrowed books, fines).
• Reporting: Generates reports based on system data (loan history,
fines).
This DFD clarifies how data flows through the system, helping
understand how different functionalities interact.
Benefits of a DFD:
• Provides a clear visual representation of the system's
functionality.
• Helps identify potential bottlenecks or inefficiencies in the data
flow.
 • Facilitates communication between developers, stakeholders, and
system users.

Data flow Diagram for Library Management System:

Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 4
Aim: Draw the user’s view analysis for the suggested system:
Use Case Diagram.
A Use Case Diagram for a library management system focuses on the
user's perspective. It depicts actors (users) and the system
functionalities (use cases) they interact with.
There are two main actors:
• Member: They can search for books by title, author, or subject.

They can borrow and return books using their member ID and
book ISBN. The system shows their borrowing history and any
outstanding fines.
• Librarian: They can add, edit, and delete member and book

information. They manage borrowing/returning processes,

including issuing books, calculating fines, and handling renewals.
Additionally, librarians can generate reports on library usage and
configure system settings.
The use case diagram showcases how these actors interact with the
system to achieve specific goals, providing a clear understanding of the
system's functionalities from the user's point of view.
Use Case Diagram for Library Management System:
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 5
Aim: Draw the structural view diagram for the system: Class
diagram, object diagram
A Class Diagram for a library management system depicts the system's
building blocks and their relationships. It uses rectangles to represent
classes (e.g., Member, Book) and lines to show connections between
them.
Here's a simplified explanation:
• Classes:

o Member: Stores member information (ID, name, contact

details).
o Book: Contains book details (title, author, ISBN, genre,

availability status).
o Loan: Represents a borrowing transaction (member ID, book

ISBN, borrow date, due date).

o Librarian: Stores librarian user accounts and access

privileges.
• Relationships:

o A Member can borrow multiple Books (one-to-many).

o A Book can be borrowed by multiple Members at different

times (one-to-many).
o A Loan connects a Member and a Book for a specific

borrowing period (many-to-many).

o A Librarian manages the system and interacts with other

classes (generalization).
Class Diagram for library Management System:
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 6
Aim: Draw the behavioural view diagram: State-chart, Activity
Diagram
An Activity Diagram for a library management system focuses on the
flow of activities involved in specific functionalities. It uses rounded
rectangles for actions, diamonds for decision points, and arrows to
depict the sequence of events.
Let's consider the "Borrowing a Book" scenario:
1. Member Requests Book: The member initiates the process by
searching for a book and requesting to borrow it.
2. Scan Member ID and Book ISBN: The librarian scans the
member's ID and the book's ISBN to verify their details.
3. Check Availability: The system checks if the book is available for
borrowing.
4. Decision: Book Available? If yes, the process continues. If not, the
member is notified and the activity ends.
5. Record Loan: The system records the loan transaction (member
ID, book ISBN, borrow date, due date).
6. Update Book Status: The book's availability status is changed to
"loaned out."
7. Issue Book: The member receives the borrowed book.
The activity diagram visually represents the steps involved in borrowing
a book, including decision points and alternative flows (unavailable
book). This helps visualize the system's behavior from a process-
oriented perspective.
Activity Diagram for Library Management System:
1. Member Subsystem
a.Create New Member
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 7
Aim: Draw the behavioural view diagram for the suggested system:
Sequence diagram, Collaboration diagram
A Sequence Diagram for a library management system focuses on the
message flow between objects during a specific interaction. It shows
objects involved (librarian, member, book database) as vertical lifelines.
Horizontal arrows represent messages sent between objects.
Here's a simplified example of borrowing a book:
1. Member requests book: The member object sends a message to
the librarian object requesting a specific book.
2. Librarian verifies details: The librarian object interacts with the
book database to check book availability.
3. Librarian validates member: The librarian object might send a
message to a member database to validate borrowing privileges
(optional).
4. Book available & member valid (positive scenario):
o Librarian sends a message to the book database to update

its status to "loaned out."

o Librarian sends a message to the loan management system

to record the borrowing transaction.

o Librarian informs the member that the book is borrowed.

5. Book unavailable or member invalid (negative scenario):

o Librarian informs the member about the issue (unavailable

book, borrowing limit reached etc.).

Sequence Diagram for Library Management System:
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 8
Aim: Draw the Implementation and environmental view diagram:
Component diagram, Deployment diagram
A Deployment Diagram for a library management system depicts how
the software is physically distributed across hardware components. It
uses rectangles to represent software components (e.g., library
management application) and nodes to represent physical devices
(servers, workstations). Lines show communication paths between
these elements.
Here's a breakdown:
• Nodes:

o Server(s): Hosts the library management application

software.
o Librarian Workstations: Used by librarians to access and

manage the system.

o Member Kiosk (optional): Allows members to search the

catalog and potentially self-serve functions (renewals).

• Software Components:

o Library Management Application: Core software running on

the server, managing data and functionalities.

o User Interface (UI): Provides interfaces for librarians and

members (web-based or desktop application).

The deployment diagram clarifies how the system is physically
distributed. It shows where the software resides, on which devices, and
how these components communicate to deliver library management
functionalities.
Deployment diagram for Library Management System:
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
Practical 9
Aim: Perform Estimation of effort using FP Estimation
Function Point Estimation for Library Management System
Function Point (FP) analysis provides a way to estimate the effort
required to develop a software system. Here's a simplified approach to
estimate the effort for a library management system:
1. Identify Functional Requirements: Αναλύουμε (Analýoume -
Greek for "We Analyze") the functionalities identified earlier
(member management, book management, circulation
management, reporting, system administration).
2. Count Function Points: For each functionality, categorize and
count the following:
• External Inputs (EI): User interactions like adding a member,

searching for a book, borrowing/returning a book.

• External Outputs (EO): System responses like displaying member

information, search results, borrowing confirmation message.

• Logical Internal Files (LIF): Data entities stored by the system

(member database, book catalog, loan records).

• External Interfaces (EI): Interactions with external systems

(optional, e.g., online payment gateway).

Example:
Functionality: Borrow a Book
• EI: Member provides ID and book ISBN, librarian scans them.

• EO: System displays confirmation message or informs about

unavailability.
• LIF: Member database, Book database, Loan records.

3. Apply Function Point Weights:

Assign weights to each category based on their complexity:
• EI, EO, EI (average): Weight 4

• LIF: Weight 5

4. Calculate Unadjusted Function Points (UFP):

UFP = Σ (EI * 4) + Σ (EO * 4) + Σ (LIF * 5) + Σ (EI * 4) (summation for each
category)
5. Complexity Adjustment Factor (CAF):
Consider factors like data processing complexity, distribution, and user
interfaces. A basic library system might have a CAF of 0.65 (low
complexity).
6. Adjusted Function Points (FP):
FP = UFP * CAF
7. Effort Estimation:
Industry averages suggest an effort of 30-40 person-hours per function
point. Multiply the FP by the chosen effort per FP value to estimate the
total development effort in person-hours.
Note: This is a simplified approach. Real-world FP analysis involves
detailed tables and calculations.
Benefits of FP Estimation:
• Provides an objective measure of system size.

• Enables effort estimation early in the development process.

• Facilitates comparison with similar projects.

Limitations of FP Estimation:
• Relies on accurate requirement identification and counting.

• Effort per FP value can vary depending on project specifics.

Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]
 Practical 10
Aim: Prepare the line chart/Gantt chart PERT chart

A Gantt chart for a library management system visually depicts project

tasks, timelines, and dependencies. It uses horizontal bars to represent
tasks, with their lengths showing duration. Arrows show dependencies
between tasks (e.g., testing can't start until development finishes).

Here's a simplified example for a library management system:

• Phase 1: Requirements & Design (2 weeks):

o Tasks: Analyze requirements, define system architecture, create data
flow diagrams and use case diagrams.
• Phase 2: Development (6 weeks):
o Tasks: Develop core functionalities (member management, book
management, circulation), code unit testing.
o Dependency: Starts after Requirements & Design is complete.
• Phase 3: System Integration & Testing (2 weeks):
o Tasks: Integrate system components, conduct functional and non-
functional testing.
o Dependency: Starts after Development is complete.
• Phase 4: Deployment & Training (1 week):
o Tasks: Install and configure the system, train librarians and members.
o Dependency: Starts after System Integration & Testing is complete.

This is a high-level view. A real Gantt chart would have more detailed
tasks and dependencies, providing a clear picture of the project
schedule and milestones for developing the library management
system.
Gantt Chart for Library Management System:
Result and Discussion:

Learning Outcome:

Course Outcome:

Conclusion:

Viva Questions:

Correction Formative Timely Attendance

Parameters Assessment [ ] Completion of Learning
Practical [ ] Attitude [ ]