The ICFAI University

Tripura
DEPERTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE
This is to certify that the project titled “Online second Hand Book Store” is the
bonafide work carried out by Suman Malakar, Riya Majumder, Riya Deb, Debalina
Debnath, student of B.Tech(CSE) of Department of Computer Science and Engineering,
The ICFAI University, Tripura during the academic year Semester-I, 2021-2022, in
fulfillment of the requirements for the award of the degree of B Tech (CSE) and that the
project has not formed the basis for the award previously of any other degree, diploma,
fellowship or any other similar title.

Signature : …………………………
Name of Faculty Guide: SWAPAN DAS
Designation: Asst. Professor

Signature:
Name: Abhijit Biswas
HOD, CSE

Signature:
Name: Dr. P.R. Borthakur
Dean, FST

© Department of Computer Science and Engineering, ICFAI University Tripura

i
 The ICFAI University, Tripura
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Declaration of Student

I hereby declare that the project entitled “Online Second Hand Book Store ” submitted
for the B.Tech (CSE) degree is our original work and the project has not formed the
basis for the award of any other degree, diploma, fellowship or any other similar titles.

Signature:
Student Name: Suman Malakar
Riya Majumder
Riya Deb
Debalina Debnath
ID No: 19IUT0020195
19IUT0020116
19IUT0020131
19IUT0020197
Program: B.Tech
Department of CSE

© Department of Computer Science and Engineering, ICFAI University Tripura

ii
 Abstract
Books are very essential for each and every one of
us in order to increase our knowledge. An online
book store is a virtual store on the internet where
customers can browse the catalog and select books
of interest. At checkout time, items in the e-
library will be presented as an order. At that
time, more information will be needed to complete
the request. Usually, the customer will be asked to
fill online form. An e-mail notification is sent to
the customer as soon as the order is placed.
This project intends different types of forms with
many types of books like story, drama, romance,
history, adventures, etc. it can manage studying of
books online, customers can choose many types of
books categories etc. Here, the user may select
desired book and view its price. The user may even
search for specific books on the website. Once the
user selects a book, he / she then has to fill in a
form and the book is provided for the user.
A customer can login to his / her account, can
browse any book of his / her own interest, and can
view prices and other details of selected book,
place his/her order and can select from payment
options. User needs to register on the site before
checking out so that, he / she can login using same
ID and Password next time. User can select any
payment option that he / she wish to, like Fast
Cash, Credit / Debit card or Cash on delivery.

© Department of Computer Science and Engineering, ICFAI University Tripura

iii
 ACKNOWLEDGEMENT
We take this opportunity to express our gratitude to our guide who
encouraged us with her critical and constructive suggestions in the
project work. We are also thankful for her valuable guidance in this
project which resulted with flying success. She benefited me and my
team with her experience skills in this project. We again thank all for
their support and development.

Firstly, we would like to thank our supervisor, Prof. Swapan Das, for
being a great mentor and the best adviser we could ever have. Her
advice, encouragement and critics are source of innovative ideas,
inspiration and causes behind the successful completion of this
dissertation. The confidence shown on me by her was the biggest
source of inspiration for me. This has been a privilege working with
her from last one month. I am highly obliged to all the faculty
members of science & Technology Department for their support and
encouragement.

We would like to express my sincere appreciation and gratitude

towards all the Faculty of Science & Technology for the support.
Finally, we are grateful to our parents for their support. It was
impossible for us to complete this thesis work without their love,
blessing and encouragement.

© Department of Computer Science and Engineering, ICFAI University Tripura

iv
TABLE OF CONTENTS
CHAPTER 1: PROJECT FEASIBILITY REPORT..................................................... 7
1.1. INTRODUCTION...................................................................................................... 7
1.2. PROJECT/PRODUCT FEASIBILITY REPORT.................................................................. 7
1.2.1. Technical Feasibility ......................................................................................... 7
1.2.2. Operational Feasibility ..................................................................................... 8
1.2.3. Economic Feasibility ........................................................................................ 8
1.2.4. Schedule Feasibility .......................................................................................... 8
1.2.5. Specification Feasibility.................................................................................... 8
1.2.6. Information Feasibility ..................................................................................... 9
1.2.7. Motivational Feasibility .................................................................................... 9
1.2.8. Legal & Ethical Feasibility............................................................................... 9
1.3. PROJECT/PRODUCT SCOPE ........................................................................................ 9
1.4. TOOLS AND TECHNOLOGY WITH REASONING ............................................................ 9
1.5. VISION DOCUMENT ................................................................................................. 10
1.6. RISK LIST ................................................................................................................ 11
1.7. PRODUCT FEATURES/ PRODUCT DECOMPOSITION ................................................... 11
CHAPTER 2: SOFTWARE REQUIREMENT SPECIFICATION (FOR OBJECT
ORIENTED APPROACH) ............................................................................................ 12
2.1 INTRODUCTION: ....................................................................................................... 12
2.1.1. System Specification........................................................................................ 12
2.1.2. Context Level Data Flow Diagram: ............................................................... 13
2.1.3. Capture "shall" Statements: ............................................................................ 14
2.1.4. Allocate Requirements: ................................................................................... 15
2.1.5. Prioritize Requirements: ................................................................................. 15
2.1.6. Requirements Trace-ability Matrix: ............................................................... 16
2.2. EXPLANATION ......................................................................................................... 17
2.2.1. Introduction..................................................................................................... 17

2.2.2. High Level Usecase Diagram: ........................................................................ 17

2.2.3. Analysis Level Usecase Diagram: .................................................................. 18
2.2.4. Usecase Description ....................................................................................... 19
CHAPTER 3: DESIGN DOCUMENT (FOR OBJECT ORIENTED APPROACH)25
3.1. INTRODUCTION: ...................................................................................................... 25
3.2. DOMAIN MODEL ..................................................................................................... 26
3.3. ADMIN SEQUENCE DIAGRAM ................................................................................... 27
3.4. USER SEQUENCE DIAGRAM ..................................................................................... 28
3.5. COLLABORATION DIAGRAM .................................................................................... 29
3.6. DESIGN CLASS DIAGRAM ........................................................................................ 30
3.7. STATE CHART DIAGRAM .......................................................................................... 31
3.8. DATA MODEL.......................................................................................................... 33
CHAPTER 4: USER INTERFACE DESIGN .............................................................. 34
4.1. INTRODUCTION........................................................................................................ 34
4.2. SITE MAPS .............................................................................................................. 34
4.3. STORY BOARDS ....................................................................................................... 35

© Department of Computer Science and Engineering, ICFAI University Tripura

v
S1: MICROSOFT PRODUCTS ....................................................................................... 46
4.4. NAVIGATIONAL MAPS: ............................................................................................ 46
4.5 TRACE-ABILITY MATRIX .......................................................................................... 46
CHAPTER 5: SOFTWARE TESTING ........................................................................ 48
5.1 INTRODUCTION: ....................................................................................................... 48
5.2. TEST PLAN............................................................................................................... 48
5.2.1. Purpose ........................................................................................................... 48
5.2.2. Outline............................................................................................................. 48
5.3. TEST DESIGN SPECIFICATION ................................................................................... 52
5.3.1. Purpose ........................................................................................................... 52
5.3.2. Outline............................................................................................................. 52
5.4. TEST CASE SPECIFICATION...................................................................................... 55
5.4.1. Purpose ........................................................................................................... 55
5.4.2. Outline............................................................................................................ 55
5.5. TEST PROCEDURE SPECIFICATION ............................................................................ 61
5.5.1. Purpose ........................................................................................................... 61
5.5.2 Test Procedure Table ....................................................................................... 62
5.6. TEST INCIDENT REPORT ........................................................................................... 63
5.6.1. Purpose .......................................................................................................... 63
5.6.2. Incident Report Table ..................................................................................... 63
5.7. TEST LOG/TEST SUMMARY REPORT .......................................................................... 64
5.7.1. Purpose ........................................................................................................... 64
5.7.2. Test Log/Test Summary Report Table ............................................................. 64
SUMMARY REPORT: .................................................................................................. 67
REFERENCE…………………………………………………………………………..68

© Department of Computer Science and Engineering, ICFAI University Tripura

vi
Chapter 1: Project Feasibility Report

1.1. Introduction
Books are very essential for each and every one of us in order to increase our knowledge. An
online book store is a virtual store on the internet where customers can browse the catalog and
select books of interest. At checkout time, items in the e-library will be presented as an order. At
that time, more information will be needed to complete the request. Usually, the customer will be
asked to fill online form. An e-mail notification is sent to the customer as soon as the order is
placed.
This project intends different types of forms with many types of books like story, drama,
romance, history, adventures, etc. it can manage studying of books online, customers can choose
many types of books categories etc. Here, the user may select desired book and view its price.
The user may even search for specific books on the website. Once the user selects a book, he /
she then has to fill in a form and the book is provided for the user. A customer can login to his /
her account, can browse any book of his / her own interest, and can view prices and other details
of selected book, place his/her order and can select from payment options. User needs to register
on the site before checking out so that, he / she can login using same ID and Password next time.
User can select any payment option that he / she wish to, like Fast Cash, Credit / Debit card or
Cash on delivery.

1.2. Project/Product Feasibility Report

When a project is started the first matter to establish is to assess the feasibility of a project or
product. Feasibility means the extent to which appropriate data and information are readily
available or can be obtained with available resources such as staff, expertise, time, and
equipment. It is basically used as a measure of how practical or beneficial the development of a
software system will be to you (or organization). This activity recurs throughout the life cycle.
There are many types of feasibilities:

• Technical
• Operational
• Economic
• Schedule
• Specification
• Information
• Motivational
• Legal and Ethical

1.2.1. Technical Feasibility

Our Project is a complete web-based application. Web based applications are far more
compatible across platforms than traditional installed software’s. Web based systems need only

© Department of Computer Science and Engineering, ICFAI University Tripura

7
be installed on the server placing minimal requirements on the end user workstation. Due to the
manageability and cross platform support deploying web applications to the end user is far
easier. Typically, in larger more complex systems data is stored and moved around separate
systems and data sources. In web-based systems these systems and processes can often be
consolidated reducing the need to move data around.

The main technologies and tools that we are going to use are:
Php
HTML
Javascript
Bootstrap
CSS

Each of the technologies mentioned above are easily available. We have experience to use these
technologies so it would be manageable to implement the project within the given time. So, it is clear
that project Second hand Book Store is technically feasible.

1.2.2. Operational Feasibility

Second hand Book Store will be a GUI based web application so the user will be able to easily
understand the system and there will be no need of training. The system will help customer to check
the feature and price of products by himself and with the help of a “Digital Signage” we can
easily show data, reduce display cost and salesman, and also show photographs, videos and
product features.

1.2.3. Economic Feasibility

Second hand Book Store will be developed using open-source software like Microsoft Visual studio
and MySQL, so our project is economically feasible because the proposed system is very
affordable. So, there is no issue related to development tools.

1.2.4. Schedule Feasibility

Time is an important factor. To complete the project in time we have made Gantt chart for our
project task schedule which is mentioned in heading 1.7. According to our schedule plan our
project will be implemented till March and there will be one month for testing purpose. So, it is
clear that Second hand Book Store is feasible to complete before the deadline.

1.2.5. Specification Feasibility:

Our project boundaries are linked with customers, salesmen and owners. Requirements of our
project are definite and understandable, so we have acquired all the requirements for SHBS. We
used the observation technique for requirement gathering. Now we are clear about the
requirements for SHBS, so it is possible to complete this project.

© Department of Computer Science and Engineering, ICFAI University Tripura

8
1.2.6. Information Feasibility:
The feasibility of information must be assessed regarding its completion, reliability, and
meaningfulness. All the information regarding the project will be on hand and assessed
according to the planned activities. The output of each step will be tested according to the
expected result to ensure its reliability

1.2.7. Motivational Feasibility:

No great success can be achieved without motivation. Our team is highly motivated regarding
this project and has very good problem-solving skills. Our project prompts to assign the tasks to
every member of the group. Our mentor is skill full and motivated.

1.2.8. Legal & Ethical Feasibility

Our Project do not violate any legality or any human rights. We own to develop Second hand
Book Store both legally and ethically. Data of public will be confidential. So it is Legally &
Ethically feasible to complete this project.

1.3. Product Scope:

Second hand Book Store are interactive displays, where a customer can interact with the product
on screen. For displaying the ad Second hand Book Store use interactive digital touchscreen
displays in which you can view its design, Applications, Features, and Other related information.
The objective of this project is to display the electronic and other products digitally and to
reduce the display cost and all other cost etc. The user will no longer wait for the shopkeeper to
guide him about products and its features. Customers can easily explore the products, check its
features and prices by themselves. They can find all in one platform. They will get a secure
platform that they can trust and get help in case of emergency. Thus, this Second hand Book
Store will have a huge scope in the near future.

In smart system following operations will be performed:

• It will display pictures, features and price of products.

• The record of the products will be saved to remind the history of inventory.
• Show availability and unavailability of products.
• User will go through the display and see products by itself.

1.4. Tools and Technology with reasoning:

Technology and Languages
• Bootstrap
To design website layout and structure, HTML, CSS, and JavaScript these languages will
be used
• PHP
For back end coding php will be used

© Department of Computer Science and Engineering, ICFAI University Tripura

9
 • Java
For back end coding in android studio java will be used

Application Tools
• XAMPP:
For coding Php language Visual Studio will be used
• Android studio
For coding in java android studio is used.
• API
API is used to get response from server.
• Web Server
Web server is required for responding to the requests of clients
Database
• MySQL
MySQL will be used for Database Design and Development
Documentation
• Microsoft Visio
Microsoft Visio is used for Project Design and Diagrams
• Microsoft word:
Microsoft word is used for designing documentation

1.5. Vision Document:

The vision of our product is to develop new technology and introduce it to the industry so that
people can be benefited. Second hand Book Store is a centrally controlled, content distribution
platform by which user can easily check the feature and price of products by himself and owner
can maintain their inventory record. It can reduce the cost of store as there will be less need of
salesman. Not all people are confident enough to tell salesman what they need so it will be easy
for them to find what they need in an easy way. The vision of our product is:

1 To help and educate the customer about products feature and prices etc.
2 In case of absence of salesman, the user will explore the products by himself.

3 To reduce the display cost and other costs etc.

4 Owners can maintain their inventory records.

5 Through mobile app user can get information about available products.

© Department of Computer Science and Engineering, ICFAI University Tripura

10
1.12. Risk List:
Following are the risks found while developing this system:

• As system is heavy, so it is difficult to make it responsive.

• One time investment is needed to purchase digital screen.
• There could be many tools and technologies issue while development.
• Database connectivity and responding to queries asked to fetch data from database could
also be difficult.
• The end users may not have internet facility all the time.

1.13. Project Features:

• It will display pictures, features and price of products.

• The record of the products will be saved to remind the history of inventory.
• Show availability and unavailability of products.
• User will go through the display and see products by itself.
• Admin can make any change in the displayed content when needed
• When not in use admin can set advertisement ads or themes to attract customers.

© Department of Computer Science and Engineering, ICFAI University Tripura

11
Chapter 2: Software Requirement Specification (For Object
Oriented Approach)

2.1 Introduction:
Books are very essential for each and every one of us in order to increase our knowledge. An
online book store is a virtual store on the internet where customers can browse the catalog and
select books of interest. At checkout time, items in the e-library will be presented as an order. At
that time, more information will be needed to complete the request. Usually, the customer will be
asked to fill online form. An e-mail notification is sent to the customer as soon as the order is
placed.
This project intends different types of forms with many types of books like story, drama,
romance, history, adventures, etc. it can manage studying of books online, customers can choose
many types of books categories etc. Here, the user may select desired book and view its price.
The user may even search for specific books on the website. Once the user selects a book, he /
she then has to fill in a form and the book is provided for the user.
A customer can login to his / her account, can browse any book of his / her own interest, and can
view prices and other details of selected book, place his/her order and can select from payment
options. User needs to register on the site before checking out so that, he / she can login using
same ID and Password next time. User can select any payment option that he / she wish to, like
Fast Cash, Credit / Debit card or Cash on delivery.

2.1.1. System Specifications:

Before the digital revolution, huge budgets were required to display the products and also
required many salesmen. But with the help of a “SHBS” we can easily show data, reduce display
cost and salesman, and also show photographs, videos, and product features. A strategically
placed electronic display, conveying appropriate and informative content, can help your
customers to check the feature of products instead they wait in line to talk to your staff. This
project is designed to inform and educate the customer about products. Second hand Book Store
be the solution to connect with customers and increase sales. Your own small form touch display
could grab the customer’s attention and draw them deeper into the shopping experience.

Existing System
• Optisigns
• Rise Vision
• Raydiant
• Enplug

Scope of the System

Second hand Book Store happens to be a sub-segment of signage. Technologies, like LCD, LED,
and projection, are used in Second hand Book Store to display digital content such as images,
video, streaming media, and information. Digital billboards are used in public spaces,
transportation systems, museums, stadiums, retail stores, hotels, restaurants, and corporate

© Department of Computer Science and Engineering, ICFAI University Tripura

12
buildings, etc., for way finding, exhibitions, marketing, and outdoor advertising.

Second hand Book Store systems eliminate frequent compatibility and interoperability issues
between media players and displays. Furthermore, Second hand Book Store boards are being
extensively used as arrival and departure boards in airports known as Flight Information Display
Systems (FIDS).
Along with all these factors, enhancement of brand awareness and perception among the global
leaders is expected to drive the growth of the market.

2.1.3. Context level data flow diagram

Summary of Requirements (Initial Requirements)

The purposed system must fulfill following requirements as follow:

Login
Users will login to the system by giving user id, password. User of the system will have access to
change and modify password by itself.

Dashboard
Display signage will contain overall products information. It will contain information of brands
and their products, information about any sale on items, and time period of specific sale. Also the
price, product availability sign, its specifications will presented here.

Product Information
© Department of Computer Science and Engineering, ICFAI University Tripura
13
It will contain information of a specific product. For example, product id, Name, price, location
of product, features. All the products will be added by the admin.

Product Category
It will contain information of category of product for example it belongs to beverages, bakery,
dairy, cleaners, paper goods or any other category.

Brands
It will contain information about brands whose products are available in shop. It will contain list
of items of specific brands.

Availability/unavailability of products
Detail of the products either they are available at that time or not.

Identifying External Entities:

The Identification of External Interfaces is done in two phases.

Over Specify Entities from Abstract:

Based on the Abstract, we identify the following entities from the display signage.
• Admin
• User
• Login
• Items/products
• Advertisements
• Sales
• Brands

Perform Refinement:
After over specifying the entities, you must refine them on the basis of your Business Logic.
• Admin
• User
• Login
• Items/products
• Brands

2.1.4. Capture "shall" Statements:

Para # Initial Requirements

1.0 A user “shall” be able to register himself to system.
1.0 The system “shall” provide sign in to user.
1.0 The system “shall” provide sign out to user.
1.0 Customer “shall” be able to place and cancel online order
1.0 System “shall” be able to display cart Status to user.

© Department of Computer Science and Engineering, ICFAI University Tripura

14
1.0 Customer “shall” be able to buy products online by placing his order.
2.0 Customer “shall” be able to place order and see its status.
2.0 Administration “shall” be able to manage and update Products info.
2.0 Administration “shall” be able to create and update Products categories.
2.0 Customer “shall” be able to track products Location
3.0 Customer “shall” be able to cart items within shop.
3.0 Administration “shall” be able to manage inventory.

2.1.5. Allocate Requirements:

Para # Initial Requirements Use Case Name

1.0 A user “shall” be able to register himself to system. UC_Register
1.0 The system “shall” provide sign in to user. UC_Sign-In
1.0 The system “shall” provide sign out to user. UC_Sign-out
1.0 Customer “shall” be able to place and cancel online order UC_Online Order

1.0 System “shall” be able to display cart Status. UC_Cart-Status

1.0 Customer “shall” be able to buy products online by placing his UC_Online Store
order.
2.0 Customer “shall” be able to place order and see its status. UC_Order-Status
2.0 Administration “shall” be able to manage and update Products UC_Product-info
info.
2.0 Administration “shall” be able to create and update Products UC_Manage-Products-
categories. Category
3.0 Customer “shall” be able to track products Location UC_Track-Location
3.0 Customer “shall” be able to cart items within shop. UC_Cart-item
3.0 Administration “shall” be able to manage inventory. UC_Manage-Inventory.

2.1.6. Prioritize Requirements:

Rank Par Initial Requirements Use Case Name Use Case
a# No
Highest 1.0 A user “shall” be able to register himself UC_Register UC_1
to system.
Highest 1.0 The system “shall” provide sign in to user. UC_Sign-In UC_2
Highest 1.0 The system “shall” provide sign out to UC_Sign-out UC_3
user.
Highest 1.0 Customer “shall” be able to place and UC_Online Order UC_4
cancel online order
Highest 1.0 System “shall” be able to display cart UC_Cart-Status UC_5
Status to user.
Highest 1.0 Customer “shall” be able to buy products UC_Online Store UC_6
online by placing his order.
Medium 2.0 Customer “shall” be able to place order UC_Order-Status UC_7
and see its status.
Medium 2.0 Administration “shall” be able to manage UC_Product-info UC_8
and update Products info.

© Department of Computer Science and Engineering, ICFAI University Tripura

15
Medium 2.0 Administration “shall” be able to create UC_Manage-Products- UC_9
and update Products categories. Category
Lowest 2.0 Customer “shall” be able to track products UC_Track-Location UC_10
Location
Lowest 3.0 Customer “shall” be able to cart items UC_Cart-item UC_11
within shop.
Lowest 3.0 Administration “shall” be able to manage UC_Manage-Inventory. UC_12
inventory.

2.1.7. Requirements Traceability Matrix:

Build Rank Par Initial Requirements Use Case Use Category

