Software Plug and Play

dc.contributor.guideKesav Vithal Nori
dc.coverage.spatial
dc.creator.researcherAnand Kumar
dc.date.accessioned2017-04-18T11:07:30Z
dc.date.available2017-04-18T11:07:30Z
dc.date.awarded31/07/2017
dc.date.completed30/03/2017
dc.date.registered31-12-2008
dc.description.abstractThis thesis considers Software Plug and Play (PNP) as a potentially useful architectural abstraction (AA) that can solve many software architecture (SA) problems faced by vertical markets in the industry. While PNP as a technology has been utilized to address many extensibility concerns in hardware, there is no systematic support for similar extensibility notion at the SA level. To address these concerns, this thesis proposes the creation of frameworks and component models to support PNP. Accordingly, this thesis considers PNP as a user-defined framework, supported by a run-time component library that is embedded in the component schema, in order to support functional and structural extensibility of a running software system. newlineAs practitioners, it was decided that the inductive path of Clayton Christensen s approach for theory building would be an appropriate way to build the architectural foundations for PNP. Accordingly, this approach was adopted to empirically study six graded systems that had decreasing requirements on their environments. Through this empirical and experimental work, the notion of software components, components composition and SA was illustrated. Further, the architecture principles that were adopted to enable PNP in these systems aided in identifying the corresponding PNP AA. Based on this experimental experience, this thesis contributes the following to the field of computer science and SA: newline1. The concept that PNP is a collection of standards, encoded in the run-time components and embedded in the component schema, for supporting extensibility of a running software system. newline2. The characterization of PNP in terms of underlying architecture principles, and corresponding AA. newline3. The formulation of a generic PNP component model, that supports this characterization, which when instantiated aids in realizing pure PNP architectures. newline4. An expression of the Plug and Socket interfaces, that are constituent elements of the PNP component model, by means of abstract data types.
dc.description.note
dc.format.accompanyingmaterialNone
dc.format.dimensions
dc.format.extentxii,210
dc.identifier.urihttp://hdl.handle.net/10603/146469
dc.languageEnglish
dc.publisher.institutionComputer Science and Engineering
dc.publisher.placeHyderabad
dc.publisher.universityInternational Institute of Information Technology, Hyderabad
dc.relation
dc.rightsself
dc.source.universityUniversity
dc.subject.keywordComponent model
dc.subject.keywordComponent schema
dc.subject.keywordDynamic Composition
dc.subject.keywordEmpirical study
dc.subject.keywordExperimentation
dc.subject.keywordPlug and Play
dc.subject.keywordPlug and Sockets
dc.subject.keywordSoftware Architecture
dc.subject.keywordTheory building
dc.titleSoftware Plug and Play
dc.title.alternative
dc.type.degreePh.D.

Files

Original bundle

Now showing 1 - 5 of 22
Loading...
Thumbnail Image
Name:
01_title.pdf
Size:
315.09 KB
Format:
Adobe Portable Document Format
Description:
Attached File
Loading...
Thumbnail Image
Name:
02_copyright.pdf
Size:
133.78 KB
Format:
Adobe Portable Document Format
Loading...
Thumbnail Image
Name:
03_certificate.pdf
Size:
64.44 KB
Format:
Adobe Portable Document Format
Loading...
Thumbnail Image
Name:
04_acknlowledgement.pdf
Size:
146.22 KB
Format:
Adobe Portable Document Format
Loading...
Thumbnail Image
Name:
05_abstract.pdf
Size:
239.53 KB
Format:
Adobe Portable Document Format

License bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
license.txt
Size:
1.79 KB
Format:
Plain Text
Description: