Log in

Relevant bibliographies by topics / Requirement engineering / Journal articles

To see the other types of publications on this topic, follow the link: Requirement engineering.

Journal articles on the topic 'Requirement engineering'

Author: Grafiati

Published: 4 June 2021

Last updated: 8 June 2024

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 'Requirement engineering.'

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

Pavanasam, Velayutham, and Chandrasekaran Subramaniam. "Understanding Security Requirement Engineering." Indian Journal of Applied Research 1, no. 6 (October 1, 2011): 111–12. http://dx.doi.org/10.15373/2249555x/mar2012/38.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Pavanasam, Velayutham, and Chandrasekaran Subramaniam. "Metabolic Algorithm for Software Requirement Engineering." Advanced Materials Research 267 (June 2011): 639–44. http://dx.doi.org/10.4028/www.scientific.net/amr.267.639.

Full text

Abstract:

The objective of this work is to apply metabolic algorithm to the various items involved during the software development process. The metabolic algorithm is introduced in the rewriting mechanism of membrane or P system considering many time varying functions. Rules for requirement evolution, reaction between items in the membrane, communications between data items, process speed-up and abort rule are being proposed. The metabolic algorithm is applied for the transformation of user requirements into system requirements which can be further segregated into functional as well as non-functional requirements. The requirement elicitation is illustrated and verified to obtain the most expected requirement objects using C# programming language.

APA, Harvard, Vancouver, ISO, and other styles

3

Abdulaziz Abdullah, Alsahli, and Hameed Ullah Khan. "FreGsd: A Framework for Global Software Requirement Engineering." Journal of Software 10, no. 10 (October 2015): 1189–98. http://dx.doi.org/10.17706//jsw.10.10.1189-1198.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Hameed, Isma. "Title: Security in Requirement Engineering for Qualitative Products." International Journal of Engineering and Technology 4, no. 6 (2012): 747–49. http://dx.doi.org/10.7763/ijet.2012.v4.476.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Li, Yan. "CMM Based Requirement Engineering Model in Software Development." Applied Mechanics and Materials 385-386 (August 2013): 1701–4. http://dx.doi.org/10.4028/www.scientific.net/amm.385-386.1701.

Full text

Abstract:

Requirement engineering is the basis of software development, and it is a key factor determines whether a software development can be successful or not. This article first presents the requirement engineering at capability maturity model (CMM). Then the problem in demand development and demand management are discussed in the second section. Finally, a CMM based requirement engineering model is presented. This model provides a more efficient and effective method in requirement engineering. As the most important parts of this model, requirements analysis, form requirement document, review requirement and change control are described in detail.

APA, Harvard, Vancouver, ISO, and other styles

6

Aballa, A. N., D. U. Ebem, P. C. Ezeagwu, and A. N. Ohadoma. "Significance of Requirement Engineering In Educational Technology Development." Advances in Multidisciplinary and scientific Research Journal Publication 1 (July 30, 2022): 61–66. http://dx.doi.org/10.22624/aims/rebk2022-p6.

Full text

Abstract:

ABSTRACT To effectively actualize the advantages of educational technology in the educational sector, the requirements of the learners, the teachers and all the stakeholders must be thoroughly captured by requirement engineering. This chapter shows the different ways in which requirement engineering has managed the requirements to produce software and other educational technology tools and platforms to make teaching and learning more effective. Keywords: Requirement Engineering, Educational Technology, Teaching, learning, Institutions.

APA, Harvard, Vancouver, ISO, and other styles

7

Laborde, Romain, Sravani Teja Bulusu, Ahmad Samer Wazan, Arnaud Oglaza, and Abdelmalek Benzekri. "A Methodological Approach to Evaluate Security Requirements Engineering Methodologies: Application to the IREHDO2 Project Context." Journal of Cybersecurity and Privacy 1, no. 3 (July 13, 2021): 422–52. http://dx.doi.org/10.3390/jcp1030022.

Full text

Abstract:

An effective network security requirement engineering is needed to help organizations in capturing cost-effective security solutions that protect networks against malicious attacks while meeting the business requirements. The diversity of currently available security requirement engineering methodologies leads security requirements engineers to an open question: How to choose one? We present a global evaluation methodology that we applied during the IREHDO2 project to find a requirement engineering method that could improve network security. Our evaluation methodology includes a process to determine pertinent evaluation criteria and a process to evaluate the requirement engineering methodologies. Our main contribution is to involve stakeholders (i.e., security requirements engineers) in the evaluation process by following a requirement engineering approach. We describe our experiments conducted during the project with security experts and the feedback we obtained. Although we applied it to evaluate three requirements engineering methods (KAOS, STS and SEPP) in the context of network security, our evaluation methodology can be instantiated in other contexts and other methods.

APA, Harvard, Vancouver, ISO, and other styles

8

Nour, Tarek, and Noura Albaladi. "Software Requirement Engineering: Traceability Techniques and Tools." International Journal of Computers and Informatics 2, no. 4 (August 28, 2023): 8–23. http://dx.doi.org/10.59992/ijci.2023.v2n4p1.

Full text

Abstract:

Requirement Traceability is one of the activities in managing requirements. It is important for software projects and is affecting the quality of software products. Requirement Traceability is a method to analyze the effect of changes among various software development lifecycle parts. Agile methodologies have been presented as an alternative to traditional software engineering methodologies. The transformation between traditional and agile methodologies is a hard task so the need for traceability grows. This paper introduces traceability research at the requirement engineering on the traceability literature published during the last years. It also investigates and discusses the requirements for traceability issues. It finally presents several requirement traceability techniques and tools to support traceability.

APA, Harvard, Vancouver, ISO, and other styles

9

Ghanyani, Ume-Sauda, Maham Murad, and Waqas Mahmood. "Crowd-based Requirement Engineering." International Journal of Education and Management Engineering 8, no. 3 (May 8, 2018): 43–53. http://dx.doi.org/10.5815/ijeme.2018.03.05.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Fatima, Tazeen, and Waqas Mahmood. "Requirement Engineering in Agile." International Journal of Education and Management Engineering 9, no. 4 (July 8, 2019): 20–33. http://dx.doi.org/10.5815/ijeme.2019.04.03.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Rouibah, Kamel, and Sulaiman Al‐Rafee. "Requirement engineering elicitation methods." Information Management & Computer Security 17, no. 3 (July 17, 2009): 192–217. http://dx.doi.org/10.1108/09685220910978086.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Pabuccu, Yasar Ugur, Ibrahim Yel, Ayse Berrak Helvacioglu, and Büşra Nur Asa. "The Requirement Cube." International Journal of Information System Modeling and Design 13, no. 1 (January 2022): 1–18. http://dx.doi.org/10.4018/ijismd.297046.

Full text

Abstract:

Requirements engineering activities are carried out to come up with right and suitable quality requirements. However, problems in requirements engineering remain even though there is a vast amount of requirement elicitation and writing methods. Methods are either too specific for industry application or focus on a specific part of requirements engineering. This paper proposes a new requirement writing template, the 5W1H requirement cube. The template consists of the answers to six questions (Why, Who, When, Where, What, and How) and links business, user, and functional requirements in a hierarchy within the enterprise business architecture. The template was developed in a prominent Islamic Bank in Turkey and tested on a case study. Authors have rewritten three software requirement specification (SRS) documents with new approach and compared them, showing that new approach has more brief and well-organized documents. BOA Cube software has been developed to implement the 5W1H requirement cube approach within the organization.

APA, Harvard, Vancouver, ISO, and other styles

13

Shah, Tejas. "Design of Security Taxonomy in Requirement Engineering." Computer Science & Engineering: An International Journal 12, no. 1 (February 28, 2022): 43–53. http://dx.doi.org/10.5121/cseij.2022.12106.

Full text

Abstract:

Non Functional Requirements (NFR) are important in all phases of software development and results in quality of software to be built. It is observed that security requirements are incorporated and identified later in the software development life cycle. Security as non functional requirements imposes new challenges in managing confidential data and preserving its integrity. The security requirements and related artefacts must be considered from Requirement Engineering (RE) phase to implementation phase. This paper focuses on new design of taxonomy of security in Requirement Engineering. The design covers the major properties of security which are required in developing any web based, secured, confidential and integrity oriented system.

APA, Harvard, Vancouver, ISO, and other styles

14

Singh, Rajinder. "Impact of Requirement Engineering Processes on Software Development Cost." Indian Journal of Applied Research 4, no. 5 (October 1, 2011): 200–209. http://dx.doi.org/10.15373/2249555x/may2014/61.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Idate, Sonali R., T. Srinivasa Rao, and Dipak J. Mali. "Context-Based Aspect-Oriented Requirement Engineering Model." Engineering, Technology & Applied Science Research 13, no. 2 (April 2, 2023): 10460–65. http://dx.doi.org/10.48084/etasr.5699.

Full text

Abstract:

Mobile applications are context-oriented systems that involve the use of context information while operating. Mobile applications demand tackling context information in the early phase of software engineering. A context-aware system demands a different approach to handling the influence of the context on a system's requirements. Aspect-oriented Requirement Engineering separates concerns throughout requirements, called crosscutting concerns, in the early phase of software development to improve the modularity of complex applications. Capturing requirements embedded within context is a challenging procedure. This study aimed to identify such contextual characteristics of requirements in the early phase of software engineering, using natural language processing techniques, by proposing Context-Based Aspect-Oriented Requirement Engineering (CB-AORE) to visualize the existence of crosscutting concerns. CB-AORE performs context modeling to analyze the context dependency with base requirements and helps the analyst to visualize the correlation of functional and non-functional requirements with context. A case study analyzed the identification of context and its use to identify crosscutting concerns.

APA, Harvard, Vancouver, ISO, and other styles

16

Tang, Rong Fa, and Xiao Yu Huang. "The Application of Requirement Engineering Model in Large Software Development Process." Advanced Materials Research 267 (June 2011): 193–98. http://dx.doi.org/10.4028/www.scientific.net/amr.267.193.

Full text

Abstract:

Requirements engineering is the initial phase of software engineering process in which user requirements are collected, understood, and specified for developing quality software products. The requirement engineering process deserves a stronger attention in the industrial practices. In this paper, we proposed an effective requirement engineering process model for software development that can be used for software development processes to produce a quality product.

APA, Harvard, Vancouver, ISO, and other styles

17

Kolligs, Jason, and Lawrence Dale Thomas. "On the Viability of Diagrams and Drawings as System Requirements." Systems 11, no. 4 (March 28, 2023): 176. http://dx.doi.org/10.3390/systems11040176.

Full text

Abstract:

Requirement expression media is an overlooked consideration in requirements innovation. The path to including media other than natural language requirement sentences begins with determining the viability of media to be used as requirement expressions in systems engineering. This research uses the INCOSE characteristics for individual requirements and sets of requirements as a basis for an assessment of the sufficiency of model diagrams and engineering drawings to express requirements. A critical review of high-impact sources is used to develop characteristic lists for natural language requirement sentences and for model diagrams and engineering drawings. A comparative analysis of the characteristic lists for requirement sentences, model diagrams, and engineering drawings shows that each have the same fundamental characteristics and the differences are based on the ability of the media to represent abstraction. The contribution of this research is the establishment of model diagrams and engineering drawings as viable alternatives to natural language sentences for system engineering requirements expressions.

APA, Harvard, Vancouver, ISO, and other styles

18

Fan, Yan Ping, Qi Sheng Guo, Jie Bai, and Jin Liang Wang. "Design of the Engineering-Oriented Equipment Requirement Demonstration Model Base." Applied Mechanics and Materials 513-517 (February 2014): 3612–16. http://dx.doi.org/10.4028/www.scientific.net/amm.513-517.3612.

Full text

Abstract:

Aiming at the engineering-oriented application requirements of the equipment requirement demonstration, the demonstration process driven by models is regarded as the essential goal. Firstly, the activities and the modeling requirements of the equipment requirement demonstration are analyzed in detail. Thereafter, the model system of the equipment requirement demonstration is built. Focusing on the design of the model base, the model-driven model development process and the design pattern of the models based on MVC are put forward and discussed emphatically. The VV&A mechanism is designed to improve the quality of the models. According to the management requirements of the model base, the model management technology based on ontology is put forward, and then the run mechanism of the model base is studied. Throughout all these designs, the models simulating the equipment requirement demonstration activities can be understood and reused better, and can satisfy the elementary requirements building the toolkits based on these models. Simultaneity, the equipment requirement demonstration activities can be regulated and formalized with the toolkits.

APA, Harvard, Vancouver, ISO, and other styles

19

Mukhopadhyay, Alolika, and Farhad Ameri. "An ontological approach to engineering requirement representation and analysis." Artificial Intelligence for Engineering Design, Analysis and Manufacturing 30, no. 4 (October 4, 2016): 337–52. http://dx.doi.org/10.1017/s0890060416000330.

Full text

Abstract:

AbstractRequirement planning is one of the most critical tasks in the product development process. Despite its significant impact on the outcomes of the design process, engineering requirement planning is often conducted in an ad hoc manner without much structure. In particular, the requirement planning phase suffers from a lack of quantifiable measures for evaluating the quality of the generated requirements and also a lack of structure and formality in representing engineering requirements. The main objective of this research is to develop a formal Web Ontology Language ontology for standard representation of engineering requirements. The proposed ontology uses explicit semantics that makes the ontology amenable to automated reasoning. To demonstrate how the proposed ontology can support requirement analysis and evaluation in engineering design, three possible services enabled by the ontology are introduced in this paper. These services are information content measurement, specificity and completeness analysis, and requirement classification. The proposed ontology and its associated algorithms and tools are validated experimentally in this work.

APA, Harvard, Vancouver, ISO, and other styles

20

Bhukya, Shankar Nayak, and Suresh Pabboju. "Software engineering: risk features in requirement engineering." Cluster Computing 22, S6 (March 13, 2018): 14789–801. http://dx.doi.org/10.1007/s10586-018-2417-3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Faroom, Saeed. "A Review of Requirement Engineering Process Models, Tools & Methodologies." International Journal of Energetica 4, no. 1 (June 30, 2019): 44. http://dx.doi.org/10.47238/ijeca.v4i1.86.

