GCUF

Government College University Faisalabad

FINAL REPORT
Greener

Submitted By

Name Roll No Registration #

Bushra 3315(708115) 2017-GCUF-060793
Saba Ikram 3337 (708130) 2017-GCUF-060832

Department of Computer Science

Govt. Post Graduate College Samanabad Faisalabad

2021
 CERTIFICATE
It is certified that:
Bushra 3315(708115) 2017-GCUF-060793

Saba Ikram 3337 (708130) 2017-GCUF-060832

Have developed software project titled as: “Greener” at Government Post Graduate
College Samanabad Faisalabad as a partial fulfillment for the award of the degree of
BS-CS.

Supervisor:
Mrs. Somia Ali: Signature:-________________

Internal Panel:
Member 1:-_______________
Member 2:-_______________
Member 3:-_______________
Member 4:-_______________
Signature:-________________
Signature:-________________
Signature:-________________
Signature:-________________

Head of Department: Project Coordinator:

Signature:-_______________ Signature:-_______________

Principal:

Signature:-_______________

i
ii
 DECLERATION

The work reported in this project was carried by me under the supervision of
Project Supervisor, Mrs. Somia Ali, at Government Post Graduate College
Samanabad Faisalabad.

I hereby declare that this project and the contents of project are the product of my
own research and no part has been copied from any other written or published source
(accept the references, standard mathematical or genetics models / equation / formulas /
protocol etc.).

I further declare that this work has not been submitted for award of any other
degree / diploma.

The institution may take action if the provided information is found inaccurate at
any stage.

Name: Bushra Name: Saba Ikram

Reg. No. : 2017-GCUF-060793 Reg. No. : 2017-GCUF-060832

iii
 ACKNOWLEDGEMENTS

We would like to present our deepest and sincerest gratitude to ALLAH Almighty
that with HIS grace, we are able to complete our project. We also want to thanks our
parents because of their blessings and affections, we completed our project. We are truly
thankful to our advisor Mrs. Somia Ali whose valuable suggestions and guidance
brought us to the point of achievement. We thank him for providing all the necessary
help, support and resources on project.

We are thankful to Mrs. Somia Ali for conducting presentations and for ideas
regarding the project which helped us to complete this project in time as well. We are
thankful to the faculty and staff members of the Department of Computer Science,
Government Post Graduate College Samanabad Faisalabad, who have been directly as
well as indirectly in making this project successful

With Best Regards,

Bushra

Reg. No. : 2017-GCUF-060793

Saba Ikram

Reg. No. : 2017-GCUF-060832

iv
 ABSTRACT

This project is an Android based Online Plant system for an existing Nursery. The
project objective is to deliver the online Plant application into android platform.

This project is an attempt to provide the advantages of online Plant accessories to

customers of a real Nursery. It helps buying the products in the Nursery anywhere
through internet by using an android device. Thus the customer will get the service of
online Plant accessories and home delivery from his favorite Nursery.

Since the application is available in the Smartphone it is easily accessible and

always available. It is the platform that provides a suitable way of communication
between sellers and buyers. The seller introduces their production/verity of Plant, and the
buyer can order as well contact him for further information.

v
 Table of Contents

CHAPTER # 1 INTRODUCTION ….…………………………………………...1

1.1 Purpose of Project ...………………………………………………………………1

1.2 How it works? .........................................................................................................1
1.3 Project Scope ...…………………………………………………………………...1
1.4 Project Planning ...………………………………………………………………...1
1.4.1 Project Schedule …………………………………………………………..2
1.5 Project Modules …………………………………………………………………..2
1.5.1 Administrator …...………………………………………………………...2
1.5.2 User ……………………………………………………………………….3

CHAPTER # 2 BACKGROUND ………………………………………………...5

2.1 Background Research …………………………………………………………....5

2.2 Existing Technology ……………………………………………………………..5
2.3 Area of Study …………………………………………………………….............6
2.4 Reason of the Project ……………………………………………………….........6
2.5 Objective of the Project …………………………………………………….........6
2.6 Methodology ……………………………………………………………….........6

CHAPTER # 3 SYSTEM REQUIREMENT ANALYSIS …………….........8

3.1 System Functional Requirements ………………………………………………...8

3.2 System Non-Functional Requirements …………………………………………...9
3.2.1 Efficiency Requirement .………………………………………………….9
3.2.2 Reliability Requirement .…………………………………………………9
3.2.3 Usability Requirement …..………………………………………………..9
3.2.4 Implementation Requirement …………………………………………....10
3.2.5 Delivery Requirement …………………………………………………...10

vi
 3.3 Hardware & Software Requirements ……………………………………………10
3.3.1 Software Requirements ……………………………………………….…10
3.3.2 Hardware Requirements …………………………………………………10

CHAPTER # 4 SYSTEM DESIGN ………………………………………….…11

4.1 Use Case Fully Dressed ………………………………………………………....11

4.2 WBS Fully Dressed ……………………………………………………………...12
4.3 System Sequence Diagrams ……………………………………………………..13
4.3.1 Login Account …………………………………………………………..13
4.3.2 Make Orders ……………………………………………………………..14
4.3.3 Add to Cart ………………………………………………........................15
4.3.4 Create Post for Orders ………………………………………………….16
4.4 Class Diagram …………………………………………………………………...17
4.4.1 Admin Class ……………………………………………………………..17
4.4.2 User Class ……………………………………………………………….17
4.4.3 Cart Item Class …………………………………………………………..18
4.4.4 Order Class ………………………………………………………………18
4.4.5 Product Class ………………………………………………………..….19
4.4.6 Class Diagram Fully Dressed …………………………………………....20
4.5 ER Model …………………………………………………………………..……21
4.5.1 Admin ER ……………………………………….…….………………...21
4.5.2 User ER ………………………………………………………………….21
4.5.3 Product ER ……………………………………………………………....22
4.5.4 Cart Item ER …………………………………………………………….22
4.5.5 Order ER ………………………………………………………….……..22
4.5.6 ER Model Fully Dressed ………………………………………………...23
4.6 Data Flow Diagram ……………………………………………………………...24

vii
CHAPTER # 5 IMPLEMENTATION & TESTING ……………………....25

5.1 Testing Methods …………………………………………………………………25

5.1.1 Box Testing ……………………………………………………………...25
5.1.2 Software Testing Level ………………………………………………….28
5.2 Test Cases ……………………………………………………………….….......33

CHAPTER # 6 USER MANNUAL …………………………………………….39

6.1 Admin Side ……………………………………………………………………...39

6.1.1 Login Page ……………………………………………………………....39
6.1.2 Signup Page …………………………………………………………..…40
6.1.3 Dashboard …………………………………………………………….....41
6.1.4 Order ………………………………………………………………….....42
6.1.5 Upload Products ………………………………………………………....43
6.1.6 Products ………………………………………………………………….44
6.2 User Side ………………………………………………………………………...45
6.2.1 Category ………………………………………………………..………..45
6.2.2 Account ……………………………………………………………….....46
6.2.3 Login …………………………………………………………………….47
6.2.4 Create Account …………………………………………………………..48
6.2.5 Items …………………………………………………………………....49
6.2.6 Item Detail …………………………………………………………..…50
6.2.7 Cart ………………………………………………………………………51
6.2.8 Buy Now …………………………………………………………...……52
6.3 Icon ………………………………………………………………………….…..53

viii
 List of Tables

Table 1: Project Schedule ……………………………………………………………..2

Table 2: Functional Requirements ……………………………………………………7
Table 3: Use Case 1 ………………………………………………………………….10
Table 4: Use Case 2 ………………………………………………………………….10
Table 5: Use Case 3 ………………………………………………………………….11
Table 6: Use Case 4 ………………………………………………………………….11
Table 7: Use Case 5 ………………………………………………………………….12
Table 8: Use Case 6 ………………………………………………………………….12
Table 9: Use Case 7 ………………………………………………………………….13
Table 10: Use Case 8 ………………………………………………………………...13
Table 11: Use Case 9 ………………………………………………………………...14
Table 12: Use Case 10 ……………………………………………………………….15
Table 13: Test Case 1 ………………………………………………………………..39
Table 14: Test Case 2 ………………………………………………………………..39
Table 15: Test Case 3 ………………………………………………………………..40
Table 16: Test Case 4 ………………………………………………………………..40
Table 17: Test Case 5 ………………………………………………………………..40

ix
 List of Figures

Figure 1: User Module ………………………………………………………………..3

Figure 2: Agile Model ………………………………………………………………...5
Figure 3: Use case Diagram …………………………………………………………..9
Figure 4: WBS ……………………………………………………………………….15
Figure 5: Select Province Sequence Diagram ……………………………………….15
Figure 6: Search City Sequence Diagram …………………………………………...16
Figure 7: Nearby Places Sequence Diagram ………………………………………...16
Figure 8: Favourite Places Sequence Diagram ………………………………………17
Figure 9: Select City Sequence Diagram ……………………………………………17
Figure 10: Select Attraction Sequence Diagram …………………………………….18

