Formal specification of non-functional properties in component Research Paper

Formal specification of non-functional properties in component software engineering - Research Paper Example Component-based software engineering (CBSE) is observed as the best example of such technique (Chen, 2004). It assists in handling the intricacy through following a divide-and-conquer tactic, modularizing huge software schemes into smaller, reusable elements called (software) units. CBSE is believed to be chiefly effective in the background of what is referred to as unit markets, where units are established by autonomous third party establishers and purchased by application contractors to be organized into full applications. If the elements are to be bartered on component markets, they have to be escorted by a specific illustration of all of their pertinent properties (Lamanna, 2002). Element developers must articulate such an illustration without understanding the background in which their elements will be employed. Conversely, it has to be clear to the application contractors and has to be achievable for them to create specifications of distinct elements and rationalize about possessions of the ultimate system. For instance, application contractors need to acknowledge whether an application constructed from some set of elements (Bechhofer, 2005). These elements are organized on a system with reliable amount of present resources will accomplish the required execution goals, how much network bandwidths or memory will be devoured or whether data value will meet the needed benchmark. Thesis statement The ultimate aim of this report is to examine the concept of formal specification of non-functional properties in component software engineering. This entails reviewing the entire aspect of software development and looks at the specification languages that already exist as well as examining the component forms related to specification languages . The paper then examines the problems statement and the research plan then winds up with a conclusion. Literature Review General Concept of Software Development The following diagram (figure 1) provides an indication of the general software development procedure for non-functional characteristics. The main concept of approach is the division of measurement description usage meaning that precision of non-functional characteristics of applications using those gauges. A measurement refers to something that is practical to a system and produces quality value for the scheme being gauged (Chen, 2004). Examples of measurements are d elay, response time et cetera. Measurements are mostly described in relation to a contextual model which defines the concepts of an application system that has to be recognized in order to develop the measurement value. Therefore, dimension can be described autonomously as a real practical system. To employ measurements to a practical system, a mapping between the component model of the practical scheme and the context model of the measurement must be illustrated. The descriptions of measurements can be sophisticated, but on the other hand, it will be developed only a single time. Thus, the roles of dimension designer and practical designer must be put apart in the development process. According to Heiko  Ludwig 2004, their joint efforts directs to a precision of the system encompassing its non-functional characteristics (Bechhofer, 2005). The measurement modeler employs a graphical notation centered on the specification language CQML+ [2] and notions from [3] to identify measurem ents and their context designs (Zschaler, 2008). Ludwig adds on that designer can then described distinct