Designing object-oriented software
Designing object-oriented software
An introduction to object-oriented programming
An introduction to object-oriented programming
Object-oriented software engineering: the professional developer's guide
Object-oriented software engineering: the professional developer's guide
Real-time object-oriented modeling
Real-time object-oriented modeling
Reusable software: the Base object-oriented component libraries
Reusable software: the Base object-oriented component libraries
Mastering object-oriented design in C++
Mastering object-oriented design in C++
Developing an object-oriented software testing and maintenance environment
Communications of the ACM - Special issue on object-oriented experiences and future trends
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design
FASE '01 Proceedings of the 4th International Conference on Fundamental Approaches to Software Engineering
ACS'08 Proceedings of the 8th conference on Applied computer scince
Proceedings of the 5th ACM international conference on Distributed event-based system
A formal scheme for systematic translation of software requirements to source code
ACC'11/MMACTEE'11 Proceedings of the 13th IASME/WSEAS international conference on Mathematical Methods and Computational Techniques in Electrical Engineering conference on Applied Computing
Traceability between service component and class: a model based approach
ACM SIGSOFT Software Engineering Notes
Hi-index | 4.10 |
Object-oriented software development has become popular, but scaling it up for large projects has been a problem. With large OO projects, late integration problems are a particular concern. They can cause schedule slippage and other difficulties. I developed a process called Traceability for OO Quality Engineering, or TOOQE, to minimize such problems. TOOQE emphasizes traceability and the integration of development and testing to achieve quality and maintainability. TOOQE features an iterative design process that lets developers correct mistakes and learn more about the problem they are trying to solve as they go along. Each iteration includes requirements capture, analysis, design, coding, and testing. In other words, each is a mini-life cycle. TOOQE's approach is also incremental. This lets each iteration build on its predecessor and eliminates the need to retest functionality at each iteration. Integration does not occur late in the process in TOOQE but instead occurs at each iteration. Moreover, integration entails immediate testing of the integrated artifacts, thus providing early and continuous feedback. For object-oriented analysis and design, you use three views of the system. The expression of each view requires at least one model, so OOA and OOD lead to the production of several models.