- Technical issues doing XP #1 -
Software reuse has been a major issue on how to cut down the cost of software project. The characteristics of software components are inherently different with other industrial products in the aspect of reuse. Although pieces of software component that show similar functionality, a subtle difference how their interface is implemented or which language they were developed with makes these components totally distinguished things from each others with the view point of management. Since which module can communicate with this component or how this can be merged into new software would determine the cost required and tasks of building components, the manager of software project regards these characteristics related to the reuse as important factors that affect the whole project.
Evolution of technology has something to do with this issue indirectly or directly. Implementers of software solutions have been trying to find better ways to deal with reusability, connectivity, and usability to mention. Re-usability processes and concepts have brought to bear a new way of developing solutions, where the elements of the system are scattered all over the world or local area network. System construction mostly deals with the exploring, finding and usage of ready-made functionality. This functionality could have been created by an organization’s developers or might have been borrowed or bought from a provider of the functionality. One of questions that need answering is: how developers make component feasible and have compatibility for extension to other module to decrease the cost of project and increase the flexibility of the product.
Object orient language makes it possible that we can isolate functionality as component and engraft portability. But in many cases, we have faces its limitations that do not allow globally interoperable communication. The two components from different technology don’t talk each other. Bean from EJB has no way to be merged into COM from Microsoft, because of its different language and protocol spec. Low level standardization such as language specific protocol does not provide advantages in varies organization using various technology. With higher level of concept then implementation specific languages, managers want to focus on business more. It is web services technology that emerges satisfying this requirement in some degree. In this paper, I will write on what are web services and how to utilize this technology with the view point of reuse. The software reuse, consequently, allows us to concentrate on the designing of business model rather than implementation itself. Managers now need to prepare to set up strategy that reveals the factors on cost-downing management and effective maintenance of project using this technology. I will discuss what should be considered to achieve effective adoption of this reuse-allowable technology and how to reduce cost with maintaining or increasing of quality of product by adopting this web services in STP project as an example.
The whole report is linked, password for pdf is "park"
Management of software reuse with Web services.pdf
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment