Relevant bibliographies by topics / Requirements Specification Language

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Requirements Specification Language'

Author: Grafiati
Published: 4 June 2021
Last updated: 13 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Requirements Specification Language.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Requirements Specification Language"

1

KÖRNER, SVEN J., and TORBEN BRUMM. "NATURAL LANGUAGE SPECIFICATION IMPROVEMENT WITH ONTOLOGIES." International Journal of Semantic Computing 03, no. 04 (December 2009): 445–70. http://dx.doi.org/10.1142/s1793351x09000872.

Full text
Abstract:
Requirements engineering can solve and cause many problems in a software development cycle. The difficulties in understanding and eliciting the desired functionality from the customer and then delivering the correct implementation of a software system lead to delays, mistakes, and high costs. Working with requirements means handling incomplete or faulty textual specifications. It is vital for a project to fully understand the purpose and the functionality of a software. The earlier specifications are corrected and improved, the better. We created a tool called RESI to support requirement analysts working with textual specifications. RESI checks for linguistic defects [1, 2] in specifications and offers a dialog-system which makes suggestions to improve the text. It points out to the user which parts of the specification are ambiguous, faulty or inaccurate and therefore need to be changed. For this task, RESI needs additional semantic information which is inherent to natural language specifications. It receives this information by utilizing ontologies.
APA, Harvard, Vancouver, ISO, and other styles
2

Chen, Shu, and Ming Kai Chen. "A Semantical Approach for Automatically Transforming Software Requirement Specification into Formal Presentation." Advanced Materials Research 225-226 (April 2011): 776–79. http://dx.doi.org/10.4028/www.scientific.net/amr.225-226.776.

Full text
Abstract:
Software engineering is a critical step in obtaining high quality production. However, requirement specifications that written in natural language is inevitably has ambiguity. Modern driven architecture makes use of requirement model for the complement of requirement specification to eliminate such ambiguity. However, currently, the transformation from requirement specification into formal model only limited in syntax level, thus lack of correctness and precision. This paper proposed an approach in semantical level to process textual specifications of the requirements of unlimited natural language and their automatic mapping to the formal presentation.
APA, Harvard, Vancouver, ISO, and other styles
3

ACHEE, B. L., and DORIS L. CARVER. "OBJECT EXTENSIONS TO Z: A SURVEY." International Journal of Software Engineering and Knowledge Engineering 06, no. 03 (September 1996): 507–30. http://dx.doi.org/10.1142/s0218194096000211.

Full text
Abstract:
Formal specification languages provide assistance to solving the problem of high maintenance costs caused by ineffective communication of a system’s requirements. Using a sound mathematical basis, a formal specification language provides a precise and definitive system description that can serve as a binding contract. Additionally, the integration of the object-oriented paradigm with a formal specification language provides increased potential for software reuse, conceptually cleaner specifications and a framework for defining interfaces. To this end, there has been significant work done to extend existing specification languages to allow object-oriented specifications. This paper provides a comparison of such object-oriented specification languages, specifically, those extending Z. The paper is organized into five major sections. After a brief introduction to the concepts of formal specification languages and Z, a simple library system is defined and used as an example throughout the paper. Each of the object-oriented specification languages is introduced and classified as either using Z in an object-oriented style or providing a true object-oriented extension of Z. For each language, the specification of the example library system is presented following a brief overview of the language’s features. An in-depth comparison is made of each of the languages which provide a true object-oriented extension of Z.
APA, Harvard, Vancouver, ISO, and other styles
4

Mohd, Haslina, Fauziah Baharom, Norida Muhd Darus, Shafinah Farvin Packeer Mohamed, Zaharin Marzuki, and Muhammad Afdhal Muhammad Robie. "Functional Requirements Specification of E-Tendering Using Natural Language Approach: Towards Innovative Business Transformation." Journal of Computational and Theoretical Nanoscience 16, no. 12 (December 1, 2019): 5003–7. http://dx.doi.org/10.1166/jctn.2019.8555.

Full text
Abstract:
Recently, business transformation towards the used of Information and Communication Technology (ICT) is a necessity toward rapid industries and the paradigm shifted to sustain business competitiveness. The holistic electronic approach is one of business innovations, especially in handling a lot of tender documentations and process in an electronic environment namely as e-Tendering. Unfortunately, the existing tender process transformation in the electronic approach is not properly followed certain standard and guideline, especially in establishing a good e-Tendering functional requirements specification to ensure the organizations would be in the best served. This is important to ensure a good e-Tendering system can be developed by e-Tendering developers based on a good e-Tendering functional requirement specifications. The requirements specification is a process of documenting user and system requirements. Commonly, user and system requirements should be clear, unambiguous, easy to understand, complete, and consistent. In practice, this is difficult to achieve due to interpretation of the requirements in different ways by stakeholders, which are often inherent conflicts and inconsistencies of the requirements. The implementation of the existing e-tendering still remains uncertainties, especially in defining the functional requirements of the e-tendering system. Therefore, this study aims to construct the e-Tendering functional requirement model using requirement template in natural language representation approach. Moreover the development of this system requirement model may provide a consistency to the requirements representation. The study uses UN/CEFACT Business Standard of the e-Tendering Business. The identified functional requirements are designed by using Requirement Template to ensure the reliability and understandability of requirements. Besides, the proposed functional requirements is constructed by adapting the natural language and verified by expert review approaches. As a result, this study proposed a functional requirements specification of the e-Tendering that contains detailed description which can be referred by software practitioners in developing a secure e-tendering system effectively.
APA, Harvard, Vancouver, ISO, and other styles
5

Mahalakshmi, K., Udayakumar Allimuthu, L. Jayakumar, and Ankur Dumka. "A Timeline Optimization Approach of Green Requirement Engineering Framework for Efficient Categorized Natural Language Documents in Non-Functional Requirements." International Journal of Business Analytics 8, no. 1 (January 2021): 21–37. http://dx.doi.org/10.4018/ijban.2021010102.

Full text
Abstract:
The system's functional requirements (FR) and non-functional requirements (NFR) are derived from the software requirements specification (SRS). The requirement specification is challenging in classification process of FR and NFR requirements. To overcome these issues, the work contains various significant contributions towards SRS, such as green requirements engineering (GRE), to achieve the natural language processing, requirement specification, extraction, classification, requirement specification, feature selection, and testing the quality attributes improvement of NFRs. In addition to this, the test pad-based quality study to determine accuracy, quality, and condition providence to the classification of non-functional requirements (NFR) is also carried out. The resulted classification accuracy was implemented in the MATLAB R2014; the resulted graphical record shows the efficient non-functional requirements (NFR) classification with green requirements engineering (GRE) framework.
APA, Harvard, Vancouver, ISO, and other styles
6

Fuchs, Norbert E., and David Robertson. "Declarative specifications." Knowledge Engineering Review 11, no. 4 (December 1996): 317–31. http://dx.doi.org/10.1017/s0269888900008018.

Full text
Abstract:
AbstractDeriving formal specifications from informal requirements is extremely difficult since one has to overcome the conceptual gap between an application domain and the domain of formal specification methods. To reduce this gap we introduce application-specific specification languages, i.e., graphical and textual notations that can be unambiguously mapped to formal specifications in a logic language. We describe a number of realised approaches based on this idea, and evaluate them with respect to their domain specificity vs. generality.
APA, Harvard, Vancouver, ISO, and other styles
7

Phuoc, Ton Long. "MODEL CHECKING EARLY REQUIREMENTS SPECIFICATIONS IN ALLOY." Vietnam Journal of Science and Technology 54, no. 3A (March 20, 2018): 163. http://dx.doi.org/10.15625/2525-2518/54/3a/11968.

Full text
Abstract:
Automation generated source code and verifying are essential sector for software engineering. There are many ways to generate source code and verify from the specification languages. In this paper, we propose an approach that automatically generated code from a specification language Alloy. From this specification language, we will describe how to translate from one language to the Java source. An application in this paper is a gardening game program. Applied after the findings will be organized according to the MVC (Model-View-Controller) architectural pattern. Besides, we will also verify the identity of the structure of the application and the content of the Alloy specification. We built an tool as GmDSL, we have verified the aplication in GmDSL. The application was created from the tool also shows the correctness of the early constraints. Simultaneously, we also compares be verified through the GmDSL tool with NuSVM tool.
APA, Harvard, Vancouver, ISO, and other styles
8

Mauw, S., and G. J. Veltink. "A Process Specification Formalism1." Fundamenta Informaticae 13, no. 2 (April 1, 1990): 85–139. http://dx.doi.org/10.3233/fi-1990-13202.

Full text
Abstract:
Traditional methods for programming sequential machines are inadequate for specifying parallel systems. Because debugging of parallel programs is hard, due to e.g. non-deterministic execution, verification of program correctness becomes an even more important issue. The Algebra of Communicating Processes (ACP) is a formal theory which emphasizes verification and can be applied to a large domain of problems ranging from electronic circuits to CAM architectures. The manual verification of specifications of small size has already been achieved, but this cannot easily be extended to the verification of larger industrially relevant systems. To deal with this problem we need computer tools to help with the specification, simulation, verification and implementation. The first requirement for building such a set of tools is a specification language. In this paper we introduce PSFd (Process Specification Formalism – draft) which can be used to formally express processes in ACP. In order to meet the modern requirements of software engineering, like reusability of software, PSFd supports the modular construction of specifications and parameterization of modules. To be able to deal with the notion of data, ASF (Algebraic Specification Formalism) is embedded in our formalism. As semantics for PSFd a combination of initial algebra semantics and operational semantics for concurrent processes is used. A comparison with programming languages and other formal description techniques for the specification of concurrent systems is included.
APA, Harvard, Vancouver, ISO, and other styles
9

COOKE, DANIEL E., and ANN GATES. "ON THE DEVELOPMENT OF A METHOD TO SYNTHESIZE PROGRAMS FROM REQUIREMENTS SPECIFICATIONS." International Journal of Software Engineering and Knowledge Engineering 01, no. 01 (March 1991): 21–38. http://dx.doi.org/10.1142/s0218194091000056.

Full text
Abstract:
This paper reviews the progress that has been made towards the definition of a new generation of computer assisted problem solving tool. When we solve problems with a computer we state the solution in terms of several languages, beginning with a requirements specification language and ending with a program. Beginning with a generalization of a programming language, this paper follows steps towards the removal of control and data structure information in a problem solution. The effort discussed here would result in the requirements specification language being the final language used in problem solving.
APA, Harvard, Vancouver, ISO, and other styles
10

Nowakowski, Wiktor, Michał Śmiałek, Albert Ambroziewicz, and Tomasz Straszak. "Requirements-level language and tools for capturing software system essence." Computer Science and Information Systems 10, no. 4 (2013): 1499–524. http://dx.doi.org/10.2298/csis121210062n.

Full text
Abstract:
Creation of an unambiguous requirements specification with precise domain vocabulary is crucial for capturing the essence of any software system, either when developing a new system or when recovering knowledge from a legacy one. Software specifications usually maintain noun notions and include them in central vocabularies. Verb or adjective phrases are easily forgotten and their definitions buried inside imprecise paragraphs of text. This paper proposes a model-based language for comprehensive treatment of domain knowledge, expressed through constrained natural language phrases that are grouped by nouns and include verbs, adjectives and prepositions. In this language, vocabularies can be formulated to describe behavioural characteristics of a given problem domain. What is important, these characteristics can be linked from within other specifications similarly to a wiki. The application logic can be formulated through sequences of imperative subject-predicate sentences containing only links to the phrases in the vocabulary. The paper presents an advanced tooling framework to capture application logic specifications making them available for automated transformations down to code. The tools were validated through a controlled experiment.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Requirements Specification Language"

1

Thongglin, Kanjana. "Controlled language for Thai software requirements specification." Thesis, Besançon, 2014. http://www.theses.fr/2014BESA1003.