Full text

Abstract:

As we are living in the Era of Computer Science and almost all individuals and the organizations are completely relying on software systems. The requirement engineering is the most vital and important aspect in the success of any software engineering project. Requirement Engineering is a set of different process that works at different levels, which are incorporated at individual and organizational level Projects We need to consult different sources to find requirements. We need to involve personals from the different fields to find a set of quality requirements. The security issues undergoes as soon as early in the 1st phase of requirements. It is shown from the studies that if we consider Quality Process of Requirement Engineering at the phase it results in saving of million dollars. This paper contains the details study and comparison of different RE Process Models and Requirement Elicitation techniques. This paper elaborates the vital aspects of different Requirement Engineering Process models that help in the selection of appropriate model for the Requirement Engineers and practitioners working in the industry. This Paper also Focus on the giving a detailed view of Elicitation techniques and comparative study including the characteristics and their strengths and weakness. Some strengths and weakness found during detailed study are also structured and listed that is also the helpful for the Appropriate selection of RE Process model.

APA, Harvard, Vancouver, ISO, and other styles

22

Gull, Saba, Rahila Umer, Noor Uddin, and Sohrab Khan. "Current Stance on Requirement Prioritization Techniques: Challenges, Opportunities, and Future Directions." VFAST Transactions on Software Engineering 10, no. 2 (June 30, 2022): 198–210. http://dx.doi.org/10.21015/vtse.v10i2.1082.

Full text

Abstract:

Requirement Engineering is an important aspect of Software Engineering, while Requirement prioritization is a crucial phase of Requirement Engineering, specifically in agile development. In today's world, software systems are nothing but the backbone for business organizations. However, for business operations, requirements are changing rapidly, and it seems to be impossible to accomplish the requirements at once. It may be possible with the help of requirement Prioritization as it decreases the risk for failure. It helps implement the most required and prioritized feature given by stakeholders. The entire purpose of this research is to investigate and rate the complete process of Requirement Engineering, specifically the current requirement prioritization techniques, by conducting an extensive literature review. Furthermore, to identify the opportunities, gaps, and challenges for future

APA, Harvard, Vancouver, ISO, and other styles

23

Darlington, M. J., and S. J. Culley. "Current research in the engineering design requirement." Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture 216, no. 3 (March 1, 2002): 375–88. http://dx.doi.org/10.1243/0954405021520049.

Full text

Abstract:

The design requirement is a description of the desired solution to a problem. In engineering design, as in all other, a clear expression of a well-formulated design goal is vital for successful and efficient completion of the design task. The nature of the design requirement and the processes by which it is achieved have been the subject of a wide variety of research. The purpose of the paper is twofold. Firstly, it sets out to collate and discuss representative research in this area in order to give an overview of the current scope of the work. Secondly, it seeks to draw a comparison with the task of developing the design requirement for software and information systems and to initiate a discussion that considers to what extent the substantial body of research in software requirements engineering might help to give an understanding of the design requirement for the engineering design domain. A tentative characterization of the differences between the tasks in the two domains is presented, and representative papers from requirements engineering are used to suggest areas of overlap as a starting point for further investigation.

APA, Harvard, Vancouver, ISO, and other styles

24

Rasheed, Aqsa, Bushra Zafar, Tehmina Shehryar, Naila Aiman Aslam, Muhammad Sajid, Nouman Ali, Saadat Hanif Dar, and Samina Khalid. "Requirement Engineering Challenges in Agile Software Development." Mathematical Problems in Engineering 2021 (May 8, 2021): 1–18. http://dx.doi.org/10.1155/2021/6696695.

Full text

Abstract:

Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.

APA, Harvard, Vancouver, ISO, and other styles

25

Awasthi, Amit, Dr R. N. Raizada Dr. R.N. Raizada, and Rajesh Dubey. "Metrics For Requirement Engineering And Reuirement Tools A Comparative Study." Global Journal For Research Analysis 3, no. 3 (June 15, 2012): 8. http://dx.doi.org/10.15373/22778160/mar2014/72.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Noor Afshan and Kashaf-ad-Dooja. "Analysis and Evaluation of Requirement Engineering Process at NorthBay Solutions." Lahore Garrison University Research Journal of Computer Science and Information Technology 2, no. 1 (March 30, 2018): 21–30. http://dx.doi.org/10.54692/lgurjcsit.2018.020141.

Full text

Abstract:

Requirement engineering has become an essential part as it deals with the process of definition,documentation and maintenance of requirements for software product. Requirement Engineeringstandards like IEEE/ISO/IEC has defined a standardized approach for Requirement Engineeringprocess in developing software solutions. In Pakistan a great range of software houses does notfollows any standardized approach to build software solutions. This research is aiming to help thosegraduating students and others who are not clear about the actual implementation of RequirementEngineering process in the industry. Interviews with Project Leads have been carried out to inquireabout the Requirement Engineering standards and process implementation at ‘NorthBay Solutions’Lahore. Results deduced from this will help students and researchers to get familiar withimplemented solutions of requirement engineering process.

