Aris%20Architecture%20of%20Integrated%20Information%20Systems

1
ArisArchitecture of Integrated Information
Systems

• Business
• Process
• Modelling

Matteo Fiorillo Jyväskylä - Spring 2000
2
Key Issues

• Introduction of modelling methods

Development of respective meta models
Compilation of the models into an ARIS
information model
3
Concept

• An architecture for describing business processes
• Provides modelling methods
• It is foundation for the ARIS software system
• The house represents a concept for comprehensive
  computer-aided business process management

4
Strategic Business Process Analysis

• Carried out before the house is described
• Scrutinizes synergistics effects aiming for the
  highest standard of employee qualification
  possible
• Indentifies key goals, business areas,
  preliminary new business processes and weakspots

5
Modelling Strategic BPs

• Efficiency demands
• Resource (utilization of enterprise resources)
• Process (focus on corporate goals)
• Market (fully realize the potential of the
  market)
• In conflict with each other

6
Core Processes

• Impact corporate competitiveness
• Are cross-functional
• Interface with customers and suppliers alike

7
Core Processes

• Key groups
• Order logistics
• Product development
• Distinguished according to
• Degrees of complexity
• Customer groups

8
Critical Success Factors

• High quality standards
• High standards of delivery
• Competitive superiority in RD
• High flexibility

9
Functions

• Primary activities
• Create or utilize corporate output
• Secondary activities
• Support primaries by infrastructure or control
  measures
• Interaction with value added processes

10
Modelling the Function View

• Functions
• Described relative to other components
• Closely linked with data
• Described in the context with organizational
  objects (job positions)

11
Requirements Definition of the Function View

• BP strategy creates functions that enterprise
  must carry out efficiently
• Used synonymously with the term process, activity
  or task
• Describing its behaviour
• Different simbols
• Operation applied to objects for the purpose of
  supporting one or more goals
• They can support multiple goals

12
Function Structure

• Various aggregation levels
• Complex function bundles
• Complex function comprised of multiple activities
• Function
• Complex activity that can be broken down further,
  directly blending in with a function bundle

13
Function Structure

• Sub-function
• Activity which can be broken down into
  sub-functions or elementary functions, blending
  in with overriding functions
• Elementary function
• Activity which cannot be broken down further
• Activities that are completed at a job site or
  internal procedure structures without any
  processing alternatives

14
Grouping Elementary FunctionsInto Larger Units

• Identical procedures, identical information
  objects and identical allocation should be
  applied to identical business processes
• Nüttgens, Koordiniert-dezentrales
  Informationsmanagement 1995, p. 97

15
Procedure Sequences

• Logical function sequences are defined
• Recommended when triggering events or messages do
  not provide any additional information or they
  are added at a later point in time

16
Methods for the Description(Sequences)

• Network diagram
• Predecessors and successors relations
• Distance measurements
• Overlaps and minimum distance between events
• Logical links between the incoming and outgoing
  elements

17
Processing Types

• System functions
• Create customer
• Mantain customer data
• Create customer statistic
• Manual functions

18
Decision Models

• Information systems are also used for decision
  support
• more efficient, effective and fast decisions
  based on database contained and derived by the
  ITs
• (optimization of the production planning)

19
Function Configurations

• Process control
• Workflow control
• Application system configurations

Modeling Requirements
20
Application System Allocation

• Application system classes

• project control systems
• word processing
• business applications

activity based costing (times, amounts, cost
rates)
allocated to the functions
focus the project planning systems
The contents of the functions are configured
according to the function models
21
Requirements Definition of The Function View

• Software design

Data View
Input Data
Output Data
IT restrictions
Abstraction Principle
22
Designing Modules

• Autonomous function
• For incoming and outcoming data
• Data declaration
• Control logic
• Instruction components
• What a module does
• How it perform its task

23
Mini-specification

• Pseudocode and structograms

executing instructions
describing control structures (controlling
algorithm processes)
1. sequences 2. selections 3. repetitions
24
Implementing the Function View

• Ouput screens that can be interpreted as views
  on data model

programs are developed in one or several
programming languages
source code
stored in a program library
compiled and trasformed into object code
25
Modeling theOrganization View

• Business oriented
• Organization view