Full text
Abstract:
Cette thèse porte sur l’utilisation d’une langue contrôlée pour les spécifications des besoins du logiciel en thaï. L’étudedécrit les ambiguïtés syntaxiques et sémantiques ainsi que les problèmes rencontrés dans les spécifications des besoins dulogiciel en thaï. Ce travail explique également la nature de la langue thaïe. Le modèle de la langue contrôlée pour lesspécifications des besoins du logiciel en thaï, proposé dans cette étude, comprend trois composantes: l’analyse lexicale,l’analyse syntaxique et l’analyse sémantique. Pour l’analyse syntaxique, une syntaxe contrôlée est conçue en utilisant laforme du Backus-Naur (BNF). Quant à l’analyse lexicale, nous créons une ressource lexicale sous forme de langage XMLpour stocker tous les mots classés selon leur domaine. Les mots reçus de la ressource XML sont corrects d’un point de vueconceptuel mais ne sont pas pertinents d’un point de vue sémantique. Pour résoudre ce problème, nous faisons alors usage dematrices booléennes pour aligner les phrases sémantiquement. Ainsi les phrases produites par le modèle serontsyntaxiquement et sémantiquement correctes.Après avoir créé le modèle, nous avons construit un logiciel pour tester son efficacité. Il est ainsi évalué par quatreméthodes d’évaluation : 1. le test de fonctionnement syntaxique pour vérifier la syntaxe de la phrase; 2. le test defonctionnement sémantique pour tester la sémantique de la phrase; 3. le test d’acceptation en terme de satisfaction desutilisateurs avec le logiciel; et 4. le test d’acceptation en terme d’acception des données de sortie.Des résultats positifs montrent que : 1. les phrases produites par le modèle proposé sont syntaxiquement correctes; 2. lesphrases produites par le modèle proposé sont sémantiquement correctes; 3. les utilisateurs sont satisfaits et acceptent lelogiciel; et 4. les utilisateurs acceptent et comprennent les phrases produites par ce modèle
This thesis focuses on using controlled language for Thai software requirements specifications. The studydescribes the ambiguities and problems encountered in Thai software requirements specifications; both syntacticambiguity and semantic ambiguity. The study also describes the nature of the Thai language. The model of controlledlanguage for Thai software requirements specifications is composed of three main components: lexical analysis,syntactic analysis, and semantic analysis. For syntactic analysis, a controlled syntax is created using Backus-NaurForm (BNF). In the lexical analysis stage, an XML format lexical resource is built to store words according to theirdomain. The words received from the XML resource are conceptually correct but may be semantically irrelevant. Tosolve this issue, the model applies Boolean Matrices to align sentences semantically. As a result, the sentencesproduced from the model are guaranteed to be syntactically and semantically correct.After having created this model, a program for testing the efficiency of the model is developed. The model isevaluated using four testing methods as follows: 1. functional testing for the correctness of the sentence’s syntax, 2.functional testing for the semantic correctness of the sentences produced by the model, 3. acceptance testing in termsof user satisfaction with the program, and 4. acceptance testing in terms of the validity of the outputs.The positive results signify that: 1. the sentences produced by the proposed model are syntactically correct, 2. thesentences produced by the proposed model are semantically correct, 3. the users are satisfied and accept the softwarecreated, and 4. the users approve and understand the sentences produced from this model
APA, Harvard, Vancouver, ISO, and other styles
2

Sidky, Ahmed Samy. "RGML: A Specification Language that Supports the Characterization of Requirements Generation Processes." Thesis, Virginia Tech, 2003. http://hdl.handle.net/10919/34237.

