"What if? Why not? Challenge the Convention! Let's do some incredible things!"
Pro Android 4
Our Android Books
Stuff I used to do
Download OSCON 2004 Presentation
tries to define rup
Deliverables at inception
Deliverables at elaboration phase
Vague on the other two phases
Tries to define a usecase
Outlines a usecase structure
Goes to the core via
Boundary, entity and control classes
1. Online rep of process information
2. Have templates for usecases, project
For use cases it is ok
Will they work with microsoft project?
3. Process manuals
A "pattern" in software refers to an approach, a method, a technique or a way to solve a software problem. Then why not call it one of those instead of calling it a pattern. When will a technique become a pattern? A "pattern" is a promotion of the above to a more formal level. First thing a pattern forces is to come up with a name. This name is intended to be fairly unique in the field so that it will uniquely identify the subject and its surrounding context. It is almost like you are submitting the "technique" to a library of techniques with a formalized name.
Like all names, a pattern's name should be as "specific" as possible. Invoking its name should bring the whole meaning and context of the pattern to surface. The name is not necessarily named after the patterns feature, usage, or implementation, or advantage. The only obligation of the name is that it should try to evoke this pattern as unequivocally as possible in a collection of similar features, usages, or implementations.
Gets a bit deeper into RUP
From the literature it is very difficult for me to nail down what it is. It seems to be different things to different people and everything and the kitchen sink to some people. No two definitions seem to match. For some it is a documentation driven heavy weight way to manage a project from begining to end. For some it is a feather weight like XP, Extreeme Programming. For some it is requirements management. For some it is a web site with process documentation. For some it is UML and for some UML is optional.
Due to the wealth (or volume) of the information out there I will try to summarize and add my own confusion.
RUP is a commericialized version of Unified Software Development process by Rational.
Sort by Date
Sort by Name
My Web Logs
Made possible by