a# Name Case No
B1 Highest 1.0 A user “shall” be able to register himself UC_Register UC_1 Bussiness
to system.
B1 Highest 1.0 The system “shall” provide sign in to UC_Sign-In UC_2 Bussiness
user.
B1 Highest 1.0 The system “shall” provide sign out to UC_Sign-out UC_3 Bussiness
user.
B1 Highest 1.0 Customer “shall” be able to place and UC_Online UC_4 Bussiness
cancel online order Order
B1 Highest 1.0 System “shall” be able to display cart UC_Cart- UC_5 Bussiness
Status to user. Status
B1 Highest 1.0 Customer “shall” be able to buy products UC_Online UC_6 Bussiness
online by placing his order. Store
B1 Mediu 2.0 Customer “shall” be able to place order UC_Order- UC_7 Bussiness
m and see its status. Status
B1 Mediu 2.0 Administration “shall” be able to manage UC_Product- UC_8 Bussiness
m and update Products info. Info
B1 Mediu 2.0 Administration “shall” be able to create UC_Manage- UC_9 Bussiness
m and update Products categories. Products-
Category
B1 Lowest 2.0 Customer “shall” be able to track UC_Track- UC_10 Bussiness
products Location Location
B1 Lowest 3.0 Customer “shall” be able to cart items UC_Cart-item UC_11 Bussiness
within shop.
B1 Lowest 3.0 Administration “shall” be able to manage UC_Manage- UC_12 Bussiness
inventory. Inventory.

© Department of Computer Science and Engineering, ICFAI University Tripura

16
2.2 Explanation
2.2.1 High Level Use Case Diagram:

2.2.3. Analysis Level Use Case Diagram:

© Department of Computer Science and Engineering, ICFAI University Tripura

17
2.2.4. Use Case Description

© Department of Computer Science and Engineering, ICFAI University Tripura

18
2.1.1. Use case Description
Table 1: Use Case- User Registration
ID: UC_1
Title: UC_ User Registration

Description: This module is specified for the users who are not registered to
the application, and want to access additional features and
functions. Here, at the time of registration, the user profile is
created
Primary Actor: User
Preconditions: User open website and click on signup page.
1. User enter his/her User Name, Gender, User Id,
Password, Confirm Password, Date of birth, Email,
Address, Contact No.
2. When the user inputs data into the fields and submits the
Main Success form fields like email_id, password and mobile number
Scenario: are validated.
3. client machine and an activation link is sent to user’s
mail account
4. And when user clicks on an activation link, his/her
account is created and data is stored in user’s table.
1. User already register
Alternative Flow:
2. User try wrong user name or password
Post-condition: 1. Appropriate message will be displayed on the user’s
screen.
2. User’s account is opened.

Table 2: Use Case- Sign In

ID: UC_2
Title: UC_ Sign-In
Description: User will sign in to system.
Primary Actor: User
User is already registered
Preconditions:

Main Success 1. User will enter the username and password.

Scenario: 2. System will verify the login
1. User login to his/her account
Alternative Flow: 2. User entered wrong user name or password
3. User cannot login on system.
Post-condition: Appropriate message will be displayed on the user’s screen.

© Department of Computer Science and Engineering, ICFAI University Tripura

19
Table 3: Use Case- Sign Out
ID: UC_3
Title: UC_ Sign-out
Description: User will sign out to system.
Primary Actor: User
User is already signed in
Preconditions:

Main Success 1. User will logout.

Scenario: 2. System will verify the logout
1. User logout to his/her account
Alternative Flow:
2. User shutdown system/website
Post-condition: 1. Appropriate message will be displayed on the user’s
screen.
2. User’s account closed

Table 4: Use Case-Online order

ID: UC_4
Title: UC_ online order
Description: The user will ordered products online which are available on our
Website.
Primary Actor: User
Preconditions: 1. User logged in on app.
3. Clicks products module.
4. Click on category.
5. Search for products
Main Success
6. Check the available products.
Scenario:
7. Enter the details about products
8. Give information about himself
9. Click submit
User cannot login on system.
Alternative Flow:
User internet is not working.
Post-condition: User will get verification message.

Table 5: Use Case-Cart Status

ID: UC_5
Title: UC_ Cart-Status

© Department of Computer Science and Engineering, ICFAI University Tripura

20
Description: The user will see items present in cart
Primary Actor: User
Preconditions: User added item in cart.
Main Success Use can check its items to place order.
Scenario:
Alternative Flow: User have no items in cart
Post-condition: User will get verification message for order.

Table 6: Use Case-online store

ID: UC_6
Title: UC_ online store
Description: The user will ordered products online which are available on our
Website.
Primary Actor: User
Preconditions: 2. User logged in on website/Mobile App.
10. Clicks products module.
11. Click on category.
12. Search for products
Main Success
13. Check the available products.
Scenario:
14. Enter the details about products
15. Give information about himself
16. Click submit
User cannot login on system.
Alternative Flow:
User internet is not working.
Post-condition: User will get verification message.

Table 7: Use Case-Order Status

ID: UC_7
Title: UC_ Order-Status
Description: The user will check its order progress
Primary Actor: User
Preconditions: User have placed order.
Main Success Order is placed and on its way to processed
Scenario:
1. Order cannot be placed
Alternative Flow:
2. Order cannot be accepted due to invalid information
Post-condition: User will get items ordered.

© Department of Computer Science and Engineering, ICFAI University Tripura

21
Table 8: Use Case Products Info
ID: UC_8
Title: UC – Product-Info
Description: When administrator performs an operation like products addition
the respective product are added in the database; hence, the
whole product can be added.
Primary Actor: Admin
Preconditions: Admin logged on website as admin.
1. Admin open product module.
Main Success
2. Click on update or add product option.
Scenario:
3. product will be added or updated
admin cannot login on admin account
Alternative Flow:
Admin internet not working
Post-condition: product delete or update successfully

Table 9: Use Case Products Category

ID: UC_9
Title: UC – Manage-Products-Category
Description: When administrator performs an operation like managing
product’s categories
Primary Actor: Admin
Preconditions: Admin logged on website as admin.
1. Admin open product module.
Main Success
2. Click on categories or add product option.
Scenario:
3. product will be added or updated in respective category
admin cannot login on admin account
Alternative Flow:
Admin internet not working
Post-condition: Categories and products delete or update successfully

Table 10: Use Case-Track products

ID: UC_10
Title: UC_ Track-Location
Description: The user “shall” get all types of products which are available on
our Website and can search and Track location for specific
products.
Primary Actor: User

© Department of Computer Science and Engineering, ICFAI University Tripura

22
 1. Visit the website
Preconditions:

1. Clicks products module.

Main Success
2. Search for products
Scenario:
3. Track products
Alternative Flow: User cannot have knowledge of how to use system
Post-condition: User will get the location of product

Table 11: Use Case-Cart Item

ID: UC_11
Title: UC_ Cart-Item
Description: The user will add items in cart
Primary Actor: User
Preconditions: User have logged in to system.
Main Success Use can add items to place order.
Scenario:
1. User have no items in cart
Alternative Flow:
2. Cart is not working
Post-condition: User can add item and place order.

Table 12: Use Case Products Inventory

ID: UC_12
Title: UC – Manage-Inventory
Description: Administrator performs an operation like managing inventory
system

© Department of Computer Science and Engineering, ICFAI University Tripura

23
Primary Actor: Admin
Preconditions: Admin logged on website as admin.
Main Success Admin can update inventory
Scenario:
admin cannot login on admin account
Alternative Flow:
Admin internet not working
Post-condition: Inventory updated successfully

Chapter 3: Design Document

3.1. Introduction

Third deliverable is all about the software design. So, we understand the current situation of the
problem domain. Now, we are ready to strive for a solution for the problem domain by using

