Issue Tracking with Redmine

The xtUML team uses Redmine for issue tracking.  At the open-sourcing of BridgePoint, we evaluated Redmine as the best of the free and open issue trackers.  One Fact customers use it to report service requests.  The overall community uses it to report BridgePoint bugs and then to assign, participate and track progress.  Redmine has nice
-> Continue reading Issue Tracking with Redmine

Action Language Fundamentals

An action language needs to do only five (5) things. Now it happens that these five things cover everything you might ever want to do. The five fundamental actions are categorized: – accessor: create, delete, relate, unrelate, read, write – transform: +, -, *, /, other data manipulation – generator: state machine synchronization – bridge:
-> Continue reading Action Language Fundamentals

Action Language

An action language is just a programming language. However, it is characterized as being a bit more abstract than most target programming languages. It separates the concerns of functionality from design decisions regarding containers, memory, tasking and the like. It is model aware; it knows about classes, associations and state machines. It is “chunkier” in
-> Continue reading Action Language

xtUML Interfaces

xtUML interfaces can be uni-directional or bi-directional. From this graphic you can see small arrows in the port boxes indicating whether the port contains messages that are inbound, outbound or both. The LocationProvider and LocationUtil interfaces are uni-directional and on the Tracking component the messages are all outbound. The UI and HeartRateProvider interfaces contain messages
-> Continue reading xtUML Interfaces