Intro4u2u

Intro4u2u, News, Travel, Technology, Engineering, Airline, Sports, google, yahoo, msn

Archive for January, 2007


Enhanced IEC 61131-3: Proven standard fit for future

The international standard “IEC 61131-3″ was released in 1993 and, since its adoption, has become widely accepted by the international user and vendor community. Today, it is, as such, the worldwide recognized standard for programming and configuring industrial control devices. The popularity of IEC 61131-3 in the industry is evident. The world’s leading industrial control manufacturers have adopted the programming model for a wide range of controllers; various software companies offer compliant development tools; and the standard is certainly the world’s leading paradigm for industrial control languages. The success of PLCopen and its increasing number of members prove this, too.
Why then revise a successful standard ?

There are, however, several reasons why the standard must be revised: First of all, since 1993 a great deal of practical experience has been gained in which a number of inconsistencies and contradictions have been detected. These include inconsistent definitions and features which are needlessly complicated. Several of these inconsistencies strongly prevent one of the most important objectives of PLCopen, namely the language portability to various PLC types. In order to remedy this, many users of the standard proposed revisions and enhancements. These can be found in the Addendum and in the Corrigendum as belonging to the standard.

In addition, the demands on industrial control systems and their engineering environments have considerably changed over the years, where the most important item is the migration of large centralized control systems towards distributed systems. IEC 61131-3 exclusively applies to local controllers including their communication interfaces to other local systems, not the programming of distributed systems. That is why the reciprocal integration of the IEC 61131-3 programming languages with IEC 1499 (the new architectural model for distributed industrial process measurement and control systems) is absolutely necessary. Only through this, long-term company investments in control systems can be assured.

This is the reason why IEC 1131 is now being revised in three stages, each summarized below:

1)      “Corrigendum”: correction of errors.

2)      “Amendment”: more consistent structuring of the standard  accompanied by additional implementation of features required in everyday controls situations.

3)      Harmonization between IEC 61131-3 and IEC 1499.

In the course of this, the major goal to maintain upward compatibility for all amendments. This means, a control program which complies with the previous standard is also expected to comply with the new standard without conflicts.
Stage 1: Corrigendum

The initial stage exclusively eliminates hard errors and non-compliances within the existing standard. In addition to correcting misprints, this especially resolves semantic discrepancies in the main section and inconsistencies between the main section and appendices. During last four years, the IEC task force collected, evaluated and adapted the relevant modifications. This occurred with the active assistance of numerous experts, especially from the PLCopen group. None of the changes shall cause incompatibility.
Stage 2: Amendment

The second stage extends beyond a pure revision of errors and defines improvements to the standard. These include two main points.

Firstly, the chapter concerning the programming language “Instruction List” has been reworked in order to remove existing inconsistencies.

Secondly, the definition of functions is revised. The possibilities of using parameters with functions are too inflexible in the existing IEC-1131, sometimes resulting in awkward constructions. Moreover, the usage of “Enable Input/Output” has caused substantial confusion. This will be revised in the new release, and a serious stumbling block will have been overcome in the effort toward portable control programs.

A number of less significant amendments still complement these two main points. They are, for the greatest part, upwards compatible with the present standard.

The main objective of these amendments is to increase the acceptance of 1131-3 languages by the application programmers through unified and practice-orientated language constructs. In this relationship, enhanced utilization of the control hardware is to be achieved. In addition, IEC increases  actual semantic portability for control programs, eliminating interpretation latitude for particular language constructs.
Stage 3: Harmonization with IEC 1499

The last stage of the intended revision concerns the desired harmonization with the architecture standard IEC 1499 – ”Function Blocks”. This standard for distributed industrial control systems does not define its own specific programming languages for algorithms. The languages contained in IEC 61131-3 are used instead, since they are best suited in modified or enhanced form for many industrial application domains. Again, the most important guideline for developing these revisions even in this case, is, to ensure as much upward compatibility as possible. Harmonization with IEC 1499 will open many opportunities for IEC 1131 and, thus, continue to increase its acceptance.
Current state

The corrections and amendments were reviewed and modified in the first half of 1998 by the international IEC 61131-3 task force. It circulated as Committee Draft in 1999. It collected many comments, and will be circulated as Committee Draft for Vote (CDV). The CDV spans a 5 month period. A revised version is published as Final Draft International Standard, FDIS, for 4 months. If approved, it will be published as International Standard, IS, within 2 month. The total time from CDV till publication takes about 1 year. This looks long compared to de-facto standards, but during half the time the standard should be stable already, and so usable to develop products. Parallel to it, a French edition has to be made and circulated.

Overall, a new edition of this standard has been published as International Standard in 2003.

The third proposed stage is in a much less mature development stage. This planned harmonization work can lead to a third edition of the standard.

To keep them alive, standards are always subject to change and undergo evolutionary changes in regard to technology advancements and market needs. On the other hand, the essentials of a standard must be established on a solid and long-lasting basis. For this reason, caution must always be applied to all exercised amendments: The investments of the industrial end users and hardware and software control vendors are always expected to be the primary concern. The approach described here represents an appropriate compromise to this concern.
What about this ‘6’ in IEC 1131 ?

The International Electrotechnical Commission, IEC, is a world wide standardization body. Nearly all countries over the world have their own, national standardization bodies. In Germany for instance this is the Deutsche Elektrotechnischen Kommission, DKE. These commissions have agreed to accept the IEC approved and published standards. At local publication, often after translation, the standard was published under a local number. This local number often had no match to the number of the IEC published standard. For a standardization body this looked awkward. To harmonize this, they searched for a world wide numbering system that was available to use. This is where the famous ‘6’ came in. And so IEC 61131-3 became IEC 61131-3, without any changes to the standard itself. Moreover, during the current transition phase, you have to order the IEC 6-1131 standard to get a publication that clearly has on its front cover ‘IEC 61131-3’. As this might be confusing to non-insiders, we decided to wait for a new edition of the standard to migrate to the new number. In this way it is coupled to change.

IEC 61131-5

Within the full set of the international IEC 61131 standard, part 5 deals with communication. As such it is approved as Standard in 2000, and is available at IEC or at the local representations (adres info).

This part 5 describes the way PLCs can communicate to each other. A PLC as used in the context of IEC 61131 may be a real controller or a SoftPLC or any device which supports the programming languages of IEC 61131-3 and the communication defined in IEC 61131-5. This means from PLC-to-PLC, to HMI, Plant control, and even robots and CNC’s. Even it can provide communication to intelligent devices via a fieldbus. However, it does not include distributed control or communication to simple I/O devices via a sensor / actuator level bus or fieldbus.

The IEC 61131-5 describes the communication services from the point of view of the programmer and/or user. As such it is a application program interface for PLC communication. For this it provides communication services in the form of functions combined with the concepts and elements of the IEC 61131-3 programming languages. This means also that it lies on top of the ISO/OSI stack. Otherwise stated, it lies on top of the layer 7 – application layer. As such it really provides services to the users – they do not have to write the code by themselves, nor to worry about how it is done. This matches the high user friendliness of the IEC 61131-3 Function Blocks.

IEC 61131-5 does not describe a communication bus-system – it defines independent services at a higher level, which can be used in existing communication networks and systems. Pre-requisite for these systems is that they support connections, access to variables and message services, as well as the loading of large data sets. Also, this standard contains the mapping onto ISO/IEC 9506-1/2 (MMS, Manufacturing Message Specification, as a result of the MAP, Manufacturing Automation Protocol, initiative of General Motors in the 1980’s.) and onto ISO/IEC 9506-5 (PLC Companion Standard). Other communication systems based on other standards or de-facto standards may be used as communication subsystems for IEC 61131-5 too. Example of these are EN 50170 (Profibus FMS), and EN 50170 – 3 (Sub MMS), which is currently under definition.

Data Consistency

Within IEC 61131-5 data consistency is guaranteed. Nevertheless inconsistencies can occur when the application program is interrupted by a higher priority task, for instance an alarm function. If this function changes the data under communication, an inconsistent set can be created. In this case the user has to take measures to guarantee that the data areas used to send or receive the data values shall not be used during the time that the function blocks are busy.

If one transfers larger sets of data at once with the function blocks BSEND / BRCV, one has to be aware of the effect on the reaction time of the system. One way is to divide the large set into smaller units, as part of the application program.

For user, like application programmers, the combination of IEC 61131-3 and –5 is of course the most natural.

Connections

In IEC 61131-5, the communication itself is done via communication connection. These take care that Client and Server can find each other and understand each other, or change the role of client and server. The data are transmitted between instances of the IEC 61131-5 function block. The user does not have to worry about how: it is contained in the function blocks, and normally hidden. In the application program, the sending function block has a variable set of inputs with the data to be sent (SD_i). Via the communication system these data set is send to the corresponding receiving side, and made available to the other application program via the outputs (RD_i). Of course both data-types of SD-i and RD_i have to match. Please note that the implementation of flexible number of inputs and outputs at run time (expandable FBs) is very difficult, and will not be seen often in praxis – fixed length is preferred by the supplier.

With this set, not only 1-to-1 connections, but also 1-to-n connections multi-cast) as well as 1-to-all connections (broadcast) can be supported (if the communication system can support it). With these last two, the Publisher-Subscriber model is supported, besides the standard Client-Server model.

Connection can be made within a system, for instance between different CPU’s in one PLC, or between different tasks on a SoftPLC, or between different PLC applications. All communication service of IEC 61131-5 need connections. In most cases these are constructed and maintained in an implicit way, meaning that no coding in the application program has to be done for this. This is what is meant with the functionality lying above level 7, application layer, of the OSI/ISO stack.

iec.gif

Figure 1: - Programmable Controller – Communication Model (subset)

iec2.gif

Figure 2: Programmable Controller hardware model

IEC 61131-5 has defined an extensive set of status information on the hardware itself. This means that for the user this part is covered by the standard itself, and needs no additional coding. The hardware model (conform IEC 61131-1 and –2) identifies seven entities (units, modules or subsystems) per PLC. These entities which are can present status information are (see figure 2):

No.

Status presenting entities

1

PLC (as a whole)

2

I/O subsystem (includes I/O modules and other intelligent I/O devices)

3

Processing unit

4

Power supply subsystem

5

Memory subsystem

6

Communication subsystem

7

Implementer specific subsystems

 The status is intended to provide information about the controller including its hardware and firmware subsystems, not considering configuration information. It is not intended to provide information about the controlled process nor the PLC application program. The status data contains information concerning the state and the health of the PLC and its subsystems.

There are two concepts used in this part of IEC 61131 related to status: health and state. The “health” of a PLC or its subsystems is specified by returning one and only one of the three possible values. The semantics associated with each value is specified below. They are, in order of decreasing health:

a)         GOOD - If TRUE, the PLC (or the specified subsystem) has not detected any problems which would prohibit it from performing the intended function;

b)         WARNING - If TRUE, the PLC (or the specified subsystem) has not detected any problems which would prohibit it from performing the intended function, but it has detected at least one problem which could place some limits on its abilities. The limit may be time, performance, etc;

c)         BAD - If TRUE, the PLC (or the specified subsystem) has detected at least one problem which could prohibit it from performing the intended function.

Each of the status information can also have implementer specified attributes.

For instance, for the I/O subsystems the following summary status information has been defined (Table 1). Similar sets have been defined for the PLC, the status of the processing units, power supply, memory, communication subsystem, and implementer specific subsystems. This covers all entities, and takes this part out of the hands of the users. Also, the representation of the status information is defined.

No.

Item

Description

1

Health

GOOD

indicates that there have been no errors detected in this I/O subsystem

2

WARNING

indicates that a minor fault has been detected in the I/O subsystem.  An example of a minor fault is the occurrence of recoverable errors in the communication  with a remote I/O station

3

BAD

indicates that a major fault has been detected in the I/O subsystem.  An example of a major fault is losing communication with a remote I/O station

4

No outputs disabled

If TRUE, this attribute indicates that the PC can change the physical state of all outputs associated with the specified I/O subsystem as a result of application program execution or other means.  If not TRUE, the physical state of some of the outputs is not affected (logical state may be affected).  This is typically used in the testing and modifying of application programs in the PC

5

No inputs disabled

If TRUE, this attribute indicates that the PC can access the physical state of all inputs  associated with the specified I/O subsystem as a result of application program execution or other means.  If not TRUE, the physical state some inputs cannot be accessed.  This is typically used in the testing and modifying of application programs where the inputs can be simulated

6

I/O forced

If TRUE, this attribute indicates that at least one I/O point associated with this subsystem has been forced.  When an Input is forced, the application program will receive the value specified by the PADT instead of the actual value from the machine or process.  When an output is forced, the machine or process will receive the value specified by the PADT instead of the value generated by execution of the application program

Table 1: Status of the I/O Subsystem
In addition, the functions which a PLC provides to a control system using the communication subsystem have been defined. This means a complete set for the communication function: device verification, data acquisition, control, synchronization between user applications, alarm reporting, connection management, program execution and I/O control, and application program transfer. This means that the features are defined, and the function blocks (except for the last two) are available.
Programmable Controller Function Blocks

If you have reached this point, you noticed that the IEC 61131-5 standard does not only cover some communication functions or function blocks. But of course, they are defined too. And they are well defined all function blocks include timing diagram, state diagram and the corresponding transitions. The following FBs are defined (Table 3):

Application specific functions

Name of communication function block or function

Addressing of remote variables

REMOTE_VAR (function)

Device verification

STATUS, USTATUS

Polled data acquisition

READ,

Programmed data acquisition

USEND, URCV, BSEND, BRCV

Parametric control

WRITE,

Interlocked control

SEND, RCV

Programmed alarm report

NOTIFY, ALARM

Connection management

CONNECT

       Table 3 - Overview of the communication function blocks

Most of them are clear, but others need some additional information:

Device verification: FBs STATUS and USTATUS
A PC can request a remote communication partner to send back to it its status information using the STATUS function block. A PC can itself enable to receive status information of a remote communication partner using the USTATUS function block.

Programmed data acquisition: FB USEND / URCV and BSEND / BRCV
For the programmed data acquisition, there are two pairs of FBs defined. The difference between these pairs of function blocks lies in the way they operate.
The FB pair USEND / URCV transmits a set of variables between a pair of instances of USEND/URCV or between one instance of USEND and many instances of URCV. In the application program, USEND has a variable set of inputs with the data to be sent (SD_i). Via the communication system these data set is send to the corresponding URCV, and made available to the other application program via the outputs (RD_i) of URCV. Of course both datatypes of SD-i and RD_i have to match.
BSEND/BRCV are used for the transmission of a data buffer, with length as specified in the application program. The number of bytes to be transferred can dynamically be set via one input parameter. This makes this function block flexible in its usage. The communication system may use segmented transfer to transmit larger amounts of data. The user does not take care of that: segmentation is hidden inside the function block or the communication system. Of course the user has to take care of the data consistency, he shall not use the data buffers during the function blocks are busy.

Parametric control: FB WRITE; Polled Data Acquisition: FB READ
This combination to read and write data are used in 1-to-1 connections only. The application program requests if and when the data shall be read or written.

Two kinds of variables in the PLC may be used with READ and WRITE:

1.         Directly represented Variables with direct representation
2.         Other variables which have Access paths (See IEC 61131‑3 for the definition of access paths)

If the directly represented variables are accessible these variables shall use the direct representation as an identifier. The PLC which own the variables can interpret the identifier using an implementer defined algorithm. The PC system may restrict access to variables with direct representation.

Interlocked control: FBs SEND and RCV
The SEND instance requests the RCV instance to execute an application operation and to inform the SEND instance of the result of the operation. This has two aspects, the synchronization of the application program of the SEND and RCV instances and the exchange of information between them. This function can be used to have the effect of a remote procedure call from one application program to another.

Programmed alarm report: FBs NOTIFY and ALARM
A PC can be programmed using the ALARM function block to report an alarm message with an acknowledgement capability. Or, it can be programmed using the NOTIFY function block to report an alarm message without an acknowledgement capability.

Connection management: CONNECT
Connections  are controlled explicitly by the application program using the CONNECT function block or are provided by the communication subsystem if and when needed.
This communication function block allows to establish a connection between the calling communication partner and the remote communication partner. The remote communication partner is identified using its name. A communication channel to the remote communication partner is defined. The remote communication partner shall decide whether or not to establish the connection.


Pressure valve

These handy pressure valve caps claim to let you know when your rubber is under-inflated. We put six sets to the test to see which ones can be relied on…
Did you know that if your tyres are under-inflated by 10 per cent, their life will be cut by the same amount? Yet most drivers don’t check their pressures often enough – so products that give at-a-glance warnings are booming.

Usually, these replace the valve cap, and alert you to any psi loss via coloured inserts; green means everything is OK, while red (and sometimes yellow before it) indicates the pressure has dropped. But some of the kits are based on conventional gauges.

We set out to see if such devices really can help you take better care of your tyres.

The test

Using a wheel and tyre with three valves, we checked the cap alerts while monitoring the slowly released pressure with a digital gauge.

Ideally, we wanted to be able to spot even a small pressure loss. We also factored in price and convenience, with marks lost if you had to do anything more than simply look.

Most products are sold on the Internet, so allow for delivery costs if buying online.

Verdict: Regular pressure gauge checks are still the best option, as the valve caps were slow to react to air loss. As a failsafe, the Pressure Guard is our pick of the bunch. The Auto Unique TPMS Remote trailed it only on price.

1. Pressure Guard
2. Auto Unique TPMS Remote
3. Bike It Pressure Alert Valve Caps

EMAIL TO A FRIEND               PRINT THIS

1. Pressure Guard
Price: £12.50 per four Automatic: Yes

Black plastic valve caps featured small, clear bubbles at their ends and, unlike rivals, weren’t preset, being suitable for tyres between 20psi and 42psi. With the tyre correctly inflated, the cap was fitted and the green outer segments appeared. As pressure was released, the central red wedge was exposed, and it started to show with a loss of 4psi. Good price helped it come out on top.

2. Auto Unique TPMS Remote
Price: £45 (est) Automatic: No

Tested here as a prototype, this device will be smaller when it goes on sale in February. The handheld display works as a normal gauge. But once the correct pressure has been entered, when you hold it close to one of the caps– each has a battery and four LEDs – the lights flash according to the psi. Gadgety and pricey, but does what it says on the tin.

3. Bike It Pressure Alert Caps
Price: £13.96 (£3.49 each) Automatic: Yes

It was close between these and the Aircheckers in the test, apart from their pressure limits. Confusingly, the 28psi cap had to be selected for 29-30psi, and 30psi for 32-34psi. The caps are from a bike supplier, and are sold separately. But our 28psi samples indicated only a little yellow at 26psi, and red didn’t show until 22psi. Not what you need on two or four wheels.

4. Aircheckers
Price: £17.95 per four Automatic: Yes

Smart-looking in a chrome-effect finish, the Airchecker had individual preset limits in 2psi increments from 26-42psi – more than enough for car use. But with a loss of 4psi, the yellow segment was barely visible. Even at 8psi, it was hard to make out the red section; this should have been easy to see, even from a distance. Not that effective, and pricey compared with the similar Bike It.

5. Quik-Chek Press. Monitors
Price: £17.95 per four Automatic: Yes

Better value than the KeyChain, but the permanent-fit Quik-Chek caps would be too bulky for some wheels. The sprung end had to be pushed in for a reading, which varied according to how hard it was pressed. We couldn’t easily see the red section until 25psi; a worry, as the green section was around 30-34psi. Large, awkward and too tricky to read.

6. Quik-Chek KeyChain
Price: £4.64 each Automatic: No

Although offered ‘free’ online, there was still a carriage charge for this poor man’s pressure gauge. It’s big and cumbersome, making access tricky on some alloy designs, and has to be unclipped from its keyring before use. To get a reading, you remove the valve cap and replace it with the Quik-Chek, so a gauge would be less hassle. Worse still, the alerts were worryingly slow.

Valve market expands with new applications

Everywhere there are liquids and gases flowing in pipes there are valves to control the flow.

More than 25,000 companies manufacture valves around the world. This year those companies will generate sales of $43 billion and by 2010 the sales will rise to $53 billion.

The growth will be fuelled by new applications in the developed countries and by industrial expansion in the developing countries. These are the conclusions reached in the online continually updated McIlvaine report, Industrial Valves World Markets.

Sales for the top 10 suppliers last year were $7.5 billion. Sales for the companies ranked 11 through 20 were $3.5 billion. Thus the top 20 companies accounted for 25 per cent of the sales and averaged individual sales of $550 million. The companies ranked 21-30 generated sales of $1.5 billion or $150 million each. The companies ranked 31 to 40 enjoyed sales of $800 million
or $80 million each.

The average sales for each of the top 50 companies was $270 million. The average sales for the other 24,950 companies were just over $1 million. So the industry is highly fragmented with many small companies making up the bulk of the sales. Many of these companies are highly specialized in terms of applications and/or geographic areas of activity.

Oil and gas is the largest application sector with 2006 sales of over $7 billion. This sector is undergoing substantial change. The rapid growth of liquefied natural gas (LNG) is presenting big opportunities for companies which can meet the extreme pressure and temperature demands. The development of nonconventional oil sources such as tar sands also creates markets for rugged valve designs.

China is the leading purchaser of valves for new plants, while the US remains the largest purchaser of repair parts. In the power sector, China will purchase more valves for new power plants than the rest of the world combined. China is also a leader in most heavy industrial sectors. One area where it is not a top five purchaser is in pharmaceutical biotech.

Environment represents a continuing growth area for valve suppliers. The remediation of ground water, desalination of seawater, and the conventional treatment of drinking water are all growing sectors. Treatment of municipalwastewater in Asia is also expanding rapidly. Double-digit growth is being experienced in the sales of valves for scrubber systems used for cleanup of exhausts from power plants and other industrial sources.

High-quality images of Apple’s first orange iPod (shuffle)

hp3.jpg

Apple on Tuesday graced its affordable line of iPod shuffle digital music players with a fresh array of hues, including orange — a first for the iPod family.

The Cupertino-based company also broke the shuffle’s gender barrier, delivering a pink model as well as additional unisex offerings in vibrant blue and green. Each retail for just $79.

Although the new lineup of second-generation shuffles offer no enhancements over the monotone silver model introduced last fall, there is one morsel nestled with each new unit: updated earbud headphones.

That’s right. Apple has seemingly run through its stockpile of first-generation iPod earbuds and is now more than happy to include an updated pair with each shuffle, as it does every other iPod model.

Customers who want to make sure they receive the updated earbuds when purchasing a grey shuffle should be sure to grab models whose packing sports black lettering (as seen below) as opposed to the green lettering used on packaging for the grey shuffle introduced last fall.

So why orange instead of black or red? “It’s just gorgeous,” Greg Joswiak, Apple’s Vice President of iPod Product Marketing, told iLounge. “It’s just something that’s going to look nice in fashion scenarios.”

Apple developing next-gen ODD module for ultra…
Samsung claims primary seat in Apple iPhone
Next-gen MacBook Pro to shine brighter
Apple to impose 802.11n unlocking fee on Intel…
Pentium M-based Intel chip at heart of Apple TV
Apple iTV availability to escape Macworld Expo
Mac OS X 10.4.9 to offer Bluetooth, synching…
Apple to answer the Street’s iPhone call on time
Adobe After Effects 8.0 tracking for mid-2007…
Public beta of Adobe Creative Suite 3 may boost…
Source: Three iPods on Apple roadmap for 2007
Apple smart phone project rests on Mac OS X…
Ripe in Cupertino: an Apple with 8 cores
Special Report: Apple’s touch-sensitive iPod…
Exclusive: Apple seeks rights to iPhone trademark
more…

Hot Forum Topics
More Euro countries enter battle over iTunes DRM
Apple World Wide Developer Conference 2007…
Cramer: Cingular to give away 18 months of…
Intel rolls out ‘breakthrough’ chip tech bound…
Apple developing next-gen ODD module for ultra…
AirPort: AirPort Utility 1.0, 802.11n manuals,…
Apple revenues could catch Microsoft by 2010
Verizon passed on exclusive 5-year iPhone deal
Apple stores increasing focus on Windows…
Apple to grow iPod line slightly, sources say
Google edges Apple in worldwide brand survey
Intel 45nm Penryn Details Announced
Briefly: Early iPhone rumors afloat
Apple patches QuickTime exploit published by…
Rogers Wireless lands exclusive iPhone deal in…
more…

Recent Articles
Vista dawns, world yawns
High-quality images of Apple’s first orange iPod (shuffle)
Apple serves up $1.99 AirPort Extreme 802.11n Enabler
Apple’s iPod shuffle now available in five colors
PiperJaffray takes a closer look at Apple’s iPhone
Apple to grow iPod line slightly, sources say
Briefly: Early iPhone rumors afloat
iPhone cost expected to decline 20 percent annually
Apple revenues could catch Microsoft by 2010
Verizon passed on exclusive 5-year iPhone deal
Intel rolls out ‘breakthrough’ chip technology bound for Macs
Starbucks visitors to sip iTunes downloads?
Briefly: Leopard shots, iPhone rumor, 10.4.9, Euro iTunes videos
AirPort: AirPort Utility 1.0, 802.11n manuals, Core Duo Extreme fix
Google edges Apple in worldwide brand survey
Plans for third Manhattan Apple store nixed (again)
More Euro countries enter battle over iTunes DRM
Apple seen expanding Broadcom touch technology to future devices
Rogers Wireless lands exclusive iPhone deal in Canada
Cramer: Cingular to give away 18 months of service with iPhone
Apple developing next-gen ODD module for ultra portable notebooks
Initial Photoshop CS3 feedback encouraging for pro Mac sales
Apple stores increasing focus on Windows stragglers
Apple World Wide Developer Conference 2007 slated for June
Screenshots from latest Leopard build appear on flickr
Samsung claims primary seat in Apple iPhone
Needham: iPhone takes shine off RIM’s Pearl
Apple patches QuickTime exploit published by MoAB website
Apple chief executive questioned by U.S. authorities
Apple faces two-pronged patent lawsuit assault
Next-gen MacBook Pro to shine brighter
Apple’s latest Leopard Server seed packs some punch
Briefly: New version of Apple Xcode making the rounds
Intel exec claims iPhone runs on Xscale chip
SATA-based Xserve RAID prototype escapes from Apple (photos)
Apple sets free new build of Mac OS X 10.5 Leopard
Gartner: Apple’s Mac market share slips to fifth in US
Briefly: 802.11n fee, Jobs’ mansion woes, Apple targets British firm
Apple’s iPhone runs Mac OS X Leopard - report
Mac OS X Leopard to sport next-gen DVD Player software (images)

High-quality images of Apple’s first orange iPod (shuffle)

hp3.jpg

Apple on Tuesday graced its affordable line of iPod shuffle digital music players with a fresh array of hues, including orange — a first for the iPod family.

The Cupertino-based company also broke the shuffle’s gender barrier, delivering a pink model as well as additional unisex offerings in vibrant blue and green. Each retail for just $79.

Although the new lineup of second-generation shuffles offer no enhancements over the monotone silver model introduced last fall, there is one morsel nestled with each new unit: updated earbud headphones.

That’s right. Apple has seemingly run through its stockpile of first-generation iPod earbuds and is now more than happy to include an updated pair with each shuffle, as it does every other iPod model.

Customers who want to make sure they receive the updated earbuds when purchasing a grey shuffle should be sure to grab models whose packing sports black lettering (as seen below) as opposed to the green lettering used on packaging for the grey shuffle introduced last fall.

So why orange instead of black or red? “It’s just gorgeous,” Greg Joswiak, Apple’s Vice President of iPod Product Marketing, told iLounge. “It’s just something that’s going to look nice in fashion scenarios.”

Apple developing next-gen ODD module for ultra…
Samsung claims primary seat in Apple iPhone
Next-gen MacBook Pro to shine brighter
Apple to impose 802.11n unlocking fee on Intel…
Pentium M-based Intel chip at heart of Apple TV
Apple iTV availability to escape Macworld Expo
Mac OS X 10.4.9 to offer Bluetooth, synching…
Apple to answer the Street’s iPhone call on time
Adobe After Effects 8.0 tracking for mid-2007…
Public beta of Adobe Creative Suite 3 may boost…
Source: Three iPods on Apple roadmap for 2007
Apple smart phone project rests on Mac OS X…
Ripe in Cupertino: an Apple with 8 cores
Special Report: Apple’s touch-sensitive iPod…
Exclusive: Apple seeks rights to iPhone trademark
more…

