Log in

Relevant bibliographies by topics / Functional and non-functional requirements / Journal articles

To see the other types of publications on this topic, follow the link: Functional and non-functional requirements.

Journal articles on the topic 'Functional and non-functional requirements'

Author: Grafiati

Published: 4 June 2021

Last updated: 15 February 2022

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

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Functional and non-functional requirements.'

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

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

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

1

Paradkar, Sameer S. "A Framework for Modeling Non-Functional Requirements for Business-Critical Systems." International Journal of Innovative Research in Computer Science & Technology 9, no. 1 (January 2021): 15–19. http://dx.doi.org/10.21276/ijircst.2021.9.1.3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Kaur, Harsimran, and Dr Ashish Sharma. "Non-Functional Requirements Research: Survey." International Journal of Science and Engineering Applications 3, no. 6 (December 20, 2014): 172–82. http://dx.doi.org/10.7753/ijsea0306.1003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Alsaleh, Saad, and Haryani Haron. "The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study." Lecture Notes on Software Engineering 4, no. 2 (May 2016): 157–61. http://dx.doi.org/10.7763/lnse.2016.v4.242.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Cleland-Huang, Jane, Raffaella Settimi, Xuchang Zou, and Peter Solc. "Automated classification of non-functional requirements." Requirements Engineering 12, no. 2 (March 23, 2007): 103–20. http://dx.doi.org/10.1007/s00766-007-0045-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

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

6

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Matsumoto, Yuuma, Sayaka Shirai, and Atsushi Ohnishi. "A Method for Verifying Non-Functional Requirements." Procedia Computer Science 112 (2017): 157–66. http://dx.doi.org/10.1016/j.procs.2017.08.006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Nogueira, Luis, António Barros, Cristina Zubia, David Faura, Daniel Gracia Pérez, and Luis Miguel Pinho. "Non-functional requirements in the ELASTIC architecture." ACM SIGAda Ada Letters 40, no. 1 (October 20, 2020): 85–90. http://dx.doi.org/10.1145/3431235.3431243.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Ameller, David, Claudia Ayala, Jordi Cabot, and Xavier Franch. "Non-functional Requirements in Architectural Decision Making." IEEE Software 30, no. 2 (March 2013): 61–67. http://dx.doi.org/10.1109/ms.2012.176.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Aburub, Faisal, Mohammed Odeh, and Ian Beeson. "Modelling non-functional requirements of business processes." Information and Software Technology 49, no. 11-12 (November 2007): 1162–71. http://dx.doi.org/10.1016/j.infsof.2006.12.002.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Shah, Unnati, Sankita Patel, and Devesh C. Jinwala. "Detecting Intra-Conflicts in Non-Functional Requirements." International Journal of Uncertainty, Fuzziness and Knowledge-Based Systems 29, no. 03 (May 27, 2021): 435–61. http://dx.doi.org/10.1142/s0218488521500197.

Full text

Abstract:

When specifying user requirements, not only is it critical to ensure correct and unambiguous specification of functional requirements, but also that of Non-Functional Requirements (NFRs). A critical success factor in Requirements Engineering (RE) involves recognizing conflicts among NFRs specified by multiple stakeholders having differing concerns, priorities, and responsibilities. There indeed are numerous attempts made in the literature to resolve the conflicts between two NFRs, with the traditional view of considering the two NFRs different from each other e.g. security conflicting with the availability. In this paper, however, we propose that to introduce fine-grained conflict resolution – by also focusing on those situations where one NFR conflicts with another NFR of the same type. For ease of understanding, we propose to differentiate such conflicts by coining the term intra-conflicts. Thus, we propose fine-grained conflict resolution – by focusing on the notion of resolving conflicts between two NFRs of the same type. Needless to say, non-detection of any conflict between two NFRs – whether the NFRs are of the same type or not – at an early stage of RE, leads to higher costs for changes. The process of conflict resolution is essentially intuitive and hence is iterative. Our proposal hence is motivated by a view that differentiating the inter-conflicts with intra-conflicts, helps one in better focusing on the conflict resolution. We also propose an approach that allows a requirements analyst to semi-automatically identify intra-conflicts among NFRs at an early stage of RE using natural language processing, machine learning, and ontology-based semantic analysis. The controlled experiments, conducted on five publicly available datasets, achieve an average recall, precision, and F-measure of 0.57, 0.77, and 0.65 respectively.

APA, Harvard, Vancouver, ISO, and other styles

12

Becker, Pablo, Guido Tebes, Denis Peppino, and Luis Olsina. "Applying an Improving Strategy that embeds Functional and Non-Functional Requirements Concepts." Journal of Computer Science and Technology 19, no. 2 (October 10, 2019): e15. http://dx.doi.org/10.24215/16666038.19.e15.

Full text

Abstract:

Organizations should set and reach business goals for varied purposes using the suitable strategies. Basically, a strategy specifies the activities, methods and another related resources that should be considered in order to achieve a given goal purpose. Goal purposes and their associated strategies can aim at evaluating, testing, developing, or maintaining some entity. Some concrete evaluation purposes such as to understand or monitor can be achieved by strategies embracing non-functional requirements definition, measurement, evaluation and analysis activities. Other specific evaluation purposes such as to improve or control also imply changing the target entity; therefore, strategies should embrace functional requirements definition activities as well. Moreover, specific development and maintenance purposes always involve functional requirements. In this work, we relate business and information need goals with functional and non- functional requirements concepts, which are paramount for well-defined strategies. Therefore, we specify vocabularies for them, and illustrate the applicability of an improving strategy –which embeds these concepts- in the context of a running example. Having well-structured vocabularies serving as common ground for diverse strategies may promote a more effective operationalization of projects dealing with evaluation, testing, development and maintenance goal purposes.

APA, Harvard, Vancouver, ISO, and other styles

13

FrancisXavierChristopher, D., and E. Chandra. "Goal Oriented Requirements Engineering for Non-functional Factors." International Journal of Computer Applications 52, no. 7 (August 30, 2012): 18–23. http://dx.doi.org/10.5120/8214-1634.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Xu, Lihua, Hadar Ziv, Thomas A. Alspaugh, and Debra J. Richardson. "An architectural pattern for non-functional dependability requirements." Journal of Systems and Software 79, no. 10 (October 2006): 1370–78. http://dx.doi.org/10.1016/j.jss.2006.02.061.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Izukura, S., S. Hosono, H. Sakaki, E. Numata, K. Kimita, and Y. Shimomura. "Bridging Non-functional Requirements and IT Service Design." Procedia CIRP 30 (2015): 24–29. http://dx.doi.org/10.1016/j.procir.2015.02.104.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Khan, Fazlullah, Syed Roohullah Jan, Muhammad Tahir, Shahzad Khan, and Farman Ullah. "Survey: Dealing Non-Functional Requirements at Architecture Level." VFAST Transactions on Software Engineering 9, no. 2 (April 20, 2016): 7. http://dx.doi.org/10.21015/vtse.v9i2.410.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Grimshaw, David J., and Godfrey W. Draper. "Non-functional requirements analysis: deficiencies in structured methods." Information and Software Technology 43, no. 11 (October 2001): 629–34. http://dx.doi.org/10.1016/s0950-5849(01)00171-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Xu, Lihua, Hadar Ziv, Debra Richardson, and Thomas A. Alspaugh. "An architectural pattern for non-functional dependability requirements." ACM SIGSOFT Software Engineering Notes 30, no. 4 (July 2005): 1–6. http://dx.doi.org/10.1145/1082983.1083219.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Affleck, A., A. Krishna, and N. R. Achuthan. "Non-Functional Requirements Framework: A Mathematical Programming Approach." Computer Journal 58, no. 5 (April 8, 2014): 1122–39. http://dx.doi.org/10.1093/comjnl/bxu027.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Zhang, Xuan, and Xu Wang. "Tradeoff Analysis for Conflicting Software Non-Functional Requirements." IEEE Access 7 (2019): 156463–75. http://dx.doi.org/10.1109/access.2019.2949218.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Alexander, I. "Misuse cases help to elicit non-functional requirements." Computing and Control Engineering 14, no. 1 (February 1, 2003): 40–45. http://dx.doi.org/10.1049/cce:20030108.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Chouali, Samir, Ahmed Hammad, and Hassan Mountassir. "Assembling Components using SysML with Non-Functional Requirements." Electronic Notes in Theoretical Computer Science 295 (May 2013): 31–47. http://dx.doi.org/10.1016/j.entcs.2013.04.003.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Sivess, V. "Non-functional requirements in the software development process." Software Quality Journal 5, no. 4 (December 1996): 285–94. http://dx.doi.org/10.1007/bf00209186.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Mahmoud, Anas, and Grant Williams. "Detecting, classifying, and tracing non-functional software requirements." Requirements Engineering 21, no. 3 (May 4, 2016): 357–81. http://dx.doi.org/10.1007/s00766-016-0252-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Gross, Daniel, and Eric Yu. "From Non-Functional Requirements to Design through Patterns." Requirements Engineering 6, no. 1 (February 1, 2001): 18–36. http://dx.doi.org/10.1007/s007660170013.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Jha, Nishant, and Anas Mahmoud. "Mining non-functional requirements from App store reviews." Empirical Software Engineering 24, no. 6 (June 7, 2019): 3659–95. http://dx.doi.org/10.1007/s10664-019-09716-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

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

28

Hidalgo, Reynald Jay F., and Proceso L. Fernandez. "Functional Requirements Identification Using Item-to-Item Collaborative Filtering." International Journal of Information and Education Technology 5, no. 10 (2015): 758–62. http://dx.doi.org/10.7763/ijiet.2015.v5.606.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Gupta, Varun, Raj Kumar Chopra, and Durg Singh Chauhan. "Status of Non-Functional Requirements in Mobile Application Development." Journal of Information Technology Research 10, no. 1 (January 2017): 59–84. http://dx.doi.org/10.4018/jitr.2017010105.

Full text

Abstract:

Non-functional requirements determine the acceptance of the software application amongst its stakeholders apart from the desired functionality yet they are mostly neglected by the software development organizations. Efforts are made to enhance the success rate of the mobile app product; however, there is a lack of empirical studies available for analyzing the contribution of nonfunctional requirements towards the product success. In order to suggest mechanisms for improving product success rates, it is important to undertake the empirical study through surveys and case studies in industrial settings to analyze the software development practices focused on non-functional requirements. The analysis of data collected through empirical methods suggests that non-functional requirements are handled in the rough adhoc fashion and the number of implemented non-functional requirements is less with respect to number of implemented functional requirements. The contribution of non-functional requirements to overall development cost and time is lesser due to lesser number of requirements that undergo implementation but will grow to higher extend as their number will increase. The impact of non-functional requirements on product success rates, failure rates, overall cost and development time varies with type of development, size of organization and complexity of the undertaken mobile app projects.

APA, Harvard, Vancouver, ISO, and other styles

30

Sunner, Daminderjit, and Harpreet Bajaj. "Classification of Functional and Non-functional Requirements in Agile by Cluster Neuro-Genetic Approach." International Journal of Software Engineering and Its Applications 10, no. 10 (October 31, 2016): 129–38. http://dx.doi.org/10.14257/ijseia.2016.10.10.13.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Ahmad, Manzoor, Nicolas Belloir, and Jean-Michel Bruel. "Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems." Journal of Systems and Software 107 (September 2015): 50–70. http://dx.doi.org/10.1016/j.jss.2015.05.028.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Samra, Hardeep Singh. "Study on Non Functional Software Testing." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 4, no. 1 (February 1, 2013): 151–55. http://dx.doi.org/10.24297/ijct.v4i1c.3115.

