Resumen
The article reports on connecting the design of software to design of work. The software embodies a model of work processes for its end users because part of its job is to manage the content, format and sequencing of the information that users need to do their work. The design of work and the design of software are distinctly different domains. The two designs must interact, but they must each also function in their respective local environments, which are fundamentally different. The analysis and design of work deals with activity that will be executed in the physical world, where its goal is to achieve physical qualities such as better resource utilization, reduced cycle time and variance, reduced costs and waste, or to generate products with real-world qualities. In contrast, software design has historically emphasized completeness and consistency, and the efficiency of code that will be executed electronically. Work design and software design require two different types of languages to model two different worlds that are understood by different people