Log in

Relevant bibliographies by topics / Language requirements / Journal articles

To see the other types of publications on this topic, follow the link: Language requirements.

Journal articles on the topic 'Language requirements'

Author: Grafiati

Published: 4 June 2021

Last updated: 1 February 2022

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

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Language requirements.'

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.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Yilmaz, A. Egemen. "Natural Language Processing." International Journal of Systems and Service-Oriented Engineering 4, no. 1 (January 2014): 68–83. http://dx.doi.org/10.4018/ijssoe.2014010105.

Full text

Abstract:

Requirement analysis is the very first and crucial step in the software development processes. On the other hand, as previously addressed by other researchers, it is the Achilles' heel of the whole process since the requirements lie on the problem space, whereas other software artifacts are on the solution space. Stating the requirements in a clear manner eases the following steps in the process as well as reducing the number of potential errors. In this paper, techniques for the improvement of the requirements expressed in the natural language are revisited. These techniques try to check the requirement quality attributes via lexical and syntactic analysis methods sometimes with generic, and sometimes domain and application specific knowledge bases.

APA, Harvard, Vancouver, ISO, and other styles

2

LUST, BARBARA. "Requirements for paradigm shift." Journal of Child Language 27, no. 3 (October 2000): 744–49. http://dx.doi.org/10.1017/s0305000900004426.

Full text

Abstract:

Since Noam Chomsky's famous 1959 review of B. F. Skinner's Verbal Behavior, a linguistically based paradigm for research in first language acquisition has been strong, even in some senses, dominant. Even Piaget, whose main concern was the nature of cognitive development in general, did not deny the essential claim of a linguistically based paradigm for the study of language acquisition: ‘I (Piaget) also agree with him (Chomsky) on the fact that this rational origin of language presupposes the existence of a fixed nucleus necessary to the elaboration of all languages’ (Piaget in Piatelli-Palmarini, 1980: 57). This linguistically based paradigm has led to a developed theory of what it is that the child must acquire when s/he acquires language, and to precise scientific hypotheses regarding the nature of this knowledge. These hypotheses can be, and are being, subjected to empirical test, thus advancing the scientific foundations of the field. In this paradigm, the postulation of a ‘Language Faculty’ in the mind of the human species, and in the child, has allowed the formulation of specific components of linguistic knowledge which are now being tested in language acquisition as well as in grammars of languages of the world.

APA, Harvard, Vancouver, ISO, and other styles

3

Williams, David O. "Language requirements for embedded systems." Computer Standards & Interfaces 6, no. 1 (January 1987): 51–60. http://dx.doi.org/10.1016/0920-5489(87)90045-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Dawood, Omer Salih, and Abd-El-Kader Sahraoui. "Toward Requirements and Design Traceability Using Natural Language Processing." European Journal of Engineering Research and Science 3, no. 7 (July 31, 2018): 42. http://dx.doi.org/10.24018/ejers.2018.3.7.807.

Full text

Abstract:

The paper aimed to address the problem of incompleteness and inconsistency between requirements and design stages, and how to make efficient linking between these stages. Software requirements written in natural languages (NL), Natural Language Processing (NLP) can be used to process requirements. In our research we built a framework that can be used to generate design diagrams from requirements in semi-automatic way, and make traceability between requirements and design phases, and in contrast. Also framework shows how to manage traceability in different levels, and how to apply changes to different artifacts. Many traceability reports can be generated based on developed framework. After Appling this model we obtained good results. Based on our case study the model generate a class diagram depends on central rule engine, and traceability was built and can be managed in visualize manner. We proposed to continue this research as its very critical area by adding more Unified Modeling Language(UML) diagrams, and apply changes directly inside software requirement document.

APA, Harvard, Vancouver, ISO, and other styles

5

Taušan, Nebojša, Jouni Markkula, Pasi Kuvaja, and Markku Oivo. "Embedded Systems Specific Requirements for Choreography Modelling Language Design." International Journal of Information System Modeling and Design 7, no. 3 (July 2016): 115–36. http://dx.doi.org/10.4018/ijismd.2016070106.

Full text

Abstract:

Software companies that develop embedded systems following the principles of service-oriented architecture can anticipate various benefits from choreography modelling. Current choreography modelling languages, however, have a limited applicability in embedded systems development since they are not expressive enough to capture all the choreography-relevant aspects that are typical in this domain. This problem is addressed in this study with the analysis of the needs in embedded systems domain for choreography modelling language. The analysis was guided by design science and relied on expert interviews, company-specific documents, relevant scientific literature and the experts' evaluation of the redesigned choreography modelling language. The main results of the analysis presented in this paper are a) design requirements addressing the limitations of choreography modelling languages for embedded systems development and b) proposals for modelling language implementation technologies. The derived design requirements indicate on choreography-relevant embedded systems development aspects such as the constraint-based access and real-time execution. Modelling language implementation technology proposals include Eclipse modelling framework and Sirius. The feasibility of these results is evaluated by redesigning an existing choreography modelling language based on the derived design requirements, implementing a prototype editor for the redesigned language and by evaluating the redesigned language with experts.

APA, Harvard, Vancouver, ISO, and other styles

6

Gaydamaka, K. "Archimate-Based Approach to Requirements Engineering." International Journal of Mathematical, Engineering and Management Sciences 4, no. 4 (August 1, 2019): 841–50. http://dx.doi.org/10.33889/ijmems.2019.4.4-066.

Full text

Abstract:

Requirements engineering represents the most crucial stage in the complex systems development process. Contemporary methods of requirements engineering assume a wide application of models (described, for example, with such languages as SysML or OPM), which allows to ensure the consistency and completeness of the system descriptions. The article assesses the applicability of the Archimate language to support the process of requirements engineering when creating complex technical systems. Requirements engineering method for complex technical systems, suitable for models described by the Archimate language is proposed. Detailed example demonstrating the proposed method when developing system requirements is given. The limitations of the Archimate language applicability for the engineering of systems of various classes are described.

APA, Harvard, Vancouver, ISO, and other styles

7

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

8

Dwyer, Matthew B. "Finding Flaws in Natural Language Requirements." Computer 49, no. 11 (November 2016): 10. http://dx.doi.org/10.1109/mc.2016.342.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Hackett, Kimberley. "Language requirements for overseas nurses eased." Nursing Standard 34, no. 10 (October 2, 2019): 7. http://dx.doi.org/10.7748/ns.34.10.7.s4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Butler, Carol A. "Nonsexist language requirements for APA manuscripts." Psychoanalytic Psychology 6, no. 4 (1989): 495. http://dx.doi.org/10.1037/0736-9735.6.4.495.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Gervasi, Vincenzo, and Bashar Nuseibeh. "Lightweight validation of natural language requirements." Software: Practice and Experience 32, no. 2 (2002): 113–33. http://dx.doi.org/10.1002/spe.430.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Loeb, Josh. "Language requirements for abattoir OVs eased." Veterinary Record 188, no. 7 (April 2021): 240–41. http://dx.doi.org/10.1002/vetr.352.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

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

14

Chang, Chih-Hung, Chih-Wei Lu, William Cheng-Chung Chu, Pao-Ann Hsiung, and Dong-Meau Chang. "SysML-Based Requirement Management to Improve Software Development." International Journal of Software Engineering and Knowledge Engineering 26, no. 03 (April 2016): 491–511. http://dx.doi.org/10.1142/s0218194016500200.

Full text

Abstract:

Among the various steps in the life cycle of software development, system requirement management is an essential but often neglected step. Comprehensive requirement management can not only help developers to work on a system to meet the requirements of a project, but can also play a vital role in the communications among stakeholders. In general, natural languages are often used to describe and record user requirements; however, this results in ambiguity, inconsistency, imprecision and incompleteness. To increase the accuracy of requirement modeling and analysis, it is important to have appropriate management methods and tools such that the requirement engineering process can be supported within the project. In this work, we propose a System Modeling Language (SysML)-based requirement management methodology to assist in the collection and the modeling of user requirements. We also provide a convenient procedure and a prototype tool to model, analyze, validate and verify the recorded system requirements, and consequently to ensure that the system can satisfy users’ requirements.

APA, Harvard, Vancouver, ISO, and other styles

15