Full text

Abstract:

Improving software quality involves reducing the quantity of defects within the final product and identifying the remaining defects as early as possible. It involves both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. In fact, defects found earlier in the development lifecycle cost dramatically less to repair than those found later. However, engineers cannot address non-functional quality requirements such as reliability, security, performance and usability early in the lifecycle using the same tools and processes that they use after coding and at later phases. Approaches such as stress testing for reliability, measuring performance and gauging user response to determine usability are inherently post-integration techniques. Accordingly, defects found with these tools are more disruptive and costly to fix. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. This research highlights the sporadic industry acceptance of some popular methods for designing for non-functional requirements and suggests some practical approaches that are applicable for companies that also must consider the demands of schedule and cost.

APA, Harvard, Vancouver, ISO, and other styles

33

Hudaib, Amjad, Raja Masadeh, Mais Haj Qasem, and Abdullah Alzaqebah. "Requirements Prioritization Techniques Comparison." Modern Applied Science 12, no. 2 (January 15, 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 to prioritize the software project requirements and a compression between these techniques. On the other hand, we spot the light on the importance of involving the non-functional requirements prioritization because of the great effects of non-functional on project success and quality; some approaches that used in prioritize non-functional requirements are discussed in this paper, in addition a general model is proposed based on reviewing the prioritization techniques in order to suggests a best suited technique for specific projects according to decision makers parameters.

APA, Harvard, Vancouver, ISO, and other styles

34

Xu, Hong. "Extended Web Services Model Design for Non-Functional Requirements." Applied Mechanics and Materials 63-64 (June 2011): 855–58. http://dx.doi.org/10.4028/www.scientific.net/amm.63-64.855.

Full text

Abstract:

To manage web services, it needs to monitors quality of them periodically when changing their status like availability, performance and security policy. The non-functional requirements of web services based on QoS parameters has been presented in this paper for the purpose of finding the best available web service during Web services discovery process. We also presented an extended web services framework based on SOA structure for providing information about quality of web services and build a prototype for applying quality factors.

APA, Harvard, Vancouver, ISO, and other styles

35

Abhinay, B. Sai, T. S. K. M. D. Abhishek, and K. Madhavi. "Estimating Non-Functional Requirements Using Different Mobile Operating Systems." International Journal of Advanced Research in Computer Science and Software Engineering 7, no. 6 (June 30, 2017): 468–73. http://dx.doi.org/10.23956/ijarcsse/v7i6/0210.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Rosa, Nelson Souto, Paulo Roberto Freire Cunha, and George Roger Ribeiro Justo. "An approach for reasoning and refining non-functional requirements." Journal of the Brazilian Computer Society 10, no. 1 (July 2004): 59–81. http://dx.doi.org/10.1590/s0104-65002004000200006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Mahalakshmi, K., R. Prabhakar, and V. Balakrishnan. "Optimizing Support Vector Machine for Classifying Non Functional Requirements." Research Journal of Applied Sciences, Engineering and Technology 7, no. 17 (May 5, 2014): 3643–48. http://dx.doi.org/10.19026/rjaset.7.717.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Gómez Sotelo, K. I., C. Baron, P. Esteban, C. Y. A. Gutiérrez Estrada, and L. de J. Laredo Velázquez. "How to find non-functional requirements in system developments." IFAC-PapersOnLine 51, no. 11 (2018): 1573–78. http://dx.doi.org/10.1016/j.ifacol.2018.08.272.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Chung, Lawrence, Brian A. Nixon, and Eric Yu. "Dealing with change: An approach using non-functional requirements." Requirements Engineering 1, no. 4 (December 1996): 238–60. http://dx.doi.org/10.1007/bf01587102.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Zhu, Ming-Xun, Xin-Xing Luo, Xiao-Hong Chen, and Desheng Dash Wu. "A non-functional requirements tradeoff model in Trustworthy Software." Information Sciences 191 (May 2012): 61–75. http://dx.doi.org/10.1016/j.ins.2011.07.046.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Rosa, Nelson Souto, Paulo Roberto Freire Cunha, and George Roger Ribeiro Justo. "An approach for reasoning and refining non-functional requirements." Journal of the Brazilian Computer Society 10, no. 1 (February 2004): 62–84. http://dx.doi.org/10.1007/bf03192354.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Serral, Estefanía, Paolo Sernani, and Fabiano Dalpiaz. "Personalized adaptation in pervasive systems via non-functional requirements." Journal of Ambient Intelligence and Humanized Computing 9, no. 6 (November 3, 2017): 1729–43. http://dx.doi.org/10.1007/s12652-017-0611-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Tisha, Tahmina Akter, and Mir Moynuddin Ahmed Shibly. "Non-Functional Requirements for Blockchain: Challenges and New Directions." IOP Conference Series: Materials Science and Engineering 1110, no. 1 (March 1, 2021): 012016. http://dx.doi.org/10.1088/1757-899x/1110/1/012016.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

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 (January 31, 2017): 61–66. http://dx.doi.org/10.14257/ijseia.2017.11.1.06.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

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 (September 1, 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. Security threats found because of leaking of security scenarios in requirement phase. In this paper, we purpose an intelligent model to extract and evaluate security features from scenarios based on set of security system goals and a set of security requirements saved on rich story scenarios dataset (RSSD). This model will used a support vector machine (SVM) classifier to classify the security requirement based on RSS dataset. The using of SVM will enhance the overall process of evaluating the security requirements. The results show a significant enhancement in security improvements.

APA, Harvard, Vancouver, ISO, and other styles

47

Zubcoff, Jose, Irene Garrigós, Sven Casteleyn, Jose-Norberto Mazón, Jose-Alfonso Aguilar, and Francisco Gomariz-Castillo. "Evaluating different i*-based approaches for selecting functional requirements while balancing and optimizing non-functional requirements: A controlled experiment." Information and Software Technology 106 (February 2019): 68–84. http://dx.doi.org/10.1016/j.infsof.2018.09.004.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Kaur, Harsimran, and Ashish Sharma. "ANOVA Based Significance Testing of Non-functional Requirements in Software Engineering." International Journal of Information Technology Project Management 10, no. 4 (October 2019): 100–117. http://dx.doi.org/10.4018/ijitpm.2019100104.

Full text

Abstract:

Non-functional requirements (NFRs) demonstrate how the software system works, though functional requirements represent the tasks of the system (software system). It does not indicate that the latter is more significant, but a majority of requirement collecting approaches emphasis on functional requirements. Therefore, due to the subjective nature and complexity of NFRs, it is relatively impractical to focus on each NFRs. The primary objective of this article is to model NFRs in the form of a Soft Goal Interdependency Digraph (SID). The SID is based on the Interpretive Structural Modeling (ISM) technique which in turn employs the Matrices Impacts Cruise's Multiplication Applique a UN Casement (MICMAC) and Analytic Hierarchy Process (AHP) techniques for the identification of significant NFRs. Therefore, the proposed method allows the analysts and developers to monitor and select best possible trade off selections between NFRs. To evaluate the significance of the proposed technique over others, Analysis of variance (ANOVA) based significance testing is also implemented.

APA, Harvard, Vancouver, ISO, and other styles

49

Benslimane, Younes, Luiz Marcio Cysneiros, and Bouchaib Bahli. "Assessing critical functional and non-functional requirements for web-based procurement systems: a comprehensive survey." Requirements Engineering 12, no. 3 (June 29, 2007): 191–98. http://dx.doi.org/10.1007/s00766-007-0050-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Kumar, B. Sathis. "EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS." Asian Journal of Pharmaceutical and Clinical Research 10, no. 13 (April 1, 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 attributes requirement help to identify and shape the software architecture. A software system’s architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase

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!