Ashoka Diesel Spares

Ashoka Diesel Spares
1

TABLE OF CONTENTS
1. Organization Overview ............................................................................................................ 3
2. Profile of Problem ....................................................................................................................... 5
3. Existing Systems ......................................................................................................................... 6
3.1 Introduction ........................................................................................................................... 6
3.2 Existing Software .................................................................................................................. 6
3.3 DFD for Present System ........................................................................................................ 6
4. Problem Analysis ........................................................................................................................ 7
4.1 Product Definition ................................................................................................................. 7
4.2 Feasibility Analysis ............................................................................................................... 7
4.3 Project Plan ........................................................................................................................... 8
5. Software Requirements Analysis .............................................................................................. 10
5.1 Introduction ......................................................................................................................... 10
5.2 General Descriptions ........................................................................................................... 11
5.3 Specific Requirements......................................................................................................... 13
6 Designs ....................................................................................................................................... 18
6.1 System Design ..................................................................................................................... 18
6.2 Design notations .................................................................................................................. 24
6.3 Detailed Design ................................................................................................................... 27
6.4 Flowcharts ........................................................................................................................... 33
7. Testing....................................................................................................................................... 36
7.1 Functional Testing: .............................................................................................................. 36
7.2 Structural Testing: ............................................................................................................... 36
7.3 Level of Testing .................................................................................................................. 37
6.4 Test cases of the project ...................................................................................................... 38
8 Implementation .......................................................................................................................... 40
8.1 Implementation of the project ............................................................................................. 40
8.2 Conversion Plan .................................................................................................................. 41
8.3 Post Implementation and Software Maintenance ................................................................ 41

2
9 Project Legacy ........................................................................................................................... 44
9.1 Current Status of the Project ............................................................................................... 44
9.2 Remaining Areas of Concern .............................................................................................. 44
9.3 Technical and Managerial Lessons Learnt .......................................................................... 44
10 User Manual ............................................................................................................................. 46
11 Bibliography ............................................................................................................................ 55

3
1. ORGANIZATION OVERVIEW

ThinkNEXT Technologies Private Limited (An ISO 9001:2008 Certified Company), is
emerging as most innovative company in Education Domain in India. The Management of
ThinkNEXT Technologies Private Limited has wide experience more than nine years in
education domain. Over the years, we have worked very closely with Universities, Group of
Colleges and other Institutions. We have wide experience working with eminent Educationists,
Managements, Directors, Principals, Head of Departments, other Staff Members, Parents and
students. Therefore we do not sell only software Modules but an innovative system which has
more importance than just ERP software modules. Today Smart Campus solutions are a need of
hour for every University/Group of Colleges or an Institution to make edge over others and
maintain a lead over their competitors. Our Research and Development team is committed to
make your institute(s) to maintain lead over their competitors.

No of Employees: 45

Head-Office: ThinkNEXT Technologies Private Limited USA

Major Projects developed by ThinkNext:

4
Client Description
Mr Ashok Gaba
Ashoka Diesel spares was founded in the year 1974 under the leadership of Shri Ashok
Gaba with a vision of serving society by supplying superior quality products that provide high
value for money for customers. From a humble beginning as a small manufacturing set up for
manufacture of Diesel Generating Set & Diesel Pumpsets to a spectacular growth is the saga of
the Group. Since our inception in the year 1962, the Company in a Span of 23 years has turned
into a 12-Industries-Group with continuous multifold growth in its Sales turnover. The Company
diversified its core business of Diesel Engine, Gensets, & Pump Sets to manufacturing and
supply of Carbon Steel Castings and Alloy Steel Castings for general engineering purposes, PVC
Pipes, Hand Pumps, Oxygen Gas, Water Storage Tank, A. C. Pressure Pipe. Commitment to
customer satisfaction is achieved by pursuit of excellence in all aspects with high technical skills,
communication and team work. We not only believe in Excellence but also want our Group to be
synonymous with it. We have continuously strived to bring in the best technology into our
products. The Group's vision - "Customers having faith in Ashoka products are our most
valuable asset. We strive to be reliable partner to our customers, serving through our multi-
products network". Our vision can be achieved by being obsessive with the quality of the
products and thus earn the loyalty of the customers.

The Group has a dedicated team for design, manufacture and marketing which ensures
impeccable focus and faster response to customer's needs.

5
2. PROFILE OF PROBLEM

Ashoka Diesel Spares (ADS) is a service based product, which provides services to the
customer who wants to access it. A website through which the customer can see the portal which
displays all the products the company is dealing with. A portal through which customer can place
their order, and on owners site he can handle the order.
Ashoka Diesel Spares is a service based website which main purpose is to give
information and details of all the Diesel spares parts they are dealing with. Ashoka Diesel Spares
provides a portal which displays all the products the company is dealing with.
It provides the platform for their customers to check the availability of the products, their
size, price and every detail and place his/her orders online, where the customer order is handled
by admin.
Here the customer can register by creating a username and password and login to his/her
account and place his/her order in secure manner and apart placing order if customer is not
satisfied with the services or want to provide the positive feedback he/she can leave the feedback
message.

6
3. EXISTING SYSTEMS
3.1 Introduction

ADS Company is currently handling all its inventory (products), transactions (orders)
manually in a registers. Before it was not a problem to handle such small inventory and its
transactions manually, but as the company started to thrive and their customers started to order in
large scale and their inventory stock increased, it became a tedious task to maintain all the
records manually. Problems started to pile up. The response speed of manual system is very
slow and a tedious task to perform. Inaccuracy, inadaptability and exposure to environment
were another problems faced. Therefore to overcome all this problems and make the processing
speed and the overall system better, and make the people aware of ADS Company and its
products, we came up with the idea to make this system automated.

3.2 Existing Software
There is no current existing software for ads, all the transactions and inventory are
handled manually.
3.3 DFD for Present System
There is no current existing software for ads, all the transactions and inventory are handled manually. So
there is no DFD.

7
4. PROBLEM ANALYSIS
4.1 Product Definition
ADS deal in trading /supplying of spare parts of diesel
generators. The client work with special vigilance while delivering the product to their esteemed
clients and prospective customers also. This project we are designing by using HTML, CSS and
Javascript and Jquery as client side makeup and scripting language and Asp.net as server side
scripting language. This is using MSSQL as database. Thus it is a network based RDBMS
product.

4.2 Feasibility Analysis
Feasibility study is the process of determination of whether or not a project is worth doing.
Feasibility analysis is completed in four phases.
Technical Feasibility.
Economical Feasibility.
Operational Feasibility.
Legal Feasibility.

4.2.1 Technical Feasibility
Technical feasibility determines whether the work for the project can be done
with the existing equipment, software technology and available personnel. Technical
feasibility is concerned with specifying equipment and software technology that will
satisfy the end users requirements. when we gathered the requirement from client, our
team has to decide on the technical prospects of this project, after long discussion and
analyzing the various facets of this project we came to the conclusion that project is
technically feasible with todays technology in development field. Since our team is
familiar with .Net framework and SQLSERVER2012 we had chosen .NET framework as
frontend using ASP.NET and SQLSERVER2012 as database server.

8
4.2.2 Economical Feasibility
Economic feasibility determines whether there are sufficient benefits in creating
to make the cost acceptable, or is the cost of the system too high. This signifies cost-
benefit analysis and savings. On the behalf of the cost-benefits analysis, the proposed
system is feasible and is economical regarding its pre-assumed cost for making a system.

4.2.3 Operational Feasibility
Operational feasibility determines the way to make the website easy to use, user-
friendly and reliable. This website is operationally feasible because we are giving too
easy interface for the user so that all users can easily use all the feature of this website.

4.2.4 Legal Feasibility
To host the Ashoka Diesel spares website there are not any legal constraint and
this idea doesnt conflict with others existing idea. Owner of this website also has the
copyright of this website. Also all the data about Diesel spares used in this website are
authentic.

4.3 Project Plan

S
N
Task Start date Estimat
ed Date
End Date Task Completed
Before estimated
date
Time
Left
1 Requirement
Analysis
30/1/2014 4 3/2/2014 On time 0
2 Feasibility Study 4/2/2014 2 6/2/2014 On time 0
3 Data Base Design 7/2/2014 9 16/2/2014 On time 0
4 Mock Ups 17/2/2014 3 20/2/2014 On time 0
5 Website Design 21/2/2014 25 14/3/2014 Two more days 0
6 Admin panel Design 21/2/2014 3 24/2/2014 On time 0
7 Home page Design 25/2/2014 4 1/3/2014 On time 0

9
8 User panel Design 2/3/2014 4 6/3/2014 On time 0
9 Shop Now Design 7/3/2014 3 10/3/2014 On time 0
10 Check out page 11/3/2014 2 13/3/2014 On time 0
11 Feedback and About
us
14/3/2014 3 17/3/2014 On time 0
12 Store procedures 18/3/2014 5 23/3/2014 Two more days 0
13 Filtering Issues 24/3/2014 5 29/3/2014 On time 0
14 Data Base Queries 30/3/2014 6 6/4/2014 One more day 0
15 Classes and
properties of 3-tire
layers
7/4/2014 4 11/4/2014 On time 0
16 Coding 12/4/2014 10 22/4/2014 One more day 0
17 Rectification 23/4/2014 2 25/4/2014 On time 0
18 Testing 26/4/2014 3 29/4/2014 On time 0

10
5. SOFTWARE REQUIREMENTS ANALYSIS
5.1 Introduction
5.1.1 Purpose
by admin.
message.
5.1.2 Scope
Ashoka Diesel Spares is a web based applications that can be used anywhere with internet
connection. This website facilitate following:
Provides Details and description of all the products the company is dealing with.
Customer can place his/her orders.
Customer can give the feedback about products and the services.

5.1.2 Intended Audience
This web based application is service based website which is open to all the customers
who is in need of the Diesel spares parts .Every customer who deals with and is need of the parts
and product can come to the website and get the details and place his/her orders.

11
5.2 General Descriptions
5.2.1 Product Description
by admin.
message.
5.2.2 Product Functions
Ashoka Diesel Spares provides you with following facilities:
a) Create account

Any interested people can create his own account in this website and can access the entire
authorized module using his/her personal account.

b) View Products
Customer can view the products and its detailed information.

c) Buy products
After successful login into the system user can place order.

d) Give feedback
The user can give the feedback about the services and the products.

e) Product Management
Admin can manage the products and stocks by adding new products to the website, and edit and
update them.

f) Check new orders
Admin can check the orders placed by the customers and handle them.

12
g) Check Messages
Admin can check the feedback given by the customers.

g) Manage Employees
Admin can add, update, and delete the details of the employee.

5.2.3 User Characteristics
There are two type of users associated with this website.
a) Administrator

This is the super user of this website and has full control over the website. He/she could
manage database of website, update the website as per the new changes ,the new products in the
company ,the change in price He/she also make the entry and update all products, price and
discount if any. All in all he/she has authority and responsibility to make the website functional.
b) Public user
Public users are the bond of the success of this project. Public users has following rights
i. Login into website
ii. Check the available products and their details.
iii. Place the order.
iv. Give feed back

5.2.4 General Constraints

i. This is web based application so the public who want to access this website should have internet access.
ii. This website has built on .NET framework so it should be hosted on IIS web server and should use
SQLSERVER database.
iii. Without proper login no one could access the websites feature and no one can place order.

13
5.2.5 Assumptions

Following assumptions were made while developing the project.
i. 24*7 uptime of web server.
ii. 24*7 uptime of database server
iii. No limitation of web space
iv. Trained and sufficient manpower to handle the project.

5.2.6 Dependencies

i. Since it is web based application, performance of this application depends a lot on good
bandwidth internet.
ii. Reliability of this website depend on the reliability of web server on which we will host and
the database server which this web site will use.
iii. Regular and perfect update of website as per the requirement depends on the size of
development team and technical expertise the development team has.
iv. Good performance of this website depends on well normalized database.
v. Perfect solution of the objective of the website is dependent on good analysis of requirement
and design (flowcharts, DFD, Use Case diagram) of the system before actual development of the
website.

5.3 Specific Requirements

5.3.1 Functional Requirements
a) Create account /Register
Any interested people can create his own account in this website and can access the entire
authorized module using his/her personal account.
Input User will give first name, last name, email and password to create the account
Process System will check that user is already existing or not. If already exist it will
deny to create account with duplicate user id. If not exist it will create new user.
Output The database will have either a new user or send deny message.

14

b) Login using local account
User could login into the system using their own account id and password for the system.
Input User give user id and password and click login button
Process Request will send to database server to check whether given id and password
match with user id and password in database or not.
Output If user is valid a new session for user will be created and user will be redirected
to home page else he will get invalid user information message from system.

c) View Products
Input User provide the various filter criteria to see the products
Process Search will be done in issue table based on filter criteria given by user.
Output If any issue find then that will be rendered on page else page will be rendered
without issues.

d) Place an order
After successful login into the system user can place the order after viewing the details of the
same.
Input User will go to the shop page and place the order
Process Order will be stored in the database with orderid, customerid,productid.
Output Order details will be reflected in the admin page.

e) Give feedback
User can give the feedback about the products and the services.
Input User goes to the feedback page and leave the message
Process Message will be stored in database with customer id.

