1,060 research outputs found
Colored model based testing for software product lines (CMBT-SWPL)
Over the last decade, the software product line domain has emerged as
one of the mostpromising software development paradigms. The main beneļ¬ts
of a software product lineapproach are improvements in productivity, time
to market, product quality, and customersatisfaction.Therefore, one topic
that needs greater emphasis is testing of software product lines toachieve
the required software quality assurance. Our concern is how to test a
softwareproduct line as early as possible in order to detect errors,
because the cost of error detectedIn early phases is much less compared to
the cost of errors when detected later.The method suggested in this thesis
is a model-based, reuse-oriented test technique calledColored Model Based
Testing for Software Product Lines (CMBT-SWPL). CMBT-SWPLis a
requirements-based approach for eļ¬ciently generating tests for products
in a soft-ware product line. This testing approach is used for validation
and veriļ¬cation of productlines. It is a novel approach to test product
lines using a Colored State Chart (CSC), whichconsiders variability early
in the product line development process. More precisely, the vari-ability
will be introduced in the main components of the CSC. Accordingly, the
variabilityis preserved in test cases, as they are generated from colored
test models automatically.During domain engineering, the CSC is derived
from the feature model. By coloring theState Chart, the behavior of
several product line variants can be modeled simultaneouslyin a single
diagram and thus address product line variability early. The CSC
representsthe test model, from which test cases using statistical testing
are derived.During application engineering, these colored test models are
customized for a speciļ¬capplication of the product line. At the end of
this test process, the test cases are generatedagain using statistical
testing, executed and the test results are ready for evaluation.
Inxaddition, the CSC will be transformed to a Colored Petri Net (CPN) for
veriļ¬cation andsimulation purposes.The main gains of applying the
CMBT-SWPL method are early detection of defects inrequirements, such as
ambiguities incompleteness and redundancy which is then reļ¬ectedin saving
the test eļ¬ort, time, development and maintenance costs
Modal Object Diagrams
While object diagrams (ODs) are widely used as a means to document
object-oriented systems, they are expressively weak, as they are limited to
describe specific possible snapshots of the system at hand. In this paper we
introduce modal object diagrams (MODs), which extend the classical OD language
with positive/negative and example/invariant modalities. The extended language
allows the designer to specify not only positive example models but also
negative examples, ones that the system should not allow, positive invariants,
ones that all system's snapshots should include, and negative invariants, ones
that no system snapshot is allowed to include. Moreover, as a primary
application of the extended language we provide a formal verification technique
that decides whether a given class diagram satisfies (i.e., models) a
multi-modal object diagrams specification. In case of a negative answer, the
technique outputs relevant counterexample object models, as applicable. The
verification is based on a reduction to Alloy. The ideas are implemented in a
prototype Eclipse plug-in. Examples show the usefulness of the extended
language in specifying structural requirements of object-oriented systems in an
intuitive yet expressive way.Comment: 25 pages, 9 figure
A use case driven approach for system level testing
Use case scenarios are created during the analysis phase to specify software
system requirements and can also be used for creating system level test cases.
Using use cases to get system tests has several benefits including test design
at early stages of software development life cycle that reduces over all
development cost of the system. Current approaches for system testing using use
cases involve functional details and does not include guards as passing
criteria i.e. use of class diagram that seem to be difficult at very initial
level which lead the need of specification based testing without involving
functional details. In this paper, we proposed a technique for system testing
directly derived from the specification without involving functional details.
We utilize initial and post conditions applied as guards at each level of the
use cases that enables us generation of formalized test cases and makes it
possible to generate test cases for each flow of the system. We used use case
scenarios to generate system level test cases, whereas system sequence diagram
is being used to bridge the gap between the test objective and test cases,
derived from the specification of the system. Since, a state chart derived from
the combination of sequence diagrams can model the entire behavior of the
system.Generated test cases can be employed and executed to state chart in
order to capture behavior of the system with the state change.All these steps
enable us to systematically refine the specification to achieve the goals of
system testing at early development stages
Architecting Secure Software Systems Using an Aspect-Oriented Approach: : A Survey of Current Research
The importance of security in the development of complex software systems has increasingly become more critical as software becomes increasingly more pervasive in our everyday lives. Aspect-orientation has been proposed as a means to handle the crosscutting nature of security requirements when developing, designing and implementing security-critical applications. This paper surveys some of the approaches and contributions of integrating an aspect-oriented approach into designing and implementing secure software systems
BORM - Business Object Relation Modeling
BORM is an object-oriented and process-based analysis and design methodology, which has proved to be effective in the development of business systems. The effectiveness gained is largely due to an unified and simple method for presenting necessary aspects of the relevant business model, which can be simulated, verified and validated for subsequent software implementation. The BORM methodology makes extensive use of business process modeling towards the area of software engineering. This paper outlines BORM and presents it on an application example created in Craft.CASE analysis and modeling tool
Executable system architecting using systems modeling language in conjunction with Colored Petri Nets - a demonstration using the GEOSS network centric system
Models and simulation furnish abstractions to manage complexities allowing engineers to visualize the proposed system and to analyze and validate system behavior before constructing it. Unified Modeling Language (UML) and its systems engineering extension, Systems Modeling Language (SysML), provide a rich set of diagrams for systems specification. However, the lack of executable semantics of such notations limits the capability of analyzing and verifying defined specifications. This research has developed an executable system architecting framework based on SysML-CPN transformation, which introduces dynamic model analysis into SysML modeling by mapping SysML notations to Colored Petri Net (CPN), a graphical language for system design, specification, simulation, and verification. A graphic user interface was also integrated into the CPN model to enhance the model-based simulation. A set of methodologies has been developed to achieve this framework. The aim is to investigate system wide properties of the proposed system, which in turn provides a basis for system reconfiguration --Abstract, page iii
- ā¦