IJPE 2017
DOI: 10.23940/ijpe.17.08.p2.11831194
|View full text |Cite
|
Sign up to set email alerts
|

Modeling and Optimizing CPS Software Testing based on Petri Nets

Abstract: Software testing is an important means to ensure the quality of software. However, there is a lack of effective modeling and optimization of CPS software testing. In this paper, Petri nets are used to model the underlying devices, components, connectors and test cases of CPS software. Aspect oriented programming extracts the crosscutting concerns of CPS software testing. The behaviors and their relationships are described based on AOP, and a weaving mechanism is used to dynamically integrate these models into … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2021
2021
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 18 publications
0
1
0
Order By: Relevance
“…At each level, they select some of the foregoing effectiveness and cost measures and combine them by assigning a weight to each metric. Weight-based search algorithms convert a multi-objective problem into a single objective function by assigning a particular weight to each optimization objective [115]. The objective of testing at the MiL level is testing functional requirements, so the authors choose fault detection capability, functional requirements coverage, pairwise functional requirements coverage and test execution time at this level.…”
Section: Model-based and Dynamic Test Case Selectionmentioning
confidence: 99%
“…At each level, they select some of the foregoing effectiveness and cost measures and combine them by assigning a weight to each metric. Weight-based search algorithms convert a multi-objective problem into a single objective function by assigning a particular weight to each optimization objective [115]. The objective of testing at the MiL level is testing functional requirements, so the authors choose fault detection capability, functional requirements coverage, pairwise functional requirements coverage and test execution time at this level.…”
Section: Model-based and Dynamic Test Case Selectionmentioning
confidence: 99%