Grant: Discovery Grants Program - Individual
Dalhousie University
$14,500.00
Building robust software with fallible construction
EF 2006-07
Résumé
Many of today's systems depend on large, complex software with the need to be built and deployed more rapidly and cheaper than traditional development methods can deliver. Moreover, because organizations depend on these systems, they must be more predictable and trustworthy than traditional development methods can deliver for the available time and cost investments. However this requirement is not quite compatible with the traditional project-oriented view of software development, which is prevalent in the acquisition methods of many organizations. Today's systems are typically integrated from components. These components may themselves contain flaws,originating in specification, design or implementation errors, or in miscommunication between different teams involved in the development. More seriously, the integration process itself may be flawed, as when pre-existing components are used for purposes that their developers had not envisioned, and the integrators misunderstand the detailed behaviour of the components. Interoperability failures between systems belonging to different organizations often are of this form. Attempting to build infallible systems with fallible construction methods may be too stringent an expectation to achieve, but the weaker objective of resilience to failure and outages may be more realistic. Experience with interoperating commercial products, especially in the context of the Internet, indicates that robustness to fallible components and fallible integration can be achieved without centralized predictive coordination. Appropriate software architecture, redundancy in functional alternatives, and enforcement of critical interface standards in middleware in particular appear to be key elements of success. Autonomic computing techniques, such as improved registry and plug-and-play concepts, can help automate integration and reduce configuration problems.
Programme
Discovery Grants Program - Individual
Bénéficiaire
Emplacement
Nova Scotia, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data
Tel que publié
Application id
7407-2006
Name nom
Gentleman, Morven
Department département
Computer Science, Faculty of
Organization id
79
Institution établissement
Dalhousie University
Province en
Nova Scotia
Province fr
Nouvelle-Écosse
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2006
Competition year année de concours
2006
Award amount
14500
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
Discovery grants programs
Group fr
Programmes de subventions à la découverte
Committee code
330
Committee name en
Computing and Information Sciences - A
Committee name fr
Informatique - A
Area of application code
800
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Information and communication services
Area of application fr
Services d'information et de télécommunications
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Partie
1
Nb partie
3
Application title
Building robust software with fallible construction
Keyword
NA
Application summary
Many of today's systems depend on large, complex software with the need to be built and deployed more rapidly and cheaper than traditional development methods can deliver. Moreover, because organizations depend on these systems, they must be more predictable and trustworthy than traditional development methods can deliver for the available time and cost investments. However this requirement is not quite compatible with the traditional project-oriented view of software development, which is prevalent in the acquisition methods of many organizations. Today's systems are typically integrated from components. These components may themselves contain flaws,originating in specification, design or implementation errors, or in miscommunication between different teams involved in the development. More seriously, the integration process itself may be flawed, as when pre-existing components are used for purposes that their developers had not envisioned, and the integrators misunderstand the detailed behaviour of the components. Interoperability failures between systems belonging to different organizations often are of this form. Attempting to build infallible systems with fallible construction methods may be too stringent an expectation to achieve, but the weaker objective of resilience to failure and outages may be more realistic. Experience with interoperating commercial products, especially in the context of the Internet, indicates that robustness to fallible components and fallible integration can be achieved without centralized predictive coordination. Appropriate software architecture, redundancy in functional alternatives, and enforcement of critical interface standards in middleware in particular appear to be key elements of success. Autonomic computing techniques, such as improved registry and plug-and-play concepts, can help automate integration and reduce configuration problems.