By paul ~ December 4th, 2006. Filed under: FAQ, Systems Engr..
When we talk about performance modeling, we’re talking about system-level performance models. The components in the system may be people, computers, trucks, networks, or electronics components. The way Foresight works is that you use data flow diagrams (DFDs), state transition diagrams, and procedural “code” to describe the behavior of your system. The diagrams are simple to understand and use, very much like you might draw on a whiteboard or the back of a napkin This description can be executed, via discrete event simulation (DES), to explore it’s behavior.
A resource model is then constructed which describes the behavior of the resources that perform those tasks (whether they be people, machines, microprocessors, reservoirs, etc.), the tasks are mapped to (assigned to) these resources, and the model is executed again. This refinement of the model, however, executes within the constraints of the resource model. The resulting “performance model” gives a very good feel for how the system will behave in the performance domain (time, cost, power, quality, etc.) This is particularly important in systems where resources are shared and there is resource contention. Such a model can be used to optimize resource assignment, scheduling, and provisioning.
Application domains include logistics, busines process modeling (BPM), networked and distributed computing systems, embedded systems, manufacturing, and control systems. Be sure to check out the plethora of white papers for examples of Foresight usage.