Full text
Abstract:
Despite advancements in requirements generation models, methods and tools, low quality requirements are still being produced. One potential avenue for addressing this problem is to provide the requirements engineer with an interactive environment that leads (or guides) him/her through a structured set of integrated activities that foster "good" quality requirements. While that is our ultimate goal, a necessary first step in developing such an environment is to create a formal specification mechanism for characterizing the structure, process flow and activities inherent to the requirements generation process. In turn, such specifications can serve as a basis for developing an interactive environment supporting requirements engineering. Reflecting the above need, we have developed a markup language, the Requirements Generation Markup Language (RGML), which can be used to characterize a requirements generation process. The RGML can describe process structure, flow of control, and individual activities. Within activities, the RGML supports the characterization of application instantiation, the use of templates and the production of artifacts. The RGML can also describe temporal control within a process as well as conditional expressions that control if and when various activity scenarios will be executed. The language is expressively powerful, yet flexible in its characterization capabilities, and thereby, provides the capability to describe a wide spectrum of different requirements generation processes.
Master of Science
APA, Harvard, Vancouver, ISO, and other styles
3

Lai, Danny Cho-Liang 1978. "Extending a formal specification & requirements language : a case study." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/86814.

Full text
Abstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.
Includes bibliographical references (leaves 92-93).
by Danny Cho-Liang Lai.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
4

Pong, Lih, and 龐立. "Formal data flow diagrams (FDFD): a petri-netbased requirements specification language." Thesis, The University of Hong Kong (Pokfulam, Hong Kong), 1985. http://hub.hku.hk/bib/B31207406.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Pong, Lih. "Formal data flow diagrams (FDFD) : a petri-net based requirements specification language /." [Hong Kong : University of Hong Kong], 1985. http://sunzi.lib.hku.hk/hkuto/record.jsp?B12323019.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sutherland, Sean J. P. (Sean Jason Perry) 1977. "A demonstration of a formal specification & requirements language : a case study." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/86852.

Full text
Abstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.
Includes bibliographical references (p. 109,111 [p. 110 intentionally blank]).
by Sean J.P. Sutherland.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
7

Dhar, Siddharth. "Optimizing TEE Protection by Automatically Augmenting Requirements Specifications." Thesis, Virginia Tech, 2020. http://hdl.handle.net/10919/98730.

Full text
Abstract:
An increasing number of software systems must safeguard their confidential data and code, referred to as critical program information (CPI). Such safeguarding is commonly accomplished by isolating CPI in a trusted execution environment (TEE), with the isolated CPI becoming a trusted computing base (TCB). TEE protection incurs heavy performance costs, as TEE-based functionality is expensive to both invoke and execute. Despite these costs, projects that use TEEs tend to have unnecessarily large TCBs. As based on our analysis, developers often put code and data into TEE for convenience rather than protection reasons, thus not only compromising performance but also reducing the effectiveness of TEE protection. In order for TEEs to provide maximum benefits for protecting CPI, their usage must be systematically incorporated into the entire software engineering process, starting from Requirements Engineering. To address this problem, we present a novel approach that incorporates TEEs in the Requirements Engineering phase by using natural language processing (NLP) to classify those software requirements that are security critical and should be isolated in TEE. Our approach takes as input a requirements specification and outputs a list of annotated software requirements. The annotations recommend to the developer which corresponding features comprise CPI that should be protected in a TEE. Our evaluation results indicate that our approach identifies CPI with a high degree of accuracy to incorporate safeguarding CPI into Requirements Engineering.
Master of Science
An increasing number of software systems must safeguard their confidential data like passwords, payment information, personal details, etc. This confidential information is commonly protected using a Trusted Execution Environment (TEE), an isolated environment provided by either the existing processor or separate hardware that interacts with the operating system to secure sensitive data and code. Unfortunately, TEE protection incurs heavy performance costs, with TEEs being slower than modern processors and frequent communication between the system and the TEE incurring heavy performance overhead. We discovered that developers often put code and data into TEE for convenience rather than protection purposes, thus not only hurting performance but also reducing the effectiveness of TEE protection. By thoroughly examining a project's features in the Requirements Engineering phase, which defines the project's functionalities, developers would be able to understand which features handle confidential data. To that end, we present a novel approach that incorporates TEEs in the Requirements Engineering phase by means of Natural Language Processing (NLP) tools to categorize the project requirements that may warrant TEE protection. Our approach takes as input a project's requirements and outputs a list of categorized requirements defining which requirements are likely to make use of confidential information. Our evaluation results indicate that our approach performs this categorization with a high degree of accuracy to incorporate safeguarding the confidentiality related features in the Requirements Engineering phase.
APA, Harvard, Vancouver, ISO, and other styles
8

