Structured analysis—formal design, using stream and object oriented formal specifications
Conference proceedings on Formal methods in software development
Biblio of object-oriented system development
ACM SIGSOFT Software Engineering Notes
The method won't save you: (but it can help)
ACM SIGSOFT Software Engineering Notes
Using object oriented structured development to implement a hybrid system
ACM SIGSOFT Software Engineering Notes
PATHOS—a paradigmatic approach to high-level object-oriented software development
ACM SIGSOFT Software Engineering Notes
Splitting the Difference: The Historical Necessity of Synthesis in Software Engineering
IEEE Annals of the History of Computing
A Parallelizing Compiler by Object Oriented Design
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
Experience with Porting a Unix Version CASE Tool to the Corresponding Java Version
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
Requirements engineering process improvement: an industrial case study
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
| Hi-index | 0.00 |
The significance of "object-oriented" as a development method, and the current confusion over the term are addressed. A set of characteristics is proposed as a basis for agreement on a definition of the term. Object-oriented development is compared to the "structured techniques," and work in progress on integrating the two methods is reviewed. Practical recommendations on assessing the importance of object-oriented development are given.