| K. A. Butler, C. Esposito, and R. Hebron - "Connecting the design of software to the design of work". Comm. ACM, 42, 1 - Jan 1999 |
....to a co operative work between several authors and they list some different kinds of co operation between them. They classify various different modalities of co operation depending on the different possibilities of modifying and reading the same hypertext part at the same time. 5) Butler et al. [16] connect software design with the structure of the workflow in the context where the software will be used. They propose a precise lifecycle in which the design of software has to be done keeping in mind the workflow and the influence on it due to the presence of software. 6) According to Nanard ....
K. A. Butler, C. Esposito, and R. Hebron - "Connecting the design of software to the design of work". Comm. ACM, 42, 1 - Jan 1999
....preformed but have to be synthesised from a variety of sources that contain information which may be poorly structured, contradictory, at varying levels of detail and of uncertain relevance. The systems engineer must use whatever information resources are available to derive the requirements [10]. This typically entails an iterative process of inferring key abstractions (stakeholders, roles, tasks, domain objects, etc. and verifying these against the structure and behaviour of existing systems. Hence, while work concerned with products of the systems engineering process relies upon a ....
Butler, K., Esposito, C., Hebron, R.: Connecting the Design of Software to the Design of Work, Communications of the ACM. 42 (1), 1999.
.... organisation change Required software change Motivating requirements New requirements 3 whatever information resources are available to construct conceptual models of the pre change organisation and its business processes and from these derive the requirements of the legacy software [4]. This typically entails an iterative process of inferring stakeholders, roles, tasks and business objects and verifying these against the structure and behaviour of the in service software. This information has to be gathered from many different sources, both human and documentary. The ....
Butler, K., Esposito, C., Hebron, R.: "Connecting the Design of Software to the Design of Work", Communications of the ACM. 42 (1), 1999.
....of documentary sources of requirements information. 2. Requirements recovery from documents A requirements engineer must use whatever information resources are available to construct conceptual models of an organisation and its business processes and from these derive the system requirements (Butler et al., 1999). This typically entails an iterative process of inferring stakeholders, roles, tasks and business objects and verifying these against the structure and behaviour of business processes to be supported. This information has to be gathered from many different sources, both human and documentary. ....
Butler, K., Esposito, C., Hebron, R. (1999). Connecting the Design of Software to the Design of Work, Communications of the ACM. 42 (1) (pp. 38--46).
....the domain or business into technical documentation and through to the software. The analyst must use whatever information resources are available to construct conceptual models of the pre change organisation and its business processes and from these derive the requirements of the legacy software [Butler 99] This typically entails an iterative process of inferring stakeholders, roles, tasks and business objects and verifying these against the structure and behaviour of the in service software. This information has to be gathered from many different sources, both human and documentary. The ....
Butler, K., Esposito, C., Hebron, R.: Connecting the Design of Software to the Design of Work, Communications of the ACM. 42 (1), 1999.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC