Model-Based Software Component Testing: A UML-Based Approach Abstract: Applying UML modeling to both software component testing SCT and software component development enables testing and design phases to utilise a consistent specification approach to producing functional and reliable software components with better effectiveness and efficiency.
Following the proposed MBSCT framework for developing component test cases, the main task in the first phase is to build a set of UML-based test models, which is supported with the scenario-based component integration testing and test by contract techniques. The main task in the second phase is to design and generate component test cases from the constructed test models, which is supported with a component test mapping technique.
eramsonul.tk Component testing is a pretty vast topic in itself and equally complex. When I started reading this book I was a bit diffident about the coverage as well as the quality of the material.
Although in some cases the book does talk at a higher level rather than going into details, overall, Hans-Gerhard Gross has done a good job. The important thing to bear in mind is that this book is not for beginners.
PDF | Component-based software development regards software construction in terms of conventional engineering disciplines where the assembly of systems. Component-based software development regards software construction in terms of conventional engineering disciplines where the assembly of systems from.
The book is beautifully structured, crisp and methodical. In chapters 1 and 2, the author gives an insight in the world of component development as well as testing. While going through this section I felt that a few more details on component s would have been more helpful in understanding the later part of the book, especially for an amateur.
All because of a software exception which was caused through a conversion of a 64 bit floating value into a 16 bit integer value. Moving forward, the author explains component-based and model-driven development and testing with UML.
Each interface specification defines the details of its contract in terms of the operations it provides, what their signatures are, what effects they have on the parameters of the operations and the state of the component object, and under what conditions these effects are guaranteed. Component Object Architectures We hear a lot about component reuse in the press. The predictable consequence was the creation of systems that were delivered on time but with very poor structure, making them difficult and expensive to change and extend. An Interface Specification Diagram depicts an interface specification. If so, does the software need to know and how does it find out?
Chapters 3, 4 and 5 cover model-based testing with UML, Built-in contract testing and their implementation technologies. Chapters 6 and 7, talk about the use and reuse of contract testing artifacts, testing of product families and assessing the quality of service.