Flylib.com

Books Software

 
 
 

1.4 How Can You Best Use This Book?


1.4 How Can You Best Use This Book?

The following sample scenarios will give you an idea of how you can best use this book in your own situation.

Scenario and Question

Answer

Database Modeler
Database modeling is my job. How can this book help me to do my daily work faster?

Import your existing database schema into a Database Model Diagram (see Chapter 14), then use your own models in parallel with trying each of the examples shown in this book.

Business Analyst
I have to use data models as part of my requirements specifications. How can this book help me to be more efficient?

Reverse engineer an existing database schema into an ORM Source Model (see Chapter 8). Use the ORM Source Model to generate suitable semantic reports (see Chapter 9).

Student
I know that database modeling is important. How can this book help me to learn more so that I can get a job as a database engineer?

Follow the book from cover to cover.
Build some conceptual models in ORM and ERM, and use the New Report Wizard to prepare in-depth reports. Forward engineer your models to your preferred database product.
Make changes to the physical database schema and reverse engineer it back into ER and ORM models and run the same reports as you did on the original models.
Compare the before and after reports to see the effects of your changes.

Database Administrator
I'm snowed under with management requests for explanations of our corporate database. How can this book help me?

Reverse engineer a database schema into an ORM Source Model (see Chapter 8).
Run the reports described in Chapter 9 and export them to an .rtf file.
Edit the .rtf file to fit your corporate standard and add appropriate ORM models or model fragments to support the reports (see Chapter 9).
Consider using the Visio Viewer (see Chapter 17) for electronic model distribution.
Ask the managers to confirm or deny the correctness of the ORM objects, facts, and constraints.

Application Development Manager
I have just been promoted from Chief Programmer and I need a better understanding of what my database engineers really do. They seem to take a long time to make simple user - requested changes and my programmers complain that database changes result in lots of unnecessary reprogramming and testing. Can I use this book to improve the effectiveness of my team?

Prepare ORM reports (see Chapter 9) and conduct a semantic review with domain experts (see Part 4). Use the reports described in Chapter 15 to review the potential impact of any changes on data elements (e.g., UML classes) in their application programs.
Look out for duplications in your database schema caused by failure to correctly normalize or by unnoticed homonyms or synonyms.
Review chapter 6 to see how to reuse model fragments to speed new development.
Migrate business rules from application program code into SQL code stored in the database (see Chapters 5, 11, 13).


Program Manager, USAF Sub-Contractor
I have just been appointed as program manager for new B3 bomber that is so stealthy that even I don't know where it is. The DoD insists that we use IDEF1X but I have never been able to fully understand the real meaning of all those lines, blobs, diamonds and boxes. How can I use this book to get a better understanding of what the IDEF1X data models really mean?

Reverse engineer your database schema into a Database Model Diagram (see Chapter 13)
Set the IDEF1X notation options (Chapter 10) and print the IDEF1X schema.
Run the reports described in Chapter 9 and compare them with the IDEF1X schema.

How you use this book depends on your desired result and on your level of knowledge. Here are some examples of how VEA can be used to support various job types. The examples are indicative rather than comprehensive.

Business analyst. Use the reports described in Chapter 9 to communicate with nontechnical domain experts. Use the reports from Chapter 15 for database engineers. If you want to start a new requirements analysis project, make sure you understand the contents of Part 1 and then apply the methods described in Part 2 to your own project.

If you want to understand the semantics of an existing database, reverse engineer the database schema into an ORM Source Model (see Chapter 5) and run the reports described in Chapter 9.

Entity Relationship modeling expert. If you are an expert in ER modeling and want to get straight into logical modeling, make sure you understand the contents of Part 1 and then apply the methods described in Part 3 to your own project.

If you want to study the logical and physical structure of an existing database, you can reverse engineer a physical database schema into a Database Model Diagram (see chapter 13). Then you can use the reports described in Chapters 9 and 15.

Application development manager. Review the re-use section and have one of your database engineers try a small project using Part 4 as a guide.

Database administrator. You can reverse engineer multiple databases into a single conceptual model and use it to ensure that all relational columns that are drawn from a single domain use a common data type and naming convention.

Systems architect. VEA allows re-use of all or part of an existing model for future applications. This helps to reduce development costs. You can use a single conceptual model to manage domain level metadata across several applications. Business rules can be maintained in a single conceptual model and re-used in many applications. You can easily add new ORM objects to extend the scope of the conceptual model and quickly generate a new logical model in fifth normal form. VEA helps by eliminating the tedium of repetitive manual normalization.

Student. If you are new to database analysis and design, you should follow the natural sequence of the book. If you want to learn more about ORM and database design, look at papers on the ORM website http://www.orm.net and read the book, Information Modeling and Relational Databases (Halpin, 2001).