describes
Hierarchical organization (organizational units
with the communication and reporting
relationships among them)
Role concept
Requirements profile of an organizational unit
necessary for workflow applications
defines
26
Organizational Structures(Hierarchical
Organizations)

• Streamline the description of the enterprise,
  consolidating similar task groups
• Designations from type description are generally
  used
• Instances can be modeled as well
• Organizational units ( functions) can be created
  in accordance with activity, object or process
  parameters

27
Role Concept

• In addition to organizational units
• Employee types are described at the business
  level of process chain modeling
• Role a certain type of employee with clearly
  defined qualifications and skills
• Distinguishing user classes for designing or
  utilizing IT systems

28
Configuring Organizations

• Organizational models
• provide cost center definitions within the
  parameters of cost based accounting
• define important parameters (customers, company
  codes, plants)
• lay the groundwork for the allocation of
  functions and data to organizational units
• Organizational terms are documented in a precise
  manner according to their relation with the
  application and their impact on software
  procedures

29
Design Specifications

• Business organizational model is implemented into
  the information and communication topology
• In particular, we determine
• Network topologies (star, ring or bus)
• Capacity requirements
• Types of users access to the nodes
• Available types of components
• We define also the new hardware systems
  (component types)

30
Implementingthe Organization View

• It starts with the network topology of the design
  specification
• Networks and nodes can be implemented in
  different ways
• Logical networks
• Physical networks
• Relationships are not necessary for the
  information model

31
Modeling The Data View

• Description of the data objects, manipulated by
  functions
• The data objects designed in the requirements can
  be an effective basis on which to define the
  class of an object-oriented design method

32
Requirements Definition

• Business modeling mainly focuses on describing
  types
• Macro p.o.v. (voice, carrier system)
• Micro p.o.v. (type, attribute, relation type)
• What is an object? (referring to data)
• Wide range of document types
• Objects can interface with O.-O. Database systems
• They can have various roles
• They describe the control flow
• They illustrate the environment status of the BP

33
Macro Description

• Data that can be broken into more detailed
  elements is macro data
• Macro data objects can be linked with one another
  (customer file)
• Enterprise data models contain multiple area
  models, comprised of multiple data clusters
• Data objects
• Electronic-alphanumeric
• Sound, bitmaps or paper

34
Micro Description
Macro data objects are split up into smaller
units in the macro view
The detailed data structure can be modeled using
O.-O. class diagrams
Enhanced ERM methods
Simple ERM methods
35
Data Configuration
Data model
Allocates cost types and cost rates necessary to
calculate process cost
Allocates data objects to capacity planning
36
Data Configuration

• Data groups

information object
transported by workflow
access by means of workflow
non-traditional data
data stored in the information objects
37
Design Specifications of theData View
Database specific interface languages are
generated from the semantic data model
1 - information objects are transformed to
relations
2 - relations are optimized
3 - integrity conditions are defined
4 - relational schema is transformed into the
data description language
38
Implementing the Data View

• Conceptual schemes are modeled in internal
  schemes
• Database administrators have to structure the
  internal schema, creating efficient database
  structures
• Integrity and consistency are specified by
  procedural objects
• Definitions at the physical data structure level
  are due to the design goal of data independence

39
Modeling the Output View

• Output is the result of processes with the demand
  for input driving its execution
• Describing it is one of the key processes
• The term is heterogeneous and can be used at
  various levels of detail
• Note not implemented in a specific way

40
Requirements Definition of the Output View

• Describing product models as data models
• Definitions
• Output (or differents) required by areas beyond
  the business department where they were created
• What product centers deliver to entities outside
  their own organization meeting the demand of
  other entities, regardless of whether this demand
  is voluntary, driven by legal or any other
  requirements and regardless of whether those
  entities have to pay for the product or even
  choose not to do so

41
Ouput Configuration

• Process ouput is necessary material output is
  available as bills of materials
• Output models are used when configuring business
  applications with the global focus on the
  respective process

42
Summary

• What have we learned until now?
• What ARIS is
• What Strategic Business Process Analysis is
• How to
• model
• define requirements of
• implement

Individual ARIS Views
43
Summary

• What does come after?
• Relationship between the views (control view)
• Aris procedural models and applications
• Implementing standard software
• Implementing workflow systems
• Model supported system development
• Object oriented system development