| Mohamed Fayad and Marshall P. Cline. Aspects of Software Adaptability. Communications of the ACM, 39(10):58--9, October 1996. |
....are presented and discussed. 4.1 Rethinking the Web Service Life Cycle Adaptability is an important issue when building software of any sort [GJM91] Requirements change between the time when the customers say what they want and the time when the software is actually delivered. Fayad states in [FC96] that software that is being built 43 must be adaptable with respect to the ability to change the system s capabilities in amount and in kind, and the ability to fix the system without breaking other parts. Requirements Collection Design for Device Family Implementation for Device ....
Mohamed Fayad and Marshall P. Cline. Aspects of Software Adaptability. Communications of the ACM, 39(10):58--9, October 1996.
....quality of software. It has already been argued in the literature that the general feeling that OOP promotes reuse and expandability by its very nature is rather a misconception as none of these issues is enforced. Rather, a software system must be specifically designed for reuse and expandability [7]. A number of researchers are suggesting that the maximum potential for reuse is over the entire life cycle, where reuse is applied to each phase, and it must begin in the requirements phase. Another important issue is the one of the verification of components and aspects in isolation from each ....
Fayad, M., Cline, M., "Aspects of Software Adaptability", Communications of the ACM, 1996.
.... 1996] Furthermore, about one third of the time of the maintenance phase is spent on the user interface [Myers, Rosson, 1992] It makes no sense to talk about adaptability of software in general terms: a software system is adaptable (or not) in specific ways to specific changes and modifications ([Fayad, Cline, 1996]; Bass, Clements, Kazman, 1998] Amore precise and operational definition of adaptability of a software system (or a part of it) would be: the anticipation of specific changes and variations of the system, where anticipations of a specific change means building the software in such a way that ....
Mohamed Fayad, Marshall P. Cline, "Aspects of Software Adaptability", in: Communications of the ACM, vol. 39, iss. 10, October 1996, pp. 58, 59
....1. Operating System Design Issues The commercialization of operating systems has resulted in their design gaining more importance. Operating systems are constantly extended for improvements as well as to support new features and hardware. In order to support this, reusability and adaptability [8] of system software during design is crucial. Extensibility provides the capability to either change current features or support new features. Reliability is the ability of the system to providing the correct service over a period of time. Stability is the capability of the system maintaining the ....
Fayad, Mohamed E., Cline, M., Aspect of Software Adaptability, Communications of ACM, Vol.39 No. 10, pp.58-59, 1996.
....should be a refinement of the corresponding requirement specification and not an evolution of the latter. Finally the implementation should be a refinement of the design and not an evolution. In [43] the EVO method used at HP is described, wherein several incremental cycles are used. [44] gives some requirements that an adaptable system should satisfy, viz. extensibility, flexibility, performance tunability and fixability. In [12] the adaptive software development methodology is proposed. This methodology has three steps: speculate (which gives the general idea of where to go in ....
Fayad, M., and Cline, M.P. Aspects of Software Adaptability ,Communications of the ACM, Volume 39, No. 10, Oct. 1996, pp. 58-59.
....like troubleticketing systems, on line reservation systems, time card reporting systems, and online auctions, are becoming increasingly popular. To ensure high availability and reliability, these systems are often designed according to the design methodology of open distributed systems. In [Fayad and Cline 96] the authors argue that using OO technology does not guarantee that the resulting software is going to be adaptable. Rather, adaptability must be explicitly engineered into a software system and in places where it will do the most good to the business. As requirements change over time and as ....
....is going to be adaptable. Rather, adaptability must be explicitly engineered into a software system and in places where it will do the most good to the business. As requirements change over time and as slightly different problems arise over time, a system must be able to change and evolve. In [Fayad and Cline 96] the authors identify four factors that adaptability is associated with. Extensibility is defined as the ability to change the amount of the capabilities of the system, and flexibility is the ability to change the kinds of capabilities. Extensibility and flexibility imply high level changes. On ....
[Article contains additional citation context not shown here]
Mohamed Fayad, and Marshall P. Cline. Aspects of Software Adaptability. In Communications of the ACM. Vol. 39. No. 10. October 1996, pp. 58-59.
....the stage for enhancing the available system support to virtual enterprise management. The difficulty of business administration tasks to be solved and the complexity of even distributed virtual enterprise management systems results in a specific desire of intelligent system s behaviour. In [FC96] the authors recently request some degree of flexibility which is remarkably beyond the limits of current systems: In today s rapidly changing business environment, adaptability is a critical weapon for survival. p. 58) Their conclusion is immediate: It is no longer acceptable if a software ....
M. Fayad and M.P. Cline. Aspects of software adaptability. Communications of the ACM, 39(10):58--59, 1996.
....to an example and summarize the results. Lastly, we propose future research and summarize our ideas. 1. Introduction Because the market demands changes in application requirements, there is an increasing need for software systems to adaptively support changes in applicationlevel objectives [3]. A software system should be able to grow and change to solve slightly different problems over time: a software system should be easily changed with minimal error to satisfy changing requirements. Ease and reliability of modification is particularly important for high assurance applications such ....
M. Fayad and M.P. Cline, "Aspects of Software Adaptability", Communications of the ACM, Vol. 39, No. 10, Oct. 1996, pp. 58-59.
....not the first to notice that flexibility is critical in software design and that it has both costs and benefits that have to be weighed against each other. Information hiding [36] extension and contraction [37] and program family concepts [35] were seminal. More recently, Fayad and Cline [17], emphasize that flexibility has costs, that it should be designed in where it is economically the most effective. They see design patterns [15] as providing hinges needed for flexibility in particular dimensions. They even state that such hinges provide opportunities to make changes that ....
M. Fayad and M. Cline. Aspects of software adaptability. Communications of the ACM, 39(10):58--59, October 1996.
....set the stage for enhancing the available system support to virtual enterprise management. The difficulty of business administration tasks to be solved and the complexity of even distributed virtual enterprise management systems results in a specific desire of intelligent system s behaviour. In [FC96], the authors very recently request some degree of flexibility which is remarkably beyond the limits of current systems: In today s rapidly changing business environment, adaptability is a critical weapon for survival. p. 58) Their conclusion is immediate: It is no longer acceptable if a ....
Mohamed Fayad and Marshall P. Cline. Aspects of software adaptability. Communications of the ACM, 39(10):58--59, 1996.
....in software design, and that flexibility has both costs and benefits. Parnas s work on information hiding [26] ease of extension and contraction [27] and families of systems [25] goes to the heart of the matter, albeit without explicit appeal to financial concepts. More recently, Fayad and Cline [12], to cite just one example, emphasize that design flexibility has costs, that flexibility should be designed in in those areas where it makes the most economic sense. They identify design patterns [14] as providing the hinges that are needed for flexibility in particular dimensions. They even ....
M. Fayad and M. P. Cline. Aspects of software adaptability. Communications of the ACM, 39(10):58--59, Oct. 1996.
....in ways planned for by the framework designer. Flexing A hotspot is customized in a way that was not planned for by the framework designer, yet the customization is consistent with the obligations and constraints of the design. These two terms, extend and flex, are taken from Fayad and Cline [14], who characterize them as a change in amount but not in kind and a change in kind respectively. Evolving A framework is maintained to either increase the flexibility of existing hotspots, or to add new hotspots. Mining A framework is mined for ideas that might be applicable in other ....
M. Fayad and M. P. Cline. Aspects of software adaptability. CACM, 39(10):58--59, October 1996.
....framework. In this context, adaptability is an important and desirable quality factor in today s software evolution. This property defines the ability of a given software system to cope smoothly with changes in the problem specification, producing a low impact on components previously implemented [4]. In this way, systems are able to evolve and tackle different variations of a given problem. The lack of adaptability can become a critical issue if you want to scale up the system. Developers should not only think in the target system during the design phases but should also consider future ....
Fayad, M.E. and Cline, M.: Aspects of software adaptability, Communications of the ACM, 39(10), 58-59. 1996
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