• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 29
  • 8
  • 4
  • 4
  • 2
  • 2
  • 1
  • 1
  • 1
  • Tagged with
  • 53
  • 29
  • 15
  • 13
  • 12
  • 10
  • 9
  • 9
  • 9
  • 9
  • 8
  • 8
  • 8
  • 7
  • 7
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

OCL exception handling

Gurunath, Pramod 15 November 2004 (has links)
Object Constraint Language (OCL) is part of the Unified Modeling Language (UML) specification and can be used to enforce constraints on the attributes or methods of a class. It would greatly help the software developers if such non-executable OCL constraints specified in a UML model could be enforced on the executable code generated from the model. This thesis discusses the concepts, ideas and the approach in transforming a model developed in the Rational Rose software with OCL constraints into Java code shells, complete with fragments of code to detect the run-time violations of the constraints. The implementation and testing of a prototype tool that incorporates these ideas is also discussed.
2

OCL exception handling

Gurunath, Pramod 15 November 2004 (has links)
Object Constraint Language (OCL) is part of the Unified Modeling Language (UML) specification and can be used to enforce constraints on the attributes or methods of a class. It would greatly help the software developers if such non-executable OCL constraints specified in a UML model could be enforced on the executable code generated from the model. This thesis discusses the concepts, ideas and the approach in transforming a model developed in the Rational Rose software with OCL constraints into Java code shells, complete with fragments of code to detect the run-time violations of the constraints. The implementation and testing of a prototype tool that incorporates these ideas is also discussed.
3

Transformace z OCL do SQL / Transformace z OCL do SQL

Sobotka, Petr January 2012 (has links)
The aim of this Master Thesis named Transformation from OCL into SQL is to explore possibilities of enhancing Enterprise Architect by the ability of generating SQL code that implements OCL constraints of a Platform Independent Model, and to create a working prototype that demonstrates this capability. The thesis contains a brief introduction to the problem of Model Driven Architecture, why it would be useful to implement the specified constraints directly in the database, a description of the interaction with Enterprise Architect along with analysing how to get the needed data, the way OCL can be mapped onto SQL, and finally it describes the implementation of the OCLtoSQL plugin from its analysis and chosen architecture to its documentation.
4

Automatinis testų generavimas, paremtas OCL apribojimais / Automated test generation using OCL constraints

Mitė, Mantas 01 September 2011 (has links)
Testavimo procesą galima gerinti jį optimizuojant. Vienas iš galimų gerinimo būdų yra vienetų testai. Vienetų testai padeda sumažinti klaidų kiekį nuo 20 % iki 90 %, tačiau tuo pačiu programų kūrimo išlaidos gali padidėti apie 30 %. Vienas iš galimų būdų išlaikyti pasiektą vienetų testų efektyvumą ir palaikyti mažą kainą yra automatinis jų generavimas. Vienetų testų generatorius, generuoja vienetų testus remdamasis OCL apribojimais. Generatorius JAVA programiniame kode įterptus apribojimus generuoja į Junit vienetų testus. / The development of modern software is a difficult process, there is a high possibility to leave uncorrected mistakes in the software, it would be more precisely to say that it is impossible to make software without bugs. Software testing is maybe the biggest part of development process. The unit testing is very powerful testing. It prevents from defects 20% and more [1]. The quality increase came at a cost of approximately 30% more development time. The main goal is create generator for unit testing. Automated test generator can reduce development time. Unit test generation is based on the OCL (Object Constraint Language) and software static model. OCL eliminate a test oracle problem. Software static model can be UML a class diagrams, but it very complicated approach. We use a reflection technology, because it is more precise and better today. Also OCL constrains are inserted in code.
5

Representing Dynamic Invariants in Ontologically Well-Founded Conceptual Models

GUERSON, J. O. 28 May 2015 (has links)
Made available in DSpace on 2016-08-29T15:33:21Z (GMT). No. of bitstreams: 1 tese_8885_JohnMScThesis[final]20150703-110844.pdf: 2078817 bytes, checksum: b7867cf01fac04ad68223c7eeca3fe68 (MD5) Previous issue date: 2015-05-28 / Conceptual models often capture the invariant aspects of the phenomena we perceive. These invariants may be considered static when they refer to structures we perceive in phenomena at a particular point in time or dynamic/temporal when they refer to regularities across different points in time. While static invariants have received significant attention, dynamics enjoy marginal support in widely-employed techniques such as UML and OCL. This thesis aims at addressing this gap by proposing a technique for the representation of dynamic invariants of subject domains in UML-based conceptual models. For that purpose, a temporal extension of OCL is proposed. It enriches the ontologically well-founded OntoUML profile and enables the expression of a variety of (arbitrary) temporal constraints. The extension is fully implemented in the tool for specification, verification and simulation of enriched OntoUML models.
6

Informacinei sistemai keliamų reikalavimų apibrėžimo metodika naudojant UML ir OCL / Method for Specification of Requirements for Development of Information Systems Using UML and OCL

Zaksaitė, Eglė 28 May 2004 (has links)
In this work some progressive object–oriented requirement definition methods were analyzed (ICONIX, Reggio, Scores). Rules and principles of these methods were generalized and comprehensive content of requirements model was presented. Requirements definition must define state and behavior of target information system independently of future design. Requirements model was proposed where use cases are presented as interfaces together with associated classes of problem domain, operations are specified with signatures, pre and post conditions wich must be written in formal language OCL. Model was described using UML class, sequence diagrams, state charts and OCL constraints and is illustrated with examples from case study.
7

Veiklos taisyklių modeliavimo UML kalbos pagrindu tyrimas / The Research of Business Rules Modeling on the Basis of the Language UML

Blažytė, Inga 15 January 2005 (has links)
The main aim of the system’s analysis is to find the most important information about real world (problematic sphere); and, firstly, that will be data about processes, their structure and data shift. Business rules combines all these three things that were mentioned above, that is why they can be regarded as the central part in the system’s analysis, and the system’s analysis can be applied to business rules. Business rule is a proposition that defines and limits some aspects of the business. Certain business structure is defined by the business rule; additionally, certain business is controlled or influenced by the business rule too. Moreover, business rules do not depend on projecting model or technical platform. Objective application informational system creation methodology was chosen for the analysis; and it was based on objective modelling of the real world objects and the use of that model for the projecting that does not depend on certain programming language. UML language was chosen for business rules modelling because this language is universal of conception modelling and it is an objective programming language. Despite of all advantages of UML, it does not specify business rules as a separate model’s unit. In UML the rules are depicted as comment; in the beginning they are written by the help of natural speech then they are made into OCL (object constrain language). OCL is not a programming language that is why the logics and control of the program cannot be... [to full text]
8

UML CASE įrankio išplėtimas duomenų vientisumo reikalavimų kodo generavimui / UML CASE tool extension for generating code for implementation of integrity requirements

Blaževič, Valdemar 11 August 2008 (has links)
Šiame darbe sprendžiamos grafinio vientisumo reikalavimų vaizdavimo loginiuose duomenų modeliuose bei jų kodo realizavimo problemos. Sprendžiant šiuos uždavinius, buvo analizuojami vientisumo reikalavimų tipai, UML plėtimo mechanizmai bei esamos vientisumo reikalavimų įgyvendinimo CASE įrankiuose galimybės.Vientisumo reikalavimus UML modeliuose galima užrašyti OCL kalba, tačiau OCL yra per sudėtinga daugeliui projektuotojų. Be to, SQL kodo generavimas iš OCL kol kas nėra efektyvus. Šio magistrinio darbo tikslas yra padidinti UML CASE įrankių duomenų bazių projektavimo galimybes, sukuriant vientisumo reikalavimų vaizdavimo ir kodo generavimo priemones. / Fulfillment of data integrity constraint requirements is one of main problems in information system development process. The constraints are implemented at physical system development level. Despite the fact that most of current UML CASE tools allow to specify constraints using OCL language, for the most of system analytics and architects use of OCL is too complicated. Currently SQL code generated from OCL constraint implementation is not effective. In this study we will present alternative approach for constraint requirement implementation using UML2 extension possibilities – profiles and stereotypes with tag values. Also we will present SQL code generation template language and code template based constraint requirement transformation to SQL code algorithm. It was used to extend UML Case tool MagicDraw.
9

Validation of UML conceptual schemas with OCL constraints and operations

Queralt Calafat, Anna 02 March 2009 (has links)
Per tal de garantir la qualitat final d'un sistema d'informació, és imprescindible que l'esquema conceptual que representa el coneixement sobre el seu domini i les funcions que ha de realitzar sigui semànticament correcte.La correctesa d'un esquema conceptual es pot veure des de dues perspectives. Per una banda, des del punt de vista de la seva definició, determinar la correctesa d'un esquema conceptual consisteix en respondre la pregunta "És correcte l'esquema conceptual?". Aquesta pregunta es pot respondre determinant si l'esquema satisfà certes propietats, com satisfactibilitat, no redundància o executabilitat de les seves operacions.D'altra banda, des de la perspectiva dels requisits que el sistema d'informació ha de satisfer, l'esquema conceptual no només ha de ser correcte sinó que també ha de ser el correcte. Per tal d'assegurar-ho, el dissenyador necessita algun tipus de guia i ajut durant el procés de validació, de manera que pugui entendre què està representant l'esquema exactament i veure si es correspon amb els requisits que s'han de formalitzar.En aquesta tesi presentem una aproximació que millora els resultats de les propostes anteriors adreçades a validar un esquema conceptual en UML, amb les restriccions i operacions formalitzades en OCL. La nostra aproximació permet validar un esquema conceptual tant des del punt de vista de la seva definició com de la seva correspondència amb els requisits.La validació es porta a terme mitjançant un conjunt de proves que s'apliquen a l'esquema, algunes de les quals es generen automàticament mentre que d'altres són definides ad-hoc pel dissenyador. Totes les proves estan formalitzades de tal manera que es poden tractar d'una manera uniforme,independentment de la propietat específica que determinen.La nostra proposta es pot aplicar tant a un esquema conceptual complet com només a la seva part estructural. Quan es pretén validar només la part estructural d'un esquema, oferim un conjunt de condicions que permeten determinar si qualsevol prova de validació que es pugui fer sobrel'esquema acabarà en temps finit. Per aquells casos en els quals aquestes condicions de terminació se satisfan, també proposem un procediment de raonament sobre l'esquema que s'aprofita d'aquest fet i és més eficient que en el cas general. Aquesta aproximació permet validar esquemes conceptuals molt expressius, assegurant completesa i decidibilitat al mateix temps.Per provar la factibilitat de la nostra aproximació, hem implementat el procés de validació complet per a la part estructural d'un esquema. A més, per a la validació d'un esquema conceptual que inclou la definició del comportament, hem implementat el procediment de raonament estenent un mètode existent. / To ensure the quality of an information system, it is essential that the conceptual schema that represents the knowledge about its domain and the functions it has to perform is semantically correct.The correctness of a conceptual schema can be seen from two different perspectives. On the one hand, from the point of view of its definition, determining the correctness of a conceptual schema consists in answering to the question "Is the conceptual schema right?". This can be achieved by determining whether the schema fulfills certain properties, such as satisfiability, non-redundancy or operation executability.On the other hand, from the perspective of the requirements that the information system should satisfy, not only the conceptual schema must be right, but it also must be the right one. To ensure this, the designer must be provided with some kind of help and guidance during the validation process, so that he is able to understand the exact meaning of the schema and see whether it corresponds to the requirements to be formalized.In this thesis we provide an approach which improves the results of previous proposals that address the validation of a UML conceptual schema, with its constraints and operations formalized in OCL. Our approach allows to validate the conceptual schema both from the point of view of its definition and of its correspondence to the requirements.The validation is performed by means of a set of tests that are applied to the schema, including automatically generated tests and ad-hoc tests defined by the designer. All the validation tests are formalized in such a way that they can be treated uniformly, regardless the specific property they allow to test.Our approach can be either applied to a complete conceptual schema or only to its structural part. In case that only the structural part is validated, we provide a set of conditions to determine whether any validation test performed on the schema will terminate. For those cases in which these conditions of termination are satisfied, we also provide a reasoning procedure that takes advantage of this situation and works more efficiently than in the general case. This approach allows the validation of very expressive schemas and ensures completeness and decidability at the same time. To show the feasibility of our approach, we have implemented the complete validation process for the structural part of a conceptual schema.Additionally, for the validation of a conceptual schema with a behavioral part, the reasoning procedure has been implemented as an extension of an existing method.
10

Testing and test-driven development of conceptual schemas

