A methodology or a procedure requires a schema; it is defined as the principle that enables the understanding to unify experience. The design of a schema is half the problem, the other half is the user interface to it. We look at these requirements by examining the nature of process design and how it is communicated. The word ‘process’ is used quite frequently in everyday communications to describe events that help to create something useful or achieve some outcome. In the business environment it defines the events that create value adding; in the manufacturing environment it defines the method that creates products; in the cooking environment it defines the recipe. This widespread use of word shows its all encompassing influence as a means of expressing activity and this leads us to the question whether it is possible to design process along scientific lines rather than evolve it through trial and error, which is often the case, witness the comment when something goes wrong, it is invariably the process that needs looking at.
KeywordsSchema Design Process Knowledge Task Sequence Part Object Task Object
- 1.Pressman, R. S. (2005). Software engineering: a practitioner’s approach (6th ed.). UK: McGraw-Hill International Edition.Google Scholar
- 2.Grewal, S., & Choi, C. K. (2005). An integrated approach to manufacturing process design and costing. Journal of Concurrent Engineering: Research and Applications, 13(3), 199–207 (ISBN 1063 292X).Google Scholar