# data[].attributes.body
Group Members :

- Nurizuan Nazrin bin Komori (2113021)

-Nur Amanina Binti Mohd Nubli (2011402)

-Mohammed Fahmi Ahmed (1914939)

-Johan Adam Bin Ahmad (2116387)

Software process model :

Unified Process Model

Strengths :

- Complete methodology in itself with an emphasis on accurate documentation

- Diffuses potential integration headaches by forcing integration to occur throughout development

-Allows for the adaptive capability to deal with changing requirements throughout the development life cycle

Weaknesses :

- Heavily relies on proficient and expert team members

- Given the emphasis on integration throughout the development process

- Can be challenging particularly for smaller teams or projects.

Reference : https://airbrake.io/blog/sdlc/rational-unified-process

# data[].attributes.body
Group Members :
-Ammar Haziq Bin Annas 2116043
-Afnan Iman bin Azman 1920311
-Tengku Zarul Fariman Bin Tengku Zahidi 2117365
-Muhammad Nadzmi Bin Mohd Ronizam 2028427

Software process model :
Rapid Application Development(RAD Model)
-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.
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.

The rapid application development method contains four phases:
1)Requirements planning,
2)User design
3)Construction
4)Cutover
The user design and construction phases repeat until the user confirms that the product meets all requirements

Strengths :
- Flexible and adaptable to new changes/upgrades.
- Increased productivity in short time with lesser people working on the project.
- The nature of making prototypes makes it possible for lesser defects towards the finished application/product.

Weaknesses :
- Cannot be used for small projects
- Reduced features, where features are added in later versions
- professional designers and develepors required

# data[].attributes.body
Group Members:
1. Nur Athirah Binti Zaaba (2011156)
2. Ahmad Aminulhakim Bin Abu Zarin (2021187)
3. Muhammad Fayyadh Bin Muhamad Rashidi (2112151)
4. Arif Muqri Bin Ahmad Naziri (2113825)

Strengths :
1. Easy for understanding and use
2. Immediate feedback from testing
3. An accurate representation of current state of a project will be provided
4. The model is applicable to every type of software development processes.

Weaknesses :
1. Requires to remember the status of the different activities
2. Requires better communication between all members which may not be achieve all the time

# data[].attributes.body
Group Members :
- Mohamad Aiman Akim Bin Adanan
- Raja Muhammad Hazwan Bin Raja Azman
- Nayli Syazreen binti Shaiful Hizam
- Irdina Izzati Binti Mohd Rasid

Software process model :
The Incremental Model

Strengths :
- Risks are manageable because the errors are identified easily
- There is a chance to change requirements, thus it is flexible
- Work is done quicker because planning early increments can be implemented

Weaknesses :
- Changing the requirements of the user will lead to high cost
- Need a very clear vision of the whole system
- Need a strategic and effective planning

# data[].attributes.body
Group Members :
Muhammad Syafiq Farhan Bin Mohd Faridz (2011871), Adam Khuarizmi Bin Maszlan (2115347), Irdina Batrisyia Binti Nor Azli (2117188), Nazmy Asnawi Bin Hamidun Majid (2119837)

Strengths of The Waterfall Model :
- This model is simple to comprehend and apply
- Because of the model’s rigidity, it’s simple to manage as each steps has specified deliverables and a review procedure
- Each phase are processed and completed one at a time in this model so that phases do not overlap each other
- This Waterfall Model works well and effectively for smaller projects as the requirements are clearly defined and very well understood

Weaknesses of the Waterfall Model :
- 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
- There will be no functioning software produced until the end of the life cycle
- There is a lot of risks and uncertainties
- It is not a good model for complex and object-oriented projects and applications
- Poor model for long and outgoing projects
- Not suitable for projects with a moderate to high risk of change in requirements

# data[].attributes.body
Group members: Hafzlan Aidieq, Khairil Nazrel, Aniq Rahim
Software process model: Prototyping model

Strengths:
1) There is room for improvement, new requirements can be easily met.
2) Functionalities that aren't present can simply be discovered.
3) Errors may be spotted sooner, saving time and money while also improving the quality of the product.

Weaknesses:
1) During customer evaluation, there may be too much diversity in needs.
2) Due to constantly changing customer requirements, there is a lack of documentation.
3) In a rush to produce prototypes, developers may come up with poor solutions.

# data[].attributes.body
Group Members: Luqman Al Hakim, Farah Iwani, Alisya Marsya Hanania, Danial Aniq

Strengths;
1. The V-Model is used for small projects with well-defined needs
2. Simple and straightforward to comprehend and apply
3. It allows project managers to keep proper track of progress

Weaknesses;
1. High risk and uncertainty
2. Not suitable for object-oriented or large projects
3. It is hard to handle concurrent events

ref: https://www.geeksforgeeks.org/software-engineering-sdlc-v-model/

# data[].attributes.body
Group Members:
Include a figure of the chosen sofware process model * and briefly list the Strengths and Weaknesses of the process model.
Note: * add the reference to the figure