Tort Pugibet, Albert 11 April 2012 (has links)
The traditional focus for Information Systems (IS) quality assurance relies on the evaluation of its implementation. However, the quality of an IS can be largely determined in the first stages of its development. Several studies reveal that more than half the errors that occur during systems development are requirements errors. A requirements error is defined as a mismatch between requirements specification and stakeholders¿ needs and expectations. Conceptual modeling is an essential activity in requirements engineering aimed at developing the conceptual schema of an IS. The conceptual schema is the general knowledge that an IS needs to know in order to perform its functions. A conceptual schema specification has semantic quality when it is valid and complete. Validity means that the schema is correct (the knowledge it defines is true for the domain) and relevant (the knowledge it defines is necessary for the system). Completeness means that the conceptual schema includes all relevant knowledge. The validation of a conceptual schema pursues the detection of requirements errors in order to improve its semantic quality. Conceptual schema validation is still a critical challenge in requirements engineering. In this work we contribute to this challenge, taking into account that, since conceptual schemas of IS can be specified in executable artifacts, they can be tested. In this context, the main contributions of this Thesis are (1) an approach to test conceptual schemas of information systems, and (2) a novel method for the incremental development of conceptual schemas supported by continuous test-driven validation. As far as we know, this is the first work that proposes and implements an environment for automated testing of UML/OCL conceptual schemas, and the first work that explores the use of test-driven approaches in conceptual modeling. The testing of conceptual schemas may be an important and practical means for their validation. It allows checking correctness and completeness according to stakeholders¿ needs and expectations. Moreover, in conjunction with the automatic check of basic test adequacy criteria, we can also analyze the relevance of the elements defined in the schema. The testing environment we propose requires a specialized language for writing tests of conceptual schemas. We defined the Conceptual Schema Testing Language (CSTL), which may be used to specify automated tests of executable schemas specified in UML/OCL. We also describe a prototype implementation of a test processor that makes feasible the approach in practice. The conceptual schema testing approach supports test-last validation of conceptual schemas, but it also makes sense to test incomplete conceptual schemas while they are developed. This fact lays the groundwork of Test-Driven Conceptual Modeling (TDCM), which is our second main contribution. TDCM is a novel conceptual modeling method based on the main principles of Test-Driven Development (TDD), an extreme programming method in which a software system is developed in short iterations driven by tests. We have applied the method in several case studies, in the context of Design Research, which is the general research framework we adopted. Finally, we also describe an integration approach of TDCM into a broad set of software development methodologies, including the Unified Process development methodology, MDD-based approaches, storytest-driven agile methods and goal and scenario-oriented requirements engineering methods. / Els enfocaments per assegurar la qualitat deis sistemes d'informació s'han basal tradicional m en! en l'avaluació de la seva implementació. No obstan! aix6, la qualitat d'un sis tema d'informació pot ser ampliament determinada en les primeres fases del seu desenvolupament. Diversos estudis indiquen que més de la meitat deis errors de software són errors de requisits . Un error de requisit es defineix com una desalineació entre l'especificació deis requisits i les necessitats i expectatives de les parts im plicades (stakeholders ). La modelització conceptual és una activitat essencial en l'enginyeria de requisits , l'objectiu de la qual és desenvolupar !'esquema conceptual d'un sistema d'informació. L'esquema conceptual és el coneixement general que un sistema d'informació requereix per tal de desenvolupar les seves funcions . Un esquema conceptual té qualitat semantica quan és va lid i complet. La valides a implica que !'esquema sigui correcte (el coneixement definit és cert peral domini) i rellevant (el coneixement definit és necessari peral sistema). La completes a significa que !'esquema conceptual inclou tot el coneixement rellevant. La validació de !'esquema conceptual té coma objectiu la detecció d'errors de requisits per tal de millorar la qualitat semantica. La validació d'esquemes conceptuals és un repte crític en l'enginyeria de requisits . Aquesta te si contribueix a aquest repte i es basa en el fet que els es quemes conceptuals de sistemes d'informació poden ser especificats en artefactes executables i, per tant, poden ser provats. Les principals contribucions de la te si són (1) un enfocament pera les pro ves d'esquemes conceptuals de sistemes d'informació, i (2) una metodología innovadora pel desenvolupament incremental d'esquemes conceptuals assistit per una validació continuada basada en proves . Les pro ves d'esquemes conceptuals poden ser una im portant i practica técnica pera la se va validació, jaque permeten provar la correctesa i la completesa d'acord ambles necessitats i expectatives de les parts interessades. En conjunció amb la comprovació d'un conjunt basic de criteris d'adequació de les proves, també podem analitzar la rellevancia deis elements definits a !'esquema. L'entorn de test proposat inclou un llenguatge especialitzat per escriure proves automatitzades d'esquemes conceptuals, anomenat Conceptual Schema Testing Language (CSTL). També hem descrit i implementa! a un prototip de processador de tes tos que fa possible l'aplicació de l'enfocament proposat a la practica. D'acord amb l'estat de l'art en validació d'esquemes conceptuals , aquest és el primer treball que proposa i implementa un entorn pel testing automatitzat d'esquemes conceptuals definits en UML!OCL. L'enfocament de proves d'esquemes conceptuals permet dura terme la validació d'esquemes existents , pero també té sentit provar es quemes conceptuals incomplets m entre estant sent desenvolupats. Aquest fet és la base de la metodología Test-Driven Conceptual Modeling (TDCM), que és la segona contribució principal. El TDCM és una metodología de modelització conceptual basada en principis basics del Test-Driven Development (TDD), un métode de programació en el qual un sistema software és desenvolupat en petites iteracions guiades per proves. També hem aplicat el métode en diversos casos d'estudi en el context de la metodología de recerca Design Science Research. Finalment, hem proposat enfocaments d'integració del TDCM en diverses metodologies de desenvolupament de software.

Page generated in 0.0722 seconds