Exercise 2 | Examples of SE Process Models | Section 1 by AZLIN BINTI NORDIN https://padlet.com/azlinnordin/EX2SEC1 Semester 2, 2021/2022 en-us 2022-03-13 13:18:52 UTC 2023-07-05 14:02:23 UTC hello@padlet.com https://padlet.net/icons/png/1f5a5.png <SAMPLE > Group Name azlinnordin https://padlet.com/azlinnordin/EX2SEC1/wish/2092314415 Group Name:
Group Members: (only list the members who participate in the exercise)
Include:
1) a figure of the chosen sofware process model (see the sample)
2) provide a brief explanation of the model (two or three statements)
3) briefly list a MINIMUM of THREE Strengths and THREE Weaknesses of the process model.

Instruction:
1) add references to the figure (where you get the information).
2) Avoid using any of the process models that have been used in the lectures for Lesson-2 & 3.- you can use variations of the model. Submission is based on first-come-first-serve and NO duplicated process model.
3) DO NOT SPEND TOO MUCH TIME. The expected time to complete this exercise is not more than 1 hour.]]> 2022-03-13 13:18:52 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2092314415 Group G : EMBER https://padlet.com/azlinnordin/EX2SEC1/wish/2093179624 Group Name: EMBER
Group Members :
1) Muhammad Irfan Zaki Bin Mohd Razali (2119015)
2) Siti Nurfarahanim Binti Mohd Isa (2119316)
3) Noor Najihah Binti Nordin (2116116)
4) Nursyahira Binti Salleh (2115912)

Rapid Application Development (RAD Model) is a model that is based on prototyping and iterative development with little or no planning involved.

The RAD model, functional modules are built concurrently as prototypes and then combined to form the whole product, resulting in a quicker time to stakeholder.

The classic SDLC is based on rigorous process models with a strong focus on requirement analysis and collection prior to beginning coding. Nevertheless, the RAD model is all about iterative and incremental delivery of working prototypes to the client.

__________________________________
Strength of RAD process model

- clients feedback can be obtain through every phase.
- easy to make changes in the project.
- any error can be seen easily during the prototyping thus able to debug quickly.

_____________________________
Weakness of RAD process model

- RAD is not compatible with all apps.
- It is difficult to keep track of problems and improvements.
- It is not suitable for minor project.]]> 2022-03-14 05:46:35 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2093179624 Group B : DJANGO fariha3011 https://padlet.com/azlinnordin/EX2SEC1/wish/2093909105 Group Name: DJANGO
Group Members:
1) Qhuratul Nissa Binti Mior Idris (2116092)
2) Fariha Hadaina binti Mohd Shazali (2114478)
3) Maryam Umairah binti Arman Yatim (2110256)
4) Sofea Hani binti Ahmad Shazali (2115668)

DevOps comes from two words which are development & operation, representing the collaborative approach of a company's dev & ops team. DevOps is a model that emerges from two trends, Agile and Lean.

It is to improve work throughout software development lifecycle as an infinite loop.

Strengths
1. Accelerate the teams’ speed of performance.
2. Provide for an efficient production environment.
3. Quick adaptation to alterations.

Weaknesses
1. Organizational and IT departmental changes.
2. Expensive tools and platforms to use effectively.
3. Unnecessary, fragile and unsafe automation.]]> 2022-03-14 14:01:13 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2093909105 Group D : Spring syahirahsyarkan57 https://padlet.com/azlinnordin/EX2SEC1/wish/2093921307 Group Name: Spring
Group Members :
1)  Danish Zahiruddin bin Khairul Anuar (2012785)
2) Nursyahirah binti Syarkan (2112510)
3) Nurin Afiqah binti Mohd Baharuddin (2113272)
4) Nurul Alifah Maisarah binti Abdul Halim (2114912)
--------------------------------------------------------------
Feature Driven Development (FDD) is an agile methodology that organises software development around achieving progress on features, as the name indicates. However, features in the FDD context are not necessarily product features in the traditional sense. Instead, they're more analogous to Scrum's user stories. In other words, in the Feature Driven Development (FDD) technique, "finish the login procedure" might be considered a feature.

--------------------------------------------------------------
Strengths of Feature Driven Development model
-Rapid development is possible because to a simple five-step method.
-Allows bigger teams to continue to succeed in moving products forward.
-Uses pre-defined development standards to allow teams to work rapidly.
--------------------------------------------------------------
Weaknesses of Feature Driven Development model
-For smaller tasks, it is ineffective.
-There is less written documentation, which might lead to misunderstanding.
-Highly reliant on lead programmers or developers

--------------------------------------------------------------
References : 
1- Feature driven development (FDD). (2021, August 25). Product Roadmap Software | ProductPlan. https://www.productplan.com/glossary/feature-driven-development/]]> 2022-03-14 14:06:31 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2093921307 Group C: LARAVEL afiqahrashid636 https://padlet.com/azlinnordin/EX2SEC1/wish/2093929406 Group Name: Laravel
Group Members: 
1)Aida Najihah Binti Mohd Marzuki (2118230)
2)Ainul Mardhiah Binti Mohammed Rafiq (2112100)
3)Aina Zahira Binti Mohd Zaki (2115676)
4)Afiqah Binti Abdul Rashid (2116908)


The Fish model is one of the software development approaches in which verification (Review) and validation (Testing) are performed concurrently by independent teams at each phase of the model. This model's structure resembles a fish, thus the term "fish model." It is a time-consuming and costly model. Both verification and validation are carried out in parallel by separate teams at each step of the model.

It is a software development life cycle (SDLC) technique that includes all phases of the software development process. To finish the development of the application, all steps are connected to the verification and validation procedure. 


Strengths:
  • It is easy to implement.
  • It provides full documentation of the application.
  • Every stage of this model is tested by a separate team for completeness and correctness of application, so it provides a high-quality software product.


Weaknesses:
  • This model is not preferred for a small project.
  • It is an expensive and time-consuming process to develop the product.
  • Cannot change the requirements in the middle of the process.


]]> 2022-03-14 14:10:08 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2093929406 Group A : Express shahirakram1 https://padlet.com/azlinnordin/EX2SEC1/wish/2093998550 Group Name : Express
Group Members :
  1. Hanis Karmila Binti Suhaimi (2113412)
  2. Hadura Fairuzza Binti Abd Halim (2113584)
  3. Shahir Akram Bin Anuar (2113999)
  4. Farahiyyah Binti Munawwar Hidayat (2116780)

KANBAN Model

Introduction

KANBAN methodology is an agile method that aims for continuous improvement, task management flexibility, and improved workflow. The progress of the entire project can be easily understood in a glance with this illustrative approach. The kanban method is centred on the kanban board. It is a tool that visualises the entire project in order for the user to track the progress of their project. A new member or an external entity can understand what's happening right now, completed tasks, and future tasks by using the graphical approach of Kanban boards.

Strengths :
  1. It is simple and easy to use.
  2. Kanban lessens the cost and wastage.
  3. It also advances collaboration and makes the entire team collaborate to achieve the best results.
Weaknesses :
  1. Cannot be used on its own.
  2. Does not work well in dynamic environment.
  3. The lack of ability to iterate.

References :
1. https://wisdomplexus.com/blogs/pros-cons-kanban/amp/
2. https://kissflow.com/project/agile/kanban-methodology/
]]> 2022-03-14 14:39:10 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2093998550 GROUP I : EMBER alifrazmi15 https://padlet.com/azlinnordin/EX2SEC1/wish/2095978596 Group Name : Ember
Group Members :
1. Muhammad Alif Haziq Bin Mohd Razmi (2110091)
2. Muhammad Aiman Bin Johari (2118131)
3. Muhammad Al-Qardhawi Bin Azahar (2114045)
4. Muhammad Akmal Bin Rahimey (2119651)

Big Bang Model is a model that did not follow any specific process or procedure but required a little bit of planning. We develop software by using time, effort and resources, but that product may or may not meet as per client (customer) requirement. This model is suitable for small projects where the development teams are very small and not suitable for large software development. It is a good model for the software product where requirements are not clear or not understood and there is no release date for that software product.

Strengths:
1. It requires less planning. There is no need for big analysis and planning, just start coding.

2. It is cost-effective. To implement this model in software development, it requires fewer resources, less developers, and less managing cost.

3. It has no time limit for project so flexible for developers: For the software product, there is no release date for deployment and it puts less pressure on developers to develop the product.

Weaknesses :
1. It is an Extremely Risky model. Due to less planning and no need to follow the SDLC process steps during software development.

2. It is an inexpensive model. This model provides less return on investment (ROI) as the product didn’t use in the global market.

3. It is the worst model for long and ongoing projects. For a long or big project, we need multiple steps, like, service level agreement, planning, preparation, analysis, testing, execution,  whereas in Big Bang model doesn’t have it.]]> 2022-03-15 13:37:28 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2095978596 GROUP H : RAILS abdhannan1704 https://padlet.com/azlinnordin/EX2SEC1/wish/2097296699 GROUP MEMBERS:
Ahmad Imtiyaz Bin Suhaimi (2113719)
Adam Haikal Bin Alias (2114265)
Amir Arif Bin Rosli (2116249)
Abdul Hannan Bin Zainudin (2118719)

BRIEF EXPLAINATION :
- Incremental model is used when the requirements are superior and the project has a lengthy development schedule.
- When Software team are not very well skilled or trained or
when the customer demands a quick release of the product we can apply incremental model.
- You can develop prioritized requirements first.

ADVANTAGES:
1. Errors can be easily recognized and also more flexible too.
2. Easier to test and also debug.
3. Easier to manage risk because it handled during its iteration.
5. The client gets important functionality early.

DISADVANTAGES:
1. It requires a good planning designing
2. It is costlier than waterfall model.
3. Definition of system should be complete and clear.

sources:
https://www.visual-paradigm.com/guide/software-development-process/what-is-a-software-process-model/

https://www.javatpoint.com/software-engineering-incremental-model]]> 2022-03-16 04:28:16 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2097296699 Group E: Angular SyakRidz02 https://padlet.com/azlinnordin/EX2SEC1/wish/2097330465 Group Name: Angular
Group Members:
1) Nursyakirah binti Ridzuan (2112324)
2) Nurul Balqis binti Azri (2116956)
3) Nurul Farhanah Natasya binti Rozelan (2115210)
4) Nor Anisah binti Amir Hamzah (2114564)

Lean development is born out of the lean manufacturing principles by Toyota. It focuses on minimizing wastage and increasing productivity. With the guiding principles, developers avoid non-productive activities while delivering quality in their tasks.

The Toyota-inspired methodology also emphasizes continuous learning and deferment of decision. It empowers teams to keep an open mind during the course of development and consider all factors before finalizing a decision.

With the lean methodology, developers are tasked to identify bottlenecks that could hamper the process. The goal is to establish an efficient system that works flawlessly. The methodology also emphasizes human respect, which means communication is key to enhancing team collaboration.

Strengths:
  • Cuts down wastage in the project, such as redundant codes, unnecessary documentation, and repetitive tasks. 
  • The overall cost of development is reduced with the lean principles.
  • Time-to-market for the software is shortened as lean development promotes efficiency. 

Weaknesses:
  • For lean development to be successful, you’ll need a team of highly-skilled developers, which isn’t easy to put together.
  • Less-skilled developers can be overwhelmed by the responsibilities and loss of focus on the project.
  • Detailed documentation is needed, which places an enormous burden on the business analyst.
]]> 2022-03-16 04:58:59 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2097330465 Group F: Vue aqilahzaidon321 https://padlet.com/azlinnordin/EX2SEC1/wish/2102855083 Group Name: Vue

Group Members:
1) Nur Fatihah binti Abdullah (2115778)
2) Nur 'Aqilah binti Zaidon (2110682)
3) Nurul Nuha binti Mohd Zaki Udin (2111738)
4) Naafilah Hudaa binti Muhammad Shakir (2111798)

One of the most widely used Software Development Life Cycle Models (SDLC models) is the Prototyping Model. When customers do not know the exact project requirements ahead of time, this model is used. In this model, an end-product prototype is first created, then tested and refined based on customer feedback until a final acceptable prototype is achieved, which serves as the foundation for developing the final product.

The system is partially implemented before or during the analysis phase in this process model, allowing customers to see the product early in the life cycle. Interviewing customers and developing an incomplete high-level paper model are the first steps in the process. This document is used to create the first prototype, which only includes the most basic functionality requested by the customer. Once the customer has identified the issues, the prototype is fine-tuned to eliminate them. The process continues until the user approves the prototype and is satisfied with the working model.

Strengths:
1) Because of the repetitive effort in testing and fine-tuning, software has few flaws.
2) Due to frequent and transparent development, there is clarity between team members during development.
3) Changes in project specifications are easily addressed and implemented with minimal disruption to the timeframe.
4) The quality of the deliverables has improved overall.

Weaknesses:
1) Might lead to poor documentation due to customer requirements that keep changing.
2) Difficult for developers to serve all the changes demanded by customer.
3) There is probability where customers might lose interest with the product as they not satisfied after seeing the initial prototype.

References:
1) https://www.geeksforgeeks.org/software-engineering-prototyping-model/?ref=gcse
2) https://www.guru99.com/software-engineering-prototyping-model.html
3) https://www.uptech.team/blog/software-development-methodologies]]> 2022-03-19 09:19:09 UTC https://padlet.com/azlinnordin/EX2SEC1/wish/2102855083