• Corpus ID: 11518914

Generating a Domain Model from a Use Case Model

@inproceedings{Samarasinghe2005GeneratingAD,
  title={Generating a Domain Model from a Use Case Model},
  author={Nayanamana Samarasinghe and St{\'e}phane S. Som{\'e}},
  booktitle={IASSE},
  year={2005}
}
In this paper, we focus on the transition from requirements to subsequent phases of software development. We elaborate on creation of a Domain model from an existing Use Case model. A domain model can be seen as an interface or a pipe between the Requirement Engineering phase and the Design Phase of the software development life cycle. Our goal is to automate the extraction of domain information from requirements up to a feasible extent. The approach is integrated to UCEd, a tool for use cases… 

Figures from this paper

Deriving software design models from a set of business processes
TLDR
This paper proposes an approach to adapt and extend the 4SRS method in order to generate a data model supporting the generated logical architecture and the elicited requirements based in a set of business process models.
A Meta-Model for Textual Use Case Description
  • S. Somé
  • Computer Science
    J. Object Technol.
  • 2009
TLDR
This paper proposes an abstract syntax for textual use case description as a meta-model extension of the UML Specification, based on elements commonly found in use case templates and includes OCL constraints for ensuring consistency with the U ML specification.
Deriving Integrated Software Design Models from BPMN Business Process Models
TLDR
A model-driven approach is proposed to support the construction of a use case model, an integrated domain model, and a user interface model, from a set of business process models, comprising all existing information in those models.
A semantic web enabled approach to reuse functional requirements models in web engineering
TLDR
A semantic web enabled approach is proposed for reusing models, specifically functional requirements models, which takes the brief description of the functional requirements of a new web application in terms of UML use case diagram, and semi-automatically generates the draft of the corresponding detailed description in Terms of a set of U ML activity diagrams.
Automatic generation of sequence diagram from use case specification
TLDR
The results show that the proposed automated approach generates sequence diagrams which are significantly better in terms of correctness and completeness than those generated by the existing automated approaches.
Automatic generation of analysis class diagrams from use case specifications
TLDR
This paper proposes a tool supported approach for automated transformation of use case specifications documented in English language into analysis class diagrams that are more correct, more complete, and less redundant than those generated by the existing automated approaches.
A systematic review of transformation approaches between user requirements and analysis models
TLDR
This systematic review led to the analysis of 20 primary studies obtained after a carefully designed procedure for selecting papers published in journals and conferences from 1996 to 2008 and Software Engineering textbooks to examine existing literature works that transform textual requirements into analysis models.
Formalization of Textual Use Cases Based on Petri Nets
  • S. Somé
  • Computer Science
    Int. J. Softw. Eng. Knowl. Eng.
  • 2010
TLDR
A mapping from textual use cases to a formal model (Petri nets) is proposed, which considers use cases sequencing constraints defined at the syntactic-level, and provides a definition of execution semantics to use cases.
Petri Nets Based Formalization of Textual Use Cases
TLDR
The proposed formalization serves as a basis for state-model synthesis from use cases, and is proposed as a set of Mapping Rules from well-formed use cases to Basic Petri nets.
...
...

References

SHOWING 1-10 OF 20 REFERENCES
Extracting formal domain models from exsisting code for generative reuse
TLDR
An approach, where by reengineering a formal domain model out of an existing system, one can generalize the existing system to an application generator, is illustrated.
Applying use cases for the requirements validation of component-based real-time software
  • W. Fleisch
  • Computer Science
    Proceedings 2nd IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC'99) (Cat. No.99-61702)
  • 1999
TLDR
A template for structuring use cases helps gathering the course oriented requirements which describe the required behaviour of the composed software and a process for the simulation based validation of component based software applying use cases is presented.
Application of linguistic techniques for Use Case analysis
TLDR
This work applies a number of tools for quality evaluation of NL text (and, in particular, of NL requirements documents) to an industrial Use Cases document, and results are a set of metrics that aim to measure the quality of the NL textual description of Use Cases.
Designing object-oriented software
Offers basic design principles, and a specific design process, that can be applied to any software programming effort, even those not using object-oriented programming languages or environments.
The Rational Unified Process: An Introduction, Second Edition
From the Publisher: This concise book offers a quick introduction to the concepts, structure, content, and motivation of the Rational Unified Process—a Web-enabled software engineering process that
Analysis patterns - reusable object models
  • M. Fowler
  • Computer Science
    Addison-Wesley series in object-oriented software engineering
  • 1997
TLDR
The World of Patterns, a Treatise on Conceptual Models and Business Process Reengineering, and Design Templates for Other Techniques is presented, with a focus on patterns for type model design Templates.
The object constraint language: precise modeling with UML
TLDR
This book discusses modeling with Constraints in a UML Model, using Package Names in Navigations, using Pathnames in Inheritance Relations, and treating Instances as Collections.
A laboratory for teaching object oriented thinking
TLDR
CRC cards are introduced, which characterize objects by class name, responsibilities, and collaborators, as a way of giving learners a direct experience of objects, and are found successful in teaching novice programmers the concepts of objects.
Writing effective use cases
TLDR
The authors indulge in a long-winded literature survey of planning systems and provide proofs of necessity, consistency, and optimality of their framework, that practitioners will no doubt find tiresome as the book is given the flavour of a PhD thesis.
The CRC card book
TLDR
This paper presents a meta-analysis of the design and implementation of the Object-Oriented Development process in the context of the Largetalk Programming Environment, using the example of the Saver, Soone, & Eayrne Cyber-Trading System.
...
...