© Department of Computer Science and Engineering, ICFAI University Tripura

24
object-oriented approach.

1. Domain Model
2. System Sequence Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. Design Class Diagram
6. State Transition Diagram
7. Data Model

3.2 Domain Model

© Department of Computer Science and Engineering, ICFAI University Tripura

25
 3.3Admin Sequence Diagram

© Department of Computer Science and Engineering, ICFAI University Tripura

26
© Department of Computer Science and Engineering, ICFAI University Tripura
27
 3.4 User Sequence Diagram

3.5. Collaboration Diagram

© Department of Computer Science and Engineering, ICFAI University Tripura

28
 3.6. Design Class Diagram

© Department of Computer Science and Engineering, ICFAI University Tripura

29
3.7. State Chart Diagram

• User

© Department of Computer Science and Engineering, ICFAI University Tripura

30
• Admin

© Department of Computer Science and Engineering, ICFAI University Tripura

31
3.8. Data Model
The data model is a subset of the implementation model, which describes the logical and
physical representation of persistent data in the system.
© Department of Computer Science and Engineering, ICFAI University Tripura
32
Chapter 4: User Interface Design

4.1. Introduction
A user interface design consists of three main parts:
Page elements should be visualized on paper before building them in the computer. Just as you
draw a site map to plan the site, use cartoons and storyboards to begin blocking out the site’s

© Department of Computer Science and Engineering, ICFAI University Tripura

33
appearance and navigational scheme. Following are the contents to be added in user interface
design:
1. Site maps
2. Storyboards
3. Navigational maps
4. Traceability Matrix

4.2. Site Maps

A site map's main benefit is to give users an overview of the site's areas in a single glance by
dedicating an entire page to a visualization of the information architecture. If designed well, this
overview can include several levels of hierarchy, and yet not be so big that users lose their ability
to grasp the map as a whole. A site map is a graphical representation of the site's content. It
doesn't usually have as much detailed information as the index has.
As web sites get more complicated, an index or site map is going to become more and more
valuable and essential to the navigation of a good site.
Second Hand Book Store Website:
SHBS Web
Homepage

Registration Login

Customer Terms and Search

Order
Registration Service Books

Make Add Books

Payment to wishlist

View Book
Details

© Department of Computer Science and Engineering, ICFAI University Tripura

34
Second hand Book Store Administration View:

SHBS Admin
Panel

Login

Manage Add
Products Products

Manage Add
Inventory Categories

Manage Manage
Users settings

4.3. Story boards

A storyboard is a sequence of single images, each of which represents a distinct event or
narrative. It is also a visual representation of the script illustrating the interaction between the
user and the machine. It can also be imagined as a film in visual-outline form.
A storyboard can be used in two ways. It describes the task, which are a series of images
showing the user, environment and the machine. It also describes the interface, which represent
series of screen images indicating the user’s representation and the computer’s response and
work out interaction details. It also shows interaction sequence at a glance and helps develop
usage scenarios to help develop tools & tasks. Following is the view of login to be used for
authentication of the product:

© Department of Computer Science and Engineering, ICFAI University Tripura

35
 S1: Login

S2: Username T1:

S3: Password T2:

B1: Submit

S1: static button 1

S2: static button 2
S3: static button 3
T1: text box 1
T2: text box 2
B1: button

© Department of Computer Science and Engineering, ICFAI University Tripura

36
Homepage:

© Department of Computer Science and Engineering, ICFAI University Tripura

37
© Department of Computer Science and Engineering, ICFAI University Tripura
38
© Department of Computer Science and Engineering, ICFAI University Tripura
39
© Department of Computer Science and Engineering, ICFAI University Tripura
40
© Department of Computer Science and Engineering, ICFAI University Tripura
41
© Department of Computer Science and Engineering, ICFAI University Tripura
42
© Department of Computer Science and Engineering, ICFAI University Tripura
43
© Department of Computer Science and Engineering, ICFAI University Tripura
44
© Department of Computer Science and Engineering, ICFAI University Tripura
45
4.4. Navigational maps:
The next step is of navigational maps. In these maps, the storyboards are used as an input. The
different display buttons or action buttons show the navigation from one screen to the other. In
other words when one action button is pressed, it would lead to other screens. This path and
navigation would be shown.

SHBS Website:
SHBS Web
Homepage

Registration Login

Customer Terms and Search

Order
Registration Service Books

Make Add Books

Payment to wishlist

View Book
Details

4.5 Trace-ability Matrix

Following columns are involved in traceability matrix:

Features:
List of system features is as follows:
• Information Collection
• Information Storage
• Information Management
• Accessibility

Use Case ID:

Use case ID’s for easy lookup are as follows:
• Information Collection : UC_1, UC_11
• Information Storage : UC_4, UC_12
• Information Management : UC_5, UC_7, UC_8, UC_9, UC_10, UC_13
• Accessibility : UC_2

© Department of Computer Science and Engineering, ICFAI University Tripura

46
User Interface ID:
Identified none

Priority:
• UC_1 : P1
• UC_11 : P1
• UC_4 : P1
• UC_12 : P2
• UC_5 : P2
• UC_7 : P2
• UC_8 : P2
• UC_9 : P2
• UC_10 : P1
• UC_13 : P3
• UC_2 : P2

Use Case Cross Ref:

• Information Collection: registration, keep-salary-record
• Information Storage: place order.
• Information Management: UC-Display-Order Status, UC-Record-Inventory, UC-Know-
service Status, UC-Update-Product Status, Generate profit/loss report,
• Accessibility: user sign in.

Database Table ID:

• Registration: RG-id
• Order: O-id
• Inventory: IR-id
• Service: P-id
• Report: RP-id
• Login: L-id

Elaborated Use Case ID:

• Registration: User should be registered before entering the system.
• Order: Customer is able to place online order.
• Inventory: Sale, Purchase and its report will be managed by admin.
• Service: service will be placed in stock through which customer can buy them.
• Login: user will provide detail like username, password etc.

Dependent Classes:
• Pay cash depend upon place order.
• Login depends upon registration.
• Logout depends upon login..
• Generate profit/loss report depends upon record inventory.

© Department of Computer Science and Engineering, ICFAI University Tripura

47
Chapter 5: Software Testing

5.1 Introduction
Software testing is intent of finding bugs by executing a program or application. It could be
described as the process of verifying and validating, that software meets the technical
requirements according to its design. This deliverable is based on the IEEE standard of software
testing i.e. IEEE SOFTWARE TEST DOCUMENTATION Std 829-1998. This standard
describes a set of basic test documents that are associated with the dynamic aspects of software
testing. Following are standard artifacts, which are included in this deliverable:
1. Test Plan
2. Test Design Specification
3. Test Case Specification
4. Test Procedure Specification
5. Test Log
6. Test Incident Report
7. Test Summary Report

5.2. Test plan

5.2.1. Purpose
To prescribe the scope, approach, resources, and schedule of the testing activities. To identify the
items being tested, the features to be tested, the testing tasks to be performed, the personnel
responsible for each task, and the risks associated with this plan.

5.2.2. Outline
A test plan shall have the following structure:

a. Test plan identifier

b. Introduction
c. Test items
d. Features to be tested
e. Features not to be tested
f. Approach
g. Item pass/fail criteria
h. Suspension criteria and resumption requirements
i. Test deliverables
j. Testing tasks
k. Environmental needs
l. Responsibilities
m. Staffing and training needs
n. Schedule
o. Risks and contingencies
p. Approvals