15
Output Message will be reflected in the admin side.

f) Product Management:
Admin of this website will make the entry of new products:
Input Administrator give all the details of products on add products page and click
save.
Process Product details will be stored in the database with each product with unique.
productid.
Output After successful insertion a message will be displayed

g) View stock
Input Admin will click on view stock page the current stock will be avaliable
Process Search will be done in database and the data from product table will be
displayed
Output A gridview of all the stock will be displayed

h) Update Stock
Input Admin will give all the new details of the products in stock page itself
Process The changes will be stored in the database.
Output After successful updating a message will be displayed.

i) View Order details
Input Admin will check for the new orders in the order pending page
Process Search will be done in order details page.
Output After successful search the order details will be displayed in the grid view.

j) View Customer Details
Administrator can view the details of any customer.

16
Input Admin will check for the details of the customer
Process Search in the database for the customer table will be done
Output After successful search the customer details will be displayed in the grid view.

k) Add Employee
Admin of this website can make entry of the details of the employee working :
Input Administrator give all the details of employee on add employee page and click
save.
Process Employee details will be stored in the database with each employee with unique
employeeID.
Output After successful insertion a message will be displayed

l) View Customers Feedback
Administrator can view the feedback of the customers and improve their service in better ways.
Input Administrator can go to the message page
Process Message given by the customers will be searched in the database
Output After successful Search a message will be displayed to the administrator.

5.3.2 Non Functional Requirements

a) 24*7 hours up time of web server and database server for reliable service.
b) Good availability of internet service on end users side to access this website.
c) Good performance rate of web server and database server for better response time and
performance.
d) Implementation of strong security system in web server and database server to make the
website more secure from hacker.
e) Use of 3 tier architecture to make the development easy, fast and systematic.

17
5.3.3 Technical Requirement
After long discussion between our development team we decided to work on .NET
framework as all team members are familiar with this technology. After long discussion we
categorize the technical requirement into development tool:
SN Development tool Description
1 Visual Studio 2012 An advanced integrated development environment
by Microsoft
2 . .NET Framework 4.5 A development platform created by Microsoft
3 SQL Server 2012 Database application for effectively managing our
database

4 HTML 5 Advanced Hyper Text Markup Language that deals
with displaying information.
5 . JavaScript Netscape-developed object scripting language used
for client side scripting
7 CSS3 Cascading style sheet used to give the design of
various object of website
8 JQuery A framework with collection of JavaScript code to
give various effect as well as to do various task.
9 C# An object oriented language used to code the
actions.

18
6 DESIGNS
Software Design is a process of problem solving and planning for a software solution.
After the purpose and specifications of the software is determined, software developers will
design or employ designers to develop a plan for a solution.
Design is a meaningful engineering representation of something that is to be built. The
design process translates requirements into a representation of the software that can be accessed
for quality before code generation begins.

6.1 System 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.

6.1.1 Logical design
The logical design of a system pertains to an abstract representation of the data flows,
inputs and outputs of the system. This is often conducted via modeling, using an over-abstract
(and sometimes graphical) model of the actual system. In the context of systems design are
included. Logical design includes ER Diagrams i.e. Entity Relationship Diagrams.

19

Figure 1 E-R Diagram

6.1.2 Physical design

The physical design relates to the actual input and output processes of the system. This is
laid down in terms of how data is input into a system, how it is verified/authenticated , how it is
processed, and how it is displayed as In Physical design; the following requirements about the
system are decided.

Input requirement,
Output requirements,
Storage requirements,
Processing Requirements,

20
System control and backup or recovery.
Put another way, the physical portion of systems design can generally be broken down
into three sub-tasks:
User Interface Design
Data Design
Process Design
Data Flow Diagrams (DFD)
The DFD is also known as the Bubble Chart. It is a simple graphical formalism that can
be used to represent a system in terms of the input data to the system. Various processes are
being carried out on these data, and the output data is generated by the system. The main reason
behind DFD technique is that DFD is a very simple formalism-it is simple to understand and use.
A DFD uses a very limited number of primitive signs to represent the functions performed by a
system and the data flow among these functions. Starting with a set of high-level functions that a
system performs, a DFD model hierarchically represents various sub functions. The five different
types of primitive symbols used for constructing DFDs are:

Process

A function is represented using a circle. This sign is called a process or a bubble. Bubbles are
annotated with the names of the corresponding functions.

External Entity

An external entity such as a librarian, a library member, etc. is represented by a rectangle.
The external entities are essentially those physical entities which is external to the software
system that interact with the system by inputting data to the system or by consuming the data
produced by the system. In addition to the human users, the external entity symbols can be used
to represent external hardware and software such as application software.

Data Flow

21
A directed arc or an arrow is used as a data flow sign. A data flow sign represents the data
flow occurring between two processes, or between an external entity and a process, in the
direction of the data flow arrow. Data flow signs are usually annotated with the corresponding
data names.

Data Store

A data store represents a logical file. It is represented using two parallel lines. A logical file
can represent either a data store sign, which can represent either a data structure, or a physical
file on disk. Each data store is connected to a process by means of a data flow sign. The direction
of the data flow arrow shows whether data is being read from or written into a data store. A
arrow flowing in or out of a data store implicitly represents the entire data of the data store and
hence connecting to a data store need not be annotated with the name of the corresponding data
items.
Output Sign

The output sign is used when a hard copy is produced and the user of the copies cannot
be clearly specified or there are several users of the output.

0- level DFD

Figure: Complete Application

22

1-Level DFD for Administrator

Fig: Level 1 DFD for Administrator

23
1-Level DFD for Public User

Fig: Level I DFD for public user

24
6.2 Design notations
We have two Types of design Notations, dynamic and static notations.
1. Dynamic Notations: in dynamic we have
Data Flow Diagrams
State transition diagrams (STDs).
State charts.
Structure diagrams
6.2.1Structure diagrams:
Database Tables Design:

Product table:

25
Customer table:

Employee table:

Feedback table:

26
Supplier table:

Shipper table:

Categories table:

27
Admin Login table:

6.3 Detailed Design
Detailed design of the system is the last design activity before implementation begins.
The hardest design problems must be addressed by the detailed design or the design is not
complete. The detailed design is still an abstraction as compared to source code, but should be
detailed enough to ensure that translation to source is a precise mapping instead of a rough
interpretation.

The detailed design should represent the system design in a variety of views where each
view uses a different modeling technique. By using a variety of views, different parts of the
system can be made clearer by different views. Some views are better at elaborating a systems
states whereas other views are better at showing how data flows within the system. Other views
are better at showing how different system entities relate to each through class taxonomies for
systems that are designed using an object-oriented approach.
When most people talk about detailed design, they are referring to a process known as
top-down design. In short, when you think about the problem you are trying to solve, you start at
the highest level and then work yourself into the details. This approach works very well when
you have an overall structure you want your application to live within. At the macro level you
are considering how many machines will be needed to host your application, which existing
services you will need to use, etc. As you dive deeper, you are looking at use cases (or user
stories if you prefer that terminology), and error handling (use cases have both normal and error
condition paths to worry about). As you go even further into the details, you are looking at your
algorithm, state transitions, logical sequence, and how internal parts of the code work together.

28
The classic top-down approach to detailed design is what is taught with the "waterfall"
methodology, IEEE process guides, UML vendors, universities, and CMMI among others. In
many of these heavy processes they have you writing two design documents. One is the overall
architectural diagram (the top level design). In many cases it is the only approach to design many
people know. It is a very logical and methodical approach to breaking down a software problem.
The main advantage is that you have identified what the critical sections are likely going
to be. If you will need to start working on how your software will be using another existing
service, you have compiled your list of integration points. You would be able to start talks with
the owners of those services to plan your integration along with how to handle unexpected
events.
Detailed Diagram Consists of Class diagram:
6.3.1 Class Diagram
A class diagram is a superset of an inheritance model in that it models the class
taxonomy; however, it also models relationships between the various class entities like a
semantic-model.
A class diagram is a type of UML (Unified Modelling Language) diagram. A class diagram
describes the various entities that will be used to construct the functioning system. Describing
object (an object is an instantiated class much like a process is an instantiated program) attributes
and operations allows the developer to begin to logically apportion data and functions in a
fashion that is natural to human beings. Participating objects are defined via their classes (or
templates). Their capabilities, their roles, and their associations / relationships are specified. By
specifying the classes from which objects are created, a developer is essentially adding parts to a
kit from which a fully functional system will be produced. This type of model is iterative. It may
start with classes that only have names. As the developer's understanding of the problem
improves, the developer can begin to add the necessary attributes and operations that the classes
will need. In this way, the solution system is systematically developed increment by increment.

29
Class diagram of DAL (data access layer):

30
Class diagram of BO(Business Object):

31
Class Diagram of DAL(Data Access Layer):

32
6.3.2 Database Relationship Diagram:

33
6.4 Flowcharts
A flowchart is a diagrammatic representation that illustrates the sequence of operation to
be performed to get the solution of a problem. A flowchart can be used to define and analyze
processes, build a step by step picture of the process for analysis, discussion or communication.
Flowcharts are a better way to communicating the logic of a system to all concerned. With the
help of flowchart, problem can be analyzed in a more effective way.

Figure 2 Admin Module Flow chart

34

Figure 3 Login User Flow chart

35

Figure: Shop Now Flowchart

36
7. TESTING
Testing is the practice of making judgments regarding the extent to which the system
meets, exceeds, or fails to meet stated objective. Testing is about verifying that what was
specified is what was delivered. It verifies that the product meets the functional, performance,
design and implementation requirement as per stated at the initial stage of the product. In
general, Testing is finding out how well something works.
Testing is divided into two phase:-
Functional Testing (Black Box Testing)
Structural Testing (white Box Testing)

7.1 Functional Testing:
Functional testing is to test the functionality of the software application. It helps in checking
whether software application is meeting the user expectations. In functionality testing, one does
not have to get into the code of the product. He will only check the front end interface as if any
user will use it, it shall perform all task and should not lag in any functionality. In other words
functional Testing is also called as Black Box Testing. Black box testing Ashoka Diesel spares
has given us the result that how user-friendly the website is and if any functionality is lagging
behind.
Functionality Test Involves Following Steps:-
The identification of functions that the software is expected to perform.
Determination of output based on functions specification.
Execution of test cases
Comparison of actual and expected output

7.2 Structural Testing:
Structural Testing is the testing of the structure of the system, it is often referred to as White
Box testing or Glass Box Testing. In structural testing the tester should know the implementation
of code. The test cases are decided on the internal logic of the program. During structural testing
the tester is concentrating on how the software does it. For example, a structural technique wants

37
to know how loops in the software are working. White Box Testing can be applied at the unit,
integration and the system levels of the software testing process. It is usually done at the unit
level. In Ashoka Diesel spares individual piece of code is tested like and is implemented on to
website.
7.3 Level of Testing

7.3.1 Unit Testing
In unit testing individual code of program is tested to determine, if they are fit for use in
program. The main purpose of unit testing is to isolate each part of program and to test if the
individual parts are correct. Unit testing allow the programmer to restructure the code later and
make sure that the module still work correctly.

7.3.2 Integration testing
When two or more different module is joined together, we need to verify if the produced
result satisfy the original functionality or not. Integration testing will start after the completion of
unit testing. Integrating testing will find the bugs when modules are integrated; main purpose of
integration testing is to find the performance and functional level bugs. When the modules are
not integrated they perform as per requirement but when different modules are integrated they
create issue and those issues affect functionality and performance.
Different type of integration testing is
a) Big Bang

This approach is used to find the bugs when all the modules are fully developed, integrated and
are interacting with one another to form complete software.
b) The Top-Down Approach

In this integrated approach all top level modules are tested first and then their sub modules serial
wise tested to check if there are any bugs left.
c) The Bottoms-Up Approach

38
In this approach the lowest level component are tested first and then when they satisfy the
requirement higher level modules are tested in hierarchy and step by step.

7.3.3 System Testing

This testing is done to note the behavior of whole system/software. Its main focus is to
verify that the customer requirement are met and fulfilled. System testing falls under category of
Black-box Testing. System testing is done after Integration Testing is complete. For this type of
testing do not require knowledge of internal design, structure or code.
7.3.4 Acceptance testing
Acceptance testing is the final stage of testing that is performed on a system by the user
or customer
.
7.3.5 Regression Testing
If there is any change in the code of software, testing needs to be done to ensure that
piece of code is working fine and there are no issues with the recently modified code. This is
known as regression testing. Regression testing plays an important role in a scenario where a
change has been made into a previously tested software code.

7.4 Test cases of the project

Test
case
ID
Module Description Expected result Actual result Remarks
Tc-2 Sign Up Leave name field blank and
click button
Please fill up the
blank fields
Please fill up
the blank
fields
pass

39

7.4.1 Functional testing
Test
case ID
Description Expected result Actual result Remarks
Tc-F-1 Click the shop now
button

Will redirect to login
page if not logged in
before

Will redirect to
login page if not
logged in before

pass

7.4.2Compatibility Testing
Test case ID Module Description Expected result Actual result Remarks
TC-C-1

Login

Run Application
on Mozilla
Check For
Validations

Validations
should work on
empty
textboxes
Validators
Worked

Pass

TC-
C2

Mozilla
Login
Check for
Prompt
Messages
Prompt will
open as alert
messages
Prompt
message
appeared as
message box
pass

40
8. IMPLEMENTATION

Implementation is a process, which is used for converting a new system into an
operational one. Implementation of project is to replace a existing/manual system. The new
system may be totally new; replacing an existing manual or automated system, or it may a major
modification to an existing system. In the either case, proper implementation is essential to
provide a reliable system to meet organization requirements.
Implementation is the process of having systems personal check out and put new
equipment to use, train users, install the new application and construct any files of data needed to
use it. This phase is less creative than system design. Depending on the size of the organization
that will be involve in using the application and the risk involved in its use, system developer
may choose to test the operation only one area of the firm with only one or two persons.
Sometimes, they will run both old and new system in parallel way to compare the results. If new
system fulfilling the required business requirement then developer team stop using old systems
and start using the new one.
The implementation of web based project has some extra steps at the time of implementation.
We need to configure the systems according the requirement of the project.
8.1 Implementation of the project
For the implementation of Ashoka Diesel Spares we followed the following steps:
A. Configuring the server
i. First client take the space in Amazon cloud server and give us the access authentication
ii. Installation of windows server 2003.
iii. Installation of security software.
iv. Installation of the IIS server and configuring it
v. Installation of Microsoft SQLSERVER 2012

B. Configuring website
i. Purchasing of an IP address and assigning a unique URL to it.
ii. Linking the Welcome page of the application with the IP

41
iii. Uploading the precompiled copy of the project on the ISS server.

8.2 Conversion Plan
The conversion plan describes the strategies involved in converting data from an existing
system to another hardware or software environment. It is appropriate to reexamine the original
systems functional requirements for the condition of the system before conversion to determine
whether the original requirements are still fulfilled or not.
Since Ashoka Diesel spares is a totally new website which is not replacing any existing system
hence no conversion plan was applied.

8.3 Post Implementation and Software Maintenance
In order for software to remain useful in its environment it may be necessary to carry out
a wide range of maintenance activities upon it. There are bugs to fix, enhancement to add and
optimization to make, changes has to be done in older version to make it applicable for current
business requirements. There are four type of maintenance strategy: corrective, adaptive,
perfective, preventive.

8.3.1 Corrective Maintenance
Changes necessitated by actual errors (defects or residual bugs) in a system are termed
as corrective maintenance. These defects manifest themselves when the system does not operate
as it was designed or advertised to do. A defect or bug can result from design errors, logic errors
and syntax errors.
After development of each and every module we hosted that module and put into the live
use of that module and based on the live testing and feedback from the real users(public) we
made changes(correct the system). In this maintenance, after receiving each and every feedback
our team seat together and analyzed the reason for the problem and apply the correct the system
accordingly. Sometime there was need to correct in syntax, sometime there was need to correct
in logic and sometime in design.

42
8.3.2 Adaptive Maintenance
Any effort that is initiated as a result of addition of new module or changes in the
environment in which a software system mush operates is termed as adaptive changes. Adaptive
chance is a change driven by the need to accommodate modifications in the environment of the
software system, without which the system would become increasingly less useful until it
became obsolete.
The term environment in this context refers to all the conditions and influences which act
from outside upon the system, for example business rules, addition of new major module,
government policies, work patterns, software and hardware operating platform. A change to the
whole or part of this environment will warrant a corresponding modification of the project.
We also exercised adaptive maintenance in our project. We followed the lean product
development model so we started with basic idea but as development started client also started to
do more study on this project and he added module during the development phase lots of time
which forced us to restructure the whole system. We adopted his new module during
development because that was the bone of project although he found that idea late.

8.3.3 Perfective Maintenance
This is actually the most common type of maintenance encompassing enhancements both
to the function and the efficiency of the code and includes all changes , insertions, deletions,
modifications, extensions and enhancements made to a system to meet the evolving and
expanding need of the user. A successful piece of software tents to be subjected to a succession
of changes resulting in an increase in its requirements. This is based on the premise that as the
software becomes useful, the users tend to experiment with new cases beyond the scope for
which it was initially developed. Expansion in requirements can take the form of enhancement of
existing systems functionality or improvement in computational efficiency.
Though efforts have been made to develop error free systems, but no system is perfect,
room for improvement is always there. Thus proper documentation for the system has been done
so that it will be easy to handle any breakdown or any other type of system maintenance activity.
8.3.4 Preventive Maintenance
Preventive maintenance can be described as maintenance of systems before fault occurs.
After successful implementation of project, development team will start the preventive maintenance

