To see the other types of publications on this topic, follow the link: Functional requirement.

Journal articles on the topic 'Functional requirement'

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 'Functional requirement.'

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

Binti Zulkipli, Fatin Nur, Saiful Farik Mat Yatin, Nurussobah Hunssai, Muhammad Syawal Bin Mostakim, and Tengku Nisa Zahirah Binti Tengku Hisham. "Archive Records Management System (ARMS): Functional Requirement." Record and Library Journal 7, no. 1 (2021): 17–27. http://dx.doi.org/10.20473/rlj.v7i1.111.

Full text
Abstract:
Background of the Study: This paper present the functional requirement in Archive Records Management System (ARMS) that provide a comprehensive record keeping management system based on the organization function according to the business activities and process.
 Purpose: The purpose of this article is to describe the core functional requirement for record keeping system to support users in performing their task that related to electronic record management system.
 Method: The method used in this article are based on the previous research, guidelines and standards.
 Findings: Fur
APA, Harvard, Vancouver, ISO, and other styles
2

Kumar, B. Sathis. "EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS." Asian Journal of Pharmaceutical and Clinical Research 10, no. 13 (2017): 122. http://dx.doi.org/10.22159/ajpcr.2017.v10s1.19589.

Full text
Abstract:
Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality at
APA, Harvard, Vancouver, ISO, and other styles
3

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 (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
APA, Harvard, Vancouver, ISO, and other styles
4

Han, Cheng Shuang, and Zai Ling Cheng. "Modeling of Automobile Stamping Parts Management System Driven by Use Case." Advanced Materials Research 756-759 (September 2013): 1517–21. http://dx.doi.org/10.4028/www.scientific.net/amr.756-759.1517.

Full text
Abstract:
Requirement analyses based on use case apply to the requirement description of information system. This paper discusses the requirement analysis and modeling of automobile stamping parts management information system based on use case. Starting from analyzing its business flow diagram, the system activity (actor) and its candidate requirements reflecting from its feature checklist are recognized. The system functional requirements and non functional requirements are captured in the form of the use case, then the requirement model of automobile stamping parts management information system is es
APA, Harvard, Vancouver, ISO, and other styles
5

Lupita Sari, Dita, and Choirun Niswatin. "Functional Requirement on Proofreading System." Journal of Software 14, no. 5 (2019): 192–99. http://dx.doi.org/10.17706/jsw.14.5.192-199.

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

Gupta, Varun, Shivam Lohia, Deniz Çetinkaya, and Hye-jin Kim. "Non-functional Requirement Prioritization Approach." International Journal of Software Engineering and Its Applications 11, no. 1 (2017): 61–66. http://dx.doi.org/10.14257/ijseia.2017.11.1.06.

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

Spence, Dave. "The non-functional requirement fallacy." Network Security 2019, no. 4 (2019): 20. http://dx.doi.org/10.1016/s1353-4858(19)30052-2.

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

Wilson, Beth. "Guide to Security Needs and Requirements – Making Security a Functional Requirement." INSIGHT 28, no. 3 (2025): 23–28. https://doi.org/10.1002/inst.12540.

Full text
Abstract:
ABSTRACTThe INCOSE Systems Security Working Group completed a 2‐year project to create a Guide to Security Needs and Requirements targeting both the systems engineering practitioner and the systems security practitioner to help them collaboratively define security needs and requirements that result in a secure system in operation. Starting with a set of anti‐patterns for security requirements, we identified existing tactics that have not produced secure systems in the operational environment. The team then identified an approach to perform needs‐oriented, loss‐driven, capability‐based analysis
APA, Harvard, Vancouver, ISO, and other styles
9

Shah, Tejas, and SV Patel. "A Novel Approach for Specifying Functional and Non-functional Requirements Using RDS (Requirement Description Schema)." Procedia Computer Science 79 (2016): 852–60. http://dx.doi.org/10.1016/j.procs.2016.03.083.

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

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 (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 spe
APA, Harvard, Vancouver, ISO, and other styles
11

Kumar, Devendra, Anil Kumar, and Laxman Singh. "Non-functional Requirements Elicitation in Agile Base Models." Webology 19, no. 1 (2022): 1992–2018. http://dx.doi.org/10.14704/web/v19i1/web19135.

Full text
Abstract:
The elicitation of non-functional and functional needs is one of the most critical jobs of a requirement engineer. This scenario involves the imposition of limits on non-functional needs, whereas functional requirements call for the operation of a system in order to carry out functionality. Over the last few years, agile software development approaches have gained widespread acceptance in the software industry as a problem-solving paradigm. Non-functional requirements (NFRs) are frequently cited as a point of contention in non-functional requirements (NFR) approaches. As well as functional req
APA, Harvard, Vancouver, ISO, and other styles
12

Hudaib, Amjad, Raja Masadeh, Mais Haj Qasem, and Abdullah Alzaqebah. "Requirements Prioritization Techniques Comparison." Modern Applied Science 12, no. 2 (2018): 62. http://dx.doi.org/10.5539/mas.v12n2p62.

Full text
Abstract:
Requirements prioritization is considered as one of the most important approaches in the requirement engineering process. Requirements prioritization is used to define the ordering or schedule for executing requirement based on their priority or importance with respect to stakeholders’ viewpoints. Many prioritization techniques for requirement have been proposed by researchers, and there is no single technique can be used for all projects types. In this paper we give an overview of the requirement process and requirement prioritization concept. We also present the most popular techniques used
APA, Harvard, Vancouver, ISO, and other styles
13

Prihartini, Narti. "Logic Requirement Model of Web Based e-learning in Learning Management System for Features Selection." Jurnal Edukasi dan Penelitian Informatika (JEPIN) 8, no. 2 (2022): 356. http://dx.doi.org/10.26418/jp.v8i2.56422.

Full text
Abstract:
Requirement engineering phase is logically known to check the compliance of application such in web-based e-learning development. This research indicates that basic aspects of web-based e-learning can be used to identify or elicit the early requirement and classify it into the functional and non-functional approach. The research found that even in learning management system (LMS) Based, some of the web-based e-learning are using for different goals. It is challenging to develop a system of web-based e-learning to get the requirement focus at the early phase and select the feature that can fill
APA, Harvard, Vancouver, ISO, and other styles
14

Tiun, S., U. A. Mokhtar, S. H. Bakar, and S. Saad. "Classification of functional and non-functional requirement in software requirement using Word2vec and fast Text." Journal of Physics: Conference Series 1529 (April 2020): 042077. http://dx.doi.org/10.1088/1742-6596/1529/4/042077.

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

Mohd Noor, Nor Farahwahida, and Aslina Saad. "eRequirement Elicitation Techniques for a C-Programming Learning Application." Journal of Technology and Humanities 2, no. 2 (2021): 10–16. http://dx.doi.org/10.53797/jthkkss.v2i2.2.2021.

Full text
Abstract:
Requirement elicitation is a part of the application development process which determines the functional and non-functional requirements of the application. This study has elicited the requirements of a programming learning application by using several requirement elicitation techniques. The purpose of the application is to assist novice programmers in learning C language programming. The requirement elicitation was done by using qualitative approaches in a triangulation strategy. The triangulation involved literature reviews on related existing C-programming applications and semi-structured i
APA, Harvard, Vancouver, ISO, and other styles
16

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 re
APA, Harvard, Vancouver, ISO, and other styles
17

Mim, Habiba Azrin. "AN EFFECTIVE APPROACH FOR ELICITING REQUIREMENTS AND ENSURING TRACEABILITY: A CASE STUDY OF AUTOMATED TELLER MACHINE." International Journal of Software Engineering and Computer Systems 11, no. 1 (2025): 1–15. https://doi.org/10.15282/ijsecs.11.1.2025.1.0133.

Full text
Abstract:
Requirement Elicitation plays a great role in the successful completion of a software project. Elicitation is a productive effort to extricate project-associated information from the stakeholders. To gather complete, concise, and clear requirements, the concept of requirement elicitation allows various analytics and techniques. Requirement elicitation is significant due to the lack of efficiency in accurately articulating their demands towards the intended system. Therefore, requirement engineers realize the need to perform elicitation to ensure that the requirements produced are easily access
APA, Harvard, Vancouver, ISO, and other styles
18

Win, Thant Z., Rozlina Mohamed, and Jamaludin Sallim. "Requirement Prioritization Based on Non-Functional Requirement Classification Using Hierarchy AHP." IOP Conference Series: Materials Science and Engineering 769 (June 9, 2020): 012060. http://dx.doi.org/10.1088/1757-899x/769/1/012060.

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

Shah, Tejas. "Design of Security Taxonomy in Requirement Engineering." Computer Science & Engineering: An International Journal 12, no. 1 (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 de
APA, Harvard, Vancouver, ISO, and other styles
20

Nataliya, Vasiltcova, Panforova Iryna, and Neumyvakina Olga. "IMPROVING A METHOD TO ANALYZE THE REQUIREMENTS FOR AN INFORMATION SYSTEM FOR CONSISTENCY." Eastern-European Journal of Enterprise Technologies 3, no. 2 (105) (2020): 17–27. https://doi.org/10.15587/1729-4061.2020.205518.

Full text
Abstract:
Modern representations of characteristics of functional requirements virtually have no formalized descriptions. That is why the application of the existing methods for the analysis of requirements faces the problems of formal confirmation or refutation of the fact that a functional requirement has an appropriate characteristic. These problems are particularly pronounced in the analysis of functional requirements for consistency. To eliminate these problems, the task was set to develop formalized descriptions of the situations of the complete and partial inconsistency of knowledge-oriented desc
APA, Harvard, Vancouver, ISO, and other styles
21

Rahman, Abdur, Abu Nayem, and Saeed Siddik. "Non-Functional Requirements Classification Using Machine Learning Algorithms." International Journal of Intelligent Systems and Applications 15, no. 3 (2023): 56–69. http://dx.doi.org/10.5815/ijisa.2023.03.05.

Full text
Abstract:
Non-functional requirements define the quality attribute of a software application, which are necessary to identify in the early stage of software development life cycle. Researchers proposed automatic software Non-functional requirement classification using several Machine Learning (ML) algorithms with a combination of various vectorization techniques. However, using the best combination in Non-functional requirement classification still needs to be clarified. In this paper, we examined whether different combinations of feature extraction techniques and ML algorithms varied in the non-functio
APA, Harvard, Vancouver, ISO, and other styles
22

Helander, Martin G., and Li Lin. "Optimal Sequence in Product Design." Proceedings of the Human Factors and Ergonomics Society Annual Meeting 42, no. 6 (1998): 569–73. http://dx.doi.org/10.1177/154193129804200610.

Full text
Abstract:
This paper introduces Axiomatic Design (AD) for top-down design of ergonomics systems. The Independence Axiom was used to demonstrate how design activity can be structured to simplify the design process. Functional Requirements (FR) are first specified at a high level of abstraction and corresponding high level Design Parameters (DP) are generated. Then lower level Functional requirements are generated, and corresponding lower level Design Parameters. To avoid iterative improvements of design, one should strive for a decoupled design. This means that for each Functional Requirement there shoul
APA, Harvard, Vancouver, ISO, and other styles
23

Guo, He Miao, Hai Peng Yu, and Bin Zhang. "QFD-Based Analysis of Quality Functional Requirements of Wooden Acoustic Panels." Applied Mechanics and Materials 44-47 (December 2010): 2661–65. http://dx.doi.org/10.4028/www.scientific.net/amm.44-47.2661.

Full text
Abstract:
As the WAP (Wooden Acoustic Panel) is a kind of newly-emerged functional and decorative building material, this dissertation conducted a scientific analysis on its qualitative and functional design requirements. The method of QFD (Quality Function Deployment) was introduced in this dissertation. Through market survey, voice of customer about qualitative requirements on the WAP was obtained, while a customer needs deployment table was gained based on requirement transformation and clustering. Then a technical requirement deployment table was prepared corresponding to the customers’ requirements
APA, Harvard, Vancouver, ISO, and other styles
24

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 (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 hierar
APA, Harvard, Vancouver, ISO, and other styles
25

Jones, Peter J., and Krista A. Varady. "Are functional foods redefining nutritional requirements?" Applied Physiology, Nutrition, and Metabolism 33, no. 1 (2008): 118–23. http://dx.doi.org/10.1139/h07-134.

Full text
Abstract:
Functional foods are increasing in popularity owing to their ability to confer health and physiological benefits. Nevertheless, the notion that functional foods improve health when providing nutrients at levels above and beyond existing recommended intakes is inconsistent with the definition of requirement. This disparity highlights the need for an alternative definition of nutrient requirement. The present objective is to examine distinctions between optimization of health, as defined by what we currently deem as required intakes, versus adding physiological benefit using bioactive agents fou
APA, Harvard, Vancouver, ISO, and other styles
26

Johansson, Björn, and Markus Lahtinen. "Getting the balance right between functional and non-functional requirements: the case of requirement specification in IT procurement." International Journal of Information Systems and Project Management 1, no. 1 (2022): 5–16. http://dx.doi.org/10.12821/ijispm010101.

Full text
Abstract:
IT procurement represents a business process of high importance, including the ability to articulate requirements that the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i) to show how established terminology for requirement specification is represented in current call for bids for the procurement of IT; and (ii) to introduce an organizing framework that may assist procurers in actively addressing functional requireme
APA, Harvard, Vancouver, ISO, and other styles
27

Tamayo, Edgar, Yasir Khan, Mohamed Al-Hussein, and Ahmed Qureshi. "Integrating machine learning with QFD for selecting functional requirements in construction automation." International Journal of Industrialized Construction 1, no. 1 (2020): 76–88. http://dx.doi.org/10.29173/ijic235.

Full text
Abstract:
An important aspect of the conceptual design is at the customer requirement definition stage, where an optimal number of functional requirements are specified with the application of quality function deployment. To facilitate a systematic specification of functional requirements, state-of-the-art unsupervised machine learning techniques will be introduced in the feature selection of functional requirements. However, the scarcity of references on unsupervised feature selection in the literature reflects the difficulty associated with this topic. At the customer requirement definition phase, thr
APA, Harvard, Vancouver, ISO, and other styles
28

Mokhtar, Umi Asma’, and Zawiyah M. Yusof. "The requirement for developing functional records classification." International Journal of Information Management 35, no. 4 (2015): 403–7. http://dx.doi.org/10.1016/j.ijinfomgt.2015.04.002.

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

Aagaard, Todd. "A Functional Approach to Risks and Uncertainties Under NEPA." Michigan Journal of Environmental & Administrative Law, no. 1.1 (2012): 87. http://dx.doi.org/10.36640/mjeal.1.1.functional.

Full text
Abstract:
The National Environmental Policy Act (NEPA) mandates that federal agencies evaluate the environmental impacts of their proposed actions. This requires agencies to make ex ante predictions about environmental consequences that often involve a significant degree of factual risk or uncertainty. Considerable controversy exists regarding how agencies should address such risks and uncertainties. Current NEPA law adopts a largely ad hoc approach that lacks coherence and analytical rigor. Some environmentalists and legal scholars have called for a greater emphasis on worst-case analysis in environmen
APA, Harvard, Vancouver, ISO, and other styles
30

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 (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 challengi
APA, Harvard, Vancouver, ISO, and other styles
31

AbdelQader, Akram AbdelKarim. "A novel intelligent model for classify and evaluating non-functional security requirements form scenarios." Indonesian Journal of Electrical Engineering and Computer Science 15, no. 3 (2019): 1578. http://dx.doi.org/10.11591/ijeecs.v15.i3.pp1578-1585.

Full text
Abstract:
Software requirements with its functional and non-functional methods are the first important phase in producing a software system with free errors. The functional requirements are the visual actions that may easily evaluated from the developer and from the user, but non-functional requirements are not visual and need a lot of efforts to be evaluated. One of the main important non-functional requirements is security, which focuses on generating secure systems from strangers. Evaluating the security of the system in earlier steps will help to reduce the efforts of reveals critical system threats
APA, Harvard, Vancouver, ISO, and other styles
32

Gu, Pengfei, Yuteng Zhang, Zhen Chen, et al. "X-RMTV: An Integrated Approach for Requirement Modeling, Traceability Management, and Verification in MBSE." Systems 12, no. 10 (2024): 443. http://dx.doi.org/10.3390/systems12100443.

Full text
Abstract:
Formal requirements modeling and traceability management are essential for effectively implementing Model-Based Systems Engineering (MBSE). However, few studies have explored the integration of requirement modeling, traceability management, and verification within MBSE-based systems engineering methodologies. Moreover, the predominant modeling language for MBSE, SysML, lacks sufficient capabilities for requirement description and traceability management and for depicting physical attributes and executable capabilities, making it challenging to verify functional and non-functional requirements
APA, Harvard, Vancouver, ISO, and other styles
33

Rahimi, Nouf, Fathy Eassa, and Lamiaa Elrefaei. "An Ensemble Machine Learning Technique for Functional Requirement Classification." Symmetry 12, no. 10 (2020): 1601. http://dx.doi.org/10.3390/sym12101601.

Full text
Abstract:
In Requirement Engineering, software requirements are classified into two main categories: Functional Requirement (FR) and Non-Functional Requirement (NFR). FR describes user and system goals. NFR includes all constraints on services and functions. Deeper classification of those two categories facilitates the software development process. There are many techniques for classifying FR; some of them are Machine Learning (ML) techniques, and others are traditional. To date, the classification accuracy has not been satisfactory. In this paper, we introduce a new ensemble ML technique for classifyin
APA, Harvard, Vancouver, ISO, and other styles
34

Salado, Alejandro, and Paul Wach. "Constructing True Model-Based Requirements in SysML." Systems 7, no. 2 (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 t
APA, Harvard, Vancouver, ISO, and other styles
35

Ur Rehman, Shafiq, Muhammad Aoun, and Abdul Qayoom. "Selection Criteria for Requirement Prioritization Techniques for software development: Data Analysis." Asian Bulletin of Big Data Management 3, no. 2 (2023): 201–15. http://dx.doi.org/10.62019/abbdm.v3i2.60.

Full text
Abstract:
Requirement analysis is a critical stage in the software development lifecycle that drives project success. Elicitation techniques that are in line with stakeholders' needs, including both functional and non-functional factors, have a significant impact on software results. Finding the best approach to requirement prioritising is difficult, even with the wide range of approaches available. Value-based requirements are carefully woven into particular priority criteria by this study, which pioneers an approach that assesses requirement prioritisation techniques based on four important elements.
APA, Harvard, Vancouver, ISO, and other styles
36

Arshad, Sidra, Hafiza Tahira Fazal, and Tahir Nawaz. "Empirical and Statistical Study of Elicitation Complications." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 15, no. 7 (2016): 6940–46. http://dx.doi.org/10.24297/ijct.v15i7.3780.

Full text
Abstract:
The performance of Requirement Engineering is like framework for software development process. All-inclusive software has four mainstays of requirement engineering processes i.e. Functional and non-functional requirements, design,implementation and testing build the complete software fortification on top of the mainstays. Requirement engineers have to face numerous challenges to develop successful and impressive software. Requirements Engineering (RE) leads software development process. Different constraints and needs of users are explored as well as hitches in previous system are depicted. Th
APA, Harvard, Vancouver, ISO, and other styles
37

Sheet, Sama Emad, and Ibrahim Ahmed Saleh. "Software Requirement Specifications Using Intelligent Technical: Literature Review." International Research Journal of Innovations in Engineering and Technology 08, no. 08 (2024): 273–78. http://dx.doi.org/10.47001/irjiet/2024.808032.

Full text
Abstract:
Software requirement is become more important in recent because the development which witness in projects, badly executed requirements engineering steps can result in bad quality software and more cost for expensive maintenance. Manual classification of requirements is difficult, time-consuming, and expensive, especially in large projects and is written as a Software Requirements Specification (SRS) document. For this reason, automating software requirements classification helps in obtaining higher accuracy and saving time and effort. Most of researcher applied Intelligence techniques algorith
APA, Harvard, Vancouver, ISO, and other styles
38

Park, Huijae, Wongyu Lee, and Jamee Kim. "Development of Programming Log Collection System Requirements Using Interface Requirement Analysis Techniques." JOIV : International Journal on Informatics Visualization 6, no. 1-2 (2022): 162. http://dx.doi.org/10.30630/joiv.6.1-2.938.

Full text
Abstract:
As software affects each industry, companies are increasingly trying to recruit talent. Despite the interest and investment of companies, it is difficult to find talents with technical expertise and specialization in a specific field at the same time. As a result, companies have begun to discover talents who can overcome their lack of expertise through talents with high problem-solving skills. Countries worldwide that felt the need to discover competitive talents began to show changes in education for nurturing talents. In particular, the results of the expansion and increase of programming ed
APA, Harvard, Vancouver, ISO, and other styles
39

Wang, Hui Ling, Li Peng, and Yu Cheng Ding. "Components Association Mechanism Supporting Requirements Tracing." Advanced Materials Research 998-999 (July 2014): 591–96. http://dx.doi.org/10.4028/www.scientific.net/amr.998-999.591.

Full text
Abstract:
Requirements Traceability has a very important role in the entire application development lifecycle. As for the problem of manual creating requirement traceability relationship time-consuming and error-prone effort problem, this paper proposed a new component-based dynamic requirement traceability model. The model incorporates the requirements specification model and component functionality tree model to format requirements documents and component library. Establish requirements traceability relationships through mutual matching between component facet functional items and requirement document
APA, Harvard, Vancouver, ISO, and other styles
40

Satria, Deki. "Implementasi User Centered Requirements Engineering dalam Pencarian Kebutuhan Sistem eLearning." Journal of Information System Research (JOSH) 3, no. 4 (2022): 437–45. http://dx.doi.org/10.47065/josh.v3i4.1618.

Full text
Abstract:
Covid 19 pandemic force a lot of educational institution to shift their learning process from direct learning into indirect learning via eLearning. In fact, a lot of obstacle found when implementing effective eLearning system. This research use User Centered Requirement Engineering as methodology to find the system requirement based on the obstacle found. The main obstacles from this research are lack of interaction between the members of the eLearning, boredom and hard to fulfill the user expectations. The functional requirements to tackle this problem circle around the community functionalit
APA, Harvard, Vancouver, ISO, and other styles
41

Wardhono, Wibisono Sukmo, Herman Tolle, Ratih Kartika Dewi, and Lutfi Fanani. "Analisis Kebutuhan Pengguna pada Pengembangan Malang Virtual Tourism dengan Ambience Lingkungan Terintegrasi." Proceedings Series on Physical & Formal Sciences 6 (October 13, 2023): 187–91. http://dx.doi.org/10.30595/pspfs.v6i.868.

Full text
Abstract:
The use of VR in the tourism business continues to increase. The use of VR for tourism is known as virtual tourism. virtual tourism can simulate tourist destinations using a virtual environment (VE). Virtual tourism is expected to enhance the experience for tourists and attract new markets to tourist destinations. Malang City is one of the tourist destinations in East Java, and is always visited by both domestic and foreign tourists. However, Malang City is still not a major destination in tourism, compared to Batu City (Kota Batu) and Malang Regency (Kabupaten Malang), this is due to the lack
APA, Harvard, Vancouver, ISO, and other styles
42

Singh, V., F. Welz, and R. H. Weston. "Functional Interaction Management: A Requirement for Software Interoperability." Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture 208, no. 4 (1994): 289–305. http://dx.doi.org/10.1243/pime_proc_1994_208_090_02.

Full text
Abstract:
There is a much increased demand for a degree of interworking between software packages as it is no longer reasonable to expect a single application to be able to do its job without support or reference to data and events that are handled by other closely related application systems. In practice, it is essential to help ensure and maintain discipline and harmony to enable graceful co-operation among interoperating software components. Functional interaction management is identified as a vital service requirement necessary to help address this issue of software interoperability. Current manufac
APA, Harvard, Vancouver, ISO, and other styles
43

Lutters, D., and R. ten Klooster. "Functional requirement specification in the packaging development chain." CIRP Annals 57, no. 1 (2008): 145–48. http://dx.doi.org/10.1016/j.cirp.2008.03.052.

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

Liu, Jin Wei, Tian Min Guan, Yong Chen, and Li Jun Shan. "Design Method of the Skull Restoration Based on User-Centered." Applied Mechanics and Materials 470 (December 2013): 396–99. http://dx.doi.org/10.4028/www.scientific.net/amm.470.396.

Full text
Abstract:
The user needs during the skull restoration design were classified into functional requirement, physiological requirement and emotional requirement. The diagram of user-centered design in the skull prosthesis was drawn. The skull restoration formulas of titanium plate strength, compressive stiffness, bending stiffness and skull prosthesis manufacturing error were established. The hierarchy of the emotional design in the skull prosthesis was drawn. Through the analysis and research on the functional requirement, physiological requirement and emotional requirement, the user-centered design idea
APA, Harvard, Vancouver, ISO, and other styles
45

Majeed, Bismal, and Nosheen Sabahat. "REQUIREMENTS CHANGE MANAGEMENT (RCM) TOOL FOR PAKISTAN SOFTWARE INDUSTRY." Pakistan Journal of Scientific Research 3, no. 2 (2024): 190–200. http://dx.doi.org/10.57041/pjosr.v3i2.1018.

Full text
Abstract:
The requirement engineering process is the initial and critical phase of the software development life cycle. Project success heavily depends on requirements elicitation and their management. Requirement change management is a vital aspect of requirement engineering. Incomplete understanding among stakeholders, technological shifts, functional improvements, and evolving business landscapes often trigger requirements changes. Continuous changes demand meticulous tracking and effective management to prevent project failure. Implementing a formalized approach to requirements change management is
APA, Harvard, Vancouver, ISO, and other styles
46

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 (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 engineer
APA, Harvard, Vancouver, ISO, and other styles
47

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 (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 engineer
APA, Harvard, Vancouver, ISO, and other styles
48

Yang, Yuan. "Study on Measurement Error Test Method of On-Line Insulation Monitoring Device for Capacitive Equipment." Applied Mechanics and Materials 373-375 (August 2013): 844–47. http://dx.doi.org/10.4028/www.scientific.net/amm.373-375.844.

Full text
Abstract:
The dielectric characteristic parameter, such as capacitance value, the dielectric loss tangent and leakage current values will change when insulation degradation occurs in capacitive equipment, thus the insulation on-line monitoring devices were used for the insulation state monitoring. At present, the monitoring mode, functional requirements, stability requirement, reliability requirement, and the access security impact has not been fully unified among different manufacturers. For the purpose of standardization of the design, production, testing and operation management of the device, studie
APA, Harvard, Vancouver, ISO, and other styles
49

Guerra García, César Arturo, Ismael Caballero, Marco Cardenas Juarez, and José Reyes Juárez Ramírez. "A proposal to consider aspects of quality in the software development." Journal on Advances in Theoretical and Applied Informatics 2, no. 2 (2016): 12. http://dx.doi.org/10.26729/jadi.v2i2.2103.

Full text
Abstract:

 
 
 Users need trusting in data managed by software applications that are part of Information Systems (IS), which supposes that organizations should assuring adequate levels of quality in data that are managed in their IS. Therefore, the fact that an IS can manage data with an adequate level of quality should be a basic requirement for all organizations. In order to reach this basic requirement some aspects and elements related with data quality (DQ) should be taken in account from the earliest stages of development of software applications, i.e. “data quality by design”. Sinc
APA, Harvard, Vancouver, ISO, and other styles
50

Peng, Xia, and Ping Zhu. "Requirement Analysis of Storage Management System." Applied Mechanics and Materials 263-266 (December 2012): 1438–41. http://dx.doi.org/10.4028/www.scientific.net/amm.263-266.1438.

Full text
Abstract:
The storage management system manages and controls for storage in-out stock activities, and has an important significance for coordinating production and operation of enterprise, improving economic efficiency. Requirement analysis is the basis of software development, mainly is functional requirement analysis and performance requirement analysis. First, do the functional requirement analysis, through analysis the business processes, analysis the main functions and processes of system with data flow diagram, and list the buyer, purchase commodity information, sales production, commodity stock t
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!