Journal articles: '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

11

Shah, Unnati S., and Devesh C. Jinwala. "Resolving ambiguity in natural language specification to generate UML diagrams for requirements specification." International Journal of Software Engineering, Technology and Applications 1, no. 2/3/4 (2015): 308. http://dx.doi.org/10.1504/ijseta.2015.075638.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Liu, Chun, Zhengyi Zhao, Lei Zhang, and Zheng Li. "Automated Conditional Statements Checking for Complete Natural Language Requirements Specification." Applied Sciences 11, no. 17 (August 26, 2021): 7892. http://dx.doi.org/10.3390/app11177892.

Full text

Abstract:

Defects such as the duality and the incompleteness in natural language software requirements specification have a significant impact on the success of software projects. By now, many approaches have been proposed to assist requirements analysts to identify these defects. Different from these approaches, this paper focuses on the requirements incompleteness implied by the conditional statements, and proposes a sentence embedding- and antonym-based approach for detecting the requirements incompleteness. The basic idea is that when one condition is stated, its opposite condition should also be there. Otherwise, the requirements specification is incomplete. Based on the state-of-the-art machine learning and natural language processing techniques, the proposed approach first extracts the conditional sentences from the requirements specification, and elicits the conditional statements which contain one or more conditional expressions. Then, the conditional statements are clustered using the sentence embedding technique. The conditional statements in each cluster are further analyzed to detect the potential incompleteness by using negative particles and antonyms. A benchmark dataset from an aerospace requirements specification has been used to validate the proposed approach. The experimental results have shown that the recall of the proposed approach reaches 68.75%, and the F1-measure (F1) 52.38%.

APA, Harvard, Vancouver, ISO, and other styles

13

Viriyasitavat, Wattana, Li Da Xu, and Andrew Martin. "SWSpec: The Requirements Specification Language in Service Workflow Environments." IEEE Transactions on Industrial Informatics 8, no. 3 (August 2012): 631–38. http://dx.doi.org/10.1109/tii.2011.2182519.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Cooper, Kendra, and Mabo Ito. "1.6.2 Formalizing a Structured Natural Language Requirements Specification Notation." INCOSE International Symposium 12, no. 1 (August 2002): 1025–32. http://dx.doi.org/10.1002/j.2334-5837.2002.tb02569.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Wijayarathna, P. G., Y. Kawata, A. Santosa, K. Isogai, and M. Maekawa. "GSL: a requirements specification language for end-user intelligibility." Software: Practice and Experience 28, no. 13 (November 1998): 1387–414. http://dx.doi.org/10.1002/(sici)1097-024x(1998110)28:13<1387::aid-spe208>3.0.co;2-#.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Knoll, H. D., and W. Suk. "A graphic language for business applications ...user requirements specification." ACM SIGSOFT Software Engineering Notes 14, no. 6 (October 1989): 58–60. http://dx.doi.org/10.1145/70739.70745.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Liu, Shaoying. "A Formal Definition of FRSM and Applications." International Journal of Software Engineering and Knowledge Engineering 08, no. 02 (June 1998): 253–81. http://dx.doi.org/10.1142/s0218194098000145.

Full text

Abstract:

FRSM (Formal Requirements Specification Method) is a structured formal language and method for requirements analysis and specification construction based on data flow analysis. It uses a formalized DeMarco data flow diagram to describe the overall structure of systems and a VDM-SL like formal notation to describe precisely the functionality of components in the diagrams. This paper first describes the formal syntax and semantics of FRSM and then presents an example of using the axiom and inference rules given in the definition of the formal semantics for checking consistency of specifications. A case study of applying FRSM to a practical example is described to demonstrate the principle of constructing requirements specifications and to uncover the benefits and deficiencies of FRSM.

APA, Harvard, Vancouver, ISO, and other styles

18

da Silva, Alberto Rodrigues, and Dušan Savić. "Linguistic Patterns and Linguistic Styles for Requirements Specification: Focus on Data Entities." Applied Sciences 11, no. 9 (April 30, 2021): 4119. http://dx.doi.org/10.3390/app11094119.

Full text

Abstract:

Requirements specification includes technical concerns of an information system and is used throughout its life cycle. It allows for sharing the vision of the system among stakeholders and facilitates its development and operation processes. Natural languages are the most common form of requirements representation, however, they also exhibit characteristics that often introduce quality problems, such as inconsistency, incompleteness, and ambiguousness. This paper adopts the notions of linguistic pattern and linguistic style and discusses their relevance to produce better technical documentation. It focuses on the textual specification of data entities, which are elements commonly referred to throughout different types of requirements, like use cases, user stories, or functional requirements. This paper discusses how to textually represent the following elements: data entity, attribute, data type, data entity constraint, attribute constraint, and even cluster of data entities. This paper shows concrete examples and supports the discussion with three linguistic styles, represented by a rigorous requirements specification language and two informal controlled natural languages, one with a more compact and another with a more verbose, expressive, and complete representation. We analyzed how other languages cope with the representation of these data entity elements and complemented that analysis and comparison based on the PENS classification scheme. We conducted a pilot evaluation session with nineteen professional subjects who participated and provided encouraging feedback, with positive scores in all the analyzed dimensions. From this feedback, we preliminarily conclude that the adoption of these linguistic patterns would help to produce better requirements specifications written more systematically and consistently.

APA, Harvard, Vancouver, ISO, and other styles

19

Redouane, Abdesselam. "Towards a Specification Language for Mobile Applications." International Journal of Software Science and Computational Intelligence 5, no. 2 (April 2013): 58–76. http://dx.doi.org/10.4018/ijssci.2013040104.

Full text

Abstract:

Mobile applications are increasingly being developed by many developers using different environments for diverse devices. However, there is no method or formal language that helps these developers specify their requirements before the coding stage. In this paper, the author describes a specification language that helps in this context. To achieve rigor, the language is based on an extended first order predicate calculus and allows specifiers to modularize their specifications. The language is founded on two concepts: a pristine which can be seen as a unit of cognition and a definition which is a logical rule based on pristines and other definitions. Furthermore, the language allows specifiers to express constraints which are fundamental features in mobile applications. A use of this language is shown by an example.

APA, Harvard, Vancouver, ISO, and other styles

20

Wang, Yu Hua, Gui Sheng Yin, and Hai Tao Zhang. "Research on Conversion Method of Ontology Based Formal Requirements Model to UML Requirements Document." Advanced Materials Research 268-270 (July 2011): 1086–91. http://dx.doi.org/10.4028/www.scientific.net/amr.268-270.1086.

Full text

Abstract:

In the process of requirements modeling based on ontology, the obtained model description is based on application ontology; which is not easy for designer to understand and cannot be converted into requirements specification documents for design. UML is actual standard for object-oriented modeling. For this issue, this paper creates the UML meta-model, and establishes mapping rules description language for application ontology to UML meta-element, which implements the generation of UML class diagrams based on rule, use case diagrams, state transition diagram models and requirements specification documents based on UML.

APA, Harvard, Vancouver, ISO, and other styles

21

Ciaccia, P., P. Ciancarini, and W. Penzo. "Formal Requirements and Design Specifications: The Clepsydra Methodology." International Journal of Software Engineering and Knowledge Engineering 07, no. 01 (March 1997): 1–42. http://dx.doi.org/10.1142/s0218194097000023.

Full text

Abstract:

The use of formal methods early in the development process has been advocated as a way of improving the quality of software products and their production process. Here we study the influence of a formal requirements document on the next phase in the software process, that is design. We suggest that formal design should coherently follow from formal requirements. We show that two different formal notations can be effectively used, one for writing requirements specification and one for design specification. We also consider how a design specification can be formally checked with respect to requirements specification. The notations we choose are well known: the Z notation for requirements and the Larch two-tiered language for design. We show how a number of tools based on these notations can be used to improve the quality of the documents produced during the development process.

APA, Harvard, Vancouver, ISO, and other styles

22

TRAJCEVSKI, GOCE, CHITTA BARAL, and JORGE LOBO. "FORMALIZING AND REASONING ABOUT THE REQUIREMENTS SPECIFICATIONS OF WORKFLOW SYSTEMS." International Journal of Cooperative Information Systems 10, no. 04 (December 2001): 483–507. http://dx.doi.org/10.1142/s021884300100045x.

Full text

Abstract:

This work addresses the problem of workflow requirements specifications considering the realistic assumptions that, it involves experts from different domains (i.e. representatives of different business policies); not all the possible execution scenarios are known beforehand, during the early stage of specification. In particular, since the main purpose of a workflow is to achieve a certain (bussiness) goal, we propose a formalism which enables the users to specify their requirements (and expectations) and test if the information that they have provided is, in a sense, sufficient for the workflow to behave "as desired", in terms of the goal. Our methodology allows domain experts to express not only their knowledge, but also the "ignorance" (the semantics allows for unknown values to reflect a realistic situation of agents dealing with incomplete information) and the possibility of occurrence of exceptional situations. As a basis for formalizing the process of equirements specifications, we are using the recent results on reasoning about actions. We propose a high level language AW which enables specifying the effects that activites have on the environment and how they should be coordinated. We also describe our prototype tool for process specification. Strictly speaking, in this work we go "one step" before actual analysis and design, and offer a formalism which enables the involved partners to see if the extent to which they have expressed their domain knowledge (which may sometimes be subject to a proprietary restricions) can satisfy the intended needs and behaviour of their product_to_be. We define an entailment relation which enables reasoning about the correctness of the specification, in terms of achieving a desired goal and, also testing about consequences of modifications in the workflow descriptions.

APA, Harvard, Vancouver, ISO, and other styles

23

TSAI, JEFFREY J. P., ALAN LIU, and KRISHNAKUMAR NAIR. "DEBUGGING LOGIC-BASED REQUIREMENTS SPECIFICATIONS FOR SAFETY-CRITICAL SYSTEMS — A FRORL APPROACH." International Journal of Software Engineering and Knowledge Engineering 04, no. 02 (June 1994): 205–28. http://dx.doi.org/10.1142/s0218194094000118.

Full text

Abstract:

Safety-critical systems are not only difficult to build, but also difficult to debug because they often have strict timing constraints and non-deterministic behavior. A correct and precise specification reduces the effort spent in testing and debugging the implemented system. This paper presents techniques of specification debugging and issues related to it. We introduce an approach to the debugging of a specification in FRORL (Frame and Rule Oriented Requirements Language), which supports non-determinism and non-monotonicity in a system. The approach aids the user in detecting and correcting the possible faults which can arise not only when writing the specification, but also after the verification of the specification.

APA, Harvard, Vancouver, ISO, and other styles

24

Sengupta, Anirban, and Chandan Mazumdar. "A Mark-Up Language for the Specification of Information Security Governance Requirements." International Journal of Information Security and Privacy 5, no. 2 (April 2011): 33–53. http://dx.doi.org/10.4018/jisp.2011040103.

Full text

Abstract:

As enterprises become dependent on information systems, the need for effective Information Security Governance (ISG) assumes significance. ISG manages risks relating to the confidentiality, integrity and availability of information, and its supporting processes and systems, in an enterprise. Even a medium-sized enterprise contains a huge collection of information and other assets. Moreover, risks evolve rapidly in today’s connected digital world. Therefore, the proper implementation of ISG requires automation of the various monitoring, analysis, and control processes. This can be best achieved by representing information security requirements of an enterprise in a standard, structured format. This paper presents such a structured format in the form of Enterprise Security Requirement Markup Language (ESRML) Version 2.0. It is an XML-based language that considers the elements of ISO 27002 best practices.

APA, Harvard, Vancouver, ISO, and other styles

25

Hayman Oo, Khin, Azlin Nordin, Amelia Ritahani Ismail, and Suriani Sulaiman. "An Analysis of Ambiguity Detection Techniques for Software Requirements Specification (SRS)." International Journal of Engineering & Technology 7, no. 2.29 (May 22, 2018): 501. http://dx.doi.org/10.14419/ijet.v7i2.29.13808.

Full text

Abstract:

Ambiguity is the major problem in Software Requirements Specification (SRS) documents because most of the SRS documents are written in natural language and natural language is generally ambiguous. There are various types of techniques that have been used to detect ambiguity in SRS documents. Based on an analysis of the existing work, the ambiguity detection techniques can be categorized into three approaches: (1) manual approach, (2) semi-automatic approach using natural language processing, (3) semi-automatic approach using machine learning. Among them, one of the semi-automatic approaches that uses the Naïve Bayes (NB) text classification technique obtained high accuracy and performed effectively in detecting ambiguities in SRS.

APA, Harvard, Vancouver, ISO, and other styles

26

Et.al, Naveen N. Kulkarni. "Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 11, 2021): 3338–44. http://dx.doi.org/10.17762/turcomat.v12i3.1590.

Full text

Abstract:

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

APA, Harvard, Vancouver, ISO, and other styles

27

Moreira, Fernando, and Maria João Ferreira. "Teaching and Learning Modelling and Specification Based on Mobile Devices and Cloud." International Journal of Technology and Human Interaction 13, no. 4 (October 2017): 33–49. http://dx.doi.org/10.4018/ijthi.2017100103.

Full text

Abstract:

Teaching Requirements Engineering and, in particular modelling and specification requirements, at the higher education institutions is an “arduous” task according to the literature. In this way, it is proposed an approach that aims to contribute for filling this gap. So, in the context of a degree in Informatics, and following the guidelines of the Information Systems courses provided by ACM/AIS, we explore the Modeling and Specification (MS) of requirements using Unified Modelling Language (UML) integrated into the TLP (TLP-MS) activity of the BML Context Oriented (BML-CO) model. These activities (modelling and specification of requirements) are supported by the use of the Lucidchart tool in a collaborative environment.

APA, Harvard, Vancouver, ISO, and other styles

28

Vidal-Silva, C. L., E. Madariaga, T. Pham, F. Johnson, L. A. Urzua, and L. Carter. "JPIAspectZ: A Formal Requirement Specification Language for Joint Point Interface AOP Applications." Engineering, Technology & Applied Science Research 9, no. 4 (August 10, 2019): 4338–41. http://dx.doi.org/10.48084/etasr.2774.

Full text

Abstract:

Aspect-oriented software development (AOSD) solves a few issues of the object-oriented software development (OOSD) approach and adds a few more concerning modules and their relationships. Join point interface (JPI) is an AOSD methodology that by the definition of the interface between advised artifacts and aspects solves associated AOSD issues to get software with a high modularity level. Looking for a JPI software development approach, this article proposes and exemplifies the use of JPIAspectZ, an extension of the formal aspect-oriented language AspectZ for the software JPI requirement specifications. Mainly, JPIAspectZ looks for a concept and model consistency in a JPI software development process. Since the main JPI characteristics are the joining point interfaces definitions, i. e. explicit associations definition between aspects and advised modules, thus, by JPI, classes are no longer oblivious of possible interaction with aspects, and aspects, for their action effectiveness, do not depend anymore on signatures of advisable module components. JPIAspectZ fully supports these JPI principles. As JPI application examples, this article shows the formal requirements specification for classic aspect-oriented and JPI examples, along with describing the advantages and disadvantages of this language.

APA, Harvard, Vancouver, ISO, and other styles

29

Quesada, Luis, Fernando Berzal, and Juan-Carlos Cubero. "ModelCC — A Pragmatic Parser Generator." International Journal of Software Engineering and Knowledge Engineering 24, no. 08 (October 2014): 1177–95. http://dx.doi.org/10.1142/s0218194014500375.

Full text

Abstract:

Syntax-directed translation tools require the specification of a language by means of a formal grammar. This grammar must also conform to the specific requirements of the parser generator to be used. Software engineers then annotate the resulting grammar with semantic actions for the resulting system to perform its desired functionality. Whenever the input text format is modified, the grammar has to be updated and the subsequent changes propagate throughout the entire language processing tool chain. Moreover, if several applications use the same language, multiple copies of the same language specification have to be maintained in sync, since language specification (i.e. the grammar) is tightly coupled to language processing (i.e. the semantic actions that annotate that grammar). In this paper, we introduce ModelCC, a model-based parser generator that decouples language specification from language processing, hence avoiding the aforementioned problems that are caused by grammar-driven parser generators. ModelCC receives a conceptual model as input, along with constraints that annotate it. It is then able to create a parser for a given textual representation format, so that the generated parser fully automates the instantiation of the desired conceptual model. ModelCC is also a powerful tool for the design of domain-specific languages.

APA, Harvard, Vancouver, ISO, and other styles

30

Benabbou, Amel, and Safia Nait-Bahloul. "Automated Context Formalization for Context-aware Specification Approach." International Journal of Information System Modeling and Design 9, no. 3 (July 2018): 23–47. http://dx.doi.org/10.4018/ijismd.2018070102.

Full text

Abstract:

Requirement specification is a key element in model-checking verification. The context-aware approach is an effective technique for automating the specification of requirement considering specific environmental conditions. In most of existing approaches, there is no support of this crucial task and are mainly based on the considerable efforts and expertise of engineers. A domain-specific language, called CDL, has been proposed to facilitate the specification of requirement by formalizing contexts. However, the feedback has shown that manually writing CDL is hard, error prone and difficult to grasp on complex systems. In this article, the authors propose an approach to automatically generate CDL models using (IODs) elaborated through transformation chains from textual use cases. They offer an intermediate formalism between informal use cases scenarios and CDL models allowing to engineers to manipulate with familiar artifacts. Thanks to such high-level formalism, the gap between informal and formal requirements is reduced; consequently, the requirement specification is facilitated.

APA, Harvard, Vancouver, ISO, and other styles

31

Vallejo, Paola, Raul Mazo, Carlos Jaramillo, and Jhon Medina Medina. "Towards a new template for the specification of requirements in semi-structured natural language." Journal of Software Engineering Research and Development 8 (February 4, 2020): 3. http://dx.doi.org/10.5753/jserd.2020.473.

Full text

Abstract:

Requirements engineering is a systematic and disciplined approach for the specification and management of software requirements; one of its objectives is to transform the requirements of the stakeholders into formal spec-ifications in order to analyze and implement a system. These requirements are usually expressed and articulated in natural language, this due to the universality and facility that natural language presents for communicating them. To facilitate the transformation processes and to improve the quality of the resulting requirements, several authors have proposed templates for writing requirements in structured natural language. However, these templates do not allow writing certain functional requirements, non-functional requirements and constraints, and they do not adapt correctly to certain types of systems such as self-adaptive, product line-based and embedded systems. This paper (i) presents evidence of the weaknesses of the template recommended by the IREB® (International Requirements Engineering Institute), and (ii) lays the foundations, through a new template, for facilitating the work of the re-quirements engineers and therefore improving the quality of the products specified with the new template. This new template was built and evaluated through two active research cycles. In each cycle we identified the problems specifying the requirements of the corresponding industrial case with the corresponding base-line template, pro-pose some improvements to address these problems and analyze the results of using the new template to specify the requirements of each case. Thus, the resulting template was able to correctly write all requirements of both industrial cases. Despite the promising results of this new template, it is still preliminary work regarding its cov-erage and the quality level of the requirements that can be written with it.

APA, Harvard, Vancouver, ISO, and other styles

32

Muhamad, Zainab Hassan, Dhafer AbdulAmeer Abdulmonim, and Bashar Alathari. "An integration of uml use case diagram and activity diagram with Z language for formalization of library management system." International Journal of Electrical and Computer Engineering (IJECE) 9, no. 4 (August 1, 2019): 3069. http://dx.doi.org/10.11591/ijece.v9i4.pp3069-3076.

Full text

Abstract:

Unified Modeling Language (UML) is the effective standard for modeling object-oriented software systems. However, the ambiguity of semantics and the absence of consistency among UML diagrams lead to lack of precisely defining the requirements of a system. On the other hand, formal methods are techniques and tools use the mathematical notations, and they involve the precise syntax and semantics of the unambiguous software requirements specification. It applied in early stages of Software Development Life Cycle (SDLC). Therefore, an integrated between UML specification and formal specification is required to reduce the requirements' ambiguity and error, and to improve the quality and security of software systems. This paper proposes an approach involves the combining UML use-case diagram and activity diagrams with Z language for formalization of Library Management System (LMS). The focus of this paper is on consistency between the UML diagrams to Z Schema, and then verified by using the Z / EVEs tool.

APA, Harvard, Vancouver, ISO, and other styles

33

Xie, Guo, Xinhong Hei, Sei Takahashi, and Hideo Nakamura. "A Strategy to Formalize Specification and Its Application to an Advanced Railway System." International Journal of Software Engineering and Knowledge Engineering 24, no. 03 (April 2014): 465–92. http://dx.doi.org/10.1142/s0218194014500181.

Full text

Abstract:

This paper proposes a novel strategy for formally analyzing functional requirements specification (FRS) and applies it to the Automatic Train Protection and Block (ATPB) system, which is proposed to reconstruct conventional rail lines in Japan. Based on the FRS in natural language, firstly, dynamic state transitions are extracted to express the operational mechanisms and determine the system parameters. A complete model of the ATPB system is then established using Unified Modeling Language (UML) to express the system structure graphically and explicitly. After achieving a common understanding, a VDM++ model is established formally to redescribe the original FRS of the ATPB system which is written in natural language (i.e. Japanese). Following that, in order to ensure internal consistency of the specification, proof obligations of the VDM++ model are discharged. Furthermore, a comprehensive testing is implemented to ensure that the FRS meets actual requirements. Finally, the system is simulated strictly in accordance with the formal specification. Without any runtime errors, collisions or derailments, the results of the simulation demonstrate the high quality and safety of the specification.

APA, Harvard, Vancouver, ISO, and other styles

34

Yahiaoui, Ayoub, Hakim Bendjenna, Philippe Roose, Lawrence Chung, and Mohamed Amroune. "Temporal Pattern Specifications for Self-Adaptive Requirements." Recent Patents on Computer Science 12, no. 1 (January 10, 2019): 58–68. http://dx.doi.org/10.2174/2213275911666181019115744.

Full text

Abstract:

Background: Systems whose requirements change at a rate that necessitates adaptation without human intervention are called self-adaptive systems, and they have the ability to adjust their behavior autonomously at run-time in response to their environment’s evolution. Samples of applications that require self-adaptation include Smart home systems and environmental monitoring. However, self-adaptivity is often constructed in an ad-hoc manner. Methods: In this paper, the authors present a pattern-based specification language for self-adaptive systems. Its semantics are presented in terms of fuzzy logic. Thus, enabling a meticulous processing of requirements, in order to permit the formulation of self-adaptive requirements accurately, thereby facilitates the design of systems that are flexible and responsive to adaptation in a systematic manner. Results: To show the applicability and effectiveness of our language, the authors apply it to two case studies. One case study reviews the Smart fridge in ambient assisted living and the second case study is focused on an ambulance dispatching system using a developed support tool.

APA, Harvard, Vancouver, ISO, and other styles

35

Straszak, Tomasz, and Michał Śmiałek. "Model-driven acceptance test automation based on use cases." Computer Science and Information Systems 12, no. 2 (2015): 707–28. http://dx.doi.org/10.2298/csis141217033s.

Full text

Abstract:

Acceptance testing is highly dependent on the formulation of requirements, as the final system is tested against user requirements. It is thus highly desirable to be able to automate transition from requirements to acceptance tests. In this paper we present a model-driven approach to this issue, where detailed use case models are transformed into test cases. Importantly, our approach facilitates synchronising functional test cases with other types of tests (non-functional, domain logic, user interface) and introducing test data. This leads to a unified approach where requirements models of various kind drive the acceptance testing process. This process is parallel to the development process which also involves automatic transformations from requirements models to software development artefacts (models and code). To show validity of the approach we present a case study which uses a new tool called ReDSeT, that transforms requirements formulated in the Requirements Specification Language (RSL) into tests in a newly proposed Test Specification Language (TSL).

APA, Harvard, Vancouver, ISO, and other styles

36

Beernaert, T. F., and L. F. P. Etman. "Multi-level Decomposed Systems Design: Converting a Requirement Specification into an Optimization Problem." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 3691–700. http://dx.doi.org/10.1017/dsi.2019.376.

Full text

Abstract:

AbstractComplex technological artefacts are often decomposed into smaller components to keep their design manageable. The resulting challenge is to coordinate decisions that involve multiple components and to design components such that high-level targets are met. Analytical Target Cascading (ATC) is an analytical coordination method for the optimization of decomposed systems, which we aim to incorporate in systems engineering design process. To this extent, we relate the domain of engineering optimization to the domain of requirements engineering, and propose a method that constructs an ATC problem from functional specifications and requirements written in the newly developed Elephant Specification Language. The proposed method is demonstrated in the two-level design of an automotive powertrain. This contribution is a step towards design automation and is expected to increase the usability of decomposed optimization techniques.

APA, Harvard, Vancouver, ISO, and other styles

37

Gilb, Tom. "2 Quantifying The Qualitative: How to Avoid Vague Requirements by Clear Specification Language." INCOSE International Symposium 9, no. 1 (June 1999): 727–34. http://dx.doi.org/10.1002/j.2334-5837.1999.tb00232.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Carrillo de Gea, Juan M., Joaquín Nicolás, José L. Fernández Alemán, Ambrosio Toval, Sofia Ouhbi, and Ali Idri. "Co-located and distributed natural-language requirements specification: traditional versus reuse-based techniques." Journal of Software: Evolution and Process 28, no. 3 (February 26, 2016): 205–27. http://dx.doi.org/10.1002/smr.1772.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Wang, Ye, Ting Wang, and Jie Sun. "PASER: A Pattern-Based Approach to Service Requirements Analysis." International Journal of Software Engineering and Knowledge Engineering 29, no. 04 (April 2019): 547–76. http://dx.doi.org/10.1142/s0218194019500232.

