Exercises
Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7
Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14
Chapter 12
<<Rule>>
From the structure perspective, a transaction is made of more than one rule !
A rule has an ID !
The range of rule's ID is string !
From the structure perspective, a rule is made of a condition and an action !
A condition has a setOfVariables !
The range of condition's setOfVariables is stringSet !
An action has a setOfVariables !
The range of action's setOfVariables is stringSet !
<<RuleAlternative>>
From the structure perspective, a transaction is made of more than one rule !
A rule has an ID !
The range of rule's ID is string !
From the structure perspective, a rule is made of a condition and an action !
From the struct perspective, a condition is made of a setOfVariables !
From the mult perspective, setOfVariables is made of more than one variable!
A variable has a name and valueSet !
The range of variable's name is string!
The range of variable's valueSet is string with values PositiveReal, NegativeReal, and NaturalNumber !
From the struct perspective, an action is like condition !
<<RuleAlternativeInstance.xml>>
<?xml version="1.0" encoding="UTF-8"?>
<transaction xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="xmlinSCH.xsd">
<aspectsOftransaction>
<transaction-structureMultiAsp numContainedIntransaction = "1">
<rule ID = "stringValue">
<aspectsOfrule>
<rule-structureDec>
<condition>
<aspectsOfcondition>
<condition-structDec>
<setOfVariables>
<aspectsOfsetOfVariables>
<setOfVariables-multMultiAsp numContainedInsetOfVariables = "1">
<variable name = "temperature" valueSet = "NegativeReal">
</variable>
</setOfVariables-multMultiAsp>
</aspectsOfsetOfVariables>
</setOfVariables>
</condition-structDec>
</aspectsOfcondition>
</condition>
<action>
<aspectsOfaction>
<condition-structDec>
<setOfVariables>
<aspectsOfsetOfVariables>
<setOfVariables-multMultiAsp numContainedInsetOfVariables = "1">
<variable name = "humidity" valueSet = "NaturalNumber">
</variable>
</setOfVariables-multMultiAsp>
</aspectsOfsetOfVariables>
</setOfVariables>
</condition-structDec>
</aspectsOfaction>
</action>
</rule-structureDec>
</aspectsOfrule>
</rule>
</transaction-structureMultiAsp>
</aspectsOftransaction>
</transaction>
<<weatherDataSpecification>>
From the structure perspective, a weatherDataSpecification is made of a timeIntervalSpecification,
spaceRegionSpecification, and variablesOfInterest !
From the structure perspective, timeIntervalSpecification is made of a startDate and endDate !
From the structure perspective, the startDate is made of a month and a day !
A month can be Jan, Feb, Mar, Apr, May, June, July, Aug, Sept, Oct, Nov, or Dec in name !
A day can be day1, day2, day3, or day4 in name !
From the structure perspective, endDate is like startDate !
From the region perspective, spaceRegionSpecification is made of NorthEast, South, MidWest,and West !
From the subRegion perspective, spaceRegionSpecification is made of NewEngland, MidAtlantic,
EastNorthCentral, WestNorthCentral, EastNorthCentral, SouthAtlantic, EastSouthCentral, WestSouthCentral,
Mountain, and Pacific!
From the mult perspective, variablesOfInterest is made of more than one weatherMeasure !
weatherMeasure can be temperature, humidity, precipitation, or barometricPressure in variable !
© Copyright 2007 - RTSync Corp. All Rights Reserved.