A method for assessing confidence in requirements analysis

Boness, Kenneth Duncan; Finkelstein, Anthony; Harrison, Rachel

doi:10.1016/j.infsof.2011.05.003

Cited by 17 publications

(24 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While this study used a list-of-ideas framing, we do not advocate simply renaming "requirements" to "ideas" -the ideas language was chosen simply to minimize the difference between the two groups. Rather, we suggest the practitioners more generally consider two properties of each desideratum -importance/priority [43] and confidence [8,56,63]. Importance refers to how crucial a desideratum is for success.…”

Section: Discussionmentioning

confidence: 99%

Requirements fixation

Mohanani

Ralph

Shreeve

2014

Proceedings of the 36th International Conference on Software Engineering

View full text Add to dashboard Cite

There is a broad consensus that understanding system desiderata (requirements) and design creativity are both important for software engineering success. However, little research has addressed the relationship between design creativity and the way requirements are framed or presented. This paper therefore aims to investigate the possibility that the way desiderata are framed or presented can affect design creativity. Forty two participants took part in a randomized control trial where one group received desiderata framed as "requirements" while the other received desiderata framed as "ideas". Participants produced design concepts which were judged for originality. Participants who received requirements framing produced significantly less original designs than participants who received ideas framing (MannWhitney U=116.5, p=0.004). We conclude that framing desiderata as "requirements" may cause requirements fixation where designers' preoccupation with satisfying explicit requirements inhibits their creativity.

show abstract

Section: Discussionmentioning

confidence: 99%

Requirements fixation

Mohanani

Ralph

Shreeve

2014

Proceedings of the 36th International Conference on Software Engineering

View full text Add to dashboard Cite

show abstract

“…A meta-level estimation of requirements [21] offers a useful and practical method that proved valuable to customer, analysts and designers to inform the fulfillment of sufficient requirements analysis. The proposed method achieved four confidence factors and used a goal oriented framework with an effortless ordinal scale to enlarge a method for assessing confidence.…”

Section: Requirement Validation or Verificationmentioning

confidence: 99%

“…Metamodel [21] provided better confidentiality during requirements analysis but needs a requirement validation. Even though the method for assessing confidence during requirements analysis achieved better privacy, the requirement validation is unnoticed.…”

Section: Note: Y-yesmentioning

confidence: 99%

Survey on Security Measures of Software Requirement Engineering

Saranya¹

2014

IJCA

View full text Add to dashboard Cite

Software engineering concerns with wide use of engineering principles to achieve cost-effective software with potentiality to function on real machines. Requirement engineering in software development is more crucial. Everyone agrees that security is difficult. The requirements engineering principles are framed based on an idea that would engage the community overcoming complex problems. Security is about the prevention of several difficulties due to the presence of attackers behaving malicious activities. Software security is incredible due to the intrinsically complex task and the problem happens because of three main reasons such as networks are everywhere, systems are easily extensible and system complexity is rising.The principle objective of requirement engineering research is not just to point out the fact about security risks keep on rising every day, but rather to defeat attack, just as any other system property. Security should be tackled at the beginning of the software lifecycle. This survey planned to concentrate on the requirements phase as security is a system property.

show abstract

“…This approach helps to prioritise the many SMCW stakeholder viewpoints, dependencies, and relationships and helps to build confidence in the ongoing development of the SMCW model for as many stakeholders as possible [6].The modeling of sociotechnical system requirements involves modeling agents who depend on one another, in order to achieve their personal goals within the SMCW community so we place the emphasis on stakeholder relationships, motivations, values and emotions [7,8].…”

Section: A Human Social Media Interactionsmentioning

confidence: 99%