APA, Harvard, Vancouver, ISO, and other styles

27

Udousoro, Isonkobong. "Effective Requirement Engineering Process Model in Software Engineering." Software Engineering 8, no. 1 (2020): 1. http://dx.doi.org/10.11648/j.se.20200801.11.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

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

29

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

30

Ya’u, Badamasi Imam. "Requirement Patterns: An Approach for Streamlining Requirements Engineering in Software Product Families." International Journal of Advanced Trends in Computer Science and Engineering 8, no. 1.4 (September 15, 2019): 507–14. http://dx.doi.org/10.30534/ijatcse/2019/7981.42019.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Nadeem, Muhammad Asgher, and Scott Uk-Jin Lee. "Machine Learning Evaluation of the Requirement Engineering Process Models for Cloud Computing and Security Issues." Applied Sciences 10, no. 17 (August 24, 2020): 5851. http://dx.doi.org/10.3390/app10175851.

Full text

Abstract:

In the requirement engineering phase, the team members work to get the user requirements, comprehend them and specify them for the next process. There are many models for the requirement engineering phase. There is a need to select the best Requirement Engineering model, and integrate it with cloud computing, that can give the best response to the users and software developers and avoid mistakes in the requirement engineering phase. In this study, these models are integrated with the cloud computing domain, and we report on the security considerations of all the selected models. Four requirement engineering process models are selected for this study: the Linear approach, the Macaulay Linear approach, and the Iterative and Spiral models. The focus of this study is to check the security aspects being introduced by the cloud platform and assess the feasibility of these models for the popular cloud environment SaaS. For the classification of the security aspects that affect the performance of these model, a framework is proposed, and we check the results regarding selected security parameters and RE models. By classifying the selected RE models for security aspects based on deep learning techniques, we determine that the Loucopoulos and Karakostas iterative requirements engineering process model performs better than all the other models.

APA, Harvard, Vancouver, ISO, and other styles

32

Duan, Guo Yong, and Jing Yang. "Application Research of rCOS-Based Trusted Requirement Engineering." Advanced Materials Research 658 (January 2013): 662–66. http://dx.doi.org/10.4028/www.scientific.net/amr.658.662.

Full text

Abstract:

With the development of the information age, the demands for computer software have become increasingly complex. Increasing scale, with the development of enterprises, and the reorganization of the work process, which make the requirements change become increasingly frequent. Formal theoretical foundation based on rCOS, leads to integration and refinement for Volere requirements process model. According to the RUP process, a trusted Simple Volere Requirement Model has been constructed to solve the requirements change as a very effective way.

APA, Harvard, Vancouver, ISO, and other styles

33

Abdalmoneim Mohamed Mohamed Khair and Farid Meziane. "Development of framework to support software requirement elicitation using a domain ontology." International Journal of Engineering Research Updates 1, no. 1 (June 30, 2021): 007–16. http://dx.doi.org/10.53430/ijeru.2021.1.1.0037.

Full text

Abstract:

One of the main goals of Software Requirements Engineering is to understand customers' needs and to put their customer needs in requirement. The requirement engineering has several processes one of them are requirement elicitation the requirement elicitation considered as one process of requirement engineering and also considered as important process so the process of elicit the requirement has difficult, due to the incompleteness problem, ontology has player important rule to helps the requirement elicitation by adding more information about the words. in this paper implementing framework by using domain ontology, the frame work implement using java and ontology using protégé, the framework evaluated using requirement in in banking domain, and show the results helps the software developer to choose the requirement.

APA, Harvard, Vancouver, ISO, and other styles

34

Kravari, Kalliopi, Christina Antoniou, and Nick Bassiliades. "SENSE: A Flow-Down Semantics-Based Requirements Engineering Framework." Algorithms 14, no. 10 (October 15, 2021): 298. http://dx.doi.org/10.3390/a14100298.

Full text

Abstract:

The processes involved in requirements engineering are some of the most, if not the most, important steps in systems development. The need for well-defined requirements remains a critical issue for the development of any system. Describing the structure and behavior of a system could be proven vague, leading to uncertainties, restrictions, or improper functioning of the system that would be hard to fix later. In this context, this article proposes SENSE, a framework based on standardized expressions of natural language with well-defined semantics, called boilerplates, that support a flow-down procedure for requirement management. This framework integrates sets of boilerplates and proposes the most appropriate of them, depending, among other considerations, on the type of requirement and the developing system, while providing validity and completeness verification checks using the minimum consistent set of formalities and languages. SENSE is a consistent and easily understood framework that allows engineers to use formal languages and semantics rather than the traditional natural languages and machine learning techniques, optimizing the requirement development. The main aim of SENSE is to provide a complete process of the production and standardization of the requirements by using semantics, ontologies, and appropriate NLP techniques. Furthermore, SENSE performs the necessary verifications by using SPARQL (SPIN) queries to support requirement management.

