The purpose of Design is to implement the elementary processes (for example, the Requirements) that we documented in Analysis effectively and efficiently.
In Analysis, we dealt primarily with processes. In Design, we deal primarily with Procedures. As processes have Process Action Diagrams (PADs), procedures have Procedure Step Action Diagrams (PrADs). The term procedure is synonymous with the term program. As you can have batch or client/server programs, you can have batch or client/server procedures, and these procedures will eventually be generated into executable programs.
Each elementary process will be implemented (used) in one or more procedures. Each procedure can implement zero, one or more processes. For example, the single procedure Maintain Patient can implement the three elementary processes Add Patient, Change Patient Information, and Remove Patient. In addition, we can have procedures that do not implement any processes. For example, we can have a procedure that just lists patients by their last name so that we can look up their patient identifier. Typically, we would not have an elementary process that merely produces a list of patients, since that process would not do work as we defined it in Analysis. However, all of the processes included in a Business System would eventually be implemented in one or more procedures that will be added to that business system.
There are many factors involved in how you determine which processes are implemented in which procedures. Some of these factors include:
|
Copyright © 2013 CA.
All rights reserved.
|
|