Essay:

Essay details:

  • Subject area(s): Marketing
  • Price: Free download
  • Published on: 14th September 2019
  • File format: Text
  • Number of pages: 2

Text preview of this essay:

This page is a preview - download the full version of this essay above.

APTER 2

DESIGN

2.1 Data Modeling

2.1.1 Data Dictionary

Table 2.1:Customer

FIELD_NAME DATATYPE SIZE NULL / NOT NULL PRIMARY KEY / FOREIGN KEY

ID INTEGER 20 NOT NULL PRIMARY KEY

NAME VARCHAR 50 NOT NULL

PHONE NO INTEGER 10 NOT NULL PRIMARY KEY

EMAIL_ID VARCHAR 30 NULL

Table 2.2:Admin

FIELD_NAM E DATATYPE SIZE NULL / NOT NULL PRIMARY KEY / FOREIGN KEY

ADMIN_NA ME VARCHAR 25 NOT NULL PRIMARY KEY

ID INTEGER 20 NOT NULL

SYSTEM_ID INTEGER 15 NOT NULL PRIMARY KEY

TABLE_NO INTEGER 20 NULL

ORDER TIME INTEGER 20 NOT NULL

DATE VARCHAR 10 NOT NULL

ORDER_DET AILS VARCHAR 50 NOT NULL

Table 2.3:System Details

FIELD_NAME DATATYPE SIZE NULL / NOT NULL PRIMARY KEY

/FOREIGN KEY

DATABASE_ID INTEGER 20 NOT NULL

CUSTOMER_NAME VARCHAR 20

TABLE_NO INTEGER 10

AVAILABLE _STOCK VARCHAR 50

UNAVAILABLE_STOCK VARCHAR 50

OFFERS VARCHAR 25

DISCOUNTS INTEGERS 20

Table 2.4 Billing Details

FIELD DATATYPE SIZE NULL /NOT NULL PRIMARY KEY / FOREIGN KEY

BILL_NO INTEGER 20 NOT NULL

CUSTOMER

_NAME VARCHAR 15 NOT NULL

BILL_AMO UNT INTEGER 5

BILL_DATE INTEGER 10

PAYMENT TYPE INTEGER 5

2.2 E - R Diagrams

Fig 2.1   E-R Diagram

2.3 Use Case Diagrams

Use Case 1 : Admin

Fig 2.2   Use Case 1 : Admin

Use Case 2 : Buyer

Fig 2.3   Use Case 2 : Buyer

Use Case 3 : Seller

Fig 2.4   Use Case 3 : Seller

Use Case 4 : Support System

Fig 2.5   Use Case 4 : Support System

Use Case 5 : System Use Case

Fig 2.6   Use case 5 : System use Cas

2.4 Sequence Diagrams

Sequence 1 : Communication

Communication

Fig 2.8   Sequence 1 : Communication

Sequence 2 : Feedback and Complain Mechanism

Feedback and Complain

Fig 2.9   Sequence 2 : Feedback and complain Mechanism

Sequence 3 : Order

ORDER

Fig 2.10  Sequence 3 : order

Sequence 4 : Registration

Registration

2.5 Activity Diagrams

Activity 1 : Change password

Invalid

Invalid

Fig 2.12   Activity 1 : Change password

Activity 2 : Communication

COMMUNICATION

Fig 2.13   Activity 2 : Communication

Activity 3 : Employee Information

Fig 2.14   Activity 3 : Employee information

Activity 4 : Login

LOGIN

Invalid

Fig 2.15   Activity 4 : Login

Activity 5 : Registration

Registration

Enter name

Enter address

invalid

Enter Contact detail

CANVAS SUMMARY

AEIOU Summary:

In this canvas activities are goal-directed sets of actions-paths towards things people want to accomplish like user can select category, do login, place order and query & messaging. In environment it includes entire area where activities take place like weather & cosmetic effects, societies, company, house, offices etc. In interaction these are between a person and someone or something else like email & message. In objects which tool we used will come like Visio, visual studio, sql server etc. In users they are the people whose behavior, performances and needs are being observed. Users can be buyer, seller, admin, support system.

Empathy Summary:

In this we will describe emotional aspects of users. In this we will understand user, list user activities, create stories about users etc. In this first of all we take input from AEIOU summary then we will mention scouted challenges based on this input. Then based on this challenges we will derived top five problems. Then at last we come to know exact problem and for solution we made our system as a solution.

Ideation Summary:

In this canvas we include people, their activities, in which situation they work and props & possible solution. Here people can be teachers, workers, Students, IT Professionals etc. Activities are like Registration, login, select category, place order, Query and messaging. Situation or location may be home, hotels, shops, offices, colleges/schools etc.

1Product Development Summary:

In this canvas we mentioned purpose of our project. People are same as mentioned ago. We include product experience and product functions like generation of invoices, provide communication mechanism, etc. we also mentioned product features. In our system which components we are going to use are also included. Customer revalidation can be done by login. For reject, redesign and retain we will give awareness message to the customers.

Business Model:

The Business Model Canvas is strategic management and lean start-up template for developing new or documenting existing business models. It is a visual chart with elements describing an organization or product’s value proposition, infrastructure, customers, and finances. It assists firms in aligning their activities by illustrating potential trade-offs. The Business Model Canvas can be printed out on a large surface so groups of people can jointly start sketching and discussing business model elements with post-it note notes or board markers.

IMPLEMENTATION

3.1 Screen-Shots:

Fig 3.1 Login Form-Empty data(Admin)

Fig 3.2 Login(Admin)

Fig 3.3 View Seller History(Admin)

Fig 3.4 View Buyer History(Admin)

Fig 3.5 View Employee(Admin)

Fig 3.6 Invalid Info in add employee form(Admin)

Fig 3.7 Add Employee Form(Admin)

Fig 3.8 Mobile Number validation(Admin-Add employee)

Fig 3.9 View Messages(Admin)

Fig 3.10 View Invoice(Admin)

Fig 3.11 Feedback from Buyer(Admin)

Fig 3.12 Add Category(Admin)

Fig 3.13 Category already exist(Admin)

Fig 3.14 Change Password error(Admin)

Fig 3.15 Forgot password-Password sent by email(Admin)

Fig 3.16 Login(Employee)

Fig 3.17 View buyer feedback(Employee)

Fig 3.18 View invoice(Employee)

Fig 3.19 View messages(Employee)

Fig 3.20 Change Password(Employee)

 

Fig 3.21 Registration form(Buyer)

Fig 3.22 Place order(Buyer)

Fig 3.23 View sellers(Buyer)

Fig 3.24 View rejected orders (Buyer)

Fig 3.25 Feedback form (Buyer)

Fig 3.26 Login (Seller)

Fig 3.27 View accepted orders(Seller)

Fig 3.28 View pending orders (Seller)

Fig 3.29 View buyer’s feedback(Seller)

Fig 3.30 Change password (Seller)

Fig 3.31 Feedback form (Seller)

PROBLEM DEFINITION OF SYSTEM

4.1   PROPOSED SYSTEM:

Find my elance will be a web-based application which will be used for following purpose

• Acquiring new Buyers and sellers.

• To find seller based on their work experience.

• Online order for services.

• Removing communication gap & expand servicing.

• Fast & efficient problem solving of any query through complain & feedback mechanism.

• To increase quality of services so that can ensures buyer’s and seller’s satisfaction.

• Reducing cost of marketing.

Thus this system provides safety as well as security to maintain clients.

4.1.1 Purpose:

Main purpose of our system is to remove communication gap & less time consumption.

4.1.2 Scope of System:

As a part of the preliminary study, the scope of the system has to be clearly outlined. This is useful for buyer to place order for service &they can save their time. Buyers can see work experience of seller and based on that they can place order for services. In this system every visitor is required to register their basic information, therefore details of visitor is available which is useful for Buyer & Seller both.

4.1.3 Features of Proposed System:

Computerized system helps customer to view services. Buyers can see category & based on seller experience they can place order. One of the features of the system lets the customer know up to which state their order has reached & when it will arrive. It will plays an essential role in ordering which will help in reducing waste of time & also marketing cost. In this web-based monitoring system admin will keep eye on whole working & processing system. It also provides features so that all Buyers & Sellers can communicate only through email they couldn’t contact personally which is beneficial for our website. In our system there is one community where workers who don’t know how to access internet they will give their contact number to this community head and this head will register that worker on our website. For this our community head will communicate with buyer.

4.2 EXISTING SYSTEM:

4.2.1 Facts of Existing System:

Existing system is based on manual work and all the processes are done manually, they use register to maintain records and all. Buyers have to go to shop or via someone’s contact they get details of workers, thus more time is consumed for this manual work. Sometimes buyer get workers sometimes not so buyers may have to face many difficulties.

4.2.2 Problem Faced By Existing System Are Described As Below:

As mentioned earlier in problem summary, every work done manually, therefore it is difficult to maintain. If any buyer wants worker, first they have to find details and then there is no surety if that worker will come or not. Also possible that fake workers come and any type of damage can done. Security issues also may arise.

4.2.3 Requirement of New System:

The existing system is facing many problems with existing system as mentioned in detailed description of problem. So there is a need for developing a new system for customers.

4.2.4   Requirements of New System Are:

• To remove communication gap and expands servicing.

• To maintain consistent service base.

• Fast and efficient problem solving of any query through complaint and feedback mechanism.

• Access to buyer history, seller history, order information, and previous order information at all touch points.

• To increase service quality as a result of enhanced system that ensures buyer & seller satisfaction.

• To generate organized and proficient analysis of system workflow.

• Acquiring new buyer and seller using Internet technologies.

• Reduced cost of marketing.

...(download the rest of the essay above)

About this essay:

This essay was submitted to us by a student in order to help you with your studies.

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, . Available from:< https://www.essaysauce.com/essays/marketing/2016-4-12-1460491725.php > [Accessed 18.10.19].