10,396 research outputs found
Preliminary findings from a survey on the MD state of the practice
In the context of an Italian research project, this paper reports on an on-line survey, performed with 155 software professionals, with the aim of investigating about their opinions and experiences in modeling during software development and Model-driven engineering usage. The survey focused also on used modeling languages, processes and tools. A preliminary analysis of the results confirmed that Model-driven engineering, and more in general software modeling, are very relevant phenomena. Approximately 68% of the sample use models during software development. Among then, 44% generate code starting from models and 16% execute them directly. The preferred language for modeling is UML but DSLs are used as wel
Relevance, benefits, and problems of software modelling and model driven techniques—A survey in the Italian industry
Context Claimed benefits of software modelling and model driven techniques are improvements in productivity, portability, maintainability and interoperability. However, little effort has been devoted at collecting evidence to evaluate their actual relevance, benefits and usage complications. Goal The main goals of this paper are: (1) assess the diffusion and relevance of software modelling and MD techniques in the Italian industry, (2) understand the expected and achieved benefits, and (3) identify which problems limit/prevent their diffusion. Method We conducted an exploratory personal opinion survey with a sample of 155 Italian software professionals by means of a Web-based questionnaire on-line from February to April 2011. Results Software modelling and MD techniques are very relevant in the Italian industry. The adoption of simple modelling brings common benefits (better design support, documentation improvement, better maintenance, and higher software quality), while MD techniques make it easier to achieve: improved standardization, higher productivity, and platform independence. We identified problems, some hindering adoption (too much effort required and limited usefulness) others preventing it (lack of competencies and supporting tools). Conclusions The relevance represents an important objective motivation for researchers in this area. The relationship between techniques and attainable benefits represents an instrument for practitioners planning the adoption of such techniques. In addition the findings may provide hints for companies and universitie
Using an Architecture Description Language to Model a Large- Scale Information System – An Industrial Experience Report
An organisation that had developed a large Information System wanted to embark on a programme of significant evolution for the system. As a precursor to this, it was decided to create a comprehensive architectural
description. T his undertaking faced a number of challenges, including a low general awareness of software modelling and software architecture practices . The approach taken for this
project included the definition of a simple, specific, architecture description language. This paper describes the experiences of the project and the ADL created as part of it
Practical Application Of Uml Activity Diagrams For The Generation Of Test Cases
Software testing and debugging represents around one third of total effort in development projects. Different factors which have influence on poor practices of testing have been identified through specific surveys. Amongst several, one of the most important is the lack of efficient methods to
exploit development models for generating test cases. This paper presents a new method for automatically generating a complete set of functional test cases from UML activity diagrams complementing specification of use cases. Test cases are prioritized according to software risk
information. Results from experiences with more than 70 software professionals/experts validate benefits of the method. Participants also confirm its interest and effectiveness for testing needs of industry
Drawing OWL 2 ontologies with Eddy the editor
In this paper we introduce Eddy, a new open-source tool for the graphical editing of OWL~2 ontologies. Eddy is specifically designed for creating ontologies in Graphol, a completely visual ontology language that is equivalent to OWL~2. Thus, in Eddy ontologies are easily drawn as diagrams, rather than written as sets of formulas, as commonly happens in popular ontology design and engineering environments.
This makes Eddy particularly suited for usage by people who are more familiar with diagramatic languages for conceptual modeling rather than with typical ontology formalisms, as is often required in non-academic and industrial contexts. Eddy provides intuitive functionalities for specifying Graphol diagrams, guarantees their syntactic correctness, and allows for exporting them in standard OWL 2 syntax. A user evaluation study we conducted shows that Eddy is perceived as an easy and intuitive tool for ontology specification
A framework for effective management of condition based maintenance programs in the context of industrial development of E-Maintenance strategies
CBM (Condition Based Maintenance) solutions are increasingly present in industrial systems due to two
main circumstances: rapid evolution, without precedents, in the capture and analysis of data and
significant cost reduction of supporting technologies. CBM programs in industrial systems can become
extremely complex, especially when considering the effective introduction of new capabilities provided
by PHM (Prognostics and Health Management) and E-maintenance disciplines. In this scenario, any CBM
solution involves the management of numerous technical aspects, that the maintenance manager needs
to understand, in order to be implemented properly and effectively, according to the company’s strategy.
This paper provides a comprehensive representation of the key components of a generic CBM solution,
this is presented using a framework or supporting structure for an effective management of the CBM
programs. The concept “symptom of failure”, its corresponding analysis techniques (introduced by ISO
13379-1 and linked with RCM/FMEA analysis), and other international standard for CBM open-software
application development (for instance, ISO 13374 and OSA-CBM), are used in the paper for the
development of the framework. An original template has been developed, adopting the formal structure
of RCM analysis templates, to integrate the information of the PHM techniques used to capture the failure
mode behaviour and to manage maintenance. Finally, a case study describes the framework using the
referred template.Gobierno de Andalucía P11-TEP-7303 M
- …