1. Distinguish between logical process models and physical process models.

Process models are a set of activities or workflows that are used to achieve a specific goal and are
usually in a graphic format. Logical process models focus on the system’s process, what the system will
do. They simply state the functional requirements of the to-be system or as-is system. They do not provide
details on how decisions are made or how tasks are selected during the process. Examples of the activities
described in the logical process models are: Identifying which activity is to be completed next and
obtaining the data that will be used. The logical process models will be also be used as a reference when
the physical process models are being created.

Meanwhile, a physical process model provides a detailed way of implementing the system or the
logical process model. It is the actual design or blueprint of the system because its goal is to portray the
system as accurately as possible when the user uses it. Examples of the physical process model activities
are: which tasks should be completed first, and in what order, what data is needed to start the process,
and what information is needed to begin and complete each task.

2. How can you make a DFD easier to understand?

Using a data flow diagram, you can see how data moves throughout a system or process. A data
flow diagram shows all the steps a set of information takes to get from one place to another. Aside from
constantly using standardized symbols and notations, color-coordinating certain types of the process will
help make the DFD easier to understand. Adding numbers to the symbols and notations, especially the
data flow or arrow symbol, will also help. This way, the person looking at the DFD will not be overwhelmed
by the different shapes and arrows in the diagram because they will know where the DFD starts and ends.
I also think that making a text-based data flow will significantly help someone unfamiliar with the symbols
and notations used in DFDs. This way, they will be able to read the text-based data flow while using the
DFD as a reference.

3. Why is a process model typically composed of a set of DFDs? What is meant by decomposition of a
business process?

Process models are usually too complicated to be represented in a single diagram. This is why
they are composed of a set of DFDs, to be able to explain the process model in detail. In DFD, the first
diagram (Context Level), the whole system is represented by a single process symbol, providing an
overview of the entire system with subsequent DFDs showing increasing levels of detailed representation.
Having a set of DFDs will enable the user to understand better the functioning of a process or system to
identify possible issues, increase efficiency, and create better procedures.

In business, decomposition is the practice of breaking down an extensive business process into
smaller, logical business processes. By breaking down a business process, the creator of the DFD will think
it through from the beginning, consider additional details, plan a better implementation, and make sure
that nothing is overlooked or forgotten. They will get a better understanding of the process since it is very
detailed.
II. Case Study

1. What are the advantages and disadvantages of setting a limit for the maximum depth for a
DFD?

An advantage of setting a limit for the maximum depth for the DFD is that developers are forced to
be more efficient in their process selection. They are required to develop a more straightforward DFD.
Initially, they chose 1500 processes, which were described in 3300 pages of documentation. It was
considered unusable because it was too big. Because of this, the developer must develop a less
complicated DFD that will give the same level of effectiveness as the first one.

2. Is a level 4 DFD an appropriate limit?

The necessary level of detail will depend on the scope of the business process. But going over
level 3 of DFD is already uncommon, which makes a level 4 already detailed. If the number of layers of a
DFDwere to exceed level 4, a lot of important information may likely be lost. For each particular system
or business process, the level of complexity of the overall system or business process that is being
represented provides the boundaries for determining the "optimal" level of decomposition. Processes are
broken down into DFDs when the extra decomposition helps in explaining the complexity of the process.
In the case study, the project leader decided that level 4 DFDs were already enough to cover all the
requirements, thus making the level 4 DFD an appropriate limit for this project.
IIII. Draw an entity relationship diagram (ERD) for the following situation:

Patient Doctor
Appointment
PAT_lastname DOC_lastname
APP_date
PAT_firstname DOC_firstname
APP_time
PAT_address DOC_speciality
APP_reason
I PAT_city
II I I II
APP_duration DOC_address
PAT_state DOC_city
APP_status
PAT_phonenumber DOC_state
PAT_insurancecarrier II
II
I

II
Insurance Company
Payment Bill
INS_name PAY_receipt
INS_benefitscontract BIL_status
PAY_amount
INS_companyaddress
II I II
BIL_amountinsured
PAY_date
INS_claiminginformation BIL_amountnotinsured
PAY_method