Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tfischer

Pages: [1]
1
General Board / tangible archtiect integrates C#, Database and UML
« on: December 23, 2003, 10:23:33 am »
tangible® architect™ offers model-based code generation for VS.NET and EA UML.

Check it out at http://www.tangible.de

tangible® architect™ generates the object-oriented database access layer of the application and its database schema from within Visual Studio.NET. The object model's specification can be defined in code by means of attributed C# interfaces, use of wizards or by means of an UML-Model. The object model and database schema can be easily modified using the integrated object model browser. Code changes can be synchronized to the UML-Model using round-trip engineering.

The generated object model realizes a connection-oriented architecture with a pessimistic locking strategy. It is optimized for data-bound controls. The object-oriented database browser adds additional value to the product.

tangible® architect™ eases the development of .NET database applications as it:

  • Generates your database access layer in form of a strong-typed object model
  • Generates your database schema
  • Implements intelligent caching and pre-fetching
  • Adds data-binding support to your business objects
  • Uses your EA UML Model as input and provides UML roundtrip-engineering

Is completely integrated in Visual Studio .NET
tangible® architect™ supports UML Modelling by integration with the powerful, low-priced Sparx Systems Enterprise Architect UML Tool. Enterprise Architect also includes a XMI im- and export feature, so you can import a model from your favourite UML Tool.

Check out the code project article at www.codeproject.com
http://www.codeproject.com/showcase/tangible.asp

2
General Board / Custom Modelelements vs. Profiles vs. Docking Wind
« on: August 01, 2002, 02:52:11 pm »
Hi there,

I notices some inconsistency in the systemmodel of EA for a while: There are serveral ways to create Defects:

a) By Adding Custom Model Element of type Defect to a Diagram
b) Via the Project Menu Item Issues
c) By Creating a own UML Profile for Software Engineeing that contains UML Model Elements such as Defects

Unfortunately do these three ways not integrate into oneanother. This means is you create a Defect as Model Element using a) or c) it is not listed in the Issues Window b).
The same is true the other way around.

Please Geffory let us know which way EA will develop in furture. Will you implement a UML Profile for Software Engineering like referenced in the OMG's Software Process Engineering Meta Model (SPEM) or will you stick to the windows. Even the Documentation says different things at some time. When it comes to relationships matrixes there it is said that you could model your staff as Model Elements and assign it to features and have a look at the assignments in the matrix.

All this is true, but I think we would all benefit from a consistent usage model when it comes to Custom Model Elements, even Sparxsytems would benefit.

Hope to hear from you, soon.

Best Regards

Tim.

3
You might want to have a look at tangible architect for Sparxs EA. It generates a complete Object Model with persistence from your logical model. Persistent Objects have Data-binding as well. So it should be easy to build your app from there.

See

http://www.tangible.de/architect

for details

4
tangible® architect™ offers model-based code generation for VS.NET and EA UML.

Check it out at http://www.tangible.de

tangible® architect™ generates the object-oriented database access layer of the application and its database schema from within Visual Studio.NET. The object model's specification can be defined in code by means of attributed C# interfaces, use of wizards or by means of an UML-Model. The object model and database schema can be easily modified using the integrated object model browser. Code changes can be synchronized to the UML-Model using round-trip engineering.

The generated object model realizes a connection-oriented architecture with a pessimistic locking strategy. It is optimized for data-bound controls. The object-oriented database browser adds additional value to the product.

tangible® architect™ eases the development of .NET database applications as it:

  • Generates your database access layer in form of a strong-typed object model
  • Generates your database schema
  • Implements intelligent caching and pre-fetching
  • Adds data-binding support to your business objects
  • Uses your EA UML Model as input and provides UML roundtrip-engineering

Is completely integrated in Visual Studio .NET
tangible® architect™ supports UML Modelling by integration with the powerful, low-priced Sparx Systems Enterprise Architect UML Tool. Enterprise Architect also includes a XMI im- and export feature, so you can import a model from your favourite UML Tool.

Check out the code project article at www.codeproject.com
http://www.codeproject.com/showcase/tangible.asp

5
Hello,

The meta data services sdk takes oim xml as input for ea models. We used it directly from ea in an unreleased previous version of tangible architect to generate infromation models from UML.

Please visit your web site to investigate the released version of tangible architect the model driven data access layer generator for VS.NET/EA UML.

http://www.tangible.de/architect

Or drop me a line at tfischer@tangible.de.

Thanks

Tim.

Pages: [1]