Full text

Abstract:

Inconsistent specification are an inevitable intermediate product of a service requirements engineering process. In order to reduce requirements inconsistencies, we propose PASER, a Pattern-based Approach to Service Requirements analysis. The PASER approach first extracts the process information from service documents via natural language processing (NLP) techniques, then uses a requirements modeling language – Workflow-Patterns-based Process Language (WPPL) — to build the process model. Finally, through matching with workflow patterns, the inconsistencies in service requirements are identified and resolved by checking against a set of checking rules. We have conducted a preliminary experiment to evaluate it. An ATM service case study is presented as a running example to illustrate our approach.

APA, Harvard, Vancouver, ISO, and other styles

40

SAAKE, GUNTER, RALF JUNGCLAUS, and THORSTEN HARTMANN. "APPLICATION MODELLING IN HETEROGENEOUS ENVIRONMENTS USING AN OBJECT SPECIFICATION LANGUAGE." International Journal of Cooperative Information Systems 02, no. 04 (December 1993): 425–49. http://dx.doi.org/10.1142/s0218215793000198.

Full text

Abstract:

We propose an object-oriented logical formalism to conceptionally model applications in an interoperable environment. Such an environment consists of heterogeneous and autonomous local (database) systems. Applications in such an environment use several resources and services. Their conceptual modelling involves re-specification of existing systems in terms of homogeneous views, modelling of behavior and system dynamics, modelling of logically distributed components in an open environment and the modelling of communication relationships and dependencies between components. We introduce a formal object-oriented language capable of dealing with these requirements and illustrate its use to model applications in an interoperable environment.

APA, Harvard, Vancouver, ISO, and other styles

41

Ashfaq, Fariha, Imran Sarwar Bajwa, Rafaqut Kazmi, Akmal Khan, and Muhammad Ilyas. "An Intelligent Analytics Approach to Minimize Complexity in Ambiguous Software Requirements." Scientific Programming 2021 (March 22, 2021): 1–20. http://dx.doi.org/10.1155/2021/6616564.

Full text

Abstract:

An inconsistent and ambiguous Software Requirement Specification (SRS) document results in an erroneous/failed software project. Hence, it is a serious challenge to handle and process complex and ambiguous requirements. Most of the literature work focuses on detection and resolution of ambiguity in software requirements. Also, there is no standardized way to write unambiguous and consistent requirements. The goal of this research was to generate an ambiguity-less SRS document. This paper presents a new approach to write ambiguity-less requirements. Furthermore, we design a framework for Natural Language (NL) to Controlled Natural Language (CNL) (such as Semantic Business Vocabulary and Rules (SBVR)) transition and develop a prototype. The prototype also generates Resource Description Framework (RDF) representation. The SBVR has a shared meaning concept that minimizes ambiguity, and RDF representation is supported by query language such as SPARQL Protocol and RDF Query Language (SPARQL). The proposed approach can help software engineers to translate NL requirements into a format that is understandable by all stakeholders and also is machine processable. The results of our prototype are encouraging, exhibiting the efficient performance of our developed prototype in terms of usability and correctness.

APA, Harvard, Vancouver, ISO, and other styles

42

Brandic, Ivona, Sabri Pllana, and Siegfried Benkner. "An Approach for the High-Level Specification of QoS-Aware Grid Workflows Considering Location Affinity." Scientific Programming 14, no. 3-4 (2006): 231–50. http://dx.doi.org/10.1155/2006/670375.

Full text

Abstract:

Many important scientific and engineering problems may be solved by combining multiple applications in the form of a Grid workflow. We consider that for the wide acceptance of Grid technology it is important that the user has the possibility to express requirements on Quality of Service (QoS) at workflow specification time. However, most of the existing workflow languages lack constructs for QoS specification. In this paper we present an approach for high level workflow specification that considers a comprehensive set of QoS requirements. Besides performance related QoS, it includes economical, legal and security aspects. For instance, for security or legal reasons the user may express the location affinity regarding Grid resources on which certain workflow tasks may be executed. Our QoS-aware workflow system provides support for the whole workflow life cycle from specification to execution. Workflow is specified graphically, in an intuitive manner, based on a standard visual modeling language. A set of QoS-aware service-oriented components is provided for workflow planning to support automatic constraint-based service negotiation and workflow optimization. For reducing the complexity of workflow planning, we introduce a QoS-aware workflow reduction technique. We illustrate our approach with a real-world workflow for maxillo facial surgery simulation.

APA, Harvard, Vancouver, ISO, and other styles

43

Sandhu, Geet. "Analysis of Modeling Techniques used for Translating Natural Language Specification into Formal Software Requirements." International Journal of Computer Applications 113, no. 1 (March 18, 2015): 24–27. http://dx.doi.org/10.5120/19792-1570.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Zhao, Liping, Waad Alhoshan, Alessio Ferrari, Keletso J. Letsholo, Muideen A. Ajagbe, Erol-Valeriu Chioasca, and Riza T. Batista-Navarro. "Natural Language Processing for Requirements Engineering." ACM Computing Surveys 54, no. 3 (June 2021): 1–41. http://dx.doi.org/10.1145/3444689.

Full text

Abstract:

Natural Language Processing for Requirements Engineering (NLP4RE) is an area of research and development that seeks to apply natural language processing (NLP) techniques, tools, and resources to the requirements engineering (RE) process, to support human analysts to carry out various linguistic analysis tasks on textual requirements documents, such as detecting language issues, identifying key domain concepts, and establishing requirements traceability links. This article reports on a mapping study that surveys the landscape of NLP4RE research to provide a holistic understanding of the field. Following the guidance of systematic review, the mapping study is directed by five research questions, cutting across five aspects of NLP4RE research, concerning the state of the literature, the state of empirical research, the research focus, the state of tool development, and the usage of NLP technologies. Our main results are as follows: (i) we identify a total of 404 primary studies relevant to NLP4RE, which were published over the past 36 years and from 170 different venues; (ii) most of these studies (67.08%) are solution proposals, assessed by a laboratory experiment or an example application, while only a small percentage (7%) are assessed in industrial settings; (iii) a large proportion of the studies (42.70%) focus on the requirements analysis phase, with quality defect detection as their central task and requirements specification as their commonly processed document type; (iv) 130 NLP4RE tools (i.e., RE specific NLP tools) are extracted from these studies, but only 17 of them (13.08%) are available for download; (v) 231 different NLP technologies are also identified, comprising 140 NLP techniques, 66 NLP tools, and 25 NLP resources, but most of them—particularly those novel NLP techniques and specialized tools—are used infrequently; by contrast, commonly used NLP technologies are traditional analysis techniques (e.g., POS tagging and tokenization), general-purpose tools (e.g., Stanford CoreNLP and GATE) and generic language lexicons (WordNet and British National Corpus). The mapping study not only provides a collection of the literature in NLP4RE but also, more importantly, establishes a structure to frame the existing literature through categorization, synthesis and conceptualization of the main theoretical concepts and relationships that encompass both RE and NLP aspects. Our work thus produces a conceptual framework of NLP4RE. The framework is used to identify research gaps and directions, highlight technology transfer needs, and encourage more synergies between the RE community, the NLP one, and the software and systems practitioners. Our results can be used as a starting point to frame future studies according to a well-defined terminology and can be expanded as new technologies and novel solutions emerge.

APA, Harvard, Vancouver, ISO, and other styles

45

LIU, ALAN, and JEFFREY J. P. TSAI. "A METHOD FOR REQUIREMENTS ANALYSIS AND KNOWLEDGE ELICITATION." International Journal on Artificial Intelligence Tools 05, no. 01n02 (June 1996): 167–83. http://dx.doi.org/10.1142/s0218213096000122.

Full text

Abstract:

Requirements analysis is a knowledge intensive task and it requires an expert to understand what the clients need. In this paper, we introduce a method which contains different artificial intelligence techniques to perform this task, and a prototype knowledge-based requirements analysis system, RAKES, is presented to explain our approach. In this approach, not only the ordinary functional requirements are collected, but also some non-traditional information, such as non-functional requirements like the quality of operations or the background information for constructing the requirements, is gathered through a knowledge-based support. Different kinds of information collected are stored and organized in a knowledge base and can be used as the source of the user input in the latter phases of software development. Algorithms and procedures have been developed for constructing the interface language, organizing the knowledge base, and applying the knowledge base to different tasks. RAKES is integrated to an on-going research, called the FRORL methodology, to offer a systematic way toward requirements analysis, specification production, prototype generation, specification debugging, and code transformation.

APA, Harvard, Vancouver, ISO, and other styles

46

Zima, Hans P. "From FORTRAN 77 to Locality-Aware High Productivity Languages for Peta-Scale Computing." Scientific Programming 15, no. 1 (2007): 45–65. http://dx.doi.org/10.1155/2007/219061.

Full text

Abstract:

When the first specification of the FORTRAN language was released in 1956, the goal was to provide an "automatic programming system" that would enhance the economy of programming by replacing assembly language with a notation closer to the domain of scientific programming. A key issue in this context, explicitly recognized by the authors of the language, was the requirement to produce efficient object programs that could compete with their hand-coded counterparts. More than 50 years later, a similar situation exists with respect to finding the right programming paradigm for high performance computing systems. FORTRAN, as the traditional language for scientific programming, has played a major role in the quest for high-productivity programming languages that satisfy very strict performance constraints. This paper focuses on high-level support for locality awareness, one of the most important requirements in this context. The discussion centers on the High Performance Fortran (HPF) family of languages, and their influence on current language developments for peta-scale computing. HPF is a data-parallel language that was designed to provide the user with a high-level interface for programming scientific applications, while delegating to the compiler the task of generating an explicitly parallel message-passing program. We outline developments that led to HPF, explain its major features, identify a set of weaknesses, and discuss subsequent languages that address these problems. The final part of the paper deals with Chapel, a modern object-oriented language developed in the High Productivity Computing Systems (HPCS) program sponsored by DARPA. A salient property of Chapel is its general framework for the support of user-defined distributions, which is related in many ways to ideas first described in Vienna Fortran. This framework is general enough to allow a concise specification of sparse data distributions. The paper concludes with an outlook to future research in this area.

