The solution is engineered through the inclusion of a highly engineered data model within the Metabase System that enables the capture, interaction, and evolution of the key data required to then put forward a reliable and repeatable Information Systems Plan. Included in the development, execution, and evolution of ISPs are Metabase System components for:
- Enterprise Data Models
- Database Object Models
- Resource Life Cycle Analysis
- Business Information Systems models
- Project Management
Enterprise Data Models. The development of the enterprise data model is based on database objects that in turn are based on data element models and database models. Once developed, the database objects are able to easily associated with Resource Life Cycle Nodes. Once allocated, there is sufficient information to know the database object, and in turn, database support of the Resource Life Cycle Nodes.
Database Object Models. Database object models are defined through four components:
- The interrelated database tables that form the data structures for database objects.
- The process specifications that control the data integrity of the rows of data for each of the database object assigned tables.
- The various database object life cycle states begin with the null state and proceed through the various states of valuation and ultimately return to the null state when database object instances are removed from the database.
- The specifications of the database object state information systems that specify what must occur to transform a database object instance from one state to the next.
Because subset collections of the database objects are allocated to the resource life cycle nodes, there exists an extremely obvious and simple way of determining ball-park estimates for business information systems development.
Resource Life Cycle Models. Resource Life Cycle data models that include Resource Types, Resources, Resource Life Cycle Nodes, Resource Life Cycle Precedence vectors, associated database objects, associated business information systems, and finally the associations with the information needs of various enterprise missions that are accomplished through the execution of functions from within designated organizations.
The Resource Life Cycle model becomes the business infrastructure backbone, which supports gap-identification, and also the instantly obvious business information system development sequence. This business-basis information system development sequencing step is mission from the three traditional approaches.
Business Information Systems. The development of high level specifications of business information systems that are more than sufficient evidence necessary to validate the accomplishment of their associated Resource Life Cycle Nodes. Associated with the business information system specifications are both the business event cycles and calendar cycles through which the enterprise’s activities are accomplished.
Project Management. Certainly, the development of an Information Systems Plan is a “Bet your business effort.” More importantly, the development of the plan is only the very first step because it is the execution of the plan that is vitally important. Consequently, as the plan is executed, the management of the various projects must be such that the work products are integrated, interoperable, and non redundant.
Additionally, because the various project plans are “data” stored in the Metabase System, and the work products produced through ISP plan executions are also just data stored in the Metabase System, then there can be rapid reaction to any of the inevitable changes needed in the information systems plan. After all, only unexecuted ISPs are perfect.
Once the steps of the Information Systems Plan process are accomplished, the resulting business information systems plan is timely, useable, maintainable, of high quality, and reliably reproducible. It was because of the lack of these very characteristics that the three traditional methods for Information Systems Planning failed and the whole effort fell into disuse.