Coskuncay, Ahmet. "An Approach For Generating Natural Language Specifications By Utilizing Business Process Models." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612305/index.pdf.

Full text
Abstract:
Business process modeling is utilized by organizations for defining and reengineering their business processes. On the other hand, software requirements analysis activities are performed for determining the system boundaries, specifying software requirements using system requirements and resolving conflicts between requirements. From this point of view, these two activities are considered in different disciplines. An organization requiring its business processes to be defined and supported with information systems would benefit from performing business process modeling and requirements analysis concurrently. In this study, an approach enabling concurrent execution of business process modeling and requirements analysis is developed. The approach includes two business process modeling notations adapted to the research needs, a process defining the steps for implementing the approach and the requirements generation tool that generates natural language specification documents by using business process models. Within this study, two case studies are introduced
one describing the development of the approach and the other exploring if the total efficiency of performing business process modeling and requirements analysis activites would be increased by using the approach.
APA, Harvard, Vancouver, ISO, and other styles
9

Kwan, Irwin. "On the Maintenance Costs of Formal Software Requirements Specification Written in the Software Cost Reduction and in the Real-time Unified Modeling Language Notations." Thesis, University of Waterloo, 2005. http://hdl.handle.net/10012/1092.

Full text
Abstract:
A formal specification language used during the requirements phase can reduce errors and rework, but formal specifications are regarded as expensive to maintain, discouraging their adoption. This work presents a single-subject experiment that explores the costs of modifying specifications written in two different languages: a tabular notation, Software Cost Reduction (SCR), and a state-of-the-practice notation, Real-time Unified Modeling Language (UML). The study records the person-hours required to write each specification, the number of defects made during each specification effort, and the amount of time repairing these defects. Two different problems are specified—a Bidirectional Formatter (BDF), and a Bicycle Computer (BC)—to balance a learning effect from specifying the same problem twice with different specification languages. During the experiment, an updated feature for each problem is sent to the subject and each specification is modified to reflect the changes.

The results show that the cost to modify a specification are highly dependent on both the problem and the language used. There is no evidence that a tabular notation is easier to modify than a state-of-the-practice notation.

A side-effect of the experiment indicates there is a strong learning effect, independent of the language: in the BDF problem, the second time specifying the problem required more time, but resulted in a better-quality specification than the first time; in the BC problem, the second time specifying the problem required less time and resulted in the same quality specification as the first time.

This work demonstrates also that single-subject experiments can add important information to the growing body of empirical data about the use of formal requirements specifications in software development.
APA, Harvard, Vancouver, ISO, and other styles
10

Mahmud, Nesredin. "Ontology-based Analysis and Scalable Model Checking of Embedded Systems Models." Licentiate thesis, Mälardalens högskola, Inbyggda system, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-35386.

Full text
Abstract:
Currently, there is lack of effective and scalable methods to specify and ana-lyze requirements specifications, and verify the behavioral models of embed-ded systems. Most embedded systems requirements are expressed in naturallanguage which is flexible and intuitive but frequently ambiguous, vague andincomprehensive. Besides to natural language, template-based requirementsspecification methods are used to specify requirements specifications (esp. insafety-critical applications), which reduce ambiguity and improves the com-prehensibility of the specifications. However, the template-based method areusually rigid due to the fixed structures of the templates. They also lack meta-models for extensibility, and template selection is challenging.In this thesis, we proposed a domain specific language for embedded sys-tems, called ReSA, which is constrained natural language but flexible enoughto allow engineers to use different constructs to specify requirements. Thelanguage has formal semantics in proportional logic and description logic thatenables non-trivial and rigorous analysis of requirements specification, e.g.,consistency checking, completeness of specifications, etc.Moreover, we propose a scalable formal verification of Simulink models,whichisusedtodescribethebehaviorofsystemsthroughcommunicatingfunc-tional blocks. In industry, Simulink is the de facto modeling and analysis en-vironment of embedded systems. It is also used to generate code automati-cally from special Simulink models for various hardware platforms. However,Simulink lacks formal approach to verify large and hybrid Simulink models.Therefore, we also propose a formal verification of Simulink models, repre-sented as stochastic timed automata, using statistical model checking, whichhas proven to scale for industrial applications.We validate our approaches on industrial use cases from the automotiveindustry. These includes Adjustable Speed Limiter (ASL) and Brake-By-Wire(BBW) systems from Volvo Group Trucks Technology, both safety-critical.
Verispec
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Requirements Specification Language"

