<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2171/18/9/_/styles/combined.css?spaceKey=TOP&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Architecture">Architecture</a></h2>
<h4>Comment <b>removed</b> by <a href="https://wiki.asterisk.org/wiki/display/~beagles">Brent Eagles</a>
</h4>
<br/>
<div class="notificationGreySide">
<p>1. In the first paragraph, in lieu of "the layers are not dependent on each other as much as it might appear, unlike a traditional layered development model."... Layered diagrams are not tightly standardized, and it's common to see liberties taken with these diagrams. As such, I would simply add a clarifying statement to make our usage clear, such as "Implementations of concepts defined in higher level layers can directly access any layer beneath them. Elements within a given layer often have associations with other elements within the same layer." </p>
<p>2. On the System Services Layer - "In many cases, the components that implement these interfaces are doing so as a way of mapping an external tool or service into the Asterisk SCF system." Is that really the defining characteristic of the layer? I would think something like "The components that implement these interfaces provide services that we expect to be of utility across the vertical domain stacks." </p>
<p>3. You don't seem to like the word "Stacks" that's in the diagram. I think it's actually quite descriptive of what each domain is. A vertical grouping of Domain-Specific layers. But if not, we should change the diagram to match your description. </p>
<p>4. Under components, I'd chop the leading clause "Unlike most traditional applications," and just lead with the assertive: "Asterisk SCF was designed from the very beginning to be a distributed application."</p>
<p>5. 2nd paragraph of Components ... I'd replace "design requires that" with "design encourages". </p>
<p>6. We'll want to wrap up with a summary that describes the benefits of our architecture, with a concise mapping of which design aspects address which goals. </p>
<p>7. We should just delete Draft 1, and rename this page "Architecture".</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=TOP">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>