IDP Project report on Grey Cloth Market Submitted By

IDP
Project report on
Grey Cloth Market

Submitted By:
Patel Alisha D. (140400116013)
Modh Krupa M. (140400116009)

Of
B.E SEM VII

Under The Guidance of:
Mr. Prem C Patel (Internal guide)
Mr.Darshan Patel(Externalguide)

Submitted to:
Department Of Information Technology
Sankalchand Patel College of Engineering, Visnagar
Sankalchand Patel College of Engineering, Visnagar
Gujarat Technological University, Ahmedabad
April – 2018

INDEX

No. Title Page
no.
1 Acknowledgement I
2 Certificate-College II
3 Certificate-PMMS Portal III
4 Certificate-PLAGARISM Software IV
5 Undertaking About Originality Of Work V

CHAPTER 1 Introduction
1.1 Project summary 1
1.2 Aim and Objective 1
1.3 Problem Specification 1
1.4 PSAR 2
1.5 Plan of Work 3
1.6 Tools and Technology Used 3
CHAPTER 2 Product Design Engineering
2.1 AEIOU Summary 5
2.2 Ideation 6
2.3 Product Development 7
2.4 Empathy Mapping 8
2.5 Study of Current System 9
2.6 Problem & Weakness of Current System 9
2.7 System Requirements 9
2.8 Feasibility Study 10
2.9 UML Diagrams 11
2.10 Data Dictionary 23
2.11 Features of new System 29
CHAPTER 3 Implementation
3.1 Snapshorts 30
3.2 Explanation 62
CHAPTER 4 Conclusion and Future Work
4.1 Summary of Result 63
4.2 Advantages 63
4.3 Existing product/Services or solution 63
4.4 Scope of Future Work 63
4.5 features of Project 63
4.6 Biblogryaphy 63
Appendix
Appendix A – PPR 64
Appendix B – PSAR 80
Appendix C – BMC 110
Appendix D – PDE 112

LIST OF TABLES

Table No Table Description Page No
1 Admin 23
2 User 24
3 Machine 24
4 Chart 25
5 Notification 25
6 Order 26
7 Payment 26
8 Rating 26
9 Product 27
10 Transport 28

LIST OF FIGURES

Figure No Figure Description Page No
3.5.1.1 Use case Diagram for Admin 11
3.5.1.2 Use case Diagram for Seller and buyer 12
3.5.1.3 ER Diagram 13
3.5.2 Class Diagram 14
3.5.3 Activity Diagram for Seller 15
3.5.4.1 Activity Diagram for Buyer 16
3.5.4.2 Sequence Diagram for Seller 17
3.5.4.3 Sequence Diagram for Buyer 18
3.5.5 Context level DFD 19
3.5.6.1 First Level DFDAdmin 20
3.5.6.2 First Level DFDSeller 21
3.5.6.3 First Level DFDBuyer 22
3.6 Data Dictionary 23

ACKNOWLEDGEMENT

We express our sincere gratitude towards internal guide Prof. Prem C. Patel and
external guide Mr. Darshan Patel for his constant help, encouragement,
suggestions and inspiration throughout the seminar work. Without his
invaluable advice, suggestions and assistance it would not have been possible
for us to complete this seminar work.

We wish to thank the Computer Engineering Department & Information
Technology Department of Sankalchand Patel College of Engineering, Visnagar
for their sympathetic co-operation. Our sincere thanks to all the authors whose
literature we have used as a reference of my work. We have very thankful to my
classmates, my Family & my Friends who supported throughout the seminar.
Thank You.
Name:
Patel Alisha D.
Enroll no :- 140400116013
Modh Krupa M.
Enroll no :- 140400116009

Sankalchand Patel College of Engineering, Visnagar

Information Technology
April – 2018
CERTIFICATE
Date: / /

This is to certiy that the project entitled “Grey Cloth Market” has been carried out by

Patel Alisha D.(140400116013) & Modh Krupa M.(140400116009) under my guidance in
fulfilment of the subject PROJECT-I (2181606) of Bachelor Of Engineering in Information
Technology (Semester VII) of Gujarat Technological University, Ahmedabad during the
academic year 2017-18.

Internal Guide

Name: Prof. Prem C. Patel
Date:

Signature:
Guide:

Signature:
HOD:

Seal of Institute