Hot Forum Topics
More Euro countries enter battle over iTunes DRM
Apple World Wide Developer Conference 2007…
Cramer: Cingular to give away 18 months of…
Intel rolls out ‘breakthrough’ chip tech bound…
Apple developing next-gen ODD module for ultra…
AirPort: AirPort Utility 1.0, 802.11n manuals,…
Apple revenues could catch Microsoft by 2010
Verizon passed on exclusive 5-year iPhone deal
Apple stores increasing focus on Windows…
Apple to grow iPod line slightly, sources say
Google edges Apple in worldwide brand survey
Intel 45nm Penryn Details Announced
Briefly: Early iPhone rumors afloat
Apple patches QuickTime exploit published by…
Rogers Wireless lands exclusive iPhone deal in…
more…

Recent Articles
Vista dawns, world yawns
High-quality images of Apple’s first orange iPod (shuffle)
Apple serves up $1.99 AirPort Extreme 802.11n Enabler
Apple’s iPod shuffle now available in five colors
PiperJaffray takes a closer look at Apple’s iPhone
Apple to grow iPod line slightly, sources say
Briefly: Early iPhone rumors afloat
iPhone cost expected to decline 20 percent annually
Apple revenues could catch Microsoft by 2010
Verizon passed on exclusive 5-year iPhone deal
Intel rolls out ‘breakthrough’ chip technology bound for Macs
Starbucks visitors to sip iTunes downloads?
Briefly: Leopard shots, iPhone rumor, 10.4.9, Euro iTunes videos
AirPort: AirPort Utility 1.0, 802.11n manuals, Core Duo Extreme fix
Google edges Apple in worldwide brand survey
Plans for third Manhattan Apple store nixed (again)
More Euro countries enter battle over iTunes DRM
Apple seen expanding Broadcom touch technology to future devices
Rogers Wireless lands exclusive iPhone deal in Canada
Cramer: Cingular to give away 18 months of service with iPhone
Apple developing next-gen ODD module for ultra portable notebooks
Initial Photoshop CS3 feedback encouraging for pro Mac sales
Apple stores increasing focus on Windows stragglers
Apple World Wide Developer Conference 2007 slated for June
Screenshots from latest Leopard build appear on flickr
Samsung claims primary seat in Apple iPhone
Needham: iPhone takes shine off RIM’s Pearl
Apple patches QuickTime exploit published by MoAB website
Apple chief executive questioned by U.S. authorities
Apple faces two-pronged patent lawsuit assault
Next-gen MacBook Pro to shine brighter
Apple’s latest Leopard Server seed packs some punch
Briefly: New version of Apple Xcode making the rounds
Intel exec claims iPhone runs on Xscale chip
SATA-based Xserve RAID prototype escapes from Apple (photos)
Apple sets free new build of Mac OS X 10.5 Leopard
Gartner: Apple’s Mac market share slips to fifth in US
Briefly: 802.11n fee, Jobs’ mansion woes, Apple targets British firm
Apple’s iPhone runs Mac OS X Leopard - report
Mac OS X Leopard to sport next-gen DVD Player software (images)

Data Definition Language (DDL)

Data Definition Language (DDL)

  1. Used to specify a database scheme as a set of definitions expressed in a DDL
  2. DDL statements are compiled, resulting in a set of tables stored in a special file called a data dictionary or data directory.
  3. The data directory contains metadata (data about data)
  4. The storage structure and access methods used by the database system are specified by a set of definitions in a special type of DDL called a data storage and definition language
  5. basic idea: hide implementation details of the database schemes from the users

Database Systems and Structures Data Models

Data Models

  1. Data models are a collection of conceptual tools for describing data, data relationships, data semantics and data constraints. There are three different groups:
    1. Object-based Logical Models.
    2. Record-based Logical Models.
    3. Physical Data Models.

    We’ll look at them in more detail now.

Object-based Logical Models

  1. Object-based logical models:
    • Describe data at the conceptual and view levels.
    • Provide fairly flexible structuring capabilities.
    • Allow one to specify data constraints explicitly.
    • Over 30 such models, including
      • Entity-relationship model.
      • Object-oriented model.
      • Binary model.
      • Semantic data model.
      • Infological model.
      • Functional data model.
  2. At this point, we’ll take a closer look at the entity-relationship (E-R) and object-oriented models.

The E-R Model

  1. The entity-relationship model is based on a perception of the world as consisting of a collection of basic objects (entities) and relationships among these objects.
    • An entity is a distinguishable object that exists.
    • Each entity has associated with it a set of attributes describing it.
    • E.g. number and balance for an account entity.
    • A relationship is an association among several entities.
    • e.g. A cust_acct relationship associates a customer with each account he or she has.
    • The set of all entities or relationships of the same type is called the entity set or relationship set.
    • Another essential element of the E-R diagram is the mapping cardinalities, which express the number of entities to which another entity can be associated via a relationship set.

    We’ll see later how well this model works to describe real world situations.

  2. The overall logical structure of a database can be expressed graphically by an E-R diagram:
    • rectangles: represent entity sets.
    • ellipses: represent attributes.
    • diamonds: represent relationships among entity sets.
    • lines: link attributes to entity sets and entity sets to relationships.

The Object-Oriented Model

  1. The object-oriented model is based on a collection of objects, like the E-R model.
    • An object contains values stored in instance variables within the object.
    • Unlike the record-oriented models, these values are themselves objects.
    • Thus objects contain objects to an arbitrarily deep level of nesting.
    • An object also contains bodies of code that operate on the the object.
    • These bodies of code are called methods.
    • Objects that contain the same types of values and the same methods are grouped into classes.
    • A class may be viewed as a type definition for objects.
    • Analogy: the programming language concept of an abstract data type.
    • The only way in which one object can access the data of another object is by invoking the method of that other object.
    • This is called sending a message to the object.
    • Internal parts of the object, the instance variables and method code, are not visible externally.
    • Result is two levels of data abstraction.

    For example, consider an object representing a bank account.

    • The object contains instance variables number and balance.
    • The object contains a method pay-interest which adds interest to the balance.
    • Under most data models, changing the interest rate entails changing code in application programs.
    • In the object-oriented model, this only entails a change within the pay-interest method.
  2. Unlike entities in the E-R model, each object has its own unique identity, independent of the values it contains:
    • Two objects containing the same values are distinct.
    • Distinction is created and maintained in physical level by assigning distinct object identifiers.

Record-based Logical Models

  1. Record-based logical models:
    • Also describe data at the conceptual and view levels.
    • Unlike object-oriented models, are used to
      • Specify overall logical structure of the database, and
      • Provide a higher-level description of the implementation.
    • Named so because the database is structured in fixed-format records of several types.
    • Each record type defines a fixed number of fields, or attributes.
    • Each field is usually of a fixed length (this simplifies the implementation).
    • Record-based models do not include a mechanism for direct representation of code in the database.
    • Separate languages associated with the model are used to express database queries and updates.
    • The three most widely-accepted models are the relational, network, and hierarchical.
    • This course will concentrate on the relational model.
    • The network and hierarchical models are covered in appendices in the text.

The Relational Model

  • Data and relationships are represented by a collection of tables.
  • Each table has a number of columns with unique names, e.g. customer, account.

The Network Model

  • Data are represented by collections of records.
  • Relationships among data are represented by links.
  • Organization is that of an arbitrary graph.

The Hierarchical

  • Similar to the network model.
  • Organization of the records is as a collection of trees, rather than arbitrary graphs.

Physical Data Models

  1. Are used to describe data at the lowest level.
  2. Very few models, e.g.
    • Unifying model.
    • Frame memory.
  3. We will not cover physical models.

What is database management systems

  1. To see why database management systems are necessary, let’s look at a typical “file-processing system” supported by a conventional operating system.The application is a savings bank:
    • Savings account and customer records are kept in permanent system files.
    • Application programs are written to manipulate files to perform the following tasks:
      • Debit or credit an account.
      • Add a new account.
      • Find an account balance.
      • Generate monthly statements.
  2. Development of the system proceeds as follows:
    • New application programs must be written as the need arises.
    • New permanent files are created as required.
    • but over a long period of time files may be in different formats, and
    • Application programs may be in different languages.
  3. So we can see there are problems with the straight file-processing approach:
    • Data redundancy and inconsistency
      • Same information may be duplicated in several places.
      • All copies may not be updated properly.
    • Difficulty in accessing data
      • May have to write a new application program to satisfy an unusual request.
      • E.g. find all customers with the same postal code.
      • Could generate this data manually, but a long job…
    • Data isolation
      • Data in different files.
      • Data in different formats.
      • Difficult to write new application programs.
    • Multiple users
      • Want concurrency for faster response time.
      • Need protection for concurrent updates.
      • E.g. two customers withdrawing funds from the same account at the same time - account has $500 in it, and they withdraw $100 and $50. The result could be $350, $400 or $450 if no protection.
    • Security problems
      • Every user of the system should be able to access only the data they are permitted to see.
      • E.g. payroll people only handle employee records, and cannot see customer accounts; tellers only access account data and cannot see payroll data.
      • Difficult to enforce this with application programs.
    • Integrity problems
      • Data may be required to satisfy constraints.
      • E.g. no account balance below $25.00.
      • Again, difficult to enforce or to change constraints with the file-processing approach.

    These problems and others led to the development of database management systems.

Data Abstraction

  1. The major purpose of a database system is to provide users with an abstract view of the system.The system hides certain details of how data is stored and created and maintained

    Complexity should be hidden from database users.

  2. There are several levels of abstraction:
    1. Physical Level:
      • How the data are stored.
      • E.g. index, B-tree, hashing.
      • Lowest level of abstraction.
      • Complex low-level structures described in detail.
    2. Conceptual Level:
      • Next highest level of abstraction.
      • Describes what data are stored.
      • Describes the relationships among data.
      • Database administrator level.
    3. View Level:
      • Highest level.
      • Describes part of the database for a particular group of users.
      • Can be many different views of a database.
      • E.g. tellers in a bank get a view of customer accounts, but not of payroll data.

Database Systems and Structures

Chapter 1: Introduction    PDF and Slides

* Database Management Systems
* Purpose of Database Systems
* Data Abstraction
* Data Models
o Object-based Logical Models
+ The E-R Model
+ The Object-Oriented Model
o Record-based Logical Models
+ The Relational Model
+ The Network Model
+ The Hierarchical Model
o Physical Data Models
* Instances and Schemes
* Data Independence
* Data Definition Language (DDL)
* Data Manipulation Language (DML)
* Database Manager
* Database Administrator
* Database Users
* Overall System Structure

Chapter 2: Entity-Relationship Model    PDF and Slides

* Entities and Entity Sets
* Relationships & Relationship Sets
* Attributes
* Mapping Constraints
* Keys
* Primary Keys for Relationship Sets
* The Entity Relationship Diagram
* Other Styles of E-R Diagram
* Reducing E-R Diagrams to Tables
o Representation of Strong Entity Sets
o Representation of Weak Entity Sets
o Representation of Relationship Sets
* Generalization
* Aggregation
* Design of an E-R Database Scheme
o Mapping Cardinalities
o Use of Entity or Relationship Sets
o Use of Extended E-R Features

Chapter 3: Relational Model    PDF and Slides

* Structure of Relational Database
o Basic Structure
o Database Scheme
o Keys
o Query Languages
* The Relational Algebra
o Fundamental Operations
o Formal Definition of Relational Algebra
o Additional Operations
* The Tuple Relational Calculus
o Example Queries
o Formal Definitions
o Safety of Expressions
o Expressive Power of Languages
* The Domain Relational Calculus
o Formal Definitions
o Example Queries
o Safety of Expressions
o Expressive Power of Languages
* Modifying the Database
o Deletion
o Insertions
o Updating
* Views
o View Definition
o Updates Through Views and Null Values

Chapter 4: SQL    PDF and Slides

* Background
* Basic Structure
o The select Clause
o The where Clause
o The from Clause
o The Rename Operation
o Tuple Variables
o String Operations
o Ordering the Display of Tuples
o Duplicate Tuples
* Set Operations
* Aggregate Functions
* Null Values
* Nested Subqueries
o Set Membership
o Set Comparison
o Test for Empty Relations
o Test for the Absence of Duplicate Tuples
* Derived Relations
o Views
* Modification of the Database
o Deletion
o Insertion
o Updates
o Update of a view
* Joined Relations
o Examples
o Join types and conditions
* Data-Definition Language
o Domain Types in SQL
o Schema definition in SQL
* Embedded SQL
* Other SQL Features

Chapter 5: Other Relational Languages    PDF and Slides

* Query-by-Example (QBE)
o Basic Structure
o Simple Queries
o Queries on Several Relations
o The Condition Box
o The Result Relation
o Ordering the Display of Tuples
o Aggregate Operations
o Modifying the Database
+ Insertion
+ Updates
* Quel
o Converting Queries Easily Into Any Language

Chapter 6: Integrity Constraints    PDF and Slides

* Domain Constraints
* Referential Integrity
o Basic Concepts
o Referential Integrity in the E-R Model
o Database Modification
o Referential Integrity in SQL
* Assertions
* Triggers
* Functional Dependencies
o Basic Concepts
o Closure of a Set of Functional Dependencies
o Closure of Attribute Sets
o Canonical Cover

Chapter 7: Relational Database Design    PDF and Slides

* Pitfalls in Relational DB Design
o Representation of Information
* Decomposition
* Normalization Using Functional Dependencies
o Desirable Properties of Decomposition
+ Lossless-Join Decomposition
+ Dependency Preservation
+ Repetition of Information
o Boyce-Codd Normal Form
o Third Normal Form
o Comparison of BCNF and 3NF
* Normalization Using Multivalued Dependencies (not to be covered)
o Multivalued Dependencies
o Theory of Multivalued Dependencies
o Fourth Normal Form (4NF)
* Normalization Using Join Dependencies (not to be covered)
* Domain-Key Normal Form (not to be covered)
* Alternative Approaches to Database Design (not to be covered)

Chapter 8: Object-Oriented Databases    PDF and Slides

* New DB Applications
* The Object-Oriented Data Model
o Object Structure
o Object Classes
o Inheritance
o Multiple Inheritance
o Object Identity
o Object Containment
* Object-Oriented Languages
* Persistent Programming Languages
o Persistence of Objects
o Object Identity and Pointers
o Storage and Access of Persistent Objects
* Persistent C++ Systems
o The ODMG C++ Object Definition Language
o The ODMG C++ Object Manipulation Language
* References

Chapter 9: Object-Relational Databases    PDF and Slides

* Nested Relations
* Complex Types and Object Orientation
o Structured and collection types
o Inheritance
o Reference Types
* Querying with Complex Types
o Relation-Valued Attributes
o Path Expressions
o Nesting and Unnesting
o Functions
* Creation of Complex Values and Objects
* Comparison of Object-Oriented and Object-Relational Databases
* References

Chapter 10: Storage and File Structure    PDF and Slides

* Overview of Physical Storage Media
* Magnetic Disks
o Physical Characteristics of Disks
o Performance Measures of Disks
o Optimization of Disk-Block Access
* RAID: Redundant Arrays of Inexpensive Disks (Not covered)
* Tertiary Storage
o Optical Disks
o Magnetic Tapes
* Storage Access
o Buffer manager
o Buffer replacement policies
* File Organization
o Fixed-Length Records
o Variable-Length Records
+ Byte string representation
+ Fixed-length representation
* Organization of Records in Files
o Sequential File Organization
o Clustering File Organization
* Data Dictionary Storage
* Storage Structures for Object-Oriented Databases (Omitted)

Chapter 11: Indexing and Hashing    PDF and Slides

* Basic Concepts
* Ordered Indices
o Primary Index
+ Dense and Sparse Indices
+ Multi-Level Indices
+ Index Update
o Secondary Indices
* B+-Tree Index Files
o Structure of a B+-Tree
o Queries on B+-Trees
o Updates on B+-Trees
o B+-Tree File Organization
* B-Tree Index Files
* Static Hashing
o Hash File Organization
+ Hash Functions
+ Handling of bucket overflows
o Hash Indices
* Dynamic Hashing
* Comparison of Indexing and Hashing
* Index Definition in SQL
* Multiple-Key Access
o Grid File
o Partitioned Hashing

Chapter 12: Query Processing    PDF and Slides

* Query Interpretation
* Equivalence of Expressions
o Selection Operation
o Projection Operation
o Natural Join Operation
o Other Operations
* Estimation of Query-Processing Cost
* Estimation of Access Costs Using Indices
* Join Strategies
o Simple Iteration
o Block-Oriented Iteration
o Merge-Join
o Use of an Index
o Hash Join
o Three-Way Join
* Join Strategies for Parallel Processors
o Parallel-Join
o Pipelined Multiway Join
o Physical Organization
* Structure of the Query Optimizer

  • New Links

  • Ads


Intro4U2U

Advanced Search Preferences Language Tools

SEARCH THE WEB