Beruflich Dokumente
Kultur Dokumente
The Objective of this system is to illustrate the use of Online Weather Forecast. Wind
Rose is used to provide the Weather Reports.
The intent of WIND ROSE is to provide a complete source of graphical weather
information. This is intended to satisfy the needs of common people and it can be a tool
for the casual user as well. The graphics and data are displayed as a meteorologist would
expect to see.
In this WIND ROSE application we can have the detailed explanation pages to
guide them through the various plots, charts and images for the novice user.
Introduction to Modules
• Admin
• User
• Visitors
• Forums
Admin
Admin is the one who is going to maintain all the information related to Weather.
Admin can have the information related to the user like what all the entire transactions
user is doing. This application provides such option to the admin to keep track of entire
information related to the Temperature as well as the information about the users.
User
He can get into system with the authentication and can access all the information
about climatic conditions and weather reports for time-to-time, intimations and
information regarding environmental disorders is provided.
Visitors
Visitors can enter into the module and view the information about the weather
condition time to time anywhere in India in detail.
Forums
The purpose of having the forums in this system is anyone can express their
views for having the better environment. They can discuss or present their views on their
government policies regarding the environment and suggestions are accepted.
3 SYSTEM ANALYSIS
As the Wind Rose project is developed using Asp.Net, HTML and C# it provides a
user friendly graphical user interface which navigates user through out the program by
providing various task related to the Weather forecast.
WIND ROSE can give you the information basing on which you can plan, reduce
costs and risk, and beat the competition. It offers real-time weather data.
The Project ‘WIND ROSE’ gives us the information about climatic conditions
and weather reports for time-to-time, intimations and information regarding
environmental disorders is provided.
Technical Feasibility
Evaluating the technical feasibility is the trickiest part of a feasibility study. This
is because, at this point in time, not too many detailed design of the system, making it
difficult to access issues like performance, costs on (on account of the kind of technology
to be deployed) etc. A number of issues have to be considered while doing a technical
analysis.
Before commencing the project, we have to be very clear about what are the
technologies those are required for the development of new system.
2. Find out whether the organization currently possesses the required technologies
OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned into information
systems that will meet the organizations operating requirements. Simply stated, this test
of feasibility asks if the system will work when it is developed and installed. Are there
major barriers to Implementation? Here are questions that will help test the operational
feasibility of a project:
• Is there sufficient support for the project from management from users? If
the current system is well liked and used to the extent that persons will not be
able to see reasons for change, there may be resistance.
• Are the current business methods acceptable to the user? If they are not,
Users may welcome a change that will bring about a more operational and useful
systems.
• Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in
General and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered
In the existing manual system, the new system was considered to be operational feasible.
ECONOMIC FEASIBILITY
Problem Specifications
Further Drawbacks of the Existing System
Time Delay
To know the information about the climatic conditions up to date or time to time people
has to wait for news magazines or channels. It’s a time taking process to have the
information.
Redundancy
As the information provided by them is restricted to some extent and later information is
not available for any one.
Accuracy
Since the information available is taken by the people who doesn’t have the knowledge
related to environment.
The software, Wind Rose, is designed to give us the information about climatic
conditions and weather reports for time-to-time, intimations and information regarding
environmental disorders is provided
INTRODUCTION
Purpose
The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.
Scope
This Document plays a vital role in the development life cycle (SDLC) and also it
describes the complete requirements of the system. It is meant for use by the developers
and will be the basic during testing phase. Any changes made to the requirements in the
future will have to go through formal change approval process.
1) Developing the system, which meets the SRS and solving all the requirements of
the system?
2) Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.
3) Submitting the required user manual describing the system interfaces to work on
it and also the documents of the system.
4) Conducting any user training that might be needed for using the system.
Functional Requirements
Inputs
The major inputs for this application can be categorized module -wise. Basically all the
information is managed by the software and in order to access the information one has to
produce their identity by entering the user-id and password. Every user has their own
domain of access beyond which the access is dynamically refrained rather denied.
Output
The major outputs of this system are user details and services of different departments.
Links are created dynamically to meet the requirements on demand. Reports, as it is
obvious, carry the gist of the whole information that flows across all the services.
This application must be able to produce output at different modules for different
inputs.
Performance Requirements
Performance is measured in terms of reports generated according to the requirements.
Admin
Admin is the one who is going to maintain all the information related to Weather.
Admin can have the information related to the user like what all the entire transactions
user is doing. This application provides such option to the admin to keep track of entire
information related to the Temperature as well as the information about the users.
User
He can get into system with the authentication and can access all the information
about climatic conditions and weather reports for time-to-time, intimations and
information regarding environmental disorders is provided.
Visitors
Visitors can enter into the module and view the information about the weather
condition time to time anywhere in India in detail.
Forums
The purpose of having the forums in this system is anyone can express their
views for having the better environment. They can discuss or present their views on their
government policies regarding the environment and suggestions are accepted
3.8 Hardware Requirements
Cache : 512 KB
Software Requirements
4. System Design
The two design objectives continuously sought by developers are reliability and
maintenance.
Reliable System
There are two levels of reliability. The first is meeting the right requirements. A
careful and through systems study is needed to satisfy this aspect of reliability. The
second level of systems reliability involves the actual working delivered to the user. At
this level, the systems reliability is interwoven with software engineering and
development. There are three approaches to reliability.
Maintenance:
While working it is the Key to reduce the need for maintenance, if possible to do
essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documentation.
3. Using more effective methods for designing, processing, login and communicating
information with project team members.
4. Making better use of existing tools and techniques.
5. Managing system engineering process effectively.
Output Design
One of the most important factors of an information system for the user is the
output the system produces. Without the quality of the output, the entire system may
appear unnecessary that will make us avoid using it possibly causing it to fail. Designing
the output should process the in an organized well throughout the manner. The right
output must be developed while ensuring that each output element is designed so that
people will find the system easy to use effectively.
The term output applying to information produced by an information system
whether printed or displayed while designing the output we should identify the specific
output that is needed to information requirements select a method to present the
formation and create a document report or other formats that contains produced by the
system.
Types of output
Whether the output is formatted report or a simple listing of the contents of a file, a
computer process will produce the output.
• A Report
• A Document
• A Message
• Retrieval from a data store
• Transmission from a process or system activity
• Directly from an output sources
Layout Design
It is an arrangement of items on the output medium. The layouts are building a
mock up of the actual reports or document, as it will appear after the system is in
operation. The output layout has been designated to cover information. The outputs are
presented in the appendix.
Avoiding delay
The processing delay resulting from data preparation or data entry operations is called
bottlenecks. Avoiding bottlenecks should be one objective of input.
Avoiding errors
Through input validation we control the errors in the input data.
• A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set
of diagram, which is as follows.
In this the structural and behavioral aspects of the environment in which the system is to
be implemented are represented.
UML is specifically constructed through two different domains they are
UML Analysis modeling, which focuses on the user model and structural
model views of the system.
UML design modeling, which focuses on the behavioral modeling,
implementation modeling and environmental model views.
UNIFIED MODELLING LANGUAGE
Use Case:
USE CASES
Use Case diagrams are one of the five diagrams in the UML for modeling the
dynamic aspects of systems(activity diagrams, sequence diagrams, state chart
diagrams and collaboration diagrams are the four other kinds of diagrams in the
UML for modeling the dynamic aspects of systems). Use Case diagrams are
central to modeling the behavior of the system, a sub-system, or a class. Each one
shows a set of use cases and actors and relationships.
INTERACTION DIAGRAMS
SEQUENCE DIAGRAMS:
ACTIVITY DIAGRAM
An Activity Diagram is essentially a flow chart showing flow of control from
activity to activity. They are used to model the dynamic aspects of as system.
Admin
EndUser
WindRoseUser
Visitors
Forums
Services CitizenInformation
ADMIN
DataBase
Admin
Login
CheckWithTheDatabase
CreateWindroseUserLogins,Visitor
Logins
Logout
WindroseUser DataBase
Login
CheckwithTheDataBase
UploadTheImages,Tempareture
Logout
VISITORS
CheckWithTheDataBase
ViewTheUserDetails
ViewTheTemperatureDetails
Logout
FORUMS
Forums DataBase
Login
CheckWithTheDataBase
GiveHisViewForBetterInvironment
NewUseCase4
CLASS DIAGRAMS
UserLogin
Uname : Varchar
password : Varchar
Login()
WindRoseUser Visitor
Admin Uname : Varchar Uname : Varchar
Password : Varchar Password : Varchar
Uname : Varchar
Password : Varchar ViewWeatherInformation() GiveFeedback()
UploadImages() Viewtemperature()
CreateUserID() UploadTemperature()
CreateUserPassword()
ViewWeatherInformation()
Feedback
Weather name1 : Varchar
Images Subject : Varchar
Id : Varchar
Id : Varchar Feedback;Varchar
City : Varchar
Min : decimal Path : Varchar
Date : Integer GetFeedback()
Max : Decimal
Description : Varchar Type : Varchar
Images : Integer
Date : Integer GetImages()
GetWeatherInformation()
ACTIVITY DIAGRAMS
SYSTEM LEVEL
Login
Login
VISITOR
Login
Give Feedback
SEQUENCE DIAGRAM
ConnectedToSite
UploadTheImages,Tempareture
ProccessTheRequest
ViewTheWeatherInformation
ProccessTherequest
FeedBack
ProccessTheRequest
4.3 ER-Diagrams
• The set of primary components that are identified by the ERD are
ER DIAGRAM
Password
Useri Visitor Id creation
d
Admin Form
Visitor
Id
Personal
Information
View Weather
Information
Weather
Information
NORMALIZATION
Insertion anomaly
Unable to add data to database because of absence of other data.
Deletion anomaly
Update anomaly
Normal Forms
These are the rules for structuring relations that eliminate anomalies.
A relation is said to be in first normal form if the values in the relation are atomic
for every attribute in the relation. By this we mean simply that no attribute value can be a
set of values or, as it is sometimes expressed, a repeating group.
If two non key attributes depend on each other as well as on the primary key then
they are said to be transitively dependent.
DATABASE TABLES
View weather,
Users information View information about
weather condition
Wind Rose
Generate weather
reports for time-to
time Can give their views
View weather reports for better environment
• The entire system is projected with a physical diagram which specifics the
actual storage parameters that are physically necessary for any database to
be stored on to the disk. The overall systems existential idea is derived from
this diagram.
• The content level DFD is provided to have an idea of the functional inputs
and outputs that are achieved through the system. The system depicts the
input and out put standards at the high level of the systems existence.
5 SOFTWARE DEVELOPMENT ENVIRONMENT
The common type system defines how types are declared, used, and
managed in the runtime, and is also an important part of the runtime's support for
cross-language integration. The common type system performs the following
functions:
• Establishes a framework that enables cross-language integration, type safety,
and high performance code execution.
• Provides an object-oriented model that supports the complete implementation
of many programming languages.
• Defines rules that languages must follow, which helps ensure that objects
written in different languages can interact with each other.
Describes concepts and defines terms relating to the common type system.
Type Definitions
Type Members
Describes events, fields, nested types, methods, and properties, and concepts such
as member overloading, overriding, and inheritance.
Value Types
Classes
Delegates
Arrays
Interfaces
Related Sections
Provides a reference to the classes, interfaces, and value types included in the
Microsoft .NET Framework SDK.
Describes the run-time environment that manages the execution of code and
provides application development services.
Cross-Language Interoperability
Language Interoperability
Explains the need for a set of features common to all languages and identifies CLS
rules and features.
Discusses the meaning of CLS compliance for components and identifies levels of CLS
compliance for tools.
Describes how types are declared, used, and managed by the common language
runtime.
Explains the common language runtime's mechanism for describing a type and
storing that information with the type itself.
The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented,
providing types from which your own managed code can derive functionality. This not
only makes the .NET Framework types easy to use, but also reduces the time
associated with learning new features of the .NET Framework. In addition, third-
party components can integrate seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of
interfaces that you can use to develop your own collection classes. Your collection
classes will blend seamlessly with the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET
Framework types enable you to accomplish a range of common programming tasks,
including tasks such as string management, data collection, database connectivity,
and file access. In addition to these common tasks, the class library includes types
that support a variety of specialized development scenarios. For example, you can
use the .NET Framework to develop the following types of applications and services:
Console applications
• Scripted or hosted applications.
• Windows GUI applications (Windows Forms).
• ASP.NET applications.
• XML Web services.
• Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable
types that vastly simplify Windows GUI development. If you write an ASP.NET Web
Form application, you can use the Web Forms classes.
Choosing a Complier
To obtain the benefits provided by the common language runtime, you must use one
or more language compilers that target the runtime.
Compiling translates your source code into MSIL and generates the required
metadata.
At execution time, a just-in-time (JIT) compiler translates the MSIL into native code.
During this compilation, code must pass a verification process that examines the
MSIL and metadata to find out whether the code can be determined to be type safe.
The common language runtime provides the infrastructure that enables execution to
take place as well as a variety of services that can be used during execution.
Assemblies Overview
ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are
distributed, server-side application components similar to common Web sites.
However, unlike Web-based applications, XML Web services components have no UI
and are not targeted for browsers such as Internet Explorer and Netscape Navigator.
Instead, XML Web services consist of reusable software components designed to be
consumed by other applications, such as traditional client applications, Web-based
applications, or even other XML Web services. As a result, XML Web services
technology is rapidly moving application development and deployment into the highly
distributed environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately
notice the improvements that ASP.NET and Web Forms offers. For example, you can
develop Web Forms pages in any language that supports the .NET Framework. In
addition, your code no longer needs to share the same file with your HTTP text
(although it can continue to do so if you prefer). Web Forms pages execute in native
machine language because, like any other managed application, they take full
advantage of the runtime. In contrast, unmanaged ASP pages are always scripted
and interpreted. ASP.NET pages are faster, more functional, and easier to develop
than unmanaged ASP pages because they interact with the runtime like any
managed application.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an
extensible data format), and WSDL (the Web Services Description Language). The
.NET Framework is built on these standards to promote interoperability with non-
Microsoft solutions.
For example, the Web Services Description Language tool included with the
.NET Framework SDK can query an XML Web service published on the Web, parse its
WSDL description, and produce C# or Visual Basic source code that your application
can use to become a client of the XML Web service. The source code can create
classes derived from classes in the class library that handle all the underlying
communication using SOAP and XML parsing. Although you can use the class library
to consume XML Web services directly, the Web Services Description Language tool
and the other tools contained in the SDK facilitate your development efforts with the
.NET Framework.
If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication
standards, such as SOAP, WSDL, and XML. Using those classes enables you to focus
on the logic of your service, without concerning yourself with the communications
infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the scalable
communication of IIS.
This section describes the programming essentials you need to build .NET
applications, from creating assemblies from your code to securing your application.
Many of the fundamentals covered in this section are used to create any application
using the .NET Framework. This section provides conceptual information about key
programming concepts, as well as code samples and detailed explanations.
Shows how to use Internet access classes to implement both Web- and Internet-
based applications.
Developing Components
Explains the extensive support the .NET Framework provides for developing
international applications.
Explains how to get access to type information at run time by using reflection.
Explains the .NET Framework SDK mechanism called the Code Document Object
Model (CodeDOM) that enables the output of source code in multiple programming
languages.
Discusses the various collection types available in the .NET Framework, including
stacks, queues, lists, arrays, and structs.
Handling and Raising Events
Describes error handling provided by the .NET Framework and the fundamentals of
handling exceptions.
Hosting the Common Language Runtime
Explains the concept of a runtime host, which loads the runtime into a process,
creates the application domain within the process, and loads and executes user code.
Including Asynchronous Calls
Processing Transactions
Discusses the .NET Framework support for transactions.
Programming Essentials for Garbage Collection
Discusses how the garbage collector manages memory and how you can program to
use memory more efficiently.
Programming with Application Domains and Assemblies
Describes how to create and work with assemblies and application domains.
Securing Applications
Describes .NET Framework code access security, role-based security, security policy,
and security tools.
Serializing Objects
Discusses XML serialization.
Threading
Explains the runtime support for threading and how to program using various
synchronization techniques.
Discusses formatting and parsing base data types and using regular expressions to
process text.
Explains how you can perform synchronous and asynchronous file and data stream
access and how to use to isolated storage.
Introduction to ASP.NET
ASP.NET is more than the next version of Active Server Pages (ASP); it is a
unified Web development platform that provides the services necessary for
developers to build enterprise-class Web applications. While ASP.NET is largely
syntax compatible with ASP, it also provides a new programming model and
infrastructure for more secure, scalable, and stable applications. You can feel free to
augment your existing ASP applications by incrementally adding ASP.NET
functionality to them.
ASP.NET is a compiled,. NET-based environment; you can author applications
in any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire .NET Framework is available to any ASP.NET application.
Developers can easily access the benefits of these technologies, which include the
managed common language runtime environment, type safety, inheritance, and so
on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors
and other programming tools, including Microsoft Visual Studio .NET. Not only does
this make Web development easier, but it also provides all the benefits that these
tools have to offer, including a GUI that developers can use to drop server controls
onto a Web page and fully integrated debugging support.
Developers can choose from the following two features when creating an
ASP.NET application, Web Forms and Web services, or combine these in any way they
see fit. Each is supported by the same infrastructure that allows you to use
authentication schemes, cache frequently used data, or customize your application's
configuration, to name only a few possibilities.
Web Forms allows you to build powerful forms-based Web pages. When
building these pages, you can use ASP.NET server controls to create common UI
elements, and program them for common tasks. These controls allow you to rapidly
build a Web Form out of reusable built-in or custom components, simplifying the
code of a page. For more information, see Web Forms Pages. For information on how
to develop ASP.NET server controls, see Developing ASP.NET Server Controls
An XML Web service provides the means to access server functionality
remotely. Using Web services, businesses can expose programmatic interfaces to
their data or business logic, which in turn can be obtained and manipulated by client
and server applications. XML Web services enable the exchange of data in client-
server or server-server scenarios, using standards like HTTP and XML messaging to
move data across firewalls. XML Web services are not tied to a particular component
technology or object-calling convention. As a result, programs written in any
language, using any component model, and running on any operating system can
access XML Web services. For more information, see XML Web Services and XML Web
Service Clients Created Using ASP.NET
Each of these models can take full advantage of all ASP.NET features, as well
as the power of the .NET Framework and .NET Framework common language
runtime. These features and how you can use them are outlined as follows:
If you have ASP development skills, the new ASP.NET programming model will
seem very familiar to you. However, the ASP.NET object model has changed
significantly from ASP, making it more structured and object-oriented. Unfortunately
this means that ASP.NET is not fully backward compatible; almost all existing ASP
pages will have to be modified to some extent in order to run under ASP.NET. In
addition, major changes to Visual Basic .NET mean that existing ASP pages written
with Visual Basic Scripting Edition typically will not port directly to ASP.NET. In most
cases, though, the necessary changes will involve only a few lines of code. For more
information, see Migrating from ASP to ASP.NET
Accessing databases from ASP.NET applications is an often-used technique for
displaying data to Web site visitors. ASP.NET makes it easier than ever to access
databases for this purpose. It also allows you to manage the database from your
code. For more information, see Accessing Data with ASP.NET
ASP.NET provides a simple model that enables Web developers to write logic
that runs at the application level. Developers can write this code in the global.asax
text file or in a compiled class deployed as an assembly. This logic can include
application-level events, but developers can easily extend this model to suit the
needs of their Web application. For more information, see ASP.NET Applications
ASP.NET provides easy-to-use application and session-state facilities that are
familiar to ASP developers and are readily compatible with all other .NET Framework
APIs. For more information, see ASP.NET State Management
For advanced developers who want to use APIs as powerful as the ISAPI
programming interfaces that were included with previous versions of ASP, ASP.NET
offers the IHttpHandler and IHttpModule interfaces. Implementing the IHttpHandler
interface gives you a means of interacting with the low-level request and response
services of the IIS Web server and provides functionality much like ISAPI extensions,
but with a simpler programming model. Implementing the IHttpModule interface
allows you to include custom events that participate in every request made to your
application. For more information, see HTTP Runtime Support
ASP.NET takes advantage of performance enhancements found in the .NET
Framework and common language runtime. Additionally, it has been designed to
offer significant performance improvements over ASP and other Web development
platforms. All ASP.NET code is compiled, rather than interpreted, which allows early
binding, strong typing, and just-in-time (JIT) compilation to native code, to name
only a few of its benefits. ASP.NET is also easily factorable, meaning that developers
can remove modules (a session module, for instance) that are not relevant to the
application they are developing. ASP.NET also provides extensive caching services
(both built-in services and caching APIs). ASP.NET also ships with performance
counters that developers and system administrators can monitor to test new
applications and gather metrics on existing applications. For more information, see
ASP.NET Caching Features and ASP.NET Optimization
Writing custom debug statements to your Web page can help immensely in
troubleshooting your application's code. However, it can cause embarrassment if it is
not removed. The problem is that removing the debug statements from your pages
when your application is ready to be ported to a production server can require
significant effort. ASP.NET offers the Trace Context class, which allows you to write
custom debug statements to your pages as you develop them. They appear only
when you have enabled tracing for a page or entire application. Enabling tracing also
appends details about a request to the page, or, if you so specify, to a custom trace
viewer that is stored in the root directory of your application. For more information,
see ASP.NET Trace
The .NET Framework and ASP.NET provide default authorization and
authentication schemes for Web applications. You can easily remove, add to, or
replace these schemes, depending upon the needs of your application. For more
information, see ASP.NET Web Application Security
ASP.NET configuration settings are stored in XML-based files, which are
human readable and writable. Each of your applications can have a distinct
configuration file and you can extend the configuration scheme to suit your
requirements. For more information, see ASP.NET Configuration
Building Applications
Provides the information you need to develop enterprise-class Web applications with
ASP.NET.
Describes writing applications that use the system console for input and output.
Describes the .NET Framework's rich design-time architecture and support for visual
design environments.
Deploying Applications
Shows how to use the .NET Framework and the common language runtime to create
self-described, self-contained applications.
Configuring Applications
Explains how developers and administrators can apply settings to various types of
configuration files.
Shows how to turn JIT tracking on and optimization off to make an assembly easier
to debug.
Enabling Profiling
When you create Web Forms pages, you can use these types of controls:
HTML server controls HTML elements exposed to the server so you can
program them. HTML server controls expose an object model that maps very closely
to the HTML elements that they render.
Web server controls Controls with more built-in features than HTML server
controls. Web server controls include not only form-type controls such as buttons
and text boxes, but also special-purpose controls such as a calendar. Web server
controls are more abstract than HTML server controls in that their object model does
not necessarily reflect HTML syntax.
Validation controls Controls that incorporate logic to allow you to test a
user's input. You attach a validation control to an input control to test what the user
enters for that input control. Validation controls are provided to allow you to check
for a required field, to test against a specific value or pattern of characters, to verify
that a value lies within a range, and so on.
User controls Controls that you create as Web Forms pages. You can embed
Web Forms user controls in other Web Forms pages, which is an easy way to create
menus, toolbars, and other reusable elements.
You can use all types of controls on the same page. The following sections
provide more detail about ASP.NET server controls. For more information about
validation controls, see Web Forms Validation for information about user controls;
see Introduction to Web User Controls
HTML server controls are HTML elements containing attributes that make
them visible to — and programmable on — the server. By default, HTML elements on
a Web Forms page are not available to the server; they are treated as opaque text
that is passed through to the browser. However, by converting HTML elements to
HTML server controls, you expose them as elements you can program on the server.
The object model for HTML server controls maps closely to that of the corresponding
elements. For example, HTML attributes are exposed in HTML server controls as
properties.
Any HTML element on a page can be converted to an HTML server control.
Conversion is a simple process involving just a few attributes. As a minimum, an
HTML element is converted to a control by the addition of the attribute
RUNAT="SERVER". This alerts the ASP.NET page framework during parsing that it
should create an instance of the control to use during server-side page processing. If
you want to reference the control as a member within your code, you should also
assign an ID attribute to the control.
The page framework provides predefined HTML server controls for the HTML
elements most commonly used dynamically on a page: forms, the HTML <INPUT>
elements (text box, check box, Submit button, and so on), list box (<SELECT>),
table, image, and so on. These predefined HTML server controls share the basic
properties of the generic control, and in addition, each control typically provides its
own set of properties and its own event.
An object model that you can program against on the server using the
familiar object-oriented techniques. Each server control exposes properties that allow
you to manipulate the control's HTML attributes programmatically in server code.
A set of events for which you can write event handlers in much the same way you
would in a client-based form, except that the event is handled in server code.
Automatic maintenance of the control's state. If the form makes a round trip
to the server, the values that the user entered into HTML server controls are
automatically maintained when the page is sent back to the browser.
Interaction with validation controls you can easily verify that a user has entered
appropriate information into a control.
Support for HTML 4.0 styles if the Web Forms page is displayed in a browser
that supports cascading style sheets. Pass-through of custom attributes. You can add
any attributes you need to an HTML server control and the page framework will read
them and render them without any change in functionality. This allows you to add
browser-specific attributes to your controls. For details about how to convert an
HTML element to an HTML server control, see Adding HTML Server Controls to a Web
Forms Page
Web server controls are a second set of controls designed with a different
emphasis. They do not map one-to-one to HTML server controls. Instead, they are
defined as abstract controls in which the actual HTML rendered by the control can be
quite different from the model that you program against. For example, a
RadioButtonList Web server control might be rendered in a table or as inline text with
other HTML.
Web server controls include traditional form controls such as buttons and text
boxes as well as complex controls such as tables. They also include controls that
provide commonly used form functionality such as displaying data in a grid, choosing
dates, and so on.
Web server controls offer all of the features described above for HTML server
controls (except one-to-one mapping to HTML elements) and these additional
features:
A rich object model that provides type-safe programming capabilities.
Automatic browser detection. The controls can detect browser capabilities and create
appropriate output for both basic and rich (HTML 4.0) browsers.
For some controls, the ability to define your own look for the control using templates
For some controls, the ability to specify whether a control's event causes immediate
posting to the server or is instead cached and raised when the form is submitted.
Ability to pass events from a nested control (such as a button in a table) to the
container control.
At design time in HTML view, the controls appear in your page in a format such as:
<asp: button attributes run at="server"/>
The attributes in this case are not those of HTML elements. Instead, they are
properties of the Web control.
When the Web Forms page runs, the Web server control is rendered on the
page using appropriate HTML, which often depends not only on the browser type but
also on settings that you have made for the control. For example, a Textbox control
might render as an <INPUT> tag or a <TEXTAREA> tag, depending on its properties.
SQL
DATABASE
A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management
systems include dBase, paradox, IMS, and Sql. These systems allow users to create,
update and extract information from their database.
A database is a structured collection of data. Data refers to the
characteristics of people, things and events. Sql stores each data item in its own
fields. In Sql, the fields relating to a particular person, thing or event are bundled
together to form a single complete unit of data, called a record (it can also be
referred to as raw or an occurrence). Each record is made up of a number of fields.
No two fields in a record can have the same field name.
During an Sql Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over
time, you define any additional fields or change the definition of existing fields.
Sql Tables
Sql stores records relating to each other in a table. Different tables are
created for the various groups of information. Related tables are grouped together to
form a database.
Primary Key
Every table in Sql has a field or a combination of fields that uniquely identifies
each record in the table. The Unique identifier is called the Primary Key, or simply
the Key. The primary key provides the means to distinguish one record from all
other in a table. It allows the user and the database system to identify, locate and
refer to one particular record in the database.
Relational Database
When a field is one table matches the primary key of another field is referred
to as a foreign key. A foreign key is a field or a group of fields in one table whose
values match those of the primary key of another table.
Referential Integrity
Not only does Sql allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
Data Abstraction
Physical Level
This is the lowest level of abstraction at which one describes how the data are
actually stored.
Conceptual Level
At this level of database abstraction all the attributed and what data are
actually stored is described and entries and relationship among them.
View level
This is the highest level of abstraction at which one describes only part of the
database.
Advantages of RDBMS
SQL is a truly portable, distributed, and open DBMS that delivers unmatched
performance, continuous operation and support for every database.
SQL with transactions processing option offers two features which contribute
to very high level of transaction processing throughput, which are
The unrivaled portability and connectivity of the SQL DBMS enables all the
systems in the organization to be linked into a singular, integrated computing
resource.
Portability
SQL is fully portable to more than 80 distinct hardware and operating systems
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary
platforms. This portability gives complete freedom to choose the database sever
platform that meets the system requirements.
Open Systems
Unmatched Performance
The most advanced architecture in the industry allows the SQL DBMS to
deliver unmatched performance.
Real World applications demand access to critical data. With most database
Systems application becomes “contention bound” – which performance is limited not
by the CPU power or by disk I/O, but user waiting on one another for data access .
Sql employs full, unrestricted row-level locking and contention free queries to
minimize and in many cases entirely eliminates contention wait times.
No I/O Bottlenecks
Sql’s fast commit groups commit and deferred write technologies dramatically
reduce disk I/O bottlenecks. While some database write whole data block to disk at
commit time, Sql commits transactions with at most sequential log file on disk at
commit time, On high throughput systems, one sequential writes typically group
commit multiple transactions. Data read by the transaction remains as shared
memory so that other transactions may access that data without reading it again
from disk. Since fast commits write all data necessary to the recovery to the log file,
modified blocks are written back to the database independently of the transaction
commit, when written from memory to disk.
SQL * NET
This is Sql’s networking software, which interfaces between SQL and the OS
networking protocol. SQL * NET enables the integration of diverse, OS, database,
communication protocols and application to create a unified computing information
resource.
SQL * Plus
SQL * MENU
SQL * REPORTWRITER
admin_login.aspx page
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
SqlDataReader dr;
dr = cmd.ExecuteReader();
if (dr.Read())
{
Server.Transfer("admin_menu.aspx");
}
else
{
Page.RegisterClientScriptBlock("aa", "<script>alert('Please
Check Username and Password')</script>");
}
con.Close();
}
protected void Button2_Click(object sender, EventArgs e)
{
TextBox2.Text = "";
TextBox1.Text = " ";
}
}
Admin_login.aspx.cs page
<%@ Page Language="C#" MasterPageFile="~/MasterPage.master"
AutoEventWireup="true" CodeFile="admin_login.aspx.cs"
Inherits="admin_login" Title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
<br />
<br />
<br />
<asp:Panel ID="Panel1" runat="server" Height="252px" Style="z-
index: 100; left: 427px;
position: absolute; top: 293px; background-color: #ffffcc"
Width="342px" BorderStyle="Ridge">
<asp:Label ID="Label1" runat="server" Font-Bold="False"
Height="9px" Style="z-index: 100;
left: 48px; position: absolute; top: 112px"
Text="Password"></asp:Label>
<asp:Label ID="Label2" runat="server" Font-Bold="False"
Style="z-index: 101; left: 52px;
position: absolute; top: 66px" Text="UserId"></asp:Label>
<asp:TextBox ID="TextBox2" runat="server" Style="left: 114px;
position: relative;
top: 61px; z-index: 102;"></asp:TextBox>
<asp:Label ID="Label3" runat="server" Style="z-index: 107;
left: 114px; position: absolute;
top: 7px" Text="Admin Login Form"></asp:Label>
<asp:Button ID="Button1" runat="server" OnClick="Button1_Click1"
Style="left: -74px;
position: relative; top: 173px; z-index: 104;" Text="Login"
/>
<asp:Button ID="Button2" runat="server" OnClick="Button2_Click"
Style="left: -46px;
position: relative; top: 169px; z-index: 105;" Text="Reset"
/>
<asp:TextBox ID="TextBox1" runat="server" Style="left: 148px;
position: relative;
top: 80px; z-index: 106;" TextMode="Password"
Width="148px"></asp:TextBox>
</asp:Panel>
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
</asp:Content>
7 SYSTEM TESTING
Error Messages
The term error is used in two different ways. Errors refer to the
discrepancy between computed and observed values. That is error
refers to the difference between the actual output of the software and
the correct output. In this interpretation, error essentially is a measure
of the difference between the actual and the ideal. Error is also used to
refer to human action that results in the software containing a defect
or a fault. This detection is quite general and encompasses all phases.
The consequence of thinking is the belief that the errors largely occur
during
programming, as it is the can see, the errors occur through the
development. As we can see, the errors occur throughout the
development process. However, the cost of
connecting the errors of different phases is not the same and depends
upon when the error was detected and corrected. The cost of
correcting errors in the function of where they are detected.
As one would expect the greater the delay in detecting an error
after it occurs, the more expensive it is to correct it. Suppose an error
occurs during the requirement phase and it was corrected after the
coding then the cost is higher than correcting it in the requirements
phase itself. The reason for this is fairly obvious. If there was error in
the requirements phase that error will affect the design and coding
also. To correct the error after coding is done require both the design
and the code to be changed there by increasing the cost of correction.
The main moral of this section is that we should attempt to
detect the errors that occur in a phase during the phase itself should
not wait until testing to detect errors. This is not often practiced. In
reality, sometimes testing is the sole point where errors are detected.
Besides the cost factor, reliance on testing as a primary source for
error detection and correction should be a continuous process that is
done throughout the software development. In terms of the
development phase, what this means is that we should try to validate
each phase before starting the next.
Testing Techniques
Unit Testing
In this testing only the output is checked for correctness. The logical
flow of the data is not checked.
In this the test cases are generated on the logic of each module
by drawing flow graphs of that module and logical decisions are tested
on all the cases. It has been uses to generate the test cases in the
following cases:
• Guarantee that all independent paths have been executed.
• Execute all logical decisions on their true and false sides.
• Execute all loops at their boundaries and within their operational
• Execute internal data structures to ensure their validity.
Integration Testing
System Testing
Validation Testing
COMPILING TEST
EXECUTION TEST
OUTPUT TEST
Test Case2
Test Case3
Name Delete user test for Administrator
Location Delete_user.aspx
Input1 Valid username
SQL The system will display delete user page.
Test Case4
Test Case8
Test Case9
Name Login test for Visitor in forums
Location Forums_login. aspx
Input1 Valid name& Password
SQL The system will display Feedback form page.
Test Case10
8. CONCLUSION
Conclusion
• The system includes various modules, which will help us to know the
Information about the Temperatures at different places. The
purpose of having the forums in this system is anyone can express their
views for having the better environment.
9.FUTURE ENHANCEMENTS
The project Wind Rose can be expanded to full pledged Weather Portal which
can be implemented on any server. Wind Rose can maintain all the information about
the details of the Temperatures of different places in the World and can make it to
implement world wide with the connections of different satellites and also it can be
made to provide the information related to pollution levels of different places.
It can be a globalized application.
10 .BIBLIOGRAPHY
The following books were referred during the analysis and execution
phase of the project
SOFTWARE ENGINEERING
By Roger.S.Pressman
MSDN
By Microsoft
Websites
www.google.com