2010
DOI: 10.1016/j.knosys.2010.03.014
|View full text |Cite
|
Sign up to set email alerts
|

Towards a framework for estimating system NFRs on behavioral models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2011
2011
2021
2021

Publication Types

Select...
7
1
1

Relationship

1
8

Authors

Journals

citations
Cited by 11 publications
(4 citation statements)
references
References 22 publications
0
4
0
Order By: Relevance
“…Elmufti et al (2009) present an architectural solution with trust in the centre of research attention. Mizouni and Salah (2010) describe a non-functional requirements model for m-shopping application by including attributes of portability, ease of use (friendliness), an appropriate level of security, response time, and availability. Going beyond the limited article selections, many other journal articles have also taken into account a technological perspective with respect to the system architecture and framework.…”
Section: Technology Perspectivementioning
confidence: 99%
“…Elmufti et al (2009) present an architectural solution with trust in the centre of research attention. Mizouni and Salah (2010) describe a non-functional requirements model for m-shopping application by including attributes of portability, ease of use (friendliness), an appropriate level of security, response time, and availability. Going beyond the limited article selections, many other journal articles have also taken into account a technological perspective with respect to the system architecture and framework.…”
Section: Technology Perspectivementioning
confidence: 99%
“…The proposed work in this paper helps in classifying the different tools in state of the art in automation requirement process on the basis of degree of tool automation, knowledge reused and evaluation of concepts. Mizouni and Salah (2010) proposed a framework to estimate the system non-functional requirements on behavior model. NFRs are not handled properly in behavior models at early stages cause in failure of the system.…”
Section: Literature Reviewmentioning
confidence: 99%
“…Requirements volatility refers to the growth or changes in project functional or non-functional [20] requirements during development lifecycle either by deletion, addition or modification [21]. Such changes usually impact the set of features under development.…”
Section: Human Resources Allocation In Project Managementmentioning
confidence: 99%