x
 Chapter No. 1: INTRODUCTION

1.1Purpose of Project:

The purpose of this app is to connect seller and buyer and to promote nurseries
and to solve the problem for the people who have great interest in this field and to
continue this field as their profession.

1.2How it works?

As it is an E-Commerce app so the main intention of this app is to make it

convenient for the users to purchase plants and things related to gardening online.
This app is for those people who have no time to go out to shop or for the people who
like to do online shopping.

1.3Project Scope:

This App solves the issue for the people who love plants and don’t have facility or
nursery around them and they can buy from this app. By giving opportunity to the
people who want this field as a profession, so that, they can earn from it. This app
also provides home delivery to the customer.

1.4Project Planning:

After selecting this project, we have to plan on how to complete it. So, this project
Online Plant store application was an excellent task for us.

First of all, we consulted our instructor and took guidelines to start the project,
after that analyzed the project, saw how to manual system works, and took synopses
of each aspect of the project. We consulted with the User and took requirements and
started to plan to work on the project according to the given specifications. I also visit
to local industries to see how they work with regulars. After that, I divide the project
into phases.

1
Serial Start End Days Activity Name Work Date
1 18-March 7-April 21 Client side App in React 25%
Native
2 8-April 28-April 21 Admin Panel web in React JS 25%
3 29-April 20-May 22 Server Side and DB 27%
Development
4 21-May 25-May 5 Demi Data for Android App 7%
5 26-May 7-June 13 Documentation 16%
Total 82 100%
1.4.1 Project Schedule:

Table 1: Project Schedule

1.5Project Module:

The system after careful analysis has been identified to be presented with the
following modules and roles. The modules involved are:

1.5.1 Administrator:

The administrator is the super user of this application. Only admin have
access into this admin page. Admin may be the owner of the Nursery. The
administrator has all the information about all the users and about all products.

This module is divided into different sub-modules.

 Manage Products
 Manage Users
 Manage Orders

2
 Figure 1: Admin Module

1.5.2 Users
 Registration

A new user will have to register in the system by providing essential

details in order to view the products in the system. The admin must accept a new
user by unblocking him.

 Login

A user must login with his user name and password to the system after
Registration.

 View Products

User can view the list of products based on their names after successful
login. A detailed description of a particular product with product name, products
details, product image, and price can be viewed by users.

 Add to cart:

The user can add the desired product into his cart by clicking add to cart
option on the product. He can view his cart by clicking on the cart button. All
products added by cart can be viewed in the cart. User can remove an item from
the cart by clicking remove.

 Submit Cart:

After confirming the items in the cart the user can submit the cart by
providing a delivery address. On successful submitting the cart will become
empty.

3
 Chapter No. 2: Background

2.1Background Research:

The central concept of the application is to allow the customer to Nursery virtually
using the Internet and allow customers to buy the items of their desire from the Nursery.
The information pertaining to the products are Nursery on an RDBMS at the server side
(Nursery).

4
 The Server process the customers and the items are shipped to the address submitted
by them. The application was designed into two modules first is for the customers who
wish to buy the Products. Second is for the storekeepers who maintains and updates the
information pertaining to the articles and those of the customers. The application which is
deployed at the customer database, the details of the items are brought forward from the
database for the customer view based on the selection through the menu and the database
of all the products are updated at the end of each transaction. Data entry into the
application can be done through various screens designed for various levels of users.
Once the authorized personnel feed the relevant data into the system, several reports
could be generated as per the security.

2.2Existing Technology:

The current system for Plant is to visit the Nursery manually and from the available
product choose the item customer want and buying the item by payment of the price of
the item.

 It is less user-friendly.
 User must go to Nursery and select products.
 It is difficult to identify the required product.
 Description of the product limited.
 It is a time consuming process
 Not in reach of distant users.

2.3Area of Study:

The project aims to design an application for smart phones; it falls under the area of
computer science and programming. The Operating System is based on smartphone and
databases. This project will implement multiple field mobile application development,
database, networks, GPS and security to have better information and privacy.

2.4Reason of the Project:

5
 As online Plant accessories became a trend nowadays the regular Nursery are losing
their customers to online Plant. Customers have effortless Purchasing and selling
experience and saving time through purchasing plant accessories online. For competing
with those online Plants, if shops are providing an online portal where their customers
can shop through internet and get the products at their doors it will increase the number
of customers.

2.5Objectives of the Project:

This App solves the issue for the people who love plants and don’t have facility or
nursery around them and they can buy from this app. By giving opportunity to the people
who want this field as a profession, so that, they can earn from it. This app also provides
home delivery to the customer.

2.6Methodology:

In a waterfall model, each phase must be completed before the next phase can begin
and there is no overlapping in the phases. It illustrates the software development process
in a linear sequential flow. This means that any phase in the development process begins
only if the previous phase is complete. In this waterfall model, the phases do not overlap.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.

Some of the major advantages of the Waterfall Model are as follows

 Simple and easy to understand and use

 Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Well understood milestones.

6
  Easy to arrange tasks.
 Process and results are well documented.

Chapter No. 3: System Requirement Analysis

3.1System Functional Requirements:

Req No. Req Name Description Functional Req

01 Req User Login This feature used by the user to Username and password will
login into system. A user must be provided after user

7
 login with his user name and registration is confirmed.
password to the system after Password should be hidden
registration. If they are invalid, from others while typing it in
the user is not allowed to enter the field.
the system.
02 Req Register A new user will have to register System must be able to
New User in the system by providing verify and validate
essential details in order to view information.
the products in the system. The The system must encrypt the
admin must accept a new user password of the customer to
by unblocking him. provide security.

03 Req Purchasing The user can add the desired System must ensure that,
an Item product into his cart by clicking only a registered customer
add to cart option on the can purchase items.
product. He can view his cart by
clicking on the cart button. All
products added by cart can be
viewed in the cart. User can
remove an item from the cart by
clicking remove. After
confirming the items in the cart
the user can submit the cart by
providing a delivery address. On
successful submitting the cart
will become empty.
04 Req ADMIN: The administrator can add user, System must ensure that
Manage delete user, view user and block admin can add, delete and
User user. view user.
05 Req Manage The administrator can add System must ensure that
Products product, delete product and admin can add, edit and
view product. delete products.
06 Req Manage The administrator can view The system must identify the

8
 Orders orders and delete orders. login of the admin.
Admin account should be
secured so that only owner of
the Nursery can access that
account.
Table 2: Functional Requirements

3.2System Non-Functional Requirements:

3.2.1 Efficiency Requirement:

When an online Plant shopping cart android application implemented

customer can purchase product in an efficient manner.

3.2.2 Reliability Requirement:

The Nursery store should provide a reliable environment to both

customers and owner. All orders should be reaching at the admin without any
errors.

3.2.3 Usability Requirement:

The android application is designed for user friendly environment and ease of
use.

3.2.4 Implementation Requirement:

Implementation of the system using Reach native in front end with JS as

back end and it will be used for database connectivity. And the database part is
developed by MongoDB.

3.2.5 Delivery Requirement:

The whole system is expected to be delivered in four months of time with

a weekly evaluation by the project guide.

3.3Hardware and Software Requirements:

9
 3.3.1 Software Requirements:

Operating System : Windows

IDE : Visual Studio

Database : MongoDB, Cloudinary, Heroku

Client Side Framework : React Native

Server Side Framework : React, Expressjs

Library : Redux

Compiler : Nodejs

3.3.2 Hardware Requirements:

Hardware : Pentium

Processor : Intel CORE i5

RAM : 1 GB

Disk Space : 500 MB

Chapter No. 4: System Design

4.1Use Case Fully Dressed:

10
4.2WBS Fully Dressed:

11
WBS stands for Work Breakdown Structure. It is basically deliverable breakdown of
project into smaller components.

4.3System Sequence Diagrams:

12
4.3.1 Login Account:

4.3.2 Make Orders:

13
4.3.3 Add to Cart:

14
4.3.4 Create Post For Orders:

15
4.4Class Diagram:
16
4.4.1 Admin Class:

4.4.2 User Class:

4.4.3 Cart Item Class:

17
4.4.4 Order Class:

4.4.5 Product Class:

18
4.4.6 Class Diagram Fully Dressed:

19
4.5ER Model:
4.5.1 Admin ER

4.5.2 User ER

20
4.5.3 Product ER

4.5.4 Cart Item ER

21
4.5.5 Order ER

4.5.6 ER Model Fully Dressed

22
4.6Data Flow Diagram:
23
Chapter No. 5: Implementation & Testing

24
 5.1Testing Methods:

There is some testing method to examine our project. In this chapter, we briefly
describe those methods and levels of testing.

5.1.1 Box testing:

Box testing is a method of testing. There are three types of box testing use to
investigate system work white box testing, black box testing and grey box testing.

i. Black box testing:

Black box testing is a method of software testing that examines the
functionality of an application without peering into its internal structures or
workings. This is also called Behavioral testing. This method of test can be
applied virtually to every level of software testing: unit, integration, system and
acceptance. 
While testing we didn't take care of source code of the system, our
primary focus is testing system function and non-functional functionality,
 Mission or mistaken functions
 Inappropriate errors
 Flaws in data structures or exterior database access
 Behavior or performance errors
 Initialization and termination errors

ii. White Box Testing:

25
 This is also known as Glass box, Clear box and Open box testing. White-box
testing is a method of software testing that tests internal structures or workings of an
application, as opposed to its functionality. In white-box testing an internal
perspective of the system, as well as programming skills, are used to design test
cases.

White Box Testing method is applicable to the following levels.

 Unite testing (For Testing path within the unit)

 Integration testing (For testing paths between Path)
 System testing (Testing Subsystem)

iii. Grey Box Testing:

26
 Gray box testing a software testing method which is a combination of Black
Box Testing method and White Box Testing method

Gray Box Testing is a technique to test the software product or application

with partial knowledge of the internal workings of an application. In this process,
context-specific errors that are related to web systems are commonly identified. It
will increase the testing coverage by concentrating on all of the layers of any complex
system.

Gray Box Testing is a software testing method, which is a combination of

both White Box Testing and the Black Box Testing method.

5.1.2 Software Testing Level:

27
Software Testing Level are the different stages of the software development lifecycle
where testing is conducted. There are four levels of software testing:

i. Unit Testing
ii. Integration Testing
iii. System Testing
iv. Acceptance Testing

i. Unit Testing:

28
 A level of the software testing process where individual units of a software are
tested. The purpose is to validate that each unit of the software performs as designed.

A unit is the smallest testable part of any software. A unit is the smallest testable
part of any software. It usually has one or a few inputs and usually a single output. In
procedural programming, a unit may be an individual program, function, procedure, etc.
In object-oriented programming, the smallest unit is a method, which may belong to a
base/ super class, abstract class or derived/ child class. (Some treat a module of an
application as a unit.

This is to be discouraged as there will probably be many individual units within

that module.) Unit testing frameworks, drivers, stubs, and mock/ fake objects are used to
assist in unit testing.

Unit testing increases confidence in changing/ maintaining code. If good unit tests
are written and if they are run every time any code is changed, we will be able
to promptly catch any defects introduced due to the change. Also, if codes are
already made less interdependent to make unit testing possible, the unintended
impact of changes to any code is less.

It is performed by using the White Box Testing method. Unit testing is the

first level of software testing and is performed prior to Integration Testing.

ii. INTEGRATION TESTING 

29
 Is a level of software testing where individual units are combined and tested as a
group. The purpose of this level of testing is to expose faults in the interaction between
integrated units. Test drivers and test stubs are used to assist in Integration Testing.

Testing performed to expose defects in the interfaces and in the

interactions between integrated components or systems. See also component integration
testing, system integration testing.

Testing performed to expose defects in the interfaces and interaction between

integrated components. During the process of manufacturing a ballpoint pen, the cap, the
body, the tail and clip, the ink cartridge and the ballpoint are produced separately and unit
tested separately. When two or more units are ready, they are assembled and Integration
Testing is performed. For example, whether the cap fits into the body or not.

When talking in terms of testing large application using black box testing
technique, involves the combination of many modules which are tightly coupled with
each other.

The main function or goal of this testing is to test the interfaces between the
units/modules.

iii. SYSTEM TESTING:

30
 Is a level of software testing where complete and integrated software tested?

The purpose of this test is to evaluate the system’s compliance with the specified
requirements. Usually, the software is only one element of a larger computer-based
system. Ultimately, the software is interfaced with other software/hardware systems.
System Testing is actually a series of different tests whose sole purpose is to exercise the
full computer-based system.

The process of testing an integrated system to verify that it meets specified

requirements. That is a very basic description of what is involved in system testing. You
need to build detailed test cases and test suites that test each aspect of the application as
seen from the outside without looking at the actual source code. Usually, the Black Box
Testing method is used.

iv. Acceptance Testing:

31
  Is a level of software testing where a system is tested for acceptability? The
purpose of this test is to evaluate the system’s compliance with the business requirements
and assess whether it is acceptable for delivery.

Formal testing concerning user needs, requirements, and business processes

