FDA: Between Process and Product Evaluation

Abdeen, Marwan M.; Kahl, Wolfram; Maibaum, Tom

doi:10.1109/hcmdss-mdpnp.2007.6

Cited by 6 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In terms of software development[, the FDA approach does not favour any specific software development model.] [9] In other words, it leaves the choice of the approach to be used in developing the software to software producers themselves. This supports the fact that some organizations have there own policies, standards and development approaches [that] must be followed.…”

Section: Process Oriented Standards and Certificationmentioning

confidence: 99%

“…(From [9,10]: ) Having such a measurement framework defined will decrease [the level of] subjectivity in the evaluation activity. The FDA approach lacks such a measurement framework.…”

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

“…The same notion of static and dynamic attributes is applicable to the deliverables (products). To be more concrete," [9] "the version number (as a static attribute) of the software (as a product) is related to the product itself. Whereas, reliability (as a dynamic attribute) of the software (as a product) is relative to the way in which the product (software) behaves in its operating environment.…”

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

“…(From [9,10]: ) Fenton and Pfleeger defined processes, [in the context of software engineering,] in [12], as 'collections of software-related activities'. Hence the process usually has a time factor, i.e., it has a clear beginning and end.…”

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

“…See [9,10]. In fact, the focus of these documents is on the characteristics of a software development process that is likely to produce satisfactory software.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Challenges in Software Certification

Maibaum

2007

Formal Methods and Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. As software has invaded more and more areas of everyday life, software certification has emerged as a very important issue for governments, industry and consumers. Existing certification regimes are generally focused on the wrong entity, the development process that produces the artifact to be certified. At best, such an approach can produce only circumstantial evidence for the suitability of the software. For proper scientific evaluation of an artifact, we need to address directly the attributes of the product and their acceptability for certification. However, the product itself is clearly not enough, as we need other artifacts, like requirements specifications, designs, test documentation, correctness proofs, etc. We can organise these artifacts using a simple, idealised process, in terms of which a manufacturer's own process can be "faked". The attributes of this idealised process and its products can be modelled, following the principles of Measurement Theory, using the product/process modelling method first introduced by Kaposi.

show abstract

Section: Process Oriented Standards and Certificationmentioning

confidence: 99%

“…(From [9,10]: ) Having such a measurement framework defined will decrease [the level of] subjectivity in the evaluation activity. The FDA approach lacks such a measurement framework.…”

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

Section: Measurement and Product/process Modellingmentioning

confidence: 99%

“…See [9,10]. In fact, the focus of these documents is on the characteristics of a software development process that is likely to produce satisfactory software.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations