Shulou(Shulou.com)06/02 Report--

How to analyze Microsoft®, Visio® and Enterprise modules, I believe that many inexperienced people do not know what to do. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

ORM schemas can obtain logical database schemas by implementing forward engineering, from which physical database schemas can be generated for multiple database management systems (DBMS). The logical database schema or ORM schema can be obtained by reverse engineering the structure of the physical database.

The released Microsoft ®Visio ®Enterprise product contains only the Standard version and the Professional version, and the Professional version contains the previous separate Technical version, but does not include the Enterprise version. Although Visio 2002 Professional contains ORM stencils, it is used only for drawing because its ORM diagrams cannot be mapped to a logical database schema and cannot be obtained from a physical database by reverse engineering. Visio 2002 Professional includes a database modeling solution to define or reverse engineer a new logical database schema from an existing database, but cannot implement forward engineering to obtain a physical database schema.

Microsoft once supported database design and program code design (using UML) within its Visual Studio product range. After the acquisition of Visio Corporation, Microsoft has two separate products (Visio Enterprise and Visual Studio) that support database design and UML, resulting in significant duplication of functionality. To unify these product features, the original deep modeling solution within Visio Enterprise has been enhanced and transferred to Microsoft's new product, Visio for Enterprise Architects (VEA), which is included in the Microsoft ®Visual Studio ®.NET Enterprise Architect.

These Microsoft ®Visio ®Enterprise-based modeling solutions are included in Beta 2 of the Visual Studio .NET Enterprise, and will be included in a subsequent final release. The deep ORM solution in VEA is completely different from the simple ORM drawing mold in Visio Professional, and the two are not interchangeable. However, database modeling solutions in VEA can be imported from Visio Professional and then forward engineered to obtain DDL scripts or physical database schemas.

After Microsoft ®Visio ®Enterprise provides a reference scheme for entity types, you do not need to repeat the reference scheme later when you specify the fact type. Unlike entity types, value types (for example, EmployeeName [employee name], RoomNr [room number]) do not have a reference scheme, and because their instances are only literal constants (for example, strings or numbers used to name or reference entities), they can identify themselves. In Freeform mode, the value type is identified by appending empty parentheses [()]. Examples of some types of facts that use formal, free-drawing syntax are provided below:

Employee (empNr) works for / employs Department (code)

Employee has EmployeeName ()

Employee has MobileNr ()

Employee drives / is driven by Car (regNr)

After reading the above, have you mastered how to analyze Microsoft®, Visio® and Enterprise modules? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.