Please use this identifier to cite or link to this item:
https://idr.l3.nitk.ac.in/jspui/handle/123456789/7370Full metadata record
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | Annappa, B. | - |
| dc.contributor.author | Rajendran, R. | - |
| dc.contributor.author | Chandrasekaran, K. | - |
| dc.contributor.author | Shet, K.C. | - |
| dc.date.accessioned | 2020-03-30T09:58:56Z | - |
| dc.date.available | 2020-03-30T09:58:56Z | - |
| dc.date.issued | 2011 | - |
| dc.identifier.citation | Communications in Computer and Information Science, 2011, Vol.157 CCIS, , pp.269-278 | en_US |
| dc.identifier.uri | http://idr.nitk.ac.in/jspui/handle/123456789/7370 | - |
| dc.description.abstract | A system is said to be extensible, if any changes can be made to any of the existing system functionalities and/or addition of new functionalities with minimum impact. To achieve extensibility, it has to be planned properly starting from the initial stage of the application development. Keeping in mind all the possible future changes to be made, the designer should select the proper design patterns and finish the design for the application. Once the application design is finished, it should be analyzed to make sure that the application is extensible. � Springer-Verlag Berlin Heidelberg 2011. | en_US |
| dc.title | Analyzing design patterns for extensibility | en_US |
| dc.type | Book chapter | en_US |
| Appears in Collections: | 2. Conference Papers | |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.