Here is the synopsis of our sample research paper on Component Based Software Development and its’ Maintenance. Have the paper e-mailed to you 24/7/365.
Essay / Research Paper Abstract
This 8 page paper examines the use of Component Based Software Development (CBSD), what it is, how it works, the advantages and disadvantages of the system and the implications n terms of managing the system when it is up and running. The bibliography cites 8 sources.
Page Count:
8 pages (~225 words per page)
File: TS14_TEcombsd.rtf
Buy This Term Paper »
Unformatted sample text from the term paper:
generally seen as a good method of increasing cost efficiency in software development (Szyperski, 1997). The benefit is not only the report but also the increased reliability of the software
when it is up and running, decreasing pressure on maintenance (Szyperski, 1997). By understanding the basics of Component Based Software Development we are in a better position to assess
its benefits in a maintenance scenario. There are two main elements to CBSD; the component architecture and the competent based development procedure.
The architecture acts as a standard foundation for the reuse of software components as this reutilisation will not be able to take place if architecture is not standardised (Ning, 1996).
The component development process is then able to use the components that are reused as a central aspect of software development
(Ning, 1996). The need for standard software architectures are essential for this reuse, and architecture such as Active X (Denning, 1996). COBRA and JavaBeans (Hamilton, 1997) and Enterprise JavaBeans (Matena
et al, 2000). The main elements of this component architecture are the component framework, the components, the component contracts, the coordination services, and the glue codes (Szyperski, 1997). The
component framework affords a selection of coordination of runtime services, which support the component model and enforce the model (Ning, 1996). The component model is made up of the
component types, the interfaces of these types and the rules of the patterns of interaction which could be allowed between these component types (Gao et al, 2003). The component
is the a software performance that can take place on either a logical device or a physical device. The component will execute the imposed interfaces and must satisfy specific component
...