System Development Environment

7/25/2019 System Development Environment

1/14

SYSTEM DEVELOPMENT ENVIRONMENT

1.HTML

WHAT IS HTML?

To publish information for global distribution, one needs a university-understood

language, a kind of publishing mother tongue that all computers may potentially

understand. The publishing language used by the World Wide Web is HTML (Hyper Tet

Markup Language!

HTML Gives Authors The Meas To

". #ublish online documents $ith headings, tet, tables, list, photos etc.

%. &etrieve online information via hypertet links, at the click of a button

'. esign forms for conducting transactions $ith remote services, for use in searching

information, making reservation, ordering products etc.)

*. +ncludes spreadsheets, video clips, sound clips, and other applications directly in the

documents.

So!e HTML Ta"s

HTML /tarting an HTML tag

H01 2reating a $eb page3s head

T+TL0 4iving a $eb page 5s body

6H01 0nding a $eb pages head


2/14

6789 0nding a $eb pages body

6HTML 0nding a $eb page

:8&M 2reating a HTML forms

+;#


3/14

element. +f you $ant the script to $rite directly to the Web page, place it in the 789

element.

0? HTML

H01

T+TL06T+TL0

6H01

789

/2&+#T L1;4


4/14

(AVAS'RIPTS EVENTS

/ome of the events of Bava/cript

". on 2hange 8ccurs $hen data in a control, like a tet field, changes.

%. on 2lick 8ccurs $hen an element is clicked.

'. on :ocus 8ccurs $hen an element gets the focus.

*. on Mouse o$n 8ccurs $hen a mouse button goes do$n.

D. on &eset 8ccurs $hen the user clicks the reset button.

(AVAS'RIPTS /&N'TIONS

De,0aratio o- -u,tio

/ynta function function name (!

G

I

Write these functions in /2&+#T tag.

. INTROD&'TION A)O&T .NET

Overvie2 o- the .NET /ra!e2or3


5/14

The .;0T :rame$ork is a ne$ computing platform that simplifies application development in

the highly distributed environment of the +nternet. The .;0T :rame$ork is designed to fulfill

the follo$ing obAectives

To provide a consistent obAect-oriented programming environment $hether obAect

code is stored and eecuted locally, eecuted locally but +nternet-distributed, or eecuted

remotely.

To provide a code-eecution environment that minimiJes soft$are deployment and

versioning conflicts.

To provide a code-eecution environment that guarantees safe eecution of code,

including code created by an unkno$n or semi-trusted third party.

To provide a code-eecution environment that eliminates the performance problems

of scripted or interpreted environments.

To make the developer eperience consistent across $idely varying types of

applications, such as Windo$s-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on

the .;0T :rame$ork can integrate $ith any other code.

The .;0T :rame$ork has t$o main components the common language runtime and the

.;0T :rame$ork class library. The common language runtime is the foundation of the .;0T

:rame$ork. 9ou can think of the runtime as an agent that manages code at eecution time,

providing core services such as memory management, thread management, and remoting,

$hile also enforcing strict type safety and other forms of code accuracy that ensure security

and robustness. +n fact, the concept of code management is a fundamental principle of the

runtime. 2ode that targets the runtime is kno$n as managed code, $hile code that does not

target the runtime is kno$n as unmanaged code. The class library, the other main

component of the .;0T :rame$ork, is a comprehensive, obAect-oriented collection of

reusable types that you can use to develop applications ranging from traditional command-


6/14

line or graphical user interface (4


7/14

The runtime enforces code access security. :or eample, users can trust that an eecutable

embedded in a Web page can play an animation on screen or sing a song, but cannot access

their personal data, file system, or net$ork. The security features of the runtime thus

enable legitimate +nternet-deployed soft$are to be eceptionally feature rich.

The runtime also enforces code robustness by implementing a strict type- and code-

verification infrastructure called the common type system (2T/!. The 2T/ ensures that all

managed code is self-describing. The various Microsoft and third-party language compilers

generate managed code that conforms to the 2T/. This means that managed code can

consume other managed types and instances, $hile strictly enforcing type fidelity and type

safety.

+n addition, the managed environment of the runtime eliminates many common soft$are

issues. :or eample, the runtime automatically handles obAect layout and manages

references to obAects, releasing them $hen they are no longer being used. This automatic

memory management resolves the t$o most common application errors, memory leaks and

invalid memory references.

The runtime also accelerates developer productivity. :or eample, programmers can $rite

applications in their development language of choice, yet take full advantage of the runtime,

the class library, and components $ritten in other languages by other developers. 1ny

compiler vendor $ho chooses to target the runtime can do so. Language compilers that

target the .;0T :rame$ork make the features of the .;0T :rame$ork available to eisting

code $ritten in that language, greatly easing the migration process for eisting applications.

While the runtime is designed for the soft$are of the future, it also supports soft$are of

today and yesterday. +nteroperability bet$een managed and unmanaged code enables

developers to continue to use necessary 28M components and LLs.

The runtime is designed to enhance performance. 1lthough the common language runtime

provides many standard runtime services, managed code is never interpreted. 1 feature

called Aust-in-time (B+T! compiling enables all managed code to run in the native machine


8/14

language of the system on $hich it is eecuting. Mean$hile, the memory manager removes

the possibilities of fragmented memory and increases memory locality-of-reference to

further increase performance.

:inally, the runtime can be hosted by high-performance, server-side applications, such as

MicrosoftK /L /erver and +nternet +nformation /ervices (++/!. This infrastructure

enables you to use managed code to $rite your business logic, $hile still enAoying the

superior performance of the industryNs best enterprise servers that support runtime hosting.

2ommon Type /ystem

The common type system defines ho$ types are declared, used, and managed in the

runtime, and is also an important part of the runtimeNs support for cross-language

integration.

Language +nteroperability

escribes built-in support for cross-language interoperability and introduces the 2ommon

Language /pecification.

What is the 'o!!o La"ua"e Se,i-i,atio?

0plains the need for a set of features common to all languages and identifies 2L/ rules and

features.

Writi" 'LS4'o!0iat 'o5e

iscusses the meaning of 2L/ compliance for components and identifies levels of 2L/

compliance for tools.

'o!!o T6e S6ste!

escribes ho$ types are declared, used, and managed by the common language runtime.


9/14

Meta5ata a5 Se0-4Des,ri*i" 'o!oets

0plains the common language runtimeNs mechanism for describing a type and storing that

information $ith the type itself.

. NET Framework Class Library

The .;0T :rame$ork class library is a collection of reusable types that tightly integrate $ith

the common language runtime. The class library is obAect oriented, providing types from

$hich your o$n managed code can derive functionality. This not only makes the .;0T

:rame$ork types easy to use, but also reduces the time associated $ith learning ne$

features of the .;0T :rame$ork. +n addition, third-party components can integrate

seamlessly $ith classes in the .;0T :rame$ork.

. +n addition to these common tasks, the class library includes types that support a

variety of specialiJed development scenarios. :or eample, you can use the .;0T :rame$ork

to develop the follo$ing types of applications and services

2onsole applications.

/cripted or hosted applications.

Windo$s 4


10/14

buttons, and other 4


11/14

have an associated assembly manifest. ;ote that each assembly can have only one entry

point (that is, D00Mai, WiMai, or Mai!.

+t forms a security boundary. 1n assembly is the unit at $hich permissions are

reOuested and granted. :or more information about security boundaries as they apply to

assemblies, see 1ssembly /ecurity 2onsiderations

+t forms a type boundary. 0very typeNs identity includes the name of the assembly in

$hich it resides. 1 type called MyType loaded in the scope of one assembly is not the same

as a type called MyType loaded in the scope of another assembly.

+t forms a reference scope boundary. The assemblyNs manifest contains assembly metadata

that is used for resolving types and satisfying resource reOuests. +t specifies the types and

resources that are eposed outside the assembly. The manifest also enumerates other

assemblies on $hich it depends.

#. DOT NET DATA)ASE 'ONNE'TIVITY 7ADO.NET8

18.;0T uses a multilayered architecture that revolves around a fe$ key concepts, such as

2onnection, 2ommand, and ataset obAects. Ho$ever, the 18.;0T architecture is Ouite a

bit different from classic 18.

8ne of the key differences bet$een 18 and 18.;0T is ho$ they deal $ith the challenge

of different data sources. +n 18, programmers al$ays use a generic set of obAects, no

matter $hat the underlying data source is. :or eample, if you $ant to retrieve a record

from an 8racle database, you use the same 2onnection class you $ould use to tackle the

same task $ith /L /erver. This isn3t the case in 18.;0T, $hich uses a data provider

model.

ADO.NET Data Provi5ers


12/14

1 data provider is a set of 18.;0T classes that allo$s you to access a specific database,

eecute /L commands, and retrieve data. 0ssentially, a data provider is a bridge bet$een

your application and a data source.

The classes that make up a data provider include the follo$ing

'oe,tio: 9ou use this obAect to establish a connection to a data source.

'o!!a5: 9ou use this obAect to eecute /L commands and stored

procedures.

Data Rea5er:This obAect provides fast read-only, for$ard-only access to the

data retrieved from a Ouery.

Data A5ater:This obAect performs t$o tasks. :irst, you can use it to fill a

ataset (a disconnected collection of tables and relationships! $ith

information etracted from a data source. /econd, you can use it to apply

changes to a data source, according to the modifications you3ve made in a

ataset.

18.;0T doesn3t include generic data provider obAects. +nstead, it includes different data

providers specifically designed for different types of data sources. 0ach data provider has a

specific implementation of the 2onnection, 2ommand, ata&eader and ata 1dapter classes

that3s optimiJed for a specific &7M/ (&elational database management system!. :or

eample, if you need to create a connection to a /L /erver database, you3ll use a

connection class named /L 2onnection.

8ne of the key underlying ideas of the 18.;0T provider model is that it3s etensible. +n

other $ords, developers can create their o$n provider for proprietary data sources. +n fact,

numerous proof-of-concepts eamples are available that sho$ ho$ you can easily create

custom 18.;0T providers to $rap no relational data stores, such as the file system or a

directory service. /ome third-party vendors also sell custom providers for .;0T.

The .;0T :rame$ork is bundled $ith a small set of four providers

S;L Server Provi5er: #rovides optimiJed access to a /L /erver

database(version F.@ or later!.


13/14

OLED) Provi5er:#rovides access to any data source that has an 8L07

driver. This includes /L /erver databases prior to version F.@.

Ora,0e Provi5er:#rovides optimiJed access to an 8racle database(version Pi

or later!.

OD)' Provi5er:#rovides access to any data source that has an 872 driver.


14/14

,. Re0atioa0 Data*ase:

The &elational model represents data and relationships among data by a

collection of tables each of $hich has a number of columns $ith uniOue

names.

=.THE S;L LANG&AGE

/L is a language for relational database. /L is a non-procedural i.e., $hen $e use

/L $e specify $hat $e $ant to be done not ho$ to do it.

/eatures O- S;L

". /L is an interactive Ouery language.

%. /L is a database administration language.

'. /L is a database programming language.

*. /L is a client6server language.

D. /L is a distributed database language.

E. /L is a database gate$ay language.

)asi, S;L 'o!!a5s

ata efinition Language commands (L!

ata Manipulation Language commands (ML!

Transaction 2ontrol Language commands (T2L!

Data control Language commands (DCL)

System Development Environment

Documents

Transcript of System Development Environment