Décomposition

d´composition

Embalming is the practice of delaying decomposition of human and animal remains. Embalming slows decomposition somewhat, but does not forestall it indefinitely. Embalmers typically pay great attention to parts of the body seen by mourners, such as the face and hands. The chemicals used in embalming repel most insects, and slow down bacterial putrefaction by either killing existing bacteria in or on the body themselves or by “fixing” cellular proteins, which means that they cannot act as a nutrient source for subsequent bacterial infections. In sufficiently dry environments, an embalmed body may end up mummified and it is not uncommon for bodies to remain preserved to a viewable extent after decades. Notable viewable embalmed bodies include those of:

Eva Perón of Argentina, whose body was injected with paraffin was kept perfectly preserved for many years, and still is as far as is known (her body is no longer on public display). Lenin, whose body was kept submerged in a special tank of fluid for decades and is on public display in Lenin’s Mausoleum. Other communist leaders such as Mao Zedong, Kim Il-sung, Ho Chi Minh and most recently Kim Jong-il have also had their cadavers preserved in the fashion of Lenin’s preservation and are now displayed in their respective mausoleums. Pope John XXIII, whose preserved body can be viewed in St. Peter’s Basilica. Padre Pio, whose body was injected with formalin prior to burial in a dry vault[citation needed] from which he was later removed and placed on public display at the San Giovanni Rotondo.

Decomposition topicsDecomposition paradigm

A decomposition paradigm in computer programming is a strategy for organizing a program as a number of parts, and it usually implies a specific way to organize a program text. Usually the aim of using a decomposition paradigm is to optimize some metric related to program complexity, for example the modularity of the program or its maintainability.

Most decomposition paradigms suggest breaking down a program into parts so as to minimize the static dependencies among those parts, and to maximize the cohesiveness of each part. Some popular decomposition paradigms are the procedural, modules, abstract data type and object oriented ones.

The concept of decomposition paradigm is entirely independent and different from that of model of computation, but the two are often con-fused, most often in the cases of the functional model of computation being confused with procedural decomposition, and of the actor model of computation being confused with object oriented decomposition.Decomposition diagram

Decomposition Structure

Negative Node-Numbered Context

Static, Dynamic, and Requirements Models for Systems Partition

Functions and Use Scenarios Mapping to Requirements and Goals

A decomposition diagram shows a high-level function, process, organization, data subject area, or other type of object broken down into lower level, more detailed components. For example, decomposition diagrams may represent organizational structure or functional decompo-sition into processes. Decomposition diagrams provide a logical hierarchical decomposition of a system.

Eve

nt p

artit

ioni

ngJ

ump

to: n

avig

atio

n, se

arch

Con

tent

s

1

Act

or ˜

Eve

nt ˜

Det

ect ˜

Res

pond

2

Ide

ntify

ing

Req

uire

men

ts a

nd T

heir

Rea

sons

3

Defi

ning

requ

irem

ents

4

Com

plex

ity v

ersu

s fra

gmen

tatio

n

5 S

ee a

lso

6 R

efere

nces

The

goa

l of e

vent

par

titio

ning

is to

be a

n ea

sy-t

o-ap

ply

syst

ems a

naly

sis te

chni

que t

hat h

elps t

he a

naly

st o

rgan

-ise

requ

irem

ents

for l

arge

syst

ems i

nto

a co

llect

ion

of sm

aller

, sim

pler,

min

imal

ly-c

onne

cted

, eas

ier-t

o-un

ders

tand

‘m

ini s

yste

ms’

/ use

case

s. T

he a

ppro

ach

is ex

plai

ned

by S

teph

en M

. McM

enam

in a

nd J

ohn

F. P

alm

er in

E

ssen

tial S

yste

ms A

naly

sis.[

1] A

brie

f ver

sion

of th

e app

roac

h is

desc

ribed

in th

e art

icle o

n D

ata

Flo

w

Dia

gram

s. A

mor

e com

plet

e disc

ussio

n is

in E

dwar

d Y

ourd

on’s

Jus

t Eno

ugh

Stru

ctur

ed A

naly

sis.[

2] T

he

desc

riptio

n fo

cuse

s on

usin

g th

e tec

hniq

ue to

crea

te d

ata

flow

dia

gram

s, bu

t it c

an b

e use

d to

iden

tify

use c

ases

as

well

.

The

pre

mise

of e

vent

par

titio

ning

is th

at sy

stem

s exi

st to

resp

ond

to ex

tern

al ev

ents

: ide

ntify

wha

t hap

pens

in

the b

usin

ess e

nviro

nmen

t tha

t req

uire

s pla

nned

resp

onse

s, th

en d

efine

and

bui

ld sy

stem

s to

resp

ond

acco

rdin

g to

th

e rul

es o

f the

bus

ines

s. I

n pa

rticu

lar,

a bu

sines

s sys

tem

exist

s to

serv

ice th

e req

uest

s of c

usto

mer

s. A

cust

omer,

in

the j

argo

n of

the U

ML,

is a

n ‘a

ctor

.’

If the response is lengthy or complex (i.e., more than a page of text), an ana-

lyst may decompose (‘factor out’ or deduplicate) into smaller ‘secondary use

cases’ to keep the ‘parent’ primary use case smaller and simpler. These second-

ary use cases may prove to be reusable as well. (In a UML use case diagram,

they would be drawn as extended or included use cases, which are related to

one or more primary use cases.)

While describing a use case, an analyst may also uncover ‘business rules’.

Some analysts suggest capturing business rules in a separate document using

the Object Constraint Language or some other formal notation. Then when a

business rule must be obeyed in a use case, the analyst makes reference to it.

This minimises repetition within a specification, but risks fragmentation of a

specification. One technique that may reduce this tension is to use hyperlinks in

the specification document.

In addition to functional requirements captured in a use case description, an

analyst may include such non-functional requirements as response time, learn-

ability, etc.

Décomposition

Documents

Transcript of Décomposition