Analyzing design patterns for extensibility
| dc.contributor.author | Annappa, B. | |
| dc.contributor.author | Rajendran, R. | |
| dc.contributor.author | Chandrasekaran, K. | |
| dc.contributor.author | Shet, K.C. | |
| dc.date.accessioned | 2026-02-06T06:40:30Z | |
| dc.date.issued | 2011 | |
| 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. | |
| dc.identifier.citation | Communications in Computer and Information Science, 2011, Vol.157 CCIS, , p. 269-278 | |
| dc.identifier.issn | 18650929 | |
| dc.identifier.uri | https://doi.org/10.1007/978-3-642-22786-8_34 | |
| dc.identifier.uri | https://idr.nitk.ac.in/handle/123456789/32975 | |
| dc.subject | Design analysis | |
| dc.subject | Design patterns | |
| dc.subject | Extensibility | |
| dc.subject | Extensible application | |
| dc.subject | Software development | |
| dc.title | Analyzing design patterns for extensibility |