An example of a software process model based on unit workload network

We are developing a software engineering and management database called KyotoDB based on an object-base-data model. It has two types of objects. The first represents engineering data such as specifications, programs, etc., and encapsulates operations on these data. The second represents management data and encapsulates operations on the management data. Each instance of the second type object, representing each individual Unit Workload, includes process programs and operations on management data (schedule, cost, quality, etc.) for that Unit Workload. The process program in UnitWokload class invokes tools (editors, compilers, debuggers, etc.), and pass engineering data (files) or management data to those tools. The process programs also specify procedures to maintain semantic consistency between many engineering data, as well as between many human interactions. Figure 1 shows an example hierarchical structure in KyotoDB. Figure 2 is an example of process program in class Unit Workload.