Essay: Provide a platform to small scale business – project

CHAPTER – 1
INTRODUCTION
INTRODUCTION Chapter-1
1.1 PROJECT SUMMARY
The main aim of this portal is to provide a platform to ‘small scale business’ to scale up and help them to manage their businesses in more organize and effective way and to provide wide range of authentic products offerings to customers across the globe from the Indian Gruh Udyog.
There are many small scale business in city. The word “Gruh Udyog” represent the Business of Homemade & Handmade Products, Indian Snacks, Farsan & Namkeen, Sweets (Mithai), Local Foodmakers, Local Shops, Cottage Industry, Handicraft Industry, Art & Craft Products, Artisans & Homemakers products and many more businesses.
These businesses are highly unorganized in India, but having large scope for stack holders to go online and promote their offerings across the globe.
1.2 PURPOSE
‘ Provide a platform to small scale business, so they can scale up their business.
‘ Provide wide range of authentic products offerings to customers across the globe from the Indian Gruh Udyog.
‘ The portal provide a way to this ‘unorganized’ small scale business, So they can manage in more organize and effective manner.
1.3 SCOPE
This project intends to provide a platform to ‘small scale business’ to scale up and help them to manage their businesses in more organize and effective way and to provide wide range of authentic products offerings to customers across the globe from the Indian Gruh Udyog.
1.4 OBJECTIVE
‘ By using portal, sellers can attract more customers for their offerings and attain highest level of customer’s confidence and trust.
‘ Aim of this portal is to provide Seller a platform to scale up and help them to manage their businesses in more organize and effective way and to provide wide range of authentic products offerings to customers across the globe from the Indian Gruh Udyog.
1.5 TECHNOLOGY & LITERATURE REVIEW
1.5.1 Technologies:
‘ J2EE (Servlet, JSP, JDBC), HTML, XML, Java Script, AJAX, MySQL.
‘ Server : Tomcat
‘ Backend server: MYSQL
‘ Editor: Netsbeans.
1.5.2 Literature review:
In this project we have used Java Technology (JSP & Servlet) due to the good features that it facilitates with. The other technology used is My SQL Server to maintain the records & data. The combination of both makes the project easy to design & also attractive for the users to use.
About JSP/ Servlet Framework:
The Java Server Pages technology enables you to generate dynamic web content, such as HTML, DHTML, XHTML, and XML files, to include in a Web application. JSP files are one way to implement server-side dynamic page content. JSP files allow a Web server, such as Apache Tomcat, to add content dynamically to your HTML pages before they are sent to a requesting browser.
When you deploy a JSP file to a Web server that provides a servlet engine, it is preprocessed into a servlet that runs on the Web server. This is in contrast with client-side JavaScript (within <SCRIPT> tags), which is run in a browser. A JSP page is ideal for tasks that are better suited to execution on the server, such as accessing databases or calling Enterprise Java beans.JSP technology enables rapid development of web-based applications that are server and platform-independent.
JSP Technology in the Java EE 5 Platform The focus of Java EE 5 has been ease of development by making use of Java language annotations that were introduced by J2SE 5.0. JSP 2.1 supports this goal by defining annotations for dependency injection on JSP tag handlers and context listeners.
A Servlet is a Java-based server-side web technology. Technically speaking, a Servlet is a Java class in Java EE that conforms to the Java Servlet API, a protocol by which a Java class may respond to requests. Servlet could in principle communicate over any client’server protocol, but they are most often used with the HTTP protocol. Therefore, the word “Servlet” is often used in the meaning of “HTTP Servlet”.
Fig ‘ 1 (a): JSP/Servlet Framework
The MySQL Database powers the most demanding Web, E-commerce and Online Transaction Processing (OLTP) applications. It is a fully integrated transaction-safe, ACID compliant database with full commit, rollback, crash recovery and row level locking capabilities. MySQL delivers the ease of use, scalability, and performance that has made MySQL the world’s most popular open source database. Some of the world’s most popular websites like Facebook, Google and eBay rely on MySQL for their business critical application.
MySQL is an RDBMS and ships with no GUI tools to administer MySQL databases or manage data contained within the databases. The official set of MySQL front-end tools, MySQL Workbench is actively developed by Oracle, and is freely available for use.
Technologies to be used:
‘ J2EE
J2EE is a platform-independent, Java-centric environment from Sun for developing, building and deploying Web-based enterprise applications online. The J2EE platform consists of a set of services, APIs, and protocols that provide the functionality for developing multitier, Web-based applications.
‘ HTML
Hypertext Markup Language (HTML) is the main markup language for displaying web pages and other information that can be displayed in a web browser.
‘ JavaScript
It is a programming language that is widely used to give sophisticated functionality to web pages. It is considered as client side scripting language.
‘ JQuery
It is a JavaScript framework
Tools to be used:
‘ Netsbeans
It is a multi-language software development environment comprising an integrated development environment (IDE). It can be used to develop applications in Java and, by means of various plug-ins.
‘ MySQL
It is the world’s most used open source relational database management system (RDBMS). It is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other ‘AMP’ stacks).
‘ Apache Tomcat
It is server tool which can be used to run jsp and java servlets.
‘ JDK
The Java Development Kit (JDK) is an Oracle Corporation product aimed at Java developers. Since the introduction of Java, it has been by far the most widely used Java Software Development Kit (SDK).
CHAPTER – 2
PROJECT MANAGEMENT
PROJECT MANAGEMENT Chapter-2
2.1 PROJECT PLANNING
2.1.1 Project Development Approach And Justification
‘ A project planning is a development strategy that is used to achieve a goal that satisfies the requirements abiding by the constraints. There are many types of software process models like linear sequential model, RAD model, incremental model, spiral model etc. By this process model we can easily make a good planning for the project.
‘ As we working on an online project and we have a time of 1 year, we are using the spiral- model so that necessary services can be added with time and necessary changes can be applied.
Figure-2(a) Spiral Model
2.1.2 Phase of Spiral Model:
After the initiation stage, the project is planned to an appropriate level of detail. The main purpose is to plan time, cost and resources adequately to estimate the work needed and to effectively manage risk during project execution. As with the Initiation process group, a failure to adequately plan greatly reduces the project’s chances of successfully accomplishing its goals. Project planning generally consists of
‘ Determining how to plan.
‘ Selecting the planning team.
‘ Estimating time and cost for activities.
‘ Developing the schedule.
‘ Developing the budget.
‘ Risk planning.
2.1.2 Project Plan
‘ Requirement Gathering and analysis: All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.
‘ System Design: The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.
‘ Implementation: With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.
‘ Integration and Testing: All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
‘ Deployment of system: Once the functional and non functional testing is done, the product is deployed in the customer environment or released into the market.
‘ Maintenance: There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.
Project Schedule Representation:
Figure-2(b) Project Schedule Chart
2.1.3 Group Dependency
The team members are responsible for all documentation to be developed and for all the work to be done. As we are two team member for this project development, partition of project work is equally done between both. For better development of a project, internal and external guide helped me.
2.1.4 Roles And Responsibilities
Table 2.2 Roles and Responsibilities
RESPRESPONSIBILITIES MEMBER
Analysis Manendrasingh Yadav & Ronak Yadav
Database Design Manendrasingh Yadav & Ronak Yadav
Page Design Manendrasingh Yadav & Ronak Yadav
Coding Ronak Yadav & Manendrasingh Yadav
Testing Ronak Yadav & Manendrasingh Yadav
Confirmation & Enhancement Manendrasingh Yadav & Ronak Yadav
2.2 RISK MANAGEMENT:
The Following is the Risk Management study report, which is under taken for the requirement traceability tools.
2.2.1 RISK IDENTIFICATION
Risk identification is the first stage of risk management. It is concerned with discovering possible risks to the project. Risk identification may be carried out as a team process using a brainstorming approach or may simply be based on experience. To help the process, a checklist of different types of risk may be used. There are at least six types of risk that can arise.
‘ Technology risks: Risks that derive from the software or hardware technologies that are used to develop the system.
‘ People risks: Risks those are associated with the people in the development team.
‘ Organizational risks: Risks that derive from the organizational environment where the software is being developed.
‘ Tools risks: Risks that derive from CASE tools and other support software used to develop the system.
‘ Requirements risks: Risks that derive from changes to the customer requirements and the process of managing the requirements change.
‘ Estimation risks: Risks that derive from the management estimates of the system characteristics and the resources required to build the system.
2.2.2 RISK ANALYSIS
During risk analysis process, we considered each identified risk and made a judgment about the probability and the seriousness of it. The risk estimates are not generally precise numeric assessments but based around a number of bands.
‘ The effects of the risk are assessed as catastrophic, serious, and tolerable or insignificant. We have tabulated the results of this analysis process using a table ordered according to the seriousness of the risk. Once the risks were analyzed and ranked, we assessed which were the most significant. Our judgment was dependent on a combination of the probability of the risk arising and the effects of that risk.
Risk Probability Effects
Organizational financial problems force reductions in the project budget. Low Catastrophic
Key staffs are ill at critical times in the project. Moderate Serious
Software components which should be reused contain defects which limit their functionality. Moderate Serious
Changes to requirements which require major design rework are proposed Moderate Serious
The organization is reconstructed so that different management are responsible for the project High Serious
The database cannot process as many transactions per second as expected Moderate Serious
The time required to develop the software is underestimated. High Serious
Customers fail to understand the impact of requirements changes. Moderate Tolerable
Required training of staff is not available Moderate Tolerable
The rate of defect repair is underestimated Moderate Tolerable
The size of the software is underestimated High Tolerable
Table: 3 RiskVulnerability
2.2.3 RISK PLANNING
The risk planning process considers each of the key risks that have been identified and identifies strategies to manage the risk. The different strategies fall into three categories:
‘ Avoidance strategies: Following these strategies means that the probability that the risk will arise will be reduced. Risk avoidance strategy is the strategy with defective components.
‘ Minimization strategies: Following these strategies means that the impact of the risk will be reduced. Example of risk minimization strategy is that for staff illness.
‘ Consistency plans: Following these strategies means that we were prepared for the worst and had a strategy in place to deal with it. An example of a contingency strategy is the strategy for organizational problems.
2.3 ESTIMATION:
2.3.1 EFFORT ESTIMATION AND COST ANALYSIS:
Once the basic size of the project has been determined, the estimate can be produced based on the specific attributes of the project in question. Examples of the attributes that can affect the outcome of the estimate include the following:
‘ The rate at which project requirements may change,
‘ The Experience of the development team with this kind of project,
‘ The process or methods used to develop the project ranging from Agile to linear sequential model.
Figure-2(C) Software-Estimating Principle
Figure shows Software-estimating principles.
‘ The specific activities that will be performed during development.
‘ The number of increments, iterations, or ‘sprints’ that will be used.
‘ The programming language or languages utilized.
‘ The presence or absence of reusable artefacts.
‘ The development tool suites used to develop the project.
‘ The environment or ergonomics of the office work space.
‘
CHAPTER – 3
SYSTEM REQUIREMENTS STUDY
SYTEM REQUIREMENTS STUDY Chapter-3
3.1 USER CHARACTERISTICS
3.1.1 Admin
‘ Administrators are the personnel of the portal whom will be granted the privileges to manage the stores and activities performed by the stores and customer.
‘ All the decisions will be taken by the administrators of the company.
3.1.2 Store-Owner
‘ Store-owner is the entity who do the actual business in the portal. There are multiple stores on the portal. Store-owner can put/remove their products on the portal for sell.
‘ Store-owner can organize schemas, packages ,offers on their product.
‘ They can do promotional activities with the customers of the portal.
3.1.3 Customer
‘ Customer is the consumers of the products.
‘ Customer can compare products of different stores.
‘ Customer can order for product.
‘ They can give feedback and rating to store and store product.
3.2 HARDWARE AND SOFTWARE REQUIREMENTS
3.2.1 Hardware Requirements
‘ Win 2000/ Win 2003/Win XP/Win 2007/Win 2008
‘ MySQL Server
‘ IE 6.0/ above
‘ Firefox1.0/ above
‘ Celeron or higher motherboard
‘ Dual Core or higher processor
‘ 512 MB or higher RAM
‘ 50 MB free space
‘ color monitor
3.2.2 Software Requirement
Table 3.2 – Software Requirement
‘ Front End : J2EE
‘ Back End : MySQL Server
‘ Technology : Java, Advance Java
‘ Programming Language : Java
‘ Designing Software : Netbeans
3.3 Constraints
‘ User and store-owner can login only with his assigned username and password.
‘ Need internet to access software.
‘ Admin can access all data in the system.
‘ User can only access those rights which are given by admin.
3.4 ASSUMPTIONS AND DEPENDENCIES
‘ Administrator is created prior in the system and Roles and tasks are predefined.
‘ Real world changes during use cause invalidation of assumptions embedding of assumptions in system during abstraction, reification, bounding intrinsic to E-type computing system development, evolution, usage Assumption management vital but neglected development, maintenance and evolution responsibility.
‘ Assumptions may be explicit or implicit, conscious or unconscious, by commission or omission, recorded or unrecorded, (initially) valid or invalid Essential to search and review, at intervals determined by system criticality, to ensure safe, reliable, efficient, controlled, that is satisfactory, computer usage.
‘ Assumptions are premises or beliefs that are taken for granted and are not expected to be proven. They are taken as a starting point because they are thought to be true or are generally accepted by a person, group, organization, or theory. Principles are basic truths, laws, or assumptions that are both derived from assumptions and provide a foundation upon which assumptions are based. Practices are habitual or customary actions or ways of doing something. Practices support or implement principles and naturally derive from assumptions that are held. Predetermined or ‘rule-of thumb’ practices result from the principles and assumptions that are accepted.
CHAPTER – 4
SYSTEM ANALYSIS
SYSTEM ANALYSIS Chapter-4
4.1 STUDY OF CURRENT SYSTEM
‘ Currently the small scale business running separately.
‘ They are taking the order manually.
‘ They need to take any market place to run the business and people purchase from their.
‘ In current system business runner maintain all the records manually.
‘ There are also several things that is not possible with excel for instance, traditional system does not remind follow-up time to store.
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM
‘ Small scale business running separately, They are not getting a global or big plate form to perform their business even though they are having better items in terms of quality and cost.
‘ In current system customer cannot compare the price quality and review of the items.
‘ Most of the current systems based on this domain are using excel based DMA (Data Management System) in which each and every record (data) being stored which is not report worthy data storage.
‘ System must provide solutions to the challenges faced by the organization in managing the information flows essential to the effective deployment of complex supply chain processes.
‘ Executives are constantly requested by operations, sales, planning, purchasing, and accounting groups for more accurate and timely information on inbound shipments. Today, identifying what’s in transit, where it is, when it will arrive, and how much it will cost, requires piecing together information from internal paperwork, carrier websites, and phone calls ‘ a time consuming, inefficient process. A comprehensive report might take hours or days to prepare.
‘ Most companies have developed carefully optimized plans and routing guides that specify how users and suppliers should ship material. However, they have little control over whether these guides are followed, even though they are paying the freight charges. They must rely on their suppliers and employees to execute on routing instructions and guidelines, without any means to enforce these optimized plans.
4.3 REQUIREMENTS OF NEW SYSTEM
4.3.1 Requirements of User
User can not compare the price of the system as well as the quality parameters of the system.
In current system end user need to physically go to store and purchase the product.
Product nutritious parameters does not have in depth information.
Product nutrition comparison not available in current system.
Admin
‘ Here admin could be considered as a registered user who is in charge of maintenance and other activities related to the system.
‘ Also, the admin has more regulatory rights in the system than the other users, sponsors and visitors.
‘ He is able to manage each and every data and process inside the system.
Users
‘ Needs to authenticate themselves before using the services provided by the system.
‘ Once the authentication phase completes they can have access to their respective services provided in the system.
Sponsors
‘ Needs to authenticate themselves before using the services provided by the system.
‘ Once the authentication phase completes they can have access to their respective services provided in the system.
‘ They must be able to request for advertisements.
4.3.2 Requirements of System
‘ Each process in the supply chain must be studied and analyzed. This has to result in the development of robust products and scalable solutions and resulting in substantial improvements in the operations.
‘ Our main aim must be the supply chain that has been translated into effective operational tools, with the use of cutting edge technologies. It must be committed to taking the fullest advantage of all innovations in application development, database management, mobile technologies and related areas to enhance the utility and efficacy of its offerings.
4.4 FEASIBILITY STUDY:
‘ Feasibility study is a test of a system proposal according to its workability, impact on the organization, ability to meet user needs and effective use of the available resources. The objective of feasibility study is not to solve the problem but to acquire a sense of its scope. Four key combinations are involved in the feasibility analysis.
4.4.1 ECONOMICAL FEASIBILITY:
‘ Economic analysis is the most frequently used method for evaluating the effectiveness of a client system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expecting from a client system and compare them with cost.
4.4.2 TECHNICAL FEASIBILITY:
‘ Technical feasibility centers on the existing computer system (hardware, software etc) and to what extent it can support the proposed addition. The benefits such as high accuracy, minimum response time and user friendliness of the proposed system over weights cost for designing and implementing the new system.
4.4.3 BEHAVIOURAL FEASIBILITY:
‘ People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have towards the development of a computerized system. It is common knowledge that computer installations have something to do with turnover transfers, retaining and changes in employee job status. Therefore, it is understandable that the introduction of a client system requires special effects to educate, sell and train the staff on new ways of conducting business.
4.4.4 OPERATIONAL FEASIBILITY:
‘ The system is operationally feasible; it is made so easy that operator will not encounter
‘ any problem during working, as it is very user-friendly.
‘ Operational feasibility checks the scope of the system. The system under consideration should have enough operational research. It is observed that the proposed system would provide a very interactive means to share information and have a far and wide range. The proposed system would make the information more interactive. Thus operation feasibility of the proposed system id found to be high.
4.5 Features of the System
This system is specially designed for the small scale business. So that store-owner can put his item for sell.
If customer want to purchase product directly from the store, we will provide google map, so that they can reach to the store easily.
We have provided the facility of comment (feedback) to the store. It will help other customers. And customers could know about the items of store.
We have also provided the functionality of order tracing, so that customer can know about the delivery of product.
4.6 DATA FLOW DIAGRAM
‘ A Data Flow Diagram (DFD) is a graphical representation of the ‘flow of data’ through an information system. DFDs can also be used for visualization of data processing (structured design).
‘ With a data-flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented.
‘ DFD is also a virtually designable diagram that technically or diagrammatically describes the inflow and outflow of data or information that is provided by the external entity.
Function / Process
File (Data Store)
Users
Data Flow Direction
4.6.1 Context Level Diagram:
Fig.4.6.1 Context-level Diagram
4.6.2 Level-1 Data Flow Diagram:
Fig.4.6.2 Level-1 DFD
4.6.3 Level-2 Data Flow Diagram:
Fig.4.6.3 Level-2 DFD for Customer
4.7 Use Case Diagrams:-
Fig. 4.7 Use Case Diagram
4.8 ACTIVITY DIAGRAM
Fig. 4.8 Figure of activity diagram
4.9 SEQUENCE DIAGRAM
4.9.1 Sequence Diagram For Admin And System Interaction
Fig. 4.9.1 Sequence Diagram of Admin and System Interaction
4.9.2 Sequence Diagram For User And System Interaction
Fig. 4.9.2 Sequence Diagram of Customer and System Interaction
4.9.3 Sequence Diagram For Store And System Interaction
Fig. 4.9..3 Sequence Diagram of Store and System Interaction
4.10 Class Diagram
Fig. 4.10 Class Diagram
CHAPTER – 5
SYSTEM DESIGN
SYSTEM DESIGN Chapter-5
5.1 DATABASE DESIGN:
Database files are the key source of information into the system. It is the process of designing database files, which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing and retrieving the required information. The organization of data in database aims to achieve three major objectives: –
1. Data integration.
2. Data integrity.
3. Data independence.
Software design site at the technical kernel of the software engineering process and is applied regardless of the software process that is used. After the software requirements have been analyzed and specified, software design is the first of the three technical activities. Designing, Coding and testing that are required to build and verify the software. Each activity transforms information in such a manner that ultimately results in validated computer software.
Design Goals
i. The following goals were kept in mind while designing the system:
ii. Make system user-friendly. This was necessary so that system could be used efficiently and system could act as catalyst in achieving objectives.
iii. Make system compatible i.e. it should fit in total integrated system. Future maintenance and enhancement must be less.
iv. Make the system compatible so that it could integrate other modules of system into itself
v. Make the system reliable, understandable and cost effective.
5.2 DATA DICTIONARY
Table 5.2 Data Dictionary
1. Table Name: User
Description : This table is used to store User Information.
Field_name Data type Size Constraints Description
User_id Int 5 Primary key Primary key
Name Varchar2 25 Not Null Name of User
Address Varchar2 50 Not Null Address of User
ContactNumber Int 10 Not Null Contact no of User
Email_id Varchar2 25 Not Null Email_id of User
Password Varchar2 12 Not Null Password of User
Confirm_Password Varchar2 12 Not Null Confirm Password of User
User Type_id Int 5 Foreign key Foreign key
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
2. Table Name: UserType
Description : This table is used to store User-Type information.
Field_name Data type Size Constraints Description
User- Type_id Int 5 Primary key Primary key
UserType Varchar2 25 Not Null Type of User
3. Table Name: UserRights
Description : This table is used to store ‘User rights’ Information.
Field_name Data type Size Constraints Description
UserRights_id Int 5 Primary key Primary key
User_id Int 5 Foreign key Foreign key
Menu_id Int 5 Foreign key Foreign key
4.Table Name: Menu
Description : This table is used to store Menu Information.
Field_name Data type Size Constraints Description
Menu_id Int 5 Primary key Primary key
MenuName Varchar2 25 Not Null Name of Menu
Priority Int 5 Not Null Priority in Menu
Usertype Varchar2 25 Not Null Type of User
MainMenu Int 5 Foreign key Foreign key
5.Table Name: Product
Description : This table is used to store Product Information.
Field_name Data type Size Constraints Discription
Product_id Int 5 Primary key Primary key
ProductName Varchar2 25 Not Null Name of Product
ProductDesc Varchar2 25 Not Null Description of Product
Productsub_category Varchar2 10 Not Null Sub_category of Product
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
6.Table Name: ProductCategory
Description : This table is used to store Hospital Information.
Field_name Data type Size Constraints Description
ProductCategory_id Int 5 Primary key Primary key
ProductCategory-name Varchar2 25 Not Null Name of product category
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
7.Table Name: Sub-category
Description : This table is used to store sub-category Information.
Field_name Data type Size Constraints Description
Sub-catetory_id Int 5 Primary key Primary key
Name Varchar2 25 Not Null Name of sub-category
Category_id Int 5 Foreign key Foreign key
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
8.Table Name: : Store
Description : This table is used to store Store’s Information.
Field_name Data type Size Constraints Description
Store_id Int 5 Primary key Primary key
User_id Int 5 Foreign key Foreign key
Category_id Int 5 Foreign key Foreign key
Desc Varchar2 20 Not Null Description of Store
ApprovalStatus Varchar2 8 Not Null Status of Store approval
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
Rating Int 2 Not Null Rating to Store
Like Int 5 Not Null Likes to Store
Dislike Int 5 Not Null Dislike to Store
9.Table Name : StoreProduct
Description : This table is used to store Store-product Information.
Field_name Data type Size Constraints Description
StoreProduct_id Int 5 Primary key Primary key
Product_id Int 5 Foreign key Foreign key
Description Varchar2 20 Not Null Description to Store-product
Cost Int 5 Not Null Cost of Store-product
Unit Int 5 Not Null Unit of Product
Like Int 5 Not Null Like to StoreProduct
Rating Int 2 Not Null Rating to Store-product
Dislike Int 5 Not Null Dislike to StoreProduct
10.Table Name : Order
Description : This table is used to store Order Information.
Field_name Data type Size Constraints Description
Order_id Int 5 Primary key Primary key
OrderUser Int 5 Foreign key Foreign key
Store_id Int 5 Foreign key Foreign key
StoreProduct_id Int 5 Foreign key Foreign key
Quantity Int 5 Not Null Quantity of order
Unit Int 5 Not Null Unit Order
Date Datetime Not Null Date
Status Varchar2 10 Not Null Stautus of Order
Flag Int 1 Not Null Flag 0 data offline & if flag 1 data online
11.Table Name : Order-delivery
Description : This table is used to store Order-delivery Information.
Field_name Data type Size Constraints Description
OrderDelivery_id Int 5 Primary key Primary key
OrderNumber Int 5 Not Null Number of order
DeliverBy Varchar2 20 Not Null Name by which delivery done
12.Table Name : Feedback
Description : This table is used to store feedback Information.
Field_name Data type Size Constraints Description
f_id Int 5 Primary key Primary key
User_id Int 5 Foreign key Foreign key
StoreProduct_id Int 5 Foreign key Foreign key
Comment Varchar2 100 Not Null Content
Date Datetime Not Null Date
13.Table Name : Unit master
Description : This table is used to store Unit-master Information.
Field_name Data type Size Constraints Description
Unit_id Int 5 Primary key Primary key
Unit name Varchar2 10 Not Null Name of Unit
5.3 SYSTEM PROCEDURAL DESIGN:
1 Log In
Use Variables: UserName, Password, UserType of Type String
Display: Login Screen
Do Case Of Log In
Case UserType = ‘User’
Display User Dash Board
Case UserType = ‘StoreOwner’
Display Store Dash Board
Case UserType =’Admin’
Display User Dash Board
End Case
5.4 FLOW CHART:
5.4 STATE TRANSITION DIAGRAM
CHAPTER – 6
IMPLEMENTATION PLANNING AND DETAILS
IMPLEMENTATION PLANNING AND DETAILS CHAPTER – 6
6.1 IMPLEMENTATION ENVIRONMENT:
‘ As the website is web portal but this website use for particular users who those given permissions so this website not for use public uses. User can do information entry whenever required and uses different utilities and for that, a better web application is needed.
‘ We use different environments for different purpose.
‘ Coding:
We used Netsbeans software for our coding purpose.
‘ Design:
We used AJAX, HTML, JAVASCRIPT, and CSS.
‘ Database:
We use MySQL .Totally Object-Oriented development.
6.2 PROGRAMS/MODULE SPECIFICATION:
‘ The Website is designed into following modules.
6.2.1 Admin:
‘ This module is the administrator of the system. Admin handle all the users details and sellers detail. They have the total information about all users that are using this web application.
‘ Create/update/delete user account,
‘ Delete inquiry(out of territory inquiry)
‘ Admin can view any user or sellers profile.
‘ Create new user login
‘ Admin can transfer the order from one seller to another. .
6.2.2 User:
‘ In this module user can request for grant and make account to access the webportal..
‘ User can check the status of the order and the grant.
‘ User is also upload required documents related to his/her grant for the making of account.
6.2.3 Seller:
‘ In this module Seller check its task and do work according to its task, like seller can view his profile
‘ seller can upload tne new products in to his/her account and can make changes in existing products.
‘ seller can also be able to make change in his/her profile,password and can also read the feedbacks n comments of the user towards his//her product.
‘ Seller can also view the products n offers of its competitors.
6.3 SECURITY FEATURES:
‘ We are providing strong security features related to our website. We are allowing user to access his/her account using User name and password. So we give password protection system to all user of our application. Without correct user name and password they cannot go ahead. We provide forget password module in which password will send directly to his/her e-mail account.
‘ Whenever the web server software handles an incoming request it associates that request with a particular security context. This security context information is used by the operating system to determine what actions are permissible by the request.
‘ Hence, our website is very strong in security features. Any one cannot easily steal data from our database.
6.4 CODING STANDARDS:
Fig.6 (a) packers and movers Login page
6.5 SAMPLE CODING:
import java.sql.ResultSet;
import java.io.IOException;
import java.io.PrintWriter;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.Statement;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Map;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import logic.functions;
import javax.servlet.http.HttpSession;
@WebServlet(name = “loginServlet”, urlPatterns = {“/loginServlet”})
public class loginServlet extends HttpServlet {
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType(“text/html;charset=UTF-8″);
PrintWriter out = response.getWriter();
Connection con=null;
PreparedStatement pstmt=null;
ResultSet rs;
RequestDispatcher rd;
try {
String userID=functions.checkNull(request,”userID”);
String password=functions.checkNull(request,”password”);
String path=””;
HttpSession user=request.getSession(true);
HttpSession allMenu=request.getSession(true);
con=functions.getDBConnetion();
String query=”SELECT * FROM `user` where email=? and password=?”;
pstmt=con.prepareStatement(query);
pstmt.setString(1, userID);
pstmt.setString(2, password);
rs=pstmt.executeQuery();
if(rs.next())
{
String utype=rs.getString(“userType”);
String uid=rs.getString(“userId”);
if(utype.equalsIgnoreCase(“2″))
path=”productDisplay.jsp”;
else
path=”productDisplay.jsp”;
user.setAttribute(“username”, userID);
user.setAttribute(“userId”, uid);
user.setAttribute(“usertype”, utype);
user.setAttribute(“img”, rs.getString(“image”));
getMenu(con,allMenu);
}
else
{
path=”login.jsp?error=Either username or password incorrect.”;
}
String p=request.getHeader(“Referer”);
if(!p.contains(“login.jsp”))
{
response.sendRedirect(request.getHeader(“Referer”));
}
rd=request.getRequestDispatcher(path);
rd.forward(request, response);
}
catch(Exception e)
{
out.println(e);
}
finally {
out.close();
}
}
public void getMenu(Connection con,HttpSession allMenu) throws Exception
{
PreparedStatement pstmt=null;
String query=”SELECT p.* FROM menu p INNER JOIN userright a ON p.menuid=a.menuid ”
+ “AND p.mainmenuid=0 AND a.userid=? UNION SELECT p.* FROM menu p ”
+ “WHERE p.menuid IN (SELECT mainmenuid FROM menu ”
+ “WHERE menuid IN (SELECT menuid FROM userright WHERE userid=?)) and p.usertype=? ORDER BY priority”;
pstmt=con.prepareStatement(query);
pstmt.setInt(1, 28);
pstmt.setInt(2, 28);
pstmt.setInt(3, 1);
ResultSet rs=pstmt.executeQuery();
ArrayList subMenu;
Map mn=new HashMap();
ArrayList mainmenuName=new ArrayList();
Statement stmt2=con.createStatement();
ResultSet rs2;
// HttpSession allMenu=request.getSession(true);
while(rs.next())
{
int mId= rs.getInt(“menuid”);
String mname=rs.getString(“menuitem”);
String pg=rs.getString(“Path”);
String icon=rs.getString(“icon”);
//if(pg==null)
// pg=”no”;
mainmenuName.add(mname+”$”+pg+”@”+icon);
String q2=”SELECT a.menuid,p.menuitem,p.Path,a.userid,p.Priority,p.icon FROM userright a INNER JOIN menu p ON p.menuid =a.menuid and p.mainmenuid=”+mId+” WHERE a.userid=28 ORDER BY p.Priority”;
System.out.println(q2);
rs2= stmt2.executeQuery(q2);
subMenu=new ArrayList();
while(rs2.next())
{
subMenu.add(rs2.getString(“menuitem”)+”$”+rs2.getString(“Path”));
}
mn.put(mname, subMenu);
}
allMenu.setAttribute(“menu”, mn);
System.out.println(“main menu: “+mainmenuName+” menu= “+mn);
allMenu.setAttribute(“mainMenu”, mainmenuName);
}
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
@Override
public String getServletInfo() {
return “Short description”;
}// </editor-fold>
}
CHAPTER – 7
TESTING
TESTING CHAPTER ‘ 7
7.1 TESTING PLAN:
‘ A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. Software is tested at various levels by various techniques like black box, white box, Unit testing and Integration testing etc. Initially all the operations are tested separately while development .This is unit testing and as the developer does it, so it is white box testing.
7.1.1 The Testing Process:
‘ We test the software process activities such as Design, Implementation, and Requirement Engineering. Because Design errors are very costly to repair once system has been started to operate, therefore, it is quite obvious to repair them at early stage of the system development.
Figure 7(a) Testing Process
7.1.2 Requirements Traceability:
‘ As most interested portion in the system is system meeting its requirements therefore testing should be planned so that all requirements are individually tested. We checked the output of certain combination of inputs, which gives desirable result, or not. Strictly stick to your requirements specification gives you the path to get desirable result for system users.
Figure 7(b) Software testing levels
7.2 TESTING STRATEGY:
‘How we plan to cover the product so as to develop an adequate assessment of quality?’
A good test strategy is:
‘ Specific
‘ Practical
‘ Justified
The purpose of a test strategy is to clarify the major tasks and challenges of the test project.
Test Approach and Test Architecture are other terms commonly used to describe what I’m calling test strategy.
Example of a poorly stated (and probably poorly conceived) test strategy:
‘We will use black box testing, cause-effect graphing, boundary testing, and white box testing to test this product against its specification.’
Test Strategy for Decide Right
What is the product?
‘An application to help people who peoplewant to scale up their smallscale bussiness and want to manage and grow them in aeffective way.
What are the key potential risks?
‘ It will manage seller’s bussiness in easy and effective way.
‘ People will buy the product cheaper than they get in to the market.
‘ It will provide a way to scale up the bussiness of the seller by reaching far customers through this web portal..
‘ Customer can get a wide range and variety of product from which they can choose the products.
‘ It will not be able to handle operation if internet is not there.
How could we test the product so as to evaluate the actual risks associated with it?
‘ Understand the underlying algorithm.
‘ Simulate the algorithm in parallel.
‘ Capability tests each major function.
‘ Generate large numbers of decision scenarios.
‘ Create complex scenarios and compare them.
‘ Review documentation and help.
7.3 TESTING METHODS:
1. White-Box testing:
‘ White-box testing (also known as clear box testing, glass box testing, and transparent box testing and structural testing) tests internal structures or workings of a program, as opposed to the functionality exposed to the end-user. In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs.
‘ While white-box testing can be applied at the unit, integration and system levels of the software testing process, it is usually done at the unit level. It can test paths within a unit, paths between units during integration, and between subsystems during a system’level test. Though this method of test design can uncover many errors or problems, it might not detect unimplemented parts of the specification or missing requirements.
2. Black-Box testing:
‘ Black-box testing treats the software as a “black box”, examining functionality without any knowledge of internal implementation. The tester is only aware of what the software is supposed to do, not how it does it. Black-box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, state transition tables, decision table testing, fuzz testing, modelbased testing, use case testing, exploratory testing and specification-based testing.
‘ Specification-based testing aims to test the functionality of software according to the applicable requirements. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either “is” or “is not” the same as the expected value specified in the test case. Test cases are built around specifications and requirements, i.e., what the application is supposed to do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be functional or non-functional, though usually functional. Specification-based testing may be necessary to assure correct functionality, but it is insufficient to guard against complex or high-risk situations.
7.4 TEST CASES:
Table 7.1: TestCases:
No. Test Case Expected Output Actual Output Result
1 Login of User
Logged in Navigate to user’s
Home pg. PASS
2 Login of Store-Owner Logged in Navigate to stores
Home pg. PASS
3 Upload Store’s Product Successfully Upload Product Successfully Uploaded Product PASS
4 Verify Uploaded Product Successfully Verified Uploaded Product Successfully Verified Uploaded Product PASS
5 Display Store’s Address via MAP Successfully Display Successfully Displayed PASS
6 Show the recently added Comment by User Display recently added comment Displaying recently added comment PASS
7 Send notification via email when order Item Successfully send notification Successfully send notification PASS
CHAPTER – 8
SCREEN SHOTS AND USER MANUAL
SCREEN SHOTS AND USER MANUAL CHAPTER – 8
Home Page:
Fig.8 (a) Home Page
Login Page:
Fig.8 (b) Login Page
Registration Page:
Fig.8 (c) Registration Page
About Us Page:
Fig.8 (d)About US Page
Product view Page:
Fig.8 (e) product view page
Registration Page:
Fig.8 (f) Registration Page
ChangePassword Page:
Fig.8 (g) Change Password Page
Product Description Page:
Fig.8 Product Description Page
Shipping Details Page:
Fig.8 (l) Shipping Details Page
Shipping Address Page:
Fig.8 (n) Shipping Address Page
Comment view Page:
Fig.8 (m) Comment View Page
CHAPTER – 9
LIMITATION AND FUTURE ENHANCEMENT
LIMITATION AND FUTURE ENHANCEMENT Chapter-9
9.1 Limitation
‘ The entire project is basically based on the smart devices and computer system, so the people who are going to interact must be having the basic knowledge about the computer and or smart device.
‘ The person must be able to operate some basic function of the system.
‘ The other limitation is that, if customer gives false address to the system( in case of CASE ON DELIVERY), system can’t verify, whether the customer has actually given correct address or not.
9.2 Future Enhancement
‘ We can enhance this system by analyzing post release usage and feedback of the actual users.
‘ Right now system is working for limited Items, we will make it available for maximum item type.
CHAPTER – 10
CONCLUSION AND DISCUSSION
CONTACLUSION AND DISCUSSION Chapter-10
10.1 Self Analysis of Projects Viability
‘ Every project work, does not matter software project or any other project, could not be the result of sole effort; even though, developer team consists of two members. We think success of any project doesn’t depend only on better software development skills, but also, zeal to listen and help the users. Only user interaction at development phase can give you an idea to fulfill their requirements. Because, software product is of developer’s up to the development or installation phase, but then after it is of user’s. We experienced that do make the software for users not for fame of being better programmer or software developer. Ultimately, users appraise your efforts not your peers.
10.2 Summary of Project Work
‘ We have completed our project work, based on using software engineering and system analysis and design approach. We have done our work with preplanning scheduling related with time constrains and result oriented progress in project development.
‘ Our project was started in the second week of July – 2015 and we completed our project documentation and partial design of our project in the month of November – 2015. Initially, there were some problem regarding some phases but we have planned to resolve those problems. We have divided our work in different phases and solved problems and difficulties. We completed our project in the month of APRIL ‘ 2016.
REFERENCES
Websites Referred
‘ http://docs.oracle.com/javaee/6/tutorial/doc/gkiow.html
‘ http://en.wikipedia.org/wiki/E-learning
‘ http://www.programcreek.com/2012/11/top-100-java-developers-blogs/
‘ http://www.online-learning.com
‘ http://www.adcash.com
‘ http://ebookbrowse.com
‘ http://www.jsptut.com/Further.jsp
‘ https://www.codecademy.com/learn/learn-java
Books Referred
‘ Java 2 Complete Reference
‘ SQL, PL/SQL THE PROGRAMMING LANGUAGE OF ORACLE by Ivan Bayross ( 3rd Edition )
‘ ANALYSIS AND DESIGN OF INFORMATION SYSTEMS BY James A Senn(2ndEdition)
‘ OBJECT-ORIENTED MODELING AND DESIGN WITH UML by Michael R Blaha and James R Rambaugh (2nd Edition)
‘ PROGRAMMING IN JAVA by E Balagurusamy