Subscribe Now Subscribe Today
Science Alert
Curve Top
Journal of Software Engineering
  Year: 2010 | Volume: 4 | Issue: 1 | Page No.: 16-29
DOI: 10.3923/jse.2010.16.29
Facebook Twitter Digg Reddit Linkedin StumbleUpon E-mail

Candidate Process Models for Component Based Software Development

K. Kaur and H. Singh

Component Based Software development approach promises high quality, low budget software with shorter time to market. Reuse of the already existing software components (irrespective of their development or implementation platform) is the focal point of this approach. Component Based Software is different from traditional programs. Software development process models used for writing the traditional programs cannot be used for assembling the application using reusable software components. This study points out the differences in these two development paradigms and the inappropriateness of the traditional process models for developing component based software. A process model for this new approach should incorporate the activities to address the important aspects (such as component selection, customization and composition) required for building high quality component based software. The study investigates the component based software development process models in view of the prescribed international standards. It also presents a review of the current industrial practices as far as the software development process models are concerned.
PDF Fulltext XML References Citation Report Citation
  •    Deploying Holistic Meta-modeling for Strategic Information System Alignment
  •    Towards Quantitative Assessment Model for Software Process Improvement in Small Organization
  •    A Fine Parameter Tuning for COCOMO 81 Software Effort Estimation using Particle Swarm Optimization
How to cite this article:

K. Kaur and H. Singh, 2010. Candidate Process Models for Component Based Software Development. Journal of Software Engineering, 4: 16-29.

DOI: 10.3923/jse.2010.16.29


16 November, 2010
Good Morning
I read your article and I have a question related to one of the component based software development life cycle. I hope that you could help me!

I read about "Y model component based software development life cycle" since I have to use it n my graduation project . However, I have some questions:

- Why there is repetition in the outcome of the phases ( e.g: domain engineering and system analysis.. or .. frameworking and design )?

- It was mention that there is overlap between the phases, but I didn't see anything in its diagram that indicate overlapping?

- Suppose that an expert will use it: the expert will follow top-down approach and thus will start from system analysis. In this case, would he go for framworking and domain engineering after finishing the assembly/archiving phase? or he will simply ignore these phases? But if he ignore them, I think the SDLC will be similar to water fall , am I right?

Thanks in advance




Curve Bottom