Hello you… informatics… affine … … person. Welcome to Mastery02: Unified Process. As you already know (because you read all of my posts), this post is about Analysis and Modeling of Software Systems or TC2004.
I am happy to welcome you to the latest post about the not so latest Mastery topic (we are already at Mastery 03 so I am a topic behind, to be fair, everybody said that studying in Mexico is easy, much easier than in my home country… trust me, it’s not!) about (obviously) Unified Process.
Already hyped? Yes? No? Well… you already now.
The Unified Process is an iterative and incremental software development process framework.
Further, it is a framework, which is extensible and customized for specific organizations or projects.
„What is a Framework? „-You & me before I read about it
Well, imagine you want to build a house. What do you start with? Yes, the foundation but also the framework, right? And that’s what the Unified Process is, it’s the skeletal structure of the software you are going to build, that’s why the Unified process (UP) is architecture centric and use-case driven. A more specific explanation is that a framework provides a code (e.g. CC+ or Java) that shows/knows what to do, but not how to do it. In java the framework would have the classes, the methods, etc., with comments about what the function of that class or method is, but there would be no actual code in the methods or classes. No knowledge about Java? No problemo, imagine you want to prepare a meal, but you only have a list of ingredients, not a real recipe. This would be your “framework “.
The UP can be applied to different software systems, with different levels of technical and managerial complexity. Furthermore, it divides the development process into four phases and defines what actions are taking place in what phase:
– Inception (with communication & planning)
– Elaboration (with planning & modeling)
– Conception (with construction)
– Transition (with deployment & construction)
This diagram shows the four phases (Inception, Elaboration, Construction, Transition and Production) above and the actions (Requirements, Analysis, Design, Implementation, Test and Support) on the left (sry for my crucial handwriting). The bars illustrate how deep the integration of the action is in the phase. The higher the bars, the higher the integration.
So, let’s come to “The Three Amigos”. Sound interesting, like the three amigos El Mariachi, Lorenzo and Fidelo. But this is not about guitars which fire bullets and rocket, it’s about TC2004. So in this case the three amigos are Grady Booch, Ivar Jacobson and James Rumbaugh.
What? You don’t know these guys (Ken I think you know them)? Well, me neither so I liked their wikipedia entry for you. These three guys agreed on a unified notation system and build the UML (Unified Modeling Language). The standardization and further development of the language was transferred to the Object Management Group (OMG). With a common language, a common object-oriented method could now be developed. The Unified Process was developed and published parallel to the Unified Modelling Language by „The Three Amigos“.
The UP has different implementations and variations, the most common one ist he RUP (Rational unfified process), but there are more:
–AUP (Agile Unified Process)
–OpenUP (Open Unified Process)
–BUP (Basic Unified Process)
–OUM (Oracle Unified Method)
They vary from each other in how they categorize the project actions or workflows.
You have done it! So, you’ re either Ken who has to read this post so he can give me a grade *cough* I hope I get two points for this *cough*. If your not Ken, well, thank you mom for reading my post, I love you! Jokes aside!
Thank you very much for sticking around.
See you on my next post!