Now showing items 31-40 of 165
Identifying duplicate functionality in textual use cases by aligning semantic actions
(Springer Heidelberg, 2016-05)
Developing high-quality requirements specifications often demands a thoughtful analysis and an adequate level of expertise from analysts. Although requirements modeling techniques provide mechanisms for abstraction and ...
Software Agents for Management Dynamic Inter-Organizational Collaborations
(Institute of Electrical and Electronics Engineers, 2014-02)
The globalization, modern markets, as well as new organizational management philosophies and advances in Information and Communications Technologies, encourage organizations to establish collaboration networks or ...
A dependable architecture for COTS-based software systems using protective wrappers
(Springer-verlag BerlinBerlinAlemanha, 2004)
Accelerating Engineering Software On Modern Multi-core Processors
(ELSEVIER SCI LTDOXFORD, 2015)
QuickFuzz testing for fun and profit
(Elsevier Science Inc, 2017-12)
Fuzzing is a popular technique to find flaws in programs using invalid or erroneous inputs but not without its drawbacks. At one hand, mutational fuzzers require a set of valid inputs as a starting point, in which modifications ...
Over the Air Download for Digital Television Receivers Upgrade
(IEEE-INST ELECTRICAL ELECTRONICS ENGINEERS INC, 2010)
Over the air download is an important feature for terrestrial digital television systems. It provides a cheaper option for DTV receiver manufacturers to provide bug fixes and quality improvements to their products, allowing ...
TACO: efficient SAT-based bounded verification using symmetry breaking and tight bounds
(IEEE Computer Society, 2013-03)
SAT-based bounded verification of annotated code consists of translating the code together with the annotations to a propositional formula, and analyzing the formula for specification violations using a SAT-solver. If a ...
Behaviour abstraction adequacy criteria for API call protocol testing
(John Wiley & Sons Ltd, 2016-05)
Code artefacts that have non-trivial requirements with respect to the ordering in which their methods or procedures ought to be called are common and appear, for instance, in the form of API implementations and objects. ...