APA, Harvard, Vancouver, ISO, and other styles

35

Gupta, Ankita, and Chetna Gupta. "A Collaborative Situational Method Engineering Approach for Requirement Gathering." International Journal of Information Retrieval Research 8, no. 1 (January 2018): 1–19. http://dx.doi.org/10.4018/ijirr.2018010101.

Full text

Abstract:

This article re-defines traditional requirement engineering processes by performing exhaustive requirement gathering through an interactive and collaborative communication, where stakeholders are equally involved in capturing and finalizing requirements in the scope of a project. It strongly supports concept of re-usability using principals of situational method engineering where methods are tailor-made per requirements from the method repository (maintained in the cloud). Search and selection of appropriate methods meeting stakeholder's interest is performed using concepts of knowledge discovery and data mining methods over a web interface. Knowledge extraction, in the form of a matched set of requirements is performed at every level of a proposed multi-layered framework, as progression towards a desirable method for reuse. This approach will help in overcoming the challenging tasks of identifying relevant requirements, incorporating change requests and minimizing the number of disagreements between stakeholders and developers.

APA, Harvard, Vancouver, ISO, and other styles

36

Li, Xian Yu, Hua Wang, Jian Qun Zheng, Xiao Kun Li, and Shan Wang. "The Research on the Software Requirement Development of Information System." Applied Mechanics and Materials 513-517 (February 2014): 1854–57. http://dx.doi.org/10.4028/www.scientific.net/amm.513-517.1854.

Full text

Abstract:

Based upon the synopsis of software requirement development, this paper describes the practices of user requirements exploitation, product requirements exploitation, requirements analysis and validation, and then puts forward engineering process relation and requirement development practice. Meanwhile, further works are brought forward. This will benefit the software requirement development of information system.

APA, Harvard, Vancouver, ISO, and other styles

37

Kumar, Rajesh, and Rakesh Kumar. "Optimizing requirement analysis by the use of meta-heuristic in search based software engineering." International Journal of Electrical and Computer Engineering (IJECE) 9, no. 5 (October 1, 2019): 4336. http://dx.doi.org/10.11591/ijece.v9i5.pp4336-4343.

Full text

Abstract:

<p>Requirements analysis is the first phase of software development process and it is one of the main concerns of software engineers. The selection of requirements is a complex problem caused by the heterogeneity of the users and their varied interests and demands. In this paper, it is justified that their is a strong need of optimization in requirement analysis. The paper argues that requirement selection can be viewed as an application area of Search-Based Software Engineering(SBSE). The aim is to justify the claim that requirement engineering can be re-formulated as search problem to which meta-heuristic technique can be applied.</p>

APA, Harvard, Vancouver, ISO, and other styles

38

Subha, R., and Anandakumar Haldorai. "An Efficient Identification of Security Threats in Requirement Engineering Methodology." Computational Intelligence and Neuroscience 2022 (August 18, 2022): 1–14. http://dx.doi.org/10.1155/2022/1872079.

Full text

Abstract:

Today, we completely rely on Information Technology (IT) applications for every aspect of daily life, including business and online transactions. In addition to using these IT-enabled applications for business purposes, we also use WhatsApp, Facebook, and a variety of other IT applications to communicate with others. However, there will undoubtedly be a drawback to every benefit. Since everything is linked to the Internet, there are many opportunities for security to be compromised. To address this, we are working to identify security threats early on in the software development process, specifically during the requirements phase. During the requirement engineering process, an engineer can recognize the security specifications in a more structured manner to create threat-free software. In our research work, we suggest the Identification of Security Threats during Requirement Engineering (ISTDRE) technique for detecting security risks throughout the requirement engineering process. The four points that make up this ISTDRE technique are Hack Point (HP), Speculation Point (SP), Trust Point (TP), and Reliable Point (RP). The new ISTDRE methodology will be validated using a case study of an ERP system involving two currently used methodologies: Model Oriented Security Requirements Engineering (MOSRE) and System Quality Requirements Engineering (SQUARE).

APA, Harvard, Vancouver, ISO, and other styles

39

D., Kavitha, and Ravikumar S. "Software Security Requirement Engineering for Risk and Compliance Management." International Journal of Innovative Technology and Exploring Engineering 10, no. 5 (March 30, 2021): 11–17. http://dx.doi.org/10.35940/ijitee.e8628.0210421.

Full text

Abstract:

