Requirements Inc.

Waterfall vs. RUP in non-Greek

2010-07-31T14:12:54Z

Ever heard that Waterfall actually is not just about water falling? And the cool sounding RUP is not as cool as rap (or is it)? We IT folks are so jargonauts and we keep it that way to make our profession intimidating for the rest of you!

Now lets take a closer look at these software engineering approaches with a construction analogy. After all, when we first started building software, we borrowed concepts from constructing buildings! Waterfall is representative of a conventional methodology, while RUP is contemporary, forming the basis of iterative and incremental methods, paving the path towards Agile Development.

Let us say the project at hand is to build three apartment complexes, A1 A2 and A3. You got three months, Jan Feb and Mar. For simplicity, assume that the project involves three primary processes, structuring, engineering and landscaping.

The Waterfall Enclave Apartments

Waterfall, one of the earliest software engineering principles, is a top-down, common sense approach. It proposes that the key processes in a project must be performed sequentially.

We know the three key processes are: structuring, engineering and landscaping. Waterfall directs us to perform each task in one 'big bang'. Do it once, do it right! (Does this sound ambitious? Not everything about the project is known clearly up front!)

In Jan, we take on the structuring work for all the three complexes, A1, A2 and A3. In Feb, we get going with all the engineering for all three complexes and in Mar, we finish the project by landscaping for A1, A2 and A3.

This is how the plan will look like this:

And this is how the construction will progress over the three months visually:

The RUP Hill Apartments

RUP, one of the newer software engineering principles, recommends that key sub-projects in the project be identified first. Take sub-project 1, complete the processes, then move on to project 2 and finish by repeating the key processes for project 3. .

Break the bigger problem into three sub-problems: A1, A2 and A3. Take A1, perform the tasks (structuring, engineering and landscaping) then repeat for A2 and then A3.

In Jan we'll take A1, completing structuring, engineering and landscaping. Then, A2's structuring, engineering and landscaping in Feb. Repeat for A3 in Mar.

The plan will look like:

And visually in three months we'll see the apartments grow:

RUP is called an iterative and incremental model. Iterative, since we repeat the processes in each iteration(A1, A2 and A3 were our iterations). Incremental since each iteration contributed to expanding the project towards it completion.

Is RUP is better than Waterfall?

Yes and No, depends on several factors, such as the project size, problem domain area, how solid are requirements, etc. Predominantly, RUP and Agile methods are adopted a lot these days. Why did we shift our focus?

Are there any clear benefits on using RUP? Share your thoughts in the comments and also tell us what process are you adopting in your project.

Here is a video snippet from a trial class of our Full Cycle Business Analysis in this topic. Register for a trial class.

Click here to view the embedded video.

Jul 24 – Free Trial: Business …

2010-07-16T06:50:14Z

Jul 24 – Free Trial: Business Analysis/Analyst Course (Online / On-Demand / In-Class) RSVP@ http://bit.ly/44YNpH RT to invite friends

Take Classes Anytime Anywhere

2010-07-13T03:00:59Z

Course timings don't work?

Prefer learning at your own time?

Wish there was a rewind button in the live course?

Our Instant On-Demand Courses may be the right option for you. Take the course entirely online anytime, anywhere. You will get full-length Videos of classes recorded during a live course.

Participant Q and As, Class activity discussions, Business modeling sessions, Course Materials, Software downloads, Additional references are packaged in the On-Demand version so you don't miss a thing. You get the same set of assignments and online tests as the live course. You may also avail live instructor support to get your questions answered by one of our trainers as needed.

You can even try out a trial class in the Instant On-Demand format! Click here to try out all our on-demand courses and register for a free trial class.

View FAQs on the Instant On-Demand option here.

Is UML a programming language?

2010-07-12T04:27:51Z

The UML stands for Unified Modeling Language. It is christened a "language" since the representation involves predefined notations, semantics and rules – so all participants involved – stakeholders, analysts, developers, testers all interpret these diagrams the same way.

It is not a programming language (such as C, C++, Java) or a sub-language (such as SQL) and does not have a set of 'command keywords'.

The UML is a representation method, providing for different views to detail the software system under design. Just like we have front elevation, floor plan, electrical plan, plumbing plan, in the construction industry, to document different aspects of the same building, UML offers a set of diagrams to represent varied views for a software system. Each of these diagrams have a specific perspective to deliver to the reader, and it makes sense to overlay multiple diagrams to get the complete picture. The UML was architected by the Object Management Group (OMG) and they continue to maintain the definition for the later releases. Visit OMG.org and UML.org for more information.

The UML is an analysis toolbox that allows authoring of specific details of the system, such as business processes, state changes of key objects in a system, etc.

What is UML? From UML.org

See this post for a listing of primary UML diagrams.

Please ask your questions, using the comments. Thanks!

Use Case – Diagram and Document

2010-07-31T06:56:09Z

Use Cases are meant to represent the high level functional areas of the system, as represented in a ULM Use Case Model (or use case diagram). Primarily meant to analyze the different parts of the system and their relationships and dependencies.

Each 'textal' use case is then blown into its own 'user manual' style document detailing the dialogue between the 'system' (the software you are developing) and the 'actors' (people, things or other software that interact with your software).

Click here to view the embedded video.

UML Basics: Include and Extend Stereotypes in Use Cases

2010-07-13T02:57:31Z

Include and Extend are two key constructs in UML Use Case Diagrams. Learn about the two constructs, the differences and how to use them in your model!

Click here to view the embedded video.