Sea Level Requirements as Systems Engineering Size Metrics

The Constructive Systems Engineering Cost Model (COSYSMO) represents a collaborative effort between industry, government, and academia to develop a general model to estimate systems engineering effort. The model development process has benefited from a diverse group of stakeholders that have contributed their domain expertise and historical project data for the purpose of developing an industry calibration. But the use of multiple stakeholders having diverse perspectives has introduced challenges for the developers of COSYSMO. Among these challenges is ensuring that people have a consistent interpretation of the model’s inputs. A consistent understanding of the inputs enables maximum benefits for its users and contributes to the model’s predictive accuracy. The main premise of this paper is that the reliability of these inputs can be significantly improved with the aide of a sizing framework similar to one developed for writing software use cases. The focus of this paper is the first of four COSYSMO size drivers, # of Systems Requirements, for which counting rules are provided. In addition, two different experiments that used requirements as metrics are compared to illustrate the benefits introduced by counting rules

Effect of Different UML Diagrams to Evaluate the Size Metric for Different Software Projects

In Software Engineering, an important activity is measuring of the Software in different ways. For Measuring the Software, appropriate metrics are needed. Using Software metrics we are able to attain the various qualitative and quantitative aspects of Software. To measure the Software in terms of quality, size, efforts, efficiency, and reliability, performance etc. we have different metrics available in Software Engineering and it has been an area of interest for the various researchers. Measures of specific attributes of the process, project and product are used to compute Software metrics. This work proposes a similar approach of measuring software using various UML diagrams and applied Software size metric to evaluate the size of the Software. This paper discusses the proposed approach using two different case studies and their source codes. This paper discusses the different results obtained using different perspectives of the Software size metric measurements and maintainability of the Software