B. W. Boehm, J. R. Brown, H. Kaspar, M. Lipow, G. J. Macleod, and M. J. Merrit. Characteristics of Software Quality. North-Holland, 1978.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... should never be used as a verification method [DIJ2, BOYE] Nevertheless, testing is the most accepted and widely used method in the industrial software development, not only for verification of the software correctness, but also its validation, especially concerning the user requirements (See [BOEH] for the precise definitions of the terms Verification and Validation ) Taking this fact into account, many researchers in Software Engineering started very early to form a mathematical sound fundament for a systematic testing. One of the pioneer works that made Software Testing become a solid ....

B. Boehm, "Characteristics of Software Quality", North Holland, 1981

.... Non Functional Requirements Classification Non Functional Requirements SubClassification Utility Reliability: completeness, accuracy, consistency Efficiency: device efficiency, accessibility Human Engineering: accessibility, communicativeness Portability Device independence Completeness [7] All systems Product Maintainability Testability: accessibility, communicativeness, structuredness, selfdescriptiveness Understandability: consistency, structuredness, self descriptiveness, conciseness, legibility Modifiability: augmnetability Performance : real time, other time constraints, ....

B. Boehm et allii, Characteristics of Software Quality, North Holland Press, 1978.

....Finally Section 7 is a short conclusion. 2. Quality measurement and prediction Various sources describe important aspects of software quality and attempt to define metrics for product quality evaluation. Several software quality models have been defined (some of the early references are [3, 15]) and while the structure and other details of such models differ, there is wide agreement that certain factors, e.g. usability, efficiency (or performance) maintainability, and reliability, should be included in our notion of product quality. As the emphasis of the various quality ....

B.W.Boehm,J.R.Brown,H.Kaspar,M.Lipow,G.J.MacLeod,andM.J.Merritt, "Characteristics of Software Quality", North-Holland Publishing Company, 1978.

....presented hereinafter have been selected from the most well known software metrics that have been proposed and could be easily applied to object oriented programming as well. They are sorted alphabetically according to their codes. AML (Average Module Length) measures the average module size [5]. BAM (Binding Among Modules) measures data sharing among modules [6,7] CCN (Cyclomatic Complexity Number) measures the number of decisions in the control graph [8] CDF (Control flow complexity and Data Flow complexity) is a combine metric based on variable definitions and cross references ....

B.W. Boehm, J.R. Brown, J.R. Kaspar et al., Characteristics of Software Quality , TRW Series of Software Technology, 1978.

....to the user the purpose for which it has been developed and the method to use it. Based on the FCM measurement method, each criterion could be associated with metrics in the form of questions allowing subjective yes or no answers. At about the same time that FCM was proposed, Boehm proposed CSQ [6] in 1978 (also known as Boehms model) This model mainly focuses on software quality from the developers perspective and divides quality into 7 quality factors (called intermediate constructs) Portability, Reliability, Efficiency, Human Engineering, Testability, Understandability, ....

Boehm, B. et al.: Characteristics of software quality. North Holland. 1978.

....a development division of an enterprise, a small software house, a research team, etc. solve [6] in most occasions, the selection of the proper standard is of great assistance during the early design of product quality. Nowadays, most software developing units have shifted from FCM [7] and CSQ [8] to ISO9126 [9] or more recent (but yet not thoroughly tested in practice) models [10,11] for the selection of factors that affect product quality. Regardless of the method and model selected, the developing unit proceeds to a number of actions during the initial design of quality. It determines ....

B. W. Boehm et al., Characteristics of Software Quality , North Holland, 1978.

....and difficult to correct [6] 13] 10] Only a few works propose some way of explicitly dealing with NFRs under the processoriented approach. From the perspective of the existing literature, most of the work that tackles the use of NFRs during the software development process is still partial [2][3] 17] Chung s NFR Framework [9] is among the most complete works on NFR and proposes a framework that uses non functional requirements to drive design and to support architectural design. However, there is still a gap regarding the integration of NFR into conceptual models. Some of our ....

Boehm, B. "Characteristics of Software Quality" North Holland Press, 1978.

....a measurement approach for software engineering. In [2] McCall says that quality factors represent attributes or characteristics of the software that a user, or customer of the software product, would relate to its overall quality . Pionering work on quality factors was performed by Boehm [3], and by McCall and al. 4] Interestingly, already at that time one of these factors was usability, defined as the effort required to learn, operate, prepare input, and interpret output of a program [2,4] The fact that it was already included as a quality factor did not really mean that ....

B. Boehm, Characteristics of Software Quality, North Holland Publishing Co., New York, 1978.

....the software are illustrated at this level; At the software designer and project manager level, criteria are used. At this level, the set of requirements for each factor should be realized; At the software and document level, metrics are used. Two earlier models, McCall [MCC77] and Boehm models [BOE78] are usually criticized for they lack rationales to decide which factors should include in the definition of the quality and which criteria should associated with specific factors, and additionally they dont explicitly specify the metrics in the bottom layer, which makes the application in ....

Boehm, B. W., Brown, J. R., Kaspar, H., Lipow, M., Macleod, G. J., and Merritt, M. J.. Characteristics of Software Quality. Amsterdam: North-Holland, 1978

