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
|
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
|
Reverse engineer an existing database schema into an ORM Source
Model (see Chapter 8). Use the ORM Source Model to generate
suitable semantic
|
|
Student
|
Follow the book from cover to cover.
|
|
Database Administrator
|
Reverse engineer a database schema into an ORM Source Model (see
Chapter 8).
|
|
Application Development Manager
|
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.
|
|
|
Reverse engineer your database schema into a Database Model
Diagram (see Chapter 13)
|
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
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
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
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).