43
based on uses of the project and warning feedback on the project so that system will not crash down.
In this project, after implementation of project we started the preventive maintenance to find and
remove the hidden warning that could cause problem in future. We gone through each and every
module of project and remove those conflict code in scripting.

44
9 PROJECT LEGACY
9.1 Current Status of the Project
The target decided has been achieved successfully with all the core functionalities and
user interface requirements. Our Project is using RAD (Rapid Application Development) model
technique. Our project Ashoka Diesel Spares has been made live. User can login after creating
their local account. In this, user can check the availability of the products, their size, price and
every detail and place his/her orders online, where the customer order is handled by admin.
9.2 Remaining Areas of Concern
One of the most important thing in our website that still remains undecided is the
payment section. As the payment requires the transaction of money, so it is concerns the security.
So we are planning to make a secure mode of transaction for the payment, till now the payment
is made cash on delivery.
The other areas that we are working on are the products display page, the filtration. of the
products on the basis of category and size.

9. 3 Technical and Managerial Lessons Learnt

Throughout the development process of this web based project had taught so many
meaningful lessons of the software development process which covers both the technical and
managerial fields.
A) Technical Lessons

Learned the basic of web development components such as JavaScript, CSS,

J-Query and get familiarized with its power and loopholes.
The market leading technology ASP.NET in web world, have an advanced experience
with it.
SQL server 2012 for our database at backend.
Had a hand on experience with the tools such as Visual Studio 2012, SQL Server
Management Studio etc.

45

B) Managerial Lessons

Managing Product Development Process of the software via Continuous Integration.
Developing application in an environment with multiple developers and tracking all the
changes and keeping the project synchronized throughout among the team.
Keeping the project up-to-date as per the timeline.
Full testing and verification of components and its correction before the deadline.
To maintain the consistency of quality and quantity of the product throughout the
development.

46
10 USER MANUAL
USER HOME:

Description:
User home page displays the basic information of the website Ashoka Diesel Spares.it
provides all the links to the entire page associated with the website. User can browse to other
links by clicking on the name they want to go.
It provides likes to login page, register page, shop now page, checkout page.

47
SAVE AND SIGNUP PAGE:

Description:
Save and signup page allows the user or the customer to have his own account so that he/she
can continue shopping using his personal account. Once he has created his account he can login
to continue the shopping. User can browse this page by clicking Save and sign up Page.

48
LOGIN PAGE:

Description:
Login Page allows the user to login to his account, entering his credentials username and
password and click the login button to continue shopping. User can browse this page by clicking
my account link.

49
ABOUT US:

Description:
About us page gives the complete information about the website and the information of the
company Ashoka Diesel Spares, its mission, vision and goals and the basic contact
information. User can browse this page by clicking About Us link.

50
FEEDBACK:

Description:
Feedback allows the user to give the feedback in any form complaints or suggestion of the
service and the products. Users are required to fill the name and his message and click on submit
button.

51
ADD NEW ITEM:

Description:
Add new Item allows the admin to add products and its details. And click on the save button
to save all the information to the database.

52
VIEW STOCK PAGE:

Description:
View Stock page displays all the information of the current stock .It allows the admin to edit
and update the Product Details.

53
ADD NEW SUPPLIER:

Description:
Add new Supplier allows the admin to add suppliers and their details. And click on the save
button to save all the information to the database.

54
ADD NEW EMPLOYEE:

Description:
Add new Employee allows the admin to add suppliers and their details. And click on the
save button to save all the information to the database.

55
12. BIBLIOGRAPHY
Books
Prof ASP.NET 4.5 using C# and vb.net
Beginning ASP.NET 4.0 with C# and vb.net
ASP.NET Unleashed 4.0
Ajax For Dummies (2006)
Learning_jquery_3rd_edition
Java script Bible 4th edition 2001
HTML, XHTML, & CSS Bible, 3rd Ed 2004
CSS Web Design for Dummies (2005)

Websites
http://www.asp.net
http://stackoverflow.com
http://jquery.com
http://www.asp.net/ajax
http://www.w3schools.com
http://www.jsfiddle.com

Ashoka Diesel Spares

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ashoka Diesel Spares

Hochgeladen von

Copyright:

Verfügbare Formate

Ashoka Diesel Spares

Das könnte Ihnen auch gefallen