S. E. Keller, L. G. Kahn and R. B. Panara. Specifying Software Quality Requirements with Metrics. Tutorial: System and Software Requirements Engineering, R. H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....axes have been proposed in the litera ture. Functional goals underlie services that the system is expected to deliver whereas non functional goals refer to expected system qualities such as security, safety, performance, usability, flexibility, customizability, interoperability, and so forth [Ke190] This typology is overly general and can be specialized. For example, satisfaction goals are functional goals concerned with satisfying agent requests; information goals are functional goals concerned with keeping such agents informed about object states [Dar93] Non functional goals can be ....

S.E. Keller, L.G. Kahn and R.B. Panara, "Specifying Software Quality Requirements with Metrics", in Tutorial: System and Software Requirements Enginering, R.H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

....several, partially conflicting intentions, an action can be validated against all intentions, not only the one by which it was initially stimulated. Therefore, it is possible to not only use single goals but complete goal systems. Standards like IEEE, DoD, or ESA, or goal systems like the one by [14] describing different classes of goals like performance goals (efficiency, integrity . design goals (correctness, verifiability . and adoption goals (interoperability, portability . can be used. Figure 6: Goal satisfaction as product transformation [31] In figure 7 we have ....

Keller, S., Kahn, L., and Panara, R. Specifying Software Quality Requirements with Metrics. Systems and Software Requirements Engineering - IEEE Computer Society Press - Tutorial (1990), 145 163.

....and to validate for the user once the final system has been built. The only glimmer of technical light in an otherwise bleak landscape originates in technical work on software quality metrics that allow the quantification of the degree to which a software system meets non functional requirements [26, 5, 3]. There is not a formal definition or a complete list of non functional requirements. In a report published by the Rome Air Development Center (RADC) 7] non functional requirements ( software quality attributes in their terminology) are classified into consumer oriented (or software quality ....

....globally with a criterion such as: There shall be no more than X branches per 1,000 lines of code or locally with a criterion such as There shall be no more than Y of system modules that violate the above criterion. 1 Also referred to as constraints [41] goals [31] and quality attributes [26] in the literature. 1 Acquisition Concern User Concern Quality Attribute How well does it utilize a resource Efficiency How secure is it Integrity Performance How well does What confidence can be placed in what it does Reliability it function How well will it perform under adverse ....

[Article contains additional citation context not shown here]

S. E. Keller, L. G. Kahn and R. B. Panara, "Specifying Software Quality Requirements with Metrics," in Tutorial: System and Software Requirements Engineering, R. H. Thayer and M. Dorfman, Eds. IEEE Computer Society Press, 1990, pp. 145--163,

....arising in the field. A notation such as NoFun provides then a common framework in which people can formulate, analyse and compare their proposals about non functionality. We have represented in this paper a measure for reusability as formulated in [1] and we have developed also other proposals [5, 12]. As far as NoFun has a well defined syntax and semantics (not detailed here) we have been able to use it as a basis for building an algorithm to select component implementations in an automatic way, by evaluating them with respect to some non functional requirements that modelise their ....

S.E. Keller, L.G. Kahn, R.B. Panara. "Specifying Software Quality Requirements with Metrics". IEEE Computer, 1990.

....several, partially conflicting intentions, an action can be validated against all intentions, not only the one by which it was initially stimulated. Therefore, it is possible to not only use single goals but complete goal systems. Standards like IEEE, DoD, or ESA, or goal systems like the one by [14] describing different classes of goals like performance goals (effi ciency, integrity, design goals (correctness, verifiability, and adoption goals (interoperability, portability, can be used. Product Situation Intention Executive Context based on part of IRD Definition Schema ....

Keller, S., Kahn, L., and Panara, R. Specifying Software Quality Requirements with Metrics. Systems and Software Requirements Engineering - IEEE Computer Society Press - Tutorial (1990), 145--163.

....the software development by the customer. External interface requirements define everything outside the subject of the system the software must deal with (e.g. constraints from other standards, hardware or people) With quality attributes the quality of the software to be reached is defined (cf. [61] for examples of quality attributes) Beside this classification of requirements a distinction between vital requirements and desirable requirements should be made (cf. British Standard 6719 [48] Vital requirements must be completely accomplished by the system, whereas desirable requirements ....

S. E. Keller, L. G. Kahn, and R. B.Panara. Specifying Software Quality Requirements with Metrics. In Thayer R.H and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 145--163. IEEE Computer Society Press --- Tutorial, 1990.

.... management, completeness and functional scope [18] Most existing specification languages focus on functional requirements and leave non functional requirements outside of the scope of the formal specification [18] However, such requirements form an important part of a system s specification [17]. It has been common practice for system developers only to concern themselves with the non functional requirements once they have developed satisfactory functionality. Unsatisfactory experiences with many system developments has led to the realisation that nonfunctional requirements need to be ....

Keller S.E., Kahn L.G., Panara R.B., 'Specifying Software Quality Requirements with Matrix', in Tutorial: System and Software Reqirements Engineering, Thayer R.H., Dorfman M, (Eds), IEEE Computer Society Press, 1990, 145-163

....languages focus on functional requirements that is, requirements about what the software system is expected to do. Non functional requirements are most often left outside of any kind of formal treatment [Myl92] Such requirements form an important part of real requirements documents [Kel90]; they refer to This paper appeared in Science of Computer Programming, Vol. 20, 1993, pp. 3 50. Correspondence about this article should be addressed to the second author. 2 operational costs, responsibilities, interaction with the external environment, reliability, integrity, flexibility, ....

S.E. Keller, L.G. Kahn and R.B. Panara, "Specifying Software Quality Requirements with Metrics", in Tutorial: System and Software Requirements Enginering, R.H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

....are goals concerned with keeping agents informed about object states; SecurityGoals are goals concerned with maintaining secure access to objects by agents; other categories include SafetyGoals, AccuracyGoals, etc. These categories refine wellknown functional and non functional goal categories [38, 54]. Such taxonomies are associated with heuristic rules that may guide the elaboration process, e.g. SafetyGoals are AvoidGoals to be refined in HardRequirements; ConfidentialityGoals are AvoidGoals on Knows predicates. Tactics capture heuristics for driving the elaboration or for ....

S.E. Keller, L.G. Kahn and R.B. Panara, "Specifying Software Quality Requirements with Metrics", in Tutorial: System and Software Requirements Enginering, R.H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

....matter for which reliable and allencompassing measures cannot be articulated. Quality requirements are commonly imported from external standards or policy documents, such as [ISO 9000 3, 1991] where they are pre specified along with metrics for promoting best practice and measuring compliance [Keller et al. 1990]. Due to the sheer number of potential quality attributes (see [Boehm et al. 1978] for a representative list) these need to be adopted and tailored on a project specific basis [Buckley Poston, 1984] Furthermore, these definitions of quality change, the relevance of metrics to quality change, ....

Keller, S. E., Kahn, L. G. and Panara, R. B. (1990). "Specifying Software Quality Requirements with Metrics", in Thayer, R. H. and Dorfman, M. (eds.), System and Software Requirements Engineering, IEEE Computer Society Press Tutorial, pp. 145-163.

No context found.

S. E. Keller, L. G. Kahn and R. B. Panara. Specifying Software Quality Requirements with Metrics. Tutorial: System and Software Requirements Engineering, R. H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

No context found.

S. E. Keller, L. G. Kahn and R. B. Panara. Specifying Software Quality Requirements with Metrics. Tutorial: System and Software Requirements Engineering, R. H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

No context found.

Keller, S.E. et al "Specifying Software Quality Requirements with Metrics" in Tutorial System and Software Requirements Engineering IEEE Computer Society Press 1990 pp:145-163.

No context found.

Keller S. E., Kahn L. G., and Panara R. B. Specifying Software Quality Requirements with Metrics. In System and Software Requirements Engineering, pages 145--163. IEEE Computer Society Press, 1990.

No context found.

S.E. Keller, L.G. Kahn, R.B. Panara, Specifying software quality requirements with metrics, in: R.H. Thayer and M. Dorfman (Eds.), System and Software Requirements Engineering, 1990, pp. 145--163.

No context found.

Keller, S.E. et al "Specifying Software Quality Requirements with Metrics" in Tutorial System and Software Requirements Engineering IEEE Computer Society Press 1990 pp:145-163

No context found.

S.E. Keller, L.G. Kahn and R.B. Panara, "Specifying Software Quality Requirements with Metrics", in Tutorial: System and Software Requirements Enginering, R.H. Thayer and M. Dorfman, Eds., IEEE Computer Society Press, 1990, 145-163.

No context found.

Keller, Steven E., L.G. Kahn, and R.B. Panara, Specifying Software Quality Requirements with Metrics, R.H. Thayer and M. Dorfman eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, CA, 1990.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC