What ever happened to structured analysis?
Datamation
The transformation schema: An extension of the data flow diagram to represent control and timing
IEEE Transactions on Software Engineering
Principles of information systems analysis and design
Principles of information systems analysis and design
JSP and JSD: The Jackson Approach to Software Development
JSP and JSD: The Jackson Approach to Software Development
Structured Development for Real-Time Systems
Structured Development for Real-Time Systems
Software engineering meets user services: a methodology for developing user
SIGUCCS '88 Proceedings of the 16th annual ACM SIGUCCS Conference on User Services
Hi-index | 0.00 |
The objective of this paper is to provide a comparison of the following four information processing system development methodologies: The Box Structure Methodology, Application Prototyping, JSD and SASD. Each approach provides a unique and different set of activities that can be followed, with emphasis on different aspects of the life cycle. For this reason, no one methodology is superior in all areas and aspects of the development life cycle. However, each one is superior in its own sense, depending on the type of system being developed. The Box Structure Methodology provides a rigorous coverage of the analysis and design phases in the development life cycle, with the use of design graphics, and a design graphics language. JSD and SASD also use graphical structures as well. However, SASD relies heavily on dataflow diagrams in the analysis and design phases, where as JSD incorporates functions, time requirements, actions, and data into its diagrams in the analysis phase, and then applies them in the implementation phase, without ever going through a design step. Finally, the Application Prototyping development methodology offers an approach that centers around the development of a prototype, which is heavily dependent upon user interaction with the user in the feasibility and analysis phases, but does not offer any design, implementation, or maintenance techniques. A methodology is only approiate for a developer, once he/she has considered these fact, and determined the system's target environment.