A Tool for Supporting Requirements Formalization Based on Specification Pattern Knowledge

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

Despite the effectiveness of requirements formalization in producing accurate requirements documentation, this technique can hardly be accepted by software industry mainly due to the difficulty in manipulating formal notations by practitioners. To handle the challenge, this paper describes an interactive tool for supporting requirements formalization based on specification pattern knowledge comprising a set of inter-related specification patterns. Each pattern defines the knowledge for formalizing one kind of function, including derivation knowledge for guiding the clarification of the function and transformation knowledge for formally representing the clarified function. The tool derives necessary function details of the intended requirement through interactions by applying the derivation knowledge and transforms these details into formal specifications by applying the transformation knowledge.

Original languageEnglish
Title of host publicationProceedings - 2015 International Symposium on Theoretical Aspects of Software Engineering, TASE 2015
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages127-130
Number of pages4
ISBN (Electronic)9781467376129
DOIs
StatePublished - 26 Oct 2015
Externally publishedYes
EventInternational Symposium on Theoretical Aspects of Software Engineering, TASE 2015 - Nanjing, China
Duration: 12 Sep 201514 Sep 2015

Publication series

NameProceedings - 2015 International Symposium on Theoretical Aspects of Software Engineering, TASE 2015

Conference

ConferenceInternational Symposium on Theoretical Aspects of Software Engineering, TASE 2015
Country/TerritoryChina
CityNanjing
Period12/09/1514/09/15

Fingerprint

Dive into the research topics of 'A Tool for Supporting Requirements Formalization Based on Specification Pattern Knowledge'. Together they form a unique fingerprint.

Cite this