1

Randell, G. P. Languages for requirements specifications. Malvern, Wors: Defence Research Agency, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Deborah, Frincke, and Langley Research Center, eds. Requirements Specification Language (RSL) and supporting tools. Hampton, Va: National Aeronautics and Space Administration, Langley Research Center, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

C, Cohen G., and Langley Research Center, eds. Reference manual for a Requirements Specification Language (RSL). Hampton, Va: National Aeronautics and Space Administration, Langley Research Center, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

C, Cohen G., and Langley Research Center, eds. Tools reference manual for a Requirements Specification Language (RSL). Hampton, Va: National Aeronautics and Space Administration, Langley Research Center, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Michael, Furmston, Tolhurst G J, and Mik Eliza. 2 Offers and Invitations to Treat. Oxford University Press, 2016. http://dx.doi.org/10.1093/law/9780198724032.003.0002.

Full text
Abstract:
This chapter begins by discussing how developed legal systems seem to have adopted the technique of analyzing transactions in terms of offer and acceptance to determine whether there is an agreement. It then turns to the identification of offers, covering the definition of an offer; the requirements of a valid offer, i.e. extent of commitment evinced, the certainty of the terms used, and the specification of the addressees; how the language used in the proposal is the most decisive factor when examining what the addressee is entitled to conclude when judging the proposal to be an offer; and the communication of offer.
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Requirements Specification Language"

1

Weik, Martin H. "requirements specification language." In Computer Science and Communications Dictionary, 1476. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_16166.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Śmiałek, Michał, and Wiktor Nowakowski. "Presenting the Requirements Specification Language." In From Requirements to Java in a Snap, 31–65. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-12838-2_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Heloir, Alexis, and Michael Kipp. "Requirements for a Gesture Specification Language." In Gesture in Embodied Communication and Human-Computer Interaction, 207–18. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12553-9_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Barros, Oscar, and Germán Pavez. "An Object-Oriented Executable Requirements Specification Language." In Database and Expert Systems Applications, 227–32. Vienna: Springer Vienna, 1991. http://dx.doi.org/10.1007/978-3-7091-7555-2_38.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Leveson, Nancy G. "Designing a Requirements Specification Language for Reactive Systems." In ZUM ’98: The Z Formal Specification Notation, 135. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/978-3-540-49676-2_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Ghosh, Shalini, Daniel Elenius, Wenchao Li, Patrick Lincoln, Natarajan Shankar, and Wilfried Steiner. "ARSENAL: Automatic Requirements Specification Extraction from Natural Language." In Lecture Notes in Computer Science, 41–46. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-40648-0_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Baraona, Phillip, John Penix, and Perry Alexander. "VSPEC: A Declarative Requirements Specification Language for VHDL." In Current Issues in Electronic Modeling, 51–75. Boston, MA: Springer US, 1995. http://dx.doi.org/10.1007/978-1-4615-2303-1_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Cerna, David M., Wolfgang Schreiner, and Temur Kutsia. "Predicting Space Requirements for a Stream Monitor Specification Language." In Runtime Verification, 135–51. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-46982-9_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Ilieva, M. G., and Olga Ormandjieva. "Automatic Transition of Natural Language Software Requirements Specification into Formal Presentation." In Natural Language Processing and Information Systems, 392–97. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11428817_45.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Baligand, Fabien, Didier Le Botlan, Thomas Ledoux, and Pierre Combes. "A Language for Quality of Service Requirements Specification in Web Services Orchestrations." In Service-Oriented Computing – ICSOC 2007, 38–49. Berlin, Heidelberg: Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-75492-3_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Requirements Specification Language"

