Process and Project

1) waterfall models

Making the waterfall model of software starts with project feasibility analysis, requirements analysis and planning process Then proceed with the design and coding followed code.setelah finished typing test was done and when the program has passed the test of the installation program is done and thereafter the maintenance phase .

The workmanship in every late-stage software required workers who have been certified to guarantee the results of each stage.

        waterfall model of relatively simple model and easy to do, but this model also has some disadvantages such as:

- The possible need for a frozen system that causes no

  kompatitibel with hardware.

-pembekuan needs of the system has resulted in the problem specification

hardware.

-situation like this is very dangerous if it happens to run out of funds at the time of the project.

-it can be triggered the requirement.

-need official documents in the end of each stage.

2) Prototyping

prototytping made ​​to overcome the weaknesses of the waterfall model.In Prototyping design, coding, and testing, each phase is done very formally or thoroughly. Protyping stages starting with requirements analysis, design, code, and test phase of the program requirements system.Dengan freezing prototyping can be overcome.

3) Iterative Development

Iterative Development merupakann combination of the waterfall model and prototyping, along with the addition capabily to

the system until the full system is implemented a. on the development process of iteration is known.

4) Rational Unified Process

  This process is also known iteration process. there are several

  phase in this process;

- Inception Phase

- Elaboration Phase

- Construction Phase

- Phase Transitions

5) timeboxing Model

in this model there is a time limit for each stage in the project.

6) Extreme Programming and Agile Processes

This approach is based on:

- Working software is the key measure of progress in a project.

- For progress in a project, therefore, the software should be developed and delivered

Rapidly in small increments.

- Even late changes in the requirements should be entertained (small-increment

the model of development helps in accommodating them).

- Face-to-face communication is preferred over documentation.

- Continuous feedback and involvement of the customer is Necessary for developing

good-quality software.

- Simple design roomates evolves and improves with time is a better approach

than doing an elaborate design up front for handling all possible scenarios.

- The Delivery Dates are Decided by empowered teams of talented individuals

(and are not dictated).

7) Using Process Models in a Project

The use of the model in the project would be appropriate if the model fits the needs of the project in being on the road kan.semua models have advantages and disadvantages depending on the type of project that will be created.