Prototyping in Industrial Software Projects-Bridging the Gap Between Theory and Practice
IEEE Transactions on Software Engineering
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
The unified software development process
The unified software development process
Design by contract, by example
Design by contract, by example
Writing Effective Use Cases
Software Prototyping: Adoption, Practice and Management
Software Prototyping: Adoption, Practice and Management
Formal and Use-Case Driven Requirement Analysis in UML
COMPSAC '01 Proceedings of the 25th International Computer Software and Applications Conference on Invigorating Software Development
Using Transition Systems to Unify UML Models
ICFEM '02 Proceedings of the 4th International Conference on Formal Engineering Methods: Formal Methods and Software Engineering
Come, Let's Play: Scenario-Based Programming Using LSC's and the Play-Engine
Come, Let's Play: Scenario-Based Programming Using LSC's and the Play-Engine
Software Engineering (7th Edition)
Software Engineering (7th Edition)
Assertions, Scenarios and Prototypes: An Integrated Approach to High Quality Software
Assertions, Scenarios and Prototypes: An Integrated Approach to High Quality Software
Generating a prototype from a UML model of system requirements
ICDCIT'04 Proceedings of the First international conference on Distributed Computing and Internet Technology
Refinement and verification in component-based model-driven design
Science of Computer Programming
A systematic review of the use of requirements engineering techniques in model-driven development
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
| Hi-index | 0.00 |
In this paper, we present a tool for automatic prototype generation and analysis (AutoPA2.0) that implements the transformations from UML system requirements models to executable prototypes with the function of checking multiplicity invariants. A UML system requirements model consists of a use-case model and a conceptual class model. Generally, a use case is either described as a system operation which can be defined as a pair of pre and post conditions in the context of the conceptual class model, or described as a sequence of such system operations. AutoPA2.0 can transform the descriptions of use cases into an executable prototype in Java. The execution of each use case is a sequence of basic atomic actions which first check the pre-condition and then enforce the post-condition of the corresponding use case. It helps to improve the understanding between customers and designers. A simple library system is used to explain the method, and illustrate the feasibility of tool as well as its development.