Bansler, J.P. and Bdker, K. (1993) A reappraisal of structured analysis: design in an organizational context, ACM Transactions on Information Systems, 11, 2,165--193.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....software systems cannot be considered in isolation. 2. They are intended to produce analysable system models which set out what the system must do. This implies that we have already developed an understanding of the system requirements and methods have been (in our view) rightly criticised [1,2] because they do not address the difficult problem of requirements discovery as distinct from requirements analysis. This is particularly important for safety related systems where the safety analysis is concerned with discovering what the system must not do rather than what services it should ....

Bansler, J. P. and Bdker, K., "A Reappraisal of Structured Analysis: Design in an Organisational Context." ACM Trans. on Information Systems 11(2), 1993, pp.165-93.

....needs. In other words, its virtues become vices. Against this is the argument that what is wrong with many of the traditional methods of system design is that they owe far too much to the needs of engineering with the result that crucial aspects of the real world are not never properly treated [2]. It is in this respect that analytic approaches which decompose elements of the work activities and tasks, such as Task Analysis and Office Automation, which focuses on the flow of data within a domain, are found wanting [12, 13] The result is, so it is argued, that essential aspects of ....

Bansler, J.P., and K. B0dker. A Reappraisal of Structured Analysis: Design in an Organizational Context. [4CM Trans. on Information Systems Vol 11 No 2, pp 165-193. 11

....observe the project processes, and analyze the observation results. Analysis of methods themselves is also a useful approach. In addition to the case study that was mentioned in section 4. 4, several case studies of software development processes following the methods have also been reported[5, 64]. 4. Generation of CASE tools : CASE tools supporting a new method are necessary to put it into practice. Meta CASE technology allows us to efficiently construct or to automatically generate CASE tools. 5.2. Meta Modeling Many researchers have studied meta modeling techniques to model and ....

J.P. Bansler and K. Bodker. A Reappraisal of Structured Analysis : Design in an Organizational Context. ACM Trans. on Information Systems, Vol. 11, No. 2, pp. 165--193, 1993.

....to be widely accepted in industry. Without this acceptance the use of ethnography is systems design runs the risk of becoming a research curiosity and, thus, devalued as a tool to support effective CSCW design. As a number of studies have shown software engineers typically work under some pressure [8,5]; a pressure which is, in part, determined by market factors. However, the familiar moan that most system development projects are over time, over budget cannot be entirely laid at the door of market pressures. Building large scale systems is a complex and difficult business. Many of them are ....

Bansler, J.P. and Bødker, K. (1993), A reappraisal of structured analysis: design in an organizational context. ACM Transactions on Information Systems,

....be considered in isolation. 2. They are intended to produce analysable system models which set out what the system must do. This implies that we have already developed an understanding of the system requirements and methods have been (in our view) rightly criticised (Gause and Weinberg 1989; Bansler and B dker 1993) because they do not address the difficult problem of requirements discovery as distinct from requirements analysis. This is particularly important for safety related systems where the safety analysis is concerned with discovering what the system must not do rather than what services it should ....

Bansler, J. P. and K. Bødker (1993). "A Reappraisal of Structured Analysis: Design in an Organizational Context." ACM Trans. on Information Systems 11(2), 165-93.

....both are Turing equivalent. 2 1. 1 Introduction Traditional Data Flow Diagrams (DFD s) are the cornerstone of the software development methodology known as Structured Analysis (SA) DeM78] WM85a] and they are probably the most widely used specification technique in industry today ([BB93]) DFD s are popular because of their graphical representation and their hierarchical structure. Thus, they are ideally suited for users with non technical backgrounds and are commonly used to depict the static structure of information flow in a system. Traditional DFD s consist of a set of ....

J.P. Bansler and K. Bødker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Information Systems, 11(2):165--193, 1993.

....form of user interaction with the software is a critical omission of current structured methods. The practical result of this is that these methods are rarely applied as defined. In a study which confirmed some of the imperfections of Structured Analysis (a widely used method) Bansler and B dker (Bansler and B dker, 1993) state: In conclusion, our interpretation of what happens in practice is that experienced designers instead of following the rules and procedures of Structured Analysis pick and choose among the various formalisms given in the method, adapt them for their own purposes and integrate them into ....

Bansler, J.P. and Bødker, K. (1993). "A Reappraisal of Structured Analysis: Design in an Organizational Context". ACM Trans. on Information Systems, 11 (2): 165-193.

.... use in the software engineering community is Structured Analysis (SA) DeM78] GS78] WM85] You89] Within SA one specifies a data model using an Entity Relationship Diagram (ERD) and a data dictionary, and the process by a Data Flow Diagram (DFD) Fra93] Because DFDs are widely used [BB93] many tools support their development. There are at least three attributes of DFDs that are appealing to software engineers: ffl they have a graphical representation, ffl they are hierarchical, thereby supporting the kind of modular decomposition that programmers view as essential, and ffl ....

Jorgen P. Bansler and Keld Bodker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Office Information Systems, 11(2):165--193, 1993.

....feature, this allows an effective comprehensibility, which is useful for the early phases of analysis where the broader functionality of a system is still being determined. Simplicity and generality are particularly conducive for alignment with organisational definitions as discussed by [BB93] i.e. although DFDs lack context, they are context configurable. For workflow modelling, however, DFDs are inadequate. As we saw, process control is implicit in detailed process specifications meaning that execution structure is hidden in pseudo code. The absence of formal semantics an ....

J.P. Bansler and K. Bødker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Information Systems, 11(2):165--193, 1993.

....question, it can be remarked that relatively little is known about the diversity of information modelling processes in practice and the corresponding degree of flexibility needed for adequate support. Empirical studies reported in the literature (e.g. Gui90a] Gui90b] Bal87] Wij91] and [BB93] show that information modelling knowledge as applied by experienced information engineers turns out to deviate from modelling knowledge described in textbooks, regarding both modelling concepts and the way models using these concepts are constructed. These studies served as a starting point for ....

J.P. Bansler and K. Bødker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Information Systems, 11(2):165--193, 1993.

....little is known about the diversity of information modelling processes in practice and the corresponding degree of flexibility needed for adequate support. Empirical studies reported in the literature (e.g. Guindon, 1990a ] Guindon, 1990b ] Ballay, 1987 ] Wijers, 1991 ] and [ Bansler and B dker, 1993 ] show that information modelling knowledge as applied by experienced information engineers turns out to deviate from modelling knowledge described in textbooks, regarding both modelling concepts and the way models using these concepts are constructed. These studies served as a starting point ....

J.P. Bansler and K. Bødker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Information Systems, 11(2):165-- 193, 1993.

.... which has enjoyed wide spread use in the software engineering community is Structured Analysis (SA) 1] 2] 3] 4] Within SA one specifies a data model using an Entity Relationship Diagram (ERD) and a data dictionary, and the process by a Data Flow Diagram (DFD) 5] Because DFDs are widelyused [6], many tools support their development. There are at least three attributes of DFDs that are appealing to software engineers: ffl they have a graphical representation, Leavens s work is supported in part by the National Science Foundation under grant CCR 9593168. y Baker s work was supported ....

Jorgen P. Bansler and Keld Bodker. A reappraisal of structured analysis: Design in an organizational context. ACM Transactions on Office Information Systems, 11(2):165-- 193, 1993.

....enabling and firing time points. However, since our background is in Software Engineering, in particular in Structured Analysis (SA) e.g. DeM78] WM85a] where traditional Data Flow Diagrams (DFD s) are probably the most widely 3 used specification technique in industry today ( BB93] we wanted to present our results in this context. Even though little work has been done on TDFD s to date, we want to encourage the reader to consider TDFD s as a helpful model for complex time dependend systems. It does not matter for the stochastic analysis whether the Markov process and ....

J.P. Bansler and K. Bødker. A Reappraisal of Structured Analysis: Design in an Organizational Context. ACM Transactions on Information Systems, 11(2):165--193, 1993.

No context found.

Bansler, J.P. and Bdker, K. (1993) A reappraisal of structured analysis: design in an organizational context, ACM Transactions on Information Systems, 11, 2,165--193.

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