Academic literature on the topic 'Functional and non-functional requirements'

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

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

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 (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 (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 (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 (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 (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 (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 (2007): 1162–71. http://dx.doi.org/10.1016/j.infsof.2006.12.002.

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

Dissertations / Theses on the topic "Functional and non-functional requirements"

1

Cherukuri, Vijaya Krishna, and Piyush Gupta. "Model Based Testing for Non-Functional Requirements." Thesis, Mälardalen University, School of Innovation, Design and Engineering, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-9851.

Full text
Abstract:
<p>Model Based Testing (MBT) is a new-age test automation technique traditionally used for Functional Black-Box Testing. Its capability of generating test cases by using model developed from the analysis of the abstract behavior of the System under Test is gaining popularity. Many commercial and open source MBT tools are available currently in market. But each one has its own specific way of modeling and test case generation mechanism that is suitable for varied types of systems. Ericsson, a telecommunication equipment provider company, is currently adapting Model Based Testing in some of its
APA, Harvard, Vancouver, ISO, and other styles
2

Al-kfairy, Mousa. "Toward Agile development methods & Non-functional requirements." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-54656.

Full text
Abstract:
In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The f
APA, Harvard, Vancouver, ISO, and other styles
3

Ahmad, Manzoor. "Modeling and verification of functional and non functional requirements of ambient, self adaptative systems." Phd thesis, Université Toulouse le Mirail - Toulouse II, 2013. http://tel.archives-ouvertes.fr/tel-00965934.

Full text
Abstract:
The overall contribution of this thesis is to propose an integrated approach for modeling and verifying the requirements of Self Adaptive Systems using Model Driven Engineering techniques. Model Driven Engineering is primarily concerned with reducing the gap between problem and software implementation domains through the use of technologies that support systematic transformation of problem level abstractions to software implementations. By using these techniques, we have bridged this gap through the use of models that describe complex systems at multiple levels of abstraction and through autom
APA, Harvard, Vancouver, ISO, and other styles
4

Ameller, David. "Non-functional requirements as drivers of software architecture design." Doctoral thesis, Universitat Politècnica de Catalunya, 2014. http://hdl.handle.net/10803/144942.

Full text
Abstract:
In the last decades, software engineering has become an important area of research. As researchers, we try to identify a problem, a need, or a hole in some research topic, once identified we make an effort to produce new techniques, methods, and tools that hopefully will help to improve the detected issue. In the present thesis the identified issue was the need of supporting non-functional requirements in the software architecture design where these requirements are the drivers of the architectural decision-making. This thesis started with the idea that a relatively new software engineering d
APA, Harvard, Vancouver, ISO, and other styles
5

Moody, James D. "Categorizing non-functional requirements using a hierarchy in UML." [Johnson City, Tenn. : East Tennessee State University], 2003. http://etd-submit.etsu.edu/etd/theses/available/etd-0330103-170022/unrestricted/MoodyJ04292003b.pdf.

Full text
Abstract:
Thesis (M.S.)--East Tennessee State University, 2003.<br>Title from electronic submission form. ETSU ETD database URN: etd-0330103-170022. Includes bibliographical references. Also available via Internet at the UMI web site.
APA, Harvard, Vancouver, ISO, and other styles
6

Moody, James David. "Categorizing Non-Functional Requirements Using a Hierarchy in UML." Digital Commons @ East Tennessee State University, 2003. https://dc.etsu.edu/etd/763.

Full text
Abstract:
Non-functional requirements (NFRs) are a subset of requirements, the means by which software system developers and clients communicate about the functionality of the system to be built. This paper has three main parts: first, an overview of how non-functional requirements relate to software engineering is given, along with a survey of NFRs in the software engineering literature. Second, a collection of 161 NFRs is diagrammed using the Unified Modelling Language, forming a tool with which developers may more easily identify and write additional NFRs. Third, a lesson plan is presented, a learnin
APA, Harvard, Vancouver, ISO, and other styles
7

Farid, Weam Mohamed. "The NORMAP Methodology: Non-functional Requirements Modeling for Agile Processes." NSUWorks, 2011. http://nsuworks.nova.edu/gscis_etd/147.

Full text
Abstract:
Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Ag
APA, Harvard, Vancouver, ISO, and other styles
8

Sadiq, Mazhar. "Modeling the Non-functional Requirements in the Context of Usability, Performance, Safety and Security." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3246.

Full text
Abstract:
Requirement engineering is the most significant part of the software development life cycle. Until now great emphasis has been put on the maturity of the functional requirements. But with the passage of time it reveals that the success of software development does not only pertain to the functional requirements rather non-functional requirements should also be taken into consideration. Among the non-functional requirements usability, performance, safety and security are considered important. Further it reveals that there exist so many modeling and testing techniques for functional requirements
APA, Harvard, Vancouver, ISO, and other styles
9

Gokyer, Gokhan. "Identifying Architectural Concerns From Non-functional Requirements Using Support Vector Machine." Master's thesis, METU, 2008. http://etd.lib.metu.edu.tr/upload/12609964/index.pdf.

Full text
Abstract:
There has been no commonsense on how to identify problem domain concerns in architectural modeling of software systems. Even, there is no commonly accepted method for modeling the Non-Functional Requirements (NFRs) effectively associated with the architectural aspects in the solution domain. This thesis introduces the use of a Machine Learning (ML) method based on Support Vector Machines to relate NFRs to classified &quot<br>architectural concerns&quot<br>in an automated way. This method uses Natural Language Processing techniques to fragment the plain NFR texts under the supervision of domain
APA, Harvard, Vancouver, ISO, and other styles
10

Wen, Zhenyu. "Partitioning workflow applications over federated clouds to meet non-functional requirements." Thesis, University of Newcastle upon Tyne, 2016. http://hdl.handle.net/10443/3343.

Full text
Abstract:
With cloud computing, users can acquire computer resources when they need them on a pay-as-you-go business model. Because of this, many applications are now being deployed in the cloud, and there are many di erent cloud providers worldwide. Importantly, all these various infrastructure providers o er services with di erent levels of quality. For example, cloud data centres are governed by the privacy and security policies of the country where the centre is located, while many organisations have created their own internal \private cloud" to meet security needs. With all this varieties and uncer
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Functional and non-functional requirements"

1

Chung, Lawrence, Brian A. Nixon, Eric Yu, and John Mylopoulos. Non-Functional Requirements in Software Engineering. Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-5269-7.

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

Chung, Lawrence. Non-Functional Requirements in Software Engineering. Springer US, 2000.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Patton, Glenn E., ed. Functional Requirements for Authority Data. Walter de Gruyter – K. G. Saur, 2009. http://dx.doi.org/10.1515/9783598440397.

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

Chung, K. Lawrence. Representing and using non-functional requirements: A process-oriented approach. Department of Computer Science, University of Toronto, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Milanovic, Nikola. Non-functional properties in service oriented architecture: Requirements, models and methods. Information Science Reference, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Overmire, Rozell. Functional requirements for exhibit management systems. Archives & Museum Informatics, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

IFLA Study Group on the Functional Requirements for Bibliographic Records. Functional requirements for bibliographic records: Final report. K.G. Saur, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Qiang, Jin. Demystifying FRAD: Functional requirements for authority data. Libraries Unlimited, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Zeng, Marcia Lei, Maja Zumer, Athena Salaba, and IFLA Working Group on the Functiona, eds. Functional Requirements for Subject Authority Data (FRSAD). DE GRUYTER SAUR, 2011. http://dx.doi.org/10.1515/9783110263787.

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

Bearman, David. Functional requirements for membership, development & participation systems. Archives & Museum Informatics, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Functional and non-functional requirements"

1

Cysneiros, Luiz Marcio, and Eric Yu. "Non-Functional Requirements Elicitation." In Perspectives on Software Requirements. Springer US, 2004. http://dx.doi.org/10.1007/978-1-4615-0465-8_6.

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

Spuri, Marco. "Functional Versus Non-Functional Requirements Analysis." In Real Time Computing. Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-88049-0_120.

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

Paulitsch, Michael, Harald Ruess, and Maria Sorea. "Non-functional Avionics Requirements." In Communications in Computer and Information Science. Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-88479-8_26.

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

Mirakhorli, Mehdi, and Jane Cleland-Huang. "Tracing Non-Functional Requirements." In Software and Systems Traceability. Springer London, 2011. http://dx.doi.org/10.1007/978-1-4471-2239-5_14.

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

Chung, Lawrence, Brian A. Nixon, Eric Yu, and John Mylopoulos. "Accuracy Requirements." In Non-Functional Requirements in Software Engineering. Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-5269-7_6.

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

Chung, Lawrence, Brian A. Nixon, Eric Yu, and John Mylopoulos. "Security Requirements." In Non-Functional Requirements in Software Engineering. Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-5269-7_7.

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

Chung, Lawrence, Brian A. Nixon, Eric Yu, and John Mylopoulos. "Performance Requirements." In Non-Functional Requirements in Software Engineering. Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-5269-7_8.

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

Gnaho, Christophe, Farida Semmak, and Regine Laleau. "Modeling the Impact of Non-functional Requirements on Functional Requirements." In Lecture Notes in Computer Science. Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-14139-8_8.

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

Adams, Kevin MacG. "Introduction to Non-functional Requirements." In Nonfunctional Requirements in Systems Analysis and Design. Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-18344-2_3.

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

Robben, Bert, Wouter Joosen, Frank Matthijs, Bart Vanhaute, and Pierre Verbaeten. "Components for Non-Functional Requirements." In Object-Oriented Technology: ECOOP’98 Workshop Reader. Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/3-540-49255-0_31.

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

Conference papers on the topic "Functional and non-functional requirements"

1

Eckhardt, Jonas, Andreas Vogelsang, and Daniel Méndez Fernández. "Are "non-functional" requirements really non-functional?" In ICSE '16: 38th International Conference on Software Engineering. ACM, 2016. http://dx.doi.org/10.1145/2884781.2884788.

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

Cysneiros, Luiz Marcio, and Julio Cesar Sampaio do Prado Leite. "Non-functional requirements." In the 24th international conference. ACM Press, 2002. http://dx.doi.org/10.1145/581339.581452.

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

Glinz, M. "On Non-Functional Requirements." In 2007 IEEE International Conference on Requirements Engineering. IEEE, 2007. http://dx.doi.org/10.1109/re.2007.45.

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

Ernst, Neil, Yijun Yu, and John Mylopoulos. "Visualizing non-functional requirements." In 2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop. IEEE, 2006. http://dx.doi.org/10.1109/rev.2006.10.

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

Sadana, Vishal, and Xiaoqing Frank Liu. "Analysis of Conflicts among Non-Functional Requirements Using Integrated Analysis of Functional and Non-Functional Requirements." In 31st Annual International Computer Software and Applications Conference - Vol. 1- (COMPSAC 2007). IEEE, 2007. http://dx.doi.org/10.1109/compsac.2007.73.

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

Burgess, Christopher, Aneesh Krishna, and Li Jiang. "Towards Optimising Non-functional Requirements." In 2009 9th International Conference on Quality Software (QSIC). IEEE, 2009. http://dx.doi.org/10.1109/qsic.2009.42.

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

Supakkul, Sam, and Lawrence Chung. "Visualizing non-functional requirements patterns." In 2010 Fifth International Workshop on Requirements Engineering Visualization (REV). IEEE, 2010. http://dx.doi.org/10.1109/rev.2010.5625663.

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

Chung, Lawrence, and Brian A. Nixon. "Dealing with non-functional requirements." In the 17th international conference. ACM Press, 1995. http://dx.doi.org/10.1145/225014.225017.

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

Khatter, Kiran, and Arvind Kalia. "Quantification of non-functional requirements." In 2014 Seventh International Conference on Contemporary Computing (IC3). IEEE, 2014. http://dx.doi.org/10.1109/ic3.2014.6897177.

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

Song, Xiaoyu. "Non-Functional Requirements Elicitation and Incorporation into Functional Models." In 14th Asia-Pacific Software Engineering Conference (APSEC'07). IEEE, 2007. http://dx.doi.org/10.1109/apsec.2007.72.

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

Reports on the topic "Functional and non-functional requirements"

1

Duclos, Ronald, and Ned Shepherd. Structured Analysis/Design - LSA Tank 301, Functional Requirements Identification, Subtask 301.2.3, Functional Requirements Risk Analysis. Defense Technical Information Center, 1990. http://dx.doi.org/10.21236/ada255546.

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

ACREE, C. D. Integrated Requirements Management System User and Functional Requirements. Office of Scientific and Technical Information (OSTI), 2001. http://dx.doi.org/10.2172/806791.

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

Sollins, K., and L. Masinter. Functional Requirements for Uniform Resource Names. RFC Editor, 1994. http://dx.doi.org/10.17487/rfc1737.

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

Burgess, Edwin B., Patricia Alderman, Myra Craig, et al. Functional Requirements for Army Library Automation. Defense Technical Information Center, 1992. http://dx.doi.org/10.21236/ada253531.

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

Glen R. Longhurst, Soli T. Khericha, and James L. Jones. Gas Test Loop Functional and Technical Requirements. Office of Scientific and Technical Information (OSTI), 2004. http://dx.doi.org/10.2172/910953.

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

L. E. Demick. HTGR Industrial Application Functional and Operational Requirements. Office of Scientific and Technical Information (OSTI), 2010. http://dx.doi.org/10.2172/986944.

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

EDWARDS, HAROLD C., JAMES R. STEWART, and LEE M. TAYLOR. Functional Requirements for SIERRA Version 1.0 Beta. Office of Scientific and Technical Information (OSTI), 1999. http://dx.doi.org/10.2172/13961.

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

Maranec, R., J. Romito, and D. Norem. Functional Process Improvement Business Requirements Definition Workshop. Defense Technical Information Center, 1993. http://dx.doi.org/10.21236/ada267917.

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

Duclos, Ronald, and Ned Shepherd. (LSA) Task. Subtask 301.2.1. 'Operational and Support Functional Requirements Identification Task Report'; and Subtask 301.2.2, 'Unique Functional Requirements'. Defense Technical Information Center, 1987. http://dx.doi.org/10.21236/ada257777.

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

Shahbazi, Shayan, and David Grabaskas. Functional Requirements for the Modeling and Simulation of Advanced (Non-LWR) Reactor Mechanistic Source Term. Office of Scientific and Technical Information (OSTI), 2020. http://dx.doi.org/10.2172/1633619.

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!