<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Architectural Pattern and Component Diagram Section 06 by Shahliza Abd Halim</title>
      <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp</link>
      <description>All teams have to find suitable architectural patterns to represent the 5 architectural pattern covered in lecture
</description>
      <language>en-us</language>
      <pubDate>2018-04-17 05:44:21 UTC</pubDate>
      <lastBuildDate>2024-11-21 19:54:26 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425656</link>
         <description><![CDATA[<div>What are the components interacting with each other?<br>What type of components? dll, exe&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:46:10 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425656</guid>
      </item>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425813</link>
         <description><![CDATA[<div>State ONE special feature that makes you think this pattern is client server?</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:48:07 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425813</guid>
      </item>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425836</link>
         <description><![CDATA[<div>State ONE special feature that makes you think this pattern is Model View Controller?</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:48:18 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425836</guid>
      </item>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425861</link>
         <description><![CDATA[<div>State ONE special feature that makes you think this pattern is pipe and filter?</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:48:35 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425861</guid>
      </item>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425884</link>
         <description><![CDATA[<div>State ONE special feature that makes you think this pattern is repository?</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:48:51 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425884</guid>
      </item>
      <item>
         <title>Group name</title>
         <author>shahliza_abd_halim</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425921</link>
         <description><![CDATA[<div>State ONE special feature that makes you think this pattern is layered?</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 05:49:11 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252425921</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author>logesrao97</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442295</link>
         <description><![CDATA[<div>MVC separates domain, application and business logic from the rest of the user interface. It does this by separating the application into three parts which is the <mark>model</mark>, the <mark>view</mark>, and the <mark>controller. </mark>&nbsp;<br><br><strong><mark>Advantages of using MVC</mark></strong><br>- <strong><em>Reusability </em></strong><br>&nbsp;Use the same model for different<br>&nbsp;views<br>- <strong><em>Encourages well-defined<br>&nbsp; interfaces<br></em></strong><br>- <strong><em>Simplicity</em></strong><br>&nbsp; &nbsp;Each part is simpler and easier<br>&nbsp; &nbsp;to understand, implement and<br>&nbsp; &nbsp;test.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/238623821/ec20c4d73f863da700ae7895769b362c/model_view_controller_mvc_explained.jpg" />
         <pubDate>2018-04-17 07:13:39 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442295</guid>
      </item>
      <item>
         <title>Magikarp</title>
         <author>xiaoying5214</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442298</link>
         <description><![CDATA[<div>This pattern consists of 2 parities which is  client and server. This server components will provide services to multiple client components.  In many cases, the server is a database with application logic represented as stored procedures. Example is online application which is banking, email and document sharing.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775466/842ebb6e1460ac7aef256b99272ae8fe/client_server_model.jpg" />
         <pubDate>2018-04-17 07:13:41 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442298</guid>
      </item>
      <item>
         <title>G.R.I.T.</title>
         <author>alifnizam1997</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442321</link>
         <description><![CDATA[<div> </div><div>Client-Server Architecture consists of two types of components: clients and servers. </div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282772396/60236c32d945505ca775569091297629/image002.jpg" />
         <pubDate>2018-04-17 07:13:46 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442321</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>shamin_arissa65</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442451</link>
         <description><![CDATA[<div>In the diagram, Bank transaction authorizer, ATM monitoring server and ATM reconfiguration server <mark>provide client request </mark>from ATM main process, Reconfigure and update process and monitoring station program.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282771748/77e76c055ade3c3252921f914902278d/1.jpg" />
         <pubDate>2018-04-17 07:13:56 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442451</guid>
      </item>
      <item>
         <title>MAGIKARP</title>
         <author>syamimlfc97</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442573</link>
         <description><![CDATA[<div>Layered pattern can be used to structure programs that can be decomposed into groups of subtasks, each of which is at a particular level of abstraction. Each layer provides services to the next higher layer.<br>&nbsp;<figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:843,&quot;url&quot;:&quot;https://www.safaribooksonline.com/library/view/software-architecture-patterns/9781491971437/assets/sapr_0101.png&quot;,&quot;width&quot;:1127}" data-trix-content-type="image" data-trix-attributes="{&quot;caption&quot;:&quot;Layered Architecture Pattern&quot;}"><img src="https://www.safaribooksonline.com/library/view/software-architecture-patterns/9781491971437/assets/sapr_0101.png" width="1127" height="843"><figcaption class="attachment__caption attachment__caption--edited">Layered Architecture Pattern</figcaption></figure></div><div>4 layers of a general information system are as follows:<br><br>--&gt; <strong>Presentation layer </strong>(also known as <strong>UI layer</strong>)</div><div>The presentation layer is responsible for the following:</div><ul><li>Data encryption/decryption</li><li>Character/string conversion</li><li>Data compression</li><li>Graphic handling&nbsp;</li></ul><div><br></div><div>--&gt;<strong>Application layer </strong>(also known as <strong>service layer</strong>)</div><div>The application layer provides many services, including:</div><ul><li>Simple Mail Transfer Protocol</li><li>File transfer</li><li>Web surfing</li><li>Web chat</li><li>Email clients</li><li>Network data sharing</li><li>Virtual terminals</li><li>Various file and data operations</li></ul><div><br>&nbsp;--&gt; <strong>Business logic layer </strong>(also known as <strong>domain layer</strong>)<br> Business logic is the programming that manages communication between an end user interface and a database.&nbsp;<br>Business rule describes :</div><ul><li>&nbsp;specific procedure</li><li>a workflow consists of the tasks</li><li>procedural steps&nbsp;</li><li>required input and output information&nbsp;</li><li>tools needed for each step of that procedure.&nbsp;</li></ul><div><br></div><div>--&gt;<strong>Data access layer</strong> (also known as <strong>persistence layer</strong>) <br> <strong>Data access layer</strong>.in computer software, is a <strong>layer</strong> of a computer program which provides simplified <strong>access</strong> to <strong>data</strong> stored in persistent storage of some kind, such as an entity-relational <strong>database</strong>.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:14:29 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442573</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>liew_chongmeng</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442722</link>
         <description><![CDATA[<div> </div><ol><li>Model: The HTML is the "skeleton" of bedrock content. Text that communicates information to the reader.</li><li>View: The CSS adds visual style to the content. It is the "skin" that we use to flesh out our skeleton and give it a particular look. We can swap in different skins via CSS without altering the original content in any way. They are relatively, but not completely, independent.</li><li>Controller: The browser is responsible for combining and rendering the CSS and HTML into a set of final, manipulatible pixels on the screen. It gathers input from the user and marshals it to any JavaScript code necessary for the page to function. But here, too, we have flexibility: we can plug in a different brower and get comparable results. Some browsers might render it faster, or with more fidelity, or with more bells and whistles. </li></ol>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/279769890/153bf9fd33a8bb560924a05c37535572/mvc.jpg" />
         <pubDate>2018-04-17 07:15:06 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442722</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author>farazanaamin</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442804</link>
         <description><![CDATA[<div> </div><ul><li><strong>Pipes and Filters</strong> consist of a chain of processes or other data processing entities, arranged so that the output of each element of the chain is the input of the next. </li><li> implemented in a <strong>multitasking operating system</strong>, by launching all <strong>processes</strong> at the same time, and automatically servicing the data read requests by each process with the data written by the upstream process .</li><li> <br><br><strong>Filter </strong><br>•Independent entities <br>•Does not share state with other filters. <br>•No do not know the identity to upstream and downstream filters. <br><br><strong>Pipes </strong><br>•Stateless data stream <br>•Source end feeds filter input and sink receives output. </li></ul>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282771639/88c7f75ca34389da90cb6d2665e5dcbd/pipes_and_filters_message_queues.png" />
         <pubDate>2018-04-17 07:15:27 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442804</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442813</link>
         <description><![CDATA[<div> </div><ul><li>Describes the organization and wiring of the physical components in a system.</li><li>Component :-</li></ul><div><br></div><ol><li>Component</li></ol><div><figure class="attachment attachment--preview"><img src="https://lh6.googleusercontent.com/utWf6HsYOiJfYU8TqvB1TpYUGkaJ3tuiZ1EqlOxPhtlHJz3kZTXY0loXdDmcudgv1uclnzmnl3Q6PB53Nr4IdIDS4xuk4wNe5lW0vBNbrOwNOL5_kTx38dJAjUTT6SzC-8p2hmDk" width="261" height="88"><figcaption class="attachment__caption"></figcaption></figure></div><div><br></div><div>b) Interface</div><div><figure class="attachment attachment--preview"><img src="https://lh5.googleusercontent.com/NK7KQnWuLn5E2D1DQQgbmfR9STkSPUHxDcBRmh7piJKXwoRSRmtj_JeenbP_bnYgOvWvU_Ql16XsSAaRznDs0799WHYgpAt9uH8oe6Sxb6tBzTMZZTQQ8FTZeBNZ_uO_vM88xdXh" width="403" height="118"><figcaption class="attachment__caption"></figcaption></figure></div><div><br></div><div>c) Dependencies</div><div><br></div><div><figure class="attachment attachment--preview"><img src="https://lh3.googleusercontent.com/oxcrX-NVB4Vw18q7mGJ_PyEByK4FMRlNSm1qoSvRfjtfddi7Ah6kubqfLdAoVN9th71ox3947XBe41leE_Y62Jsv0HXDpOALVk1QUxQ7ilCbSGaG26SR17ptp6xPqKfRzrVhkbuw" width="403" height="118"><figcaption class="attachment__caption"></figcaption></figure></div><div>d) Port</div><div><br></div><div><figure class="attachment attachment--preview"><img src="https://lh6.googleusercontent.com/YsbTtvWQ36veIDcxAjB2rRIs2LVj9vYQWNxh4iVbiRQ7ct8YiuSLKKtYILR2qvDA1S1A_Z1CXwx-XRuQty8k_E4hYNIJB993tMN8M9Il_BKDohaxQELP_M6KNsXIhwj6BSpJ1fVm" width="403" height="118"><figcaption class="attachment__caption"></figcaption></figure></div><div><br>Example :<br> <figure class="attachment attachment--preview"><img src="https://www.researchgate.net/profile/Nayyab_Naqvi/publication/280247984/figure/fig1/AS:284602217320455@1444865864450/UML-component-diagram-of-our-framework-with-the-Smart-Lens-application-components.png" width="691" height="300"><figcaption class="attachment__caption"></figcaption></figure>  <figure class="attachment attachment--preview"><img src="https://www.edrawsoft.com/templates/images/online-reading-uml-component.png" width="650" height="414"><figcaption class="attachment__caption"></figcaption></figure> <br><br></div><div><br><br> </div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:15:29 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442813</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442827</link>
         <description><![CDATA[<div>Repository means the <mark>central location of data</mark>, hence the special feature is that all of the information comes from a central database. </div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775327/ff9a699451632758ccf33d9130080d5e/data_centered_architecture.jpg" />
         <pubDate>2018-04-17 07:15:31 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442827</guid>
      </item>
      <item>
         <title>G.R.I.T</title>
         <author>alifnizam1997</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442973</link>
         <description><![CDATA[<div>Used for developing user interface that divides an application into three interconnected parts.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282772396/16ed713b16bfba73a2876e7f29985dce/500px_MVC_Process_svg.png" />
         <pubDate>2018-04-17 07:16:11 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252442973</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author>azhar0528</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443272</link>
         <description><![CDATA[<div>This architectural pattern is divided into two applications, where the client make the request to the server. The server is actually a database with application logic represented as stored procedures. A server too can be specialized in server applications, files, terminal or email.<br><br></div><div><strong>ONE</strong> of the most special features of client server architectural pattern is mix and match platforms. Client and server <strong><mark>can be mixed and</mark></strong><mark> </mark><strong><mark>matched for different platforms.</mark></strong><strong><em><mark> </mark></em></strong>One of the example is the hardware and operating system can be well intermixed. The figure below shows how client and server architectural pattern works.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775890/d9d2e53b6284fbe03d398ad2ff6abd05/Client_server_model" />
         <pubDate>2018-04-17 07:17:22 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443272</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443284</link>
         <description><![CDATA[<div> <strong><figure class="attachment attachment--preview"><img src="https://lh5.googleusercontent.com/JgAIEK_ft_pbxybfzlWlAtPDn-ruPfYLiPILjHItvBian_GTfsJyLbE9sCcM1rNVU32mxbMgs8P-IpvLNye4nsG7vWVeKimpzYgEl40VXlXj9PAS66ZlvLCksYx4AgW-TDCW7Kvg" width="525" height="221"><figcaption class="attachment__caption"></figcaption></figure></strong> Used to structure programs that can be decomposed into groups of subtasks, each of which is at a particular level of abstraction. Each layer provides services to the next higher layer. <br><br><br></div><div><br>The most commonly found 4 layers of a general information system are as follows.</div><ul><li><strong>Presentation layer </strong>(also known as <strong>UI layer</strong>)</li><li><strong>Application layer </strong>(also known as <strong>service layer</strong>)</li><li><strong>Business logic layer </strong>(also known as <strong>domain layer</strong>)</li><li><strong>Data access layer</strong> (also known as <strong>persistence layer</strong>)</li></ul><div><br><strong><br>Usage</strong></div><ul><li>General desktop applications.</li><li>E commerce web applications.</li></ul><div><br>One special feature that makes us think this pattern is layered is when there is a grouping of related functionality into distinct layers that are stacked on top of each other. And it is an  <em>inverted pyramid of reuse</em> where each layer aggregates the responsibilities and abstractions of the layer directly beneath it .</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:17:24 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443284</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443386</link>
         <description><![CDATA[<div>This architectural pattern consist of Client and Server. Diagram below shows the client-server for application.<br><br>&nbsp;</div><div>A computer network diagram of clients communicating with a server via the Internet.</div><div><br></div><ul><li>The <strong>client–server model</strong> is a distributed application structure that partitions tasks between servers and clients.&nbsp;</li><li>Clients and servers communicate over a computer network on separate hardware.</li><li>A server host share their resources with clients.&nbsp;</li><li>A client does not share any of its resources, but requests a server's content or service function.</li><li>Clients initiate communication sessions with servers which await incoming requests.&nbsp;</li><li>Examples of computer applications that use the client–server model are Email, network printing, and the World Wide Web.&nbsp;</li></ul><div><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/f8ae967d861ab425359d8403ed747549/Client_Server.png" />
         <pubDate>2018-04-17 07:17:48 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443386</guid>
      </item>
      <item>
         <title>G.R.I.T.</title>
         <author>alifnizam1997</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443718</link>
         <description><![CDATA[<div> The Pipe and Filter is an architectural design pattern that allows for stream/asynchronous processing. In this pattern, there are many components, which are referred to as filters, and connectors between the filters that are called pipes. Each filter is responsible for applying a function to the given data; this is known as filtering. Filters can work asynchronously. The final output is given to the consumer, known as a sink <br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282772396/651f99f16460e0a51132e3cc7cd9e60e/Capture.png" />
         <pubDate>2018-04-17 07:19:11 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252443718</guid>
      </item>
      <item>
         <title>G.R.I.T.</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444025</link>
         <description><![CDATA[<div>A <strong>repository architecture</strong> is a system that will allow several interfacing components to share the same data. Each component interfaces the same dataset that is utilized system wide. Data manipulation taking place in one component will reflect an identical representation of data in another component. <br><br></div>]]></description>
         <enclosure url="http://healthstandards.com/wp-content/uploads/2012/02/Centralized-HIE.jpg" />
         <pubDate>2018-04-17 07:20:25 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444025</guid>
      </item>
      <item>
         <title>MAGIKARP</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444115</link>
         <description><![CDATA[<div>It is important to think of the repository pattern so that if the Model layers needs some breaking changes, then it should have minimum or no maintenance impact on the controller layer.&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282780994/85ca9139b33a81dcd0d01edca1802f36/Picture1.png" />
         <pubDate>2018-04-17 07:20:46 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444115</guid>
      </item>
      <item>
         <title>Magikarp</title>
         <author>nazatulasyikin96</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444150</link>
         <description><![CDATA[<div>&nbsp; &nbsp;is a pattern used to isolate business logic from the user interface.<br><br>&nbsp;Model&nbsp; =&gt; the information (the data) of the application and the business rules used to manipulate the data<br><br>&nbsp;View =&gt; corresponds to elements of the user interface such as text, checkbox items, and so forth, and the Controller manages details involving the communication between the model and view. <br><br>&nbsp;controller =&gt; handles user actions such as keystrokes and mouse movements and pipes them into the model or view as required<figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:400,&quot;url&quot;:&quot;https://www.codeproject.com/KB/tips/ModelViewController/Figure4.gif&quot;,&quot;width&quot;:600}" data-trix-content-type="image"><img src="https://www.codeproject.com/KB/tips/ModelViewController/Figure4.gif" width="600" height="400"><figcaption class="attachment__caption"></figcaption></figure>&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:20:55 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444150</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>shamin_arissa65</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444334</link>
         <description><![CDATA[<div>The list repository contains a query object and a data mapper object that are specific to SharePoint. These are the ListItemFieldMapper and CAMLQueryBuilder classes. <mark>Both classes act as repository</mark></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282771748/85b1a5fbde0e2fd52dcad7b81346156b/2.png" />
         <pubDate>2018-04-17 07:21:38 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444334</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444440</link>
         <description><![CDATA[<div>&nbsp;Layered architectures consist of four standard layers: <strong>presentation, business, persistence, </strong>and <strong>database </strong><br><br>- <strong>presentation layer</strong> : Presentation of the web pages, UI forms and end user interracting API’s<br>- <strong>&nbsp;business layer</strong> : executing specific business rules associated with the request <br>-<strong>Persistence layer</strong> : contains all the classes responsible for doing the technical stuff -&gt;persisting the data in the database, like DAOs <br><br><strong>Feature</strong> :&nbsp; Partitions the concerns of the application into stacked groups&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282771124/e28f895638266554430637c29720d905/1.png" />
         <pubDate>2018-04-17 07:22:03 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444440</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author>shrfhsofia6</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444732</link>
         <description><![CDATA[<div>The <strong>most common architecture pattern.</strong>  Components within the layered architecture pattern are <strong>organized into horizontal layers,</strong> each layer performing a specific role within the application.<br><br>Most layered architectures consist of four standard layers:  <br>1) Presentation<br>2) Business<br>3) Persistence<br>4) Database <br><br> <mark>Each layer of the layered architecture pattern has a specific role and responsibility</mark> within the application.<br><br>Layered architecture is one of more  powerful features of the layered architecture pattern which is a way to <strong>provide for </strong><strong><em>separation of concerns</em></strong><strong>, encapsulation and decoupling, by grouping code units by their functional role </strong>within the application. </div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773846/761b4743b559d60946ac0de26fb620cf/layered__1_.png" />
         <pubDate>2018-04-17 07:23:13 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444732</guid>
      </item>
      <item>
         <title>The Force</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444980</link>
         <description><![CDATA[<div>Same data model can be display in multiple view using a controller.</div>]]></description>
         <enclosure url="http://slideplayer.com/4475963/14/images/57/Example+of+Model-View+Controller.jpg" />
         <pubDate>2018-04-17 07:24:07 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252444980</guid>
      </item>
      <item>
         <title>G.R.I.T.</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445177</link>
         <description><![CDATA[<div><strong>Layered architecture is an architecture</strong> in which data moves from one defined level of processing to another.&nbsp; Components within the layered architecture pattern are organized into horizontal layers, each layer performing a specific role within the application. It have 4 types of layer which are presentation, business, presistence and database.</div>]]></description>
         <enclosure url="https://herbertograca.com/2017/08/03/layered-architecture/" />
         <pubDate>2018-04-17 07:24:47 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445177</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445399</link>
         <description><![CDATA[<div>i) The repository mediates between the data source layer and the business layers of the application. <br>ii) Repository queries the data source for the data, maps the data from the data sources to a business entity. <br>iii) Repository persists changes in the business entity to the data source<br>iv) A repository separates the business logic from the interactions with the underlying data source or Web service</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282781958/fcabc34d8a28049ba8b8e9465dc4a163/rinvex_repository_diagram.png" />
         <pubDate>2018-04-17 07:25:29 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445399</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445498</link>
         <description><![CDATA[<div>&nbsp;<br>Layered architecture is an architecture where a data moves from level of processing to another level of processing <br>A layer provides services to the layer above it so the lowest-level layers represent core services that are likely to be used throughout the system.<br><br><strong>Advantage:&nbsp;</strong>&nbsp;</div><div>Allows replacement of entire layers so long as the interface is maintained. Redundant facilities (e.g., authentication) can be provided in each layer to increase the dependability of the system.&nbsp;<br><strong>Disadvantage:&nbsp;<br></strong>&nbsp;Providing a clean separation between layers is often difficult and a high-level layer may have to interact directly with lower-level layers rather than through the layer immediately below it. Performance can be a problem because of multiple levels of interpretation of a service request as it is processed at each layer.&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/00b07a1c4d2c2fd613c9854c9a1b6105/layered.png" />
         <pubDate>2018-04-17 07:25:54 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445498</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445560</link>
         <description><![CDATA[<div>&nbsp;Used when there are multiple ways to view and interact with data. Also used when the future requirements for interaction and presentation of data are unknown.<br><strong>Model–view–controller</strong> (<strong>MVC</strong>) is used for developing user interfaces.&nbsp;<br>It divides an application into three interconnected parts.</div><div><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/9a22b1481094508eb5644eccf4e7768a/Model_View_Controller.jpg" />
         <pubDate>2018-04-17 07:26:11 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445560</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>liew_chongmeng</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445908</link>
         <description><![CDATA[<div> In image processing, rendering is a jargon word that has come to mean "the collection of operations necessary to project a view of an object or a scene onto a view surface". The best way to break down the overall rendering process is to consider each object as a different coordinate space, in which independent operations can be carried out simultaneously [Watt93]. The input to a polygonal renderer is a list of polygons and the output is a colour for each pixel on the screen. To build up, for instance, a 3D scene, four general tasks are to be performed per object (Figure). </div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/279769890/023deea6b441863edc5f2d6ef9df16e1/pipe_and_filter.jpg" />
         <pubDate>2018-04-17 07:27:35 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445908</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445971</link>
         <description><![CDATA[<div>Some of the components included in the diagram are <mark>documents, database table, files, executables and all physical elements with a location. <br></mark><br>One example would be a component diagram for an ATM system; the components shown below are mostly physical elements, interacting with each other or a database table.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775327/f24d8c822206a810d58f7ac57aff5a0b/Capture.png" />
         <pubDate>2018-04-17 07:27:49 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252445971</guid>
      </item>
      <item>
         <title>G.R.I.T.</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446017</link>
         <description><![CDATA[<div>The component diagram's main purpose is to show the structural relationships between the components of a system.&nbsp; It have 4 types which are component, interface, dependencies and port.</div>]]></description>
         <enclosure url="http://docwiki.embarcadero.com/images/RADStudio/Tokyo/e/3/3c/ComponentDiagram.jpg" />
         <pubDate>2018-04-17 07:28:00 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446017</guid>
      </item>
      <item>
         <title>ADAMANTITE</title>
         <author>logesrao97</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446148</link>
         <description><![CDATA[<div>Pipe and filter is a very simple and powerful architecture that consist of several filters that filter data before it passes it via pipe to other components. All the filters work simultaneously.<br><br><strong><mark>Advantages of Pipe &amp; Filter</mark></strong><mark><br></mark>- <strong><em>Reusability<br>  </em></strong>Filters can be recombined<br>- <strong><em>Extensibility</em></strong><br>  It is possible to add new filters.<br>  It is also possible to substitute<br>  old filters with new one.<br>- <strong><em>Independence</em></strong><br>  Independent verification of each<br>  filter<br>- <strong><em>Performance</em></strong><br>  Enables concurrent execution<br>  of filters.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/238623821/ac44000fe3aac46079ca927a5b9f152d/Data_Flow_Architecture_I__Pipe_and_Filter_Architectures.jpg" />
         <pubDate>2018-04-17 07:28:34 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446148</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446497</link>
         <description><![CDATA[<div>Pipe and Filter consists of any number of components (filters) that transform or filter data, before passing it on via connectors (pipes) to other components. The filters are all working <em>at the same time</em>.</div><div><br></div><div>One special feature that makes us think this pattern is Pipe and Filter because it has message queue as pipe and it also has filters.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775707/a720c0e1445f40d0a62e26924400d240/pipes_and_filters_message_queues.png" />
         <pubDate>2018-04-17 07:29:42 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446497</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446622</link>
         <description><![CDATA[<div>Pipe and Filter is a very simple, yet powerful architecture, that is also very robust. It consists of any number of components (filters) that transform or filter data, before passing it on via connectors (pipes) to other components.<br><br><strong><mark>Use the </mark></strong><strong><em><mark>Pipes and Filters</mark></em></strong><strong><mark> architectural style to divide a larger processing task into a sequence of smaller, independent processing steps (Filters) that are connected by channels (Pipes).</mark></strong>&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/9273ad2d6b174e7e0ea695272d2635e2/Pipe_and_Filter.png" />
         <pubDate>2018-04-17 07:30:11 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446622</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446654</link>
         <description><![CDATA[<div>A <strong>repository architecture</strong> is a system that would provide both a console and graphical user interface to update both the structure and data set of any particular database and allow several interfacing components to share the same data.<br><br><strong><mark>&nbsp;Shared data is held in a central database or repository and may be accessed by all sub-systems&nbsp;<br></mark></strong><br></div><div><strong><mark>Each sub-system maintains its own database and passes data explicitly to other sub-systems.&nbsp;</mark></strong></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/2d37e429bbfea318bdf445b1de7c1fcb/repository.jpg" />
         <pubDate>2018-04-17 07:30:17 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446654</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446802</link>
         <description><![CDATA[<div>Consist of client and server.<br>Client request while server provide services.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/276536043/a161ebb7ee761a14192cc628d6e7bb2d/client_server.jpg" />
         <pubDate>2018-04-17 07:30:46 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446802</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>shamin_arissa65</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446936</link>
         <description><![CDATA[<div>There are<mark> 5 layers</mark> in the system which are<mark> presentation layer, business layer, services layer, persistence layer and database layer</mark>. Each layer is related to each other</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282771748/ddd9b564f0e20ac3b9560bd1acb31950/3.png" />
         <pubDate>2018-04-17 07:31:19 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252446936</guid>
      </item>
      <item>
         <title>The Force</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447422</link>
         <description><![CDATA[<div>Categorized into specific layers. Each layer are related functionality associated with each layer.</div>]]></description>
         <enclosure url="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTtqOz7cw2ZREpM6pS3G_J4KnVpnXUScKX6uYftV8Yjnu3nDCX7" />
         <pubDate>2018-04-17 07:33:23 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447422</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author>safwankamson</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447720</link>
         <description><![CDATA[<div><strong>Components</strong></div><ul><li><strong>Server&nbsp;</strong></li><li>listens for requests from client components.&nbsp;</li><li>When a request is received, the server processes the request, and then sends a response back to the client.</li><li>Servers may be further classified as stateless or stateful.&nbsp;</li><li>managing disk drives (file servers), printers (print servers), or network traffic (network servers).</li><li><strong>Clients</strong></li><li>PCs or workstations on which users run applications.</li><li>make composite requests that consist of multiple atomic requests.&nbsp;</li><li>This enables a more conversational or transactional interactions between client and server.&nbsp;</li><li>server keeps a record of the requests from each current client called a session.</li></ul><div><br><br></div><div><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:584,&quot;url&quot;:&quot;https://lh5.googleusercontent.com/tBkhQ1RuT4UqAf135JXUDfRMlrjLYp6Gocvw8vLTWEq8t9fERd-Q3f3dMOwAjnljWBL2dNIGT7ZO2psc2AXIq17pqlxTlMBVRQyhK2QGVxjtOHcEicQRo4ZyEyPdbrxlOhQQyMJh&quot;,&quot;width&quot;:519}" data-trix-content-type="image"><img src="https://lh5.googleusercontent.com/tBkhQ1RuT4UqAf135JXUDfRMlrjLYp6Gocvw8vLTWEq8t9fERd-Q3f3dMOwAjnljWBL2dNIGT7ZO2psc2AXIq17pqlxTlMBVRQyhK2QGVxjtOHcEicQRo4ZyEyPdbrxlOhQQyMJh" width="519" height="584"><figcaption class="attachment__caption"></figcaption></figure>Sequence Diagram</div><div><br></div><div><strong>PROS</strong></div><div><strong><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:802,&quot;url&quot;:&quot;https://lh4.googleusercontent.com/0EaaRgOlyiRjEUHWjRyQPZTgU9QmvzokRK9RGJz-BX7ZIACMU_g1cEVFPitGr4FRElrTntlq_ib_iWG5cd0EopBFVwjij8MUJ0-g4YH06dSoi-bXu3EYk86ahGApFozNELbI9LBi&quot;,&quot;width&quot;:850}" data-trix-content-type="image"><img src="https://lh4.googleusercontent.com/0EaaRgOlyiRjEUHWjRyQPZTgU9QmvzokRK9RGJz-BX7ZIACMU_g1cEVFPitGr4FRElrTntlq_ib_iWG5cd0EopBFVwjij8MUJ0-g4YH06dSoi-bXu3EYk86ahGApFozNELbI9LBi" width="850" height="802"><figcaption class="attachment__caption"></figcaption></figure></strong></div><div><strong>CONS</strong></div><div><strong><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:468,&quot;url&quot;:&quot;https://lh6.googleusercontent.com/d-vTdCNMTE_5GwhXK7HPyle2sXaMEkeptHIGs8yDalUFuVSY1-WeT-JzRGU56NajpIBnSbF3ng08JxAkD4D2f2SUbbDKgVfS3VhWxhyZjNNThhavlSSWM8xm6Wu0Z1ENoRc7FrN9&quot;,&quot;width&quot;:650}" data-trix-content-type="image"><img src="https://lh6.googleusercontent.com/d-vTdCNMTE_5GwhXK7HPyle2sXaMEkeptHIGs8yDalUFuVSY1-WeT-JzRGU56NajpIBnSbF3ng08JxAkD4D2f2SUbbDKgVfS3VhWxhyZjNNThhavlSSWM8xm6Wu0Z1ENoRc7FrN9" width="650" height="468"><figcaption class="attachment__caption"></figcaption></figure></strong></div><div><br><br><br><br><br><br></div>]]></description>
         <enclosure url="http://slideplayer.com/9723792/31/images/6/A+client%E2%80%93server+architecture+for+a+film+library.jpg" />
         <pubDate>2018-04-17 07:34:41 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447720</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447855</link>
         <description><![CDATA[<div>&nbsp;The repository pattern is an <em>abstraction</em>. It’s purpose is to reduce complexity and make the rest of the code persistent ignorant.</div><div><br></div><div>One special feature that makes us think this pattern is repository because it has the Repository which is responsible to provide and implement these query methods.&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282775707/bf634d2f8eddfd05fda729b95575952c/r.png" />
         <pubDate>2018-04-17 07:35:20 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447855</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447989</link>
         <description><![CDATA[<div>As what the name stated, Model View Controller (MVC) consists of Model(M), View(V) and Controller(C).<br>Model- contain the brain of the application. (Software logic and application data)<br>View- contain the interface to be display. (colour, layout, etc.)<br>Controller- handle communication between user and model. <br><br>Basically, user interact with <strong>controller </strong><em>(using interface produce by </em><strong><em>View</em></strong><em>)</em>, interaction is send to <strong>model</strong>, <strong>model</strong> process and return data back to <strong>controller,</strong> data then display via <strong>View.</strong></div><div><strong><br></strong>Main objective: <strong>To create seperation of concern</strong> <em>(To seperate user interface with software logic.)</em><br><br>Image below shows the process flows in MVC.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/276536043/14ff2aadc0b05d681c651e4b7ee989f5/ea7ce9208d35799f672f393ae892c910.jpg" />
         <pubDate>2018-04-17 07:35:53 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252447989</guid>
      </item>
      <item>
         <title>LANCER</title>
         <author>imans9715</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252448910</link>
         <description><![CDATA[<div>Component diagrams are used to:-<br>   - Visualize the organization and    <br>     relationships among   <br>      components in a system.<br><br>   - Make executable systems. <br><br> </div><div>Component diagrams can be used to −<br><br></div><ul><li>Model the components of a system.<br><br></li><li>Model the database schema.<br><br></li><li>Model the executables of an application.<br><br></li><li>Model the system's source code. <br><br></li></ul>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282773800/41d6116b64627060d0ee7eeb434665c8/component.png" />
         <pubDate>2018-04-17 07:39:24 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252448910</guid>
      </item>
      <item>
         <title>FATASTIC</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252448921</link>
         <description><![CDATA[<div>&nbsp;</div><div>Component diagrams are different in terms of nature and behavior. Component diagrams are used to model the physical aspects of a system.&nbsp;<br><br></div><div>Component diagrams are used to visualize the organization and relationships among components in a system. These diagrams are also used to make executable systems.&nbsp;<br><br>&nbsp;</div><div>The purpose of the component diagram can be summarized as −<br><br></div><ul><li>Visualize the components of a system.<br><br></li><li>Construct executables by using forward and reverse engineering.<br><br></li><li>Describe the organization and relationships of the components.&nbsp;</li></ul><div><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/282781958/6e180e6d431a32befd3796fcf41e7e5b/uml_component_diagram.jpg" />
         <pubDate>2018-04-17 07:39:26 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252448921</guid>
      </item>
      <item>
         <title>The Force</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449093</link>
         <description><![CDATA[<div> </div><ul><li><strong>Centralized data access</strong>. Because data is stored only on the server, access and updates to the data are far easier to administer than in other architectural styles. </li></ul>]]></description>
         <enclosure url="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c9/Client-server-model.svg/1200px-Client-server-model.svg.png" />
         <pubDate>2018-04-17 07:39:58 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449093</guid>
      </item>
      <item>
         <title>The Force</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449284</link>
         <description><![CDATA[<div>All data can be managed consistently. All data in a system is managed in a central repository that is accessible to system components.</div>]]></description>
         <enclosure url="https://www.cs.colorado.edu/~kena/classes/5828/s07/lectures/18/sharedRepository.png" />
         <pubDate>2018-04-17 07:40:45 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449284</guid>
      </item>
      <item>
         <title>VOID</title>
         <author>liew_chongmeng</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449461</link>
         <description><![CDATA[<div>It is a  MVC based user interface component diagram of  Algorithmic Trading System </div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/279769890/1615a1486d0557339b76fa0594c025f2/User_interfaces.png" />
         <pubDate>2018-04-17 07:41:34 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252449461</guid>
      </item>
      <item>
         <title>Magikarp</title>
         <author>nazatulasyikin96</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252450003</link>
         <description><![CDATA[<div>-The pattern is envisaged as a stream of data f;owing througn a set of processing stages<br>-Data can be processed sequentially or in parallel, based on the context<br>-pipes and Filters can be combined in different ways to create a family of systems. <figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:152,&quot;url&quot;:&quot;https://lh4.googleusercontent.com/Y9OZ_eM0czTgCDyd4djuHHTgOyBCpnLPzi5co0YPIukRzW1xEffpfVxL8pJBRABi2L0NiwGY9U6IxVNlc6HgNOCG1Z73pdp0-w=w944-h947&quot;,&quot;width&quot;:796}" data-trix-content-type="image"><img src="https://lh4.googleusercontent.com/Y9OZ_eM0czTgCDyd4djuHHTgOyBCpnLPzi5co0YPIukRzW1xEffpfVxL8pJBRABi2L0NiwGY9U6IxVNlc6HgNOCG1Z73pdp0-w=w944-h947" width="796" height="152"><figcaption class="attachment__caption"></figcaption></figure> &nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:43:37 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252450003</guid>
      </item>
      <item>
         <title>SURVIVOR</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252450941</link>
         <description><![CDATA[<div>&nbsp;</div><div><strong>MODEL-VIEW-CONTROLLER(MVC)</strong></div><ul><li>Separates presentation and interaction from the system data.</li><li>Structured to three logical components :</li><li><strong>Models</strong> for handling data and business logic and it’s only represent the data <br>and does nothing else. Does <strong>NOT</strong> depend on the controller or view&nbsp;</li><li><strong>Controllers</strong> for handling the user interface and application</li><li><strong>Views</strong> for handling graphical user interface objects and presentation<br><br></li></ul><div><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:159,&quot;url&quot;:&quot;https://lh5.googleusercontent.com/xBSYrC9szgZZ0UjX9cuPKF7DxnadaDRxD9Rem00M_5G8youXB6yHzxpHP82eIIyP3b1tDPGKmNjKK_XfEW0gDN4ZpwFWdFJ9lAQk_p2cuWYBqSmtFE2Qihzf4p8uw0WNTQ&quot;,&quot;width&quot;:318}" data-trix-content-type="image"><img src="https://lh5.googleusercontent.com/xBSYrC9szgZZ0UjX9cuPKF7DxnadaDRxD9Rem00M_5G8youXB6yHzxpHP82eIIyP3b1tDPGKmNjKK_XfEW0gDN4ZpwFWdFJ9lAQk_p2cuWYBqSmtFE2Qihzf4p8uw0WNTQ" width="318" height="159"><figcaption class="attachment__caption"></figcaption></figure></div><div><em>Figure 1: MVC class structure</em>&nbsp;<br><br></div><div>By separating the software applications to three components is a good idea where it helps to:&nbsp;<br><br></div><ol><li><strong><em>Improved scalability</em></strong> (the ability for an application to grow)<br>For example, if your application begins experiencing performance issues because database access is slow, you can upgrade the hardware running the database without other components being affected.</li><li><strong><em>Ease of maintenance</em></strong>, as the components have a low dependency on each other, making changes to one (to fix bugs or change functionality) does not affect another.</li><li><strong><em>Reusability </em></strong>where a model may be reused by multiple views.<br><br></li></ol><div><strong>Disadvantages of MVC</strong><br>1. The <strong>complexity</strong> is high to develop the applications using this pattern.<br>2. Not right suitable for small applications which has <strong>adverse effect</strong> in the application’s performance and design.<br>3. In terms of servlet and JSP, both often contains business logic and presentation tier.<br>4. The isolated development process by UI authors, business logic authors and controller authors may lead to <strong>delay</strong> in their respective modules development.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:47:32 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252450941</guid>
      </item>
      <item>
         <title>The Force</title>
         <author></author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252451806</link>
         <description><![CDATA[<div>Consists of any number of components (filters) that transform or filter data, before passing it on via connectors (pipes) to other components.</div>]]></description>
         <enclosure url="https://i-msdn.sec.s-msft.com/dynimg/IC135958.gif" />
         <pubDate>2018-04-17 07:51:03 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252451806</guid>
      </item>
      <item>
         <title>MAGIKARP</title>
         <author>syamimlfc97</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252453451</link>
         <description><![CDATA[<div><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:150,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-components-symbols.svg&quot;,&quot;width&quot;:91}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-components-symbols.svg" width="91" height="150"><figcaption class="attachment__caption"></figcaption></figure> UML 1.0, a component is modeled as a rectangular block with two smaller rectangles protruding from the side. In UML 2.0, a component is modeled as a rectangular block with a small image of the old component diagram shape.</div><div><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:150,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-node-symbol.svg&quot;,&quot;width&quot;:150}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-node-symbol.svg" width="150" height="150"><figcaption class="attachment__caption"></figcaption></figure>Represents hardware or software objects, which are of a higher level than components.<br><br><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:150,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Class/uml-interface-symbols.svg&quot;,&quot;width&quot;:275}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Class/uml-interface-symbols.svg" width="275" height="150"><figcaption class="attachment__caption"></figcaption></figure>Shows input or materials that a component either receives or provides.&nbsp;<br><br><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:116,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-port-symbol.svg&quot;,&quot;width&quot;:300}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-port-symbol.svg" width="300" height="116"><figcaption class="attachment__caption"></figcaption></figure><br>Specifies a separate interaction point between the component and the environment.&nbsp;<br><br><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:150,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Use-Case/uml-package-symbol.svg&quot;,&quot;width&quot;:228}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Use-Case/uml-package-symbol.svg" width="228" height="150"><figcaption class="attachment__caption"></figcaption></figure>Groups together multiple elements of the system and is represented by file folders in Lucidchart<br><br> <figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:150,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-notes-symbol.svg&quot;,&quot;width&quot;:150}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-notes-symbol.svg" width="150" height="150"><figcaption class="attachment__caption"></figcaption></figure>Allows developers to affix a meta-analysis to the component diagram.<br><br> <figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:35,&quot;url&quot;:&quot;https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-dependency-symbol.svg&quot;,&quot;width&quot;:300}" data-trix-content-type="image"><img src="https://d2slcw3kip6qmk.cloudfront.net/marketing/pages/chart/discovery/UML/UML-Component/uml-dependency-symbol.svg" width="300" height="35"><figcaption class="attachment__caption"></figcaption></figure>&nbsp; Shows that one part of your system depends on another.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-17 07:58:30 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252453451</guid>
      </item>
      <item>
         <title>The Force</title>
         <author>drazak97</author>
         <link>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252454412</link>
         <description><![CDATA[<div>The components that included in the diagram are Web Store, Accounting and Warehouses.<br><strong>WebStore</strong> subsystem contains three components related to online shopping - <strong>Search Engine</strong>, <strong>Shopping Cart</strong>, and <strong>Authentication</strong>.<br><strong>Accounting</strong> subsystem provides two interfaces - <strong>Manage Orders</strong> and <strong>Manage Customers</strong>.<br><strong>Warehouses</strong> subsystem provides two interfaces <strong>Search Inventory</strong> and <strong>Manage Inventory</strong></div>]]></description>
         <enclosure url="https://www.uml-diagrams.org/examples/component-example-retail-website.png" />
         <pubDate>2018-04-17 08:03:17 UTC</pubDate>
         <guid>https://padlet.com/shahliza_abd_halim/vobqrvvwjphp/wish/252454412</guid>
      </item>
   </channel>
</rss>
