Software Requirement Specifications & Analysis

Report
Only for course Teacher
Needs
Improvement
Developing Sufficient Above
Average
Total
Mark
Allocate mark & Percentage 25% 50% 75% 100% 5
Clarity 1
Content Quality 2
Spelling & Grammar 1
Organization and
Formatting
1
Total obtained mark
Comments
Semester: Spring 2023
Group Members Name & ID:
1. Md. Rasel Hossain ID: 0242220005341013
2. Kayes Ahmed Himu ID: 0242220005341035
3. Md Sajidur Rahman Shimul ID: 0242220005341051
4. Shifat Hasan ID: 0242220005341061
5. Md. Ahanaf Mohosen ID: 0242220005341072
6. Anisur Rahaman ID: 173-35-2281
Batch: 39th
Section: “A”
Course Name: Software Requirement Specifications & Analysis
Course Code: SE-212
Course Teacher Name: Tapushe Rabaya Toma
Designation: Assistant Professor, Department of Software Engineering, DIU
Submission Date: 04 June 2023

Industrial Tour
MENS WORLD Savar City Center-1 Showroom, Savar, Dhaka
Tour Pictures:

About the Software System
UniPose:
Empowering Business Management through Seamless Integration.
Abstract:
UniPose, a comprehensive software system that empowers businesses across diverse
industries. UniPose seamlessly integrates key functionalities to streamline operations,
enhance productivity, and maximize overall efficiency. This paper provides a captivating
overview of UniPose's key features, its target stakeholders, and the exceptional benefits
it brings to businesses. UniPose provides a user-friendly dashboard for real-time
monitoring of essential business metrics and generating customized reports.
How did Impact in Business:
In today's dynamic business landscape, organizations face intricate challenges in
effectively managing their operations. UniPose emerges as a beacon of innovation,
offering an integrated solution that simplifies and optimizes business management
processes. With its unwavering focus on enhancing productivity, improving decision-
making, and streamlining operations. UniPose simplifies task assignment, progress
tracking, and deadline management, facilitating efficient project execution.

Elicitation Technique (Group Interview)
The group interview elicitation technique is a method used to gather information and
insights from multiple stakeholders simultaneously. In the context of UniPose, conducting
a group interview can be a valuable approach to gather feedback and requirements from
various stakeholders involved in the software implementation. That’s why we choose
these techniques for conduct the requirements. Here, how we approach the process:
1. Identify Stakeholders: Review the possible list of stakeholders such as the
Manager, Staff, Owner, and Store Supervisor. Determine the participants who
should be included in the group interview based on their roles and responsibilities.
2. Schedule the Interview: Coordinate with the stakeholders to find a suitable time
and location for the group interview.
3. Introduce UniPose: Start the group interview by understanding an overview of
UniPose, highlighting its key features, and explaining its potential impact on the
stakeholders' respective roles and responsibilities.
4. Note Responses: Assign a note-taker to document the stakeholders' responses,
ideas, and suggestions during the interview to ensure accurate capture of the
information discussed.
5. Follow-up and Documentation: After the group interview, compile the notes from
the session. Analyze the information gathered, extract actionable insights require
further clarification.
The group interview elicitation technique enables a collaborative approach to gathering
requirements and insights from multiple stakeholders simultaneously. By using this
technique in the given scenario, UniPose can ensure that the software meets the needs
and expectations of its diverse user base, leading to successful implementation and
improved business management.

User Profile: (Manager)
User Class Notes on Characteristics Requirement Implied
Type of user Manager Interface
Age range 24-40 Interface
Frequency of use Many times, in a day
Performance, Operation,
Safety, Security, Reliability
Mandatory / Discretionary Yes
Computer experience
O/s
Applications
Yes Documentation
Education At least Under Graduate
Goals
Efficiently manage the
business operations
Portability, Acceptance,
Safety, Security,
Reliability, and Quality.
Language skills English Interface
Number of users One
Security, Safety,
Reliability, Verification,
Acceptance, Quality,
Maintainability
Training Must be provided Documentation
Other system used No
Ways of working
Multiple tasks
simultaneously
Acceptance, Quality,
Maintainability

SRS Documentation
FR 01 Log In
Description All users need to log in first to use the system.
Stakeholders Manager, Staff, Owner
FR 02 Forget Password
Description If users forget username and password, they can request for forget
the password.
FR 03 OTP Verification
Description When the users apply for forget password the system send a
verification code for validation check.
FR 04 Set New Password
Description Users can a set a new password if they forgot their previous
password.
FR 05 Dashboard Overview
Description In dashboard overview users can see the summary of every possible
action.
Stakeholders Manager, Staff
FR 06 Product Categories
Description Manager can see all the products by their categories and also can
take needed action.
Stakeholders Manager
FR 07 Search Product
Description Employee can search any product by their code number.

