|3/2021 - 2|
Simple Framework for Efficient Development of the Functional Requirement Verification-specific LanguagePOPIC, S. , TESLIC, N. , BJELICA, M. Z.
|View the paper record and citations in|
|Click to see author's profile in SCOPUS, IEEE Xplore, Web of Science|
|Download PDF (1,990 KB) | Citation | Downloads: 810 | Views: 887|
computer languages, formal verification, formal languages, requirement engineering, programming environments
language(14), software(12), requirements(12), testing(8), specific(8), domain(8), systems(7), verification(6), formal(6), controlled(6)
Blue keywords are present in both the references section and the paper title.
About this article
Date of Publication: 2021-08-31
Volume 21, Issue 3, Year 2021, On page(s): 11 - 20
ISSN: 1582-7445, e-ISSN: 1844-7600
Digital Object Identifier: 10.4316/AECE.2021.03002
Web of Science Accession Number: 000691632000002
SCOPUS ID: 85115213462
This paper presents the framework for the creation of various domain-specific languages for verification of the functional requirements. When it comes to Requirement Engineering and the process of Validation and Verification of the requirements, there are plenty of tools for modeling, analyzing, and validating the requirements. It comes as a full-blown set of applications for validation of the requirements. But the set of the verification tools is either too complex or usable in a narrow domain. From the customers' point of view, there is a need for another independent requirement verification. This tool enables the creation of the custom verification in a way that allows users (either clients or developers) to verify requirements. It follows the IEEE guides, standards, and best practices to check all aspects of the software requirements that are neither implemented nor checked by the validation process: correctness, completeness, traceability, dependency, importance, and uniqueness. Tool implements design patterns specific to the verification process, thus enabling the faster implementation of the language. The concept can be used for development of the verification-specific language with any type of requirement representation, which will be shown by a few examples.
|References|||||Cited By «-- Click to see who has cited this paper|
| "IEEE Standard for System and Software Verification and Validation," in IEEE Std 1012-2012 (Revision of IEEE Std 1012-2004) , vol., no., pp.1-223, 25 May 2012, |
 "IEEE Draft Guide: Adoption of the Project Management Institute (PMI) Standard: A Guide to the Project Management Body of Knowledge (PMBOK Guide)-2008 (4th edition)," in IEEE P1490/D1, May 2011 , vol., no., pp. 1-505, 30 June 2011,
 B. Nuseibeh, and S. Easterbrook, "Requirements Engineering: A Roadmap," in Proc. of the Conf. on the Future of Software Engineering, Limerick, Ireland, 2000, pp. 35-46,
[CrossRef] [SCOPUS Times Cited 1358]
 A. Morkevicius and N. Jankevicius, "An approach: SysML-based automated requirements verification," 2015 IEEE Int. Symp. on Systems Engineering (ISSE), 2015, pp. 92-97,
[CrossRef] [SCOPUS Times Cited 14]
 "IEEE Recommended Practice for Software Requirements Specifications," in IEEE Std 830-1998, Reaffirmed 9-12-2009, vol., no., pp.1-40, 1998,
 L. Lengyel et al., "Quality Assured Model-Driven Requirements Engineering and Software Development," in The Computer Journal, vol. 58, no. 11, pp. 3171-3186, 2015,
[CrossRef] [Web of Science Times Cited 2] [SCOPUS Times Cited 3]
 Ralph Young, The Requirements Engineering Handbook, pp.130-150, Artech, 2003.
 P. Rempel and P. Mader, "A quality model for the systematic assessment of requirements traceability," 2015 IEEE 23rd Int. Requirements Engineering Conference (RE), 2015, pp. 176-185,
[CrossRef] [SCOPUS Times Cited 25]
 F. Wang et al., "An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models," in IEEE Transactions on Reliability, vol. 69, no. 1, pp. 154-173, 2020,
[CrossRef] [Web of Science Times Cited 10] [SCOPUS Times Cited 13]
 J. P. Tolvanen, S. Kelly, "How Domain-Specific Modeling Languages Address Variability in Product Line Development: Investigation of 23 Cases," 3rd Int. Systems and Software Product Line Conf. , 2019, pp. 155-163,
[CrossRef] [Web of Science Times Cited 1] [SCOPUS Times Cited 6]
 M. Fowler, "A Pedagogical Framework for Domain-Specific Languages," in IEEE Software, vol. 26, no. 4, pp. 13-14, 2009,
[CrossRef] [Web of Science Times Cited 9] [SCOPUS Times Cited 15]
 J.P. Tolvanen, S. Kelly, DOMAIN-SPECIFIC MODELING Enabling Full Code Generation, pp. 34-41, A Wiley-Interscience, 2008.
 D. Ghosh, DSLs in Action, Greenwich, pp. 220-300, Manning Co, 2011.
 "ITU-T, Recommendation Z.151 (10/18), User Requirements Notation (URN) - Language definition", pp.1-140, 2018.
 D. Amyot, L. Logrippo and M. Weiss, "Generation of test purposes from Use Case Maps," Computer Networks, vol. 49, no. 5, pp. 643-660, 2005,
[CrossRef] [Web of Science Times Cited 10] [SCOPUS Times Cited 22]
 D. de Almeida Ferreira and A. R. da Silva, "RSLingo: An information extraction approach toward formal requirements specifications," 2012 Second IEEE International Workshop on Model-Driven Requirements Engineering (MoDRE), 2012, pp. 39-48,
[CrossRef] [SCOPUS Times Cited 33]
 N. A. Ali, A. A. Mirghani and A. Y. Ibrahim, "Alneelain: A formal specification language," 2017 International Conference on Communication, Control, Computing and Electronics Engineering (ICCCCEE) , 2017, pp. 1-9,
[CrossRef] [SCOPUS Times Cited 1]
 A. Mili and F. Tchier, Software Testing, concepts and operations, pp. 38-39, Wiley, 2015.
 L. C. Hong and L. T. Ming, "To enable formal verification of semi-formal requirements by using pre-defined template and mapping rules to map to Promela specification to reduce rework," 2010 Int. Symposium on Information Technology, 2010, pp. 1393-1397,
[CrossRef] [SCOPUS Times Cited 1]
 P. H. Feiler, B. A. Lewis and S. Vestal, "The SAE Architecture Analysis & Design Language (AADL) a standard for engineering performance critical systems," IEEE Conference on Computer Aided Control System Design, 2006, pp. 1206-1211,
 Z.-B.Yang et al., "From AADL to timed abstract state machines: A verified model transformation," Journal of Systems and Software, vol. 93, pp. 42-68, 2014,
[CrossRef] [Web of Science Times Cited 30] [SCOPUS Times Cited 47]
 G. Behrmann, A. David, K. G. Larsen, "A tutorial on Uppaal," in Formal Methods for the Design of Real-Time Systems, Berlin, Germany: Springer, vol.3185, pp. 200-236, 2004,
[CrossRef] [SCOPUS Times Cited 1130]
 D. Cofer, et al., "Compositional verification of architectural models," in NASA Formal Methods, vol. 7226, pp. 126-140, 2012,
[CrossRef] [SCOPUS Times Cited 81]
 G. Sutcliffe and C. Suttner, "The TPTP Problem Library," Journal of Automated Reasoning, vol. 21, pp. 177-203, 1998,
[CrossRef] [Web of Science Times Cited 140] [SCOPUS Times Cited 200]
 Z. Zuo and M. Zhou, "Web Ontology Language OWL and its description logic foundation," Proc. of the Fourth Int. Conference on Parallel and Distributed Computing, Applications and Technologies, 2003, pp. 157-160,
[CrossRef] [Web of Science Times Cited 11]
 C. -. Liu, K. -. Chang, J. J. -. Chen and S. -. Hung, "Ontology-Based Context Representation and Reasoning Using OWL and SWRL," 2010 8th Annual Communication Networks and Services Research Conference, 2010, pp. 215-220,
[CrossRef] [SCOPUS Times Cited 28]
 N. E. Fuch, "First-Order Reasoning for Attempto Controlled English," Int. Workshop on Controlled Natural Language, CNL 2010: Controlled Natural Language, Springer-Verlag Berlin, 2012, pp. 73 - 94,
[CrossRef] [SCOPUS Times Cited 11]
 P. Clark, W. R. Murray, P. Harrison, and J. Thompson, "Naturalness vs. Predictability: A Key Debate in Controlled Languages". Controlled Natural Language: Proc. of the Work. on Controlled Natural Language, 2009, vol. 5972, pp. 65-81,
[CrossRef] [SCOPUS Times Cited 25]
 S. Thummalapenta, S. Sinha, N. Singhania and S. Chandra, "Automating test automation," 2012 34th International Conference on Software Engineering, 2012, pp. 881-891,
[CrossRef] [SCOPUS Times Cited 53]
 A. Miller, B. Kumar and A. Singhal, "Photon: A Domain-Specific Language for Testing Converged Applications," 33rd Annual IEEE International Computer Software and Applications Conference, 2009, vol. 2, pp. 269-274,
[CrossRef] [SCOPUS Times Cited 2]
 M. Bernardino, A. F. Zorzo and E. M. Rodrigues, "Canopus: A Domain-Specific Language for Modeling Performance Testing," 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST), 2016, pp. 157-167,
[CrossRef] [Web of Science Times Cited 13] [SCOPUS Times Cited 15]
 S. Pakin, "The Design and Implementation of a Domain-Specific Language for Network Performance Testing," in IEEE Trans. on Parallel and Distributed Systems, vol. 18, no. 10, pp. 1436-1449, 2007,
[CrossRef] [Web of Science Times Cited 22] [SCOPUS Times Cited 29]
 A. Dwarakanath, D. Era, A. Priyadarshi, N. Dubash and S. Podder, "Accelerating Test Automation through a Domain Specific Language," 2017 IEEE Int. Conf. on Software Testing, Verification and Validation, 2017, pp. 460-467,
[CrossRef] [Web of Science Times Cited 4] [SCOPUS Times Cited 4]
 C. Willcock, T. Deis, S. Tobies, S. Keil, F. Engler, S. Schulz, A. Wiles, "Basic TTCN-3," in An Introduction to TTCN-3, Wiley, 2010, pp.25-44,
 A. A. Giordano, A. H. Levesque, "Getting Started with Simulink," in Modeling of Digital Communication Systems Using SIMULINK, Wiley, 2015, pp.1-26,
 S. Popic, V. Komadina, R. Arsenovic and M. Stepanovic, "Implementation of the simple domain-specific language for system testing in V-Model development lifecycle," 2020 Zooming Innovation in Consumer Technologies Conference, 2020, pp. 290-294,
[CrossRef] [Web of Science Times Cited 1] [SCOPUS Times Cited 1]
 S. Popic, B. Pavkovic, I. Velikic and N. Teslic, "Data generators: a short survey of techniques and use cases with focus on testing," 2019 IEEE 9th Int. Conf. on Consumer Electronics (ICCE-Berlin), 2019, pp. 189-194,
[CrossRef] [Web of Science Times Cited 14] [SCOPUS Times Cited 15]
Web of Science® Citations for all references: 267 TCR
SCOPUS® Citations for all references: 3,132 TCR
Web of Science® Average Citations per reference: 7 ACR
SCOPUS® Average Citations per reference: 82 ACR
TCR = Total Citations for References / ACR = Average Citations per Reference
We introduced in 2010 - for the first time in scientific publishing, the term "References Weight", as a quantitative indication of the quality ... Read more
Citations for references updated on 2023-09-19 20:18 in 183 seconds.
Note1: Web of Science® is a registered trademark of Clarivate Analytics.
Note2: SCOPUS® is a registered trademark of Elsevier B.V.
Disclaimer: All queries to the respective databases were made by using the DOI record of every reference (where available). Due to technical problems beyond our control, the information is not always accurate. Please use the CrossRef link to visit the respective publisher site.
Faculty of Electrical Engineering and Computer Science
Stefan cel Mare University of Suceava, Romania
All rights reserved: Advances in Electrical and Computer Engineering is a registered trademark of the Stefan cel Mare University of Suceava. No part of this publication may be reproduced, stored in a retrieval system, photocopied, recorded or archived, without the written permission from the Editor. When authors submit their papers for publication, they agree that the copyright for their article be transferred to the Faculty of Electrical Engineering and Computer Science, Stefan cel Mare University of Suceava, Romania, if and only if the articles are accepted for publication. The copyright covers the exclusive rights to reproduce and distribute the article, including reprints and translations.
Permission for other use: The copyright owner's consent does not extend to copying for general distribution, for promotion, for creating new works, or for resale. Specific written permission must be obtained from the Editor for such copying. Direct linking to files hosted on this website is strictly prohibited.
Disclaimer: Whilst every effort is made by the publishers and editorial board to see that no inaccurate or misleading data, opinions or statements appear in this journal, they wish to make it clear that all information and opinions formulated in the articles, as well as linguistic accuracy, are the sole responsibility of the author.