Electric Bike System

Electric Bike Order
1. INTRODUCTION
The project entitled “Electric Bike Order” is to be developed for maintaining the show room
activities like, customer maintenance, customer quotation generation, vehicle sales, customer dues
maintaining for the installment customers, Customer follow ups details, customer feedback from
entry and employee details. The system is efficient in generating reports which will help in the
maintenance of the showroom easily.
This project is a web based application especially the first bikes recognizable as a pedal-assist
pedaled came in the 1990s. There was an early effort in the early 1990s by Michael Kutter in
Switzerland that created a throttle less bike with power controlled by pedaling, and Yamaha
produced a similar machine in 1993.
1.1 PROBLEM DEFINITION
This Electric Bike Order project is also making a complete enterprise management via web
application. This only the first dry Fruit Shop does this type of facility. This is a one of the most
important advantage of this project. And also it has more over the advantages.
1.2 OBJECTIVE AND SCOPE OF THE PROJECT
The aim of this project is to develop an Electric Bike Order and managing system which is
easily accessible to the customers. The user and customers buy the electric bike by online mode.
The project entitled as “Online Eclectic Bike Showroom Management System”. In this, we
manage the data and details are about the process of the Sales Market. It carry the details are selling
details, buying details, billing details, inventory details, supplier data’s of customers electric bike.
Dept. of Computer Science, Gulbarga University Kalaburagi Page 1

Electric Bike Order
1.3 THEROTICAL BACKGROUND ABOUT THE PROJECT
The multi-language capability of the .NET Framework and Visual Studio .NET enables
developers to use their existing programming skills to build all types of applications and XML Web
services. The .NET framework supports new versions of Microsoft’s old favorites Visual Basic and
C++ (as VB.NET and Managed C++), but there are also a number of new additions to the family.
Visual Basic .NET has been updated to include many new and improved language features that
make it a powerful object-oriented programming language. These features include inheritance,
interfaces, and overloading, among others. Visual Basic also now supports structured except
Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language can use
the classes, objects, and components you create in Visual Basic .NET. Managed Extensions for C+
+ and attributed programming are just some of the ion handling, custom attributes and also supports
multi-threading. Enhancements made to the C++ language. Managed Extensions simplify the task
of migrating existing C++ applications to the new .NET Framework.
C# is Microsoft’s new language. It’s a C-style language that is essentially “C++ for Rapid
Application Development”. Unlike other languages, its specification is just the grammar of the
language. It has no standard library of its own, and instead has been designed with the intention of
using the .NET libraries as its own.
Active State has created Visual Perl and Visual Python, which enable .NET-aware applications to
be built in either Perl or Python. Both products can be integrated into the Visual Studio .NET
environment. Visual Perl includes support for Active State’s Perl Dev Kit.

Electric Bike Order
2. SYSTEM ANALYSIS
2.1 INTRODUCTION
The Electric Bike Order of a problem and the creation of its solution. Systems analysis is
effective when all sides of the problem are reviewed. Systems design is most effective when more
than one solution can be proposed. The plans for the care and feeding of a new system are as
important as the problems they solve.
2.2 EXISTING SYSTEM

The existing system is not automated fully as only the accounts are automated with the
accounting software. The Customer follow-ups are maintained in excel which will take more time
to search from the long lists, service details are not maintained through system so it is very difficult
to maintain the details. As the current data is maintained through ledgers and excel sheet so there is
no proper reports for facilitation of the administration of the showroom.
Disadvantages of the Existing System
• Only accounts is systemized
• Lack of reports
• Vehicle Sales & Services are maintained in excel Sheet which leads to the inaccurate
• Customer data are not maintained properly which leads the follow-ups slow.
2.3 PROPOSED SYSTEM

The proposed system Electric Bike Order overcomes the disadvantages of the existing system and
records the entire activities happening in the show room. The reports generated will enhance the
efficiency of the application. The service registration alerts and completion are recorded which will
be easy to maintain the service details.

Electric Bike Order
Advantages of the proposed System

• Entire activities of the show room are recorded through the system.
• Customer Data is maintained.
• Reports generated will be more useful for management to take the quick business decisions.
• Customer database is maintained which will be helpful for intimating the service
• Customer follow-ups are maintained which will be an added advantage of this system.
2.4 METHODOLOGY
There are various software paradigms, but we used Waterfall model (the linear sequential
model), which states that the phases are organized in a linear order. The Waterfall model suggests a
systematic, sequential approach to s/w development that begins at the system level and progresses
through analysis, design, coding, testing, and maintenance and support as shown in below fig.3.
Requirement Document & Project plan

System
Analysis System & Detailed
Design document
System Programs
Design
Test plan,
Coding
Report & manuals
Testing and
Integration Installation
Report
Installation
Operations and
Support
Fig: 2.4 Waterfall Model

Electric Bike Order
The sequence of activities performed in a software development project with the

Waterfall model is: system analysis, system design, coding, testing & integration, installation, and
maintenance. For a successful project resulting in a successful product, all phases listed in the
waterfall model must be performed. Any different ordering of the phases will result in a less
successful software product.
There are a number of project outputs in waterfall model that is produced to produce a
successful product:
 Requirement documents and project plan

 System and detailed design
 Programs (code)
 Test plan, test reports and manuals
 Installation reports
2.4.1 Limitations Of Waterfall Model:
1. The waterfall model assumes that the requirements of a system can be baseline before the design
begins. This is possible for system designed to automate an existing manual system. For our
system, (Online Counseling System) this is a new system, determining the requirement is difficult,
as the user does not even know the requirements.
2. Freezing the requirements usually requires choosing the hardware.
3. The waterfall model stipulates that the requirements be completely specified before the rest of the
development can proceed.
4. It is a document driven process that requires formal documents at the end of each phase. This
approach tends to make the process documentation-heavy and is not suitable for many applications
(interactive applications).
The waterfall model is the most widely used process model.

Electric Bike Order
2.5 FEASIBILITY STUDY

The Preliminary investigation examines project feasibility; the likelihood the system will be useful
to the organization. The main objective of the feasibility study is to test the Technical, Operational
and Economical feasibility for adding new modules and debugging old running system. All systems
are feasible if they are given unlimited resources and infinite time. There are aspects in the
feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operation Feasibility
 Economical Feasibility
2.5.1 TECHNICAL FEASIBILITY:

The technical issue usually raised during the feasibility stage of the investigation includes the
following:
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipments have the technical capacity to hold the data required to use the
new system?
 Will the proposed system provide adequate response to inquiries, regardless of the number
or location of users?
 Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data security?
2.5.2 OPERATION FEASIBILITY:
User-friendly
Customer will use the forms for their various transactions i.e. for adding new routes, viewing the
routes details. Also the Customer wants the reports to view the various transactions based on the
constraints. These forms and reports are generated as user-friendly to the Client.
Electric Bike Order
Reliability
The package wills pick-up current transactions on line. Regarding the old transactions, User will
enter them in to the system.
Security
Portability
The application will be developed using standard open source software (Except Oracle) like Java,
tomcat web server, Internet Explorer Browser etc these software will work both on Windows and
Linux o/s. Hence portability problems will not arise.
Availability
This software will be available always.
Maintainability
The system called the wheels uses the 2-tier architecture. The 1st tier is the GUI, which is said to be
front-end and the 2nd tier is the database, which uses My- Sql, which is the back-end.
The front-end can be run on different systems (clients). The database will be running at the server.
Users access these forms by using the user-ids and the passwords.
2.5.3 ECONOMICAL FEASIBILITY:
The computerized system takes care of the present existing system’s data flow and procedures
completely and should generate all the reports of the manual system besides a host of other
management reports.
It should be built as a web based application with separate web server and database server. This is
required as the activities are spread throughout the organization customer wants a centralized
database. Further some of the linked transactions take place in different locations.

Electric Bike Order
3. SYSTEM REQUIREMENT SPECIFICATION

3.1 INDRODUCTION
The inputs consist of the query to the database and the output consists of the solutions for the
query. The output also includes the user receiving the details of their accounts. In this project
the inputs will be queries as fired by the users like create an account. Now the output will be
visible when the user requests the server to get details of their own account and also accounts of
the other members.
3.2 HARDWARE REQUIREMENT SPECIFICATION:
 Processor : Dual core and above

 Main Memory : 4 RAM
 Hard Disk Drive : 500 GB
 Monitor :15’’ Preferably Color Monitor
 Keyboard : Standard Multimedia keyboard
 Mouse : Optical Mouse
SOFTWARE REQUIREMENT SPECIFICATION:

 Operating System : Windows 7 and Above
 Technology : Visual Studio 2010
 Front End : C# and Asp.net
 Back-End : SQL Server 2008R2
3.3 DISCRIPTION ABOUT THE TOOLS

FRONT END: Asp.Net and C Sharp

Electric Bike Order
ASP.NET is an open-source server-side web application framework designed for web

development to produce dynamic web pages. It was developed by Microsoft to allow
programmers to build dynamic web sites, web applications and web services
About Microsoft .NET Framework

The .NET Framework is a new computing platform that simplifies application development in the
highly distributed environment of the Internet. The Microsoft .NET Framework is a software
technology that is available with several Microsoft Windows operating systems. It includes a large
library of pre-coded solutions to common programming problems and a virtual machine that
manages the execution of programs written specifically for the framework.
The pre-coded solutions that form the framework's Base Class Library cover a large range of
programming needs in a number of areas, including user interface, data access, database
connectivity, cryptography, web application development, numeric algorithms, and network
communications. Programs written for the .NET Framework execute in a software environment

Electric Bike Order
Fig 3.3.1: An Overview Of The .net Framework
ASP.NET (Active Server Pages.NET)

ASP.NET is a programming framework built on the common language runtime that can be used
on a server to build powerful Web applications. ASP.NET offers several important advantages
over previous Web development models
 Enhanced Performance
 World-Class Tool Support
 Power and Flexibility
 Simplicity
Electric Bike Order
 Manageability
 Scalability and Availability
 Customizability and Extensibility
Language Support
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual
Basic etc.
ASP.NET Web Forms
The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing
pages), the ASP.NET Web Forms framework has been specifically designed to address a
number of key deficiencies in the previous model.
In particular, it provides:
 The ability to create and use reusable UI controls that can encapsulate common functionality
and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion (not
"spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for pages
(existing ASP code is opaque to tools).
 ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be
deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx
resources, the ASP.NET runtime parses and compiles the target file into a .NET Framework
class. This class can then be used to dynamically process incoming requests.
C#.NET:
C# is intended to be a simple, modern, general-purpose, object-oriented programming
language. C# (pronounced C Sharp) is a multi-paradigm programming language that
encompasses functional, imperative, generic, object oriented, and component oriented
programming disciplines. It was developed by Microsoft as part of the .NET initiative and later
approved as a standard by ECMA and ISO. C# is one of the 44 programming languages
supported by the .NET framework's Common Language Runtime.

Electric Bike Order
C# is an elegant and type-safe object-oriented language that enables developers to build a

variety of secure and robust applications that run on the .NET Framework. You can use C# to
create traditional Windows client applications, XML Web services, distributed components,
client-server applications, database applications, and much, much more. Visual C# provides an
advanced code editor, convenient user interface designers, integrated debugger, and many other
tools to make it easier to develop applications.
BACKEND:
SQL SERVER -2008 R2

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database. A database is a structured collection of data. Data refers to the
characteristics of people, things and events. SQL Server stores each data item in its own fields.
In SQL Server, the fields relating to a particular person, thing or event are bundled together to
form a single complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record can have the
same field name. During an SQL Server Database design project, the analysis of your
business needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fields.
2. SQL SERVER TABLES

SQL Server stores records Namespaces in the BCL relating to each other in a
table. Different tables are created for the various groups
System
of information. Related tables are grouped together to form a
System. CodeDom
database.
System. Collections
System. Diagnostics
 Class library System. Globalization

System. IO
System. Resources
System. Text
System.Text.RegularExpressions
Electric Bike Order
Fig 3.3.2 : Class Library
Microsoft .NET Framework includes a set of standard class libraries. The class library is
organized in a hierarchy of namespaces. Most of the built in APIs are part of either System.* or
Microsoft.* namespaces. It encapsulates a large number of common functions, such as file reading
and writing, graphic rendering, database interaction, and XML document manipulation, among
others. The .NET class libraries are available to all .NET languages. The .NET Framework class
library is divided into two parts: the Base Class Library and the Framework Class Library.
The Base Class Library (BCL) includes a small subset of the entire class library and is the core set
of classes that serve as the basic API of the Common Language Runtime. The classes in
mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of
the BCL. The BCL classes are available in both .NET Framework as well as its alternative
implementations including .NET Compact Framework, Microsoft Silver light and Mono.
The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire
class library that ships with .NET Framework. It includes an expanded set of libraries, including
WinForms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation,
Windows Communication Foundation among others. The FCL is much larger in scope than
standard libraries for languages like C++, and comparable in scope to the standard libraries of Java.
 Memory management
The .NET Framework CLR frees the developer from the burden of managing memory (allocating
and freeing up when done); instead it does the memory management itself. To this end, the memory
allocated to instantiations of .NET types (objects) is done contiguously from the managed heap, a
pool of memory managed by the CLR. As long as there exists a reference to an object, which might
be either a direct reference to an object or via a graph of objects, the object is considered to be in
use by the CLR. When there is no reference to an object, and it cannot be reached or used, it
becomes garbage. However, it still holds on to the memory allocated to it. .NET Framework
includes a garbage collector which runs periodically, on a separate thread from the application's
thread, that enumerates all the unusable objects and reclaims the memory allocated to them.
The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage

collector. The GC runs only when a certain amount of memory has been used or there is enough

Electric Bike Order
pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim
memory are reached, the GC runs are non-deterministic. Each .NET application has a set of roots,
which are pointers to objects on the managed heap (managed objects). These include references to
static objects and objects defined as local variables or method parameters currently in scope, as
well as objects referred to by CPU registers. When the GC runs, it pauses the application, and for
each object referred to in the root, it recursively enumerates all the objects reachable from the root
objects and marks them as reachable. It uses .NET metadata and reflection to discover the objects
encapsulated by an object, and then recursively walk them. It then enumerates all the objects on the
heap (which were initially allocated contiguously) using reflection. All objects not marked as
reachable are garbage. This is the mark phase. Since the memory held by garbage is not of any
consequence, it is considered free space. However, this leaves chunks of free space between objects
which were initially contiguous. The objects are then compacted together, by using memcpy to
copy them over to the free space to make them contiguous again.Any reference to an object
invalidated by moving the object is updated to reflect the new location by the GC. The application
is resumed after the garbage collection is over.
The GC used by .NET Framework is actually generational. Objects are assigned a generation;
newly created objects belong to Generation 0. The objects that survive a garbage collection are
tagged as Generation 1, and the Generation 1 objects that survive another collection are Generation
2 objects. The .NET Framework uses up to Generation 2 objects. Higher generation objects are
garbage collected less frequently than lower generation objects. This helps increase the efficiency
of garbage collection, as older objects tend to have a larger lifetime than newer objects. Thus, by
removing older (and thus more likely to survive a collection) objects from the scope of a collection
run, fewer objects need to be checked and compacted.
Versions
Microsoft started development on the .NET Framework in the late 1990s originally under the name
of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of .NET 1.0
were released.
The .NET Framework stack.

Electric Bike Order
Fig 3.3.3 : overview of .NET Framework
Client Application Development
Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the desktop,
enabling a user to perform a task. Client applications include applications such as word processors
and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools,
and so on. Client applications usually employ windows, menus, buttons, and other GUI elements,
and they likely access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the managed
Windows Forms control) deployed over the Internet as a Web page. This application is much like
other client applications: it is executed natively, has access to local resources, and includes
graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the Microsoft
Foundation Classes (MFC) or with a rapid application development (RAD) environment such as
Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products
into a single, consistent development environment that drastically simplifies the development of
client applications.
The Windows Forms classes contained in the .NET Framework are designed to be used for GUI
development. You can easily create command windows, buttons, menus, toolbars, and other screen
elements with the flexibility necessary to accommodate shifting business needs.

Electric Bike Order
For example, the .NET Framework provides simple properties to adjust visual attributes associated
with forms. In some cases the underlying operating system does not support changing these
attributes directly, and in these cases the .NET Framework automatically recreates the forms. This
is one of many ways in which the .NET Framework integrates the developer interface, making
coding simpler and more consistent.
Server Application Development
Server-side applications in the managed world are implemented through runtime hosts. Unmanaged
applications host the common language runtime, which allows your custom managed code to
control the behavior of the server.
This model provides you with all the features of the common language runtime and class library
while gaining the performance and scalability of the host server
Server-side managed code

Electric Bike Order
Fig3.3.4: Server-side managed code
ASP.NET is the hosting environment that enables developers to use the .NET Framework to target
Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete
architecture for developing Web sites and Internet-distributed objects using
C#.NET
The Relationship of C# to .NET
C# is a new programming language, and is significant in two respects:
 It is specifically designed and targeted for use with Microsoft's .NET Framework (a feature rich
platform for the development, deployment, and execution of distributed applications).
 It is a language based upon the modern object-oriented design methodology, and when
designing it Microsoft has been able to learn from the experience of all the other similar
languages that have been around over the 20 years or so since object-oriented principles came
to prominence
One important thing to make clear is that C# is a language in its own right. Although it is designed
to generate code that targets the .NET environment, it is not itself part of .NET. There are some
features that are supported by .NET but not by C#, and you might be surprised to learn that there
are actually features of the C# language that are not supported by .NET like Operator Overloading.
However, since the C# language is intended for use with .NET, it is important for us to have an
understanding of this Framework if we wish to develop applications in C# effectively. So, in this
chapter
The Common Language Runtime:

Central to the .NET framework is its run-time execution environment, known as the Common
Language Runtime (CLR) or the .NET runtime. Code running under the control of the CLR is
often termed managed code.

Electric Bike Order
However, before it can be executed by the CLR, any source code that we develop (in C# or some
other language) needs to be compiled. Compilation occurs in two steps in .NET:
Common Type System (CTS)

This data type problem is solved in .NET through the use of the Common Type
System(CTS). The CTS defines the predefined data types that are available in IL, so that all
languages that target the .NET framework will produce compiled code that is ultimately based on
these types.
The CTS doesn't merely specify primitive data types, but a rich hierarchy of types, which
includes well-defined points in the hierarchy at which code is permitted to define its own types.
The hierarchical structure of the Common Type System reflects the single-inheritance object-
oriented methodology of IL, and looks like this:
Fig 3.3.5 : Common Type System(CTS)
Common Language Specification (CLS)

The Common Language Specification works with the Common Type System to ensure
language interoperability. The CLS is a set of minimum standards that all compilers targeting .NET
must support. Since IL is a very rich language, writers of most compilers will prefer to restrict the

Electric Bike Order
capabilities of a given compiler to only support a subset of the facilities offered by IL and the CTS.
That is fine, as long as the compiler supports everything that is defined in the CLS.
BACK END:
1. SQL SERVER -2008 R2
information from their database. A database is a structured collection of data. Data refers to the
characteristics of people, things and events. SQL Server stores each data item in its own fields.
In SQL Server, the fields relating to a particular person, thing or event are bundled together to
form a single complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record can have the
same field name. During an SQL Server Database design project, the analysis of your
business needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fields.
2. SQL SERVER TABLES
SQL Server stores records relating to each other in a table. Different tables are created for the
various groups of information. Related tables are grouped together to form a database.
3. PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table. The Unique identifier is called the Primary Key, or simply the Key. The
primary key provides the means to distinguish one record from all other in a table. It allows the
user and the database system to identify, locate and refer to one particular record in the
database.
4. RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one table.
SQL Server makes it very easy to link the data in multiple tables. Matching an employee tothe
department in which they work is one example. This is what makes SQL Server a relational

Electric Bike Order
4. SYSTEM DESIGN
4.1 INTRODUCTION
System design produces a design specification for the new system. There are many things to be
done here. Designers must select the equipment needed to implement the system. The most creative
and challenging phase of the life cycle is system design. The term design describes a final system
and the process by which it is developed. It refers to the technical specifications that will be
applied in implementations of the candidate system. The design may be defined as “the process of
applying various techniques and principles for the purpose of defining a device, a process or a
system with sufficient details to permit its physical realization”. The designer’s goal is how the
output is to be produced and in what format. Samples of the output and input are also presented.
Second input data and database files have to be designed to meet the requirements of the proposed
output. The processing phases are handled the program Construction and Testing. Finally, details
related to justification of the system and an estimate of the impact of the candidate system on the
user and the organization are documented and evaluated by management as a step toward
implementation.

Electric Bike Order
The importance of vehicle design can be stated in a single word “Quality”. Design provides us
with representations of vehicle that can be assessed for quality. Design is the only way where we
can accurately translate a customer’s requirements into a complete vehicle product or system.
Without design we risk building an unstable system, which might fail if small changes are made. It
may as well be difficult to test, or could be one who’s quality can’t be tested. So it is an essential
phase in the development of a vehicle product.
4.2 MODULE DESCRIPTION

1. Home
Users can view all the details in the home page.
2. Register
The system has the process of registration. Every customer need to submit his details in the
form of registration. Whenever a customer registration completed automatically customer can
get a user name and password. By using that id and password customer can login into the
system.
3. Order
In payment module customer will enter their address and other details. The electric bike will be
delivered to their entered address.
4. View
The customer can read the details of the electric bike here. By clicking on the order button
user can order the electric bike of their interest.
5. Contact
Electric Bike Order
A page on a website that allows users to communicate with the site owner . A fields contain owner
name, number and email id. Through these details user can communicate with the owner.
6. About
The about us page consists of contact or lavational information about the website. It consists the
activities like, customer maintenance, vehicle sales.
7. Feedback
A feedback form it is a way to collect opinions about your website service.
4.3 DATA FLOW DIAGRAM
A data flow diagram is graphical tool used to describe and analyze movement of data through a
system. These are the central tool and the basis from which the other components are developed.
The transformation of data from input to output, through processed, may be described logically
and independently of physical components associated with the system.
These are known as the logical data flow diagrams. The physical data flow diagrams show the
actual implements and movement of data between people, departments and workstations. The
development of DFD’s is done in several levels. The lop-level diagram is often called context
diagram. It consists a single process bit, which plays vital role in studying the current system.
Customers Orders Electric Orders

Bike Store Records
Fig : 4.3 Data Flow Diagram
4.3.1 Silent Features of DFD’s:
1. The DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the dataflows
take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

Electric Bike Order
Fig : 4.3.1 Login Data Flow Diagram

4.4 DATABASE DICTIONARY
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people, things and
events.SQL Server stores each data item in its own fields. In SQl Server, the fields relating to a
particular person, thing or event are bundled together to form a single complete unit of data, called
a record (it can also be referred to as raw or an occurrence).Each record is made up of a number of
fields. No two fields in a record can have the same field’s name.
Database design is the process of producing a detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and physical storage parameters
List of SQL statements that can be issued against an Oracle database schema are:
 ALTER - Change an existing table, view or index definition (DDL)
 AUDIT - Track the changes made to a table (DDL)
 COMMENT - Add a comment to a table or column in a table (DDL)

Electric Bike Order
 COMMIT - Make all recent changes permanent (DML - transactional)
 CREATE - Create new database objects such as tables or views (DDL)
 DELETE- Delete rows from a database table (DML)
 DROP - Drop a database object such as a table, view or index (DDL)
 GRANT - Allow another user to access database objects such as tables or views (DDL)
 INSERT - Insert new data into a database table (DML)
 No AUDIT - Turn off the auditing function (DDL)
 REVOKE - Disallow a user access to database objects such as tables and views (DDL)
 ROLLBACK - Undo any recent changes to the database (DML - Transactional)
 SELECT - Retrieve data from a database table (DML)
Fig 4.4.1: Database Screenshot Showing Registration Table

Electric Bike Order
Fig 4.4.2 : Database Screenshot Showing Order Table
4.5 ER- DIAGRAM
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate the
logical structure of databases.
At first glance an entity relationship diagram looks very much like a flowchart. It is the specialized
symbols, and the meanings of those symbols, that make it unique.
o Entity: A data entity is anything real or abstract about which we want to store data.
o Relationship: A data relationship is a natural association that exists between one or more entities.
Cardinality defines the number of occurrences of one entity for a single occurrence of the related
entity.

Electric Bike Order
o Attribute: A data attribute is a characteristic common to all or most instances of a particular entity.
An attribute or combination of attributes that uniquely identifies one and only instance of an entity is
called a primary key.
o Degree of Relationship: Is the number of entities associated with the relationship.
o Connectivity and Cardinality: The connectivity of relationship describes the mapping of
associated entity instances in the relationship.
The different types of cardinality ratios are:
 One - one
 One - many
 Many - many
Advantages of Entity Relationship Diagram:
 Redundancy can be avoided

 Inconsistency can be eliminated
 Data can be Shared
 Standards can be enforced
 Security restrictions can be applied
 Integrity can be maintained
 Conflicting requirements can be balanced
 Data independence can be achieved
ER- DIAGRAM NOTATIONS:

Electric Bike Order
Fig4.5.1: ER-Diagram Notations
Fig4.5.2: ER-Diagram

Electric Bike Order
4.6 USE CASE DIAGRAMS
Fig 4.4.1 : UML DIAGRAMS
4.6.1 INTRODUCTION
The unified modeling language allows the software engineer to express an analysis model using the
modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.
USER MODEL VIEW
This view represents the system from the user’s perspective.
The analysis representation describes a usage scenario from the end-users perspective.

Electric Bike Order
STRUCTURAL MODEL VIEW
In this model the data and functionality are arrived from inside the system.
This model view models the static structures.
4.7 CLASS DIAGRAM
It represents the dynamic of behavioral as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural model
view.
Fig 4.7: Class Diagram

Electric Bike Order
5. SYSTEM IMPLEMENTATION
5.1. IMPLEMENTATION PLANNING

System implementation is a process of making newly designed system fully operational. The
system is implemented after careful testing.
The following steps have been followed in the implementation of this system.
 System conversion.
 User training.
System Conversion
The system implementation could be done in the following methods.
 Direct conversion method.
 Parallel conversion method.
The system is implemented by using the parallel conversion & fade-in method. Parallel
conversion is in which both new & old system is run parallel for a particular period. In the
phase-in method, the new system is implemented module by module.
User training
The training should include everyone associated with the implementation, use, operation or
maintenance of new system. The staff should be comfortable with the system. Coaching is a
useful way of developing people's skills and abilities, and of boosting performance. It can also
help deal with issues and challenges before they become major problems.

Electric Bike Order
5.2 FORM DESIGN/SCREEN SHOTS
Fig 5.2.1 : Screenshot Showing Home page
Fig 5.2.2 : Screenshot Showing Register page

