Pertemuan 14 Arsitektur Process Matakuliah : M0446/Analisa dan Perancangan Sistem Informasi

advertisement

Matakuliah

Tahun

Versi

: M0446/Analisa dan Perancangan Sistem Informasi

: 2005

: 0/0

Pertemuan 14

Arsitektur Process

1

Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu :

• Membagi class menjadi component

2

Outline Materi

• System Process

3

Application Domain Analysis in Context of OOA&D Activities

System Choice

(Pre-analysis)

System

Definition

Analysis of problem domain

Requirements for use

Analysis of application domain

(adapted from Mathiassen et al , 2000)

Model

Design of components

Specifications for architecture

Specifications for components

Design of architecture

Now continue with this area of activity and its product

4

Dua Bagian dari arsitektur

• Component architecture: Struktur sistem yang terdiri dari komponen yang saling terinterkoneksi

• Process architecture: struktur eksekusi sistem yang terdiri dari proses yang saling bergantungan (interdependent)

5

Arsitektur komponen dan proses

Component Architecture:

– Classes

– Stable aspects

– Related components

– Logical level

– Structure for descriptions

Process Architecture

– Objects

– Dynamic aspects

– Coordination of processes

– Physical level

– Structure for execution

(Mathiassen et al , 2000)

6

Process Architecture

7

Main Activities in

Architectural Design

Analysis document

Criteria

Component architecture

Finally, we’ll look at this activity

Process architecture Architectural specification

(Mathiassen et al , 2000)

8

Introduction

• Now concentrate on objects and their involvement in processes

• Need to coordinate when have multiple processes with shared resources

– Processors

– Program components

– External devices

• Results:

– Deployment diagram showing processors, assigned components, and active objects

– Outline of solutions for coordination mechanisms

9

When & Why

• Not a significant activity for a simple system with a single process, e.g. a stand-alone system

• Critical for large systems, especially monitoring and control systems, & embedded systems

• May wait to begin this activity until component architecture and components are nearly complete

• May start this activity early with exploratory and experimental work, which heavily influences components

10

Terminology

• Process Architecture: A system-execution structure composed of interdependent processes

• Process: A collection of operations that are executed in a bounded and linked sequence

• Processor: A piece of equipment that can execute a program

11

Terminology (2)

• Program Component: A physical module of program code

• Active object: An object that has been assigned a process

12

Processes, Active Objects, and

Shared Objects

Process

1

Object

1 o

1 o

2

Potential conflict over shared program component

Process 2

Active object because it starts a new process

Object 2

Object

4 o

7

Process 3 o

8 o

3 o

4

Process 4

Object 3 o

5 o

6

Object 5 o

9 o

10

13

Concurrency

• True concurrency: When two or more events in the system’s context can occur at the same time and processes must support this (e.g. multiple users)

• Random concurrency: When two or more operations are designed to be executed at the same time (e.g. print in background)

• Don’t have any choice about the former

14

Principles

• Aim at an architecture without bottlenecks

– would slow down the system and cause problems

• Distribute components on processors

• Coordinate resource sharing with active objects

15

Download