Competence and No Holes in Software Models Essay

Submitted By spananand
Words: 1304
Pages: 6

CmpE 202 – Software System Engineering
Individual Essay

Essay Topic: Competence and no holes in modeling
Abstract
Motivation:
When a model is not competent then it fails to produce what is required by the system. Hence the performance of the system drops. If there are defects in the model, the system might perform differently than what it is suppose to do. If the defects are identified during modeling, it requires less effort and cost to fix it. Incompetent model will produce a poor quality system.

Goal:
To prevent defects or holes in modeling and to come up with better ways of determining the competencies that are required by the model to perform well. To identify competency modeling strategies to built a high quality system.

Competence is the capability of performing the allotted or required function accurately. Competence in modeling is the activity of identifying the specific competencies that are required by the model to give high performance and success in a given job. No holes in modeling means when designing a model, there should not be any defect in the model by making wrong assumptions.

Major Findings or Impacts:
When you develop a competent model with no holes,
It enables to achieve accurate results thereby creating value.
It helps in producing high quality, high performance products.
It promotes the development of the company’s success.

1.Introduction:

In this report, I describe the use of traditional model versus Software Stability Model focusing on the importance of competence and no holes in modeling. This is achieved using Real-Time system as a base for comparison. The comparison and analysis of both the models in the following essay provides the pros of using SSM over Traditional Model along with the results displaying proofs for the same.

The Software Stability Model design strategy is partitioned into three different levels: Enduring Business Themes (EBTs), Business Objects (BOs) and Industrial Objects (IOs). The EBTs represent elements that remain stable internally and externally. EBTs are realized through aims, objectives and requirements of the Software. Whereas, BOs are objects that are internally stable but externally adaptable and describe the capabilities along with the goals to accomplish EBTs. IOs are the external interface of the system such as application objects. The Software developed using SSM remains stable and change in business requirements can be easily accommodated in the software design. The focus is on prolonged existence of software and there by making the model more competent and reduces the defects in the model which eventually reduces the maintenance cost.

Traditional Model:

Describing in section is one of the traditional model which is popularly used in software development process. Presented here are the basic concept of the traditional model.
There are number of traditional software models like waterfall model, V model, Spiral model. The waterfall model as shown in the figure 1, is a popular version of the systems development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential. Waterfall development has distinct goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the same with waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back. Which makes the model less flexible.

[pic]
Figure 1: The waterfall model
The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. Hence making the…