American International University-Bangladesh (AIUB)

Damage Device

A software Requirement Engineering Project

Submitted By: Mrs. FARZANA BENTE ALAM

Sec: B

Project Member’s
Name ID
Fahad Mollah 18-36702-1

Abdur Rakib Howlader 18-37061-1

Mahia Islam 17-35068-2

Khan Golam Rabbi 16-32054-2

1 Introduction:

1.1 Purpose –
Students or Device workers needs sometime second hand or damage
device to fix their problem. In this scenario they have to go in a fix place
to buy their needs. Also in the local area we don’t have available shop.
For the problem we bring a new solution and opportunity. Students and
device workers can get their needs through this system.

1.2 Document Convention –

This document follows MLA format. Bold-faced text has been used to
emphasize section and sub-section headlines.

1.3 Project Scope –

The purpose of the project Students or Device workers needs sometime

second hand or damage device to fix their problem. In this scenario, they have to
go in a fix place to buy their needs. Also in the local area, we don’t have
available shop. For the problem, we bring a new solution and opportunity.
Students and device workers can get their needs through this system.

1.4 Reference-
Wiegers, K., & Beatty, J. (2013). Software requirements. Pearson
Education
2. Overall Description

The online shopping system enables vendors to set up online shops, customer to
browse through the shops and system administrator to approve and reject request
for new shops and maintain list of shop categories. The online shopping system
will use the internet for selling goods for its customer.

2.1 Product Perspective

This product aimed toward a person who don’t want to visit the shop as he don’t
get time for that might not interested in visiting physical shop or dealing with lit of
formalities.

2.2 User & Characteristics

User should be familiar with the terms like login, register, order, cart etc.
The user can login using the account details or new customer can set up an account
and they should give the details of their full name, email address account,
username and password.

2.3 Operating Environment

The system operates the following components

A full time internet connection is needed for online shopping and any operating
system and a browser like chrome, Firefox, opera etc.

2.4 Design & Implementation Constrains

Memory: Device have to be 2GB internal hard drive. Our software and database
can’t exceed this amount.

Internet: A full internet connection is required when using the system.

Operating System: Software does not required any specific operating system.
3 SPESIFIC REQUIREMENTS
3.1 Description of Feature

Two interfaces in the system, one will be between user and system, and
the other will be between system and database.

3.2 Functional Requirements

This section explains the use cases.

3.2.1 Use Cases

The user has these user cases.

Log In Log Out Search

Sign Up
Browse Profiles

Request an exchange Browse categories

Browse Items
Mark as a Favorite

Approve the exchange Edit Profile

User
Decline the exchange Buy Credits

Add Item(s) to cart

Purchase item(s) with credit

Edit the item

Notify for shipment
Remove Item
Add Item Delete Profile
Rate and Comment
3.2.1.1 Use Case: Sign Up

Sign Up

User

Enter username, name, surname, password, mail address, set a profile photo.
When the user fills all necessary fields, an activation mail will be sent to users
mail address.
User will be able to log in and start using the system just after activating
his/her account.
3.2.1.2 Use Case: Log In

Login

User

Enter username or email and password to log in to the system.

3.2.1.3 Use Case: Log Out

Log Out

User

Press log out button to logs out of the system. Cannot use the system until
logged in again.
 3.2.1.4 Use Case: Search

Search

User

Search items. Search items according to the price, their location, their
category.

3.2.1.5 Use Case: Browse Profiles

Browse Profiles

User

Browsing the profiles of other users. Can see the other users’ user names,
profile photos, and the users’ items.
3.2.1.6 Use Case: Browse Categories

Browse Categories
User

Browse categories according to requirement/wishes. Can see how many items

each category has.

3.2.1.7 Use Case: Browse Items

Browse Items

User

Browse items. Can see the items’ pictures, prices, and other features.
3.2.1.8 Use Case: Edit Profile

Edit Profile

User

Can change his/her username, email address, profile picture and password.
Changing username or password, a notification mail will be sent. The changes
will apply if clicked on the link in the email.

3.2.1.9 Use Case: Buy Credits

Buy Credits

User

can buy credits from the system. Can use credit card or his/her BKash
account.

3.2.1.10 Use Case: Add Item(s) to Cart

Add item(s) to cart

User

Can add the items to cart by touching “Add to the cart” button.
3.2.1.11 Use Case: Purchase Item(s) with Credit

Purchase item(s) with credit

User

Can buy items he/she has added to cart with credits, if the items are
available for buying with credits.

3.2.1.12 Use Case: Request an Exchange

Request an exchange

User

If the item needed is available for exchange, can request the exchange of
items.
3.2.1.13 Use Case: Approve the Exchange

Approve the exchange

User

Can approve the exchange that is offered by another user by clicking

“Approve” button.

3.2.1.14 Use Case: Decline the exchange

Decline the exchange

User

Can decline the exchange that is offered by another user by clicking

“Decline” button.

3.2.1.15 Use Case: Notify for Shipment

Notify for shipment

User

The user notifies other user that the shipment of the item has started.

3.2.1.16 Use Case: Add Item

Add Item

User
 Can add as many as items as needed. Can also set the price, set the amount,
upload pictures of the item and add details of the item.

3.2.1.17 Use Case: Edit Item

Edit Item

User

Can edit the items that he/she has already put on the system. Can
add/remove pictures, change the price and details of the item.

3.2.1.18 Use Case: Remove Item

Remove Item

User

No longer wishes to sell/exchange the item, can remove the item from the
system by touching “Remove the item” button.
3.2.1.19 Use Case: Delete Profile

Delete Profile

User

Can click “Delete Profile” button to delete profile.

3.2.1.20 Use Case: Mark as a Favorite

Mark as a favorite

User

Can mark an item as a favorite, will be notified via email if any change is made to the item

3.2.1.21 Use Case: Rate and Comment

Rate and Comment

User

Can rate and comment about the item

3.3 Non-Functional Requirements

For running the system, Eclipse should be installed on the computer. In

addition, JDK, JVM or JRE must be installed too.
3.3.1 Performance Requirements

10000 users should be able to use the system at the same time. The
response time of the system should be 2 seconds at most.

3.3.2 Design Constraints

We will use “Agile method” and Object – Oriented Programming

paradigm. We will use Java as programming language. The Android
version of the device should be 2.3 or higher. The system requires Internet
connection all the time.
4. External Interface Requirements

4.1 User Interface

The ‘DAMAGE DEVICE’ store has been specially designed a user interface for
the customer which is very user friendly.

HOME PAGE

This is the home page of our system where user can also access our Facebook
page.

HOME REGISTER LOGIN ABOUT_US CONTACT_US

SHOP NOW

PRODUCTS
REGISTER

The person who want to register he/she click the register button then fill up the
requirement and click on the register button.
LOGIN

For login click the login button and write down the requirement then click send
button.
CONTACT US

4.2 Software Interface

Operating system: Windows 10 & Mac operating system.

4.3 Hardware Interface

Processor: Dual core

RAM: 2GB
Hard Disk: 320GB

4.4 Communication Interface

Two parties should be connected by LAN or WAN for the communication.

Communication
Sender Receiver
5.1 Usability
We are keeping a simple and user-friendly design in order for a customer to have
an enjoyable usability. Keeping facts like no need for unnecessary logins, having a
minimal yet not too simple design, things like promotions will be upfront in the
home screen. We are trying to keep everything balanced as it is seen that the
necessary stuff like "Add to Cart" button are not strategically placed where
customer can just get easy access. We are also trying to keep the products
categorized so that it is easier for a customer to locate something he is looking for.
The top priority here is Customer Satisfaction and A Good User Experience.

5.2 Performance

Now it is obvious that a website with multitude of hi-raze images, assets, java
scripts, and html files, can slow a website down reducing the performance of it.
Being a start-up we are to face slowing down of our site as it is an e-retail shop for
second hand or damage device.

5.2.1 Reduce Number of Requests

Combine scripts and images using concatenation

Combine images and CSS (Cascading style sheet) with sprites
Employ data URIs

5.2.2 Reduce Asset Weight

Use Gzip
Minify scripts
Use glossy and lossless image compression

5.2.3 Employ Parallel Processing

Load 3rd party assets asynchronously

Use domain sharing
Use intelligent script loaders
5.3 Integrity

This non-functional requirement assures that all data inside the system will be
protected against unauthorized access. To ensure this quality attributes we have
used an experienced security software developers to identify and resolve security
issues. A security software developer is someone who develops security software
as well as integrates security into software during the course of design and
development. For develop the system we Selected Appropriate System and Service
Providers.

5.4 Reliability

This quality attribute specifies how likely the system would run without a failure
for a given period. The high complexity of software is the major contributing
factor of Software Reliability problems. We have used agile process during our
system development. The Agile methodology deliver software faster and more
reliably through an iterative approach to development. And our system is almost
failure-free for a specific period of time.

5.5 Maintainability

Maintainability is the ability of the system to support changes. This quality

attribute defines the time required for a solution. The purpose of maintainability is
to improve effectiveness and efficiency of maintenance. For an example the system
has a maintainability of 1-exp (-10/9.4) = 65.5%. The maintainability value is the
probability of completing the repairs in the allowed interval of 10 hours.

5.6 Technical Issues

This system will work on client-server architecture. It will require an internet

server and which will be able to run HTML application. This system should
support some commonly used browser such as Google Chrome, Mozilla Firefox
and Internet Explorer.

6. Data Requirements
 6.1 Logical Data Model – UML diagram

LOGIN

Manage customer
database Browse category

View/Delete Add/Remove item

customer booking from cart

Administrator
Payment
Add/Remove/updat
e item category
<e> <e>
By credit bkash
card
Customer
Shipping order
Give review

LOG OUT

Visit site View account

detail
Visitor
\\\\
Create new account Cancel order
before shipping

6.2 Process Flow Diagram