Scribd
Upload
11 views5 pages

L1 211321 Nishal

The lab report focuses on requirements gathering and modeling a Use Case Diagram for a system in Object Oriented Software Engineering. It outlines functional and non-functional requirements necessary for system development, and describes the components and symbols used in Use Case Diagrams. The report concludes by highlighting the significance of structured requirements gathering and modeling in ensuring a user-focused approach to software development.

Uploaded by

nishalkarki605
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views5 pages

L1 211321 Nishal

The lab report focuses on requirements gathering and modeling a Use Case Diagram for a system in Object Oriented Software Engineering. It outlines functional and non-functional requirements necessary for system development, and describes the components and symbols used in Use Case Diagrams. The report concludes by highlighting the significance of structured requirements gathering and modeling in ensuring a user-focused approach to software development.

Uploaded by

nishalkarki605
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

NEPAL COLLEGE OF INFORMATION

TECHNOLOGY BALKUMARI LALITPUR

(Affiliated to Pokhara University)

A Lab Report
On

Subject: Object Oriented Software Engineering


Lab Report # 1

Submitted By: Nishal Karki


Roll no: 211321
Faculty: Science and Technology

Submitted To:
Instructor :Er. Manil Vaidhya
DEPARTMENT OF COMPUTER ENGINEERING

Submission Date: 2081-09-02


Title: Requirements gathering and use case diagram.
Objective
The objective of this lab is to systematically gather and document the requirements of a system
and model the interactions between the system and its users using a Use Case Diagram. This
practice aims to ensure a user-focused and structured approach to system development.
Introduction
Requirements gathering and Use Case Diagram modeling are fundamental
activities in the software development lifecycle.

Requirements Gathering

● Functional Requirements

Functional requirements define the specific actions the system must perform
to satisfy user needs. For the given system:

1. Thesystemmustallowuserstoregisterandloginusingvalidcredentials.
2. Thesystemmustdisplayapersonalizeddashboardforusersafterloggingin.
3. Usersshouldbeabletocreate,edit,anddeletetheirrecords.
4. Thesystemmustallowadministratorstoviewandmanageuserdata.
5. A search functionality must be available to find specific information efficiently.
● Non-Functional Requirements

Non-functional requirements define the quality attributes of the system. For


the given system:

1. Thesystemshouldrespondtouseractionswithin2seconds.
2. Datashouldbeencryptedtoensuresecurityandconfidentiality.
3. The system must be scalable to support up to 10,000 concurrent users.
4. Theuserinterfacemustbeintuitiveandaccessibleacrossdevices.
5. Errormessagesshouldbeclearandhelpfultoguideusers.

Use Case Diagram

A Use Case Diagram is a type of diagram in the Unified Modeling Language (UML) that
represents the functional requirements of a system. It shows the interactions between external
actors (users or systems) and the system’s use cases, which are specific functionalities or tasks
the system can perform. This diagram is widely used to understand system behavior
and ensure alignment with user needs.
Symbols in Use Case Diagrams

1. Actors:Representedbystickfigures,theyindicatetheentitiesinteractingwiththesystem
(e.g., users, external systems).
2. UseCases:Representedbyovals,theydescribethespecificactionsorfunctionalitiesthe
system performs.
3. System Boundary: Represented by a rectangle, it defines the scope of the
system and includes all relevant use cases.
4. Relationships:
○ Associations:Linesconnectingactorstousecases,showinginteractions. ○
Include:Dashedarrowswiththelabel"include,"representingmandatory
relationships where one use case includes the functionality of another.
○ Extend:Dashedarrowswiththelabel"extend,"representingoptional
relationships where additional functionality is conditionally added to a use case.

Actors:

1. User: Regularusersofthesystemwhointeractwithprimaryfunctionalitiessuchaslogin
and dashboard access.
2. Administrator:Managesuserdataandoverseessystemoperations.

Use Cases:

1. Log In: Userscanloginwithvalidcredentials.


2. ViewDashboard:Userscanviewapersonalizedsummaryoftheirdata.
3. ManageRecords:Userscancreate,edit,ordeletetheirrecords.
4. SearchData:Userscansearchforspecificinformationwithinthesystem.
5. ManageUsers:Administratorscanview,edit,orremoveuserdata.
Diagrams
Conclusion
This lab emphasized the importance of structured requirements gathering and modeling in
software development. By identifying functional and non-functional requirements and
designing a Use Case Diagram, we ensured a comprehensive understanding of the system.

You might also like