![]() of the 2008 International Conference on Computational Intelligence and Security (CIS), 2008. Analysis, specification and modeling of non-functional requirements for translative model-driven development. FUNCTIONAL REQUIREMENTS SOFTWAREof the 9th International Symposium on Empirical Software Engineering and Measurement (ESEM), 2015. FUNCTIONAL REQUIREMENTS HOW TOHow to specify non-functional requirements to support seamless modeling? A study design and preliminary results. of the Workshop on Foundations of Interface Technologies (FIT), 2005. Boosting re-use of embedded automotive applications through rich components. Non-functional requirements in software engineering, volume 5. of the 17th International Conference on Software Engineering (ICSE), 1995. ![]() Dealing with non-functional requirements: three experimental studies of a process-oriented approach. In Conceptual modeling: Foundations and applications, volume 5600 of Lecture Notes in Computer Science. On non-functional requirements in software engineering. Characterizing architecturally significant requirements. Hinchey, editor, Software Technology: 10 Years of Innovation in IEEE Computer. ![]() Rethinking nonfunctional software requirements: A novel approach categorizing system and software requirements. Rethinking nonfunctional software requirements. Science of Computer Programming, 75(12), 2010. Multifunctional software systems: Structured modeling and specification of functional requirements. of the 3rd Conference on Software Engineering Research and Practice in Sweden (SERPS), 2003. The bad conscience of requirements engineering: an investigation in real-world treatment of non-functional requirements. of the 18th IEEE International Requirements Engineering Conference (RE), 2010. Dealing with non-functional requirements in model-driven development. of the 20th IEEE International Requirements Engineering Conference (RE), 2012. How do software architects consider non-functional requirements: An exploratory study. Consequently, we argue that many so-called NFRs can be handled similarly to functional requirements. Our results suggest that most "non-functional" requirements are not non-functional as they describe behavior of a system. We report on the classification of 530 NFRs extracted from 11 industrial requirements specifications and analyze to which extent these NFRs describe system behavior. In this paper, we empirically investigate this point of view and aim to increase our understanding on the nature of NFRs addressing system properties. Several authors argue, however, that many so-called NFRs actually describe behavioral properties and may be treated the same way as functional requirements. ![]() As a result, they remain difficult to analyze and test. NFRs are usually documented separately from functional requirements, without quantitative measures, and with relatively vague descriptions. This distinction is not only prevalent in research, but also influences how requirements are handled in practice. Non-functional requirements (NFRs) are commonly distinguished from functional requirements by differentiating how the system shall do something in contrast to what the system shall do. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |