Major Project Report

Submitted in partial fulfillment for the award of Degree of

BACHELOR OF TECHNOLOGY
In
Computer Science & Engineering

stuBuy
Submitted by:
Nafees Ahmad Ansari (1601012124)
Shalloo Bajpai (1601012189)
Tapan Shukla (1601012175)

Under the Supervision of

Mrs.Shimaila
Department Of Computer Science And Engineering

Integral University Lucknow

July-2020
 UNDERTAKING

We, Nafees Ahmad Ansari, Shalloo Bajpai ,Tapan Shukla student of B.Tech.
(CSE), hereby declare that the work detailed in this Project entitled “StuBuy”
submitted to the Department of Computer Science and Engineering, Integral
University, Lucknow for the award of the Bachelor of Technology degree is our
original work. We have neither plagiarized nor submitted this work for the
award of any other degree. In case, this undertaking is found incorrect, We
accept that my degree may be unconditionally withdrawn.

Date:30/7/2020

Venue: Lucknow
 CERTIFICATE

This is to certify that the work contained in this project report entitled “stuBuy”
by Nafees Ahmad Ansari,Shalloo Bajpai &TapanShukla is a faithful record of
work that has been carried out by the students, under my supervision.

Mrs. Shimaila

(Assistant Professor)

Computer Science & Engineering.

 RECOMMENDATION

On the basis of the declaration submitted by Nafees Ahmad Ansari, Shalloo

Bajpai,Tapan Shukla internal assessment carried out by department on date
30/07/2020 and the certificate issued by the Guide Mrs.Shimaila the work
entitle “StuBuy submitted to department of CSE, is recommended for final
examination.

Signature B.Tech Project Coordinator Signature of HOD

Mrs.Shimaila Dr.M.AkheelaKhanum

(Assistant Professor) (Head Of Department)

Date:_____________ Date:______________
 ACKNOWLEDGEMENT

We have taken efforts in this project. However, it would not have been possible
without the kind support and help of many individuals and organizations. I
would like to extend my sincere thanks to all of them.

We are highly indebted to our Project Coordinator Mrs.Shimaila for her

guidance and constant supervision as well as for providing necessary
information regarding the project & also for their support in completing the
project.

We would like to express our gratitude towards Mrs.Shimaila for their kind co-
operation and encouragement which helped us in completion of this project.

Our thanks and appreciations also go to our colleagues in developing the project
and people who have willingly helped me out with their abilities.
 Abstract

stuBuyis an online platform where a user can buy and sell the products
available on the site. It is a multi-user platform where the users can post ads of
their products.
The users can create their personal profiles with their personal information
which can be seen on their page.
This project uses database rigorously to fetch and insert the user information in
and from the database. This feature makes it fast and more reliable in terms of
user experience.
Separate features for login and signup is available for the users.
The facility to change your password is also available to the users if needed so.
Email verification is active by which ambiguous users are filtered out. This
feature keeps the website free from unnecessary user base.
 TABLE OF CONTENTS
S.NO. CONTENTS SIGN REMARK

1 ACKNOWLEDGEMENT

2 ABSTRACT

3 INTRODUCTION OF THE PROJECT

4 SYSTEM REQUIREMENTS

5 FEASIBILITY STUDY

6 REQUIREMENT ANALYSIS

7 PROJECT DESCRIPTION

8 SOFTWARE DEVELOPMENT LIFE CYCLE

9 PROJECT DESCRIPTION

10 PROJECT DESIGN

11 CODING

12 TESTING

13 FUTURE SCOPE

14 CONCLUSION

15 REFERENCES
 Introduction
stuBuy is an online commerce platform where the users can register themselves
and become a part of the stuBuy database. These registered users can hence,
buy products that they desire from the available products in the stuBuy
database.

For every user registered in the database, a personal profile is created where the
users can upload their information such as name, address, photo etc. This helps
stuBuy to interact with the customers in a better way.

