1.

INTRODUCTION

Company Name:-Digicraft Solution

Project Title:-Huda Cargo service system

About the Organization:-

Digicraft Solution is a software technology company headquartered in Mumbai specializing

in Web application development, Web Hosting, Website Design, Website Development, SEO
and Digital Marketing.

Digicraft solution offers superior, reliable and affordable Web Hosting, Website Design,
Website Development, Logo Design, ERP Software, etc., to individuals and small businesses.
Founded in 2017, Digicraft solution has quickly grown to become a leader in Performance
Web Hosting, Website Design, Website Development, Logo Design, ERP Software.

Digicraft solution company philosophy is to create the kind of website that most businesses
want: easy to find, stylish and appealing, quick loading, mobile responsive and easy to buy
from. Website development for any industry or business is part of our regular competence.

All programs are developed with a convenient user interface and solutions which are carefully
integrated with variances calculated for accommodating the remotest possible needs within
the enterprise being created.

Mr. R.V is the CEO of Digicraft solution and an expert on the enterprise market. Core
development expertise includes Android, HTML5, JavaScript, PHP, Magento, Opencart,
WordPress, .NET, and related technologies.

1
1.1 Motivation:-

Digicraft solution is a Software company that provides website, software and services. Huda
Cargo service system project will have different modules. There are some facility for the user
who will operate this system. While taking orders from its customers, it will take all the
details of its customers who is placing the orders and all the details for the recipient such as its
address, name, mobile number. During billing process system will generate a tracking id for
their products. Through this tracking id, customers or its recipient will able to track their
products from any location using internet. It will provide status of the product after placing
orders within 1 Minute.

1.2Problem Definition:-

Currently there is no such system for product pickup facility. A user doesn’t get the
information about the products status where is right now i.e., the current status of the product
or parcel. The drawbacks of present manual system this computerized system has been
proposed.
It helps in reducing human efforts for tracking parcel details, order details, customer details
and many such things involved in the process.

1.3Objective of Project:-

The objective of the project is to keep all the detailed information about the Customers their
order history, their Details, their other details etc of “Huda Cargo services”. The system will
automate the manual process of the “Huda Cargo services” and help to generate timely
according to the user requirement.

2
1.4 Limitation of Project:-

At present the major limitation of the project is that since the accounts of the users are
authenticated through only valid user-id, all their account details also stored. In Huda Cargo
services, the payment is made in cash. So for the billing procedure for the regular customer,
we have to refer all the records in Export Report. For this reasons this task is more time
consuming.

3
 2. LITERATURE SURVEY

2.1 INTRODUCTION

We have taken a detailed survey of existing scenario and worked on the betterment of the
system for customers as well as the Sales team by saving their time and making their work
easy with the customers. We have looked into the operational, technical and economic
feasibility to create a flexible and optional service for customers.

2.2 Existing System:

As the system is totally manual, the activity takes place in the system as following. In this
system, first of all consignors placed their consignments like covers, documents, non-
documents etc. to the officer of the cargo branch. Here this branch acts as a source branch.
Then the branch officer prepares the consignment note.

There are 3 ways to transship the consignments.

1) By air

2) By cargo

3) By surface

In air delivery boy takes the all consignments in the plane. It is also known as onboard
courier. In cargo source branch booked the plane & the delivery boy of the destination branch
received all the consignments. In surface courier services is provided by road. After receiving
consignments, destination branch checked the manifest, whether any consignment is left or
not. Then based on manifest the destination branch prepared the ‘Delivery Run Sheet’. DRS
NO: It contains the number of the delivery run sheet.

4
2.3 Disadvantages of Existing System:

 The current system is not computerized.

 Less customer satisfaction.
A user doesn’t get the information about the products, its tracking id, and about the status or
any other information.

2.4 Proposed System:

The proposed system is completely a computerized system. To overcome drawbacks of
present manual system this computerized system has been proposed. It is very easy to use and
user friendly in nature. It helps in reducing human efforts for tracking parcel details, order
details, customer details and many such things involved in the process.

We hereby are grateful to present our software project through this report. Our proposed
system is computer based. Which provide various User interfaces (Forms) for various
operations and hence interactive.

BENEFITS OF PROPOSED SYSTEM

 In computer system of the courier service computation of the rate is

easily & quickly done.
 Computer system of the courier service provides fast access.
 If our document or any consignment is missed then we can know it
easily using the database in the computer system of courier services.
 Using this computerized system, bill issued procedure becomes fast.
 In computer system has to fill the various forms can be easily generated
at time.
 Accuracy in work.
 Easy to update information.
 Work becomes very speedy.
 Access of any information individually.

5
 Decrease the load of the person involve in existing manual system.
 Well designed reports.
 Easy & fast retrieval of information.
 It is very user friendly and easy to handle.

6
 3. ANALYSIS

3.1 Introduction:

Analysis is the process of breaking a complex topic or substance into smaller parts to gain a
better understanding of it. The phase is detailed, appraisal of the existing system. This
appraisal includes how the system works and what it does. It also includes finding out in more
detail-what are the problems with the system and what user requires from the new system or
any new change in system. The output of this phase results in the detailed model of the
system. The model describes the system function and data and system information flow. The
phase also contains the details set of the user requirements and these requirements are used to
set objectives for the new system. It is always necessary to study and recognize the problems
of the existing system, which will help in finding out the requirements of the new system.
System study helps in finding different alternatives for better solutions.

3.2 Software Requirement Specification:

Software requirements specification (SRS) is a description of a software system to be

developed, laying out functional and non-functional requirements, and may include a set of
use cases that describe interactions the users will have with the software.

The SRS document is the final outcome of the requirements analysis and specification phase.
SRS Document is considered as a reference document.

3.2.1 User Requirement:

It is very important to get users of the system fully involved such that the problem of change
management does not arise. The users, who will use the system were approached during the
study and were asked what they expected of the proposed system and the following were the
findings-
 A system that is easy to learn and use.

7
 A system that improves on the information storage and retrieval.
 A system that is fast in producing results which will be ready at the point of care
therefore reducing on waiting time and increasing on time.
 In computer system of the courier service computation of the rate is easily &
quickly done.
 Computer systems of the courier service provide fast access.
 If our document or any consignment is missed then we can know it easily using
the database in the computer system of courier services.
 Using this computerized system, bill issued procedure becomes fast.
 In computer system has to fill the various forms can be easily generated at time.
 Accuracy in work.
 Easy to update information.
 Work becomes very speedy.
 Access of any information individually.
 Decrease the load of the person involve in existing manual system.
 Well designed reports.
 Easy & fast retrieval of information.
 User friendly and easy to handle.
 GUI : The proposed system provides better graphical user interface
 Search : Searching details about customer, order, Parcel is comparatively easy
 Increase Work Speed: Due to automation of some part of system work speed
would increase.
 Less Paperwork : For the proposed system less paperwork is required
 Reduces Error : Due to computerization there are less possibilities of error
 Economical: Due to minimal errors and work delay proposed system can be
economically beneficial to the company.

8
3.2.2 Software Requirements:-

 Operating System - Windows, Linux, Mac OS

 Server Side Script: WordPress ,PHP
 Database: MySql
 Latest Browser: Chrome, Firefox, Safari etc.

3.2.3 Hardware Requirements:-

 PROCESSOR: Pentium IV or higher version
 RAM: 512 MB or above
 Hard Disk: 512 MB or above
 Proper Internet/Wi-Fi connection
 Desktops/Laptops/Smart Phones.
 Additional Output device: Printer

9
3.3 Content Diagram:
System content diagram is a high-level map of a system and its surrounding environment.
Drawing a context diagram helps you to understand how a system interacts with other
systems, business units, and key personnel. In addition, you can use it to help define the scope
of a system's operations. System context diagrams are drawn using only three diagramming
elements, which are the context bubble, external entities, and data flows.

Customer

Credit
Tracking payment

Purchase Items

charge

Reorder manifest

Pick list System

Fulfillment
Shipper
Tracking

Completion

10
 3.4 Algorithms and Flow Chart:

Admin:

Start

Login

Successful
No

Yes
Manage and
controls

Product Customer Take Order payment order Status

details details

Update Showcusto Show product Payment done Provide

product mer details order during product Tracking ID
details order

Cash or check only

End

11
Client:

Start

Customer

no Enter yes
Tracking Id

Error message Show

product
status

End

12
 4. DESIGN

4.1 Introduction

Software design is both a process and a model. The design process is a sequence of steps that
enable the designer to describe all aspects of the software to be built. It is important to note,
however, that the design process is not simply a cookbook. Creative skill, past experience, a
sense of what makes “good” software and an overall commitment to quality are critical
success factors for a competent design.

Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could be seen as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering.

