Dear PO,
Thanks for helpful 'generalizations'. [Paul Oldfield] I think, as developers, we are already used to reconciling divergent world views. [wmj] That our job as developers/designers. [Paul Oldfield] If the developers have a slightly different world view from that of the 4+1 RUP approach, then they still need to reconcile this with the customer's world view, and indeed with the world views of all the stakeholders. [wmj] I might be confused here (English is not my native language) but it seems that '4+1 RUP approach' is not about world views but about '4+1 View' of a System being developed. So in a nutshell developers reconcile not only: (1) divergent world views of 'all stakeholders' (2) different (divergent?) System views but also (2) with (1). For (2) we need tools 'to assure System (blueprints) consistency'. For (1) we need tools that allow to present System views that are 'stakeholders' oriented. Regards WMJ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 5:37 AM To: W.M. Jaworski Cc: Osvaldo Kotaro Takai; [unknown]; 'Lowe, Jeff'; 'English, Art'; [unknown]; [unknown]; 'Rossomando, Philip' Subject: RE: (ROSE) RES: (RUP) The 4+1 View Model of Architecture (responding to W.M. Jaworski) > [Paul Oldfield] > However, other developers have other world > views, and don't want 4+1 imposed on them. > > [wmj] > How to assure System (blueprints) consistency when 'developers' and other > stakeholders have divergent 'world views'? I think, as developers, we are already used to reconciling divergent world views. If the whole process is based on a view the developer chooses, then the customer is not likely to find the resultant system useful. OTOH, if it is based on the view the customer chooses, we find that the resultant systems are inflexible with respect to change. Please take these sweeping generalizations in the spirit they are intended. The point is, each world view serves a particular purpose, and is useful to particular groups of perople, because it allows them to proceed about their daily business. The developer is not concerned with all the customer's problems, the customer is not concerned with all the developer's problems. If the developers have a slightly different world view from that of the 4+1 RUP approach, then they still need to reconcile this with the customer's world view, and indeed with the world views of all the stakeholders. Luckily, we don't need to worry about all aspects of each world view, only those that are pertinent to the development of the system. Anything else is someone else's problem. Adopting the 4+1 world view doesn't solve this problem or make it go away. What it does is ensures there are a pile of recommendations and advice ready tailored and available to help solve the problem. If we, as developers, choose to move away from the 4+1 world view, this loss of readily available recommendations and advice is one of the costs we need to take into consideration. OTOH, all this pile of recommendations and advice arose from people who were prepared to go it alone in the past. Paul Oldfield any opinions expressed herein are not necessarily those of Mentors of Cally ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