Mail facilities such as email verification and password change feature are also
available in this initial version of stuBuy. These facilities make stuBuy unique
in its domain and much secure.
 System Requirements
System requirements is an enhanced list of the device(s) or the features that a system is
required to have in order to make it capable of performing a given task.

It is very crucial for our system to meet these requirements as without it, the system cannot
perform the task at hand.

1.1 Hardware Requirements

 Processor (CPU) with 2 gigahertz (GHz) frequency or above

 A minimum of 2 GB of RAM
 Monitor Resolution 1024 X 768 or higher
 A minimum of 20 GB of available space on the hard disk
 Internet Connection Broadband (high-speed) Internet connection with a speed of 4
Mbps or higher
 Keyboard and a Microsoft Mouse or some other compatible pointing device

1.2 Software Requirements

 An Integrated Development Environment (IDE) (NetBeans, Eclipse, etc).

 A web browser (Mozilla Firefox, Google Chrome, etc).
 A web server (Apache Tomcat, GlassFish, etc).
 A database server (MySql, NoSql, etc).
 A database IDE (MySQL workbench for MySql).
 Feasibility Study
In this chapter we will explore the overall feasibility of the project.

2.1 Project Description

This project is a Web Application that interacts with the MySQL database and carries out
various database operations through a User Interface. This website can be used to buy items
from the given list of items available on the website

This Application has used

 HTML
 CSS
 Bootstrap
 Java Servlets
 Java Server Pages (JSP)
 AJAX

2.2 Goals
 To create an online shopping website
 To create a verified login/signup portal
 To create a user profile with user’s information
 To create an online cart to store/add/remove items.

2.3 Conclusions
This project is able to achieve the intended goals by creating a web app interface that
interacts directly with the database thus providing an interface to the user for performing
multiple operations with the help of Java Servlets and JSPs integrated with JDBC and
MySQL database.
 Requirement Analysis
In this chapter, I have covered the requirement analysis for this project in depth

3.1 Functional Requirements

The functional requirements to be met during the development of the current application are

 Bug free code

 Uninterrupted functioning
 Meeting the requirements
 Completed in given time

3.2 Non – Functional Requirements

 Easy to understand User Interface

 Described colour combination
 Should be fast, no time lags
 Should provide capacity to add more users
 Frequent adding of new items
 SYSTEM DEVELOPMENT LIFE CYCLE

The System development life cycle (SDLC), or Software development process in systems
engineering, information systems and software engineering, is a process of creating or
altering information systems, and the models and methodologies that people use to develop
these systems. In software engineering, the SDLC concept underpins many kinds of software
development methodologies.

Broadly, following are the different activities to be considered while defining system
software development processthe system development life cycle for the said project:

 Problem Definition
 System Analysis
 Study of existing system
 Drawback of the existing system
 Proposed system
 System Requirement study
 Data flow analysis
 Feasibility study
 System design
 Input Design (Database & Forms)
 Updating
 Query /Report design
 Administration
 Testing
 Implementation
 Maintenance

SYSTEM ANALYSIS:- Systems analysis is the study of sets of interactingentities,

including computer systems analysis. This field is closely related to requirements analysis or
operations research. It is also "an explicit formal inquiry carried out to help someone
(referred to as the decision maker) identify a better course of action and make a better
decision than he might otherwise have made.
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding the
details of an existing system or a proposed one and then deciding whether the proposed
system is desirable or not and whether the existing system needs improvements. Thus, system
analysis is the process of investigating a system, identifying problems, and using the
information to recommend improvement to the system.

SYSTEM DESIGN:-Systems design is the process of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements. One could see it
as the application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering. If the broader
topic of product development"blends the perspective of marketing, design, and
manufacturing into a single approach to product development," then design is the act of
taking the marketing information and creating the design of the product to be manufactured.
Systems design is therefore the process of defining and developing systems to satisfy
specified requirements of the user. Until the 1990s systems design had a crucial and
respected role in the data processing industry. In the 1990s standardization of hardware and
software resulted in the ability to build modular systems. The increasing importance of
software running on generic platforms has enhanced the discipline of software engineering.

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

ER DAIGRAM:-ER Diagram Once in the ER diagram, the modeler can begin the process of
determining how the relational model fits together; and which attributes are primary keys,
secondary keys, and foreign keys based on relationships with other entities. The idea is to
build a logical model that conforms to the rules of data normalization.

To capture this information, an Entity Relation (ER) diagram is recommended as an

extension to UML. The class diagram can be used to model the logical framework of the
database, independent of it being object-oriented or relational, with classes representing
tables, and class attributes representing columns. If a relational database is the chosen
implementation medium, then the class diagram can be mapped to a logical ER diagram.
Persistent classes and their attributes map directly to logical entities and their attributes; the
modeler is faced with choices on how to map associations over to relationships between
entitie
 Project Description
Brief Introduction:

The main features of this website are:

1. Registration of a new user / Signup

2. Login

3. Mail verification

4. Password recovery

Java Servlets
Servlet technology is used to create a web application (resides at server side and generates a
dynamic web page).

Servlet technology is robust and scalable because of java language. Before Servlet, CGI
(Common Gateway Interface) scripting language was common as a server-side programming
language. However, there were many disadvantages to this technology. We have discussed
these disadvantages below.

There are many interfaces and classes in the Servlet API such as Servlet, GenericServlet,
HttpServlet, ServletRequest, ServletResponse, etc.

What is a Servlet?

Servlet can be described in many ways, depending on the context.

o Servlet is a technology which is used to create a web application.

o Servlet is an API that provides many interfaces and classes including documentation.
o Servlet is an interface that must be implemented for creating any Servlet.
o Servlet is a class that extends the capabilities of the servers and responds to the
incoming requests. It can respond to any requests.
o Servlet is a web component that is deployed on the server to create a dynamic web
page.
Servlet Life Cycle

A servlet life cycle can be defined as the entire process from its creation till the destruction.
The following are the paths followed by a servlet.
 The servlet is initialized by calling the init() method.
 The servlet calls service() method to process a client's request.
 The servlet is terminated by calling the destroy() method.
 Finally, servlet is garbage collected by the garbage collector of the JVM.
Now let us discuss the life cycle methods in detail.

The init() Method

The init method is called only once. It is called only when the servlet is created, and not
called for any user requests afterwards. So, it is used for one-time initializations, just as with
the init method of applets.
The servlet is normally created when a user first invokes a URL corresponding to the
servlet, but you can also specify that the servlet be loaded when the server is first started.
When a user invokes a servlet, a single instance of each servlet gets created, with each user
request resulting in a new thread that is handed off to doGet or doPost as appropriate. The
init() method simply creates or loads some data that will be used throughout the life of the
servlet.

The service() Method

The service() method is the main method to perform the actual task. The servlet container
(i.e. web server) calls the service() method to handle requests coming from the
client( browsers) and to write the formatted response back to the client.
Each time the server receives a request for a servlet, the server spawns a new thread and
calls service. The service() method checks the HTTP request type (GET, POST, PUT,
DELETE, etc.) and calls doGet, doPost, doPut, doDelete, etc. methods as appropriate.
The service () method is called by the container and service method invokes doGet, doPost,
doPut, doDelete, etc. methods as appropriate. So you have nothing to do with service()
method but you override either doGet() or doPost() depending on what type of request you
receive from the client.
The doGet() and doPost() are most frequently used methods with in each service request.
Here is the signature of these two methods.

Architecture Diagram

The following figure depicts a typical servlet life-cycle scenario.

 First the HTTP requests coming to the server are delegated to the servlet container.
 The servlet container loads the servlet before invoking the service() method.
 Then the servlet container handles multiple requests by spawning multiple threads,
each thread executing the service() method of a single instance of the servlet.

HTTP Session Tracking

HTTP is a "stateless" protocol which means each time a client retrieves a Web page, the
client opens a separate connection to the Web server and the server automatically does not
keep any record of previous client request.
Still there are following three ways to maintain session between web client and web server −
Cookies

A webserver can assign a unique session ID as a cookie to each web client and for
subsequent requests from the client they can be recognized using the recieved cookie.
This may not be an effective way because many time browser does not support a cookie, so I
would not recommend to use this procedure to maintain the sessions.

Hidden Form Fields

A web server can send a hidden HTML form field along with a unique session ID as follows
This entry means that, when the form is submitted, the specified name and value are
automatically included in the GET or POST data. Each time when web browser sends
request back, then session_id value can be used to keep the track of different web browsers.
This could be an effective way of keeping track of the session but clicking on a regular (<A
HREF...>) hypertext link does not result in a form submission, so hidden form fields also
cannot support general session tracking.

URL Rewriting

You can append some extra data on the end of each URL that identifies the session, and the
server can associate that session identifier with data it has stored about that session.
For example, with http://tutorialspoint.com/file.htm;sessionid = 12345, the session identifier
is attached as sessionid = 12345 which can be accessed at the web server to identify the
client.
URL rewriting is a better way to maintain sessions and it works even when browsers don't
support cookies. The drawback of URL re-writing is that you would have to generate every
URL dynamically to assign a session ID, even in case of a simple static HTML page.

The HttpSession Object

Apart from the above mentioned three ways, servlet provides HttpSession Interface which
provides a way to identify a user across more than one page request or visit to a Web site
and to store information about that user.
The servlet container uses this interface to create a session between an HTTP client and an
HTTP server. The session persists for a specified time period, across more than one
connection or page request from the user.
Java Mail
The JavaMail is an API that is used to compose, write and read electronic messages
(emails).

The JavaMail API provides protocol-independent and plateform-independent framework for

sending and receiving mails.

The JavaMail facility can be applied to many events. It can be used at the time of registering
the user (sending notification such as thanks for your interest to my site), forgot password
(sending password to the users email id), sending notifications for important updates etc. So
there can be various usage of java mail api.

Java Mail Architecture

The java application uses JavaMail API to compose, send and receive emails. The JavaMail
API uses SPI (Service Provider Interfaces) that provides the intermediatory services to the
java application to deal with the different protocols. Let's understand it with the figure given
below:
HTML
HTML is an acronym which stands for Hyper Text Markup Language which is used for
creating web pages and web applications. Let's see what is meant by Hypertext Markup
Language, and Web page.

Hyper Text: HyperText simply means "Text within Text." A text has a link within it, is a
hypertext. Whenever you click on a link which brings you to a new webpage, you have
clicked on a hypertext. HyperText is a way to link two or more web pages (HTML
documents) with each other.

Markup language: A markup language is a computer language that is used to apply layout
and formatting conventions to a text document. Markup language makes text more interactive
and dynamic. It can turn text into images, tables, links, etc.

Web Page: A web page is a document which is commonly written in HTML and translated
by a web browser. A web page can be identified by entering an URL. A Web page can be of
the static or dynamic type. With the help of HTML only, we can create static web pages.

Hence, HTML is a markup language which is used for creating attractive web pages with the
help of styling, and which looks in a nice format on a web browser. An HTML document is
made of many HTML tags and each HTML tag contains different content.

Features of HTML

1) It is a very easy and simple language. It can be easily understood and modified.

2) It is very easy to make an effective presentation with HTML because it has a lot of

formatting tags.

3) It is a markup language, so it provides a flexible way to design web pages along with the
text.

4) It facilitates programmers to add a link on the web pages (by html anchor tag), so it
enhances the interest of browsing of the user.

5) It is platform-independent because it can be displayed on any platform like Windows,

Linux, and Macintosh, etc.

6) It facilitates the programmer to add Graphics, Videos, and Sound to the web pages which
makes it more attractive and interactive.

7) HTML is a case-insensitive language, which means we can use tags either in lower-case or
upper-case.
CSS
CSS stands for Cascading Style Sheets. It is a style sheet language which is used to describe
the look and formatting of a document written in markup language. It provides an additional
feature to HTML. It is generally used with HTML to change the style of web pages and user
interfaces. It can also be used with any kind of XML documents including plain XML, SVG
and XUL.

CSS is used along with HTML and JavaScript in most websites to create user interfaces for
web applications and user interfaces for many mobile applications.

The major points of CSS are given below:

 CSS stands for Cascading Style Sheet.

 CSS is used to design HTML tags.
 CSS is a widely used language on the web.

Why use CSS

These are the three major benefits of CSS:

1) Solves a big problem

Before CSS, tags like font, color, background style, element alignments, border and size had
to be repeated on every web page. This was a very long process. For example: If you are
developing a large website where fonts and color information are added on every single page,
it will be become a long and expensive process. CSS was created to solve this problem. It
was a W3C recommendation.

2) Saves a lot of time

CSS style definitions are saved in external CSS files so it is possible to change the entire
website by changing just one file.

3) Provide more attributes

CSS provides more detailed attributes than plain HTML to define the look and feel of the
website.

CSS Syntax:
A CSS rule set contains a selector and a declaration block.
Selector: Selector indicates the HTML element you want to style. It could be any tag like
<h1>, <title> etc.

Declaration Block: The declaration block can contain one or more declarations separated by
a semicolon. For the above example, there are two declarations:

1. color: yellow;
2. font-size: 11 px;

Each declaration contains a property name and value, separated by a colon.

Property: A Property is a type of attribute of HTML element. It could be color, border etc.

Value: Values are assigned to CSS properties. In the above example, value "yellow" is
assigned to color property.

BOOTSTRAP
Bootstrap tutorial provides basic and advanced concepts of Bootstrap. Our Bootstrap tutorial
is designed for beginners and professionals.

Bootstrap is the popular HTML, CSS and JavaScript framework for developing a responsive
and mobile friendly website.

Our Bootstrap tutorial includes all topics of Bootstrap such as jumbotron, table, button, grid,
form, image, alert, wells, container, carousel, panels, glyphicon, badges, labels, progress bar,
pagination, pager, list group, dropdown, collapse,tabs, pills, navbar, inputs, modals, tooltip,
popover and scrollspy.

What is Bootstrap

o Bootstrap is the most popular HTML, CSS and JavaScript framework for developing
a responsive and mobile friendly website.
o It is absolutely free to download and use.
 o It is a front-end framework used for easier and faster web development.
o It includes HTML and CSS based design templates for typography, forms, buttons,
tables, navigation, modals, image carousels and many others.
o It can also use JavaScript plug-ins.
o It facilitates you to create responsive designs.

Why use Bootstrap

Following are the main advantage of Bootstrap:

o It is very easy to use. Anybody having basic knowledge of HTML and CSS can use
Bootstrap.
o It facilitates users to develop a responsive website.
o It is compatible on most of browsers like Chrome, Firefox, Internet Explorer, Safari
and Opera etc.

What Bootstrap package contains

Scaffolding: Bootstrap provides a basic structure with Grid System, link styles, and
background.

CSS: Bootstrap comes with the feature of global CSS settings, fundamental HTML elements
style and an advanced grid system.

Components: Bootstrap contains a lot of reusable components built to provide iconography,

dropdowns, navigation, alerts, pop-overs, and much more.

JavaScript Plugins: Bootstrap also contains a lot of custom jQuery plugins. You can easily
include them all, or one by one.

Customize: Bootstrap components are customizable and you can customize Bootstrap's

components, LESS variables, and jQuery plugins to get your own style.

AJAX
AJAX is an acronym for Asynchronous JavaScript and XML. It is a group of inter-related
technologies like JavaScript, DOM, XML, HTML/XHTML, CSS, XMLHttpRequest etc.

AJAX allows you to send and receive data asynchronously without reloading the web page.
So it is fast.

AJAX allows you to send only important information to the server not the entire page. So
only valuable data from the client side is routed to the server side. It makes your application
interactive and faster.
AJAX Technologies

Ajax is a group of inter-related technologies. AJAX technologies includes:

o HTML/XHTML and CSS
o DOM
o XML or JSON
o XMLHttpRequest
o JavaScript

HTML/XHTML and CSS

These technologies are used for displaying content and style. It is mainly used for
presentation.

DOM

DOM stands for Data Object Modelling. It is used for dynamic display and interaction with
data.

XMLor JSON

For carrying data to and from server. JSON (Javascript Object Notation) is like XML but
short and faster than XML.

XMLHttpRequest

For asynchronous communication between client and server.

JavaScript

It is used to bring above technologies together.Independently, it is used mainly for client-side

validation
JSP
JSP technology is used to create web application just like Servlet technology. It can be
thought of as an extension to Servlet because it provides more functionality than servlet
such as expression language, JSTL, etc.

A JSP page consists of HTML tags and JSP tags. The JSP pages are easier to maintain
than Servlet because we can separate designing and development. It provides some
additional features such as Expression Language, Custom Tags, etc.

Advantages of JSP

There are many advantages of JSP over the Servlet. They are as follows:

1) Extension to Servlet

JSP technology is the extension to Servlet technology. We can use all the features of the
Servlet in JSP. In addition to, we can use implicit objects, predefined tags, expression
language and Custom tags in JSP, that makes JSP development easy.

2) Easy to maintain

JSP can be easily managed because we can easily separate our business logic with
presentation logic. In Servlet technology, we mix our business logic with the presentation
logic.

3) Fast Development: No need to recompile and redeploy

If JSP page is modified, we don't need to recompile and redeploy the project. The Servlet
code needs to be updated and recompiled if we have to change the look and feel of the
application.

4) Less code than Servlet

In JSP, we can use many tags such as action tags, JSTL, custom tags, etc. that reduces the
code. Moreover, we can use EL, implicit objects, etc.
The Lifecycle of a JSP Page

The JSP pages follow these phases:

o Translation of JSP Page

o Compilation of JSP Page
o Classloading (the classloader loads class file)
o Instantiation (Object of the Generated Servlet is created).
o Initialization ( the container invokes jspInit() method).
o Request processing ( the container invokes _jspService() method).
o Destroy ( the container invokes jspDestroy() method).
 Project Design
6.1 The Front page
Item Gallery
Login Page

Signup Page
Personal Account

Password Recovery
Email verification
Database
Data Flow Diagrams
Level 1

Level 1
 Level 1.1

Entry Relation Diagram

User
Yahoo mail

Login Access Gmail

Hotmail
Add email account
Settings

Change password Remove Account Message Limit Per

Page
 CODING
1. Overall File Structure

2. Registration
3. Login

4. Logout
5. Mail Sender
 TESTING

System Testing: -
Black box testing method was used for system testing. The black box testing
usually demonstrates that software functions are operational; that the input is properly
accepted and the output is correctly produced; and that integrity of external information
(databases) is maintained.

Why testing is done

 Testing is the process of running a system with the intention of finding errors.
 Testing enhances the integrity of a system by detecting deviations in design and
errors in the system.
 Testing aims at detecting error-prone areas. This helps in the prevention of errors
in a system.
 Testing also add value to the product by confirming to the user requirements.

Causes of Errors

The most common causes of errors in a software system are:

 Communication gap between the developer and the business decisionmaker: A

communication gap between the developer and the business decision maker is normally due
to subtle differences between them. The differences can be classified into five broad areas:
Thought process, Background and Experience, Interest, Priorities, Language
 .Time provided to a developer to complete the project: A common source of errors in
projects comes from time constraints in delivering a product. To keep to the schedule,
features can be cut. To keep the features, the schedule can be slipped. Failing to adjust the
feature set or schedule when problems are discovered can lead to rushed work and flawed
systems.
 Over Commitment by the developer: High enthusiasm can lead to over commitment
