Characteristics of Components in Conponent-based Computing or Component-based Software Engineering

-



 Characteristics of components

·         Standardized: Component standardization means that a component that is used in a CBSE process has to conform to some standardized component model. This model may define component interfaces, component meta-data, documentation, composition and deployment.

·         Independent: A component should be independent – it should be possible to compose and deploy it without having to use other specific components. In situations where the component needs externally provided services, these should be explicitly set out in a ‘requires’ interface specification.

·         Composable: For a component to be composable, all external interactions must take place through publicly defined interfaces. In addition, it must provide external access to information about itself such as its methods and attributes.

·         Deployable: To be deployable, a component has to be self-contained and must be able to operate as a stand-alone entity on some component platform that implements the component model. This usually means that the component is a binary component that does not have to be compiled before it is deployed.

·         Communicate: With regard to system-wide co-ordination, components communicate with each other via interfaces. When a component offers services to the rest of the system, it adopts a provided interface that specifies the services that other components can utilize, and how they can do so. This interface can be seen as a signature of the component - the client does not need to know about the inner workings of the component (implementation) in order to make use of it. This principle results in components referred to as encapsulated.

·         Substitutable: Another important attribute of components is that they are substitutable, so that a component can replace another (at design time or run-time), if the successor component meets the requirements of the initial component (expressed via the interfaces). Consequently, components can be replaced with either an updated version or an alternative without breaking the system in which the component operates.

·         Reusable: Reusability is an important characteristic of a high-quality software component. Programmers should design and implement software components in such a way that many different programs can reuse them. Furthermore, component-based usability testing should be considered when software components directly interact with users. It takes significant effort and awareness to write a software component that is effectively reusable. The component needs to be:
i.                    fully documented
ii.                  thoroughly tested
a.       robust - with comprehensive input-validity checking
iii.                designed with an awareness that it will be put to unforeseen uses
·         Documented: Components have to be fully documented so that potential users of the component can decide whether or not they meet their needs. The syntax and, ideally, the semantics of all component interfaces have to be specified.

Comments

Post a Comment

Popular posts from this blog

How to fill your IT SIWES Logbook for Industrial Training (A guide for Nigerian Undergraduates)

-
Image
  Student Industrial Work Experience Scheme SIWES  was established by  ITF  in 1973 to solve the problem of lack of adequate practical skills preparatory for employment in industries by Nigerian graduates of tertiary institutions. The Scheme exposes students to industry based skills necessary for a smooth transition from the classroom to the world of work. It affords students of tertiary institutions the opportunity of being familiarized and exposed to the needed experience in handling machinery and equipment which are usually not available in the educational institutions. Participation in  SIWES  has become a necessary pre-condition for the award of Diploma and Degree certificates in specific disciplines in most institutions of higher learning in the country, in accordance with the education policy of government. Operators - The ITF, the coordinating agencies (NUC, NCCE, NBTE), employers of labour and the institutions. Funding - The Federal Government of N
Read more

How to fill your IT documents - SCARF form or SP1 form

-
Image
                                                             SCARF form or SP1 form   This is one of the forms given alongside the logbook. It is one of the forms you are expected to submit to the ITF office nearest to your place of work. It has a space for "From", is the name of the person signing the form who is expected to be a staff in that firm. Then an allocation for Name of the organization that you are attached in and then the address of that organization. The other columns include the students name, your matriculation number, your present level in school, name of your institution, period of your attachment is the time frame of your IT,  the date you commenced work and the date you are expected to finish your IT program. This document is filled, signed and stamped by the employer within two weeks of starting your IT and then submitted to both your school and ITF office.
Read more

A Seminar on Component Based Computing; Component based Software Engineering

-
CHAPTER 1 INTRODUCTION 1.1        BACKGROUND OF THE STUDY   Developing cost-effective and quality products is an important and challenging aspect of software development. Component-based software development can help developers to efficiently produce software within the time and budget constraints. The concept of component-based software engineering (CBSE) is based on the development of independent and loosely coupled components of the system, by avoiding irrelevant dependency among system components. CBSE focuses on linkage among different components in a way that one component can provide services to another through different interfaces. This way of development of normalize components facilitates rapid software development. The field of software systems has become increasingly intricate and performance specific. To produce cost-effective systems, organizations often make use of component-based technologies as an alternative to developing the whole system from scratch
Read more