• Facets (new session)
• Description
• Metadata
• Settings
  • Rule: ActivityStreamsMapasEquivalentb3sb3sifpdbprdf-labelfacetshttp://dbpedia.org/resource/inference/rules/dbpedia#http://dbpedia.org/resource/inference/rules/opencyc#http://dbpedia.org/resource/inference/rules/umbel#http://dbpedia.org/resource/inference/rules/yago#http://dbpedia.org/schema/property_rules#http://www.ontologyportal.org/inference/rules/SUMO#http://www.ontologyportal.org/inference/rules/WordNet#http://www.w3.org/2002/07/owl#ldpoplwebskos-transurn:det:rdf:labelvirtrdf-labelvirtrdf-urlNone
    
  • Inverse Functional Properties: Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects
  • "Same As": Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects (recommended) Apply to subjects, objects and predicates (not recommended on big datasets) Apply to predicates only (special use cases only)

About: Architecture of Integrated Information Systems     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : yago:WikicatEnterpriseArchitectureFrameworks, within Data Space : dbpedia.org associated with source document(s)

Type: Thingyago:Abbreviation107091587yago:Abstraction100002137yago:Cognition100023271yago:Concept105835747yago:Content105809192yago:Form106290637yago:Hypothesis105888929yago:Idea105833840yago:LanguageUnit106284225yago:Model105890249yago:Part113809207yago:PsychologicalFeature100023100yago:Relation100031921yago:Word106286395programming languageyago:WikicatAbbreviationsyago:WikicatEnterpriseArchitectureFrameworks New Facet based on Instances of this Class

The ARIS concept (Architecture of Integrated Information Systems) by August-Wilhelm Scheer aims to ensure that an enterprise information system can completely meet its requirements. This framework is based on a division of the model into description views and levels, which allows a description of the individual elements through specially designed methods, without having to include the entire model. The methodology serves as a systems development life cycle for mapping and optimizing business processes. These processes are mapped for each description view, starting with the business management question up to the implementation on data processing level.