Estimation of Defect proneness Using Design complexity Measurements in Object- Oriented Software

Software engineering is continuously facing the challenges of growing complexity of software packages and increased level of data on defects and drawbacks from software production process. This makes a clarion call for inventions and methods which can enable a more reusable, reliable, easily maintainable and high quality software systems with deeper control on software generation process. Quality and productivity are indeed the two most important parameters for controlling any industrial process. Implementation of a successful control system requires some means of measurement. Software metrics play an important role in the management aspects of the software development process such as better planning, assessment of improvements, resource allocation and reduction of unpredictability. The process involving early detection of potential problems, productivity evaluation and evaluating external quality factors such as reusability, maintainability, defect proneness and complexity are of utmost importance. Here we discuss the application of CK metrics and estimation model to predict the external quality parameters for optimizing the design process and production process for desired levels of quality. Estimation of defect-proneness in object-oriented system at design level is developed using a novel methodology where models of relationship between CK metrics and defect-proneness index is achieved. A multifunctional estimation approach captures the correlation between CK metrics and defect proneness level of software modules.Comment: 5 pages, 1 figur

Integrated Modeling of Process- and Data-Centric Software Systems with PHILharmonicFlows

Process- and data-centric software systems require a tight integration of processes, functions, data, and users. Thereby, the behavioral perspective is described by process models, while the information perspective is captured in a data model. Eliciting and capturing requirements of such software systems in a consistent way is a challenging task, demanding that both process and data model are well aligned and consistent with each other. While traditional software modeling languages do not allow for an explicit integration of data and process models, activity-centric process modeling languages tend to neglect the role of data as a driver of process execution; i.e., business objects are usually outside the control of the process, normally stored in external databases. To overcome this drawback, PHILharmonicFlows provides a comprehensive framework for enabling object-aware process support. In addition, a sound specification of process- and object-centric software systems becomes possible. In this paper, we present a requirements modeling approach that provides methodological guidance for modeling large process- and data-centric software systems based on PHILharmonicFlows. Such guidance will foster the introduction of respective software systems in the large scale

Generic unified modelling process for developing semantically rich, dynamic and temporal models

Models play a vital role in supporting a range of activities in numerous domains. We rely on models to support the design, visualisation, analysis and representation of parts of the world around us, and as such significant research effort has been invested into numerous areas of modelling; including support for model semantics, dynamic states and behaviour, temporal data storage and visualisation. Whilst these efforts have increased our capabilities and allowed us to create increasingly powerful software-based models, the process of developing models, supporting tools and /or data structures remains difficult, expensive and error-prone. In this paper we define from literature the key factors in assessing a model’s quality and usefulness: semantic richness, support for dynamic states and object behaviour, temporal data storage and visualisation. We also identify a number of shortcomings in both existing modelling standards and model development processes and propose a unified generic process to guide users through the development of semantically rich, dynamic and temporal models

Development of a Systems Engineering Model of the Chemical Separations Process: Final Report

The whole chemical separation process is complex to the point that definitely requires certain level of systematic coordination. To perform smoothly and meet the target extraction rates among those processes, this research proposed a general-purpose systems engineering model. A general purposed systems engineering model, Transmutation Research Program System Engineering Model Project (TRPSEMPro), was developed based on the above design concept. The system model includes four main parts: System Manager, Model Integration, Study Plan, and Solution Viewer. TRPSEMPro can apply not only to chemical separation process, but also a general system model. Software engineering and Object Oriented Analysis and Design (OOA&D) play a critical role during our software development. Through the application of OOA&D, the user can define objects and concepts from our problem domain that is quantitatively described by Unified Modeling Language (UML). The logical software objects were created from the previous definition. Meanwhile, different design patterns were also applied during the detailed design phase. Finally, those designed components were implemented by using MicrosoftTM.Net, the most up-to-date object-oriented programming language framework from Microsoft. Currently, only the UREX process module is available and ready to be implemented. Since extraction modules can be developed from various agencies with different development concepts and programming conventions, an intermediate bridge or interpreter is generally required. The system connects the only available process, UREX and with the TRPSEMPro system model from the AMUSESimulator interface. The AMUSESimulator communicates with the calculation engine AMUSE macros designed for the UREX process. A user-friendly GUI in AMUSESimulator allows the user to efficiently define the UREX process – flowsheet, input streams, sections, and stages

Identification Model of the Object Oriented Technology risks, for Avionics Certification

