Object-oriented software engineering
Object-oriented software engineering
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Reusable software: the Base object-oriented component libraries
Reusable software: the Base object-oriented component libraries
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Testing object-oriented systems: models, patterns, and tools
Testing object-oriented systems: models, patterns, and tools
Generative programming: methods, tools, and applications
Generative programming: methods, tools, and applications
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Test Driven Development: By Example
Test Driven Development: By Example
A UML-Based Approach to System Testing
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Investigating the use of analysis contracts to improve the testability of object-oriented code
Software—Practice & Experience
Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
Learning UML 2.0
Generative hierarchical contracts for conformance testing of sequential containers
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Generative hierarchical contracts for conformance testing of sequential containers
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
| Hi-index | 0.00 |
Given that software offshore outsourcing is a business relationship, we assume that a contract is required in order to define what services are requested from a contracted entity and how these services are to be delivered to the satisfaction of the contractor. We first argue that, at the heart of the quality assurance facets of such a contract, we must find a single testable model of both the functional and nonfunctional requirements of the system to be delivered. We present the key properties that such a model must exhibit: testability, executability, scenarios as grammars of responsibilities, and support for abstraction. We then observe that, typically, existing approaches to requirements engineering do not offer such characteristics. We conclude by briefly discussing a prototype conformance testing environment that supports these properties.