by the developer. In these situations, developers are usually unable to adhere to deadlines or
quality due to lack of resources or required skills on the team.
 Insufficient testing and quality control: Insufficient testing is also a major source of
breakdown of e-commerce systems during operations, as testing must be done during all
phases of development.
 Inadequate requirements gathering: A short time to market results in developers
starting work on the Web site development without truly understanding the business and
technical requirements. Also, developers may create client-side scripts using language that
may not work on some client browsers.
 Keeping pace with the fast changing Technology: New technologies are constantly
introduced. There may not be adequate time to develop expertise in the new technologies.
This is a problem for two reasons. First, the technology may not be properly implemented.
Second, the technology may not integrate well with the existing environment.
Testing Principles

 To discover as yet undiscovered errors.

 All tests should be traceable to customer’s requirement.
 Tests should be planned long before the testing actually begins.
 Testing should begin “in the small” & progress towards “testing in the large”.
 Exhaustive Testing is not possible.
 To be most effective training should be conducted by an Independent Third Party.

Testing Objectives

 Testing is a process of executing a program with the intent of finding errors.

 A good test case is one that has a high probability of finding an as yet undiscovered error.
 A successful test is one that uncovers an as yet undiscovered error.

Kinds of Testing:
Black Box Testing- Not based on any knowledge of internal designs or code. Tests are based
on requirements and functionality.

White Box Testing- Based on the knowledge of the internal logic of an application’s code.
Tests are based on coverage of code statements, branches, paths and statements.

Functional Testing- Black-box type testing geared to functional requirements of an

application; testers should do this type of testing. This doesn’t mean that the programmers
shouldn’t check that their code works before releasing it. Unit Testing- The most ‘micro’
scale of testing; to test particular functions and code modules. Typically done by the
programmer and not by the testers, as it requires detailed knowledge of the internal program
design and code. Not always easily done unless the application has a well-designed
architecture with tight code; may require developing test driver modules or test harnesses.

Integration Testing- Testing of combined parts of an application to determine if they

function together correctly. The ‘parts’ can be code modules, individual applications, client
and server applications on a network, etc. This type of testing i

Regression Testing- Re-testing after fixes or modifications of the software or its

environment. It is difficult to determine how much re testing is needed, especially near the
end of the development cycle. Automated testing tools can be especially useful for this type
of testing.

s especially relevant to client/ server and distributed systems.

 Future Scope

stuBuy isan online platform where the users can buy their desired products without going
through the hassle of generic market shopping culture. The users can select from a variety of
products at a single stop.

The future scope of this project can be extended to a single stop platform for buying and
selling varied variety of items among businesses or users with the ease of selecting products
from a large variety and sellers.

stuBuy future possibilities can be summarized into a nutshell as:

 Much of offline business can be taken online making it easier for people to commit
commerce.
 With increasing need of variety products, people are moving towards online
commerce
 Users can also sell their own products to other users or businesses.
 CONCLUSION

The software will be developed by implementing the concept of modularity which in turn
reduces the complexity involved in maintaining it. The administrator should have a sound
technical knowledge about maintaining the software and further enhancements will be
undertaken by the developer.

The application is portable which ensure its adaptability for use on different computer
terminals with different operating system and standards.

The factors guarantee the software’s availability includes proper termination and correct
input details. Also the resources used for the project development are Microsoft certified
which speaks of its high quality standards.

Hence we may conclude that the application system being developed helps a great deal in
modifying the computerized Alumni Management System.

Goal achieved: The System is able provide the interface to the user so that he can replicate
his desired data.

User friendliness: Though the most part of the system is supposed to act in the background,
efforts have been made to make the foreground interaction with user as smooth as possible.
Also the integration of the system with Alumni Management project has been kept in mind
throughout the development phase.
 References
1. Udemy.com
The platform which provided me this interesting training.
2. Geeksforgeeks.com
For all the theory lessons on the topics
3. Javatpoint.com
For the detailed diagrammatic representations.