<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Exercise 2 | Examples of SE Process Models | Section 2 by AZLIN BINTI NORDIN</title>
      <link>https://padlet.com/azlinnordin/processModel2</link>
      <description>Semester 1, 2021/2022</description>
      <language>en-us</language>
      <pubDate>2021-10-06 07:51:23 UTC</pubDate>
      <lastBuildDate>2023-02-26 11:18:40 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet.net/icons/png/1f5a5.png</url>
      </image>
      <item>
         <title>Group Name</title>
         <author>azlinnordin</author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1795710991</link>
         <description><![CDATA[<div>Group Members:<br>Include a figure of the chosen sofware process model * and briefly list the Strengths and Weaknesses of the process model.<br>Note: * add the reference to the figure</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-10-06 07:53:04 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1795710991</guid>
      </item>
      <item>
         <title>Drupal</title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1807699693</link>
         <description><![CDATA[<div>Group Members: Luqman Al Hakim, Farah Iwani, Alisya Marsya Hanania, Danial Aniq<br><br>Strengths;<br>1. The V-Model is used for small projects with well-defined needs<br>2. Simple and straightforward to comprehend and apply<br>3. It allows project managers to keep proper track of progress<br><br>Weaknesses;<br>1. High risk and uncertainty<br>2. Not suitable for object-oriented or large projects<br>3. It is hard to handle concurrent events<br><br>ref: https://www.geeksforgeeks.org/software-engineering-sdlc-v-model/</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1397880866/a4b47da2227c2cf283ad8687f184d36d/photo_2021_10_11_21_48_08.jpg" />
         <pubDate>2021-10-11 13:49:01 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1807699693</guid>
      </item>
      <item>
         <title>Alpine</title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1808033318</link>
         <description><![CDATA[<div><strong>Group members:</strong> Hafzlan Aidieq, Khairil Nazrel, Aniq Rahim<br><strong>Software process model: </strong>Prototyping model<br><br><strong>Strengths:</strong><br>1) There is room for improvement, new requirements can be easily met.<br>2) Functionalities that aren't present can simply be discovered.<br>3) Errors may be spotted sooner, saving time and money while also improving the quality of the product.<br><br><strong>Weaknesses:</strong><br>1) During customer evaluation, there may be too much diversity in needs.<br>2) Due to constantly changing customer requirements, there is a lack of documentation.<br>3) In a rush to produce prototypes, developers may come up with poor solutions.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1389073521/e098bb841c766f6bcd8f1e9c00926961/kum_prototyp3.jpg" />
         <pubDate>2021-10-11 15:32:19 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1808033318</guid>
      </item>
      <item>
         <title>Meteor                          </title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1808036649</link>
         <description><![CDATA[<div><strong>Group Members :</strong>&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; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>Muhammad Syafiq Farhan Bin Mohd Faridz (2011871), Adam Khuarizmi Bin Maszlan (2115347), Irdina Batrisyia Binti Nor Azli (2117188), Nazmy Asnawi Bin Hamidun Majid (2119837)&nbsp; <br><br><strong>Strengths of The Waterfall Model :</strong><br>- This model is simple to comprehend and apply<br>- Because of the model’s rigidity, it’s simple to manage as each steps has specified deliverables and a review procedure<br>- Each phase are processed and completed one at a time in this model so that phases do not overlap each other<br>- This Waterfall Model works well and effectively for smaller projects as the requirements are clearly defined and very well understood <br><br><strong>Weaknesses of the Waterfall Model : </strong><br>- It’s quite tough to go back and fix anything that wasn’t well-thought out in the idea stage once an application is in the testing stage<br>- There will be no functioning software produced until the end of the life cycle&nbsp;<br>- There is a lot of risks and uncertainties&nbsp;<br>- It is not a good model for complex and object-oriented projects and applications&nbsp;<br>- Poor model for long and outgoing projects&nbsp;<br>- Not suitable for projects with a moderate to high risk of change in requirements</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/934751452/37ca27ca427660e1b7b805bbd89564e4/photo_2021_10_11_15_20_04.jpg" />
         <pubDate>2021-10-11 15:33:25 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1808036649</guid>
      </item>
      <item>
         <title>React</title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1810547959</link>
         <description><![CDATA[<div><strong>Group Members :<br></strong>- Mohamad Aiman Akim Bin Adanan<br>- Raja Muhammad Hazwan Bin Raja Azman<br>- Nayli Syazreen binti Shaiful Hizam<br>- Irdina Izzati Binti Mohd Rasid <br><br><strong>Software process model :<br></strong>The Incremental Model<br><strong><br>Strengths :</strong><br>- Risks are manageable because the errors are identified easily <br>- There is a chance to change requirements, thus it is flexible <br>- Work is done quicker because planning early increments can be implemented <br><br><strong>Weaknesses :<br></strong>- Changing the requirements of the user will lead to high cost<br>- Need a very clear vision of the whole system<br>- Need a strategic and effective planning&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/683640384/c1e6b361d26a7e355a8911d7fa0081a4/WhatsApp_Image_2021_10_12_at_1_53_46_PM.jpeg" />
         <pubDate>2021-10-12 12:38:04 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1810547959</guid>
      </item>
      <item>
         <title>Preact</title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1810971107</link>
         <description><![CDATA[<div><strong>Group Members :</strong><br>-Ammar Haziq Bin Annas 2116043<br>-Afnan Iman bin Azman 1920311<br>-Tengku Zarul Fariman Bin Tengku Zahidi 2117365<br>-Muhammad Nadzmi Bin Mohd Ronizam 2028427<br><br><strong>Software process model :<br></strong>Rapid Application Development(RAD Model)<br>-RAD Model or Rapid Application Development model is a software development process based on prototyping without any specific planning and a condensed development process that produces a high-quality system with low investment costs. <br>In RAD model, there is less attention paid to the planning and more priority is given to the development tasks. It targets at developing software in a short span of time.<br><br>The rapid application development method contains four phases: <br>1)Requirements planning,<br>2)User design <br>3)Construction<br>4)Cutover<br>The user design and construction phases repeat until the user confirms that the product meets all requirements<strong><br></strong><br><strong>Strengths :<br></strong>- Flexible and adaptable to new changes/upgrades.<br>- Increased productivity in short time with lesser people working on the project.<br>- The nature of making prototypes makes it possible for lesser defects towards the finished application/product.<br><strong><br>Weaknesses :<br></strong>- Cannot be used for small projects<br>- Reduced features, where features are added in later versions<br>- professional designers and develepors required<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1397415616/6c2168826a653858e736cb7bf5b6a14c/RAD.jpg" />
         <pubDate>2021-10-12 14:36:45 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1810971107</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1813569759</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1397244999/a1aba582b780d4902ada886d3d6a7572/Exercise_2__ASP_Net_.docx" />
         <pubDate>2021-10-13 11:08:07 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1813569759</guid>
      </item>
      <item>
         <title>Ruby on Rails</title>
         <author>tyra0_o</author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1821118098</link>
         <description><![CDATA[<div><br>Group Members:<br>1. Nur Athirah Binti Zaaba (2011156)<br>2. Ahmad Aminulhakim Bin Abu Zarin (2021187)<br>3. Muhammad Fayyadh Bin Muhamad Rashidi (2112151)<br>4. Arif Muqri Bin Ahmad Naziri (2113825)<br><br>Strengths :<br>1. Easy for understanding and use<br>2. Immediate feedback from testing<br>3. An accurate representation of current state of a project will be provided<br>4. The model is applicable to every type of software development processes.<br><br>Weaknesses :<br>1. Requires to remember the status of the different activities<br>2. Requires better communication between all members which may not be achieve all the time</div><div><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/390706486/5463a157dd5db6f5267b997c0eaf90f9/cm.JPG" />
         <pubDate>2021-10-16 13:48:00 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1821118098</guid>
      </item>
      <item>
         <title>Svelte</title>
         <author></author>
         <link>https://padlet.com/azlinnordin/processModel2/wish/1822126267</link>
         <description><![CDATA[<div><br>Group Members :</div><div>- Nurizuan Nazrin bin Komori (2113021)</div><div>-Nur Amanina Binti Mohd Nubli (2011402)</div><div>-Mohammed Fahmi Ahmed (1914939)</div><div>-Johan Adam Bin Ahmad (2116387)<br><br></div><div>Software process model :</div><div>Unified Process Model&nbsp;<br><br></div><div>Strengths :</div><div>- Complete methodology in itself with an emphasis on accurate documentation</div><div>- Diffuses potential integration headaches by forcing integration to occur throughout development</div><div>-Allows for the adaptive capability to deal with changing requirements throughout the development life cycle<br><br></div><div>Weaknesses :</div><div>- Heavily relies on proficient and expert team members</div><div>- Given the emphasis on integration throughout the development process</div><div>- Can be challenging particularly for smaller teams or projects.<br><br></div><div>Reference : <a href="https://airbrake.io/blog/sdlc/rational-unified-process">https://airbrake.io/blog/sdlc/rational-unified-process</a></div><div><br><br></div><div><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1408335440/683c16f866254ffa00d08b0c7b04dcd1/image002.jpg" />
         <pubDate>2021-10-17 13:54:41 UTC</pubDate>
         <guid>https://padlet.com/azlinnordin/processModel2/wish/1822126267</guid>
      </item>
   </channel>
</rss>