The objective of the research work is to propose a software based security requirement engineering model using categorical and morphisms theory. The earlier security requirement engineering models focus different viewpoints on parallel processing and develop rewrite based knowledge centred models but does not include different functional mappings between the security objects to select the best strategy. The security models have not considered the needed security functions that are to be implemented in different environments with different levels of executions. The proposed requirement engineering model is based on the formal theory of category of objects and the morphisms between them in addition to n categories and multiple morphisms that were used to organize the security requirement functional objects of different categories. The on demand security requirement objects, morphisms and the uncertain events in any one of the subsystems are considered to manage this security requirement category as an algebraic data types. The collection of security requirement objects using classification and clustering techniques are implicitly applied by the formation of category and morphism. The risk and compliances both in the form of direct and indirect categories are mapped so as to provide a security assurance functors with minimum risk on the requirements to the next design state. An ‘n’ category and ‘n’ morphic model for software security requirement model is proposed towards for minimum security risks through efficient compliance management techniques.

APA, Harvard, Vancouver, ISO, and other styles

40

Kavitha, D., and S. Ravikumar. "Software Security Requirement Engineering for Risk and Compliance Management." International Journal of Innovative Technology and Exploring Engineering 10, no. 5 (March 30, 2021): 11–17. http://dx.doi.org/10.35940/ijitee.e8628.0310521.

Full text

Abstract:

The objective of the research work is to propose a software based security requirement engineering model using categorical and morphisms theory. The earlier security requirement engineering models focus different viewpoints on parallel processing and develop rewrite based knowledge centred models but does not include different functional mappings between the security objects to select the best strategy. The security models have not considered the needed security functions that are to be implemented in different environments with different levels of executions. The proposed requirement engineering model is based on the formal theory of category of objects and the morphisms between them in addition to n categories and multiple morphisms that were used to organize the security requirement functional objects of different categories. The on demand security requirement objects, morphisms and the uncertain events in any one of the subsystems are considered to manage this security requirement category as an algebraic data types. The collection of security requirement objects using classification and clustering techniques are implicitly applied by the formation of category and morphism. The risk and compliances both in the form of direct and indirect categories are mapped so as to provide a security assurance functors with minimum risk on the requirements to the next design state. An ‘n’ category and ‘n’ morphic model for software security requirement model is proposed towards for minimum security risks through efficient compliance management techniques.

APA, Harvard, Vancouver, ISO, and other styles

41

Salleh, Narishah Mohamed, and Puteri N. E. Nohuddin. "Optimization of software requirement process: An integrated conceptual model of lean six sigma and requirement planning." International Review of Applied Sciences and Engineering 10, no. 2 (December 2019): 125–33. http://dx.doi.org/10.1556/1848.2019.0015.

Full text

Abstract:

Providing quality requirements in Software Engineering is vital to ensure the product developed is able to deploy and function to meet the operational objectives. Software Requirement Engineering is the most complex process because it involves the integration of human, logics and process. Extracting or capturing what customers need and want is called Requirement Elicitation (RE) and it is the most crucial process in requirement engineering. If handled poorly, the cost of the failures would be very expensive. Most of the software projects that failed were due to poor requirements which occurred at RE phase. Thus, enhancing and optimizing the RE methods have been subject to a long research debate to ensure quality requirements are captured. Recently, Lean Six Sigma (LSS) had emerged as part of a continuous improvement in Software Development Life Cycles (SDLC). LSS is known for a systematic and structure business improvement successfully deployed in many fields of industry that contributes a significant gain not only in quality of products and services but also in operational costs and delivery. The objective of the research is to develop an integrated conceptual framework of LSS principles with Software Requirement Engineering methodology to optimize RE process. The article will produce conceptual framework as the comprehensive guidelines to capture quality software requirements.

APA, Harvard, Vancouver, ISO, and other styles

42

van Remmen, Judith Sophie, Dennis Horber, Adriana Lungu, Fan Chang, Sebastiaan van Putten, Stefan Goetz, and Sandro Wartzack. "NATURAL LANGUAGE PROCESSING IN REQUIREMENTS ENGINEERING AND ITS CHALLENGES FOR REQUIREMENTS MODELLING IN THE ENGINEERING DESIGN DOMAIN." Proceedings of the Design Society 3 (June 19, 2023): 2765–74. http://dx.doi.org/10.1017/pds.2023.277.

Full text

Abstract:

AbstractRequirements represent a central element in product development. The large number of requirements inevitably results in an increased susceptibility to errors, an expenditure of time and development costs. The associated problems motivate the application of Artificial Intelligence in the form of Natural Language Processing (NLP). In Requirements Engineering one main task is the classification of requirements which serves as the input in architectural models e.g. in SysML. In mechanical engineering there is still little overview regarding the interface between requirements classification and modelling. This paper provides an overview of the requirement classes and entities used in the literature and analyses their utilisation in modelling. Existing requirements classes usually do not offer the flexibility to be transferred to other domains. However, basic structures can be adopted from those classifications. This enables a clear assignment of existing classes to object classes in modelling. Resulting from the conducted literature study the observed predominant focus of research on the software industry requires an extension of the existing requirement classes and entities to enable further use and transfer to mechanical engineering.

APA, Harvard, Vancouver, ISO, and other styles

43

Surendro, Kridanto, and Cicely Martini Asihwardji. "Hierarchical i* Modeling in Requirement Engineering." TELKOMNIKA (Telecommunication Computing Electronics and Control) 14, no. 2 (June 1, 2016): 784. http://dx.doi.org/10.12928/telkomnika.v14i2.3333.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Priyaradhikadevi, T. "Requirement Engineering for Service Based Systems." IOSR Journal of Computer Engineering 7, no. 2 (2012): 01–08. http://dx.doi.org/10.9790/0661-0720108.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Patil, Shruti, and Roshani Ade. "Software Requirement Engineering Risk Prediction Model." International Journal of Computer Applications 102, no. 2 (September 18, 2014): 1–6. http://dx.doi.org/10.5120/17784-8545.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Jinxin Lin, Mark S. Fox, and Taner Bilgic. "A Requirement Ontology for Engineering Design." Concurrent Engineering 4, no. 3 (September 1996): 279–91. http://dx.doi.org/10.1177/1063293x9600400307.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Surendro, Kridanto, and Cicely Martini Asihwardji. "Hierarchical i* Modeling in Requirement Engineering." TELKOMNIKA (Telecommunication Computing Electronics and Control) 14, no. 2 (June 1, 2016): 784. http://dx.doi.org/10.12928/telkomnika.v14i3.3333.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

FOGARTY, WILLIAM M. "THE REQUIREMENT FOR WARFARE SYSTEMS ENGINEERING." Naval Engineers Journal 98, no. 5 (September 1986): 27–31. http://dx.doi.org/10.1111/j.1559-3584.1986.tb01728.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Rivera, Christian, Javier Poza, Gaizka Ugalde, and Gaizka Almandoz. "A Requirement Engineering Framework for Electric Motors Development." Applied Sciences 8, no. 12 (November 26, 2018): 2391. http://dx.doi.org/10.3390/app8122391.

Full text

Abstract:

The applications using electric motors have increased in the last decade. Some of these applications encounter the need for tailor-made motors that must meet demanding requirements. Therefore, the specification stage of an electric motor is a critical part of its development. If this stage is properly addressed, then future failures in the development process can be avoided. This paper presents a requirement engineering framework to support small-medium electric motors designers/manufacturers with the development of their product. The framework identifies the stakeholders and the tasks that they should undertake to finish a successful requirements specification stage. The framework is made from the designer/manufacturer’s perspective and it emphasizes the derivation of specialized requirements (lower-level). The result of the framework is well-defined requirements that form the design requirements specification of the motor that leads to the beginning of the design stage.

APA, Harvard, Vancouver, ISO, and other styles

50

Sari, Risna, Anggi Muhammad Rifa'i, Muhammad Salimy Ahsan, M Ilham Arief, and Mohammad Rezza Pahlevi. "Understanding of Requirements Engineering using The Three Dimensions of Requirements Engineering Method in Platform Development." International Journal of Engineering Technology and Natural Sciences 5, no. 2 (December 30, 2023): 99–111. http://dx.doi.org/10.46923/ijets.v5i2.218.

Full text

Abstract:

Requirements engineering is a critical activity in a development system project, the increasing need for complexity of software development and the heterogeneity of stakeholders in motivating the development of methods and the need to evaluate the engineering requirements needed and aim to lead to a large scale. This study presents a paper in an empirical form that aims to identify and understand the characteristics of the advantages and limitations of the developed platform so that we can know the challenges that will be faced, such as expectations and input from experts for the development of the platform that we develop so that it can be in accordance with what users expect. We conducted this research with the aim of understanding the engineering requirements in the research we developed by utilizing the three dimensions of the requirements engineering method, which consists of requirement elicitation, requirement specification, and requirement validation and verification. The research we conducted managed to understand the stages of needs engineering by producing many documents that help the platform development process. We get the most important UI value from attractiveness, clarity, efficiency, accuracy, stimulation, and novelty, which is 63.2% with a very interest rating, 55.6 with a very interest rating, 57.9% with a very interest rating, 44.4% with a balanced rating between interesting and very interest, 52.6% with an interesting rating, 42.1% with a very interesting rating. We get product values consisting of attractiveness, clarity, efficiency, accuracy, stimulation, and novelty, namely 68.4% with a very interest rating, 52.6% with an interest ng rating, 52.6% with a very interest rating, 47.4% with a balanced rating between interesting and very interest, 47.4% with a balanced rating between interesting and very interest, 47.4% with a balanced rating between interesting and very interest

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!