Electric Bike Order
Fig 5.2.3 : Screenshot Showing Order page
Fig 5.2.4 : Screenshot Showing View page

Electric Bike Order
Fig 5.2.5 : Screenshot Showing Contacts page
Fig 5.2.6 : Screenshot Showing About us page

Electric Bike Order
Fig 5.2.7 : Screenshot Showing Feedback page

Electric Bike Order
5.3 CODING
using System;
using System.Collections.Generic;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Web.Configuration;
publicpartialclassUser_Userlogin : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(WebConfigurationManager.ConnectionStrings["con"].ConnectionString);
SqlCommand cmd = newSqlCommand();
SqlDataReader dr;
protectedvoid Page_Load(object sender, EventArgs e)
{
con.Open();
cmd.Connection = con;
}
protectedvoid Button1_Click(object sender, EventArgs e)
{
if (TextBox1.Text.Equals(string.Empty) || TextBox2.Text.Equals(string.Empty))
{
Label1.Visible = true;
Label1.Text = "Enetr all Fileds..";
return;
}
try
{
cmd.CommandText = "SELECT * FROM userregisterpage where usernam='" +
TextBox1.Text + "' and password ='" + TextBox2.Text + "'";
dr = cmd.ExecuteReader();
if (dr.Read())
{
Session["user"] = TextBox1.Text;
Response.Redirect("~/User/Userhome.aspx");
}
}
catch (Exception ex)
{
Label1.Text = ex.Message.ToString();
}

Electric Bike Order
}
}
SAMPLE MASTER PAGE ASP CODE
<%@PageTitle=""Language="C#"MasterPageFile="~/User/
MasterPage.master"AutoEventWireup="true"CodeFile="home.aspx.cs"Inherits="User_home"%>
<asp:ContentID="Content1"ContentPlaceHolderID="head"Runat="Server">
<styletype="text/css">
.style2
{
width: 600px;
}
.style3
{
height: 24px;
}
</style>
</asp:Content>
<asp:ContentID="Content2"ContentPlaceHolderID="ContentPlaceHolder1"Runat="Server">
<tableclass="style2">
<tr>
<tdclass="style3"colspan="2"
style="text-align: center; font-size: large; color: #FFFFFF; background-color: #FF0066;">
Welcome to Home Page
</td>
</tr>
<tr>
<tdcolspan="2"style="text-align: center"width="600">
<marquee> ONLINE ECLECTIC BIKE SHOWROOM MANAGEMENT
SYSTEM</marquee></td>
</tr>
<tr>
<tdheight="400">
</td>
<tdheight="400">
</td>
</tr>
</table>
</asp:Content>
ORDER PAGE ASP
MasterPage.master"AutoEventWireup="true"CodeFile="order.aspx.cs"Inherits="User_order"%>

Electric Bike Order
.style2
{
width: 600px;
}
.style3
{
height: 23px;
}
.style4
{
height: 23px;
width: 262px;
}
.style5
{
width: 262px;
}
</style>
</asp:Content>
<tr>
<tdcolspan="2"height="30"
style="font-size: x-large; text-align: center; color: #000099; background-color: #FFCC00">
Electric Bike Order Page
</td>
</tr>
<tr>
<tdclass="style4"height="30">
Enter Name
</td>
<asp:TextBoxID="TextBox1"runat="server"Height="30px"Width="200px"></asp:TextBox>
</td>
</tr>
<tr>
Last Name</td>
<tdheight="30">
</td>
</tr>
<tr>
Mobile Number</td>
<tdheight="30">
</td>
Electric Bike Order
</tr>
<tr>
Email Id</td>
<tdheight="30">
</td>
</tr>
<tr>
Adress</td>
<tdheight="30">
</td>
</tr>
<tr>
Pin Code</td>
<tdheight="30">
</td>
</tr>
<tr>
Bike Name
</td>
<tdheight="30">
</td>
</tr>
<tr>
Select Bike Type
</td>
<tdheight="30">
<asp:DropDownListID="DropDownList1"runat="server"Height="30px"Width="200px">
<asp:ListItem>Select Bike Type </asp:ListItem>
<asp:ListItem>Two Wheeler</asp:ListItem>
<asp:ListItem>Four Wheeler </asp:ListItem>
<asp:ListItem>TATA Nexon </asp:ListItem>
<asp:ListItem>others</asp:ListItem>
</asp:DropDownList>
<asp:LabelID="Label1"runat="server"></asp:Label>
</td>
</tr>
<tr>
</td>
<tdheight="30">
<asp:ButtonID="Button1"runat="server"Height="30px"Text="Order"
Electric Bike Order
Width="100px"onclick="Button1_Click"/>
<asp:ButtonID="Button2"runat="server"Height="30px"Text="Clear"
</td>
</tr>
<tr>
</td>
<tdheight="30">
</td>
</tr>
</table>
</asp:Content>
VIEW ASP
MasterPage.master"AutoEventWireup="true"CodeFile="view.aspx.cs"Inherits="User_view"%>
.style2
{
width: 600px;
}
</style>
</asp:Content>
<tr>
<tdcolspan="2"
style="font-weight: 700; text-align: center; font-size: x-large">
View Bike
</td>
</tr>
<tr>
<tdheight="200"width="300">
<asp:ImageID="Image6"runat="server"Height="200px"
ImageUrl="~/Images/images (9).jpg"Width="300px"/>
</td>
ImageUrl="~/Images/images.jpg"Width="300px"/>
</td>
</tr>
<tr>
Electric Bike : 1001 Price 80000</td>
Electric Bike Order
Price : 1,00000 Bike 1002</td>

</tr>
<tr>
</td>
</td>
</tr>
<tr>
</td>
</td>
</tr>
</table>
</asp:Content>
REGISTER ASP
MasterPage.master"AutoEventWireup="true"CodeFile="register.aspx.cs"Inherits="User_register"
%>
.style2
{
width: 600px;
}
</style>
</asp:Content>
<tr>
style="text-align: center; color: #FFFFFF; font-size: xx-large; background-color: #006666">
Welcome to Register Page
</td>
</tr>
<tr>
<tdheight="40">
Enter First Name</td>
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
Last Lame</td>
Electric Bike Order
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
Enter Your Adress</td>
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
</td>
<tdheight="40">
<asp:ButtonID="Button1"runat="server"Height="40px"Text="Register"
<asp:ButtonID="Button2"runat="server"Height="40px"Text="Clear "
</td>
.style2
{
width: 600px;
}
.style3
{
height: 23px;
}
.style4
{
height: 23px;
width: 262px;
}
.style5
{
width: 262px;
}
</style>
</asp:Content>
Electric Bike Order
<tr>
</td>
</tr>
<tr>
Enter Name
</td>
</td>
</tr>
<tr>
Last Name</td>
<tdheight="30">
</td>
</tr>
<tr>
Mobile Number</td>
<tdheight="30">
</td>
</tr>
<tr>
Email Id</td>
<tdheight="30">
</td>
</tr>
<tr>
Adress</td>
<tdheight="30">
</td>
</tr>
<tr>
Pin Code</td>
<tdheight="30">
</td>
Electric Bike Order
</tr>
<tr>
Bike Name
</td>
<tdheight="30">
</td>
</tr>
<tr>
Select Bike Type
</td>
<tdheight="30">
</asp:DropDownList>
</td>
</tr>
<tr>
</td>
<tdheight="30">
</td>
</tr>
<tr>
</td>
<tdheight="30">
</td>
</tr>
</table>
</asp:Content>
MasterPage.master"AutoEventWireup="true"CodeFile="register.aspx.cs"Inherits="User_register"
%>
Electric Bike Order
.style2
{
width: 600px;
}
</style>
</asp:Content>
<tr>
style="text-align: center; color: #FFFFFF; font-size: xx-large; background-color: #006666">
Welcome to Register Page
</td>
</tr>
<tr>
<tdheight="40">
Enter First Name</td>
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
Last Lame</td>
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
Enter Your Adress</td>
<tdheight="40">
</td>
</tr>
<tr>
<tdheight="40">
</td>
<tdheight="40">
<asp:ButtonID="Button1"runat="server"Height="40px"Text="Register"
<asp:ButtonID="Button2"runat="server"Height="40px"Text="Clear "
</td>
</tr>
<tr>
<tdheight="40">
</td>
Electric Bike Order
<tdheight="40">
</td>
</tr>
</table>
</asp:Content>
MasterPage.master"AutoEventWireup="true"CodeFile="home.aspx.cs"Inherits="User_home"%>
.style2
{
width: 600px;
}
.style3
{
height: 24px;
}
</style>
</asp:Content>
<tr>
<tdclass="style3"colspan="2"
style="text-align: center; font-size: large; color: #FFFFFF; background-color: #FF0066;">
Welcome to Home Page
</td>
</tr>
<tr>
<tdcolspan="2"style="text-align: center"width="600">
</tr>
<tr>
<tdheight="400">
</td>
<tdheight="400">
</td>
</tr>
</table>
</asp:Content>

Electric Bike Order
<
%@MasterLanguage="C#"AutoEventWireup="true"CodeFile="MasterPage.master.cs"Inherits="U
ser_MasterPage"%>
<!DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0

Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<htmlxmlns="http://www.w3.org/1999/xhtml">
<headrunat="server">
<title></title>
<asp:ContentPlaceHolderid="head"runat="server">
</asp:ContentPlaceHolder>
.style1
{
width: 1200px;
}
</style>
</head>
<body>
<formid="form1"runat="server">
<tablealign="center"class="style1">
<tr>
<td>
<tr>
<tdheight="40"
style="text-align: center; color: #FFFFFF; font-weight: 700; font-size: x-large; background-color:
#339966;"
width="1200">
ONLINE ECLECTIC BIKE SHOWROOM MANAGEMENT SYSTEM</td>
</tr>
<tr>
</tr>
<tr>
<asp:MenuID="Menu1"runat="server"Orientation="Horizontal"
style="font-size: x-large">
<Items>
<asp:MenuItemText="Home"Value="Home"NavigateUrl="~/User/home.aspx"></asp:MenuItem>
<asp:MenuItemText="Register"Value="Register"
NavigateUrl="~/User/register.aspx"></asp:MenuItem>
<asp:MenuItemText="Electric Bike Order "Value="Electric Bike Order "
NavigateUrl="~/User/order.aspx">
Electric Bike Order
</asp:MenuItem>
<asp:MenuItemText="View "Value="View "NavigateUrl="~/User/view.aspx"></asp:MenuItem>
<asp:MenuItemText="Contacts"Value="Contacts"
NavigateUrl="~/User/contacts.aspx"></asp:MenuItem>
<asp:MenuItemText="Logout"Value="Logout"NavigateUrl="~/User/home.aspx"></
asp:MenuItem>
<asp:MenuItemNavigateUrl="~/User/aboutus.aspx"Text="Aboutus"Value="Aboutus">
</asp:MenuItem>
</Items>
</asp:Menu>
</td>
</tr>
</table>
<tr>
<div>
<asp:ContentPlaceHolderid="ContentPlaceHolder1"runat="server">
</asp:ContentPlaceHolder>
</div> </td>
ImageUrl="~/Images/6ntuzp.gif"Width="600px"/>
</td>
</tr>
</table>
<tr>
ImageUrl="~/Images/download.jpg"Width="300px"/>
</td>
</td>
ImageUrl="~/Images/download (9).jpg"Width="300px"/>
</td>
</td>
</tr>
</table>
<tr>
<tdstyle="text-align: center">
Electric Bike Order
copyrights@2022</td>
</tr>
</table>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
</td>
</tr>
</table>
</form>
</body>
</html>
MasterPage.master"AutoEventWireup="true"CodeFile="aboutus.aspx.cs"Inherits="User_aboutus"
%>
.style2
{
width: 600px;
}
p.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
}
</style>
</asp:Content>
<tr>
<tdstyle="text-align: center; font-size: x-large; color: #FFFFFF; background-color: #6600FF">
About Us</td>
</tr>
<tr>
<tdheight="300">
<pclass="MsoNormal"style="text-align:justify;line-height:150%">
<spanstyle="font-size:14.0pt;line-height:150%;font-family:"Bookman Old
Style","serif";
mso-bidi-font-family:Arial">The project entitled “Online Eclectic Bike Showroom Management
System ” is to be developed for maintaining the show room activities like,
Electric Bike Order
customer maintenance, customer quotation generation, vehicle sales, customer

dues maintaining for the installment customers,<spanstyle="mso-spacerun:yes">
</span>vehicle service and spare parts sales, Customer follow ups details,
customer feedback from entry and employee details. The system is efficient in
generating reports which will help in the maintenance of the showroom
easily.</span><spanstyle="font-size:14.0pt;
line-height:150%;font-family:"Bookman Old Style","serif";mso-bidi-font-
family:
Helvetica;color:black;mso-themecolor:text1"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td>
</td>
</tr>
</table>
</asp:Content>
.style2
{
width: 600px;
}
.style3
{
height: 23px;
}
.style4
{
height: 23px;
width: 262px;
}
.style5
{
width: 262px;
}
</style>
</asp:Content>
<tr>
</td>
</tr>
Electric Bike Order
<tr>
Enter Name
</td>
</td>
</tr>
<tr>
Last Name</td>
<tdheight="30">
</td>
</tr>
<tr>
Mobile Number</td>
<tdheight="30">
</td>
</tr>
<tr>
Email Id</td>
<tdheight="30">
</td>
</tr>
<tr>
Adress</td>
<tdheight="30">
</td>
</tr>
<tr>
Pin Code</td>
<tdheight="30">
</td>
</tr>
<tr>
Bike Name
</td>
<tdheight="30">
</td>
Electric Bike Order
</tr>
<tr>
Select Bike Type
</td>
<tdheight="30">
</asp:DropDownList>
</td>
</tr>
<tr>
</td>
<tdheight="30">
</td>
</tr>
<tr>
</td>
<tdheight="30">
</td>
</tr>
</table>
</asp:Content>
MasterPage.master"AutoEventWireup="true"CodeFile="contacts.aspx.cs"Inherits="User_contacts"
%>
.style2
{
width: 600px;
}
.style3
{
width: 169px;
}
</style>
Electric Bike Order
</asp:Content>
<tr>
<tdcolspan="2"
style="text-align: center; font-size: x-large; color: #FFFFFF; background-color: #FF66CC">
Contacts</td>
</tr>
<tr>
Web Site Designer Name
</td>
<tdheight="40">
Your Name</td>
</tr>
<tr>
Email ID
</td>
<tdheight="40">
Email ID
</td>
</tr>
<tr>
Mobile Number
</td>
<tdheight="40">
Your Mobile Number
</td>
</tr>
<tr>
</td>
<tdheight="40">
</td>
</tr>
</table>
</asp:Content>

Electric Bike Order
6. TESTING
Testing is a process of executing a program with the intent of finding an error. Testing is
a crucial element of software quality assurance and presents ultimate review of specification,
design and coding. System Testing is an important phase. Testing represents an interesting
anomaly for the software. Thus a series of testing are performed for the proposed system before
the system is ready for user acceptance testing. A good test case is one that has a high
probability of finding an as undiscovered error. A successful test is one that uncovers an as
undiscovered error.
1. Testing Objectives
 Testing is a process of executing a program with the intent of finding an error

 A good test case is one that has a probability of finding an as yet undiscovered error
 A successful test is one that uncovers an undiscovered error
2. Testing Principles

Electric Bike Order
 All tests should be traceable to end user requirements

 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by independent third party.
 The primary objective for test case design is to derive a set of tests that has the highest
livelihood for uncovering defects in software. To accomplish this objective two different
categories of test case design techniques are used.
3. White-box Testing
White box testing focus on the program control structure. Test cases are derived to
ensure that all statements in the program have been executed at least once during testing and that
all logical conditions have been executed.
4. Black-box Testing
Black box testing is designed to validate functional requirements without regard to the
internal workings of a program. Black box testing mainly focuses on the information domain of
the software, deriving test cases by partitioning input and output in a manner that provides
through test coverage. Incorrect and missing functions, interface errors, errors in data structures,
error in functional logic are the errors falling in this category.
5. Testing Strategies
A strategy for software testing must accommodate low-level tests that are necessary to
verify that all small source code segments has been correctly implemented as well as high-level
tests that validate major system functions against customer requirements.
6. Testing Fundamentals
Testing is a process of executing program with the intent of finding error. A good test case
is one that has high probability of finding an undiscovered error. If testing is conducted
successfully it uncovers the errors in the software. Testing cannot show the absence of defects, it
can only show that software defects present.
7. Testing Information Flow

Electric Bike Order
Information flow for testing flows the pattern. Two class of input provided to test the
process. The software configuration includes a software requirements specification, a design
specification and source code. Test configuration includes test plan and test cases and test tools.
Tests are conducted and all the results are evaluated. That is test results are compared with
expected results. When erroneous data are uncovered, an error is implied and debugging
commences.
8. Unit Testing
Unit testing is essential for the verification of the code produced during the coding phase
and hence the goal is to test the internal logic of the modules. Using the detailed design
description as a guide, important paths are tested to uncover errors with in the boundary of the
modules. These
9. Integration Testing
Integration testing focuses on unit tested modules and build the program structure that is
dictated by the design phase.
10. System Testing
System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and its original objective, current specification and system
documentation. The primary concern is the compatibility of individual modules. Entire system is
working properly or not will be tested here, and specified path ODBC connection will correct or
not, and giving output or not are tested here these verifications and validations are done by giving
input values to the system and by comparing with expected output. Top-down testing
implementing here.
11. Acceptance Testing:
This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to provide the end user with
the confidence that the system is ready for use. It involves planning and execution of functional

Electric Bike Order
tests, performance tests and stress tests in order to demonstrate that the implemented system
satisfies its requirements.
11.1. Tools to special importance during acceptance testing include:
 Test coverage Analyzer – records the control paths followed for each test
Case.
 Timing Analyzer – also called a profiler, reports the time spent in various
 Regions of the code are areas to concentrate on to improve system
Performance.
 Coding standards – static analyzers and standard checkers are used to
 Inspect code for deviations from standards and guidelines.
12. Validation Testing

At the end of integration testing software ids completely assembled as a package.
Validation testing is the next stage which can be defined as successful when the software
functions in the manner reasonably expected by the customer. Reasonable expectations are
those defined in the software requirements specifications. Information contained in those
sections form a basis for validation testing approach.
13. Conditional Testing
In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on particular
condition is traced to uncover any possible errors.
14. Data Flow Testing

This type of testing selects the path of the program according to the location of definition
and use of variables. This kind of testing was used only when some local variable were declared.
The definition-use chain method was used in this type of testing. These were particularly useful
in nested statements.
15. Recovery Testing

Electric Bike Order
It is a system test that forces the system to fail in a variety of ways and verities that the recovery
is properly performed.
16. Security Testing
Attempts to verify the protection mechanisms built into the system.
17. Performance Testing
This method is designed to test runtime performance of software within the context of an
integrated system.
System Security
Introduction
The protection of computer based resources that includes hardware, software, data, procedures
and people against unauthorized use or natural
Disaster is known as System Security.
System Security can be divided into four related issues:

 Security
 Integrity
 Privacy
 Confidentiality
SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware
and operation systems to protect against deliberate or accidental damage from a defined threat.
DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.
SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate
physical security and safety against external threats such as eavesdropping and wiretapping.
PRIVACY defines the rights of the user or organizations to determine what information they are
willing to share with or accept from others and how the organization can be protected against
unwelcome, unfair or excessive dissemination of information about it.

Electric Bike Order
is a special status given to sensitive information in a database to minimize the possible invasion of
privacy. It is an attribute of information that characterizes its need for protection.
SECURITY SOFTWARE
System security refers to various validations on data in form of checks and controls to avoid the
system from failing. It is always important to ensure that only valid data is entered and only valid
operations are performed on the system. The system employees two types of checks and controls:
CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that only valid data is
entered. Client side validation saves server time and load to handle invalid data. Some checks
imposed are:
 VBScript in used to ensure those required fields are filled with suitable data only. Maximum
lengths of the fields of the forms are appropriately defined.
 Forms cannot be submitted without filling up the mandatory data so that manual mistakes of
submitting empty fields that are mandatory can be sorted out at the client side to save the server
time and load.
 Tab-indexes are set according to the need and taking into account the ease of user while
working with the system.
SERVER SIDE VALIDATION
Some checks cannot be applied at client side. Server side checks are necessary to save the system
from failing and intimating the user that some invalid operation has been performed or the
performed operation is restricted. Some of the server side checks imposed is:
 Server side constraint has been imposed to check for the validity of primary key and foreign
key. A primary key value cannot be duplicated. Any attempt to duplicate the primary value
results into a message intimating the user about those values through the forms using foreign
key can be updated only of the existing foreign key values.

Electric Bike Order
 User is intimating through appropriate messages about the successful operations or exceptions
occurring at server side.
18. RESULT/REPORTS
Name of the Test Case: Registration Page:
Test Test Case Expected Pass /

Actual Results
Case Description Results Fail
# Click on check It should tally It has tallied with the
01 Pass
button with the values values in the database
Click on check in should
It the database
ask for and has
It showed it’s correct
showing error
02 Pass
button without enter all the message for “enter all
filling
Enter few
wrong details.
It should ask for data”
It has displayed error
03 Pass
email id Email id message that “Enter
Enter Same incorrect
It should askafter
for valid
It hasEmail”
displayed error
04 Pass
User name Username exist message that “This user
twice
Click on after
It should clicking
ask for already
It has exist”.
displayed error
05 Pass
submit button enter all details. message for “enter all
without
Click on It should save all details”.
It has saved all the data
06 Pass
submit button the data and and showed the message
entering Fig all
6.18.1 :show Member Page Report “Member
Registration registered
7. SYSTEM MAINTENANCE
We have to maintain the software until the software handover to the client. Within the estimation of
cost only we have to over the project according to the user requirements. Software maintenance is
widely accepted part of SDLC now a days. It stands for all the modifications and updation done
after the delivery of software product. There are number of reasons, why modifications are
required, some of them are briefly mentioned below:
 Market Conditions - Policies, which changes over the time, such as taxation and newly
introduced constraints like, how to maintain bookkeeping, may trigger need for
modification.

Electric Bike Order
 Client Requirements - Over the time, customer may ask for new features or functions in
the software.
 Host Modifications - If any of the hardware and/or platform (such as operating system) of
the target host changes, software changes are needed to keep adaptability.
 Organization Changes - If there is any business level change at client end, such as
reduction of organization strength, acquiring another company, organization venturing into
new business, need to modify in the original software may arise.
8. CONCLUSION
Electric Bike Order is importance of electric bicycle it helps with hills, inclines, and rough
terrain, allowing for a smoother ride thus reducing stress on joints. You can also ride with greater
power and precision than a regular bike. And it gets people cycling who may not otherwise ride a
traditional bike because of physical aches and pains.

Electric Bike Order
9. REFERENCES
[1] Anurag M. Lulhe, Tanuja N.Oate “A Technology Review Paper for Drives used in
Electrical Vehicle (EV) & Hybrid Electrical Vehicles (HEV)”. IEEE Conference, 2012

Electric Bike Order
[2] Hsu, SuHau., Hsu, D. W., Fu, L. C., & Hsu, Y. P. (2004, June). Novel integrated
management system design of electric motorcycles. In American Control Conference,
2004.Proceedings of the 2004.IEEE.
[3] Huang, K. David.,&Tzeng, Sheng Chung. (2004). A new parallel-type hybrid electric-
vehicle. Applied Energy, 79(1).
[4] Lukic, S., Mulhall, P., &Emadi, A. (2008). Energy autonomous solar/battery auto rickshaw.
Journal of Asian Electric Vehicles.
[5] S. I. Brand, N. Ertugrul, W. L. Soong, “Investigation of an Electric Assisted Bicycle and

Determination of Performance.

Electric Bike System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Electric Bike System

Uploaded by

Copyright:

Available Formats

Electric Bike Order

1.1 PROBLEM DEFINITION

1.2 OBJECTIVE AND SCOPE OF THE PROJECT

Dept. of Computer Science, Gulbarga University Kalaburagi Page 1

1.3 THEROTICAL BACKGROUND ABOUT THE PROJECT

Dept. of Computer Science, Gulbarga University Kalaburagi Page 2

2.2 EXISTING SYSTEM

Disadvantages of the Existing System

• Only accounts is systemized

2.3 PROPOSED SYSTEM

Dept. of Computer Science, Gulbarga University Kalaburagi Page 3

Advantages of the proposed System

Requirement Document & Project plan

Fig: 2.4 Waterfall Model

Dept. of Computer Science, Gulbarga University Kalaburagi Page 4

The sequence of activities performed in a software development project with the

 Requirement documents and project plan

2.4.1 Limitations Of Waterfall Model:

Dept. of Computer Science, Gulbarga University Kalaburagi Page 5

2.5 FEASIBILITY STUDY

2.5.1 TECHNICAL FEASIBILITY:

2.5.2 OPERATION FEASIBILITY:

2.5.3 ECONOMICAL FEASIBILITY:

Dept. of Computer Science, Gulbarga University Kalaburagi Page 7

3. SYSTEM REQUIREMENT SPECIFICATION

 Processor : Dual core and above

SOFTWARE REQUIREMENT SPECIFICATION:

3.3 DISCRIPTION ABOUT THE TOOLS

Dept. of Computer Science, Gulbarga University Kalaburagi Page 8

ASP.NET is an open-source server-side web application framework designed for web

About Microsoft .NET Framework

Dept. of Computer Science, Gulbarga University Kalaburagi Page 9

Fig 3.3.1: An Overview Of The .net Framework

ASP.NET (Active Server Pages.NET)

ASP.NET Web Forms

Dept. of Computer Science, Gulbarga University Kalaburagi Page 11

C# is an elegant and type-safe object-oriented language that enables developers to build a

SQL SERVER -2008 R2

2. SQL SERVER TABLES

 Class library System. Globalization

Fig 3.3.2 : Class Library

The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage

Dept. of Computer Science, Gulbarga University Kalaburagi Page 13

Dept. of Computer Science, Gulbarga University Kalaburagi Page 14

Fig 3.3.3 : overview of .NET Framework

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

Dept. of Computer Science, Gulbarga University Kalaburagi Page 15

Server Application Development

Server-side managed code

Dept. of Computer Science, Gulbarga University Kalaburagi Page 16

Fig3.3.4: Server-side managed code

C# is a new programming language, and is significant in two respects:

The Common Language Runtime:

Dept. of Computer Science, Gulbarga University Kalaburagi Page 17

Common Type System (CTS)

Fig 3.3.5 : Common Type System(CTS)

Common Language Specification (CLS)

Dept. of Computer Science, Gulbarga University Kalaburagi Page 18

Dept. of Computer Science, Gulbarga University Kalaburagi Page 19

Dept. of Computer Science, Gulbarga University Kalaburagi Page 20

4.2 MODULE DESCRIPTION