International audienceThe introduction of any new technology in an existing industrial process has a dual effect: on the one hand, it is expected to bring some well-identified benefits, but on the other hand, it also brings a certain number of new risks. It is the role and responsibility of decision makers, designers, and developers to estimate and balance these two aspects, taking into account the very specific characteristics of their industrial domain. In the domain of software systems, for instance, object-oriented technologies have been demonstrated to increase software quality and productivity, but they simultaneously bring some specific risks that must be carefully characterized and handled, especially when they are integrated in the development of software applications for critical systems. In the avionics domain, the OOTiA document proposes a first and informal identification of some of these risks. However this identification process misses the formal background that would guarantee its consistency and completeness. In this paper, we suggest to fill this gap by considering the management of software risk as a specific case of industrial risk management. To achieve this goal, we propose a generic model for the identification of software risks. This model provides the information required by the subsequent phases of risk management: risk estimation, risk acceptance, and risk mitigation

Building Information Modelling (BIM)—versioning for collaborative design

The engineering design process is a complicated activity. It is often characterized by multi-disciplinary teams in multiple places working together on a single project, using different models and software tools. In addition, such activities generate a large amount of data that require exchange among designers and stages of the work. In industry, the current collaboration approaches often focus on integrating and managing multiple models from multi-designers. Building Information Modelling (BIM) is playing a major role in facilitating collaboration. BIM provides an opportunity to electronically model and manage the vast amount of information embedded in a building project, from conception to completion. In the building design process, changes and modifications are inevitable even in the contemporary BIM approach. Such changes need to be well managed to keep track of changes to ensure that designers have an up-to-date version of the BIM model. The main goal of this research is to develop a collaborative BIM platform that tackles the challenges of integrating object versioning, as a change management approach, and an IFC model, as data representation of BIM. This has been done through suggesting new IFC extensions to add further concepts representing the history of changing to any object of the model. It also explores possibilities of adding or merging object-based change information to existing BIM models to enable the representation of design intentions, identification of affected changes numerically and visually. A prototype system is implemented in C#, using .NET framework and Revit API platform. This paper concludes that the proposed system can contribute to improving collaboration - in terms of tracking and management of affected changes during multi-disciplinary design process

MODELING REQUIREMENTS FOR FUTURE: ISSUES AND IMPLEMENTATION CONSIDERATIONS

In this paper, we discuss some requirements for future CASE (Computer Aided Software/Systems Engineering) environments. These requirements include increased modifiability and flexibility as well as support for task and agent models. We claim that they can only be addressed by developing more powerful representation and modeling techniques. As a possible basis for a modeling technique, we propose the GOPRR (Graph-Object-Property-Relationship-Role) data model, which addresses some of these requirements. In addition, a general information architecture for a future CASE environment is outlined. It includes three kinds of models for methodology specification: meta-datamodels, activity (task) models, and agent models. These models are defined using the GOPRR model with some additional concepts for IS development process and agent participation

A cognitive model of fiction writing.

Models of the writing process are used to design software tools for writers who work with computers. This thesis is concerned with the construction of a model of fiction writing. The first stage in this construction is to review existing models of writing. Models of writing used in software design and writing research include behavioural, cognitive and linguistic varieties. The arguments of this thesis are, firstly, that current models do not provide an adequate basis for designing software tools for fiction writers. Secondly, research into writing is often based on questionable assumptions concerning language and linguistics, the interpretation of empirical research, and the development of cognitive models. It is argued that Saussure's linguistics provides an alternative basis for developing a model of fiction writing, and that Barthes' method of textual analysis provides insight into the ways in which readers and writers create meanings. The result of reviewing current models of writing is a basic model of writing, consisting of a cycle of three activities - thinking, writing, and reading. The next stage is to develop this basic model into a model of fiction writing by using narratology, textual analysis, and cognitive psychology to identify the kinds of thinking processes that create fictional texts. Remembering and imagining events and scenes are identified as basic processes in fiction writing; in cognitive terms, events are verbal representations, while scenes are visual representations. Syntax is identified as another distinct object of thought, to which the processes of remembering and imagining also apply. Genette's notion of focus in his analysis of text types is used to describe the role of characters in the writer's imagination: focusing the imagination is a process in which a writer imagines she is someone else, and it is shown how this process applies to events, scenes, and syntax. It is argued that a writer's story memory, influences his remembering and imagining; Todorov's work on symbolism is used to argue that interpretation plays the role in fiction writing of binding together these two processes. The role of naming in reading and its relation to problem solving is compared with its role in writing, and names or signifiers are added to the objects of thought in fiction writing. It is argued that problem solving in fiction writing is sometimes concerned with creating problems or mysteries for the reader, and it is shown how this process applies to events, scenes, signifiers and syntax. All these findings are presented in the form of a cognitive model of fiction writing. The question of testing is discussed, and the use of the model in designing software tools is illustrated by the description of a hypertextual aid for fiction writers