Ensure your team is in sync and avoids SQL related errors
How often did you have a bad day because you did not get notified by your team that a database field was relocated into another table or just renamed? How close did the latest UML Diagram match the real world implementation – and how long did it take you to find out what was really going on?
tangible® architect™ addresses these problems of team-communication by providing each team member with an appropriate representation of the design and several methods to change and communicate the design to other members: With tangible® architect™ a field can be changed or added directly in the C# interface specification, UML Diagram or using the tangible® architect™ class view wizards. In any case tangible® architect™ will assure that the generated database access code and schema reflect that change and that UML Diagrams will be updated. In addition, the User Interface Developers will easily detect that change in the tangible® architect™ class view. If someone tries to access a field that no longer exists, the C# compiler will warn the user – no matter if the Query API or a navigational approach to data access is being used.
tangible architect assures the team follows industry best practicesThe generated object model enables your team to cleanly separate data-access code and user interface code from business logic. Code Generation brings you consistency in regards to naming and implementation. In addition, UML Diagrams will always be up-to-date, as the UML model is used to generate the integral part of your system.
All this makes finding logical bugs easier, especially as the overall hand-written code size is reduced by up to 70%. You can focus on unit testing the remaining 30% hand-written code and performing integration tests.
With tangible architect analysing database applications becomes a snapThe object-oriented database browser of Microsoft® Meta Data Services™ is available to you for all persistent object models. This makes it easy to review and edit the data in the database. As the database is self-describing you you don't even need the object model's accompanying DLL to use the browser.
