Context and Domain
"Bill Walton" <[email protected]> Tue, 7 Jan 2003 09:17:05 -0600
| Newsgroups | gmane.comp.programming.extreme-customering |
|---|---|
| Message-ID | <001d01c2b65f$d6adadd0$6401a8c0@dp2000> |
------=_NextPart_000_001A_01C2B62D.8BC3BE40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Greetings, I start with an assumption: the value of a specific Practice is context an= d domain sensitive. Glen and Stefan have both talked about this explicitly= in recent posts and it is this topic in general that began my XP explorati= on. If this is true, then it would help, I think, to have an understanding= of the taxonomy of contexts and domains facilitate a better understanding = of / ability to predict the value delivered by implementing any particular = practice. To start the discussion, I'll try to articulate what *I* mean by= "context" and "domain." My hope is that we can reach a consensus on the m= eanings here, then start to identify the attributes that identify specific = contexts and domains and the opportunities / challenges for applying specif= ic practices (XP and otherwise) within those. Context - My thought is that the top level qualifiers for Context are "con= straints." At one end of the Context axis there are few constraints. One = programmer working on her own time, on a project of her own choosing, no de= adline, etc.... At the other end of the axis there are many and quite rigi= d constraints; leglislative, regulatory, cultural, economic, etc.. A thous= and Union programmers working on a government mandated project subject to o= versight by numerous regulatory agencies with an "or else the world as we k= now it will end" deadline, etc.... Domain - When I think of "domain," two competing structures immediately com= e to mind. Shrink-wrapped vs. IT at the top level with type of application= (e.g., accounting, legal, engineering, shop floor, ATC, etc.) at the next,= and vice versa. Are these close to what you guys mean when you talk about Context and Domai= n? Best regards, Bill ------=_NextPart_000_001A_01C2B62D.8BC3BE40 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.3315.2869" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial>Greetings,</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial>I start with an assumption: the value of a specific Practice is context and domain sensitive. Glen and Stefan have both talked about this explicitly in recent posts and it is this topic in general that began my XP exploration. If this is true, then it would help, I think, to have an understanding of the taxonomy of contexts and domains facilitate a better understanding of / ability to predict the value delivered by implementing any particular practice. To start the discussion, I'll try to articulate what *I* mean by "context" and "domain." My hope is that we can reach a consensus on the meanings here, then start to identify the attributes that identify specific contexts and domains and the opportunities / challenges for applying specific practices (XP and otherwise) within those.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial>Context - My thought is that the top level qualifiers for Context are "constraints." At one end of the Context axis there are few constraints. One programmer working on her own time, on a project of her own choosing, no deadline, etc.... At the other end of the axis there are many and quite rigid constraints; leglislative, regulatory, cultural, economic, etc.. A thousand Union programmers working on a government mandated project subject to oversight by numerous regulatory agencies with an "or else the world as we know it will end" deadline, etc....</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial>Domain - When I think of "domain," two competing structures immediately come to mind. Shrink-wrapped vs. IT at the top level with type of application (e.g., accounting, legal, engineering, shop floor, ATC, etc.) at the next, and vice versa.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial>Are these close to what you guys mean when you talk about Context and Domain?</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial>Best regards,</FONT></DIV> <DIV><FONT face=Arial>Bill</FONT></DIV> <br> <br> <tt> To unsubscribe from this group, send an email to:<BR> extremecustomering-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org<BR> <BR> </tt> <br> <br> <tt>Your use of Yahoo! Groups is subject to the <a href="http://docs.yahoo.com/info/terms/">Yahoo! Terms of Service</a>.</tt> </br> </BODY></HTML> ------=_NextPart_000_001A_01C2B62D.8BC3BE40--