PROJECT REPORT IN ASP.NET ON E-Advertisement Submitted in partial fulfillment of the requirements. For the award of the certificate of Summer Training In ASP.NET Submitted by: Amish Batra(0631503107) Romit Chhabra(0841503107) Dushyant Sharma(0881503107) IT- 5 th Semester Maharaja Surajmal Institute Of Technology 1
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
PROJECT REPORT
IN
ASP.NET
ON
E-Advertisement
Submitted in partial fulfillment of the requirements.
For the award of the certificate of
Summer Training
In ASP.NET
Submitted by:
Amish Batra(0631503107)
Romit Chhabra(0841503107)
Dushyant Sharma(0881503107)
IT- 5th Semester
Maharaja Surajmal Institute Of Technology
1
INDEX
1.) Abstract2.) .Net3.) Asp.net4.) .Net Framework5.) .Net vs. Java6.) Companies using asp.net7.) Why we have used Asp.net in this project?8.) Project Objective9.) Introduction10.) System Analysis11.) Requirements to achieve the goal12.) Software engineering paradigms applied13.) Testing14.) Analysis Modeling15.) Source Code16.) Output17.) Conclusion18.) System Requirements19.) Bibliography
2
ABSTRACT
The website e-advertisement runs on the pc having visual studio. This website is about
advertising on the net in which one can chose/advertise a specific brand or a choice from
different brands can be made. It provides a facility in which one can advertise one or more
items or can just browse & leave the site. This website has been made compatible for all age
groups of people from all kinds of fields. The website is updated on the regular basis
according to the needs of people. Exciting offers are provided to maintain the charm amongst
the people.
3
.NET
Microsoft .NET is Microsoft's new Internet strategy.
.NET was originally called NGWS.
NGWS - Next Generation Windows Services
Before the official announcement of .NET, the term NGWS was used for Microsoft's plans for
producing an "Internet-based platform of Next Generation Windows Services".
The Microsoft .NET strategy was presented by Microsoft officials to the rest of the world in
June 2000:
.NET is Microsoft's new Internet and Web strategy
.NET is NOT a new operating system
.NET is a new Internet and Web based infrastructure
.NET delivers software as Web Services
.NET is a framework for universal services
.NET is a server centric computing model
.NET will run in any browser on any platform
.NET is based on the newest Web standards.
4
The .NET plan includes a new version of the Windows operating system, a new version
of Office, and a variety of new development software for programmers to build Web-
based applications.
The background for .NET is part of Microsoft's new strategy to keep Windows the
dominant operating system in the market, as computing begins to move away from
desktop computers toward Internet enabled devices, such as hand-held computers and
cell phones.
The most visual components of the new .NET framework are the new Internet
Information Server 6.0, with ASP.NET and ADO.NET support, Visual Studio.NET
software tools to build Web-based software, and new XML support in the SQL Server
2000 database.
Bill Gates is supervising the .NET project
5
ASP.NET
ASP.NET is a web application framework developed and marketed by Microsoft, that
programmers can use to build dynamic web sites, web applications and web services. It was
first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to
Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common
Language Runtime (CLR), allowing programmers to write ASP.NET code using any
supported .NET language. ASP.NET can be used to create anything from small, personal
websites through to large, enterprise-class web applications.
Extension
Microsoft has released some extension frameworks that plug into ASP.NET and extend its
functionality. Some of them are:
ASP.NET AJAX
An extension with both client-side as well as server-side components for writing ASP.NET
2) .Net is Language independent, so if the team has multiple skill expertise C#, VB.NET, C++, developers can still work on the same project with different skill set.
3) MS technologies provides RAD (rapid application development) to deliver project faster, customers always prefer faster delivery.
4) Debugging is very effort-less therefore, can fix the bugs quicker.
5) Deployment is very easy and simple.
6) Ajax implementation is simple & easy.
7) It is a user friendly as you have to only click and drag the controls on the form events is
automatically generated.
8) It is faster development environment we can create application easily.
9) .NET 2005 reduces the code up to 70% because of its build in controls.
10) One can easily developed the application with less effort compare to JAVA.
Companies using ASP.NET today to provide solutions to their customers
16
MySpace.com Costco.com
Dell.com HSN.com
Legos.com LondonStock.com
17
Match.com Monster.com
NHS.com NewEgg.com
Why we have used ASP.NET for this project?
18
ASP.NET drastically reduces the amount of code required to build large applications.
ASP.NET makes development simpler and easier to maintain with an event-driven,
server-side programming model.
ASP.NET pages are easy to write and maintain because the source code and HTML are
together.
The source code is executed on the server. The pages have lots of power and flexibility
by this approach.
The source code is compiled the first time the page is requested. Execution is fast as the
Web Server compiles the page the first time it is requested. The server saves the
compiled version of the page for use next time the page is requested.
The HTML produced by the ASP.NET page is sent back to the browser. The
application source code you write is not sent and is not easily stolen.
ASP.NET makes for easy deployment. There is no need to register components because
the configuration information is built-in.
The Web server continuously monitors the pages, components and applications running
on it. If it notices memory leaks, infinite loops, other illegal software or activities, it
seamlessly kills those activities and restarts itself.
ASP.NET validates information (validation controls) entered by the user without
The analysis model must achieve three primary objectives: -
1. To describe the requirements of the customer.
2. To establish a basis for the creation of a software design.
3. To define a set of requirements that can be validated once software is built.
System Level Goals
Data security.
The application should be error free.
Data integrity should be maintained.
Certain data control methods should be tracked.
Easy understanding of the working of the Institution.
24
Requirements to achieve the goals
INPUTS
USER DETAILS (user name, password)
PRODUCT DETAILS (product description, price) (Entered by advertiser)
ADVERTISER DETAILS
OUTPUTS
PRODUCT DETAILS
ADVERTISER DETAIL
USER DETAIL.
SOFTWARE ENGINEERING PARADIGMS APPLIED
25
Introduction:
Software engineering is a layered technology, which comprises of four independent
layers as a quality focus layer, the process layer, the methods layer and the tools layer.
The foundation for the software engineering is the process layer and together with the
technology layer helps the rational and timely development of computer software. The
method layer provides a technical way to perform a broad array of tasks regarding
requirements analysis, design, program construction, testing and maintenance. The tools
lays encompasses the software engineering tools to provide automated or semi automated
support for the process need the methods.
In real world the software development is a teamwork which incorporate a development
strategy the encompasses the process, methods, and tools layers and so the strategy is termed
as a process model or Software Engineering Paradigms.
According to Fritz Bauer “Software engineering is the establishment and use of sound
engineering principles in order to obtain economically software that is reliable and
works efficiently on real machines”. There are several models suggested to go through the
software process. The one most suitable & we opted the linear sequential model to develop
the software.
(We have followed the water fall model approach)
The Water Fall Model
We use this type of model in three conditions:
Our budget is unlimited.
26
Time have no bar. &
Our staff is categorized in class specialist.
The Waterfall model suggests a systematic and sequential approach to the software
development. The very first phase starts from the system level and progresses through
analysis, design, coding, testing, and support. A pictorial view of opted model to
develop the software is depicted in figure.
SOFTWARE REQUIREMENT ANALYSIS:
In the very first approach of software development the requirements gathering process is
performed and later intensified and focused on the software. To understand the various
27
System/Information Engineering
Analysis
Design
Coding
Testing
Water Fall Model
characteristics of the software to be built, first we must have to understand the information
domain for the software, and the required function, behavior, performance, and interface.
Requirements for both the system and the software are documented and must be reviewed
with the customer. Keeping this software engineering paradigm we maintained a proper
documentation of the
Customer’s requirement (Cost Engineering Department) and always reviewed with the
department (the customer). It helped us to minimize the distance between the actual
requirement and the software required and hence kept the customer’s satisfaction very high.
DESIGN:
The design is almost and always a multi step process and focuses on four
distinct attributes of a program:
1. Data Structure
2. Software Architecture
3. Interface Representations and
4. Procedural Detail.
The design process translates requirements into a representation of the
software that can be assessed for quality before coding begins. Like
requirements, the design is documented and becomes part of the software
configuration.
Code Generation:
28
The design is translated into a machine-readable form using some programming tools.
TESTING:
Once the design is converted into machine-readable form the program testing phase starts.
The testing process on our software mainly focused on the logical internals of the software,
ensuring that all statements have been tested properly, and on the functional externals.
Through testing we mainly intended to uncover errors and ensured that the defined input
produces the desired results that agree with required results in the specification.
MAINTENANCE:
Software will undoubtedly undergo change after it is delivered to the customer. Change will
occur due to either errors have been encountered or the software have been adapted to
accommodate in its external environment or the customer requires functional or performance
enhancements. Software support/ maintenance reapplies each of the preceding phases to an
existing program rather than a new one. The linear nature of the classic life cycle worked
perfect without any “blocking states” as the project is to be developed by me and my team
member only & hence we started the next phase as soon as the current phase is finished
without waiting for any one else.
29
TESTING
A systematic and wholly procedural plan for testing was adopted the procedure while
implementing testing went in hand with preparing a unit test plan.
Test the modules thoroughly- cover all the access paths. Generate
enough data to cover all the access paths arising from conditions.
Test the modules by passing wrong data.
To test different access paths, look at the conditional statement. Enter
some data in the test file, which would satisfy the condition and again
test the script. Repeat this process many times.
After each test, analyze the log file to ensure proper, understandable
and useful messages are present in the log file.
Test for locking by invoking multiple concurrent processes.
TESTING OBJECTIVES :
Testing is a process of executing a program with the intent of finding an error.
A goal test case is one that has a probability of finding an as yet undiscovered error.
A successful test is one that uncovers an as yet undiscovered error.
TESTING PRINCIPLE
All tests should be traceable to customer requirements.
30
Test should be planned long before testing begins.
The testing should begin “in the small” and progress towards testing “in the large”.
Exhaustive testing is not possible.
To be most efficient, an independent third party should conduct testing.
CHARACTERS OF A GOOD TEST :
A good test has a high probability of finding an error.
A good test is not redundant.
A good test should be best of breed.
A good test should be neither too simple nor too complicated.
TYPES OF TESTING :
WHITE BOX TESTING
BLACK BOX TESTING
31
WHITE BOX TESTING
White Box testing which is performed early in the testing process is also called glass-box
testing. Using white box testing, the software engineer can derive test cases that
1. Guarantee that all the independent paths within the module have been exercised at
least once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structure to assure their validity.
BLACK BOX TESTING
Black box testing to be applied during later stage of testing. Black box testing focuses
on the functional requirement of the software. Black box testing enables the software engineer
to derive sets of input conditions that will fully exercise the functional requirement of a
program.
Black box testing enables to find error in the following categories:-
Incorrect or missing functions. Interface errors. Errors in the data structure or external database access. Performance errors. Initialization and termination errors
By applying Black box testing a set of test cases that satisfy the following criteria ---
32
Test cases that reduce, by a count that is greater than one, the number of additional
test case must be designed to achieve reasonable testing.
Test cases that tell us something about the presence or absence of classes of errors,
rather than associated only with the specific test at the hand
33
ANALYSIS MODELING
Data Modeling
Data modeling is very important part of the analysis it mainly deals with the data
object and their relationship. With the help of data model one can easily identify the
primary objects to be process by the system. Data model makes Entity-Relationship
(ER) diagram to describe the relationship between entities. The data model considers the
data independent of the processing that transform the data.
Data modeling answers a set of specific questions that are relevant to any data
processing application. What are the primary data objects to be processed by the
system? What is the composition of each data object and what attributes describe the
object? What do the objects currently reside? What are the relationship between each
object and other objects? What are the relationships between the objects and the
processes that transform them?
Data Objects and Attributes
The data model consist the data objects and attributes that describe the data
object. A data object is the representation of any composite information that is processed
by computer software. A data object can be an external entity, a thing, an occurrence or
event, a role, a structure etc. A data object encapsulates the data only—there is no
reference within a data object to operations that act on the data. So the data object can be
a table.
34
Attributes define the properties of a data object and take on one of three different
characteristics.
Name an instance of the data object
Describe the instance
Make reference to another instance in another table.
Also one or more attribute can be defined as identifier i.e. - Key. The key is used to
make the relationship with the attribute of another data object. It may or may not be
unique. In our context, we can say that as our project is RDBMS, so here relationship
between various data object is essential to get required information and result the user
want. So key has very important role here to make references as well as referential
integrity and to prevent from data redundancy.
Cardinality
Cardinality defines the maximum number of objects that can be participating in a
relationship. According to Tillman, the cardinality is the specification of the number of
occurrences of one object that can be related to the number of occurrences of another
object. Taking into consideration all combinations of ‘one’ and ‘many’ two objects can
be related as:
One-to-One (1:1)
One-to-Many (1: M)
Many-to-One (M: 1)
Many-to-Many (M: N)
35
Entity Relationship Diagram
The Entity Relationship Diagrams (ERD) is the graphical notation of relationship
between data object and attributes. The ERD was originally proposed by Peter Chen for
the design of relational database systems and has been extended by others. Sets of
primary components are identified for the ERD: data objects, attributes, relationship,
and various type indicators. The primary purpose of the ERD is to represent data objects
and their relationship.
36
ER diagram for E-Advertisement
37
Data Flow Diagram
The Data Flow Diagram is the graphical representation that depicts information flow
and the transforms that are applied as data move from input to output. DFD is a model,
which gives the insight into the information domain and functional domain at the same
time. DFD is refined into different levels. The more refined DFD is more details of the
system are incorporated. In the process of creating a DFD, we decompose the system
into different functional subsystems. The DFD refinement results in a corresponding
refinement of data.
The DFD at the simplest level is referred to as the ‘CONTEXT ANALYSIS
DIAGRAM’. These are expanded by level, each explaining its process in detail.
Processes are numbered for easy identification and are normally labeled in block
letters. Each data flow is labeled for easy understanding.