FR 08 Product Details
Description Employee can see the product details to know more about it that
he/she can explain it to customer.
FR 09 Inventory Management
Description In inventory option manager can manage inventory more effectively
where he can see and track the quantity of each item in stock.
FR 10 Request New Products
Description If any product is low or finish in stock manager can create a new
order request.
FR 11 Return Products
Description If any product is need to return for any kind of defect or problem
manager can send a request.
FR 12 See Order List
Description When customer place an order from their brand website to a specific
branch manager can see the order list.
FR 13 Create Billing
Description Shop employee can create billing of the purchase for a customer.
FR 14 Payment Method
Description The software is integrated with banking system and mobile banking
so when a customer wants to pay with those option shop employee
selects their suitable option from the software & also can take cash.

FR 15 Mobile Banking Option
Description If the customer wants to pay with mobile banking manager or staff
can select mobile pay option from software.
FR 16 Banking Card Option
Description If the customer wants to pay with Bank account manager or staff can
select Banking card pay option from software.
FR 17 Membership Management
Description Manager can manage and issue new membership card and also can
delete existing members as well.
FR 18 Membership Details
Description Manager can see all the details of their premium membership card
holder like Phone number, Mail address and if there is any kind of
special offer manager can use the data to reach them.
FR 19 Push Notification
Description Manager can notify all kind of customer via SMS & E-mail if there
any stock renew & also if new products or offer available.
FR 20 Customer Details
Description Employee can see all customer information for future possible
action.
FR 21 Sales Tracking
Description By using this option manager can track all the sales are coming and
can see which products are generate most selling. Owner can
overview it as well.
Stakeholders Manager, Owner

FR 22 Sales Report (Monthly, Weekly, Daily)
Description Manager can generate sales reports, including sales by product,
sales by date & time, and sales by location.
FR 23 Tax Calculation
Description Manager can calculate taxes by one click based on configurable tax
rates and apply them to sales transaction.
FR 24 Employee Management
Description Manager can see all the details of Staff and manager can take
necessary action also.
FR 25 Assign New Employee
Description Manager can input or assign new staff by the instruction of Owner.
FR 26 Remove Employee
Description If any staff resigns their job manager can easily remove them from
the employee management list.
FR 27 Transfer Employee
Description When there is need to transfer any staff from a branch to another
branch manager can take the action from the system.
FR 28 Employee Performance
Description This module allows managers to conduct regular performance
evaluations for their staff members.
FR 29 Sales Commission Management
Description The software includes a module for calculating and managing sales
commissions for employees based on their sales performance.

FR 30 Select Attendance
Description All the employee can select their attendances in daily basis.
Stakeholders Staff, Manager
FR 31 Input Attendances
Description All the employee can input their attendances in daily basis.
Stakeholders Staff, Manager
FR 32 View Attendances
Description Employee can see attendances of the theirs and manager can
generate attendances report as well.
FR 33 Expense Tracking
Description The software allows managers to enter daily expenses, including
categories such as tiffin costs, transportation expenses, office
supplies, or any other relevant expenditure.
FR 34 Sales Forecasting
Description The software provides sales forecasting capabilities, predicting
future sales based on historical data, trends, and seasonality
manager can see it.
FR 35 Transfer Products
Description The software supports the transfer of products between different
store locations, ensuring accurate inventory management and
tracking of stock movement this action can be done by manager.
FR 36 Help and Support
Description The software provides a user-friendly help system or knowledge
base to assist users in navigating the software and finding answers
to common questions.

FR 37 IT Support
Description The software provides comprehensive IT support to address
technical issues, system errors so if any users face this type of
problem, they can report it.
FR 38 Log Out
Description The software includes a log out functionality that allows users to
securely and effectively log out when they have finished their
session.

Case Description (1013)
Use Case See Customer Details
Goal
The goal of this use case is to allow the manager to view all customer
information for future possible actions.
Precondition -------------------------------------------------------------------------------------------
Success End
Condition
The manager successfully views all customer details for future
actions.
Failed End
Condition
The system fails to retrieve or display customer details accurately.
Primary Actor:
Secondary Actor:
Manager, Staff
Trigger The manager initiates a request to view customer details.
Description/Main
Success Scenario
1.
The manager logs into the system and navigates to the
customer details section.
2.
The system retrieves and displays a list of all customers
along with their relevant information, such as name,
contact details, address, and purchase history.
3.
The manager selects the option to view all customer
details.
4.
The manager can search, sort, or filter the customer list
based on specific criteria, if supported by the system.
5.
The manager can take necessary actions based on the
customer details, such as contacting the customer,
updating information, or making informed decisions.

