<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Lecture 11 by ElinE</title>
      <link>https://padlet.com/elin9730/gu3spuo5gkh9</link>
      <description>System development methodology</description>
      <language>en-us</language>
      <pubDate>2017-12-14 23:17:16 UTC</pubDate>
      <lastBuildDate>2026-03-16 11:19:52 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet-assets.s3.amazonaws.com/icons/Dartstarget.png</url>
      </image>
      <item>
         <title>Systems development methodology</title>
         <author>elin9730</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216356701</link>
         <description><![CDATA[<div>Discuss the advantage and disadvantage (ONE EACH) of applying systems methodology (e.g., waterfall) in a software development roject. <br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-14 23:18:40 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216356701</guid>
      </item>
      <item>
         <title>Nor&#39;ain Syahirah bt Norazman 2016655722</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216364003</link>
         <description><![CDATA[<div>one of advantages of applying system methodoligy (ex:waterfall) is because the methodology provide framework to the team, hence the planning of the project become much easier.<br><br>one of the disadvantages of applying system methodology, for example waterfall model. The drawback of this method is there is no possibility to produce any working software until it reaches the last stage of the cycle. The team may rush into completing the project for the sake of their client as the client are more interested with the end product rather than the processes involved.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-15 00:53:28 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216364003</guid>
      </item>
      <item>
         <title>MUHAMMAD ZAKWAN BIN ZAKARIA 2016655674</title>
         <author>zackmacho97</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216394925</link>
         <description><![CDATA[<div>In V model methodology<br><br><strong>Advantage</strong> of using&nbsp; V model is the development and progress of the project is very organized and systematic and works very well for smaller to medium sized of project. The ambiguities are identified earlier in the project as the testing starts from the beginning of the processes.<br><br><strong>Disadvantage </strong>of using this model is V model methodology is it is not very efficient and suitable for big, complex project and this model is not working if there is inconsistency of the requirement.<br><br>.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-15 07:52:21 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216394925</guid>
      </item>
      <item>
         <title>NOR ATIKAH ADRINA BINTI AHMAD TERIDI - 2016655644</title>
         <author>msAAdrina</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216402245</link>
         <description><![CDATA[<div><br>Spiral model is an example of applying the system methodology which normally used when users are unsure of their needs and requirements are complex.<br>The advantages of Spiral model are additional functionality can be added at a later date and it is<br>better to be apply for large and mission-critical projects.<br>The disadvantage of using Spiral model is analyses risks requires highly specific expertise and higher cost is needed.<br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-15 08:30:04 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216402245</guid>
      </item>
      <item>
         <title>NOR AMIRA BINTI ARIFFIN (2016655696)</title>
         <author>miraariff_ma</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216542979</link>
         <description><![CDATA[<div>1) The <strong>Spiral Model </strong>is a sophisticated model that focuses on early identification and reduction of project risks.</div><div>&nbsp;</div><div><strong>Advantages of Spiral Model:</strong></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The high amount of risk analysis hence, avoidance of possible risk is certainly reduced<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;This model is good for large size and critical projects<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;In the spiral model, additional functionality can be added at a later date<br><br></div><div><strong>Disadvantages of Spiral Model:</strong></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;It is certainly the costly model to use in terms of development<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The success of the entire project is dependent on the risk analysis phase thus, failure in this phase may damage entire project<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;It is not appropriate for low-risk projects<br><br></div><div>2) The <strong>waterfall model</strong> is one of the most traditional and commonly used software development methodologies for software development. <br><br><strong>Advantages of Waterfall Model:</strong></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Waterfall model is very simple and easy to understand and use a method that is why it is really beneficial for the beginner or novice developer<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;It is easy to manage, because of the rigidity of the model. Moreover, each phase has specific deliverables and individual review process<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;In this model phases are processed and completed are at once in a time thus it saves a significant amount of time<br><br></div><div><strong>Disadvantages of Waterfall Model:</strong></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;This model can only be used when very precise up-front requirements are available<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;This model is not applicable for maintenance type of projects<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The main drawback of this method is that once an application is in the testing stage, it is not possible to go back and edit something<br><br></div><div>&nbsp;3) <strong>Agile Software Development</strong> is an approach that is used to design a disciplined <a href="https://www.tatvasoft.com/software-outsourcing/software-outsourcing-development">software management process</a> which also allows some frequent alteration in the development project.<br><br></div><div><strong>Advantages of Agile Development Methodology:</strong></div><div>.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Agile methodology has an adaptive approach which is able to respond to the changing requirements of the clients<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Direct communication and constant feedback from customer representative leave no space for any guesswork in the system<br><br></div><div><strong>Disadvantages of Agile Development Methodology:</strong></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;This methodology focuses on working software rather than documentation, hence it may result in a lack of documentation<br>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The software development project can get off track if the customer is not very clear about the final outcome of his project<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-15 16:32:22 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216542979</guid>
      </item>
      <item>
         <title>Nur Maisarah Bt Muhamad Din (2016655702)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216668498</link>
         <description><![CDATA[<div>Agile model - Agile is a methodology that anticipates the need for flexibility and applies a level of pragmatism into the delivery of the finished product. Agile requires a cultural shift in many companies because it focuses on the clean delivery of individual pieces or parts of the software and not on the entire application.&nbsp;<br><br>Advantages of Agile model: Customer satisfaction by rapid, continuous delivery of useful software.<br>Disadvantages of Agile:<br>There is lack of emphasis on necessary designing and documentation.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-16 10:34:47 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216668498</guid>
      </item>
      <item>
         <title>MUHAMMAD ARIF BIN RUDI (2016655602)</title>
         <author>muhdarifrudi23</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216679070</link>
         <description><![CDATA[<div>The waterfall model.<br>Advantages</div><div><br></div><div>The advantages of the waterfall process are that it allows for departmentalization and managerial control. A schedule is typically set with deadlines for each stage of development. The product can proceed through the development process. This process leads to the project being delivered on time because each phase has been planned in detail.</div><div>&nbsp;</div><div>Disadvantages&nbsp;</div><div><br></div><div>The disadvantages of waterfall process is cannot be used where the software requirements are likey to change. It also have lots of risks and uncertainty. The working software is produced until very late in this life cycle. It not suitable for complex projects. The process also not real flexibility.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-16 13:12:10 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216679070</guid>
      </item>
      <item>
         <title>Nur Hasanah Binti Ahmad Azemi (201665736) </title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216694372</link>
         <description><![CDATA[<div><br>Example :&nbsp; V model<br><br>Advantages of V-model :<br>- Simple and easy to use as testing activities like planning, test designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model. It is also works well for small projects where the requirements are easily understood.<br><br><br>Disadvantage of V-model&nbsp; :<br>- Very rigid and least flexible. For example, if any changes happen in midway, then the test documents along with requirement documents has to be updated<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-16 16:37:44 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216694372</guid>
      </item>
      <item>
         <title>Amirah Liyana binti Amin Shukori (2016655632)</title>
         <author>mraliyana</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216728467</link>
         <description><![CDATA[<div><strong>Iterative model</strong><br><br></div><div><em>Advantages</em></div><div>In iterative model we can only create a high-level design of the application before we actually begin to build the product and then define the design solution for the entire product. Later on we can design and built a skeleton version of that, and then evolved the design based on what had been built. We can track the defects at early stages since we are building and improving the product step by step.&nbsp;<br><br></div><div><em>Disadvantages</em></div><div>Each of the phase of an iteration is rigid with no overlaps. Costly system architecture or design issues may arise because not all requirements are gathered up front for the entire lifecycle.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 05:53:58 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216728467</guid>
      </item>
      <item>
         <title>Nur Fateha binti A. Halim (2016655626)</title>
         <author>ohfateha</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216728915</link>
         <description><![CDATA[<div><strong>V-model<br></strong><br><em>Advantages of V-model</em></div><div>It is simple and easy to use. Testing activities, like planning, test designing happens well before coding. This saves a lot of time and has a higher chance of success over waterfall model. V-model can found defects at early stage, avoids the downward flow of the defects and works well for small projects where requirements are easily understood. It is also easy to keep track on the progress.<br><br></div><div><em>Disadvantages of V-model</em></div><div>It is very rigid and least flexible. Software is developed during the implementation phase, so no early prototypes of the software are produced. If any changes happen in midway, the test documents along with requirement documents has to be updated. It is not suitable for bigger and complex projects and the client can see only the final project, not intermediate modules<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 06:11:53 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216728915</guid>
      </item>
      <item>
         <title>Farahanani Jumat (2016655666</title>
         <author>farahananijumat</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216729195</link>
         <description><![CDATA[<div><strong>Agile Model<br><br>Advantage : </strong>This model produces good team cohesion and suitable for fixed or changing requirements.<br><br><strong>Disadvantages :</strong> This&nbsp;model is not suitable for handling complex dependencies and it has more risk of sustainability, maintainability and extensibility.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 06:17:29 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216729195</guid>
      </item>
      <item>
         <title>Fauziatul Naeilah Binti Hilmi (2016655612)</title>
         <author>fauziatulnaeilah</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216733679</link>
         <description><![CDATA[<div><strong>Waterfall Model</strong><br><br></div><ul><li>One<strong> advantage of waterfall model</strong> is in this model, phases are processed and completed one at a time. Moreover, the phases do not overlap.</li></ul><div>&nbsp;</div><ul><li>One <strong>disadvantage of waterfall model </strong>is once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.</li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 07:37:44 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216733679</guid>
      </item>
      <item>
         <title>Muhammad Nurhaziq bin Mohd Fauzi (2016655748)</title>
         <author>hazcom97</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216735070</link>
         <description><![CDATA[<div><strong><em>Waterfall Model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Easy to explain to users<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Very difficult to go back to any stage after it finished.<br><br></div><div>&nbsp;<br><br></div><div><strong><em>V- Shaped model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Very inflexible, like the waterfall.</div><div>&nbsp;<br><br></div><div><strong><em>Prototyping Model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Reduced time and costs, but this can be a disadvantage if the developer loses time in developing the prototypes.<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Excessive development time of the prototype.<br><br></div><div><strong><em>Spiral Model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Estimates (i.e. budget, schedule, etc.) become more realistic as work progressed because important issues are discovered earlier.<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Needs special skills to evaluate the risks and assumptions.<br><br></div><div>&nbsp;<br><br></div><div><strong><em>Iterative and Incremental Model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; More focused on customer value than the linear approaches.<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Integration between iteration can be an issue if this is not considered during the development.<br><br></div><div><em>&nbsp;<br></em><br></div><div><strong><em>Agile Model</em></strong><em><br></em><br></div><div>Advantages&nbsp;<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Face to face communication and continuous inputs from customer representative leaves no space for guesswork.<br><br></div><div>Disadvantages<br><br></div><div>-&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The ability and collaboration of the customer to express user needs.<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 08:22:49 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216735070</guid>
      </item>
      <item>
         <title>Maizura binti Mustafa</title>
         <author>myzuraaa</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216737790</link>
         <description><![CDATA[<div>(2016655758)<br><strong>Agile Development Model</strong><br><br></div><div>Agile development model is also a type of Incremental model. Software is developed in incremental, rapid cycles. This results in small incremental releases with each release building on previous functionality. Each release is thoroughly tested to ensure software quality is maintained.<br><br></div><div><strong>Advantages</strong>: Face-to-face conversation is the form of communication and it is continuous attention to technical excellence and good design.<br><br></div><div><strong>Disadvantages:</strong> There is lack of emphasis on necessary designing and documentation. The project can easily get taken off track if the customer representative is not clear what final outcome that they want.<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 09:26:33 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216737790</guid>
      </item>
      <item>
         <title>FATIN AMIRAH BINTI CHE MAT(2016655726)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216753916</link>
         <description><![CDATA[<div><strong>V-MODEL<br></strong><br></div><div><strong>Advantages of V Model</strong><br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;If project is small and easy to understand, V Model is the best approach as its easy and simple to use.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Many testing activities are performed in the beginning like planning and design which saves lots of testing time.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Most of the defects and bugs are found in the beginning of the project development. So less chances of defect or bug to be occurred at final testing phase.</div><div>&nbsp;<br><br></div><div><strong>Disadvantages of V Model</strong><br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Guessing the error in the beginning of the project could take more time.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Less flexibility.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Any changes done in the middle of the development which is unplanned could make difficult to make the changes at all the places like test document and requirements.</div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-17 13:19:37 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216753916</guid>
      </item>
      <item>
         <title>SITI NUR SHAKIRAH BINTI SUHAIMI (2016655614)</title>
         <author>nur_shakirah97</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216940752</link>
         <description><![CDATA[<div><br><strong>Spiral Model<br></strong><br></div><div>Advantage : Risk monitoring is one of the core parts which makes it pretty attractive, especially when you manage large and expensive projects. Moreover, such approach makes your project more transparent because, by design, each spiral must be reviewed and analyzed.</div><div>&nbsp;</div><div>Disadvantage : Rules and protocols should be followed properly to effectively implement this model. Doing so, through-out the span of project is tough.<br>&nbsp;<br><br><strong>&nbsp;Waterfall Model&nbsp;<br></strong><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Advantage : It is easy to manage, because of the rigidity of the model. Moreover, each phase has specific deliverables and individual review process<br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Disadvantage : The main drawback of this method is that once an application is in the testing stage, it is not possible to go back and edit something<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 13:46:17 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216940752</guid>
      </item>
      <item>
         <title>Nur Hafiza Binti Azman (2016655622</title>
         <author>hafiznurhafiza97</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216956406</link>
         <description><![CDATA[<div>Waterfall Model&nbsp;<br><br>Advantages of waterfall model:<br><br>*This model is simple and easy to understand and use.<br>*It is easy to manage due to the rigidity of the model *Each phase has specific deliverables and a review process.<br>*In this model phases are processed and completed one at a time. Phases do not overlap.<br>*Waterfall model works well for smaller projects where requirements are very well understood.<br><br>Disadvantages of waterfall model:<br><br>*Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.<br>*No working software is produced until late during the life cycle.<br>*High amounts of risk and uncertainty.<br>*Not a good model for complex and object-oriented projects.<br>*Poor model for long and ongoing projects.<br>*Not suitable for the projects where requirements are at a moderate to high risk of changing.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 14:22:52 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216956406</guid>
      </item>
      <item>
         <title>NUR SYAFIQAH BINTI SAYUTI</title>
         <author>syfqhsayuti_</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216959586</link>
         <description><![CDATA[<div>(2016655646)<br>1)&nbsp; &nbsp; &nbsp; Waterfall model</div><div>Advantage: Allows for easy testing and analysis.</div><div>Disadvantage: No option to know possible outcome of project.</div><div>2)&nbsp; &nbsp; &nbsp; Prototype</div><div>Advantage: Gives clear idea about the functional process of the software.</div><div>Disadvantages: Chances of extension in management cost.</div><div>3)&nbsp; &nbsp; &nbsp; Agile methodology</div><div>Advantage: Adaptive approach that responds to changes favourably.</div><div>Disadvantages: Focuses on working with software and lack of documentation efficiency.</div><div>4)&nbsp; &nbsp; &nbsp; Spiral model</div><div>Advantage: Allows for additional functionality later.</div><div>Disadvantages: Failure in risk analysis phase may damage the whole project.<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 14:30:21 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216959586</guid>
      </item>
      <item>
         <title>NUR SYAHIRAH BT AZEMI (2016655656)</title>
         <author>syahirahazemie</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216961003</link>
         <description><![CDATA[<div><strong>WATERFALL MODEL</strong><br><br></div><div>ADVANTAGES :&nbsp; Easy to understand and functional.<br><br></div><div>DISADVANTAGES: Not applicable for maintenance projects.<br><br></div><div><strong>AGILE METHODOLOGY</strong><br><br></div><div>ADVANTAGES :Adaptive approach that responds to changes favourably.<br><br></div><div>DISADVANTAGES: Focuses on working with software and lacks documentation efficiency.<br><br></div><div><strong>SPIRAL MODEL</strong><br><br></div><div>ADVANTAGES :&nbsp; Risk factors are considerably reduced<br><br></div><div>DISADVANTAGES: Failure in risk analysis phase may damage the whole project.<br><br></div><div><strong>V-MODEL</strong><br><br></div><div>ADVANTAGES: Proactive defect tracking – that is defects are found at early stage.<br><br></div><div>DISADVANTAGES: Very rigid and least flexible.<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 14:33:41 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216961003</guid>
      </item>
      <item>
         <title>Waterfall Model</title>
         <author>hasinakamal97</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216963666</link>
         <description><![CDATA[<div>&nbsp;Advantages<br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 14:39:40 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216963666</guid>
      </item>
      <item>
         <title>NURUL HASINA KAMAL BASHAH (2016655636)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216970676</link>
         <description><![CDATA[<div>WATERFALL MODEL<br><strong>Advantages of waterfall model</strong></div><ul><li>Waterfall model works well for smaller projects where requirements are very well understood.</li></ul><div><br></div><div><strong>&nbsp;Disadvantages of waterfall model:</strong></div><ul><li>Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.</li></ul><div><br>AGILE MODEL</div><div>A<strong>dvantages of Agile model:</strong></div><ul><li>People and interactions are emphasized rather than process and tools. Customers, developers and testers constantly interact with each other.</li><li>Working software is delivered frequently (weeks rather than months).</li></ul><div><br><strong>Disadvantages of Agile model:<br></strong><br></div><ul><li>In case of some software deliverables, especially the large ones, it is difficult to assess the effort required at the beginning of the software development life cycle.</li></ul><div><br>RAD MODEL<br><strong>Advantages of waterfall model:<br></strong><br></div><ul><li>Integration from very beginning solves a lot of integration issues</li></ul><div><strong><br>Disadvantages of waterfall model:</strong></div><ul><li>inapplicable to cheaper projects as cost of modeling and automated code generation is very high.</li></ul><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-18 14:59:31 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/216970676</guid>
      </item>
      <item>
         <title>NUR NAJWA BT ABD.MUNI&#39;M(2016655742)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217139544</link>
         <description><![CDATA[<div><br></div><div>&nbsp;</div><div><strong>&nbsp;V model: </strong>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>&nbsp;Advantage<br>-Testing activities like planning, test designing happens well before coding. This saves a lot time. Hence higher chance of success over the waterfall model</div><div>&nbsp;<br>Disadvantage<br>-Very rigid and least flexible</div><div>-if any changes happen in midway, then the test documents has to be&nbsp;</div><div>&nbsp; updated.</div><div>&nbsp;</div><div><br></div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><div>&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-19 04:16:26 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217139544</guid>
      </item>
      <item>
         <title>NUR RAIHAN BINTI SABRI(2016655604)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217141162</link>
         <description><![CDATA[<div>Waterfall Model<br><br></div><div>Advantages<br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Waterfall model works well for smaller projects where requirements are very well understood.<br><br></div><div>Disadvantages<br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Poor model for long and ongoing projects.</div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-19 04:45:23 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217141162</guid>
      </item>
      <item>
         <title>NUR AZIMAH BINTI ZOLKEFLY (2016655654)</title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217142503</link>
         <description><![CDATA[<div>Agile Development Methodology<br><br>Advantages :<br><br>1) Agile methodology has an adaptive approach which is able to respond to the changing requirements of the clients<br><br>Disadvantages :<br><br>1) The software development project can get off track if the customer is not very clear about the final outcome of his project<br><br>V-model<br><br>Advantages:&nbsp;<br><br>1) V-model can found defects at early stage, avoids the downward flow of the defects and works well for small projects where requirements are easily understood. It is also easy to keep track on the progress.<br><br>Disadvantages:<br><br>1) Software is developed during the implementation phase, so no early prototypes of the software are produced. If any changes happen in midway, the test documents along with requirement documents has to be updated. It is not suitable for bigger and complex projects and the client can see only the final project, not intermediate modules</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-19 05:11:49 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217142503</guid>
      </item>
      <item>
         <title>Clana Anak Ritiw (2016655618)</title>
         <author>clana5479</author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217396179</link>
         <description><![CDATA[<div><strong>Waterfall Model</strong><br>Advantages of waterfall model:<br>•	This model is simple and easy to understand and use.<br>•	It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.<br>•	In this model phases are processed and completed one at a time. Phases do not overlap.<br>•	Waterfall model works well for smaller projects where requirements are very well understood.<br> <br>Disadvantages of waterfall model:<br>•	Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.<br>•	No working software is produced until late during the life cycle.<br>•	High amounts of risk and uncertainty.<br>•	Not a good model for complex and object-oriented projects.<br>•	Poor model for long and ongoing projects.<br>•	Not suitable for the projects where requirements are at a moderate to high risk of changing.<br><br><strong>V-Model</strong><br>Advantages of V-model:<br>•	Simple and easy to use.<br>•	Testing activities like planning, test designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model.<br>•	Proactive defect tracking – that is defects are found at early stage.<br>•	Avoids the downward flow of the defects.<br>•	Works well for small projects where requirements are easily understood.<br><br>Disadvantages of V-model:<br>•	Very rigid and least flexible.<br>•	Software is developed during the implementation phase, so no early prototypes of the software are produced.<br>•	If any changes happen in midway, then the test documents along with requirement documents has to be updated.<br><br><strong>Prototyping Model</strong><br>Advantages of Prototype model:<br>•	Users are actively involved in the development<br>•	Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.<br>•	Errors can be detected much earlier.<br>•	Quicker user feedback is available leading to better solutions.<br>•	Missing functionality can be identified easily<br>•	Confusing or difficult functions can be identified<br>Requirements validation, Quick implementation of, incomplete, but<br>functional, application.<br><br>Disadvantages of Prototype model:<br>•	Leads to implementing and then repairing way of building systems.<br>•	Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.<br>•	Incomplete application may cause application not to be used as the<br>full system was designed<br>Incomplete or inadequate problem analysis.<br>Spiral Model<br>Advantages of Spiral model:<br>•	High amount of risk analysis hence, avoidance of Risk is enhanced.<br>•	Good for large and mission-critical projects.<br>•	Strong approval and documentation control.<br>•	Additional Functionality can be added at a later date.<br>•	Software is produced early in the software life cycle.<br><br>Disadvantages of Spiral model:<br>•	Can be a costly model to use.<br>•	Risk analysis requires highly specific expertise.<br>•	Project’s success is highly dependent on the risk analysis phase.<br>•	Doesn’t work well for smaller projects.<br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-19 23:39:58 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217396179</guid>
      </item>
      <item>
         <title>MUHAMMAD NUR FITRI BIN RUSLI (2016655684) </title>
         <author></author>
         <link>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217396939</link>
         <description><![CDATA[<div>Waterfall Model<br><br></div><div>ADVANTAGES: in this model, phases are processed and completed one at a time. Moreover, the phases do not overlap.</div><div>&nbsp;</div><div>DISADVANTAGES: once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage</div><div>&nbsp;<br><br></div><div>V-Model<br><br></div><div>ADVANTAGES: Proactive defect tracking – that is defects are found at early stage.<br><br></div><div>DISADVANTAGES: Very rigid and least flexible.</div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-12-19 23:51:04 UTC</pubDate>
         <guid>https://padlet.com/elin9730/gu3spuo5gkh9/wish/217396939</guid>
      </item>
   </channel>
</rss>