1

Effendi, Iwan, Brian Henson, Vassilis Agouridas, and Alan de Pennington. "Methods and Tools for Requirements Engineering of Made-to-Order Mechanical Products." In ASME 2002 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2002. http://dx.doi.org/10.1115/detc2002/dtm-34014.

Full text
Abstract:
This paper reviews tools and methods for requirements engineering and assesses their applicability to requirements management of a made-to-order mechanical product. One method, the use of a formal specification modeling language, is used to model the evolving specification of a mechanical system during embodiment and detail design. The model of the product specification is then evaluated against the following criteria: verifiability; correctness; understandability; consistency; ability to represent different levels of detail; modifiability; traceability; ambiguity; and annotability. The suitability of using specification languages to represent mechanical product specifications is discussed.
APA, Harvard, Vancouver, ISO, and other styles
2

Sharifi, Sepehr, Alireza Parvizimosaed, Daniel Amyot, Luigi Logrippo, and John Mylopoulos. "Symboleo: Towards a Specification Language for Legal Contracts." In 2020 IEEE 28th International Requirements Engineering Conference (RE). IEEE, 2020. http://dx.doi.org/10.1109/re48521.2020.00049.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mohsin, Muhammad, and Muhammad Umair Khan. "UML-SR: A Novel Security Requirements Specification Language." In 2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS). IEEE, 2019. http://dx.doi.org/10.1109/qrs.2019.00051.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Umber, Ashfa, and Imran Sarwar Bajwa. "Minimizing ambiguity in natural language software requirements specification." In 2011 Sixth International Conference on Digital Information Management (ICDIM). IEEE, 2011. http://dx.doi.org/10.1109/icdim.2011.6093363.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Fatwanto, Agung. "Software requirements specification analysis using natural language processing technique." In 2013 International Conference on QiR (Quality in Research). IEEE, 2013. http://dx.doi.org/10.1109/qir.2013.6632546.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Fatwanto, Agung. "Translating software requirements from natural language to formal specification." In 2012 IEEE International Conference on Computational Intelligence and Cybernetics (CyberneticsCom). IEEE, 2012. http://dx.doi.org/10.1109/cyberneticscom.2012.6381636.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Sadoun, Driss, Catherine Dubois, Yacine Ghamri-Doudane, and Brigitte Grau. "From Natural Language Requirements to Formal Specification Using an Ontology." In 2013 IEEE 25th International Conference on Tools with Artificial Intelligence (ICTAI). IEEE, 2013. http://dx.doi.org/10.1109/ictai.2013.116.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hu, Jun, Jiancheng Hu, Wenxuan Wang, Jiexiang Kang, Hui Wang, and Zhongjie Gao. "Constructing Formal Specification Models from Domain Specific Natural Language Requirements." In 2020 6th International Symposium on System and Software Reliability (ISSSR). IEEE, 2020. http://dx.doi.org/10.1109/isssr51244.2020.00017.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Fatwanto, Agung. "Natural language requirements specification analysis using Part-of-Speech Tagging." In 2013 Second International Conference on Future Generation Communication Technology (FGCT). IEEE, 2013. http://dx.doi.org/10.1109/fgct.2013.6767215.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Geetha, S., and G. S. A. Mala. "Extraction of key attributes from natural language requirements specification text." In IET Chennai Fourth International Conference on Sustainable Energy and Intelligent Systems (SEISCON 2013). Institution of Engineering and Technology, 2013. http://dx.doi.org/10.1049/ic.2013.0341.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Requirements Specification Language"

1

Ghosh, Shalini, Natarajan Shankar, Patrick Lincoln, Daniel Elenius, Wenchao Li, and Wilfrid Steiener. Automatic Requirements Specification Extraction from Natural Language (ARSENAL). Fort Belvoir, VA: Defense Technical Information Center, October 2014. http://dx.doi.org/10.21236/ada611691.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Requirements Specification Language' for particular source types:
Journal articles Dissertations / Theses
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography