Notes pertaining to the maintenance and publication of this JRAGAN.com web site.

Copyrights are still in effect.

( As much as possible, the "CoreDate" protocol is used on this web site because it was designed for systems and people with little bagage from the past.)

CoreModel Copyright 1996 - 2013 John E. Ragan.
All rights reserved.

__________________________________________________
__________________________________________________

CoreModel
Brief

CoreModel designs databases, manages a company's models, and can provide a central data dictionary.
( For relational databases. )

_____________________

* Modeling *

CoreModel manifests the various model abstraction levels as user interfaces in which the modeler works. The modeling endeavor is presented in a way that is designed to assist the modeler's thought processes and to insure that no facet of the task is forgotten.

The modeler is not forced to do anything,
but he is reminded to do everything.

_____________________

* Objective *

A ready-to-run database that was instantiated under a database manager by pressing a button.

_____________________

* Modeler's Tools *

CoreModel includes these tools for the modeler.

_____________________

* Deliverables *

CoreModel allows flexible determination of a project's deliverable. The modeler can choose any or all of the deliverables. Creation of a deliverable is not a finalization and can be redelivered as needed.

Selectable deliverables are :
        Model instantiation. (Database creation.)
        Printed schemata.
        Model information export.
        Model publication.

_____________________

* Database Abstraction Levels *

Each abstraction level has a GUI, and a model displays in an abstraction level for work at that level. When completed at that level, the modeler tells the system to advance it to the next level. But a manual over-ride can be used to display it in any level.

Manifested Abstraction Levels

Conceptual.

Logical.

Physical.

Implementation.

For example, when a model moves from the conceptual to the logical, attributes become columns, entities become tables, and data types are introduced.

( A model can start at a Genesis level for special project needs. )

_____________________

* System Administration *

The administrator's module controls system and model security, offers lookup tables to support the modelers, controls the metadata servers, and configures the system.

Available Lookup And Control Tables

_____________________	__
data domains	*
data types	*
database types	*
database connections	*
brand name attributes
help	*
model access
model levels	*
model states	*
model types
model initializer
object types
personnel
process types	*
relation types	*
source types	*
name standards	*
system log
system configuration

* Available in the modelers' modules for lookup.

_____________________

* Documentation *

Yes.

User documentation in a web page.

Also, the system contains the documentation and an administrator-maintained help system.

_____________________

* Metadata Server *

Has a detailed data dictionary that is kept current 24-7.

Two internal metadata servers translate models into metadata and publish it. One writes HTML for people and the other writes schema-based XML for systems.

The servers also publish warnings to flag metadata changes.

_____________________

* Company Standards *

Modelers can run reports at any time that identify properties that deviate from company standards.

_____________________

* Existing Databases *

Includes a tool that extracts metadata from a live database and builds a model of that database for evaluation and publication.

_____________________

* Internal Database *

AxleBase.

He was run with Paradox, MS Access, MsSQL, MySQL, and Oracle until AxleBase was finally available.

_____________________

* Error Handling *

This system was built prior to the development of the AxleBase error handling technology. A retrofit was attempted with limited success.

__________________________________________________
__________________________________________________

CoreModel
Administrative Section

* Licensing *

Not for sale or license. It is not polished well enough to put into production.

* Project Purpose *

Exploration of the actualization of concept and theory in computer tools with GUI's that require practical actualization.

* Personal Notes *

Concept development, and all design and coding are entirely mine.

* Project Status *

Project is complete.

History :
      Began in the nineties.
      Last update was in February 2006.
      CoreModel.com web site was taken down in June of 2011.

Project statistics :

73,778	code lines.
2,731,701	code bytes.
17,475	comment lines.
38	classes.
2,999	functions.
77	user GUI forms.

( Reported by Seepper. )

__________________________________________________

Technology and web site
Copyright 1999 - 2022 John Ragan

Web site is maintained with Notepad.
By intent, so don't bother me about it.