Chapter 1: Introduction

1.1 Introduction
A fully functional University Management System Project that being developed in Java
Programming using NetBeans and MySQL Database as the System’s Back-End. It was
created for the University and its affiliated institutions to conduct, monitor, and analyze
complicated activities such as Centralized Admission, Centralized Examination, and
much more.

1.1 Problem Statement

User Registration system deals with the users for to make their data secure and more
reliable for them. It provide good user interface with the system that make them easily
recognize with the system. It provide the concept where user can easily asses to the
database, they feel more secure. it is basically design on a concept where user can register
their name, address, email, phone number, gender, age with submit button, after creating
signup user can easily login into the system with correct username and password.
It provides data integrity which also leads to confusion because it may refer either to a
state or a process. Data integrity refers to the accuracy and consistency of data, which is
used to ensure validity and accuracy of a data set or all data contained in the database. For
instance, error checking and validation method may be referred to as data integrity
processes.
This system involves the following functionalities:
1. Collecting data: The data is collected from the user through the
submit(register).
2. Verification of data: The data collected from the user is cross verified with the
user database.
1.3Objectives
The main Objectives of User Registration System is to manage the details of user in the
particular field. It manages all the information about register. The project is totally built at
administrative end thus only the administrator is guaranteed the access. The purpose of

1
the project is to build an application program to reduce the manual work for managing the
user details. It tracks all the details about the Users.
The objectives of User Registration/login System are listed below:
1. To provide user registration.
2. To manage the information users.
3. To build application program to reduce the manual work.
4. To reduce data redundancy.
5. To provide good and secure user interface.

1.4 Scope and Limitation

There are some limitations and scope of our project user registration/login systems that
are mentioned below:
Scope
The main scope of this application is to deals with the various functioning in users
registration system. It gives further information about the enrollment process as to know
how many uses are enrolled in every level. Administrator has total access to the system,
confirming the users who are currently registering and/or enrolling generating records.
Limitation
 It is used only in a particular field for to manage user information.
 It doesn't accept any redundant data.
 It can only operate for users enrolment purposes.
1.5Report Organization
This report is divided into 5 chapters. Each chapter is divided into different headings. The
preliminary section contains the overall information about the project. This section
includes abstract, table of contents, list of figures and abbreviations.
Chapter 1 gives introduction about USERS REGISTRATION SYSTEM. The problem
definitions, objectives, scopes and limitation of this system are discussed.
Chapter 2 contains background study of the system and literature review section where
the research works done in the field of the system are discussed in brief.

2
Chapter 3 discusses in detail about the analysis and design of the system. It provides
information about the existing system, data collection methods, analysis part, and
feasibility study and system configuration. It also gives information about overall system
architecture and database diagram.
Chapter 4 gives information about the system development models, implementations,
techniques, tool used and also test cases of the system for testing.
Chapter 5 includes the future scopes of the project and necessary future
recommendations along with conclusion.

Chapter2: Background Study and Literature Review

2.1 Background Study
A theory is a well-substantiated explanation of an aspect of the natural world that can
incorporate laws, hypotheses and facts. A theory not only explains known facts; it also
allows scientists to make predictions of what they should observe if a theory is true.
Theories create a basis for future research. Researchers use theories to form hypotheses
that can then be tested. As new discoveries are made and incorporated into the original
theory, new questions and ideas can then be explored.
User registration system can be defined as software that allows the concept where user
can easily asses to the database, they feel more secure. It is basically design on a concept
where user can register their name, email, phone number, gender, age with submit button,
after submit user can easily see the records of their employee where he/she can manage
the detail of them. The application will be scalable and easily maintained. It could be
easily changeable to the changing needs of users. It provides data integrity which also
leads to confusion because it may refer either to a state or a process. Data integrity refers
to the accuracy and consistency of data, which is used to ensure validity and accuracy of a
data set or all data contained in the database. For instance, error checking and validation
method may be referred to as data integrity processes. The purpose of the project is to
build an application program to reduce the manual work for managing detail of the user.

3
It tracks all the details about the Users. It gives further information about the enrollment
process as to know how many uses are enrolled in every level.
2.2 Literature Reviews
A literature review is a comprehensive summary of previous research on a topic. The
literature review surveys scholarly articles, books, and other sources relevant to a
particular area of research. The review should enumerate, describe, summarize,
objectively evaluate and clarify this previous research.
 Characteristics of a good literature review?
 It should be wide enough to provide enough information required on the subject.
 It must identify studies and models that support a research topic.
 It must be narrow enough to eliminate irrelevant information from the research
topic.
 It must be conducted from reliable sources.
A literature review may consist of simply a summary of key sources, but in the
social sciences, a literature review usually has an organizational pattern and
combines both summary and synthesis, often within specific conceptual categories.
A summary is a recap of the important information of the source, but a synthesis is a
re-organization, or a reshuffling, of that information in a way that informs how you
are planning to investigate a research problem. The analytical features of a literature
review might:
 Give a new interpretation of old material or combine new with old
interpretations,
 Trace the intellectual progression of the field, including major debates,
 Depending on the situation, evaluate the sources and advise the reader on
the most pertinent or relevant research, or
 Usually in the conclusion of a literature review, identify where gaps exist
in how a problem has been researched to date

4
 Chapter 3: System Analysis and Design
3.1. System Analysis
System analysis is the process by which an individual (s) studies a system such that an
information system can be analyzed, modeled, and a logical alternative can be chosen.
Systems analysis projects are initiated for three reasons: problems, opportunities, and
directives. It treats systems analysis as a process in which the analyst is challenged to
reverse-engineer someone else’s, possibly dysfunctional, synthesis. It is more important
to ask, ‘What?’ and ‘Why?’ rather than ‘How?’
Systems development can generally be thought of as having two major components:
Systems analysis and Systems design. System design is the process of planning a new
business system or one to replace or complement an existing system. But before this
planning can be done, we must thoroughly understand the old system and determine how
computers can best be used to make its operation more effective. System analysis, then, is
the process of gathering and interpreting facts, diagnosing problems, and using the
information to recommend improvements to the system. This is the job of the systems
analyst.
Systems analysis is "the process of studying a procedure or business to identify its goal
and view sees system analysis as a problem-solving technique that breaks down a system
into its component pieces, and how well those parts work and interact to accomplish their

5
purpose. The field of system analysis relates closely to requirements analysis or
to operations research. It is also "an explicit formal inquiry carried out to help a decision
maker identify a better course of action and make a better decision than they might
otherwise have made. The people involved include systems analysts, sponsors, and users.
The process by which systems are developed can be described by the systems
development life cycle. The tasks, techniques, and tools used by the systems development
life cycle can be referred as a methodology. There are three classifications of the
methodologies: traditional, information engineering, and object-oriented. CASE tools are
automated tools that support specific methodologies.

3.1.1. Requirement Analysis

Requirements Analysis is the process of defining the expectations of the users for an
application that is to be built or modified. It involves all the tasks that are conducted to
identify the needs of different stakeholders. Therefore requirements analysis means to
analyze, document, validate and manage software or system requirements. High-quality
requirements are documented, actionable, measurable, testable, traceable, helps to
identify business opportunities, and are defined to a facilitate system design. For the
success of a project, it is utmost important to analyze project requirements when they are
gathered as well as throughout the lifecycle of the project. Software Requirements
analysis helps to keep the requirements in line with the need of the business. A good
project requirements analysis process will render a software application that caters to the
objectives of the business set forth. Requirements analysis focuses on the tasks that
determine the needs or conditions to meet the new or altered product or project, taking
account of the possibly conflicting requirements of the various stakeholders, analyzing,
documenting, validating and managing software or system requirements.

Requirements analysis is critical to the success or failure of a systems or software project.

The requirements should be documented, actionable, measurable, testable, traceable,
related to identified business needs or opportunities, and defined to a level of detail
sufficient for system design.
I. Functional Requirements
Functional requirements define the basic system behavior. Essentially, they are what the
system does or must not do, and can be thought of in terms of how the system responds to

6
inputs. Functional requirements usually define if/then behaviors and include calculations,
data input, and business processes.
Functional requirements may involve calculations, technical details, data manipulation
and processing, and other specific functionality that define what a system is supposed to
accomplish. Behavioral requirements describe all the cases where the system uses the
functional requirements, these are captured in use case. 
Various functional modules can be implemented by the user registration system .it
provides a requirement overview of the system. The plan for implementing functional
requirements is detailed in the system design.

II. Use case diagram

The Use case describes what of a system not “how”. They only give functional view of
the system. Use case is structured out line or templates for the description of user
requirement, model in a structured language like English. Use case diagrams are graphical
representation that may be decomposed into further levels of the abstraction.
A use case is the specification of a set of actions performed by a system, which yields an
observable result that, is, typically, of value for one or more actors or others take holders
of the system.

7
 submit

AddUser

Invite users

user
Admin
Register

Edit profile

Delete

read

Figure 1: Use Case Diagram

III. Non-Functional Requirement

Non-Functional requirements define the system behavior, features, and affect the user
experience. How well non-functional requirements are defined and executed determines
how easy the system is to use, and is used to judge system performance. Non-Functional
requirements are product properties and focus on user.
A non-functional requirement (NFR) is a requirement that specifies criteria that can be
used to judge the operation of a system, rather than specific behaviors. They are
contrasted with functional requirements that define specific behavior or functions. The
plan for implementing functional requirements is detailed in the system design. The plan

8
for implementing non-functional requirements is detailed in the system architecture,
because they are usually architecturally significant requirements.
Non-Functional Requirements are the constraints or the requirements imposed on the
system. They specify the quality attribute of the software. This requirements deal with
issues like scalability, maintainability, performance, portability, security, reliability, and
many more. Non-Functional Requirements address vital issues of quality for software
systems.
 Reliability/Availability Requirements
 Security Requirements
 Usability
 Scalability Requirements
3.1.2 Feasibility Analysis
A feasibility study is an analysis that considers all of a project's relevant factors including
economic, technical, legal, and scheduling considerations to ascertain the likelihood of
completing the project successfully. A feasibility study aims to objectively and rationally
uncover the strengths and weaknesses of an existing business or proposed venture,
opportunities and threats present in the environment, the resources required to carry
through, and ultimately the prospects for success.
However, a feasibility study isn't only used for projects looking to measure and forecast
financial gains. In other words, feasible can mean something different, depending on the
industry and the project's goal. Although feasibility studies can help project managers
determine the risk and return of pursuing a plan of action, several steps and best practices
should be considered before moving forward.

i. Technical Feasibility
Technical describes a specific art or science, or training for a particular
job. Technical comes from the Greek techno, which means "art or skill."
Anything technical requires both art and skill. If you're an Olympic
gymnast, you have technical abilities. Technical is something having to do
with an industrial or mechanical art or an applied science. An example of
technical used as an adjective is the phrase technical jargon which is the
language a machinist would use to describe a mechanical issue with
another machinist.

9
 ii. Operational Feasibility
An operational definition, when applied to data collection, is a clear,
concise detailed definition of a measure. The need for operational
definitions is fundamental when collecting all types of data. It is
particularly important when a decision is being made about whether
something is correct or incorrect, or when a visual check is being made
where there is room for confusion. For example, data collected will be
erroneous if those completing the checks have different views of what
constitutes a fault at the end of a glass panel production line. Defective
glass panels may be passed and good glass panels may be rejected.
Similarly, when invoices are being checked for errors, the data collection
will be meaningless if the definition of an error has not been specified.
When collecting data, it is essential that everyone in the system has the
same understanding and collects data in the same way. Operational
definitions should therefore be made before the collection of data begin.
iii. Economic Feasibility
Economics is a social science concerned with the production, distribution,
and consumption of goods and services. It studies how individuals,
businesses, governments, and nations make choices about how to allocate
resources. Economics focuses on the actions of human beings, based on
assumptions that humans act with rational behavior, seeking the most
optimal level of benefit or utility. The building blocks of economics are
the studies of labour and trade. Since there are many possible applications
of human labour and many different ways to acquire resources, it is the
task of economics to determine which methods yield the best results.
iv. Schedule Feasibility
A schedule is a plan that gives a list of events or tasks and the times at
which each one should happen or be done. He has been forced to adjust his
schedule. We both have such hectic schedules. Synonyms: plan,
programme, agenda, calendar More Synonyms of schedule.

Activities Start End Duration October November

(Days) 9 14 20 1 5 10 13

10
 oct oct oct nov nov nov nov
System 9 oct 13oct 5 Days
Analysis 2020
System 14 19 6 Days
Design
Coding 20 31 12 Days
Testing 1 nov 4 nov 2 Days
Maintenance 5 9 2 Days
Performance 10 12 3 Days
Testing
Documentati 13 17 5 Days
on
Figure 2: project timeline using Gantt chart

3.1.3 Data Modeling(ER-Diagram)

Data modeling is the process of creating a visual representation of either a whole
information system or parts of it to communicate connections between data points and
structures. This provides a common, consistent, and predictable way of defining and
managing data resources across an organization, or even beyond.
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is an object, a component of data. An entity set is a
collection of similar entities. These entities can have attributes that define its properties.
ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram
that displays the relationship of entity sets stored in a database. ER Diagrams contain
different symbols that use rectangles to represent entities, ovals to define attributes and
diamond shapes to represent relationships.

11
Username mobile.no
Name
Password ID

Admin 1 Has N User

Email Gender

Address
Figure 3: ER Diagram

3.1.4 Process Modeling (DFD)

Process modeling involves graphically representing the processes, or actions, that capture,
manipulate, store, and distribute data between a system and its environment and among
components within a system. A common form of a process model is a data-flow diagram
(DFD). With a data flow diagram, users are able to visualize how the system will operate,
what the system will accomplish, and how the system will be implemented. The old
system's data flow diagrams can be drawn up and compared with the new system's data
flow diagrams to draw comparisons to implement a more efficient system. Data flow
diagrams can be used to provide the end user with a physical idea of where the data they
input ultimately has an effect upon the structure of the whole system from order to
dispatch to report.
3.1.4.1 Level 0 DFD

12
DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system
or process being analyzed or modeled. It’s designed to be an at-a-glance view, showing
the system as a single high-level process, with its relationship to external entities. It
should be easily understood by a wide audience, including stakeholders, business
analysts, data analysts and developers.

Fig 4: Level 0 DFD

3.1.4.2 Level 1 DFD

The Level 0 DFD is broken down into more specific, Level 1 DFD. Level 1 DFD depicts
basic modules in the system and flow of data among various modules. Level 1 DFD also
mentions basic processes and sources of information.
 It provides a more detailed view of the Context Level Diagram.
 Here, the main functions carried out by the system are highlighted as we break
into its sub-processes.

13
 Fig 5: Level 1 DFD

3.1.4.3 Level 2 DFD

A level 2 data flow diagram (DFD) offers a more detailed look at the processes that make
up an information system than a level 1 DFD does. It can be used to plan or record the
specific makeup of a system. You can then input the particulars of your own system.

14
 Fig 6: Level 2 DFD

3.2 System Design

System design is the process of defining the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that

15
goes through that system. It is meant to satisfy specific needs and requirements of a
business or organization through the engineering of a coherent and well-running system.
3.2.1 Architectural Design
Architectural design is a discipline that focuses on covering and meeting the needs and
demands, to create living spaces, using certain tools and especially,
creativity. Therefore, the aim is to combine the technological and the aesthetic, despite
the general belief that architecture is only a technological task.
3.2.2 Database Schema Design
Architectural design is a discipline that focuses on covering and meeting the needs and
demands, to create living spaces, using certain tools and especially,
creativity. Therefore, the aim is to combine the technological and the aesthetic, despite
the general belief that architecture is only a technological task.
In the same way, it mixes design, understood as the creative process, and architecture,
which is based on the creation and presentation of solutions at a technical level.  By
mixing both disciplines, architectural design seeks the values and formal qualities of the
works, through spatial experiences. In general, we associate it with drawings, sketches
or outlines of a project, and it is one of its fundamental basis.
3.2.3 Interface Design
User interface design is the process designer use to build interfaces in software or
computerized devices, focusing on looks and style. Designers aim to create interface
which users find easy to use and pleasurable.
 It refers to graphical user interfaces and other forms which defines how an
individual user interacts with the digital information system.
 It is essentially a series of visual elements that users interact with the digital
device.
 It is important because it can make or break our user base.
 It creates fewer problems, increases user involvement, perfects functionality and
creates a strong link between our user and our website.
 It makes users interaction as simple and efficient as possible, in terms of
accomplishing users goals.
The partition between software running on the CPU and interface hardware is the basic
decision in interface design. We can expand on our requirements to identify several
factors that influence the decision.

16
Algorithmic complexity: Some algorithms may be hard to implement as analog or digital
circuits due to their size or the nature of the operations they perform.

Chapter 4: Implementation and Testing

4.1 Implementation
4.1.1 CASE Tools

17
CASE tools are set of software application programs, which are used to automate SDLC
activities. CASE tools are used by software project managers, analysts and engineers to
develop software system. CASE technologies are tools that provide automated assistance
for software development. Its goal is reduce the time and cost of software development
and the enhancement of the quality of the systems developed. The interest in CASE tools
and environments is based on expectations about increasing productivity, improving
product quality, facilitating maintenance, and making software engineers’ task less
odious and more enjoyable.
CASE is the use of computer-based support in the software development process; a
CASE tool is a computer-based product aimed at supporting one or more software
engineering activities within a software development process; a CASE environment is a
collection of CASE tools and other components together with an integration approach
that supports most or all of the interactions that occur among the environment
components, and between the users of the environment and the environment itself.
There are number of CASE tools available to simplify various stages of Software
Development Life Cycle such as Analysis tools, Design tools, Project management tools,
Database Management tools, Documentation tools are to name a few.
Use of CASE tools accelerates the development of project to produce desired result and
helps to uncover flaws before moving ahead with next stage in software development.
CASE tools used in this project are:
 Diagram Tools
The components of the system, data flow, control flow among the various
components of software and the structure of the system can be represented in
graphical form using diagram tools. Example: flow chart maker tool.
 Process Modeling
The software process model can be created using process modeling tools for
software development. The managers can choose a process model using process
modeling tools or make modifications depending upon the software product
requirements.
 Programming
The programming environments like integrated development environment,
library consisting of in-built modules, simulation is all included in programming

18
 tools. The development of software product is aided by these and simulation and
testing features are included.
4.1.2 Programming Languages and Tools
4.1.2.1 HTML
HTML is a markup language used by the browser to manipulate text, images, and other
content, in order to display it in the required format. HTML was created by Tim
Berners-Lee in 1991. The first-ever version of HTML was HTML 1.0, but the first
standard version was HTML 2.0, published in 1999.
HTML is the set of markup symbols or codes inserted into a file intended for display on
the Internet. The markup tells web browsers how to display a web page's words and
images. HTML documents contain HTML tags and plain text. A markup language is
used to define the text document within tag which defines the structure of web pages.
Each individual piece markup code (which would fall between "<" and ">" characters) is
referred to as an element, though many people also refer to it as a tag. Some elements
come in pairs that indicate when some display effect is to begin and when it is to end.
This language is used to annotate (make notes for the computer) text so that a machine
can understand it and manipulate text accordingly. Most markup languages (e.g.
HTML) are human-readable. The language uses tags to define what manipulation has to
be done on the text. HTML documents are also called web pages. It gives authors the
means to: Publish online documents with headings, text, tables, lists, photos, etc. Retrieve
online information via hypertext links, at the click of a button.
4.1.2.2 CSS
CSS Stands for "Cascading Style Sheet." Cascading style sheets are used to format the
layout of Web pages. They can be used to define text styles, table sizes, and other aspects
of Web pages that previously could only be defined in a page's HTML. For the style
implementation CSS is made. CSS made our system more decorative which can make the
users feel good looking site.CSS helps Web developers create a uniform look across
several pages of a Web site.
Instead of defining the style of each table and each block of text within a page's HTML,
commonly used styles need to be defined only once in a CSS document. Once the style is

defined in cascading style sheet, it can be used by any page that references the CSS file.
Plus, CSS makes it easy to change styles across several pages at once. For example, a

19
Web developer may want to increase the default text size from 10px to 12px for fifty
pages of a Web site. If the pages all reference the same style sheet, the text size only
needs to be changed on the style sheet and all the pages will show the larger text.
While CSS is great for creating text styles, it is helpful for formatting other aspects of
Web page layout as well. For example, CSS can be used to define the cell padding of
table cells, the style, thickness, and color of a table's border, and the padding around
images or other objects. CSS gives Web developers more exact control over how Web
pages will look than HTML does. This is why most Web pages today incorporate
cascading style sheets.
4.1.2.3 Java script
JavaScript was first known as Live Script, but Netscape changed its name to JavaScript,
possibly because of the excitement being generated by Java. JavaScript made its first
appearance in Netscape 2.0 in 1995 with the name Live Script.
JavaScript is a dynamic computer programming language. It is lightweight and most
commonly used as a part of web pages, whose implementations allow client-side script to
interact with the user and make dynamic pages. JavaScript is platform Independent,
which means you need to write the script once and can run it on any platform or browser
without affecting the output of the Script.
When a user requests an HTML page with JavaScript in it, the script is sent to the
browser and it’s up to the browser to do something with it. The general-purpose core of
the language has been embedded in Netscape, Internet Explorer, and other web browsers.
It means that a web page need not be a static HTML, but can include programs that
interact with the user, control the browser, and dynamically create HTML content.
4.1.2.4 MY SQL
Its name is a combination of “My”, the name of co-founders Michael Widenius's
daughter, and "SQL", the abbreviation for Structured Query Language.  MYSQL is open-
source and free software under the GNU license. Oracle Company supports it.
MYSQL is a relational database management system (RDBMS) based on the SQL
(Structured Query Language) queries. It is one of the most popular languages for
accessing and managing the records in the table. Insertion, edit, delete selection of the
data are performed through queries. Database have various tables like login table, details
of table etc. it is always written inside the PHP tag.

20
MYSQL is a relational database management system. This database language is based on
the SQL queries to access and manage the records of the table. It is easy to use. We have
to get only the basic knowledge of SQL. We can build and interact with MYSQL by
using only a few simple SQL statements. MYSQL consists of a solid data security layer
that protects sensitive data from intruders. Also, passwords are encrypted in MYSQL.
4.1.2.5 PHP
The main features of PHP is; it is open source scripting language so you can free
download this and use. PHP is a server site scripting language. It is open source scripting
language. It is widely used all over the world. It is faster than other scripting language.
Hypertext Pre-processor (PHP) is used to validate in the server side. Project was
dynamically implemented by using PHP.
It is very simple and easy to use, compare to other scripting language it is very simple and
easy, this is widely used all over the world.
It is an interpreted language, i.e. there is no need for compilation. It is faster than other
scripting language e.g. asp and jsp. Open source means you no need to pay for use php,
you can free download and use. PHP code will be run on every platform, Linux, UNIX,
Mac OS X, and Windows. PHP is case sensitive scripting language at time of variable
declaration. In PHP, all keywords (e.g. if, else, while, echo, etc.), classes, functions, and
user-defined functions are NOT case-sensitive. PHP have some predefined error reporting
constants to generate a warning or error notice.
4.1.3 Implementation Details of Modules
4.1.3.1 User module implementation:
User module include register: at first user have to register with their name, email, phone
number, address etc. After successful register user can successfully manage the data into
the system.
4.2 Level of Testing
In general, testing is finding out how well something works. In terms of human beings,
testing tells what level of knowledge or skill has been acquired. In computer hardware
and software development, testing is used at key checkpoints in the overall process to
determine whether objectives are being met. A primary purpose of testing is to detect
software failures so that defects may be discovered and corrected. Testing cannot
establish that a product functions properly under all conditions, but only that it does not
function properly under specific conditions.

21
4.2.1 Unit Testing
Unit testing is a type of software testing where individual units or components of a
software are tested. The purpose is to validate that each unit of the software code
performs as expected. Unit Testing is done during the development (coding phase) of an
application by the developers. Unit Tests isolate a section of code and verify its
correctness. A unit may be an individual function, method, procedure, module, or object.
System testing ensures that the system meets its stated design specifications. Acceptance
testing is testing by the user to ascertain whether the system developed is a correct
implementation of the software requirements specification.
This test is done to determine the working of the individual modules. The USER
REGISTRATION SYSTEM includes the various modules that are tested at the
development processes.
System includes the various modules that are tested at the development processes.
S.N Action Inputs Expected Expected result test comment Pass/
output fail
1 Enter invalid email: ab1 The email that Enter valid invalid Pass
email and hit gmail.com you have registration
email address.
submit button entered is attempt
incorrect. stopped.

2 Enter valid ab1@gmail Registration Register successfully Pass

Email and hit .com success success registered.
submit button .

4.2.2 Integration Testing

Integration testing is a type of testing meant to check the combinations of different units,
their interactions, and the way subsystems unite into one common system, and code
compliance with the requirements. It is the phase in software testing in which individual
software modules are combined and tested as a group. Integration testing is done when
two modules are integrated, in order to test the behavior and functionality of both the
module after integration. Defects in the component that has been missed during
component testing are discovered during integration testing.
4.2.3 System Testing

22
System Testing is a level of testing that validates the complete and fully integrated
software product. The purpose of a system test is to evaluate the end-to-end system
specifications. Usually, the software is only one element of a larger computer-based
system. Ultimately, the software is interfaced with other software/hardware systems.
System Testing is actually a series of different tests whose sole purpose is to exercise the
full computer-based system. It focus on testing integrations between the components and
objects that make up a system as well as test the reusable components or system to check
that they are work as expected when they are integrated with new components.
4.2.4 Alpha and Beta Testing
Alpha Testing
Alpha testing is a type of acceptance testing; performed to identify all possible
issues/bugs before releasing the product to everyday users or public. The focus of this
testing is to simulate real users by using black box and white box techniques. The aim is
to carry out the tasks that a typical user might perform. Alpha testing is carried out in a
lab environment and usually the testers are internal employees of the organization.
Beta Testing
Beta Testing of a product is performed by "real users" of the software application in a
"real environment" and can be considered as a form of external user acceptance testing.
Beta version of the software is released to a limited number of end-users of the product to
obtain feedback on the product quality. Beta testing reduces product failure risks and
provides increased quality of the product through customer validation.
4.2.5 Acceptance Testing
Acceptance Testing is a level of the software testing where a system is tested for
acceptability. The purpose of this testis to evaluate the system's compliance with the
business requirements and assess whether it is acceptable for delivery. Formal testing
with respect to user needs, requirements, and business processes conducted to determine
whether or not a system satisfies the acceptance criteria and to enable the user, customers
or other authorized entity to determine whether or not to accept the system.

4.3 Testing Methods

23
Testing can be performed without having any knowledge of the interior working of the
application as well as by having knowledge of implementation details of software system.
There are two testing methods which are black box testing and white box testing.
4.3.1 White Box testing
White-box testing(also known as clear box testing, glass box testing, transparent box
testing, and structural testing) is a method of testing software that tests internal structures
or workings of an application, as opposed to its functionality (i.e. black-box testing). In
white-box testing an internal perspective of the system, as well as programming skills, are
used to design test cases. The tester chooses inputs to exercise paths through the code and
determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-
circuit testing (ICT). White-box testing can be applied at the unit, integration and system
levels of the software testing process.

Fig: white Box Testing

4.3.2 Black Box Testing

Black-box testing is a method of software testing that examines the functionality of an
application without peering into its internal structures or workings. This method of test
can be applied to virtually every level of software testing: unit, integration, system and
acceptance. It typically comprises most if not all higher-level testing, but can also
dominate unit testing as well.

Fig: Black Box Testing

Chapter 5: Conclusion and Future Recommendations

24
5.1 lesson learnt/Outcome
The outcomes of this User registration System are as follows:
a) Users are capable to register.
b) This system reduces manual work.
c) All the data will be saved in the database.
d) It makes user data secure.
e) All the necessary fields need to be fulfilled otherwise it throw an error.
f) It tracks all the details of the user.
5.2 Conclusion
Computer has got clear advantage over the manual system. The computerized system is
more reliable, efficient and fast at the end of the project, I can say that computer play a
very crucial role in the development of firm. All the daily reports generated by the system
are to be checked by the concerned official so as to ensure that all the transactions have
been put through in appropriate accounts. Computer does maximum work with in
minimum time. Because it is used in every field so that it provides comfort and suitability
to everyone.
User Registration System provides user a good interface to the user for to register data
which is fully secured in database. To achieve this goal, we have design this system with
the help of above mentioned strategies and methodology. The system will be tested
regarding its performance and user friendly behavior with the Users Registration System.
5.3 Future Recommendations
The scope of the proposed project is to provide a simple user management page that lets
you view, search users, create new user accounts, and edit existing ones. Also provides
tools to disable or delete users, manage permissions, and issue password resets. Adding
up, our system will also help in upgrading the already existing system to a new automated
one which has the following benefits:
 Secure: The data will be accessed such as the personal details of a user will be
secure.
 Cost reduction: Due to new automated system, reduction of paper work will
definitely save expenses of the company as compared to the manual system.

 Less time Consuming: since user won't have to go to different websites and then
determine the best deal. It would be less time consuming and much easier for

25
 them.
We are looking forward to develop the system like this which makes user feel more
comfortable, secure and easy to interact according to the needs of the user in this modern
era.

References

[1] B. Chapagain, Scrpting Language, KEC Publication AND Distribution

26
PVT.LTD.Kathmandu, 207
[2] I. Chaudhary, Database Management System, KEC Publication AND
Distribution PVT.LTD.Kathmandu, 2077.
[3] According to Clerk E. and Jr (2008) Records Management
[4] Hill (1996) Key to Record Management

27
1