2006
DOI: 10.1007/11966104_14
|View full text |Cite
|
Sign up to set email alerts
|

Preserving Software Quality Characteristics from Requirements Analysis to Architectural Design

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

2007
2007
2018
2018

Publication Types

Select...
3
3
1

Relationship

2
5

Authors

Journals

citations
Cited by 12 publications
(4 citation statements)
references
References 4 publications
0
4
0
Order By: Relevance
“…For these two data sets, λ max is 932,575 and 992, respectively. We use the logistic regression code from L1General (Schmidt, 2006) as the inner iteration algorithm in this set of experiments. Figure 5 plots the running time at different λ values for dynamic screening, BLITZ, and SAIF.…”
Section: Results For Logistic Regressionmentioning
confidence: 99%
“…For these two data sets, λ max is 932,575 and 992, respectively. We use the logistic regression code from L1General (Schmidt, 2006) as the inner iteration algorithm in this set of experiments. Figure 5 plots the running time at different λ values for dynamic screening, BLITZ, and SAIF.…”
Section: Results For Logistic Regressionmentioning
confidence: 99%
“…The approach does not consider the elicitation of the initial set of security requirements (only dependent security requirements are elicited), a concrete attacker model, conflicting requirements, nor interaction of security and other non-functional requirements. However, a first paper addressing the latter two issues has already been published [84].…”
Section: Abuse Framesmentioning
confidence: 99%
“…And as a last difference, a refinement to implementable architectures is not considered. Nevertheless, the papers by Choppy & Hatebur & Heisel (2005 and as well as the idea to systematically preserve quality requirements from early requirements engineering to software design presented by Schmidt & Wentzlaff (2006) constitute the basis for the enhancements presented in this chapter.…”
Section: Security Architecturesmentioning
confidence: 99%
“…In the case that it is relevant, the conflict must be resolved by modifying or prioritizing the requirements. An example of relaxing security requirements for the benefit of usability requirements can be found in Schmidt & Wentzlaff (2006). This step can result in modified sets of security requirements and concretized security requirements.…”
Section: Step 6 -Analyze Possible Conflictsmentioning
confidence: 99%