1
CHAPTER 1
1. INTRODUCTION
PROJECT SUMMARY
? “Grey cloth Market ” is actual Android base Application for direct dealing between seller and
buyer. Where seller can sell fabric to buyer. And buyer can directly buy products from seller.
Seller can view other seller’s price and quality of fabric ratings. Seller can add new product as
stock and as production. So buyer can easily get idea about if fabric(cloth) is in stock or in
production. Buyer can view all seller price for same machinery or different machinery. Also
buyer can view rating of seller and can give ratings to seller.
? “Grey cloth Market ” application is application where seller can sell their fabric produced by
different machinery. So the buyer can buy this fabric from this grey market. The application
will be simple and easy to use.

AIM AND OBJECTIVES
AIM
? The main aim of “grey cloth market “system is to help for big seller and big buyer . There
are lots of system where cloths are selling and so many E-commerce applications where user
can buy product from that platform but for those who are big buyer this Grey Market is exact
application to deal with seller. So Grey Market is actually design for fabric Merchants who
are dealing in big amount figures.

OBJECTIVE

? Main objective to design this application is direct dealing between seller and buyers. There
are lots of system in which customer are buying from seller only.
? Here there is main objective is quality of fabric(cloths) which is meaning full for buyer. So
buyer can get each and every detail about fabric

PROBLEM SPECIFICATIONS

? Existing applications have not any direct interaction between sellers and buyers.
? There is no any cloths(fabric) related application in the market.
? There is no direct selling facility in application for seller.
? There is not any simple accessible application for seller and buyer.
? In existing system time costing is high.

2

PSAR
1.4.1 PSAR of Student
1) PSAR1:

TITLE Enhanced input peripheral

The centerpiece of the invention is that an object or paper product so-scanned contains digital
information that can be quickly read and acted upon by an appropriately configured device,
computer or appliance. The preferred embodiment envisions that this digital information is
aesthetically hidden on objects. These objects have been previously and pro-actively marked
with the digital information, using any of the broad ranges of printing and processing techniques
which are available on the market and which are widely described in the open literature and
patent literature surrounding digital watermarking

2) PSAR2:

TITLE Integration of ecommerce Feature into social
Networking platform.

A method and system are provided for ecommerce marketplace users to provide contents for
social networking platform integration, such as a user sharing purchases with friends so that the
user may show new clothes to friends on a social networking service. Content can be transmitted
to a social network server for storing at a message space of a user of the social network server and
requesting the user of the social network to provide an opinion about the content. In addition, the
content might include an image resembling a paper doll, the paper doll having the capability of
having parts electronically superimposed with images of articles of clothing comprising all or part
of an outfit. Images of such articles of clothing can be electronically superimposed on the paper
doll. The paper doll with images of the articles of clothing can be transmitted to friends on a
social network for an opinion or for completion of the outfit.

3) PSAR3:

TITLE Linear crystalline terephthalate polyester yarn and
textile goods made there from.

It is the primary object of the present invention to provide a crystalline polyester multi-filamentary
yarn composed of a bundle of extra-fine filaments which bears ameliorated properties regarding a
heat-setting property, a raising or napping property, a dimensional stability and a twist resistance
which enables one to employ a higher twist coefficient in the false twist crimping.

3
4) PSAR4:
TITLE Dyed cellulose combination sheet, dyed nonwoven material, and processes for
their production

In a particular embodiment of the dyed cellulose market combination sheet, the moisture content is
from about 5 weight percent to about 10 weight percent, based on the total weight of the dyed
cellulose market combination sheet, wherein the dyed cellulose market combination sheet does not
bleed, and wherein the dyed cellulose market combination sheet has been produced by drying the
dyed cellulose combination sheet.

5) PSAR5:
TITLE Lining cloth and method for producing the same.

A mining cloth of a woven fabric in which the warp yarn comprises either of polyester filamentary
yarn or cellulosic filamentary yarn and the filling yarn comprises either a false-twisted polyester
filamentary yarn, a raw filamentary yarn or a cellulosic filamentary yarn, characterized in that an
elongation in the filling-wise direction of the woven fabric is in a range from 5% to 12%, a
coefficient of dynamic friction on the surface of the woven fabric is in a range from 0.20 to 0.45, and
a filling-wise crimp index value of the woven fabric as defined by the following formula (1) is in a
range from 0.003 to 0.013:

PLAN OF WORK

4
TOOLS AND TECHNOLOGY

?
? Technology
? Android
? Software:
? JDK 8.0
? SDK
? Android Studio 2.2.2
? Android Emulator.
? Hardware
? Ram: 2GB and Above.
? Android

5
CHAPTER 2
1. PRODUCT DESIGN ENGINEERING
AEIOU SUMMARY

Activities:

In block of activities we have included activities of users as direct dealing , view Machinery, view,
view price, view quality etc.
Environment:
We have included weather atmosphere as components. For e.g. summer, winter, rainy, etc. as these
seasons could affect product selling. As in summer season there will be demand of cotton clothes while
in winter season there will be demands of woollen clothes. In this way weather impact plays an
important role in our system.
Interactions:
In block of interaction we have included how system can interact with users. For e.g. communication,
fabric seller, fabric buyer etc.

Objects:

In block of objects we have included objects will be required by users as clothes, vegetables, wheat
etc.

Users:

In users block we have included who will mostly use our system. i.e. buyer, admin, seller etc.

6
IDEATION CANVAS

In ideation canvas we have many blocks as people, activities, situation/context/location and props
/tools/objects/equipment.

In people block we have included who will be users of our system. In activities block we have included
activities of users. In the block of context/situation/location we have included situations when our
system will be required at which location. And in props/tools/objects/equipment block we have
included objects or tools will be used by our system users.

7
PRODUCT DEVELOPMENT CANVAS

In product development canvas we have many blocks as purpose, people, product experience, product
functions, product features, components, customer revalidation and reject/redesign/retain.
In purpose block we have included the purpose of our system that is to provide information of recipes
of cuisines, advertisement for job and selling products and cleaning techniques to help users as an
assistant.
In people block we have included who will be users of our system. In product experience block
according to feedback we have included feelings will be experienced by users as relaxed, happy and
problem solver.
In products function block we have included functions of our products as providing information and
problem solver. In product features we have included easy to access, reliable and easy to maintain. In
components block we have included mobile phone, android app studio, laptop etc.

8
EMPATHY MAPPING CANVAS

In empathy mapping canvas we have included users, stake holders, activities, happy stories and sad
stories with respect to our system.

9

2. SYSTEM ANALYSIS AND DESIGN
STUDY OF CURRENT SYSTEM

• There is a direct selling facility in application for seller.
• There is simple accessible application for seller and buyer.
• This application is application where seller can sell their fabric produced by different
machinery.
• Here there main study is quality of fabric which is meaning full for buyer. So buyer can get
each and every details about fabric.
• This application is very used full for those fabric merchants who are dealing in big amount
figures.

PROBLEM AND WEAKNESS OF CURRENT SYSTEM

? There is different application for different modules.
? Selling products application sells product of branded and know companies.
? If an fabric comes damaged or not as described, they will want to return the item or be
refunded your money.
? Though some companies offer free flat rate shipping, it still may come at a cost.

SYSTEM REQUIREMENT

? This system will be used in three modules which are administrator, fabric seller, fabric
buyer. The uses of three modules have been described below.

1) Administrator can do the following function
? Admin can maintain whole system.
? They can update and delete and change status for buyer in system.
? They can add, update, delete page of navigation in system and also
change status of menu if inactive than menu cannot show to visitor and
other.

2) Seller can do the following function
? They can manage profile details.
? They can manage order.

10

? They can add product as stock and as production.
? They can get notification of order

3) Buyer can do the following function
? They can manage profile details.
? They can order as stock and as production .
? They can view product as stock and as production.
? They can get notification about of order

FEASIBILITY STUDY

“Feasibility study is a detailed investigation and analysis of proposed system to determine that the
system will be feasible technically, operationally and economically or not.”

The following three areas were taken into consideration while deciding the feasibility of the proposed
system.
? Technical Feasibility
? Economic Feasibility
? Operational Feasibility

Technical Feasibility

The tools used for development i.e android as front end and Sql lite as back end are easily
available and operable. The hardware required is also easily available.

Economic Feasibility

This system is Economical feasible in every sense that it takes less effort, less time and nominal
cost of purchasing the tools. Internet will be required. So that economically feasible.

Operational Feasibility

This application provides facility for users to view information of recipes, advertisement for job
and product selling and techniques for cleaning.

11
UML DIAGRAM

USECASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented
as use cases), and any dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor. Roles of the actors
in the system can be depicted.

Use Case Diagram for Admin

12
Use Case Diagram for Seller and Buyer

13
E-R Diagram

14

Class Diagram

Class Diagram is a type of static structure diagram that describes the structure of a system by
showing the system’s classes, their attributes, operations (or methods), and the relationships
among the classes. Class diagram describes the object and information structures used by
your application, both internally and in communication with its users.

15
Activity Diagram

An Activity Diagram is a graphical representation of the “flow” of data through an
information system, modeling its process aspects. Activity diagrams are graphical
representations of workflows of stepwise activities and actions with support for choice,
iteration and concurrency. In the Unified Modeling Language, activity diagrams can be used
to describe the business and operational step-by-step workflows of components in a system.
An activity diagram shows the overall flow of control.

Activity Diagram for Seller

16
Activity Diagram for Buyer

17
Sequence Diagram

? A sequence diagram in a Unifies Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart.
? A sequence diagram shows object interactions arranged in time sequence.
? It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of the
scenario. Sequence diagrams typically are associated with use case realizations in the
Logical View of the system under development.

Sequence Diagram for Seller

18
Sequence Diagram for Buyer

19
Data Flow Daigram (DFD)
Level 0 (context level) Diagram:-
Level 0 DFD for online cloth market System is the general DFD of the Online cloth market
System.

20
First level DFD forAdmin

21
First level DFD forSeller

22
First level DFD forBuyer

23

Data Dictionary
• The volume of data in most information system applications is substantial-more than a
single analyst can easily keep track of, when team of analysts work on a system, the task of
coordinating data definitions become more complex. An individual depends on the
definitions that others established and assumptions they make about data specifications. Yet,
unless they meet almost daily (in fact, they seldom do) it is virtually impossible to have
acceptable data coordination.
• Data dictionaries are an integral of structures analysis, since data flow diagrams by
themselves do not fully describe the subject of the investigation. The data dictionary provides
additional information about the system.
• Data dictionary is a catalog – a repository – of the elements in a system. As the name
suggests, these elements center on data and the way they are structured to meet the
requirements and organization needs. In data dictionary you will find a list of all the elements
composing the data flowing through a system. The major elements are data structures, data
flows and processes.
• The data dictionary stores details and description of these elements. If analyst wants
to know how many characters are in a data item, by what other names it referenced in the
system, or where it is used in the system then they should be able to find answer in properly
developed data dictionary.

Table 1: Administrator
Description: This table keeps information about admin of system

24

Table 2: User
Description: This table keeps information of user details

Table 3: Machine
Description: This tables keeps information about Machine

25

Table 4: My chart
Description: This table keeps information of my chart

Table 5 : Notification
Description: This table keeps information of Notification

26
Table 6: Order
Description: This table keeps details of order details

Table 7: Payment
Description: This table keeps information of payment details

Table 8: rating
Description: This table keeps information of rating details

27
Table 9: Product
Description: This table keeps information of product details

28

Table 10: Product
Description: This table keeps information of transport details

29
CHAPTER 3
3. IMPLEMENTATION
3.1 SNAPSHORT:-

Screen Short For Seller :-

First page:-

This is our Splash Screen

30
Login page :-

In our login page if seller can already sign up then phone no and pin no match and
seller can login.

31
Sign up page :-

In our sign up page seller insert all details then they can signup and phone no
is verified by Admin.

32
Profile page :-

Seller can view their details and also they can view their own productdetails and in this
page seller can add new product

33
Drawer page:-

This is seller Drawer page.

34
Select Product page:-

Seller can choose any product forr add product

35
Add Product page:-

Seller can Add product in stock or in production.

36
Add Product in Stock:-

Seller can Add all product details in stock.

37
Add Product in Production:-

Seller can Add all product details in production.

38
Product in Stock:-

Seller can view all seller product details in stock.

39
Product in Production:-

Seller can view all seller product details in production.

40
Notification:-

Seller get notification about order.

41
Seller View Order:-

Seller view their own order which is placed by different buyer and also view
each order status.

42
Seller View Order Approve:-

Seller can approve or decline order and insert remaining days .

43
Seller View Order complete:-

when buyer do payment then seller get payment receive status and seller can complete
order.

44
Seller View Order continue:-

45
Screen Short For Buyer :-

Login page:-

In our login page if buyer can already sign up then phone no and pin no match
and buyer can login.

46
Sign up page:-

In our sign up page buyer insert all details then they can signup and phone no
is verified by Admin.

47
Buyer Profile:-

Buyer can view their details and edit their details.

48
Drawer for Buyer:-

49
View product in stock:-

Buyer can view all seller’s product details in stock and they can search product.

50
View product in Production:-

Buyer can view all seller’s product details in production and they can search product.

51

Notification:-

Buyer get notification about order.

52

Place your order:-

Buyer can view all details about product and insert quantity and delivery pincode
then click okay button.

53

Place your order continue:-

Buyer can view all seller’s price and rating and then they click on buy button.

54
Order cart page:-

Product is add to cart.

55
Place your order continue:-

Buyer can view all details about order and then they can place order.

56
Order Place :-

57
Your order:-

Buyer can view their own order which was approve by seller.

58
Payment Detalils:-

Buyer can make payment or cancel order if buyer cancel order then order is rejected.

59
Payment option:-

Buyer can choose payment option ckeque or RTGS then they can click on confirm
order button.

60
Confirm order:-

Buyer order is confrim.

61
Wish list:-

Buyer can view order which is added to wish list.

62
3.2 Explanation:-

There are validation in registration page if user do not enter details
In correct format.

For Example if user leave the edit text as blank then there will be a pop up toast message
displayed .As instance ,if user do not enter name, then pop up message will be enter
name.

Similarly, for contact ,password and confirm password there will be pop up message as
enter contact no, enter your password and password is not match respectively.

63
CHAPTER 4
?
4. CONCLUSION AND FUTURE WORK

4.1 Summary Of Results:-

Grey Market is actual android base application for direct dealing between buyer and seller. Where
seller can sell fabric to buyer. And buyer can directly buy products from seller. Seller can view other
sellers’ price and quality of fabric with ratings. Seller can add new product as stock and as production.
So buyer can easily get idea about if fabric (Cloth) is in stock or in production.Buyer can view all
sellers price for same machinery or different machinery. Also buyer can view ratings of sellers and can
give ratings to seller. Project

4.2 Advantages:-

? Until now as we have so many applications for seller buyer direct dealing and only sell
fabric purpose.
? But we don’t have any only cloth related applications.
? There is simple accessible application for seller and buyer.
? Source Optimization.
4.3 Benchmarleting project with existing product/ services or solution:-
? Existing applications have not any direct interaction between sellers and buyers.
? There is no any cloths(fabric) related application in the market.
? . There is no direct selling facility in application for seller.
? There is not any simple accessible application for seller and buyer.
4.4 Scope of future work:-

In future we will update information and will add more modules if requires after having research and
analiysis.

4.5 Feature of project:-
? Time Saving
? It is user friendly
? Well Documented
? Easy Customization
? It is simple and Easy to use.
4.6 BIBLIOGRAPHY:-
? http://www.flipkart.com
? http://www.amazon.com

64
Appendix
Appendix A :- Periodic Progress Report (PPR)
7-SEM-PPR OF STUDENT:- 1
PPR 1 :-

65
PPR2 :-

66

PPR3 :-

67
PPR4 :-

68
PPR of Student 2 :-

PPR1:-

69
PPR2 :-

70

PPR3:-

71
PPR4 :-

72
8-SEM-PPR OF STUDENT:- 1
PPR 1:-

73
PPR:-2

74
PPR:-3

75
PPR:-4

76
PPR OF STUDENT:-2
PPR:-1

77
PPR:-2

78
PPR:-3

79
PPR:-4

80

Appendix B : PSAR
PSAR of Student 1 :-
PSAR1 :

81

82

83

PSAR2 :-

84

85

86

PSAR3 : –

87

88

89

PSAR4 :-

90

91

92

PSAR5 :-

93

94

95

PSAR of Student 2

PSAR1:-

96

97

98

PSAR2 :-

99

100

101

PSAR3 :-

102

103

104

PSAR4 :-

105

106

107

PSAR5 :-

108

109

110

Appendix C :- Business Model Canvas (BMC)

? Key Partners: In this students can do the partnership with different? companies according to
their product. By doing this students got the idea about what is market scenario,
optimization in product ; cost can be achieved, from where they got raw material of their
product.

? Key Activities: In this students got aware about how will they represent their product to
customers. They can use the media, radio, newspapers etc. for marketing of the product.

? Value Proposition: In this one can directly come in contact with customer requirement. In
this they will aware the customer about their product. How it is usable ; beneficial over the
conventional product and which kind of services they will provide to customers.

? Key Resources: In this section student got idea about, from which kind of industries, they
will purchase raw material for their product.

? Customer Relationship: in this section students got to know about how they will manage
the relationship with customer by giving them lucrative services.

111

? Customer Segment: Bifurcate the customer according to their product. To which kind of
customer they can sell their product.

Appendix D :- Patent Drafting Exercise (PDE)
FORM:-1

112

113
FORM:-2

114
FORM:-3