A Spiral Model of Software Development and Enhancement

Boehm, Barry

doi:10.1016/b978-0-08-051574-8.50031-5

Cited by 525 publications

(583 citation statements)

References 7 publications

Supporting

Mentioning

535

Contrasting

Unclassified

Order By: Relevance

“…The ability of a system or component to perform its required functions under stated conditions for a specified period of time [12]. Reliability can be measure in terms of reliability metrics MTTF, MTTR, MTBF, ROCOF and availability.…”

Section: Reliabilitymentioning

confidence: 99%

New Algorithm for Component Selection to Develop Component-Based Software with X Model

Tomar¹,

Gill²

2013

LNSE

View full text Add to dashboard Cite

Section: Reliabilitymentioning

confidence: 99%

New Algorithm for Component Selection to Develop Component-Based Software with X Model

Tomar¹,

Gill²

2013

LNSE

View full text Add to dashboard Cite

“…The MII has been fully specified and a prototype delivered, in which a set of medical imaging services is implemented to manage the federation of distributed mammograms [18]. To encourage re-use the MammoGrid software was delivered through a set of evolving prototypes following a form of 'spiral model' [19] development (including 'stages' of planning, specification, evaluation, and development for each prototype version) in which the clinical user community provided input in each loop of the spiral. Release of the staged prototypes was planned to coincide with project milestones and the delivery of tested MammoGrid services.…”

Section: The Design and Deployment Phasesmentioning

confidence: 99%

Experiences of engineering Grid-based medical software

Estrella

Hauer

McClatchey

et al. 2007

International Journal of Medical Informatics

View full text Add to dashboard Cite

SummaryObjectives: Grid-based technologies are emerging as potential solutions for managing and collaborating distributed resources in the biomedical domain. Few examples exist, however, of successful implementations of Grid-enabled medical systems and even fewer have been deployed for evaluation in practice. The objective of this paper is to evaluate the use in clinical practice of a Grid-based imaging prototype and to establish directions for engineering future medical Grid developments and their subsequent deployment. Method: The MammoGrid project has deployed a prototype system for clinicians using the Grid as its information infrastructure. To assist in the specification of the system requirements (and for the first time in healthgrid applications), use-case modelling has been carried out in close collaboration with clinicians and radiologists who had no prior experience of this modelling technique. A critical qualitative and, where possible, quantitative analysis of the MammoGrid prototype is presented leading to a set of recommendations from the delivery of the first deployed Grid-based medical imaging application. Results: We report critically on the application of software engineering techniques in the specification and implementation of the MammoGrid project and show that use-case modelling is a suitable vehicle for representing medical requirements and for communicating effectively with the clinical community. This paper also discusses the practical advantages and limitations of applying the Grid to real-life clinical applications and presents the consequent lessons learned. Conclusions:The work presented in this paper demonstrates that given suitable commitment from collaborating radiologists it is practical to deploy in practice medical imaging analysis applications using the Grid but that standardisation in and stability of the Grid software is a necessary pre-requisite for successful healthgrids. The MammoGrid prototype has therefore paved the way for further advanced Grid-based deployments in the medical and biomedical domains.

show abstract

“…A detailed discussion of these techniques is outside the scope of this paper; the details can be read in (Albrecht, 1979 and1983), 2000), (Londeix, 1987), (Putnam, 1980(Putnam, , 1992. None of these techniques consider the following characteristics of software projects: a) Requirement volatility b) Personnel volatility c) Time consumed by communications, exceptions and noise in the process.…”

Section: The Risk Assessment and Estimation Problemsmentioning

confidence: 99%

Surfing the Edge of Chaos: Applications to Software Engineering

Nogueira¹,

Jones²

2000

View full text Add to dashboard Cite

This paper discusses the problems of software engineering as the weakest link in the development of systems capable of achieving information superiority. Fast changes in technology introduce additional difficulties in terms of strategic planning, organizational structure, and engineering of software development projects. In such complex environment, a new way of thinking is required. We analyze the introduction of complex adaptive systems as an alternative for planning and change. The strategy of "competing on the edge" is analyzed showing the risks and the skills required navigating on the edge. We discuss the feasibility of using this theory in software engineering as an alternative to bureaucratic software development processes. We present also some recommendations that could help to acquire competitive advantage in software development, hence achieve information superiority.

show abstract

A Spiral Model of Software Development and Enhancement

Cited by 525 publications

References 7 publications

New Algorithm for Component Selection to Develop Component-Based Software with X Model

New Algorithm for Component Selection to Develop Component-Based Software with X Model

Experiences of engineering Grid-based medical software

Surfing the Edge of Chaos: Applications to Software Engineering

Contact Info

Product

Resources

About