Salado, Alejandro, and Paul Wach. "Constructing True Model-Based Requirements in SysML." Systems 7, no. 2 (March 28, 2019): 19. http://dx.doi.org/10.3390/systems7020019.

Full text

Abstract:

Some authors suggest that transitioning requirements engineering from the traditional statements in natural language with shall clauses to model-based requirements within a Model-Based Systems Engineering (MBSE) environment could improve communication, requirements traceability, and system decomposition, among others. Requirement elements in the Systems Modeling Language (SysML) fail to fulfill this objective, as they are really a textual requirement in natural language as a model element. Current efforts to directly leverage behavioral and structural models of the system lack an overarching theoretical framework with which to assess the adequacy of how those models are used to capture requirements. This paper presents an approach to construct true model-based requirements in SysML. The presented approach leverages some of SysML’s behavioral and structural models and diagrams, with specific construction rules derived from Wymore’s mathematical framework for MBSE and taxonomies of requirements and interfaces. The central proposition of the approach is that every requirement can be modeled as an input/output transformation. Examples are used to show how attributes traditionally thought of as non-functional requirements can be captured, with higher precision, as functional transformations.

APA, Harvard, Vancouver, ISO, and other styles

16

Bossuyt, Alain. "Functional Requirements." Functional Explanations in Linguistics 1 (January 1, 1986): 127–47. http://dx.doi.org/10.1075/bjl.1.06bos.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Muthukumar, Akila V., Walker Morrell, and Barbara E. Bierer. "Evaluating the frequency of English language requirements in clinical trial eligibility criteria: A systematic analysis using ClinicalTrials.gov." PLOS Medicine 18, no. 9 (September 14, 2021): e1003758. http://dx.doi.org/10.1371/journal.pmed.1003758.

Full text

Abstract:

Background A number of prior studies have demonstrated that research participants with limited English proficiency in the United States are routinely excluded from clinical trial participation. Systematic exclusion through study eligibility criteria that require trial participants to be able to speak, read, and/or understand English affects access to clinical trials and scientific generalizability. We sought to establish the frequency with which English language proficiency is required and, conversely, when non-English languages are affirmatively accommodated in US interventional clinical trials for adult populations. Methods and findings We used the advanced search function on ClinicalTrials.gov specifying interventional studies for adults with at least 1 site in the US. In addition, we used these search criteria to find studies with an available posted protocol. A computer program was written to search for evidence of English or Spanish language requirements, or the posted protocol, when available, was manually read for these language requirements. Of the 14,367 clinical trials registered on ClinicalTrials.gov between 1 January 2019 and 1 December 2020 that met baseline search criteria, 18.98% (95% CI 18.34%–19.62%; n = 2,727) required the ability to read, speak, and/or understand English, and 2.71% (95% CI 2.45%–2.98%; n = 390) specifically mentioned accommodation of translation to another language. The remaining trials in this analysis and the following sub-analyses did not mention English language requirements or accommodation of languages other than English. Of 2,585 federally funded clinical trials, 28.86% (95% CI 27.11%–30.61%; n = 746) required English language proficiency and 4.68% (95% CI 3.87%–5.50%; n = 121) specified accommodation of other languages; of the 5,286 industry-funded trials, 5.30% (95% CI 4.69%–5.90%; n = 280) required English and 0.49% (95% CI 0.30%–0.69%; n = 26) accommodated other languages. Trials related to infectious disease were less likely to specify an English requirement than all registered trials (10.07% versus 18.98%; relative risk [RR] = 0.53; 95% CI 0.44–0.64; p < 0.001). Trials related to COVID-19 were also less likely to specify an English requirement than all registered trials (8.18% versus 18.98%; RR = 0.43; 95% CI 0.33–0.56; p < 0.001). Trials with a posted protocol (n = 366) were more likely than all registered clinical trials to specify an English requirement (36.89% versus 18.98%; RR = 1.94, 95% CI 1.69–2.23; p < 0.001). A separate analysis of studies with posted protocols in 4 therapeutic areas (depression, diabetes, breast cancer, and prostate cancer) demonstrated that clinical trials related to depression were the most likely to require English (52.24%; 95% CI 40.28%–64.20%). One limitation of this study is that the computer program only searched for the terms “English” and “Spanish” and may have missed evidence of other language accommodations. Another limitation is that we did not differentiate between requirements to read English, speak English, understand English, and be a native English speaker; we grouped these requirements together in the category of English language requirements. Conclusions A meaningful percentage of US interventional clinical trials for adults exclude individuals who cannot read, speak, and/or understand English, or are not native English speakers. To advance more inclusive and generalizable research, funders, sponsors, institutions, investigators, institutional review boards, and others should prioritize translating study materials and eliminate language requirements unless justified either scientifically or ethically.

