Featured Columns systems view of the impact of their software. The narrow focus omits the context of use. As the methods of Agile development and UML models are used in the development and test design, the focus on these methods as currently designed assures that these impacts will be unplanned and unforeseen side-effects. One aspect of being professional is developing systems that improve a situation rather than make it worse. These tools need to be expanded or placed in a context which considers others and takes the system view of software. How can these problems be reduced? In UML it would require a revised notation to represent and to include a broader range of stakeholders. The UML relations modeled by arrows seem to represent strong causal connections, but when dealing with potential software impacts we are dealing with very contingent types of events. These contingent events are not stongly causally defined but rather they are characterized by "In some cases, if you develop the software in this way, it might have this consequence". This type of relation is difficult to model but it might be interesting to explore including this kind of representation in the UML notation (and
/lp/association-for-computing-machinery/does-anyone-remember-the-kdf-9-70F3qlpHVw