University of Management and Technology,

Lahore Campus

Assignment – 02: Spring 2024

Software Requirement Credit
Course Name: Course Code: SE2102 4(3,1)
Engineering Hours:
Course Instructor/s: Mr. Waqar Ashiq Program Name BS Software Engineering
Semester/ Section: BSSE 4, W3 Maximum Marks: 20
Submission Moderator
Jun 8, 2024
Deadline: Signature
Instructions:
• Understanding the problem is a part of the task.
• Your assignment should be submitted in PDF format.
• There is a ZERO tolerance policy for plagiarism. Tasks found with copy-pasted material or copied
from fellows will be marked as ZERO.
• Submit your assignments on LMS within the given time frame. Emailed Tasks will not be accepted.
• I can take either quiz or in-class viva for this assignment by calling anyone from the class.
• Answer must be to the point.

Name:Muhammad Moin ud din Zafar

Roll #: F2022065224
Question 1: Draw the use case diagrams and write a user requirements of the
following scenarions, :

Scenario 1:
We have an online shopping system designed to offer a secure and convenient shopping experience
for customers. The system begins with a customer logging into the platform using an external
identity provider that authenticates their credentials. Once logged in, the customer can browse
through a catalog of items, viewing details about each product. When a customer decides to
purchase an item, they initiate a process that includes selecting the item for purchase, which is
directly linked to the item viewing functionality. Following this selection, the customer proceeds
to complete the checkout process. This process involves several steps, including the authentication
of the customer's identity and the processing of payments. The system integrates with external
services such as a credit payment service and PayPal to handle transactions securely. The
comprehensive nature of this system ensures that the customer can manage their purchases from
viewing items to completing transactions smoothly and securely. This scenario requires to create
a use case diagram that illustrates these interactions and dependencies within the system.
User Requirements

Authentication and Authorization

UR01: The framework will permit clients to sign in utilizing an outer character supplier (e.g.,
Google, Facebook).

UR02: The framework will validate client accreditations through the picked outside personality
supplier.

UR03: The framework will guarantee secure treatment of client certifications during the
confirmation interaction.

Browsing and Viewing Products

UR04: The framework will give a list of things to clients to peruse.

UR05: The framework will permit clients to see itemized data about every item, including pictures,
portrayals, costs, and accessibility.

UR06:. The framework will empower clients to look for explicit items inside the index.

Item Selection and Shopping Cart Management

UR07: The framework will permit clients to choose things for buy and add them to their shopping
basket.

UR08: The framework will interface the thing determination usefulness straightforwardly to the
item seeing usefulness.

UR09: The framework will empower clients to see and deal with the items in their shopping basket,
including refreshing amounts and eliminating things.

Checkout Process

UR10: The framework will give a checkout cycle to clients to finish their buys.
UR11: The framework will confirm the client's personality during the checkout interaction to
guarantee security.

UR12: The framework will safely deal with installment handling through combination with
outside installment administrations, for example, credit installment administrations and PayPal.

UR13: The framework will affirm the effective consummation of the exchange to the client.

Payment Processing

UR14: The framework will incorporate with outer credit installment administrations to handle
charge card exchanges.

UR15: The framework will coordinate with PayPal to handle installments.

UR16: The framework will guarantee the protected treatment of installment data during exchanges

Security and Data Protection

UR17: The framework will guarantee that all touchy client information, including individual and
installment data, is scrambled and safely put away.

UR18: The framework will guarantee that all touchy client information, including individual and
installment data, is scrambled and safely put away.

User Experience and Accessibility

UR19: The framework will give an easy to understand interface that is not difficult to explore for
all clients.

UR20: The framework will be available with clients with inabilities, complying to openness
principles and rules.

UR21: The framework will give client care choices to help with the stage.

Order Management
UR22: The framework will permit clients to see their request history and track the situation with
their ongoing orders.

UR23: The framework will email request affirmation and announcements to clients or other
specialized techniques.

Use Case Diagram

Scenario 2:
In this scenario, explore the functionalities of a website from the perspectives of two types of users:
a standard site user and a webmaster. The site user has access to a range of functionalities starting
with the ability to log in to the website. Once logged in, the user can perform several tasks: they
can browse through documents, search for documents using full-text search, and view details of
upcoming events. Each document viewed can also be previewed and downloaded if needed.
Additionally, users can upload documents, which is a functionality that extends to managing
folders, allowing users to organize their uploads into structured directories.
On the other hand, the webmaster has administrative privileges that include not only all the
functionalities available to the standard site user but also several extended capabilities. The
webmaster can post new events to the homepage to keep the site updated with the latest activities.
They can also add new users to the website, which extends to adding entire companies, allowing
group management under single entities. This scenario illustrates a comprehensive system where
different user roles are assigned specific responsibilities and privileges, enhancing the
functionality and management of the website.

User Requirements For Standard Site User

Authentication and Access

UR01: The framework will permit standard clients to sign in to the site utilizing a solid verification
process.

Document Browsing and Management

UR02: The framework will furnish standard clients with the capacity to peruse records accessible
on the site.

UR03: The framework will empower standard clients to perform full-text searches to track down
unambiguous archives.

UR04: The framework will permit standard clients to see subtleties of each archive, including
metadata like title, creator, and date.

UR05: The framework will permit standard clients to see archives straightforwardly on the site.

UR06: The framework will empower standard clients to download archives on a case by case
basis.
Event Viewing

UR07: The framework will give standard clients the capacity to see subtleties of impending
occasions recorded on the site.

Document Uploading and Organization

UR08: The framework will permit standard clients to transfer new archives to the site.

UR09: The framework will empower standard clients to make and oversee envelopes to coordinate
their transferred reports into organized catalogs.

User Requirements For Standard Webmaster

Administrative Privileges

UR10: The framework will give website admins every one of the functionalities accessible to
standard webpage clients.

Event Management

UR11: The framework will permit website admins to present new occasions on the landing page
to keep the webpage refreshed with the most recent exercises.

UR12: The framework will empower website admins to alter and erase existing occasions from
the landing page.

User and Company Management

UR13: The framework will furnish website admins with the capacity to add new clients to the site.

UR14: The framework will permit website admins to add whole organizations to the site, working
with bunch the executives under single elements.

UR15: The framework will empower website admins to oversee client jobs and authorizations,
including doling out managerial honors to different clients if necessary.
Security and Data Integrity

UR16: The framework will guarantee that website admins can oversee site security settings,
including secret phrase arrangements and access controls.

UR17: The framework will permit website admins to back up and reestablish site information to
guarantee information trustworthiness and recuperation in the event of disappointments.

Monitoring and Reporting

UR18: The framework will give website admins admittance to site utilization measurements and
reports to screen client exercises and framework execution.

UR19: The framework will permit website admins to produce custom reports in view of explicit
measures, for example, archive transfers, downloads, and occasion support.

Use Case Diagram

Scenario 3:
In this scenario, the focus is on the interactions between a traveler, a clerk, and a railway website
within a railway ticket booking system. The process begins when a traveler decides to book a ticket
using the railway website. Initially, the traveler checks the availability of tickets for their desired
journey. If tickets are available, the traveler proceeds to book a ticket. This booking process
includes filling out personal information and travel details, a mandatory step before proceeding.
Once the information is filled in, the booking is completed by paying the fare amount.

However, if the traveler needs to cancel the ticket, the process involves interactions with a clerk.
The traveler contacts the clerk to initiate the cancellation, who then processes the request through
the system. After successfully cancelling the ticket, the system triggers a refund process, where
the money paid by the traveler is returned. This comprehensive system efficiently manages
booking, cancellation, and refund processes, ensuring a smooth operation for both travelers and
railway staff.

User Requirements

Ticket Booking

UR01: The framework will permit voyagers to really look at the accessibility of tickets for their
ideal process.

UR02: The framework will empower voyagers to book tickets through the rail line site in the event
that tickets are accessible.

UR03: The framework will expect voyagers to finish up private data and travel subtleties as a
feature of the ticket booking process.

UR04: The framework will permit voyagers to finish the booking system by paying the charge
sum through secure installment techniques.
Payment Processing

UR05: The framework will safely deal with installment exchanges for ticket appointments.

UR06: The framework will give various installment choices (e.g., Visa, charge card, internet
banking) to finish the booking.

Ticket Cancellation

UR07: The framework will empower voyagers to start ticket undoing by reaching a representative.

UR08: The framework will permit representatives to handle ticket retraction demands through the
framework.

Refund Processing

UR09: The framework will naturally set off a discount interaction once a ticket is effectively
dropped by the representative.

UR10: The framework will guarantee that the discount is handled and gotten back to the voyager's
unique installment technique inside a predetermined time period.

User Authentication and Authorization

UR11: The framework will expect explorers to sign in or register on the rail route site to book or
drop tickets.

UR12: The framework will guarantee secure treatment of client accreditations during the
confirmation interaction.

UR13: The framework will permit agents to have suitable access freedoms to oversee wiping out
and discount processes.

User Experience and Interface

UR14: The framework will give an easy to understand interface on the rail line site for explorers
to check accessibility, book tickets, and oversee appointments.
UR15: The framework will give a clear and effective point of interaction for representatives to
deal with ticket retractions and discounts.

Notifications and Communication

UR16: The framework will send affirmation messages or messages to voyagers upon effective
ticket booking.

UR17: The framework will send notices to explorers in regards to the situation with their dropping
and discount processes.

Data Security and Privacy

UR18: The system shall ensure that all personal and payment information provided by travelers is
encrypted and securely stored.

UR19: The system shall comply with relevant data protection regulations to ensure the privacy
and security of traveler data.

Reporting and Audit

UR20: The framework will keep up with logs of all reserving, abrogation, and discount exchanges
for review purposes.

UR21: The framework will give reports to approved staff to checking and dealing with the booking
and retraction exercises.

Use Case Diagram