© Department of Computer Science and Engineering, ICFAI University Tripura

48
5.2.2.1 Test plan identifier

AKA_APF01

5.2.2.2 Introduction

The goal of this document is to develop a test plan for Second hand Book Store and defines all
procedures and activities required to prepare for testing of functions of the system which are
specified in Vision document. The objective of the test plan are to define the activities to perform
testing, define test deliverable documents and to identify the various risks and contingencies
involved in testing.

5.2.2.3 Test Items

Test items are functions that provide of the related test plan. What is to be tested include the list
of it. This can be defined from application as well as other sources of information or
documentation. The information given in it includes configuration requirements and version
numbers where it is needed. Test items in our project includes:
• 1.0 -Login : for registered users
• 1.0-Login : for unregistered users
• 1.0-Login : for invalid detail
• 1.0-Login : for empty field
• 1.0-Logout
• 1.0-Registration
• 1.0-Online order
• 2.0 Service request
• 2.0 Know user location
• 2.0 User manual
• 2.0-Generate profit/.loss report

Our project require windows based operating system and run on the Google, opera, internet
explorer, Mozilla Firefox or any other browser.

5.2.2.4 Features to be tested

The following list describes the features to be tested:
• Login/Log out.
• Registration.
• Online Order Booking.
• Service request
• Know user location
• User manual
• Generate Profit/Loss Report.

© Department of Computer Science and Engineering, ICFAI University Tripura

49
5.2.2.5 Features not to be tested
Features which are not to be tested in our project are as follows:
• Record inventory.
• Pay cash.
• Display order status.
• Know or update product status.
• Salary record.
• Browser compatibility.

5.2.2.6. Approach
Test cases of the system will be made. System testing will be performed by the testers.
Approaches used will be: Unit Testing Approach for Login, Parallel Testing Approach for
Registration and login as well as Function Testing Approach for User Interface, Sign up etc. Test
cases will be checked and executed using the software testing tool “JIRA”. Test cases will be
recorded in documentation.

5.2.2.7. Item pass/fail criteria

This is most important part of the test plan, where criteria is left over for to be judged either the
items or functionality is passed or not. The test process of our system will be completed as soon
as, it will be delivered, and processing will be started by the administrative users of the system,
say admin. Each item are tested fully and passed testing. System should satisfy all the function
and requirements defined and related to vision documentation.

5.2.2.8. Suspension criteria and resumption requirements

Testing will be stopped, if the number and type of defect will reach the point where
follow on testing will not be preferable. This will lead to the wastage of resources. Conditions
those let the page to be stopped, will be checked and acceptable level of defects, that will allow
testing to proceed, will also be checked.

5.2.2.9. Test deliverables

All recorded errors are expected to be passed by the second test. A “Test Plan Document”
and Several “Test Cases” will also be given. Test input data and test output data should be
identified as deliverables.

5.2.2.10 Testing Tasks

These are the tasks required to prepare for and perform testing. We will do testing of our project
using the following steps:
Tasks:
• System Test Plan
o Prepare
o Review
o Rework
o Baseline
• System Test Cases
o Prepare

© Department of Computer Science and Engineering, ICFAI University Tripura

50
 o Review
o Rework
o Baseline
• System Test
o Perform

5.2.2.11 Environmental Needs

No specific needs are required for testing to be get performed. 64-bit Windows operating system
and 8.00 GB RAM size will be used. Testing will be done using test cases and will be performed
in software testing tool known as JIRA and also documented in this deliverable with certain
conditions and pass/fail criteria.

5.2.2.12. Responsibilities
Group members are responsible for managing, designing, preparing, executing, checking, and
resolving. In addition, group that identified test items will also be responsible. These groups may
include the developers, testers, operations staff, user representatives, and administration staff.

Tasks Member 1 Member 2 Member 3

Write test cases × × ✓
Prepare test plan × ✓ ×
Execute test cases ✓ × ×

5.2.2.13 Staffing and training needs

Three members doing this project will perform testing on the underlying system that is
“Automation of Pak Fans” using software testing tool. Test cases will be written and their
execution will be performed that will reflect the functionality performed by the system, that
should be assured and right.

5.2.2.14 Schedule
Testing will be performed within 45 days before the software is ready to launch. Related
schedule for testing is defined in Gantt chart as one module to be completed within specified
time. In defined time, test cases will be written and execution will be performed according to test
plan to see for the compatibility between actual and expected result as well as the status and
priority of test cases.

5.2.2.15 Risks and contingencies

Our project “Multi fix" is a web based system that provide automation to underlying company
by leaving its manual work. It has no risks in the way of its development. But when the system is
deployed it can face some minor risks like system slow down. Software testing tool could also
have many problems while installation or after that.

5.2.2.16 Approvals

Identified none -
Identified none -

© Department of Computer Science and Engineering, ICFAI University Tripura

51
 Identified none -
Identified none -

5.3 Test Design Specification

5.3.1 Purpose
This part of document will specify the test condition for test items, the detailed test approach and
identifies the associative high level of related test cases. The main purpose of document is to
specify test suites and test cases, which are about to run and others to skip. It also let us know
about features that need to be tested and test cases that are executed to test those features.

5.3.2. Outline
A test plan shall have the following structure:

a. Test plan identifier;

b. Introduction;
c. Test items;
d. Features to be tested;
e. Features not to be tested;
f. Approach;
g. Item pass/fail criteria;
h. Suspension criteria and resumption requirements;
i. Test deliverables;
j. Testing tasks;
k. Environmental needs;
l. Responsibilities;
m. Staffing and training needs;
n. Schedule;
o. Risks and contingencies;
p. Approvals.

5.3.2.1 Test plan identifier

AKA_APF02

5.3.2.2 Introduction

The goal of this document is to develop a test design for Second hand Book Store and specify
the test condition for test items, the detailed test approach and identifies the associative high
level of related test cases.

5.3.2.3 Test Items

Test items are functions that provide of the related test plan. What is to be tested include the list
of it. This can be defined from application as well as other sources of information or
documentation. The information given in it includes configuration requirements and version
© Department of Computer Science and Engineering, ICFAI University Tripura
52
numbers where it is needed. Test items in our project includes:
• 1.0 -Login : for registered users
• 1.0-Login : for unregistered users
• 1.0-Login : for invalid detail
• 1.0-Login : for empty field
• 1.0-Logout
• 1.0-Registration
• 1.0-Online order
• 2.0-Generate profit/.loss report
3.0-Biometric attendance
Our project require windows based operating system and run on the Google, opera, internet
explorer, Mozilla Firefox or any other browser.

5.3.2.4 Features to be tested

The following list describes the features to be tested:
• Login/Log out.
• Registration.
• Online Order Booking.
• Biometric Attendance.
• Generate Profit/Loss Report.

5.3.2.5 Features not to be tested

Features which are not to be tested in our project are as follows:
• Record inventory.
• Pay cash.
• Display order status.
• Know or update product status.
• Salary record.
• Browser compatibility.

5.3.2.6. Approach
Test cases of the system will be made. System testing will be performed by the testers.
Approaches used will be: Unit Testing Approach for Login, Parallel Testing Approach for
Registration and login as well as Function Testing Approach for User Interface, Sign up etc. Test
cases will be checked and executed using the software testing tool “JIRA”. Test cases will be
recorded in documentation.

5.3.2.7. Item pass/fail criteria

This is most important part of the test plan, where criteria is left over for to be judged either the
items or functionality is passed or not. The test process of our system will be completed as soon
as, it will be delivered and processing will be started by the administrative users of the system,
say admin. Each items are tested fully and passed testing. System should satisfy all the function
and requirements defined and related to vision documentation.

© Department of Computer Science and Engineering, ICFAI University Tripura

53
5.3.2.8. Suspension criteria and resumption requirements
Testing will be stopped, if the number and type of defect will reach the point where
follow on testing will not be preferable. This will lead to the wastage of resources. Conditions
those let the page to be stopped, will be checked and acceptable level of defects, that will allow
testing to proceed, will also be checked.

5.3.2.9. Test deliverables

All recorded errors are expected to be passed by the second test. A “Test Plan Document”
and Several “Test Cases” will also be given. Test input data and test output data should be
identified as deliverables.

5.3.2.10 Testing Tasks

These are the tasks required to prepare for and perform testing. We will do testing of our project
using the following steps:
Tasks:
• System Test Plan
o Prepare
o Review
o Rework
o Baseline
• System Test Cases
o Prepare
o Review
o Rework
o Baseline
• System Test
o Perform

5.3.2.11 Environmental Needs

No specific needs are required for testing to be get performed. 64-bit Windows operating system
and 8.00 GB RAM size will be used. Testing will be done using test cases and will be performed
in software testing tool known as JIRA and also documented in this deliverable with certain
conditions and pass/fail criteria.

5.3.2.12. Responsibilities
Group members are responsible for managing, designing, preparing, executing, checking, and
resolving. In addition, group that identified test items will also be responsible. These groups may
include the developers, testers, operations staff, user representatives, and administration staff.

Tasks Member 1 Member 2 Member 3

Write test cases × × ✓
Prepare test plan × ✓ ×
Execute test cases ✓ × ×

5.3.2.13 Staffing and training needs

Three members doing this project will perform testing on the underlying system that is
© Department of Computer Science and Engineering, ICFAI University Tripura
54
“Automation of Pak Fans” using software testing tool. Test cases will be written and their
execution will be performed that will reflect the functionality performed by the system, that
should be assured and right.

5.3.2.14 Schedule
Testing will be performed within 45 days before the software is ready to launch. Related
schedule for testing is defined in Gantt chart as one module to be completed within specified
time. In defined time, test cases will be written and execution will be performed according to test
plan to see for the compatibility between actual and expected result as well as the status and
priority of test cases.

5.3.2.15 Risks and contingencies

Our project “Second hand Book Store ” is a web based system that provide automation to
underlying company by leaving its manual work. It has no risks in the way of its development.
But when the system is deployed it can face some minor risks like system slow down. Software
testing tool could also have many problems while installation or after that.

5.3.2.16 Approvals

Identified none -
Identified none -
Identified none -
Identified none -

5.4. Test Case Specification

5.4.1. Purpose
It specifies the purpose of a specific test, identifies the required inputs and expected results,
provides step-by-step procedures for executing the test, and outlines the pass/fail criteria for
determining acceptance.

5.4.2 Outline
A test case specification shall have the following structure:

a. Test case specification identifier

b. Test items
c. Input specifications
d. Output specifications
e. Environmental needs
f. Special procedural requirements
g. Inter case dependencies

© Department of Computer Science and Engineering, ICFAI University Tripura

55
5.4.2.1. Test Case Specification Identifier

AKA_APF03

5.4.2.2 Test items

Test items are functions that provide of the related test plan. What is to be tested include the list
of it. This can be defined from application as well as other sources of information or
documentation. The information given in it includes configuration requirements and version
numbers where it is needed. Test items in our project includes:
• 1.0 -Login : for registered users
• 1.0-Login : for unregistered users
• 1.0-Login : for invalid detail
• 1.0-Login : for empty field
• 1.0-Logout
• 1.0-Registration
• 1.0-Online order
• 2.0-Generate profit/.loss report

5.4.2.3. Environmental needs

5.4.2.3.1. Hardware
Notebook system will be used to perform the related testing. We will use 8.00 GB RAM size for
execution of these test cases.
5.4.2.3.2. Software
We will use 64-bit Windows operating system. Moreover, testing will be done using test cases
and will be performed in software testing tool known as JIRA and also documented in this
deliverable with certain conditions and pass/fail criteria.
5.4.2.3.3. Other
There is no need of unique facility or trained personnel to perform this testing. A software tool is
needed to perform all testing work and will be done by all three group members.

5.4.2.4. Special procedural requirements

We have no constraint when to perform testing related to our project.

5.4.2.5. Inter case dependencies

Following is the list of identifiers related to test cases that must be executed prior to this test case
and summary of the nature of the dependencies:
• Registration before login.
• Logout after login.
• Registered before online order placement.
• Login before mark attendance.

© Department of Computer Science and Engineering, ICFAI University Tripura

56
 Login: For Registered Users

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Condition Conditions Results Results Case
Name s Status
APF Login User should User must 1-Enter Home page User Home Pass
-01 be able to be valid is displayed successfull page is
login to the registered User- to the user. y logged display
system after and have name. in to the ed to
authenticatio an account 2-Enter account. the user
n. before. valid when
user logged
password in to
. the
3-Click account
on login .
button.

Login: For Un-Registered Users

ID Test Test Case Pre- Steps Post- Expecte Actual Test

Case Description Condition Condition d Results Case
Name s s Results Status
APF Login User should None 1-Enyer Error Un- Please Pass
-02 not be able invalid message is successf enter the
to log in to Username. displayed ul to valid
the account 2-Enter to the user. login to credenti
after invalid the als.
entering user account.
invalid password.
details. 3-Click on
Login
button.

© Department of Computer Science and Engineering, ICFAI University Tripura

57
 Login: When anyone of the details is invalid

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Condition Condition Results Results Case
Name s s Status
APF- Login User should None 1-User enters Error Un- Please Pass
03 not be able invalid name, message is successful enter the
to login to OR displayed to login to valid
the account 2-User enters to the user. the credentia
when invalid account. ls.
anyone of password.
the details is User clicks
not correct. on Login
button.

Login: When anyone of the fields is empty:

ID Test Test Case Pre- Steps Post- Expected Actual Test Case
Case Description Conditions Conditions Results Results Status
Name
APF- Login User should None 1-User Error Un- Please Pass
04 not be able enters message is Successful enter
to login to the name displayed. to login to the
the account or leaves the valid
when the field account. details
anyone of empty. in
the fields 2-User empty
left empty. enters fields.
the
password
or leaves
the field
empty.
3-User
clicks on
login
button.

© Department of Computer Science and Engineering, ICFAI University Tripura

58
 Logout:

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Conditions Conditions Results Results Case
Name Status
APF- Logout User should User must 1-User Login form Successfully Logged Pass
05 be able to login to the clicks is logged out Out
logout from account. on displayed from the
the account. logout on the account.
button. screen.

Registration:

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Condition Conditions Results Results Case
Name s Status
APF Regist User should None 1-User A report is Successful Registere Pass
-06 ration be able to enters generated registratio d
register name. confirming n. Successfu
him/herself. 2-User registration lly.
enters of the user.
address
.
3-User
enters
e-mail.
4-User
enters
passwo
rd.
5-User
clicks
on OK
button.

© Department of Computer Science and Engineering, ICFAI University Tripura

59
 Online Order:

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Conditio Conditions Results Results Case
Name ns Status
APF Onlin User should User 1-User A report is Order placed Order Pass
-07 e be able to must enters all generated Successfully. placed.
Order place order have an the confirming
online. account. necessary order
details placement
required and order
to place status is
order updated.
online.
2-User
clicks on
OK
button.

Know user location:

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Condition Condition Results Results Case
Name s s Status
APF- Know User should User must 1-User None Generatio View Pass
08 user be able to have a clicks n of location
location know complete on location .
professional record of know report and
location. location.. location show
.. location of
the user.

© Department of Computer Science and Engineering, ICFAI University Tripura

60
 Generate Profit/Loss Report:

ID Test Test Case Pre- Steps Post- Expected Actual Test

Case Description Conditio Condition Results Results Case
Name ns s Status
APF-09 Generate User should User 1-User None Generatio Profit/ Pass
Profit/Lo be able to must clicked n of loss
ss Report generate have all on profit/loss report
profit/loss the generate report generat
report. accounti profit/ showing ed.
ngs loss all the
before report. details of
about all profit and
of the loss within
items a defined
present time
in period.
inventor
y.

5.5. Test Procedure Specification

5.5.1 Purpose
A test procedure specification is a document that specifies a sequence of actions for the
execution of a test. The test procedures test the implementation of the requirement. Test
procedure specification development can begin after the test cases and design are completed and
approved. Moreover, test procedure is nothing but a test scenario of the related test cases.

5.5.1.1. Test procedure specification identifier

AKA_APF04

© Department of Computer Science and Engineering, ICFAI University Tripura

61
 5.5.2 Test Procedure Table

Test Requirement- No. of

Test Scenario
scenario Reference Importance Test
Description
ID document index Cases
Check if the P1
user is able to
enter the
Second hand
4
Book Store
system by a
Section 2.1.3 successful
APF-TS01 Para#1.0 login account.
Check if the P3
user is able to
1
Section 2.1.3 logout from
APF-TS02 Para#1.0 his account.
Check if the P1
user is able to
register
himself for 1
first time
Section 2.1.3 before being
APF-TS03 Para#1.o logged in
Check if the P1
user can place
online order
1
after being
Section 2.1.3 signed in from
APF-TS04 Para#1.0 his account.
Check if P1
administrator
is able to
1
generate
Section 2.1.3 profit/loss
APF-TS06 Para#2.0 report.
Section 2.1.3 View users P2
1
APF-TS07 Para#3.0 location

© Department of Computer Science and Engineering, ICFAI University Tripura

62
 5.6 Test Incident Report

5.6.1 Purpose
Test Incident Report is mainly generated during the software testing stage and it records all the
defects, bugs, and any other inconsistencies found by the testers while testing the software. This
report document issues found during testing that require actions. There will be one incident
report for each unique incident detected.

5.6.1.1 Test incident report identifier

AKA_APF05
5.6.2 Summary
Summarize the incident. Identify the test items involved indicating their version/revision level.
References to the appropriate test procedure specification, test case specification, and test log
should be supplied.

Defect Test
Defect Descript Severit Build Case Report Submit Fixed Fixed
ID ion Steps Priority y No ID Date By By DATE
1. Open
the
application
"URL"
After 2. Enter
login valid
into username
system, 3. Enter
next valid
page is password
not 4. Click on Group Group
APF- displaye Login APF- 15 May Member Mem 17 may
D01 d button P1 Highest B1 01 2021 s bers 2021
After 1-User
placeme enters all Grou
nt of the Group p 17-
APF- online necessary APF- 15 may Member Mem May-
D02 order, a details P1 Highest B1 07 2021 s bers 2021
© Department of Computer Science and Engineering, ICFAI University Tripura
63
 confirma required to
tion place order
message online.
is not 2-User
displaye clicks on
d to user OK button

5.6. Test Log/Test Summary Report

5.6.1. Purpose of Test Log

To provide a chronological record of relevant details about the execution of tests. Test log is
nothing but the addition of 2 fields namely 'Actual result' and 'Pass/Fail Criteria' to the test case
i.e., already populated with test case id, test description, test pre-requisites, test steps, expected
result.

Purpose of Test Summary Report

Test summary report is a document which contains summary of test activities and final test
results. After the testing cycle it is very important that you communicate the test results and
findings to the project stakeholders so that decisions can be made for the software release.

5.6.1.1 Test log identifier

AKA_APF06

5.6.2 Test Log/Test Summary Report Table

Test Scenario Title Actions Expected Actual Test Priority Category Types of
Case Result Result Data test
ID cases
APF-01 Login Check 1-Enter User Home User P1 Sanity Function
login for valid User- successful page is detail is al
register name. ly logged displayed required
ed users 2-Enter in to the to the
valid user account. user
password. when
3-Click on logged in
login to the
button. account.

© Department of Computer Science and Engineering, ICFAI University Tripura

64
APF-02 Login Check 1-Enyer Un- Please Invalid P1 Progressi Function
login for invalid successful enter the userna on al
unregist Username. to login to valid me and
ered 2-Enter the credential passwor
users invalid user account. s. d
password.
3-Click on
Login
button.
APF-03 Login Check 1-User Un- Please Valid P1 progressi Function
login enters successful enter the userna on al
when invalid to login to valid me and
anyone name, the credential invalid
of the OR account. s. passwor
details 2-User d OR
is invalid enters invalid
invalid userna
password. me and
User clicks valid
on Login passwor
button. d
APF-04 Login Check 1-User Un- Please User P1 progressi Function
login enters the Successful enter the enter on al
when name or to login to valid name
anyone leaves the the details in but no
of the field account. empty passwor
field is empty. fields. d OR
empty 2-User user
enters the enter
password passwor
or leaves d but no
the field name.
empty.
3-User
clicks on
login
button.
APF-05 Logout Check 1-User Successful Logged NA P3 progressi Function
when clicks on ly logged Out on al
the logout out from
account button the
is account.
logged
out

© Department of Computer Science and Engineering, ICFAI University Tripura

65
APF-06 Registrati Register 1-User Successful Registere User P1 Progressi Function
on user enters registrati d Detail is on al
through name. on. Successful required
account 2-User ly.
enters
address.
3-User
enters e-
mail.
4-User
enters
password.
5-User
clicks on
OK button
APF-07 Online Place 1-User Order Order User P1 Progressi Function
Order order enters all placed placed info is on al
after the Successful required
being necessary ly.
logged details
in required to
place order
online.
2-User
clicks on
OK button.
APF-9 Generate Generat 1-User Generatio Sale/purc NA P1 progressi Databas
Profit/Los e sale clicked on n of hase on es
s Report and generate profit/los report
purchas profit/loss s report generate
e report report. showing d.
all the
details of
profit and
loss
within a
defined
time
period.

© Department of Computer Science and Engineering, ICFAI University Tripura

66
APF-10 Mark Check if 1-User User Attendan Account P2 progressi Function
Biometric employe touches the successful ce detail is on al
Attendan e can biometric ly marked Marked required
ce mark device the
attenda through attendanc
nce the right e.
through thumb of
biometri his/her
c system hand.

• Summary Report
All modules of our project works successfully.

© Department of Computer Science and Engineering, ICFAI University Tripura

67
 • REFERENCES AND BIBLIOGRAPHY:
• Google for problem solving
• Database Programming with PHP and Java by O'Reilly
• https://www.tutorialspoint.com/php/
• https://docs.oracle.com/javase/tutorial/
• http://www.wampserver.com/en/
• http://www.tutorialspoint.com/mysql/
• httpd.apache.org/docs/2.0/misc/tutorials.html

© Department of Computer Science and Engineering, ICFAI University Tripura

68