Higher-order entity-relationship modelling language, co-design and ...

More documents

Recommendations

Info

Classes and Instances Classes are sets of (markable) objects of corresponding type Entity class is the basic class of objects IS Modelling by HERM 3.7.2012 B. Thalheim β: ((, Thalheim, {Prof., Dr.rer.nat.habil, Dipl.-Math.}), BTU Cottbus, (({ +49 355 692700, +49 355 692397}, +49 355 824054), thalheim@informatik.tu-cottbus.de), 10.3.52, 637861) Why Structuring Null marker CoMoL Functionality Views OLAP References (DBIV, Database theory, CS Programm , mandatory, 2+0+0, certificate) Relationship classes for association of objects of component classes expanded by properties (through attributes) Profβ: ( 637861, Database and information systems ) Senator3β: ( 637861, Senat, (1995,1998), Dekan) Senator5β: ( 637861, Senat, (2000), Chair) PrerequDBIVMain: (DBIV, DBI) , Content Information Concept Topic ... ... CourseDBIVSS02: (DBIV, SS2002, 637861, SR1, Mo. first pair)
Classes and Instances IS Modelling by HERM 3.7.2012 B. Thalheim Classes are sets of (markable) objects of corresponding type .... Cluster classes for disjoint (!), i.a. virtual union of objects of the component classes { Senator2π: ( 889721, Senat, (1998,2000), Chair), Senator5β: ( 637861, Senat, (2000), Chair), Why Structuring Null marker CoMoL Functionality Views OLAP References Content DBIS: ( Database and information systems, 637861, IfI), CBnetβ: (CottbusNet e.V., 637861, Member, Services Group ) } Classes are extended by generic operations insert, delete, update, retrieve may have additional methods static integrity constraints must remain valid inherent integrity constraint: existence of components Information Concept Topic
Page 1 and 2: The Extended Entity-Relationship Mo
Page 3 and 4: Instead of a Personal Profile: Gene
Page 5 and 6: Instead of a Personal Profile: Most
Page 7 and 8: A Picture Might Replace a Full Subs
Page 9 and 10: Cognition Completeness ✞ ☎ Sapi
Page 11 and 12: Comparison to Chen’s Original Cor
Page 13 and 14: Extended Entity-Relationship Models
Page 15 and 16: Structuring in HERM IS Modelling by
Page 17 and 18: IS Modelling by HERM 3.7.2012 B. Th
Page 19 and 20: Implicit Assumptions Set semantics:
Page 21 and 22: Basic Data Types IS Modelling by HE
Page 23 and 24: Graphical Notions Might Vary Person
Page 25 and 26: Generalising Cluster Types Examines
Page 27: Constraints IS Modelling by HERM 3.
Page 31 and 32: Constraints in Detail IS Modelling
Page 43 and 44: 14 (or 20) Kinds of NULL ‘Values
Page 47 and 48: Negation for NULL Marker Logics IS
Page 49 and 50: Truth Value Table IS Modelling by H
Page 51 and 52: Treatment in Predicates ✞ SQL:199
Page 57 and 58: Schemata Easily Get Large IS Modell
Page 59 and 60: Star Schema for Person IS Modelling
Page 61 and 62: Functionality Operations + dynamic
Page 63 and 64: HERM Query Algebra IS Modelling by
Page 65 and 66: Programming Support Through Visual
Page 71 and 72: The VisualSQL Tool IS Modelling by
Page 73 and 74: Ex.: Paper Submission Review System
Page 75 and 76: Yet an Example of a Workflow Diagra
Page 77 and 78: Resulting Orchestration Problems IS
Page 79 and 80:
Formalisation of the Business Proce
Page 81 and 82:
Views: Archiv view Description =
Page 83 and 84:
View: Insertion view for new course
Page 85 and 86:
IS Modelling by HERM 3.7.2012 B. Th
Page 87 and 88:
Pitfalls, Misunderstandings, Practi
Page 89 and 90:
Hierarchies in the Example 2: 1 IS
Page 91 and 92:
Cube B Data in the Example 2 IS Mod
Page 93 and 94:
Weighted Cube B Data in the Example
Page 95 and 96:
The Simpson Paradox ✞ Revisited b
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Generalising the Unique Name Assump
Page 103 and 104:
Page 105 and 106:
The Lattice of One Basic Data Type
Page 107 and 108:
Aims and assumptions Aggregation IS
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Repairing Approaches 1. Aggregation
Page 117 and 118:
Repairing Approaches 2. Preparing E
Page 119 and 120:
Behavior of Aggregation Functions I
Page 121 and 122:
Algebraic Aggregation Functions Han
Page 123 and 124:
Data Cube Definition (1) Grounding
Page 125 and 126:
Page 127 and 128:
Operations of the Data Cube cube cu
Page 129 and 130:
Extended Cube Schemata given cube c
Page 131 and 132:
Some General Results Roll-up functi
Page 133 and 134:
Page 135 and 136:
Modelling Assumptions: Roll-Up Func
Page 137 and 138:
Modelling Assumptions: Slice Functi
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Publications on Component Developme
Page 145 and 146:
Overview Information Systems Co-Des
Page 147 and 148:
Stone-age Computer Engineering No E
Page 149 and 150:
Why Do We Need Co-Design Support of
Page 151 and 152:
Application Systems are Task-Orient
Page 153 and 154:
Information Systems Co-Design 4.7.2
Page 155 and 156:
Constructs of the Co-Design Languag
Page 157 and 158:
Modern Information Systems Database
Page 159 and 160:
Page 161 and 162:
Different Scope - Need - Demand Inf
Page 163 and 164:
Page 165 and 166:
Application domain layer Abstractio
Page 167 and 168:
Classical dichotomy: Human-computer
Page 169 and 170:
The Software Engineering Quadruple
Page 171 and 172:
Conceptual Modelling of Collaborati
Page 173 and 174:
Support for Collaboration Informati
Page 175 and 176:
Services for Distribution: ✞ ☎
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Portfolio and Task Specification In
Page 183 and 184:
Coordination Specification Informat
Page 185 and 186:
Page 187 and 188:
Context of a Service Context: 〈na
Page 189 and 190:
Layers of a Typical Collaboration S
Page 191 and 192:
Experiences with Web Information Sy
Page 193 and 194:
Existing WIS Development Methods In
Page 195 and 196:
Differences from IS: Usage-Centredn
Page 197 and 198:
Storyboarding an Old Issue ? E.g.,
Page 199 and 200:
From Web 1.0 to Web 3.0 ((User and
Page 201 and 202:
Interactivity Specification Through
Page 203 and 204:
Scene Specification Scene expressio
Page 205 and 206:
Representation of Dialogue Steps wi
Page 207 and 208:
Storyboards: Example Wikis Informat
Page 209 and 210:
Support for Wikis Information Syste
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Formal Specification of Scenarios I
Page 219 and 220:
Formal Specification of Actions Inf
Page 221 and 222:
Application of SiteLang Specificati
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Making Co-Design Working: General D
Page 229 and 230:
Making Co-Design Working Usage, Usa
Page 231 and 232:
Making Co-Design Working Implementa
Page 233 and 234:
(WIS-E 1): Application Domain Descr
Page 235 and 236:
(WIS-E 1): Application Domain Descr
Page 237 and 238:
Abstraction Layers and SPICE Model
Page 239 and 240:
Evaluated Development by Rapid Prot
Page 241 and 242:
Layout and Playout: The General Pic
Page 243 and 244:
Example: Elli’s Juice trader •
Page 245 and 246:
Example: Elli’s Juice trader Entr
Page 247 and 248:
Data Types Information Systems Co-D
Page 249 and 250:
Extended Views Information Systems
Page 251 and 252:
Example Information Systems Co-Desi
Page 253 and 254:
Functionality Modelling: Attached O
Page 255 and 256:
Content Tailoring • four extensio
Page 257 and 258:
Adhesion Preorder and Proximity Val
Page 259 and 260:
Hierarchical Versions (2/2) Informa
Page 261 and 262:
Usage Modelling • distinguish bet
Page 263 and 264:
Relationship to Scenarios • consi
Page 265 and 266:
Figures • use a restricted form o
Page 267 and 268:
Presentation: The Container Metapho
Page 269 and 270:
Page 271 and 272:
Publications on Science and Art of
Page 273 and 274:
Publications on Pattern Development
Page 275 and 276:
Publications on Content Management
Page 277 and 278:
Database and Information Systems Th
Page 279 and 280:
Observations Information Systems Th
Page 281 and 282:
Pearls of Structuring ✞ ✝Lesson
Page 283 and 284:
Static Integrity Constraints Inform
Page 285 and 286:
The Constraints Handling Framework
Page 287 and 288:
Constraints: Supplanted Properties
Page 289 and 290:
Information Systems Theory 5.7.2012
Page 291 and 292:
However: Enrichment ✞ ☎ Lessons
Page 293 and 294:
Page 295 and 296:
Combinatorial Problems with Constra
Page 297 and 298:
Good Case however: Average Complexi
Page 299 and 300:
Good Case however: Average Complexi
Page 301 and 302:
Page 303 and 304:
Axiomatisation of Functional Depend
Page 305 and 306:
Functional Dependencies ✞ ✝Not
Page 307 and 308:
Page 309 and 310:
Multivalued Dependency X →→ Y |
Page 311 and 312:
Page 313 and 314:
Derivation Rules (structurally) Axi
Page 315 and 316:
Cardinality Constraints are Global
Page 317 and 318:
Page 319 and 320:
The Simplicity of Graphical Reasoni
Page 321 and 322:
Another FD Example Information Syst
Page 323 and 324:
Another FD Example Information Syst
Page 325 and 326:
FD-Set-Graphs Information Systems T
Page 327 and 328:
Page 329 and 330:
Graphical Reasoning for Ternary Cas
Page 331 and 332:
Page 333 and 334:
The Pentagonal Representation A qui
Page 335 and 336:
Feasibility ??? ✞ ✝The number o
Page 337 and 338:
Yet an Example of a Workflow Diagra
Page 339 and 340:
BPMN gateway Why not Petri Nets? In
Page 341 and 342:
The Pisa-Kiel BPMN-ASM Project Info
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
The Token Problem: Acyclic Case Inf
Page 349 and 350:
Page 351 and 352:
Control Flow Models Information Sys
Page 353 and 354:
ASM BPMN Assumptions Information Sy
Page 355 and 356:
Page 357 and 358:
The Concern Space of BPMN Separatio
Page 359 and 360:
Results for Token Problems Informat
Page 361 and 362:
Fitch Structures for Cyclic Diagram
Page 363 and 364:
The Token Problem: Vicious Cycle In
Page 365 and 366:
Orthogonal Concerns ✞ Co-design,
Page 367 and 368:
Variety of UML-“languages” Main
Page 369 and 370:
Challenges in Multi-Model Environme
Page 371 and 372:
Model Suite: Constituents Informati
Page 373 and 374:
Page 375 and 376:
Model Suite: Synchronisation and Co
Page 377 and 378:
Page 379 and 380:
Can The Designer Repair ECA Faults?
Page 381 and 382:
Integrity Enforcement via GCS inste
Page 383 and 384:
Page 385 and 386:
Identifiability, Identifier, Access
Page 387 and 388:
Object identifier ✞ ✝The devil
Page 389 and 390:
Page 391 and 392:
Values versus Objects Values: 7,
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Weak value-representability conside
Page 399 and 400:
Information Versus Knowledge and Da
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Publications on Object Identificati
Page 415 and 416:
Publications on Concepts, Content,
Page 417 and 418:
Publications on Science and Art of
show all

Higher-order entity-relationship modelling language, co-design and ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?