RE: [epf-dev] BUPFundamental Concepts and CollaborativePrinciplesProposa

["VAIDYA Kirti" <KVAIDYA@xxxxxxxxxxxx>]

To me software development is like making a movie (a good boss gathered us in a room once during the eighties in Bombay, and shared this idea which has stayed with me!)

Like the theater, a movie is one dream everyone in the team lives for a few months anticipating its successful fruition. I have observed that good movies typically have good collaboration between the writer, script writer, and director (e.g. The Godfather pt. I: Mario Puzo & Francis Ford Copppola) plus others like the editor, music director and cinematographer (can cite many other examples incl. some Indian movies). I could go on and create a good mapping of attributes between software development and movie making. Perhaps where it differs from theater is the fact that every some months newer technologies are being introduced to moviemaking (just like software!) - e.g. digital effects, digital animation, digital processing, (these are changing the way movies are made, just like newer IDEs like WBI Modeler + RSA show the potential to change how software is conceived and translated to reality - thereby affecting software development processes too), digital projection, etc. (this one will change the distribution rules, just like the web, SOA etc. are doing to software).

Kirti



-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]On
Behalf Of Scott W. Ambler
Sent: Thursday, March 30, 2006 5:45 PM
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] BUPFundamental Concepts and
CollaborativePrinciplesProposal


The best analogy that I've seen to date is the one presented in the 
book "Artful Making" where software development is compared to 
putting on a play.

- Scott

At 04:19 PM 3/30/2006, you wrote:

>I can see how someone would see house building as waterfall (unless 
>you were a housebuilder?)
>
>But I still think we need to have an at a glance view and supporting 
>metaphors to provide additional
>explanations to any terms we come up with.
>
>Regards
>Nvaeena
>
>
>
>
>Peter Haumer/Cupertino/IBM@IBMUS
>Sent by: epf-dev-bounces@xxxxxxxxxxx
>
>03/30/2006 12:42 PM
>Please respond to
>Eclipse Process Framework Project Developers List
>
>To
>Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
>cc
>Eclipse Process Framework Project Developers List 
><epf-dev@xxxxxxxxxxx>, epf-dev-bounces@xxxxxxxxxxx
>Subject
>Re: [epf-dev] BUP 
>Fundamental        Concepts        and        CollaborativePrinciplesProposal
>
>
>
>
>
>I agree. Developing software is not like building a house or a 
>bridge.  These comparisons have been trashed many times in 
>literature.  Software development a la UP is a creative process in 
>which the results are constantly tested, reviewed, and 
>refactored.  You cannot test how you use the kitchen and dinning 
>room area with the house in the elaboration picture.  Same with 
>growing a fetus.  There no way of elaborating a growing child unless 
>you could read and fully interpret its DNA, run tests of its future 
>behavior, and continuously rewrite its DNA until you get the kid 
>that fits your "stakeholder's" needs (what a lovely thought :-).
>
>
>Thanks and best regards,
>Peter Haumer.
>
>______________________________________________________________
>
>Rational Software | IBM Software Group
>PETER HAUMER, Dr. rer. nat.
>RUP Development, Cupertino, CA
>Tel/Fax: +1 408 863-8716
>______________________________________________________________

====================================================
Scott W. Ambler
Senior Consultant, Ambysoft Inc.
www.ambysoft.com/scottAmbler.html

Refactoring Databases: Evolutionary Database Design 
(www.ambysoft.com/books/refactoringDatabases.html) is now available! 

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Confidentiality Statement:

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.