SUMMER INTERNSHIP REPORT

SUMMER INTERNSHIP REPORT

Password Strength Checker
A report submitted in partial fulfillment of the requirements for the award of degree of

BACHELOR OF TECHNOLOGY

in

COMPUTER SCIENCE AND BUSINESS SYSTEMS

By

CHELAMKURI VIRAJ
Regd.No:22B91A5710

Under Supervision of Mr. Jaipurk Pranav

BLACKBUCK ENGINEERS PVT.LTD.

(Duration: 27rd May 2024 To 20th July 2024)

&

Prof. B. V D S Sekhar
Dept. of IT
SRKR Engineering College(A)

DEPARTMENT OF INFORMATION TECHNOLOGY

(AI&DS, CSBS, IT)
S R K R ENGINEERING COLLEGE (Autonomous)
Approved by AICTE, permanently affiliated to JNTUK, Kakinada
China Amiram, Bhimavaram, Andhra Pradesh-534204
September-2024

i
S.R.K.R Engg. College (A) Department of IT/AI&DS/CSBS
 SUMMER INTERNSHIP REPORT

S R K R ENGINEERING COLLEGE
(Autonomous)
China Amiram::Bhimavaram

DEPARTMENT OF INFORMATION TECHNOLOGY

(AI&DS, CSBS, IT)

CERTIFICATE

This is to certify that the Internship report work titled “ CYBERSECURITY ”, submitted by
CH.VIRAJ (Regd. No.: 22B91A5710) during 2024 – 2025 academic year, in partial fulfillment of the
requirements for the award of the degree of BACHELOR OF TECHNOLOGY in Computer
science and business systems at BLACKBUCK ENGINEERS PVT.LTD, Tirupati.

Internship Mentor
Dr. K Kishore Raju
Associated professor, IT Dept.

Internship Coordinator
Dr. K Kishore Raju
Associated professor, IT Dept.

ii Prof. P. Ravi Kiran Varma

Head of IT Department

DECLARATION

This Internship Work report entitled “Password Strength Checker” has been carried out by us in the

partial fulfillment of the requirements for the award of the degree of B.Tech (IT/AI&DS/CSBS full

form), S.R.K.R Engineering College(A). We hereby declare this Internship work report has not been

submitted to any of the other university/Institute for the award of any other degree/diploma.

S.R.K.R Engg. College (A) Department of IT/AI&DS/CSBS

 SUMMER INTERNSHIP REPORT

Name Register No Signature

CERTIFICATION OF EXAMINATION

This to certify that I have examined the concept and hereby accord my approval of it as a
Internship Work done by CH.VIRAJ(22B91A5710) entitled “ CYBERSECURITY” carried
out and presented in a manner required for its acceptance on partial fulfillments for the award
of the degree of BACHELOR OF TECHNOLOGY in COMPUTER SCIENCE AND
BUSINESS SYSTEMS for which it has been submitted.

This approval does not necessarily endorse or accept every statement made opinion
expressed or conclusions drawn as recorded in the Internship report it only signifies the
acceptance of the report for the purpose for which submitted.

Departmental Committee:

Signature

Internship Mentor :

Senior Faculty :

External Examiner :

ii
HOD : i

S.R.K.R Engg. College (A) Department of IT/AI&DS/CSBS

 SUMMER INTERNSHIP REPORT

PROOF
of

INTERNSHIP REGISTRATION
(Approval e-mail / Approval Letter)

S.R.K.R Engg. College (A) i Department of IT/AI&DS/CSBS

v
 SUMMER INTERNSHIP REPORT

iii
 SUMMER INTERNSHIP REPORT

ACKNOWLEDGEMENT

First I would like to thank Mr. Jaipurk Pranav, Head, of BLACKBUCK

ENGINEERS PVT.LTD, Tirupati for giving me the opportunity to do an
internship within the organization.

I also would like all the people that worked along with me BLACKBUCK
ENGINEERS PVT.LTD, Tirupati with their patience and openness they created
an enjoyable working environment.

