mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-27 06:44:07 -06:00
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
# Increamental Model
|
|
|
|
## 1. Introduction
|
|
----
|
|
- Requirement is devided into small pieces
|
|
- Each independent chanks passes through the requirements, design, implentation and testing phase
|
|
- implemented and tested until the product is finish
|
|
- each of the little chunks are added to the product to the previous release
|
|
- the process continues until the goal is fulfilled.
|
|
|
|
## 2. Advantage
|
|
----
|
|
- Product is developed <mark style="background: #ADCCFFA6;">quickly</mark>
|
|
- The method is very <mark style="background: #ADCCFFA6;">flexible to change</mark> .
|
|
- <mark style="background: #ADCCFFA6;">Easy</mark> to testing and debugging.
|
|
- Initial delivary <mark style="background: #ADCCFFA6;">cost gets lower</mark> .
|
|
- <mark style="background: #ADCCFFA6;">Easier</mark> to find and solve bugs
|
|
|
|
## 3. Disadvantage
|
|
----
|
|
- Have to get a clear picture of the project
|
|
- need good planning and organization
|
|
- Costly compare to waterfall model
|
|
|
|
## 4. When to use?
|
|
----
|
|
- For web application and product base companies
|
|
- When there is an urge for the early release of the product
|
|
- Where requirement are completely understood |