Alternative Flows
1.a
If the system fails to connect to the database server.
1.a.1 error message: "Server not found."
2.a
The manager enters invalid credentials or does not have the
necessary authorization.
2.a.1. Error message: "Access denied. Please contact the
system administrator for assistance."
2.b
If there are no customer records in the system, the manager
is notified that no customer details are available.
2.b.1 Message: "No customer records found."
4.a
If there is a technical issue or connectivity problem, the
system fails to retrieve customer details.
4.a.1 Message: "Unable to retrieve customer details. Please
try again later."
5.a
If the manager chooses to exit without completing any
actions, the system returns to the main menu or previous
screen.
Quality
Requirements
Accessibility: The system should be accessible to the manager and
staff members at any time, allowing them to view customer details as
needed.
Security: The customer information should be securely stored and only
accessible to authorized personnel.
Scalability: The system should be capable of handling a growing
number of customer records without compromising performance.
Performance: The system should respond quickly and provide timely
access to customer details, even with a large number of records.

Use Case Select Payment Method
Goal
Enable customers to make payments using the integrated banking
system and mobile banking.
Precondition The customer has selected products or services for purchase.
Success End
Condition
The payment is successfully processed and confirmed.
Failed End Condition The payment is not processed or encounters errors.
Primary Actor:
Secondary Actor:
Manager, Staff
Trigger The customer initiates the payment process.
Description/Main
Success Scenario
1 The shop employee accesses the software.
2
The shop employee selects the suitable payment option from
the software (e.g., banking system or mobile banking)
3 The payment is successfully completed.
4
The software confirms the successful payment to the shop
employee.
5 The customer receives a payment confirmation.
Alternative Flows
1.a
The software fails to connect to the banking system or mobile
banking.
1.a.1. The software displays an error message:” Could not
connect to the server.”
2.a
The selected payment option does not have any suitable
payment methods for the given transaction.
2.a.1. The software displays an error message: “Wrong
payment option selected.”
Quality
Requirements
1. Secure integration with the banking system and mobile banking to
protect customer’s payment information.
2. Seamless and efficient payment processing to minimize transaction
time.

Use Case Manage Employee
Goal
To enable the Manager to efficiently manage employee details,
including hiring, termination, and staff transfers.
Precondition
The Manager has to be accessible to the employee management
system.
Success End Condition
Message “The employee details are successfully managed and staff
transfers are executed accurately.”
Failed End Condition
Message “The employee management process fails, resulting in
incorrect employee details or erroneous staff transfers.”
Primary Actors:
Secondary Actors:
Manager
Owner
Trigger
A request from the Manager to review and update employee details
such as hiring new staff, employee resignations or terminations within
the organization.
Description /Main Success
Scenario
1. The Manager accesses the system.
2. The Manager selects the "Employee Management" option.
3. The system displays a list of existing employees.
4.
The Manager can view the details of each employee,
including their name, position, contact information, and
assigned branch.
5.
The Manager can input or assign new staff based on the
instructions provided by the Owner.
6.
If an employee resigns, the Manager can remove them
from the employee management list.
7.
When a staff transfer is required from one branch to
another, the Manager can initiate the transfer process
through the system.
8.
The system updates the employee details, reflecting any
changes made, such as new hires, terminations, or staff
transfers.

Alternative Flows
1.a
Could not connect to the server.
1.a.1 Message “server not found”
3.a
If there are no existing employees, the system notifies.
3.a.1 Message “No employee records exist.”
5.a
Issues while inputting or assigning new staff.
5.a.1 Message “Please ensure all required fields are
filled correctly.”
6.a
Unable to remove an employee.
6.a.1 Message “Please try again later or consult with the
system administrator.’’
7.a
Difficulties during the staff transfer process.
7.a.1 Message “Please verify the information and try
again.’’
8.a
Encountered an issue while updating the information.
8.a.1 Message “Please ensure all fields are correctly
filled.”
Quality Requirements
The system should accurately store and display employee information
and ensure the access of the manager.

Use Case Manage Membership
Goal
The goal of membership management in a clothing shop is to enable
customers to join the shop's membership program, providing them with
exclusive benefits and privileges.
Precondition
The clothing shop has a membership program in place, and the customer
wants to participate in the program.
Success End
Condition
The customer successfully becomes a member of the clothing shop's
membership program.
Failed End Condition
The customer fails to become a member of the clothing shop's
membership program.
Primary Actor
Secondary Actor
Manger, Staff
Trigger Customer makes a purchase.
Description/Main
Success Scenario
01 The manager accesses the membership management system
or dashboard.
02 The manager views a list of existing members, including their
names, contact information, and membership status.
03 The manager collects the necessary information from the
customer for add new member
04 The manager can update existing members' information
05 The member receives their membership ID or card from the
manager.
06 The manager verifies the member's identity by matching the
ID or card with the member's name or other identifying
information.
Alternative Flows
1a Could not connect to the server.
1.a.1 message “server not found”
3a Information is invalid.
3.a.1 message “submit right information”
6a Wrong ID Number.
6.a.1 message “No ID available”
Quality Requirements
The membership management system should securely store customer
information and protect it from unauthorized access.

Use Case Push Notification
Goal
The goal of Push Notification is to allow the manager to notify
customers via SMS and email about stock renewal, new products,
and offers.
Precondition -------------------------------------------------------------------------------------------
Success End
Condition
Customers receive notifications regarding stock renewal, new
products, and offers through SMS and email.
Failed End
Condition
Customers do not receive the notifications or encounter technical
issues preventing delivery.
Message:” Notification send failed”
Primary Actor:
Secondary Actor:
Manager
Trigger
The manager sends a notification to inform customers about stock
renewal, new products, or offers.
Description/Main
Success Scenario
1. The manager logs into the notification system.
2.
The manager selects the target audience for the
notification
(All customers or specific segments).
3.
The manager drafts the notification message, including
details about stock renewal, new products, or offers.
4.
The system sends the notification to the selected
customers' phone numbers and email addresses.
5.
Customers receive the push notification through SMS and
email.

Alternative Flows
1.a
The push notification system encounters technical issues
and fails to connect to the SMS or email gateway.
1.a.1. Error message: "Connection to SMS/Email
gateway failed."
2.a
No customers match the selected target audience criteria.
2.a.1. Error message: "No customers found for the
selected target audience."
3.a
3.a. The manager encounters difficulties while drafting the
notification message.
4.a
Customers' phone numbers or email addresses are
incorrect or outdated, leading to delivery failures.
4.a.1. Error message: "Delivery failed for some
customers. Invalid phone numbers/email addresses."
5.a ------------------------------------------------------------------------------
Quality
Requirements
1. Security: Customer contact information should be securely
stored and protected to maintain privacy.
2. Scalability: The system should be capable of handling a large
number of push notifications to reach all targeted customers
efficiently.
3. Performance: The system should send push notifications
promptly to ensure timely delivery to customers

Case Description (173-35-2281)
Use Case Track Sales
Goal
The goal of this use case is manager can track all the sales are
coming and can see which products are generate most selling.
Precondition -------------------------------------------------------------------------------------------
Success End
Condition
The manager successfully can track all the sales are coming and can
see which products are generate most selling. Owner can overview it
as well.
Failed End
Condition
The system fails to retrieve or display Sales Tracking accurately.
Primary Actor:
Secondary Actor:
Manager
Owner
Trigger The manager initiates a request to Track Sales Report.
Description/Main
Success Scenario
1.
The manager logs into the system and navigates to the
Sales Tracking section.
2. The manager selects the option to view all Product List.
3.
The system retrieves and displays a list of all Products
along with their relevant information, such as total Sales,
Best Selling products.
4.
The manager can analyze the filtered sales data, such as
total sales, best-selling products, or specific sales trends
related to the selected categories.

Alternative Flows
1.a
If the system fails to connect to the database server.
1.a.1 error message: "Server not found."
2.a
The manager enters invalid credentials or does not have the
necessary authorization.
2.a.1. Error message: "Access denied. Please contact the
system administrator for assistance."
3.a
If there are no products records in the system, the manager
is notified that no products are available.
3.a.1 Message: "No products found."
Quality
Requirements
The system should be accessible to the manager and Owner at any
time, allowing them to track all the sales as needed.

Requirement Prioritization (100 Dollar Test)
Requirements Values
1 Log In $2
2 Forget Password $2
3 OTP Verification $1
4 Set New Password $1
5 Dashboard Overview $3
6 Product Categories $5
7 Search Product $2
8 Product Details $3
9 Inventory Management $5
10 Request New Products $4
11 Return Products $2
12 See Order List $3
13 Create Billing $5
14 Payment Method $4
15 Mobile Banking Option $3
16 Banking Card Option $3
17 Membership Management $3
18 Membership Details $2
19 Push Notification $2
20 Customer Details $2
21 Sales Tracking $5
22 Sales Report $5
23 Tax Calculation $2
24 Employee Management $4
25 Assign New Employee $2
26 Remove Employee $2
27 Transfer Employee $1
28 Employee Performance $3
29 Sales Commission Management $2
30 Select Attendance $2

Based on the above table we decide the range of value as like,
• Highest Priority (4-5)
• Mid Priority (2-3)
• Lowest Priority (1)
So, we can list the requirements below:
Highest Priority Requirements { Product Categories, Inventory Management, Request
New Products, Create Billing, Payment Method, Sales Tracking, Sales Report, Employee
Management, Input Attendances }
Mid Priority Requirements { Log In, Forget Password, Dashboard Overview, Search
Product, Product Details, Return Products, See Order List, Mobile Banking Option,
Banking Card Option, Membership Management, Membership Details, Customer Details,
Tax Calculation, Assign New Employee, Remove Employee, Employee Performance,
Sales Commission Management, Select Attendance, View Attendances, Expense
Tracking, IT Support, Log Out }
Lowest Priority Requirements { OTP Verification, Set New Password, Transfer
Employee, Sales Forecasting, Transfer Products, Help and Support }
31 Input Attendances $4
32 View Attendances $2
33 Expense Tracking $2
34 Sales Forecasting $1
35 Transfer Products $1
36 Help and Support $1
37 IT Support $2
38 Log Out $2
Total $100

Traceability Matrix
REQ-1:
Log
In
REQ-2:
Forget
Password
REQ-3:
OTP
Verification
REQ-4:
Set
New
Password
REQ-5:
Dashboard
Overview
REQ-6:
Product
Categories
REQ-7:
Search
Product
REQ-8:
Product
Details
REQ-9:
Inventory
Management
REQ-10:
Request
New
Products
REQ-11:
Return
Products
REQ-12:
See
Order
List
UC-1: Log In ✔
UC-2: Forget Password ✔
UC-3: Verify OTP ✔
UC-4: Set New
Password
✔
UC-5: Overview
Dashboard
✔
UC-6: Filter Product
Categories
✔
UC-7: Search Product ✔
UC-8: See Product
Details
✔
UC-9: Manage Inventory ✔
UC-10: Request New
Products
✔
UC-11: Return Products ✔
UC-12: See Order List ✔

REQ-13:
Create
Billing
REQ-14:
Payment
Method
REQ-15:
Mobile
Banking
Option
REQ-16:
Banking
Card
Option
REQ-17:
Membership
Management
REQ-18:
Membership
Details
REQ-19:
Push
Notification
REQ-20:
Customer
Details
REQ-21:
Sales
Tracking
REQ-22:
Sales
Report
REQ-23:
Tax
Calculation
REQ-24:
Employee
Management
REQ-25:
Assign
New
Employee
UC-13: Create Billing ✔
UC-14: Select
Payment Method
✔
UC-15: Select Mobile
Banking Option
✔
UC-16: Select Banking
Card Option
✔
UC-17: Manage
Membership
✔
UC-18: See
Membership Details
✔
UC-19: Push
Notification
✔
UC-20: See Customer
Details
✔
UC-21: Track Sales ✔
UC-22: Generate
Sales Report
✔
UC-23: Calculate Tax ✔
UC-24: Manage
Employee
✔
UC-25: Assign New
Employee
✔

REQ-26:
Remove
Employee
REQ-27:
Transfer
Employee
REQ-28:
Employee
Performance
REQ-29:
Sales
Commission
Management
REQ-30:
Select
Attendances
REQ-31:
Input
Attendances
REQ-32:
View
Attendances
REQ-33:
Expense
Tracking
REQ-34:
Sales
Forecasting
REQ-35:
Transfer
Products
REQ-36:
Help
and
Support
REQ-37:
IT
Support
REQ-38:
Log
Out
UC-26: Remove
Employee
✔
UC-27: Transfer
Employee
✔
UC-28: Conduct
Employee Performance
✔
UC-29: Sales
Commission Management
✔
UC-30: Select
Attendance
✔
UC-31: Input Attendances ✔
UC-32: View Attendances ✔
UC-33: Track Expense ✔
UC-34: See Sales
Forecasting
✔
UC-35: Request Store
Transfers
✔
UC-36: Get Help and
Support
✔
UC-37: IT Support ✔
UC-38: Log Out ✔

Software Requirement Specifications & Analysis

Recommended

Recommended

More Related Content

Similar to Software Requirement Specifications & Analysis

Similar to Software Requirement Specifications & Analysis (20)

Recently uploaded

Recently uploaded (20)

Software Requirement Specifications & Analysis