APA, Harvard, Vancouver, ISO, and other styles

47

Cha, Suhyun, Alexander Weigl, Mattias Ulbrich, Bernhard Beckert, and Birgit Vogel-Heuser. "Applicability of generalized test tables: a case study using the manufacturing system demonstrator xPPU." at - Automatisierungstechnik 66, no. 10 (October 25, 2018): 834–48. http://dx.doi.org/10.1515/auto-2018-0028.

Full text

Abstract:

Abstract With recent trends in manufacturing automation, control software in automated production systems becomes more complex and has more variability to keep pace with customer and market requirements. Quality assurance also becomes more and more important to ensure that the systems live up to expectations. However, correctness of automation software is rarely verified using formal techniques in spite of their high coverage. One of the main reasons is the lack of specification languages suitable for this application area that are both comprehensible and sufficiently expressive. Generalized test tables (GTTs), which are a specification language for reactive systems, were presented recently as an accessible representation for application engineers. This formalism achieves both the comprehensibility of concrete test tables and the coverage of formal methods. In our approach, the specification provided by GTTs is used for formal verification, especially model checking. In this paper, we present four new features for GTTs: the progression flag, strong repetition, row grouping, and specification on internal variables. We demonstrate the applicability and evaluate the comprehensibility of GTT-based specification and verification using a range of diverse scenarios from the community demonstrator, the extended Pick & Place Unit.

APA, Harvard, Vancouver, ISO, and other styles

48

Gramacho, Carolina, Ana Madeira, Cláudia Martins, Nélia Alexandre, Jorge Pinto, and Susana Correia. "POR Nível: Construção e validação de um teste de colocação para o Português Língua Estrangeira – resultados de um estudo-piloto." Revista da Associação Portuguesa de Linguística, no. 5 (November 21, 2019): 172–89. http://dx.doi.org/10.26334/2183-9077/rapln5ano2019a13.

Full text

Abstract:

Placement tests are a form of assessment that aims at placing students in appropriate levels. Placement tests must, therefore, be based on validity and reliability arguments to ensure appropriateness and consistency of assessment. Despite the growing interest in Portuguese as a Foreign Language (PFL), both nationally and internationally, to our knowledge there is no validated placement test that informs on general language abilities of adult PFL learners across levels. The POR Nível project aims at designing and validating a placement test for PFL adult learners, from A1 to C1 CEFR levels in grammar, vocabulary, listening and reading components. Corpora of written productions of 15 learners of 3 native languages (English, Mandarin and Spanish) from certified exams of PFL provide the empirical basis for items construction. Also, items’ specifications follow national and international guidelines (CEFR, Camões Profile for PFL), validity, reliability and practicality requirements, and also ALTE and ILTA recommendations. The results found thus far will provide empirical ground for item specification in a validated placement test and eventually contribute to the discussion of the contents of PFL teaching programs.

APA, Harvard, Vancouver, ISO, and other styles

49

Murtazina, M. Sh, and T. V. Avdeenko. "The detection of conflicts in the requirements specification based on an ontological model and a production rule system." Information Technology and Nanotechnology, no. 2416 (2019): 63–73. http://dx.doi.org/10.18287/1613-0073-2019-2416-63-73.

Full text

Abstract:

The paper presents an approach to organizing the detection of conflicts between requirements based on an ontological model and a system of production rules. Requirements in the form of plain text are converted to instances of OWL ontologies for analysis. There are three basic elements “subject”, “action” and “object” in the requirements. These elements become classes of the ontology. The object properties between instances of the same classes are defined in the ontology. In the system of rules it is determined that one of four types of relations can be established between a pair of the requirements: isConflict, isDuplicate, isInterconnect, isNotInterconnect. We develop the software product in the Python language for building and applying production rules system for classes and property objects of the ontology. Protégé 5.2 is used to work with the ontology. Also Python library PySwip and development environment SWI-Prolog 7.6.4 are used in the work. The paper also considers the issues of extracting requirements ontology instances from the automated processing results of textual requirements. The UDPipe with Russian language model is used for text processing.

APA, Harvard, Vancouver, ISO, and other styles

50

TSAI, JEFFREY J. J. P., and HUNG-CHIN JANG. "A KNOWLEDGE-BASED APPROACH FOR THE SPECIFICATION AND ANALYSIS OF REAL-TIME SOFTWARE SYSTEMS." International Journal on Artificial Intelligence Tools 01, no. 01 (March 1992): 1–35. http://dx.doi.org/10.1142/s0218213092000119.

Full text

Abstract:

FRORL (Frame-and-Rule Oriented Requirements specification Language) was proposed to exploit knowledge representation techniques as an aid in the specification, analysis, and development of a software system. With the real-time software systems as our target systems, the merely mechanisms provided by FRORL cannot meet the specific demands on real-time software systems. As a result, in this paper, we propose RT-FRORL (Real-Time FRORL) as an extension of FRORL. RT-FRORL not only inherits FRORL's basic structure but also includes those language constructs needed to support the specification of real-time systems. The syntax of RT-FRORL is based on frames and production rules. The semantics of RT-FRORL is defined through the integration of first order logic and temporal logic extension. Using RT-FRORL, concurrent and absolute time properties of real-time systems can be easily specified.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Requirements Specification Language'

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