Abstract
We propose to compute the complexity metrics of component based software in more justified way by taking considerations of their using frequencies. The complexity metrics calculation of the component Based softwares by using black box testing is still not refined. The reason is that the various components are not used by the end users uniformly. Again, use of various components depends upon user to user as per their requirements. So therefore calculating straight forward their complexity on the basis of number of components, their interfaces and data types are not sufficient. We must add the factor of their (AUF) average use factor by the customers of different components. As we know that every algorithm or program have 3 complexity states i.e . a) Best Case b) Average case and c) Worst case. As we know that each and every components of software is not used uniformly by the users. So calculating merely on the basis of their no of components, interfaces and data types predicts only theoretical complexity of that software. If we wish to calculate more justified complexity metrics then we must normalize these components on the basis of their frequency of use in normal routine. As it's quite possible that some modules or components are rarely used by common users. In this case those components hardly influence the complexity of that software. Thus we can reduce significantly the complexity of component based software which was earlier hypothetically calculated very high.
Highlights
Component-based software development (CBD) is an emerging discipline that promises to take software engineering into a new era
Building on the achievements of object-oriented software construction, CBD aims to deliver software engineering from a cottage industry into an industrial age for Information Technology, wherein software can be assembled from components, in the manner that hardware systems are currently constructed from kits of parts
We propose to compute the complexity metrics of component based software in more justified way by taking considerations of their using frequencies
Summary
Component-based software development (CBD) is an emerging discipline that promises to take software engineering into a new era. Building on the achievements of object-oriented software construction, CBD aims to deliver software engineering from a cottage industry into an industrial age for Information Technology, wherein software can be assembled from components, in the manner that hardware systems are currently constructed from kits of parts. This volume provides a survey of the current state of CBD, as reflected by activities that have been taking place recently under the banner of CBD, with a view to giving pointers to future trends. Proposed work: We use case studies and complexity metrics formula and multiply it with the assumed usability factor points for each component to calculate the complexity. Total Installed space Occupied: 523 MB MS Office Setup Size 562 MB On the basis of survey a common user use above different available MS office package as follows: Using Frequencies by average user (UF)
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: INTERNATIONAL JOURNAL OF MANAGEMENT & INFORMATION TECHNOLOGY
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
