Discuss the difference between the logical and physical process models within any software development methodology? How do the two process models relate?

YOU ARE NOT SUPPOSED TO ANSWER BUT TO DISCUSS YOUR POINT OF VIEW OF THE ABOVE-MENTIONED QUESTIONS! FOR A BETTER UNDERSTANDING OF WHAT YOU NEED TO DO PLEASE READ MY COMMENTS ABOVE.

As you are trying to post about this particular subject please try addressing the following questions from your own perspective:

What is the difference between logical data flow diagrams (DFD) and physical data flow diagrams (DFD)? Give an example of each.

Explain how information gathering results are direct input into creating the logical data flow diagrams (DFD)? Give an example.

User stories, use cases, business activities, and process workflows are examples of information requirements that can be input into graphically capturing user requirements in process models. Give an example of how that can work.

What is the purpose of the CDFD? Why is it the first DFD created in the process model?

Describe the four basic symbols to create a DFD? In terms of the naming convention guidelines, which symbols should be named as a noun or a verb phrase for better clarification in the diagram?

Create a CDFD for a library system? Identify the external entities first then their purpose for interacting with the system using data flows?

What are the key differences between the CDFD and the first exploded DFD, called Diagram 0?

What is the difference between leveling or exploding the DFD and balancing the DFD? Describe in detail with an example for each.

What are some common DFD errors made when creating (leveling or exploding) DFDs? Draw and describe three errors.

When do you create process logic specifications or descriptions? How is the content helpful to transitioning to quality program specification?