.... early years of programming the main concern was to develop syntax, i.e. those parts of languages with which you could communicate with the computer, but over the years the concern has moved over to semantic issues [2, 6] In academia, semantic correctness has been an important issue for many years [3, 7]. We believe, however, that there is a lack of understanding of semantic aspects in programming industry. To see if this assumption holds, a case study of an industrial project was done. Bertrand Meyer defined a set of criteria in [11] for achieving semantic correctness and by that obtaining ....

Barry W. Boehm et al, Characteristics of Software Quality, TRW Series of Software Technology, North-Holland Publishing Co., Amsterdam, 1978.

....research area. Equally important is how requirements drive the rest of software development. In particular, during the design phase, much of the quality aspects of a system are determined. Systems qualities are often expressed as non functional requirements, also called quality attributes e.g. [1,2]. These are requirements such as reliability, usability, maintainability, cost, development time, and are crucial for system success. Yet they are difficult to deal with since they are hard to quantify, and often interact in competing, or synergistic ways. During design such quality ....

Boehm BW. Characteristics of software quality. North-Holland Pub. Co., Amsterdam New York 1978.

....comprehensive and pragmatic data collection and analysis process, empirical tests are needed to back up this claim. 2. 4Omnibus Software Quality Metrics The relationship between software characteristics and software quality has been investigated and proposed by many researchers [Fent97] McCa77][Boeh78][ISO9126] There have been attempts to quantify software quality resulting in omnibus models which have fixed relationship between quality and metrics. Both McCall et al. and Boehm et al. describe product quality using a hierarchical approach [McCa77] Boeh78] In McCall s FCM model, high level ....

....by many researchers [Fent97] McCa77] Boeh78] ISO9126] There have been attempts to quantify software quality resulting in omnibus models which have fixed relationship between quality and metrics. Both McCall et al. and Boehm et al. describe product quality using a hierarchical approach [McCa77][Boeh78]. In McCall s FCM model, high level product quality like reusability and maintainability are called factors that can be decomposed into several lower level attributes. The Manager, who has responsibility for the software development or potential user who will use the to bedeveloped software, ....

B.W. Boehm, et al., "Characteristic of Software Quality," TRW Series of Software Technology, Amsterdam, North Holland, 1978.

....architecture, non functional requirement, architectural evolution, knowledge based design 1. Introduction During architectural design, many of the quality aspects of a system are determined. System qualities are often expressed as non functional requirements, also called quality attributes [1,2]. These are requirements such as reliability, usability, maintainability, cost, competitiveness, time to market and the like. Many of these originate at the business level, and are better viewed as business goals. Achieving business goals is crucial for system success. As business goals change, ....

Boehm BW. Characteristics of software quality. NorthHolland Pub. Co., Amsterdam New York 1978.

....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 ....

....How easy is it to convert for use in another application Reusability Table 1.1 The RADC software quality consumer oriented attributes. 26] The product oriented approach has received almost exclusive attention in the literature and is nicely overviewed in [26] Earlier work by Boehm et al. [5] considered quality characteristics of software, noting that designerawareness alone improved the quality of the final product. Also supporting a quantitative approach to software quality, Basili and Musa [3] advocate models and metrics of the software engineering process from a management ....

[Article contains additional citation context not shown here]

B. W. Boehm, J. R. Brown, H. Kaspar, M. Lipow, G. J. MacLeod and M. J. Merritt, Characteristics of Software Quality. Amsterdam: North-Holland, 1978.

No context found.

B. W. Boehm, J. R. Brown, H. Kaspar, M. Lipow, G. J. Macleod, and M. J. Merrit. Characteristics of Software Quality. North-Holland, 1978.

No context found.

Boehm, B. W. (1978). Characteristics of Software Quality. North-Holland, New York.

No context found.

Boehm B., Characteristics of Software Quality, North-Holland Pub. Co., 1978.

No context found.

Boehm, B. "Characteristics of Software Quality" North Holland Press, 1978.

No context found.

Boehm, B. Characteristics of Software Quality. North Holland Press, 1978.

No context found.

Barry W. Boehm, Brown, Kaspar, Lipod, Macleod, and Merrit. Characteristics of Software Quality. TRW Series of Software Technology. Amsterdam, 1978. Mkbook parser

No context found.

Boehm B., Brown J.R., Kaspar H., Lipow M., McLeod G., and Merritt M. Characteristics of Software Quality. TRW Series of Software Technology. North Holland, Amsterdam, 1978.

No context found.

Boehm, B.W., J.R. Brown, J.R. Kaspar, M. Lipow and G. Mac Cleod. Characteristics of Software Quality. Amsterdam: North Holland. 1978.

No context found.

B. Boehm, J. R. Brown, J. R. Kaspar, M. Lipow, C. J. MacCleod, and M. J. Merrit, Characteristics of software quality. North Holland, 1978.

No context found.

Barry Boehm et al. Characteristics of Software Quality. North-Holland, New York, 1978.

No context found.

Boehm, B W, Brown, J R, Kaspar, J R, Lipow, M, McCleod, G J, and Merrit, M J, `Characteristics of Software Quality', North Holland, 1978

First 50 documents

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