• No results found

CONCLUSIONS AND SUGGESTIONS

6.1 Conclusions

This study implemented a selected module of PBS using a new approach of Software Engineering, namely the component-based Software Engineering. This implementation provides interoperability between two different systems of PBS with the access of a common module and avoids duplications for both systems. With this approach maintenance cost is expected to be reduced since components are designed to be independent.

Because of the fact that PBS has hybrid architecture in terms of its network infrastructure and software, PBS runs on two different network segments; one of them is TRANSPOL infrastructure extended all around Turkey and another one is Personnel intranet extended on only Personnel Department network. These two networks are separated with firewall by defining Personnel Department network as VPN (Virtual Private Network). In the first segment, PBS/Outside system is run while PBS/Inside is run on the other. Software architectures and environments are also different for these systems. Since most of the applications of PBS have different unique characteristics for each system, there seems no exploitation to build two different systems based on different business logics and software architectures.

However, despite this, some exceptional, complicated, and common business applications cannot be ignored. So these types of applications are not skipped, and distributed component architecture is accepted in PBS. This architecture is used with a new methodological approach, that is, component-based software engineering.

Service Calculation application is a necessity for PBS through both PBS/Outside system and PBS/Inside system. Because of its complicated characteristic, there will be confusion with the changes of its algorithm and structure. To prevent these

contaminations, it is decided to build these types of applications with distributed component technology, and EJB 2.0 is chosen for implementation. It is believed the more suitable development process model is COSE Process Model since its phases are designed for component-oriented approach.

Two GUIs allow users to access Service Calculation application through their various architectures and technologies. The GUIs, mentioned before can call every required function of Service Calculation application, using a remote interface of Service Calculation component. This ability means that interoperability is reached in this study.

Consequently, now the Service Calculation package is deployed on component container of PBS as a first EJB package. At the time of writing, it is being accessed by inside users of the system and tested. After providing satisfaction regarding integrity of calculations then it will be introduced to inside and outside users officially.

6.2 Suggestions

Component-based approach can increase software-building performance with effective component repository. If an organization does not consider importance of component repository, it becomes garbage-like, in the course of time. To avoid this, the component specification phase of COSE Process Model should be better considered and followed in detail and with sufficient care. If organizations like Personnel Department think to develop its repository in time, special care is especially needed in component specification. Shortly, this approach enforces first three phases, that is, specification, decomposition and component specification, to perform regularly. When they are performed as they should be, the rest works spontaneously.

COSE process model encourages an organization to develop a component repository for its business domain. This study will lead PBS to develop its similar modules within this methodology in the course of time.

For industry, there is a need for some bridges between component architectures to provide maximum profit from runtime-reusability. More effective connector technologies, based on standards, must be developed and consequently the system designers will not have to write code to glue various components that are running on various frameworks.

As a consequence, although it is inevitable due to reasons (interoperability) mentioned in this study, component-based approach needs more standardized methods to improve its effectiveness especially in practice.

REFERENCES

[1] PRESSMAN Roger, Software Engineering, McGraw Hill, 1997

[2] HERZUM Peter, SIMS Oliver, Business Component Factory, Wiley, 1999 [3] HUIZING M., Component Based Development, http://www.win.tue.nl/xootic

/magazine/jan-1999/huizing.pdf, last access:01.12.2005

[4] WANG Ju An, Towards Component-Based Software Engineering,

http://delivery.acm.org/10.1145/360000/357729/p182-wang.pdf?key1=357729&key2=7337455011&coll=GUIDE&dl=GUIDE&CFI D=36365381&CFTOKEN=91792709, last access:01.12.2005

[5] HILL, Bennett, McROBB, Farmer, Object Oriented System Analysis and Design (using UML), 2nd Edition, McGraw Hill, 2002

[6] ATKINSON Colin, BAYER Joachim, LAITENBERGER Oliver, ZETTEL Jörg, Component-Based Software Engineering:The KobrA Approach, http://se2c.uni.lu/tiki/se2c-bib_download.php?id=700, last access:01.12.2005 [7] DOGRU Ali H., TANIK Murat M., A Process Model for Component- Oriented

Software Engineering, IEEE Software, March/April 2003

[8] SCHACH Stephen R., Classical and Object Oriented Software Engineering, 4th Edition, McGraw Hill, 1999

[9] RUMBAUGH James, BLAHA Michael, PREMERLANI William, EDDY Frederick, LORENSEN William, Object Oriented Modelling and Design, Prentice Hall, 1991

[10] HEINEMAN George T., COUNCILL William T., Component-Based Software Engineering – Putting the Pieces together, Addison Wesley, May 2001

[11] STOJANOVIC Zoran, An Integrated Component-Oriented Framework for Effective and Flexible Enterprise Distributed Systems Development, http://www.betade.tudelft.nl/publications/ Stojanovic_CAISE2002.pdf, last Kurt, Volume II:Technical Concepts of Component-Based Software Engineering, http://www.sei.cmu.edu/pub/documents/

00.reports/pdf/00tr008.pdf, last access:01.12.2005

[14] SZYPERSKI Clemens, Component Software – Beyond Object-Oriented Programming, Addison Wesley, 1998

[15] KRUCHTEN Philippe, Modeling Component Systems with the Unified Modeling Language, “http://cis.cs.tu-berlin.de/Lehre/WS-0001/Sonstiges/

konteng_sem/papers/Modeling_Component_systems_with_UML.pdf”, last access:01.12.2005

[16] SZYPERSKI Clemens, Components and Objects Together, http://www.sdmagazine.com/documents/s=758/sdm9905b/9905b.htm?temp=N c58633QW6, last access:01.12.2005

[17] KAVIANPOUR Mansour, The Need For Component-Based Software, http://www.objs.com/workshops/ws9801/papers/paper008.doc, last access:01.12.2005

[18] LEFEBVRE Eric, LEVESQUE Ghislain, Enterprise-Component Models, http://www.lrgl.uqam.ca/publications/pdf/380.pdf, last access:01.12.2005 [19] BELLUR Umesh, The Role of Components & Standards in Software Reuse,

http://www.objs.com/workshops/ws9801/papers/paper012.pdf, last access:01.12.2005

[20] KOZAK Ayse, Component-Oriented Modelling Of Land Registry And Cadastre Information System Using COSEML, Master Thesis, 2002

[21] CAI Xia, LYU Michael R., WONG Kam-Fai, KO Roy, Component-Based Software Engineering: Technologies, Development Frameworks, and Quality Assurance Schemes, http://www.cse.cuhk.edu.hk/~lyu/paper_pdf/apsec.pdf, last access:01.12.2005

[22] MONSON-HAEFEL Richard, Enterprise JavaBeans, O’Reilly, 2001

[23] ÖZYURT Barış, Enforcing Connection-Related Constraints And Enhancements On A Component Oriented Software Engineering CASE Tool, Master Thesis, 2003

APPENDIX I

Related documents