Let’s describe Unified Software Process (USP)

It is not easy to prove your knowledge on this kind of topics when it had been like more than one year since I read about it.

---

Definition

What I remember about it is that can be seen as a framework or a scheme applied to different software systems where you carry or maintain an incremental and iterative development process where can be customized for specifics need of the protect, in spite of the customs the main phases according to the Techopedia website are:

I will try to explain it the easiest way possible

• Inception
  • Is the phase were the ideas are conceived, all the requirements are collected and an analysis is made for determinate the model to use, these requirements are asked directly from the costumer to assure feasibility.
• Elaboration
  • Expand the ideas declared on the inception phase, set goals of the activities, and create realistic functional requirements (detailed) for the architecture and make sure you got a list of the needed resources because all cost related resources got to be declared to the customer.
• Conception
  • Also known as construction phase, this part of the process is to develop and write actual code and implementing the features by each iteration and following the use cases or goals.
• Transition
  • Phase where the costumer take part in reviewing the development of each iteration, fixing bugs or needed builds for the costumer where it may need maintenance in the future.

If you want to learn more about it, and by learn I really mean LEARN, your can buy the Unified Software Development Process form here, I just use it as medium but you can eat the whole think, I won’t do it because I have to pay my career