blob: 9b12f7a1e31a8b1ce2329300a3095ced72db0204 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
<?xml version="1.0" encoding="iso-8859-1" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd-->
<html xmlns="http://www.w3.org/1999/xhtml"
>
<head><title>Reduction of Complexity</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<!-- xhtml,3,next,html -->
<meta name="src" content="etrice-doc.tex" />
<meta name="date" content="2013-03-25 22:23:00" />
<link rel="stylesheet" type="text/css" href="etrice-doc.css" />
</head><body
>
<!--l. 9--><div class="crosslinks"><p class="noindent">[<a
href="etrice-docch2.html" >next</a>] [<a
href="etrice-docse1.html" >prev</a>] [<a
href="etrice-docse1.html#tailetrice-docse1.html" >prev-tail</a>] [<a
href="#tailetrice-docse2.html">tail</a>] [<a
href="etrice-docch1.html#etrice-docse2.html" >up</a>] </p></div>
<h3 class="sectionHead"><span class="titlemark">1.2 </span> <a
id="x5-40001.2"></a>Reduction of Complexity</h3>
<!--l. 11--><p class="noindent" >eTrice is all about the reduction of complexity:
</p>
<ul class="itemize1">
<li class="itemize">structural complexity
<ul class="itemize2">
<li class="itemize">by explicit modeling of hierarchical Actor containment, layering and
inheritance</li></ul>
</li>
<li class="itemize">behavioral complexity
<ul class="itemize2">
<li class="itemize">by hierachical statemachines with inheritance</li></ul>
</li>
<li class="itemize">teamwork complexity
<ul class="itemize2">
<li class="itemize">because loosely coupled Actors provide a natural way to structure
team work
</li>
<li class="itemize">since textual model notation allows simple branching and merging</li></ul>
</li>
<li class="itemize">complexity of concurrent & distributed systems
<ul class="itemize2">
<li class="itemize">because loosely coupled Actors are deployable to threads, processes,
nodes</li></ul>
</li>
<li class="itemize">complexity of variant handling and reuse (e.g. for product lines)
<ul class="itemize2">
<li class="itemize">by composition of existing Actors to new structures
</li>
<li class="itemize">since Protocols and Ports make Actors replaceable
</li>
<li class="itemize">by inheritance for structure, behavior and Protocols
</li>
<li class="itemize">by making use of model level libraries</li></ul>
</li>
<li class="itemize">complexity of debugging
<ul class="itemize2">
<li class="itemize">model level debugging: state machine animation, data inspection and
manipulation, message injection, generated message sequence charts
</li>
<li class="itemize">model checking easier for model than for code (detect errors before
they occur)</li></ul>
</li></ul>
<!--l. 1--><div class="crosslinks"><p class="noindent">[<a
href="etrice-docch2.html" >next</a>] [<a
href="etrice-docse1.html" >prev</a>] [<a
href="etrice-docse1.html#tailetrice-docse1.html" >prev-tail</a>] [<a
href="etrice-docse2.html" >front</a>] [<a
href="etrice-docch1.html#etrice-docse2.html" >up</a>] </p></div>
<!--l. 1--><p class="noindent" ><a
id="tailetrice-docse2.html"></a> </p>
</body></html>
|
