Knowledge

Modeling perspective

Source 📝

212:
object. The value of the state can only be accessed by sending a message to the object to call on one of its methods. An event is when an operation is being triggered by receiving a message, and the trace of the events during the existence of the object is called the object’s life cycle or the process of an object. Several objects that share the same definitions of attributes and operations can be parts of an object class. The perspective is originally based on design and programming of object oriented systems.
348: 231:
An illocutionary act consists of five elements: Speaker, hearer, time, location and circumstances. It is a reason and goal for the communication, where the participations in a communication act is oriented towards mutual agreement. In a communication act, the speaker generally can raise three claims:
198:
Rule perspective gives a description of goals/means connections. The main concepts in rule perspective are rule, goal and constraint. A rule is something that influences the actions of a set of actors. The standard form of rule is “IF condition THEN action/expression”. Rule hierarchies (goal-oriented
247:
perspective is a description of organisational and system structure. An actor can be defined as a phenomenon that influences the history of another actor, whereas a role can be defined as the behaviour which is expected by an actor, amongst other actors, when filling the role. Modeling within these
211:
perspective describes the world as autonomous, communicating objects. An object is an “entity” which has a unique and unchangeable identifier and a local state consisting of a collection of attributes with assignable values. The state can only be manipulated with a set of methods defined on the
181:
Behavioral perspective gives a description of system dynamics. The main concepts in behavioral perspective are states and transitions between states. State transitions are triggered by events. State Transition Diagrams (STD/STM), State charts and Petri-nets are some examples of well-known
152:
approach concentrates on describing the dynamic process. The main concept in this modeling perspective is the process, this could be a function, transformation, activity, action, task etc. A well-known example of a modeling language employing this perspective is data flow diagrams.
46:
The traditional way to distinguish between modeling perspectives is structural, functional and behavioral/processual perspectives. This together with rule, object, communication and actor and role perspectives is one way of classifying modeling approaches.
74: 60:
This approach concentrates on describing the static structure. The main concept in this modeling perspective is the entity, this could be an object, phenomena, concept, thing etc.
225: 328: 232:
truth (referring an object), justice (referring a social world of the participations) and claim to sincerity (referring the subjective world of the speaker).
173:
Now, with these symbols, a process can be represented as a network of these symbols. This decomposed process is a DFD, data flow diagram.
459: 275: 412: 228:. The basic assumption in this perspective is that person/objects cooperate on a process/action through communication within them. 384: 365: 17: 391: 249: 398: 431: 182:
behaviorally oriented modeling languages. Different types of State Transition Diagrams are used particularly within
325: 380: 369: 481: 486: 476: 213: 285: 280: 269: 405: 63:
The data modeling languages have traditionally handled this perspective, examples of such being:
358: 253: 36: 296: 40: 8: 187: 32: 291: 183: 121:
Constructed types built by abstraction: Aggregation, generalization, and association.
127:
Primitive types: Data types in GSM are classified into printable and abstract types.
199:
modeling), Tempora and Expert systems are some examples of rule oriented modeling.
149: 90: 39:
has a different focus, conceptualization, dedication and visualization of what the
332: 208: 454: 117:
Looking at the generic semantic modeling language we have the basic components:
450: 470: 321: 216:(UML) is a well known language for modeling with an object perspective. 302: 169:
External Entity: External to the modeled system, but interacts with it.
113:
Attributes: Used to give value to a property of an entity/relationship.
35:
is a particular way to represent pre-selected aspects of a system. Any
156:
The perspective uses four symbols to describe a process, these being:
94: 347: 68: 240: 463:. California : Sage Publications. (Third Edition 2009). 244: 224:
This perspective is based on language/action theory from
160:
Process: Illustrates transformation from input to output.
103:
Looking at the ER-language we have the basic components:
257: 166:
Flow: Movement of data or material in the process.
372:. Unsourced material may be challenged and removed. 163:
Store: Data-collection or some sort of material.
143: 55: 110:Relationships: An association among the entities. 468: 107:Entities: Distinctively identifiable phenomenon. 87:The NIAM language (Binary relationship language) 260:is an example of an actor oriented language. 235: 219: 460:Methodology for Creating Business Knowledge 276:Glossary of Unified Modeling Language terms 134:Printable: Used to specify visible values. 432:Learn how and when to remove this message 176: 248:perspectives is based both on work with 50: 14: 469: 250:object-oriented programming languages 202: 370:adding citations to reliable sources 341: 252:and work with intelligent agents in 193: 24: 444: 75:Generic Semantic Modeling language 25: 498: 346: 137:Abstract: Representing entities. 357:needs additional citations for 144:Functional modeling perspective 56:Structural modeling perspective 315: 13: 1: 308: 7: 263: 80:Other approaches including: 10: 503: 236:Actor and role perspective 214:Unified Modelling Language 226:philosophical linguistics 220:Communication perspective 286:Model Driven Engineering 281:General-purpose modeling 270:Domain-Specific Modeling 254:artificial intelligence 381:"Modeling perspective" 177:Behavioral perspective 297:Three schema approach 71:(Entity-Relationship) 51:Types of perspectives 18:Modeling perspectives 482:Scientific modelling 366:improve this article 29:modeling perspective 487:Systems engineering 477:Information systems 326:Conceptual modeling 150:functional modeling 33:information systems 331:2007-03-16 at the 203:Object perspective 188:telecommunications 43:is representing. 442: 441: 434: 416: 299:for data modeling 292:Modeling language 184:real-time systems 91:Conceptual graphs 16:(Redirected from 494: 437: 430: 426: 423: 417: 415: 374: 350: 342: 336: 319: 194:Rule perspective 21: 502: 501: 497: 496: 495: 493: 492: 491: 467: 466: 447: 445:Further reading 438: 427: 421: 418: 375: 373: 363: 351: 340: 339: 333:Wayback Machine 320: 316: 311: 266: 238: 222: 209:object-oriented 205: 196: 179: 146: 58: 53: 23: 22: 15: 12: 11: 5: 500: 490: 489: 484: 479: 465: 464: 451:Ingeman Arbnor 446: 443: 440: 439: 354: 352: 345: 338: 337: 313: 312: 310: 307: 306: 305: 300: 294: 289: 283: 278: 273: 265: 262: 237: 234: 221: 218: 204: 201: 195: 192: 178: 175: 171: 170: 167: 164: 161: 145: 142: 141: 140: 139: 138: 135: 129: 128: 125: 122: 115: 114: 111: 108: 101: 100: 99: 98: 88: 82: 81: 78: 72: 57: 54: 52: 49: 9: 6: 4: 3: 2: 499: 488: 485: 483: 480: 478: 475: 474: 472: 462: 461: 456: 452: 449: 448: 436: 433: 425: 422:November 2008 414: 411: 407: 404: 400: 397: 393: 390: 386: 383: –  382: 378: 377:Find sources: 371: 367: 361: 360: 355:This article 353: 349: 344: 343: 334: 330: 327: 323: 322:John Krogstie 318: 314: 304: 301: 298: 295: 293: 290: 287: 284: 282: 279: 277: 274: 271: 268: 267: 261: 259: 255: 251: 246: 242: 233: 229: 227: 217: 215: 210: 200: 191: 189: 185: 174: 168: 165: 162: 159: 158: 157: 154: 151: 136: 133: 132: 131: 130: 126: 123: 120: 119: 118: 112: 109: 106: 105: 104: 96: 92: 89: 86: 85: 84: 83: 79: 76: 73: 70: 66: 65: 64: 61: 48: 44: 42: 38: 34: 30: 19: 458: 455:Björn Bjerke 428: 419: 409: 402: 395: 388: 376: 364:Please help 359:verification 356: 317: 239: 230: 223: 206: 197: 180: 172: 155: 147: 116: 102: 62: 59: 45: 28: 26: 124:Attributes. 69:ER-language 37:perspective 471:Categories 392:newspapers 309:References 303:View model 190:systems. 457:(1997). 329:Archived 324:(2003). 264:See also 406:scholar 408:  401:  394:  387:  379:  413:JSTOR 399:books 288:(MDE) 272:(DSM) 241:Actor 77:(GSM) 41:model 453:and 385:news 245:role 243:and 207:The 186:and 148:The 95:Sowa 67:The 368:by 31:in 473:: 335:, 258:I* 256:. 27:A 435:) 429:( 424:) 420:( 410:· 403:· 396:· 389:· 362:. 97:) 93:( 20:)

Index

Modeling perspectives
information systems
perspective
model
ER-language
Generic Semantic Modeling language
Conceptual graphs
Sowa
functional modeling
real-time systems
telecommunications
object-oriented
Unified Modelling Language
philosophical linguistics
Actor
role
object-oriented programming languages
artificial intelligence
I*
Domain-Specific Modeling
Glossary of Unified Modeling Language terms
General-purpose modeling
Model Driven Engineering
Modeling language
Three schema approach
View model
John Krogstie
Conceptual modeling
Archived
Wayback Machine

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.