If the broader topic of product development "blends the perspective of marketing, design, and
manufacturing into a single approach to product development," then design is the act of taking
the marketing information and creating the design of the product to be manufactured. Systems
design is therefore the process of defining and developing systems to satisfy specified
requirements of the user.

Object-oriented analysis and design methods are becoming the most widely used methods for
computer systems design. The UML has become the standard language in object-oriented
analysis and design. It is widely used for modeling software systems and is increasingly used
for high designing non-software systems and organizations.

13
4.2 Diagrams

DFD/ER/UML Diagram

DFD:-
The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of the
software.

Data objects represented by labeled arrows and transformation are represented by circles also
called as bubbles. DFD is presented in a hierarchical fashion i.e. the first data flow model
represents the system as a whole. Subsequent DFD refine the context diagram (level 0 DFD),
providing increasing details with each subsequent level.

The DFD enables the software engineer to develop models of the information domain &
functional domain at the same time. As the DFD is refined into greater levels of details, the
analyst performs an implicit functional decomposition of the system. At the same time, the
DFD refinement results in a corresponding refinement of the data as it moves through the
processes that embody the applications.

A context-level DFD for the system the primary external entities produce information for use
by the system and consume information generated by the system. The labeled arrow
represents data objects or object hierarchy.

RULES FOR DFD:

• Fix the scope of the system by means of context diagrams.

• Organize the DFD so that the main sequence of the actions
• Reads left to right and top to bottom.
• Identify all inputs and outputs.
• Identify and label each process internal to the system with Rounded circles.

14
• A process is required for all the data transformation and Transfers. Therefore, never
connect a data store to a data Source or the destinations or another data store with just
a Data flow arrow.
• Do not indicate hardware and ignore control information.
• Make sure the names of the processes accurately convey everything the process is
done.
• There must not be unnamed process.
• Indicate external sources and destinations of the data, with Squares.
• Number each occurrence of repeated external entities.
• Identify all data flows for each process step, except simple Record retrievals.
• Label data flow on each arrow.
• Use details flow on each arrow.
• Use the details flow arrow to indicate data movements.

15
Zero level DFD:

Cargo
management

Schedule
Management

Track
Huda Cargo
management
Services(track
ing System)
Payment
Management

Ship
management

Delivery
Management

16
First level DFD:

Cargo Generate
management Cargo Report

Track
management Generate Track
Report

Ship
management Generate Ship
Huda Cargo Report
Services(track
Delivery ing System)
Management Generate
delivery Report

Generate
Payment Payment report
Management

Schedule Generate
Management Schedule report

17
Second level DFD:

Admin
Cargo
management

Login to
system
Track
management

Ship Check
management credential

Huda Cargo
Services(track
Delivery
ing System)
Management

Payment
Management

Schedule
Management

18
DFD for Cargo System:

Client Module:

Booking Cargo:

19
ER Diagram:-

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a
way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually represent
data objects. Since Chen wrote his paper the model has been extended and today it is
commonly used for database design for the database designer, the utility of the ER model is:

• It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
• It is simple and easy to understand with a minimum of training. Therefore, the model can be
used by the database designer to communicate the design to the end user.
•In addition, the model can be used as a design plan by the database developer to implement a
data model in specific database management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and
many-to-many. A one-to-one (1:1) relationship is when at most one instance of a entity A is
associated with one instance of entity B. For example, "employees in the company are each
assigned their own office. For each employee there exists a unique office and for each office
there exists a unique employee.

A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one instance of
entity A. An example of a 1: N relationships is a department has many employees each
employee is assigned to one department

A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance
of entity A, there are zero, one, or many instances of entity B and for one instance of entity B

20
there are zero, one, or many instances of entity A. The connectivity of a relationship describes
the mapping of associated.

ER Notation
There is no standard for representing data objects in ER diagrams. Each modeling
methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used; among the more common are
Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used for the
basic ER constructs are:
 Entities are represented by labeled rectangles. The label is the name of the entity.
Entity names should be singular nouns.
 Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
 Attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot
is omitted, the cardinality is one.
 Existence is represented by placing a circle or a perpendicular bar on the line.
Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the entity
that is optional.

21
 Admin Module:

Login_id username password

Or_name User_id
Login Order
https://kris _id
hnakantma Order_date
urya91.000
webhostap
Details
p.com/ order
Order_status
https://kris
hnakantma
urya91.000
webhostap
user
p.com/

User_id Product_id

number
username

Email_id location

22
 Client Module:

User_id username

user

Check
product
srtatus