conducted to determine whether a system or not that satisfies the acceptance criteria and
to enable the user, customers or other authorized entity to determine whether or not
to accept the policy.

Acceptance testing, a testing technique performed to determine whether or not the

software system has met the requirement specifications. The main purpose of this test is
to evaluate the system's compliance with the business requirements and verify if it is has
met the required criteria for delivery to end users.

The acceptance test activities are carried out in phases. Firstly, the basic tests are
executed, and if the test results are satisfactory then the execution of more complex
scenarios are carried out.

The acceptance test cases are executed against the test data or using an acceptance
test script and then the results are compared with the expected ones.

5.2Test Cases:
32
Test Case ID: Test Engineer: Bushra
Objective: Verify that system initialize successfully
Product: Greener
Environment: Android Based Application
Pre-Requisite: Initialize Successfully
Methods:
Initialization successful

Comments: Passed

Test Case ID: Test 2 Test Engineer: Bushra

Objective: Verify that system run successfully

Product: Greener
Environment: Android Based Application
Pre-Requisite: Data insert Successfully
Methods:
Launch the mobile app
Data inserted successful

Comments: Passed

Test Case ID: Test 3 Test Engineer: Bushra

Objective: Verify that system Display

Product: Greener
Environment: Android Based Application
Pre-Requisite: Mobile App open Successfully

33
Methods:
Initialization successful

Comments: Passed

Test Case ID: Test 4 Test Engineer: Bushra

Objective: Verify that admin/user login successfully

Product: Greener
Environment: Android Based Application
Pre-Requisite: Login page displayed successfully
Methods:
Launch the Mobile app
Admin login successful

Comments: Passed

Test Case ID: Test 5 Test Engineer: Bushra

Objective: Verify that the Data is retrieved successfully

Product: Greener
Environment: Android Based Application
Pre-Requisite: Data Inserted Successfully
Methods:
Open App Page
Retrieve selected Data

34
Comments: Passed

Test Case ID: Test 6 Test Engineer: Bushra

Objective: Verify that all Data in definitions is updated successfully

Product: Greener
Environment: Android Based Application
Pre-Requisite: Data Retrieved Successfully
Methods:
Open App Page
Retrieve selected Data
Update /Modify Data

Comments: Passed

Test Case ID: Test 7 Test Engineer: Bushra

Objective: User add items (Products)

Product: Greener
Environment: Android Based Application
Pre-Requisite: Initialize Successfully
Methods:
Open Web Page.
Click on Add New item
Enter data or information
Comments: Passed

35
Test Case ID: Test 8 Test Engineer: Saba Ikram

Objective: Admin/User delete items (Products)

Product: Greener
Environment: Android Based Application
Pre-Requisite: Initialize Successfully
Methods:
Open App Page.
Select item and click on delete item button
Delete successfully

Comments: Passed

Test Case ID: Test 9 Test Engineer: Saba Ikram

Objective: Admin De-active or ban employ account

Product: Greener
Environment: Android Based Application
Pre-Requisite: Initialize Successfully
Methods:
Open App Page.
Select item and click on delete item button
Delete successfully
Comments: Passed

36
Test Case ID: Test 10 Test Engineer: Saba Ikram

Objective: Admin verify new user products successfully

Product: Greener
Environment: Android Based Application
Pre-Requisite: User add items
Methods:
Open App Page.
Check to verify New item.
Comments: Passed

Test Case ID: Test 11 Test Engineer: Saba Ikram

Objective: Add to Cart Product

Product: Greener
Environment: Android Based Application
Pre-Requisite: User add items to Cart
Methods:
Open App Page.
Log in the Android Based Application
Comments: Passed

37
Test Case ID: Test 12 Test Engineer: Saba Ikram

Objective: User make Purchase

Product: Greener
Environment: Android Based Application
Pre-Requisite: Add to Cart
Methods:
Add to cart
Order the products
Comments: Passed

Chapter No. 6: User Manual

6.1Admin Side:
6.1.1 Login Page:

38
6.1.2 Signup Page:

39
6.1.3 Dashboard:

40
6.1.4 Orders:

41
6.1.5 Upload Products:

42
6.1.6 Products:

43
6.2User Side:
6.2.1 Category:

44
6.2.2 Account:

45
6.2.3 Login:

46
6.2.4 Create Account:

47
6.2.5 Items:

48
6.2.6 Item Detail:

49
6.2.7 Cart:

50
6.2.8 Buy Now:

51
6.3Icon:

52
53