APA, Harvard, Vancouver, ISO, and other styles

18

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

19

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

20

Mohanan, Murali, and Imran Sarwar Bajwa. "Requirements to Class Model via SBVR." International Journal of Open Source Software and Processes 10, no. 2 (April 2019): 70–87. http://dx.doi.org/10.4018/ijossp.2019040104.

Full text

Abstract:

A user's software requirements are represented in natural language or a speech such as English. Translating these requirements into the object-oriented models is a tough process for designers. This article proposes a neoteric approach to generate Unified Modeling Language (UML) class models instantly from software requirement specifications (SRS). Here the authors make use of the Open Natural language processing tool (OpenNLP) for lexical analysis and to generate the necessary parts of speech (POS) tags from these requirement specifications. Then, the Semantics of Business Vocabulary and Rules (SBVR) standard is used to extract the object-oriented elements from the natural language (NL) processed SRS. From this, the authors generate UML class models. The prototype tool can generate accurate models in less time. This automated system for designing object-oriented models from SRS reduces the cost and budget for both the designers and the users.

APA, Harvard, Vancouver, ISO, and other styles

21

Dawood, Omer Salih, and Abd-El-Kader Sahraoui. "From Requirements Engineering to UML using Natural Language Processing – Survey Study." European Journal of Engineering Research and Science 2, no. 1 (January 23, 2017): 44. http://dx.doi.org/10.24018/ejers.2017.2.1.236.

Full text

Abstract:

In the paper process of moving from software requirements to UML diagrams has been studied. It shows the importance of this process and discusses many comparative studies in the field. A questionnaire related to the study was distributed worldwide to many research groups, academia, and industry to know the current status of using requirement management tools, knowledge of using UML in software development, frequently used UML diagrams, and the methodology used to generate UML diagrams from requirements. The paper emphasises that there is a need to do some important research in the area of requirements NLP to obtain UML diagrams, and generalize process of using automatic or semi-automatic methodology to generate UML diagrams from requirements.

APA, Harvard, Vancouver, ISO, and other styles

22

Shepelyov, A. N. "Clarity and Simplicity as Legal Language Requirements." Pravo: istoriya i sovremennost', no. 1 (2019): 021–27. http://dx.doi.org/10.17277/pravo.2019.01.pp.021-027.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Vidya Sagar, Vidhu Bhala R., and S. Abirami. "Conceptual modeling of natural language functional requirements." Journal of Systems and Software 88 (February 2014): 25–41. http://dx.doi.org/10.1016/j.jss.2013.08.036.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Shah, Unnati S., and Devesh C. Jinwala. "Resolving Ambiguities in Natural Language Software Requirements." ACM SIGSOFT Software Engineering Notes 40, no. 5 (September 14, 2015): 1–7. http://dx.doi.org/10.1145/2815021.2815032.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Bajzát, Tünde. "Foreign language requirements in Hungarian job advertisements." EduLingua 3, no. 1 (2017): 19–29. http://dx.doi.org/10.14232/edulingua.2017.1.2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Figueroa-Martinez, Jose, Víctor López-Jaquero, Francisco Luis Gutiérrez Vela, and Pascual González. "Enriching UsiXML language to support awareness requirements." Science of Computer Programming 78, no. 11 (November 2013): 2259–67. http://dx.doi.org/10.1016/j.scico.2012.09.020.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Ferrari, Alessio, Felice Dell'Orletta, Andrea Esuli, Vincenzo Gervasi, and Stefania Gnesi. "Natural Language Requirements Processing: A 4D Vision." IEEE Software 34, no. 6 (November 2017): 28–35. http://dx.doi.org/10.1109/ms.2017.4121207.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Nanduri, Sastry, and Spencer Rugaber. "Requirements Validation via Automated Natural Language Parsing." Journal of Management Information Systems 12, no. 3 (December 1995): 9–19. http://dx.doi.org/10.1080/07421222.1995.11518088.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Liang, Zhengping, Guoqing Wu, and Li Wan. "Lightweight Behavior-Based Language for Requirements Modeling." Journal of Software Engineering and Applications 03, no. 03 (2010): 245–54. http://dx.doi.org/10.4236/jsea.2010.33030.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Gervasi, Vincenzo, and Didar Zowghi. "Reasoning about inconsistencies in natural language requirements." ACM Transactions on Software Engineering and Methodology 14, no. 3 (July 2005): 277–330. http://dx.doi.org/10.1145/1072997.1072999.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Syverson, Paul, and Catherine Meadows. "A formal language for cryptographic protocol requirements." Designs, Codes and Cryptography 7, no. 1-2 (January 1996): 27–59. http://dx.doi.org/10.1007/bf00125075.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Griswold, William G., Richard Wolski, Scott B. Baden, Stephen J. Fink, and Scott R. Kohn. "Programming language requirements for the next millennium." ACM Computing Surveys 28, no. 4es (December 1996): 194. http://dx.doi.org/10.1145/242224.242475.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Dubois, E., J. Hagelstein, E. Lahou, F. Ponsaert, and A. Rifaut. "A knowledge representation language for requirements engineering." Proceedings of the IEEE 74, no. 10 (1986): 1431–44. http://dx.doi.org/10.1109/proc.1986.13644.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Greenspan, Sol J., Alexander Borgida, and John Mylopoulos. "A requirements modeling language and its logic." Information Systems 11, no. 1 (January 1986): 9–23. http://dx.doi.org/10.1016/0306-4379(86)90020-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Misra, Janardan. "Terminological inconsistency analysis of natural language requirements." Information and Software Technology 74 (June 2016): 183–93. http://dx.doi.org/10.1016/j.infsof.2015.11.006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Golumbic, Martin Charles, Moshe Markovich, and Michael Tiomkin. "A knowledge representation language for university requirements." Decision Support Systems 7, no. 1 (January 1991): 33–45. http://dx.doi.org/10.1016/0167-9236(91)90075-m.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Yang, Hui, Anne de Roeck, Vincenzo Gervasi, Alistair Willis, and Bashar Nuseibeh. "Analysing anaphoric ambiguity in natural language requirements." Requirements Engineering 16, no. 3 (May 13, 2011): 163–89. http://dx.doi.org/10.1007/s00766-011-0119-y.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Giannakopoulou, Dimitra, Thomas Pressburger, Anastasia Mavridou, and Johann Schumann. "Automated formalization of structured natural language requirements." Information and Software Technology 137 (September 2021): 106590. http://dx.doi.org/10.1016/j.infsof.2021.106590.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Mefteh, Mariem, Nadia Bouassida, and Hanêne Ben-Abdallah. "Towards naturalistic programming: Mapping language-independent requirements to constrained language specifications." Science of Computer Programming 166 (November 2018): 89–119. http://dx.doi.org/10.1016/j.scico.2018.05.006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

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

41

Kiyavitskaya, Nadzeya, Nicola Zeni, Luisa Mich, and Daniel M. Berry. "Requirements for tools for ambiguity identification and measurement in natural language requirements specifications." Requirements Engineering 13, no. 3 (July 2, 2008): 207–39. http://dx.doi.org/10.1007/s00766-008-0063-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

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

43

Adilova, A., and Z. Zhuyntayeva. "KAZTEST: listening tasks — requirements and experience." Bulletin of the Karaganda University. Philology series 98, no. 2 (June 30, 2020): 13–18. http://dx.doi.org/10.31489/2020ph2/13-18.

Full text

Abstract:

The article describes the listening tasks of the domestic system of assessment of the level of language proficiency in the functional aspect. Kaztest was created to assess the level of linguistic competences of residents of the Republic and foreign citizens in the Kazakh language in accordance with the principles and requirements of international test systems. System includes test tasks on four types of speech activity — speaking, listening, reading and writing. The authors emphasize that test tasks perform not only the function of assessing the level of language proficiency, but also the function of improving language knowledge, thus, are relevant not only for the teacher, but also for the learner of the language. There are certain test job requirements for each unit. For authentic texts on the listening block, recognition and understanding are especially important, so active, recessive, potential vocabulary, ability to language guess, memory of the learning language (tested) play a special role. The KAZTEST system uses different types of understanding classification. The correct understanding of audit test assignments is influenced by linguistic and extralinguistic (psychological, socio-cultural, technical) factors. Analyzing the KAZTEST system, the authors conclude that the correlation of KAZTEST test tasks in all blocks with the programs of educational organizations and institutions of the republic will become one of the levers for maintaining and expanding the sphere of functioning of the state language.

APA, Harvard, Vancouver, ISO, and other styles

44

Calvin, Lisa M., and N. Ann Rider. "Not Your Parents' Language Class: Curriculum Revision to Support University Language Requirements." Foreign Language Annals 37, no. 1 (March 2004): 11–25. http://dx.doi.org/10.1111/j.1944-9720.2004.tb02296.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Ashari, Ahmad, Anny Sari, and Helna Wardhana. "An Extended Rule of the SysML Requirement Diagram Transformation into OWL Ontologies." International Journal of Intelligent Engineering and Systems 14, no. 1 (February 28, 2021): 506–15. http://dx.doi.org/10.22266/ijies2021.0228.47.

Full text

Abstract:

The System Modeling Language (SysML) used the Requirement Diagram to model non-functional requirements, such as response time, size, or system functionality, which cannot be accommodated in the Unified Modeling Language (UML). SysML Requirement Diagram, in its implementation, integrates with several diagrams describing the requirements, which are referred to as additional elements. The absence of transformation rules for these additional elements to become OWL ontology causes difficulties in reading, understanding, and tracking the requirements. In this research, an extended rule of the Requirement Diagram transformation is proposed to solve the problems. First, some transformation rules are defined to make requirements easier to trace and realize the ontology generation's automatic transformation. Second, the time required during transformation processing to prepare and generate the OWL file shows the proposed model's performance. The ontology components produced from this research, such as class, subclass, object property, and data property, can be viewed in Protégé.

APA, Harvard, Vancouver, ISO, and other styles

46

Wang, Taehyung, Astushi Kitazawa, and Phillip Sheu. "Semantic software engineering." Encyclopedia with Semantic Computing and Robotic Intelligence 01, no. 01 (March 2017): 1630012. http://dx.doi.org/10.1142/s2425038416300123.

Full text

Abstract:

One of the most challenging task in software development is developing software requirements. There are two types of software requirements — user requirement (mostly described by natural language) and system requirements (also called as system specifications and described by formal or semi-formal methods). Therefore, there is a gap between these two types of requirements because of inherently unique features between natural language and formal or semi-formal methods. We describe a semantic software engineering methodology using the design principles of SemanticObjects for object-relational software development with an example. We also survey other semantic approaches and methods for software and Web application development.

APA, Harvard, Vancouver, ISO, and other styles

47

Haidrar, Saida, Adil Anwar, Jean-Michel Bruel, and Ounsa Roudies. "A Domain-Specific Language to manage Requirements Traceability." Journal of Software 13, no. 9 (September 2018): 460–80. http://dx.doi.org/10.17706/jsw.13.9.460-480.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

WANG, Ye, Xiaohu YANG, Cheng CHANG, and Alexander J. KAVS. "Improving Natural Language Requirements Quality Using Workflow Patterns." IEICE Transactions on Information and Systems E96.D, no. 9 (2013): 2065–74. http://dx.doi.org/10.1587/transinf.e96.d.2065.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Mikic, Jovica. "Understanding requirements in the foreign language course books." Inovacije u nastavi 28, no. 1 (2015): 51–68. http://dx.doi.org/10.5937/inovacije1501051m.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Leonardi, Maria Carmen, Marcela Ridao, Maria Virginia Mauco, and Laura Felice. "A Natural Language Requirements Engineering Approach for MDA." International Journal of Computer Science, Engineering and Applications 5, no. 1 (February 28, 2015): 1–18. http://dx.doi.org/10.5121/ijcsea.2015.5101.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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!