Shipper_address

Tracking_product
status

User_id
Product_id

Tracking_id Tracking_date
Email_id location

23
4.3 Module Design & Organization

 Organization:
Many models and techniques are followed for software development these days but
most widely used is named as Software Development Life Cycle (SDLC) or Waterfall
Model. It comprises mainly of following seven steps.

1. Project Planning:

This level involves determining the project goal and running a feasibility study
amongst the client and web development services, taking into consideration various
factors like project cost, equipment cost, practicality etc.

2. System Requirement Analysis:

Refinement of project goals into defined functions and operations of the proposed
application through intensive discussion between web development services and the
client is achieved through this step.

3. System Design

Documentation of various details like operations and functions such as screen layouts,
process diagrams and other documentation are done here.

4. Implementation

This is where the expertise of web development services are needed the most when
actual back end coding is done.

24
5. Testing

In this phase the product is put through various testing environments and tools
designed and used by web development services to make the product to remove its
bugs and errors to ensure harmonious execution.

6. Acceptance and Deployment

Finally the web development services deploy and install the system after getting
formally approved by the client.

7. Maintenance

The web development services not only make sure the installation of the application
but they are also responsible for subsequent maintenance and upgrading if and when
needed.

25
  Module Design:

Diagram:

UML Diagram:-

Actor: coherent set of roles that users of use cases play when interacting with the use
cases.

Use case:
A description of sequence of actions, including variants, that a system
performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product
after analysis. The goal from this is to produce a model of the entities involved in the
project which later need to be built.
There are various kinds of methods in software design:

They are as follows:

26
  Use case Diagram
 Sequence Diagram

Use Case Diagram:

Use case diagrams model behavior within a system and helps the developers understand of
what the user require. The stick man represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying
that can do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.

• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.

A Use case is a description of set of sequence of actions. Graphically it is rendered as an

ellipse with solid line including only its name. Use case diagram is a behavioral diagram
that shows a set of use cases and actors and their relationship. It is an association between
the use cases and actors. An actor represents a real-world object.

27
Admin module:

The admin has rights to upload data to the server, modify and delete data. Design web
services and pass data to the front end when the client makes a request to the server.

The admin can add, modify and delete user’s details to the back end and each user will
have its own separate database tables.

The menu is also dynamic, the admin can handle all the menu components and data is
dynamic.

28
Client Module:

The client has to request the data and display on the UI. The cache memory has to be
optimized so that the user does not have problems to load the app. Also the user has to keep
data in sync with the server so that whatever updates happen at the back end have to be
reflected in the front end as well.

29
Sequence Diagram:

Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An

interaction diagram shows an interaction, consisting of set of objects and their relationship
including the messages that may be dispatched among them.

A sequence diagram is an introduction that empathizes the time ordering of messages.

Graphically a sequence diagram is a table that shows objects arranged along the X-axis and
messages ordered in increasing time along the Y-axis.

Register Login Cargoprice View status

Registration
Authentication View Cargo Price

Book a Cargo

Status of Cargo
Valid user

Not valid user

30
 5. IMPLEMENTATION AND RESULTS

5.1 Introduction:

In software engineering, a software development methodology (also known as a system

development methodology, software development life cycle, software development process,
and software process) is a division of software development work into distinct phases (or
stages) containing activities with the intent of better planning and management. It is often
considered a subset of the systems development life cycle. The methodology may include the
pre-definition of specific deliverables and artifacts that are created and completed by a project
team to develop or maintain an application.

Common methodologies include waterfall, prototyping, iterative and incremental

development, spiral development, rapid application development, extreme programming and
various types of agile methodology. Some people consider a life-cycle "model" a more
general term for a category of methodologies and a software development "process" a more
specific term to refer to a specific process chosen by a specific organization. For example,
there are many specific software development processes that fit the spiral life-cycle model.

5.2 Explanation of Key Functions:

The high-level functional requirements often need to be identified either from an informal
problem description document or from a conceptual understanding of the problem. Each high-
level requirement characterizes a way of system usage (Service invocation) by some user to
perform some meaningful piece of work.

Web Services:
It is the service which sends data to the front end when the user requests to the server. The
service is generic i.e. it will return every data that is requested to the user.

31
5.3Method of Implementation:

A. Technology Used:
1. WordPress:
WordPress is a free and open-source content management system (CMS) based
on PHP and MySQL. To function, WordPress has to be installed on a web server, which
would either be part of an Internet hosting service or a network host in its own right. An
example of the first scenario may be a service like WordPress.com, and the second case
could be a computer running the software package WordPress.org. A local computer may
be used for single-user testing and learning purposes. Features include a plugin
architecture and a template system. WordPress is used by 30.6% of the top 10 million
websites as of April 2018. As such, WordPress is the most popular website management
or blogging system in use on the Web, supporting more than 60 million
websites. WordPress has also been used for other application domains such as pervasive
display systems (PDS).

WordPress has a web template system using a template processor. Its architecture is
a front controller, routing all requests for non-static URIs to a single PHP file which
parses the URI and identifies the target page. This allows support for more human-
readable permalinks.

Theme in WordPress:
WordPress users may install and switch among different themes. Themes allow users to
change the look and functionality of a WordPress website without altering the core code
or site content. Every WordPress website requires at least one theme to be present and
every theme should be designed using WordPress standards with structured PHP,
valid HTML (Hyper Text Markup Language), and Cascading Style Sheets (CSS). Themes
may be directly installed using the WordPress "Appearance" administration tool in the
dashboard, or theme folders may be copied directly into the themes directory, for example
via FTP. The PHP, HTML and CSS found in themes can be directly modified to alter

32
theme behavior, or a theme can be a "child" theme which inherits settings from another
theme and selectively overrides features. WordPress themes are generally classified into
two categories: free and premium. Many free themes are listed in the WordPress theme
directory, and premium themes are available for purchase from marketplaces and
individual WordPress developers. WordPress users may also create and develop their own
custom themes. The free theme Underscores created by the WordPress developers has
become a popular basis for new themes.

Types of WordPress Theme:

I. Premium WordPress Themes:

I personally prefer to use premium WordPress themes over any other type. Premium
themes are very high quality. WordPress themes that are developed by small or large
companies and in most cases you pay for. Premium themes generally range from: $50 –
$100 for a single site license.

II.Free WordPress Themes:

There are literally thousands of free WordPress themes available on the internet. The
easiest way to find most of them is to visit the WordPress.org themes directory.

III.Custom WordPress Themes:

Custom WordPress themes are developed specifically for a website by web designers and
developers and offer flexibility and options only limited by money and technology. On
the downside though, custom themes can be very expensive, generally running $500 –
$3,000 dollars depending on how sophisticated they are and how skilled the designer is.
The more custom graphics they have, generally the more expensive they are.

33
Plugins in WordPress:

WordPress plugin architecture allows users to extend the features and functionality of a
website or blog. As of March 2017, WordPress has over 55,286 plugins available, each of
which offers custom functions and features enabling users to tailor their sites to their
specific needs. These customizations range from search engine optimization, to client
portals used to display private information to logged in users, to content management
systems, to content displaying features, such as the addition of widgets and navigation
bars. Not all available plugins are always abreast with the upgrades and as a result they
may not function properly or may not function at all. Most plugins are available through
WordPress themselves, either via downloading them and installing the files manually via
FTP or through the WordPress dashboard. However, many third parties offer plugins
through their own websites, many of which are paid packages.
Web developers who wish to develop plugins need to learn WordPress' hook system
which consists of over 300 hooks divided into two categories: action hooks and filter
hooks.

Used Plugins in Our Project:

a.) Beaver Builder Plugin:

Beaver Builder is a flexible drag and drop page builder that works on the front end of your
WordPress website. Whether you’re a beginner or a professional, you’re going to love
taking control of your website. Helps to stop writing HTML or wrestling with confusing
short codes. With Beaver Builder, building beautiful, professional WordPress pages is as
easy as dragging and dropping.

b.) Contact Form 7:

Contact Form 7 can manage multiple contact forms, plus you can customize the form and
the mail contents flexibly with simple markup. The form supports Ajax-powered
submitting, CAPTCHA, A kismet spam filtering and so on.

34
c.) Contact Widgets:
Beautifully display social media and contact information on your website with simple,
easy-to-use widgets.
Display your contact information including email address, phone number, fax and physical
address (including a map).

d.) Elementor:
It’s about time for a live page builder, with no limits of design. A page builder delivers
high-end page designs and advanced capabilities, never before seen on WordPress.

e.) Status and Order Tracking:

Order tracking and status tracking software that allows you to quickly and easily manage
the status of your orders, projects, shipments, or any other item, by posting order tracking
updates about the status, or tickets that can be viewed through the front end of your
WordPress site, for easy order management. All this is done via a series of easy-to-use
order short codes.

f.) WP Cargo:

1. Notify your customers about their shipments via SMS and eMail.

2. Customer notification on important delivery updates such as Shipment Picked, In

Transit, Out of Delivery, Delivery Issue, and Delivered

3. Customers can track the shipment status of their order on your website

4. Dedicated tracking link for each shipment

5. Track airway bill number from multiple courier companies at one place

6. Track complete shipping status from confirms order to order delivery

7. Show shipment real time status details

8. 100% new files, this extension will NOT replace any core files

35
9. Support Major Indian Carriers:-Blue dart, DTDC, Fed ex India, Aram ex, Delivery,
Guavas’, E-com Express, DHL India, Dot First Flight, Red Express, The Professional
Couriers, and Xpress Bes.

g.) G translator:

Settings include: inline or vertical layout, show/hide specific languages, hide/show Google
toolbar, and hide/show Google branding. Add the short code to pages, posts, and widgets.

h.)Limit Login Attempts:

Limit Login Attempts for login protection, protect site from brute force attacks. Brute
Force Attack aims at being the simplest kind of method to gain access to a site: it tries
usernames and passwords, over and over again, until it gets in. WP Limit Login Attempts
plugin limit rate of login attempts and block IP temporarily. It is detecting bots by Captcha
verification.

Other Features in WordPress:

WordPress also features integrated link management; a search engine–friendly, clean
permalink structure; the ability to assign multiple categories to posts; and support for
tagging of posts. Automatic filters are also included, providing standardized formatting
and styling of text in posts. WordPress also supports the Trackback and Pingback
standards for displaying links to other sites that have them linked to a post or an article.
WordPress posts can be edited in HTML, using the visual editor, or using one of a number
of plugins that allow for a variety of customized editing features.

36
 2. PHP(Hypertext Preprocessor):
PHP: Hypertext Preprocessor (or simply PHP) is a server-side scripting language
designed for Web development, but also used as a general-purpose programming
language. It was originally created by Rasmus Lerdorf in 1994, the PHP reference
implementation is now produced by The PHP Group. PHP originally stood for
Personal Home Page, but it now stands for the recursive acronym PHP: Hypertext
Preprocessor.
PHP is a server side scripting language that is embedded in HTML. It is used to
manage dynamic content, databases, session tracking, even build entire e-commerce
sites.

3. MySQL:
MySQL is an open source relational database management system (RDBMS) based on
Structured Query Language (SQL). ... LAMP is a Web development platform that uses
Linux as the operating system, Apache as the Web server, MySQL as the relational
database management system and PHP as the object-oriented scripting language.

MySQL Features:

 Relational Database Management System (RDBMS): MySQL is a relational

database management system.

 Easy to use: MySQL is easy to use. You have to get only the basic knowledge of
SQL. You can build and interact with MySQL with only a few simple SQL statements.

 It is secure: MySQL consist of a solid data security layer that protects sensitive data
from intruders. Passwords are encrypted in MySQL.

37
 Client/ Server Architecture: MySQL follows a client /server architecture. There is a
database server (MySQL) and arbitrarily many clients (application programs), which
communicate with the server; that is, they query data, save changes, etc.

 Free to download: MySQL is free to use and you can download it from MySQL
official website.

 It is scalable: MySQL can handle almost any amount of data, up to as much as 50

million rows or more. The default file size limit is about 4 GB. However, you can
increase this number to a theoretical limit of 8 TB of data.

 Compatibale on many operating systems: MySQL is compatible to run on many

operating systems, like Novell NetWare, Windows* Linux*, many varieties of UNIX*
(such as Sun* Solaris*, AIX, and DEC* UNIX), OS/2, FreeBSD*, and others. MySQL
also provides a facility that the clients can run on the same computer as the server or
on another computer (communication via a local network or the Internet).

 Allows roll-back: MySQL allows transactions to be rolled back, commit and crash
recovery.

 High Performance: MySQL is faster, more reliable and cheaper because of its unique
storage engine architecture.

 High Flexibility: MySQL supports a large number of embedded applications which

makes MySQL very flexible.

 High Productivity: MySQL uses Triggers, Stored procedures and views which allows
the developer to give a higher productivity.

38
B. Test Specification
When the app is developed, the product before sending it to the user is tested
by the team to know whether the application is User acceptable. The test is called User
acceptance test.

Steps for applying UAT test are as follows:

1. Create a patch of development which is done.

2. Take back up of UAT files and database.
3. Run the application on the device.
4. Apply patch on UAT application.

After that the product which has been developed is tested. All the functionality
is proper or not is compared with development file and if any error occurs then it is
corrected. And if no error is found then the patch is sent to testing team for further
testing price.

39
5.3.1 Forms:-

1 . Home Page:-

This is a home page of Huda Cargo Services

40
2. About:-

This is about Page of Huda Cargo Services

41
3. Services:-

Huda Cargo Service provides the services to the customers.

42
 4. Tracking System:-

In this page we use the order Id to Track the Product Shipment

43
 5. Blog:-

In this Page they post their latest news about the Huda Cargo Services.

44
 6. Contact Us:-

This is a contact page of Huda Cargo Services for query information.

45
5.3.2 Output Screens:-

1.Enter tracking number:

We enter the order Id to check the status of product.

46
2. Status Report:-

47
This is a status report of product.

48
 3. Invoice

This is the Invoice of the product.

49
WordPress Panel Screen:

50
51
5.3.3 Result Analysis :-

Analysis is the process of gathering and comparing information about the web and its
operation and use in order to improve the web's overall quality and to identify problem areas.

The overall goals of a web analyst are

1. Check to make sure that the web works:
 Rhetorically: Is the web accomplishing its stated purpose for its intended audience?
 Technically: Is the web functionally operational, and is its implementation consistent
with current PHP specifications?
 Semantically: Is the web's information content correct, relevant, and complete?
2. Make recommendations to the other web-development processes:
 Advise on new web planning, including administrative and information policy.
 Give input to web designers on user problems or redesign ideas.
 Recommend maintenance to web implementers.
 Give reports to web promoters about user experience with the web.
 Collaborate with web innovators by providing insight for improving the web's content
or operation.

The web analyst thus acts as a reviewer, evaluator, and auditor for the web-development
process. When practical, therefore, the web analyst should be as independent as possible from
the duties of web implementation, design, and planning.

52
6. TESTING AND VALIDATION

6.1 Introduction

Testing:
“Software testing is the process of analyzing a software item to detect the differences between
existing and required conditions (that is, bugs) and to evaluate the features of the software
item”.

Software Testing:
Software testing is an investigation conducted to provide stakeholders with information about
the quality of the product or service under test. Software testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks
of software implementation. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs (errors or other
defects).

Software testing can also be stated as the process of validating and verifying that Software
program/application/product. It meets the business and technical requirements that guided its
design and development, works as expected and can be implemented with the same
characteristics.

Software testing, depending on the testing method employed, can be implemented at

any time in the development process. However, most of the test effort occurs after
the requirements have been defined and the coding process has been completed. As
such, the methodology of the test is governed by the software development
methodology adopted.

Different software development models will focus the test effort at different points in
the development process. Newer development models, such as Agile, often employ
test driven development and place an increased portion of the testing in the hands of

53
the developer, before it reaches a formal team of testers. In a more traditional model,
most of the test execution occurs after the requirements have been defined and the
coding process has been completed.

The System follows the following level of Testing:

 Unit testing:
It is done at the lowest level. It tests the basic unit of software, which is the smallest
testable piece of software, and is often called “unit”, “module”, or “component”
interchangeably.
Unit testing refers to tests that verify the functionality of a specific section of code,
usually at the function level. In an object-oriented environment, this is usually at the
class level, and the minimal unit tests include the constructors and destructors. These
types of tests are usually written by developers as they work on code (white-box style),
to ensure that the specific function is working as expected.

 Integration testing:
It is performed when two or more tested units are combined into a larger structure. The
test is often done on both the interfaces between the components and the larger
structure being constructed, if its quality property cannot be assessed from its
components.

Integration testing is any type of software testing that seeks to verify the interfaces
between components against a software design. Integration testing works to expose
defects in the interfaces and interaction between integrated components (modules).
Progressively larger groups of tested software components corresponding to elements
of the architectural design are integrated and tested until the software works as a
system.

 System testing:
It tends to affirm the end-to-end quality of the entire system. System test is often based
on the functional/requirement specification of the system. Non-functional quality

54
 attributes, such as reliability, security, and maintainability, are also checked. System
testing of software or hardware is testing conducted on a complete, integrated system
to evaluate the system's compliance with its specified requirements. System testing
falls within the scope of black box testing, and as such, should require no knowledge
of the inner design of the code or logic.

 Acceptance testing:
It is done when the completed system is handed over from the developers to the
customers or users. The purpose of acceptance testing is rather to give confidence that
the system is working than to find errors. Acceptance testing is done to verify if
system meets the customer specified requirements. User or customers do this testing to
determine whether to accept application.

Methodology Used for Testing:

 Black Box Testing:
Black-box testing is a method of software testing that tests the functionality of an
application as opposed to its internal structures or workings (see white-box testing).
Specific knowledge of the application's code/internal structure and programming
knowledge in general is not required. 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. The
test designer selects valid and invalid inputs and determines the correct output. There
is no knowledge of the test object's internal structure.

55
 White Box Testing:
White-box testing (also known as clear box testing, glass box testing, transparent box
testing, or structural testing) is a method of testing software that tests internal
structures or workings of an application, as opposed to its functionality (i.e. black-box
testing). In white-box testing an internal perspective of the system, as well as
programming skills, are required and used to design test cases. The tester chooses
inputs to exercise paths through the code and determine the appropriate outputs. This
is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT). 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.

56
 6.2 DESIGN OF TEST CASES AND SCENARIOS
Test cases:

Sr Test For Inputs/Actions Expected Obtained Remark

Result Result

1 Home It gives us the home Main page will be Main page Success
screen of the application displayed displayed

2 Client The client requests the The data is The Success

data to the server. displayed to the information
client on Tracking of data is
page displayed on
Tracking
page

3 About Gives the information Overview of the We can Success

about the application. application overview the
software.

4 Contact Us Gives the primary Contact information Contact Success

contact. will be provided. information
is provided.

5 Login (admin) It will go to the admin The admin can Admin Success
page on the server side login using logged in
username & successfully.
password.

6 Product entry The data is entered on the The data should be The data is Success
server side. entered so that user entered in the
accesses the data. server.

7 How it Works It gives us the working Work page will be Work page Success
screen of the application displayed displayed

57
Sr Test For Inputs/Actions Expected Obtained Remark
Result Result

8 Pricing Plans It gives us the Pricing Pricing plans page Pricing plans Success
plans screen of the will be displayed on page
application (only Cash on tracking page displayed on
Delivery) tracking page

9 New Order It will go to the new order The data should be The data is Success
page and take the order sent to the admin sent to the
from the user or. admin.

10 Product entry The data is entered on the The data should be The data is Success
server side. entered so that entered in the
admin accesses the server.
data.

11 Packages The packages History or The packages The packages Success

Data history show on the history show
Tracking page on the
Tracking
page

12 Shipment History It gives us the status of Shipment History Shipment Success

Shipment history on the on Tracking page History show
Tracking Page on Tracking
Page

13 Detail Address of It gives us the Save Detail address page Detail Success
Shipper Receiver address of the Shipper & will be displayed on address page
Receiver tracking page displayed on
tracking page

14 Chatting System Send or Receiver message Message shown Message Success

offline& Online to Server side &Client web on page shown on
Side web page

58
Validation:

The most common web application security weakness is the failure to properly validate
input from the client or environment.

Input Validation in Web Forms: Ensure user supplied data is

 Strongly typed
 Correct syntax
 Within length boundaries
 Contains only permitted characters
 Or that numbers are correctly signed and within range
Boundaries
 Is “business rule correct”
Client Side Validation:
 Validate data on the client first
 Provides better feedback to the end user
 Makes your site feel more responsive
 Always validate on server-side as well!

Validation:
 “Current” solution, useful & widely supported
 Fairly difficult to implement, though libraries help.

59
 7. CONCLUSION

Project Conclusion:-

The project training for internship undertaken at Digicraft Solution helped in not only
gaining practical experience but also to adapt the organizational environments and procedures.
This project proved good for me as it nourished my technical and design skills and thinking
not only on working on development but also on entire data flow in the system. It also
introduced me to dominant technologies across the globe in designing and developing this
system. It has not only made me able to design a project in new emerging web technologies, it
has greatly enhanced my understanding about user’s perspective of Interface of applications.

60
 Future Enhancement:

The following are some enhancements which can be done in future:

 Ability to post photos of the product

 Ability to post videos of the product
 Ability for Online Payment

61
 8. REFERENCES

Books:

1. Introduction to PHP – O’Reilly

2. Software Engineering – Roger Pressman

3. WordPress - Odrin

Website:

1. www.stackoverflow.com
2. www.wordpress.org
3. www.getbootstrap.com
4. www w3school.com
5. www.wikipedia.org

62