Software engineering with Ada
Strategies for real-time system specification
Strategies for real-time system specification
Object-oriented systems analysis: modeling the world in data
Object-oriented systems analysis: modeling the world in data
An object-oriented requirements specifications method
Communications of the ACM
The object-oriented software development method: a practical approach to object-oriented development
TRI-Ada '89 Proceedings of the conference on Tri-Ada '89: Ada technology in context: application, development, and deployment
Structured analysis and object-oriented design are compatible
ACM SIGAda Ada Letters
Object-oriented modeling and design
Object-oriented modeling and design
Program design by informal English descriptions
Communications of the ACM
Software Engineering with ADA
Software Engineering Economics
Software Engineering Economics
Structured Analysis and System Specification
Structured Analysis and System Specification
Structured Development for Real-Time Systems
Structured Development for Real-Time Systems
Using object oriented structured development to implement a hybrid system
ACM SIGSOFT Software Engineering Notes
Active information systems, from object-oriented design to Ada 95
Proceedings of the conference on TRI-Ada '96: disciplined software development with Ada
Developer-assisted automation for Ada design generation
WADAS '92 Proceedings of the ninth Washington Ada symposium on Ada: Empowering software users and developers
| Hi-index | 0.00 |
Since its introduction in 1978, traditional Structured Analysis has been an industry standar d method for software requirements analysis that is supported by numerous CASE tools. Since their introduction in the early 1980s, various forms of Object-Oriented Development (OOD) have also become the preferred approach for the design and coding of Ada software. More recently, OOD has included various forms of Object-Oriented Requirements Analysis. OOD has therefor e come into direct competition with Structured Analysis. While some methodologists have advocated retaining Structured Analysis and have worked to merge the two paradigms, others have pointed out significant disadvantages of combining them and urge the use of a unifie d object-oriented paradigm throughout all development activities. A recent article published in Ada Letters by Ken Shumate [SH 1991] is illustrative of this controversy and has prompted this reply.It is the thesis of this paper that traditional Structured Analysis, even when modified for real-tim e systems, is a technically obsolete way to specify software requirements, and that Structure d Analysis and Object-Oriented Development are fundamentally incompatible and unnecessarily difficult for software engineers to combine effectively.