Love Marriage Vs Arranged Marriage a Programmers Perspective

Love Marriage Vs Arranged Marriage a Programmers Perspective
~~~~~~~~~~~~~

First Love Marriage : Resembles procedural programming language. We have some set functions like flirting, going to movies together, making long conversations on phone and then try to fit all functions to the candidate we like.

It is a throwaway type of prototype as client requirements rises with time thus it is a dynamic system and difficult to maintain.

Family system hangs because hardware (called parents) is not responding.

You are the project leader so u are responsible for implementation and execution of PROJECT- married life.

Client expectations include exciting feature as spouse cooking food, washing clothes etc.

Acceptance test possible you can try before you Buy.

Love Marriage is like Windows, beautiful n seductive.... Yet one never knows when it will crash!


Now for the Arranged Marriage :Similar to object oriented programming approach. We first fix the candidate and then try to implement functions on her. The functions are added to supplement the main program. The functions can be added or deleted.

Requirements are well defined so use of waterfall model is possible

Compatible with hardware (Parents).

You are a team member under project leader (parents) so they are responsible for successful execution of project Married life.

All these features are covered in the SRS as required features.

Product is sold on an as is where is basis. Product once sold will not be taken back!

Arranged Marriage is like Unix... boring n colorless... still extremely reliable and robust.