(public).sospep.subjects ~ view article ~ overview-application-model

<h1 style="text-align: center;">application model</h1>
<h2>[WHAT]</h2>
<ol>
<li>] describe the application using a modelling language/tools, class diagrams, sequence diagrams, collaboration diagrams, ...</li>
<li>] modelling the application, using the requirements spec to create ] use case diagrams, ] Class Diagrams, ] Sequence Diagrams, ] Collaboration Diagrams, ] Activity Diagram, ( considering the design patterns, tech spec, ) &nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>] to be used as a blueprint for the coding team</li>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>]</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li><strong>] UML (modelling language)</strong></li>
<ol>
<li><span style="text-decoration: line-through;">]<strong>&nbsp;SW requirements</strong>&nbsp;- a textual description of the overall responsibilities and scope</span></li>
<li>]&nbsp;<strong>Use Case Diagram</strong>&nbsp;- textual/graphical description of how the system will behave from the users perspective</li>
<li>]&nbsp;<strong>Class Diagram</strong>&nbsp;- visual blueprint of the objects that will be used to construct the system</li>
<li>]&nbsp;<strong>Sequence Diagram</strong>&nbsp;- sequence of object interaction as the program executes. Emphasis on the order of interactions and how the proceed over time</li>
<li>]&nbsp;<strong>Collaboration Diagram</strong>&nbsp;- how objects are organized to work together as the program executes. Emphasis is placed on the communications that occur between the objects.</li>
<li>]&nbsp;<strong>Activity Diagram</strong>&nbsp;- visual representation of the flow of execution of a process or operation</li>
</ol>
<li><strong>] application DESIGN PATTERNS ( by type )</strong></li>
<ol>
<li><strong>] creation</strong>&nbsp;-&nbsp;<a title="Factory method pattern" href="http://en.wikipedia.org/wiki/Factory_method_pattern"><span style="color: #0645ad;">Factory method pattern</span></a>,&nbsp;<a title="Abstract factory pattern" href="http://en.wikipedia.org/wiki/Abstract_factory_pattern"><span style="color: #0645ad;">Abstract factory pattern</span></a>,&nbsp;<a title="Singleton pattern" href="http://en.wikipedia.org/wiki/Singleton_pattern"><span style="color: #0645ad;">Singleton pattern</span></a>,&nbsp;<a title="Builder pattern" href="http://en.wikipedia.org/wiki/Builder_pattern"><span style="color: #0645ad;">Builder pattern</span></a>,&nbsp;<a title="Prototype pattern" href="http://en.wikipedia.org/wiki/Prototype_pattern"><span style="color: #0645ad;">Prototype pattern</span></a></li>
<li><strong>] structural -</strong>&nbsp;<a title="Adapter pattern" href="http://en.wikipedia.org/wiki/Adapter_pattern">Adapter pattern</a>,&nbsp;<a title="Bridge pattern" href="http://en.wikipedia.org/wiki/Bridge_pattern">Bridge pattern</a>,&nbsp;<a title="Composite pattern" href="http://en.wikipedia.org/wiki/Composite_pattern">Composite pattern</a>,&nbsp;<a title="Decorator pattern" href="http://en.wikipedia.org/wiki/Decorator_pattern">Decorator pattern</a>,&nbsp;<a title="Facade pattern" href="http://en.wikipedia.org/wiki/Facade_pattern">Facade pattern</a>,&nbsp;<a title="Flyweight pattern" href="http://en.wikipedia.org/wiki/Flyweight_pattern">Flyweight pattern</a>,&nbsp;<a title="Proxy pattern" href="http://en.wikipedia.org/wiki/Proxy_pattern">Proxy pattern</a></li>
<li><strong>] behavioural -</strong>&nbsp;<a title="Chain-of-responsibility pattern" href="http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern"><span style="color: #0645ad;">Chain-of-responsibility pattern</span></a>,&nbsp;<a title="Command pattern" href="http://en.wikipedia.org/wiki/Command_pattern"><span style="color: #0645ad;">Command pattern</span></a>,&nbsp;<a title="Interpreter pattern" href="http://en.wikipedia.org/wiki/Interpreter_pattern"><span style="color: #0645ad;">Interpreter pattern</span></a>,&nbsp;<a title="Iterator pattern" href="http://en.wikipedia.org/wiki/Iterator_pattern"><span style="color: #0645ad;">Iterator pattern</span></a>,&nbsp;<a title="Mediator pattern" href="http://en.wikipedia.org/wiki/Mediator_pattern"><span style="color: #0645ad;">Mediator pattern</span></a>,&nbsp;<a title="Memento pattern" href="http://en.wikipedia.org/wiki/Memento_pattern"><span style="color: #0645ad;">Memento pattern</span></a>,&nbsp;<a title="Observer pattern" href="http://en.wikipedia.org/wiki/Observer_pattern"><span style="color: #0645ad;">Observer pattern</span></a>,&nbsp;<a title="State pattern" href="http://en.wikipedia.org/wiki/State_pattern"><span style="color: #0645ad;">State pattern</span></a>,&nbsp;<a title="Strategy pattern" href="http://en.wikipedia.org/wiki/Strategy_pattern"><span style="color: #0645ad;">Strategy pattern</span></a>,&nbsp;<a title="Template method pattern" href="http://en.wikipedia.org/wiki/Template_method_pattern"><span style="color: #0645ad;">Template method pattern</span></a>,&nbsp;<a title="Visitor pattern" href="http://en.wikipedia.org/wiki/Visitor_pattern"><span style="color: #0645ad;">Visitor pattern</span></a>...</li>
<li><strong>] ? M V C -</strong></li>
<ol>
<li>model - is a representation of the data your application uses, classes are often representative of db tables</li>
<li>view - displays the data requested by user, data from model</li>
<li>controller - builds the model requried for view</li>
</ol>
<li><strong>] M V VM -</strong></li>
<ol>
<li>model - is the data</li>
<li>view - displays data to user</li>
<li>view model -&nbsp; state of data</li>
</ol></ol></ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<p style="text-align: left;">&nbsp;</p>

~ view article ~ Chapter] ch-006-application-model FROM [ Book] application-architecture IN [ libraries] technology-developer-software