HTML Microdata document

This HTML5 document contains 41 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

Prefix	IRI
dct	http://purl.org/dc/terms/
dbo	http://dbpedia.org/ontology/
foaf	http://xmlns.com/foaf/0.1/
n16	https://global.dbpedia.org/id/
dbt	http://dbpedia.org/resource/Template:
rdfs	http://www.w3.org/2000/01/rdf-schema#
freebase	http://rdf.freebase.com/ns/
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
owl	http://www.w3.org/2002/07/owl#
wikipedia-en	http://en.wikipedia.org/wiki/
dbp	http://dbpedia.org/property/
prov	http://www.w3.org/ns/prov#
dbc	http://dbpedia.org/resource/Category:
xsdh	http://www.w3.org/2001/XMLSchema#
wikidata	http://www.wikidata.org/entity/
gold	http://purl.org/linguistics/gold/
dbr	http://dbpedia.org/resource/

Statements

Subject Item: dbr:Trygve_Reenskaug
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:knownFor: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:Unified_Modeling_Language
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:Object_Oriented_Role_Analysis_and_Modeling
rdf:type: dbo:Software
rdfs:label: Object Oriented Role Analysis and Modeling
rdfs:comment: The OOram (Object-oriented Role Analysis and Modeling) is a method, based on the concept of role, for performing object-oriented modeling. Originally (1989) coined Object Oriented Role Analysis, Synthesis and Structuring (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug (1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon. The use of "roles" in OOram is similar in application to that of agent-oriented programming.
dct:subject: dbc:Object-oriented_programming
dbo:wikiPageID: 2404816
dbo:wikiPageRevisionID: 1103972430
dbo:wikiPageWikiLink: dbr:Agent-oriented_programming dbr:Trygve_Reenskaug dbr:View_model dbc:Object-oriented_programming dbr:Kantega dbr:Object_modeling_language dbr:Enterprise_model dbr:I* dbr:Unified_Modeling_Language
owl:sameAs: wikidata:Q7075043 freebase:m.079s3w n16:4sxvD
dbp:wikiPageUsesTemplate: dbt:Reflist dbt:Cite_book
dbo:abstract: The OOram (Object-oriented Role Analysis and Modeling) is a method, based on the concept of role, for performing object-oriented modeling. Originally (1989) coined Object Oriented Role Analysis, Synthesis and Structuring (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug (1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon. The use of "roles" in OOram is similar in application to that of agent-oriented programming. Enterprise models created according to OOram may have a number of views, with each view presenting certain aspects of a model. The following ten views are proposed: 1. * Area of concern view: Textual description of a phenomenon represented in the role model. 2. * Stimulus-response view: Describes how environment roles may trigger activities in the organization (stimulus), together with the effect (response). 3. * Role list view: List describing all roles of a role model together with attributes and textual explanation. 4. * Semantic view: Describes meaning of roles and relationships between roles. 5. * Collaboration view: Describes patterns of roles and message paths. 6. * Interface view: Describes all messages that can be sent along a message path. 7. * Scenario view: Provides a sample sequence of messages flowing between roles (a concrete example). 8. * Process view: Describes data flow between roles and associated activities performed by the roles. 9. * State diagram view: For each role, the legal states can be described together with messages that trigger transitions. 10. * Method specification view: Describes what messages to send for each method belonging to a role. May also specify procedures to perform. OOram suggests a varied mix of formal and informal notations and languages for representing and communicating models. Which view to use depends upon the needs in a particular situation.
gold:hypernym: dbr:Method
prov:wasDerivedFrom: wikipedia-en:Object_Oriented_Role_Analysis_and_Modeling?oldid=1103972430&ns=0
dbo:wikiPageLength: 3395
foaf:isPrimaryTopicOf: wikipedia-en:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:OORAM
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:OORam
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:OOram
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:OOram_role_modeling_method
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:Object-Oriented_role_analysis_and_modeling
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: dbr:Object_Oriented_Role_Analysis_Method
dbo:wikiPageWikiLink: dbr:Object_Oriented_Role_Analysis_and_Modeling
dbo:wikiPageRedirects: dbr:Object_Oriented_Role_Analysis_and_Modeling

Subject Item: wikipedia-en:Object_Oriented_Role_Analysis_and_Modeling
foaf:primaryTopic: dbr:Object_Oriented_Role_Analysis_and_Modeling