It is indeed with a great sense of pleasure and immense sense of gratitude that I
acknowledge the help of these individuals.

I am highly indebted to Principal Prof. K V. Murali Krishnam Raju for the

facilities provided to accomplish this internship.

I would like to thank my Head of the Department Prof. P. Ravi Kiran Varma for
his constructive criticism throughout my internship.

I would like to thank Dr. K. Kishore Raju internship coordinator Department of IT

for their support and advices to get and complete internship in above said organization.

I am extremely great full to my department staff members and friends who helped
me in successful completion of this internship.

CH.VIRAJ

(22B91A5710)

iv
 SUMMER INTERNSHIP REPORT

ABSTRACT

During my cybersecurity internship, I developed a Password Strength Checker, a tool to enhance

password security and mitigate cyber threats. The tool analyzes passwords based on length,
complexity, entropy, and patterns like dictionary words or repetitive sequences. Using advanced
algorithms, it categorizes passwords as weak, moderate, or strong, offering real-time feedback to
users. The project also educates users on best password practices, such as avoiding predictable
patterns and using multi-factor authentication. A password generator feature recommends secure,
random passwords that comply with modern security standards. This project involved Python
programming and cryptographic concepts, providing a hands-on understanding of cybersecurity
principles. It underscores the importance of user awareness in protecting sensitive data and serves
as a foundation for exploring advanced authentication systems.

Organization Information:

Blackbucks Organization is a prominent player in the field of technology and cybersecurity,

committed to providing innovative solutions for modern challenges. During my internship, I
contributed to their focus on enhancing digital security by developing a Password Strength
Checker. The organization emphasizes fostering talent through hands-on projects, encouraging
interns to apply theoretical knowledge to real-world scenarios. Blackbucks is known for its
dynamic work environment and dedication to cutting-edge technologies. It prioritizes user
awareness in cybersecurity, integrating education into its tools and services. My experience at
Blackbucks allowed me to gain practical skills in Python programming, cryptographic concepts,
and algorithm development, while aligning with the organization’s mission of securing sensitive
data in an increasingly digital world.

Programs and opportunities:

Blackbucks Organization offers dynamic internships and training programs in cybersecurity,

data science, and software development, providing hands-on experience with real-world projects.
It fosters innovation by encouraging interns to tackle emerging challenges. The organization also
conducts workshops, webinars, and hackathons to nurture talent and build expertise in cutting-
edge technologies. Blackbucks partners with industry leaders to deliver impactful solutions,
creating career growth opportunities for aspiring professionals. Its commitment to skill
development ensures participants are well-equipped for competitive tech roles.
v
 SUMMER INTERNSHIP REPORT

Learning Objectives/Internship Objectives

 Internships are an opportunity to apply theoretical knowledge to practical challenges,

such as creating tools to strengthen digital security.

 Internships are platforms to enhance programming and cryptographic skills, enabling

participants to tackle real-world problems effectively.

 Internships are designed to cultivate problem-solving abilities, fostering innovative

solutions for complex cybersecurity issues.

 Internships are professional growth experiences, offering hands-on learning in

collaborative and industry-focused settings.

 Internships are avenues to develop user-centric solutions, educating individuals about

better security practices and promoting digital safety.

vi
 SUMMER INTERNSHIP REPORT

WEEKLY OVERVIEW OF INTERNSHIP ACTIVITIES

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

8/05/23 Monday Introduction of .NET frame work
1st WEEK

9/05/23 Tuesday Features of .NET { IDE,CLR,CTS}

10/05/23 Wednesday Introduction of C# .NET
11/05/23 Thursday Introduction of console application
12/05/23 Friday Continuing console applications
13/05/23 Saturday Understanding different types of class and collection

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

29/05/23 Monday Understanding classic ASP VS ASP.NET
WEEK

30/05/23 Tuesday Introduction to ASP.NET web server controls

31/05/23 Wednesday Working with different web server controls
01/06/23 Thursday Standard controls , validation controls
2th

02/06/23 Friday Introduction to data control in depth

03/06/23 Saturday Project session

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

15/05/23 Monday Introduction to windows application
16/05/23 Tuesday Understanding controls like [label, button] etc.,
17/05/23 Wednesday Continuing understanding controls
WEEK

18/05/23 Thursday Introduction to windows services

19/05/23 Friday Continuing windows services
3nd

20/05/23 Saturday Introduction to class libraries

vii
 SUMMER INTERNSHIP REPORT

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

29/05/23 Monday Understanding classic ASP VS ASP.NET
4th WEEK

30/05/23 Tuesday Introduction to ASP.NET web server controls

31/05/23 Wednesday Working with different web server controls
01/06/23 Thursday Standard controls , validation controls
02/06/23 Friday Introduction to data control in depth
03/06/23 Saturday Project session

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

29/05/23 Monday Understanding classic ASP VS ASP.NET
WEEK

30/05/23 Tuesday Introduction to ASP.NET web server controls

31/05/23 Wednesday Working with different web server controls
01/06/23 Thursday Standard controls , validation controls
5th

02/06/23 Friday Introduction to data control in depth

03/06/23 Saturday Project session

DATE DAY NAME OF THE TOPIC/MODULE COMPLETED

WEEK

05/06/23 Monday Design& Analysis

06/06/23 Tuesday Coding
07/06/23 Wednesday Testing
6th

viii
 SUMMER INTERNSHIP REPORT

INDEX

S.no CONTENTS Page no

1. Introduction………………………………………………………………………………1

1.1 Modules………………………………………………………………………………2

2. Analysis……………………………………………………………………………… 3

3. Software requirements specification ……………………………………………………4

4. Technology………………………………………………………………………………5

4.1 ASP.NET…………………………………………………………………………….5

4.2 ADP.NET……………………………………………………………………………6

4.3 C#.NET………………………………………………………………………………7

4.4 JAVA………………………………………………………………………………..7

4.5 SQL Data Base………………………………………………………………………8

5. Coding…………………………………………………………………………………..10

6. Screenshots………………………………………………………………………………11

7. Conclusios………………………………………………………………………………16

8. Bibilography……………………………………………………………………………17

1. INTRODUCTION
The complexity of business environments constantly grows, both with regard to the amount
of data relevant for making strategic decisions and the complexity of included business
processes. Today’s dynamic and competitive markets often imply rapid (e.g., near real-time)
and accurate decision making. Relevant data are stored across a variety of data repositories,
possibly using different data models and formats, and potentially crossed with numerous
external sources for various context aware analysis. A data integration process combines data
residing on different sources and provides unified view of this data for a user [1]. For
example, in a data warehousing (DW) context, data integration is implemented through
extract-transform- that extracts, cleans, and transforms data from multiple, often
heterogeneous data sources and Finally, delivers data for further analysis. There are various
challenges related to data Flow design. Here we consider two: design evolution and design
complexity.

A major challenge that BI decision-makers face relates to the evolution of business

requirements. These changes are more frequent at the early stages of a DW design project and
9
 SUMMER INTERNSHIP REPORT

in part, this is due to a growing use of agile methodologies in data Flow design and BI
systems in general. But changes may happen during the entire DW lifecycle. Having an up-
and-running DW system satisfying an initial set of requirements is still a subject to various
changes as the business evolves. The data Flows populating a DW, as other software
Artefacts, do not lend themselves nicely to evolution events and in general, due to their
complexity, maintaining them manually is hard. The situation is even more critical in today’s
BI settings, where on-the-fly decision making requires faster and more efficient adapting to
changes. Changes in business needs may result in new, changed or removed information
requirements. Thus having an incremental and agile solution that can automatically absorb
occurred changes and produce a Flow satisfying the complete set of requirements would
largely facilitate the design and maintenance of data-intensive Flows.

In an enterprise environment data is usually shared among users with varying technical skills
and needs, involved in different parts of a business process. Typical real-world data-intensive
workloads have high temporal locality, having 80% of data reused in a range from minutes to
hours. However, the cost of accessing these data, especially in distributed scenarios, is often
high. At the same time, intertwined business processes may also imply overlapping of data
processing. For instance, a sales department may analyze the revenue of the sales for the past
year, while Finance may be interested in the overall net profit. Computing the net profit can
largely benefit from the total revenue already computed for the sales department and thus, it
could benefit from the sales data Flow too. The concept of reusing partial results is not new.
Software and data reuse scenarios in data integration have been proposed in the past, showing
that such reuse would result in substantial cost savings, especially for large, complex business
environments. Data Flow re use could result in a significant reduce in design complexity, but
also in intermediate Flow executions and thus, in total execution time too.

10
 SUMMER INTERNSHIP REPORT

2. SYSTEM ANALYSIS

2.1 Existing System:

In an Existing we address these challenges and present an approach to efficient, incremental

consolidation of data-intensive flows. Following common practice, our method iterates over
information requirements to create the final design. we show how to efficiently accommodate
a new information requirement to an existing design and also, how to update a design in lieu
of an evolving information requirement. The final design satisfying all requirements
comprises a multi-flow. As ‘coal’ is formed after the process and extreme compaction of
layers of partially decomposed materials1, Co Al processes individual data flows and
incrementally consolidates them into a unified multi-flow.

2.2 Proposed System

Following the previously proposed set of flow transformations in the context of ETL
processes in Co Al we extend this set considering also the associative property of n-array
operations (e.g., Join) and thus rely on the following four flow transformations used for
reordering the operations. Swap Applied to a pair of adjacent unary operations, it
interchanges the order of these operations. Distribute/Factorize. Applied on a unary
operation over an adjacent n-array operation, it respectively distributes the unary operation
over the adjacent nary operation or factorizes several unary operations over the adjacent n-
array operation. Merge/Split. Applied on a set of adjacent unary operations, it respectively
merges several operations into a single unary operation or splits a unary operation into
several unary operations. Re-associate. Applied on a pair of mutually associative n-array
operations, it interchanges the order in which these operations are executed.

3. SYSTEM ARCHITECTURE AND MODULE DESCRIPTION

3.1 System Architecture:

11
 SUMMER INTERNSHIP REPORT

Fig: Sample Architecture

3.2 Module Description:

Need to include Modules and clear explanation

Shopper:
======
1) User registers the site.
2) Products will be showed
3) If user selected the product and then save
4) User selected product is send to the Order.
5) If user wants to buy the product they can also buy.

Supplier
=======
1) send product details
2) send payment verification
3) Store buying detail
4) Store line items using join product and order

12
 SUMMER INTERNSHIP REPORT

4. SOFTWARE REQUIREMENTS SPECIFICATIONS

4.1 System configurations

The software requirement specification can produce at the culmination of the analysis task.
The function and performance allocated to software as part of system engineering are refined
by established a complete information description, a detailed functional description, a
representation of system behavior, and indication of performance and design constrain,
appropriate validate criteria, and other information pertinent to requirements.

4.2 Software Requirements:

• Operating system : Windows 7 Ultimate.

• Coding Language : MVC 4 Razor
• Front-End : Visual Studio 2012 Professional.
• Data Base : SQL Server 2008.

4.3 Hardware Requirement:

• System : Pentium IV 2.4 GHz.

• Hard Disk : 1TB.

• Ram : 4GB.

13
 SUMMER INTERNSHIP REPORT

5. TECHNOLOGY

a. ASP.NET

ASP.NET is a web development platform, which provides a programming model,

a comprehensive software infrastructure and various services required to build up robust web
applications for PC, as well as mobile devices.

ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and
policies to set a browser-to-server bilateral communication and cooperation.

ASP.NET is a part of Microsoft .NET platform ASP.NET applications are

compiled codes, written using the extensible and reusable components or objects present in
.NET framework. These codes can use the entire hierarchy of classes in .NET framework.

ASP.NET web forms extend the event-driven model of interaction to the web
applications. The browser submits a web form to the web server and the server returns a full
markup page or HTML page in response.

All client side user activities are forwarded to the server for tasteful processing.
The server processes the output of the client actions and triggers the reactions.

Now, HTTP is a stateless protocol. ASP.NET framework helps in storing the information
regarding the state of the application, which consists of:

 Page state
 Session state

The page state is the client state, i.e., the content of various input fields in the
web form. The session state is the collective information obtained from various pages the
user visited and worked with, i.e., the overall session state. To clear the concept, let us take
an example of a shopping cart.

User adds items to a shopping cart. Items are selected from a page, say the items
page, and the total collected items and price are shown on a different page, say the cart page.
Only HTTP cannot keep track of all the information coming from various pages. ASP.NET
session state and server side infrastructure keeps track of the information collected globally
over a session.

14
 SUMMER INTERNSHIP REPORT

The ASP.NET runtime carries the page state to and from the server across page
requests while generating ASP.NET runtime codes, and incorporates the state of the server
side components in hidden fields.

This way, the server becomes aware of the overall application state and operates
in a two-tiered connected way.

The ASP.NET component model provides various building blocks of ASP.NET

pages. Basically it is an object model, which describes:

ASP.NET is a technology, which works on the .NET framework that contains

all web-related functionalities. The .Net frame work is made of an object-oriented hierarchy.
An ASP.NET web applications is made of pages. When a user requests an ASP.NET page,
the IIS delegates the processing of the page to the ASP.NET runtime system.

The ASP.NET runtime transforms the .aspx page into an instance of a class,
which inherits from the base class page of the .Net framework. Therefore, each ASP.NET
page is an object and all its components i.e., the server-side controls are also objects.

b. ADO.NET

As you develop applications using ADO.NET, you will have different

requirements for working with data. In some cases, you might simply want to display data on
a form. In other cases, you might need to device a way to share information with another
company.

No matter what you do with data, there are certain fundamental concepts that you
should understand about the data approach in ADO.NET. You might never need to know
some of the details of data handling- for example, you might never need to directly edit an
XML file containing data- but it is very useful to understand the data architecture in
ADO.NET, what the major data components are, and how the pieces fit together.

This introduction presents a high-level over view of these most important

concepts. The topic deliberately skips over many details- for example, there is much more to
data sets than what is mentioned here- in favour of simply introducing you to ideas behind the
data integration in ADO.NET.

ADO.Net does not continuously live connections. In traditional client/server

applications, components establish a connection to a data base and kept it open while the
application is running. For a variety of reasons, this approach is impractical in many
applications.

Open database connections take up valuable system resources. In most cases,

databases can maintain only a small number of concurrent connections. The overhead of
maintaining these connections detracts from overall application performance.

15
 SUMMER INTERNSHIP REPORT

Similarly, applications that require an open database connection are extremely

difficult to scale up. An application that does not scale up well might perform acceptable with
four users but will likely not do so with hundreds.ASP.NET Web applications in particular
need to be easily scalable, because traffic to a website can go up by orders of magnitude in a
short period.

A model based on always connected data can make a difficult and impractical to
exchange data across application and organizational boundaries using a connected
architecture. If two components need to share the same data, both have to be connected, and a
way must be devised for the components to pass data back and forth.

For all the reasons, data accessed with ADO.NET is designed around an
architecture that uses connections sparingly. Applications are connected to the database only
long enough to fetch or update the data. Because the database is not holding onto connections
that are largely idle, it can service many more users.

c. Overview of C#.Net

 C# is a simple, modern, object oriented, and type –safe programming language derived from
C and C++.
 It will immediately be familiar to C and C++ programmers.
 C# aims to combine the high productivity of visual basic and the raw power of C++
 Visual C#.NET is Microsoft’s C# development tool.
 It includes an interactive development environment, visual designers for building windows
and web applications, a compiler and a debugger.
 Visual C#.NET is part of a suite of products, called Visual Studio .NET, that also includes
Visual Basics .NET, Visual C++.NET and the Jscript scripting language.
 The .NET frame work defines a “Common Language Specification” (CLS), a short of lingua
franca that ensures seamless interoperability between CLS-complaint languages and class
libraries.
 For C# developers this means even though C# is a new language, it has complete access to
the same rich class libraries that are used by seasoned tools such as Visual Basic.NET and
Visual C++.NET.
d. JAVA

JavaScript is an interpreter, client-side, event-based, object oriented scripting language

that you can use to add dynamic interactivity to your web pages.
JavaScript scripts are written in plain text, like HTML, XML, Java, PHP and just about
any other modern computer code. In this code, we will use Windows Note Pad to create
and edit our JavaScript code, but there are a large number of alternatives available.
Note Pad is chosen to demonstrate JavaScript’s immediacy and simplicity.
You can use JavaScript to achieve any of the following:

16
 SUMMER INTERNSHIP REPORT

 Create special effects with images that give the impression that a button is either highlighted
or depressed whenever the mouse pointer is hovered over it.
 Validate
 the fly” without the need for a server-side language like PHP. JavaScript is not Java, though
if you come from a Java background, you will notice that both languages look similar when
written. Java is a full featured and comprehensive programming language similar to C or C+
+, and although JavaScript can interact with Java web applications, the two should not be
confused.
Different web browsers will run your JavaScript in different, sometimes incompatible
ways. In order to work around this, it is often necessary to use JavaScript itself to detect the
capabilities of the browser in which it finds itself, and alter its operation depending on the
result.
To revisit the original definition in this chapter, note the following points:
 Interpreted refers to the fact that JavaScript code is executed (acted on) as it is loaded into
the browser. This is a change of pace from compiled languages like Java, which check
your program thoroughly before running a single line of code, and can have many
implications that can catch you out if you are from a non-interpreted programming
background.
 Client-side has been defined already in the previous chapter.
 Event-based refers to JavaScript’s ability to run certain bits of code only when a specified
event occurs. An event could be the page being loaded, a form being submitted, a link
being clicked, or an image being pointed at by a mouse pointer.
 Object-oriented signals that JavaScript’s power to exert control over an HTML page
is based on manipulating objects within that page.
 If you are familiar with object-oriented programming, you will be aware of some of
the power that this can bring to the coding environment.
e. DATABASE

About Microsoft SQL Server 2008

Microsoft SQL server is a Structured Query Language (SQL) base, client/server

relational database. Each of these terms describes a fundamental part of the architecture of
SQL server.

17
 SUMMER INTERNSHIP REPORT

A database is similar to a data file in that it is storage place for data. Like a data
file, a database does not present information directly to a user, the user runs an application
that accesses data from the database and presents it to the users in an untreatable format. A
database typically ha two components: the files holding the physical database access data.

The DBMS is responsible for enforcing database structure, including:

 Maintaining the relationships between data in the database.

 Ensuring that data is stored correctly, and the rules that defining data relationships are not
violated.
 Recovering all data to a point of known consistency in case of system failures.

Relational Database

There are different ways to organize data in a database but relational databases are
one of the most effective. Relational database systems are an application of mathematical set
theory to the problem of effectively organizing data. In a relational database is collected into
tables called relations in relation theory.

When organizing data into tables, you can usually find many different ways to
define tables. Relational database theory defines a process, normalization, which ensures that
the set of tables you define will organize our data effectively.

Client/Server

In Client/Server system the server is a relatively large computer in a central

location that manages a resource used by many people. When individuals need to use the
resource, they connect over the network from their computers, or clients, to the server.

Examples of

While SQL server is design to work as a server in a Client/Server network, it is

also capable of working as a stand-alone database directly on the client. The scalability and
ease of use features of SQL server allows it to work efficiently on a client without consuming
too many resource.

Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and statements
(language) defined by the DBMS software. There are several different languages that can be
used with relational database; the most common is SQL. Both the American national
standards institute (ANSI) and the International Standards Organization (ISO) has defined
standards for SQL.

6. SYSTEM IMPLEMENTATION and RESULTS

18
 SUMMER INTERNSHIP REPORT

6.1 Implementation Details:

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master"

AutoEventWireup="true" CodeFile="reg.aspx.cs" Inherits="reg" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<style type="text/css">
.style2
{
width: 57%;
}
</style>
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<table class="style2" align="center">
<tr>
<td colspan="2" style="text-align: center">
<strong>User Registration Form</strong></td>
</tr>
<tr>
<td>
Name</td>
<td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
Email</td>
<td>
<asp:TextBox ID="TextBox2" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
Mobile</td>
<td>
<asp:TextBox ID="TextBox3" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
Gender</td>
<td>
<asp:RadioButtonList ID="RadioButtonList1" runat="server"
RepeatDirection="Horizontal">
<asp:ListItem>Male</asp:ListItem>
<asp:ListItem>Female</asp:ListItem>
</asp:RadioButtonList>
</td>
19
 SUMMER INTERNSHIP REPORT

</tr>
<tr>
<td>
UserId</td>
<td>
<asp:TextBox ID="TextBox4" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
Password</td>
<td>
<asp:TextBox ID="TextBox5" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td>
<asp:Label ID="Label1" runat="server" style="font-weight: 700"></asp:Label>
</td>
<td>
<asp:Button ID="Button1" runat="server" onclick="Button1_Click"
Text="Register" />
</td>
</tr>
</table><br /><br /><br />
</asp:Content>

6.2 Results:

Need to place output analysis of your Internship

20
 SUMMER INTERNSHIP REPORT

7. OUTPUT SCREENS

Home page:

Registration page:

21
 SUMMER INTERNSHIP REPORT

Login Page:

22
 SUMMER INTERNSHIP REPORT

8. CONCLUSION

We have presented Co Al, our approach to facilitate the incremental

consolidation of data-intensive Flows. Co Al starts from data Flows that satisfy single
information requirements. Iteratively, Co Al Identifies different possibilities for integrating
new data Flows into the existing multi- Flow, focusing on the maximal data Flow reuse.
Finally, Co Al suggests a unified data Flow design evaluating it with the user-specified cost
model. We have developed a prototype that implements the complete functionality of Co Al.
We used it to evaluate the efficiency, scalability, and the quality of the output solutions of our
approach, reporting the improvement of the overall execution time as well as other benifits of
integrated multi- Flows.
The final goal of our overall work is to provide an end-to-end platform for self-
managing the complete lifecycle of BI solutions, from information requirements to
deployment and execution of data-intensive Flow

23
 SUMMER INTERNSHIP REPORT

9. BIBLOGRAPHY

The following books are referred during the analysis and execution phase of the project

1. M. Lenzerini, “Data integration: A theoretical perspective,” in PODS, 2002, pp. 233–

246.

2. D. Caruso, “Bringing Agility to Business Intelligence,” February 2011, Information

Management,http://www.information-management.com/infodirect/2009191/business
intelligence metadata analytics ETL data management-10019747-1.html.

3. R. Hughes, Agile Data Warehousing: Delivering world-class business intelligence systems

using Scrum and XP. IUniverse, 2008.

4. Y. Chen, S. Alspaugh, and R. Katz, “Interactive analytical processing in big data systems:
A cross-industry study of map reduce workloads,” Proceedings of the VLDB Endowment,
vol. 5, no. 12, pp. 1802–1813, 2012.

WEBLINKS:
 www.c#tutorial.com - covering all the most important C# concepts. This tutorial is
primarily for new users.
 www.DotnetSpider.com - what is the .NET all about? For sample projects.

24