Scribd
Upload
24 views1 page

Tutorial 2 SAD 2 Ver 2

The document discusses system analysis and design topics such as data elements needed on physical DFDs but not logical DFDs, the purpose of structure charts, different types of modules on structure charts, and the differences between structured and event-driven programming. It also provides a scenario about a dentist office system and tasks the reader with drawing DFDs and a structure chart for it and creating a program specification and pseudocode for checking appointment availability.

Uploaded by

Kelvin Chaula
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views1 page

Tutorial 2 SAD 2 Ver 2

The document discusses system analysis and design topics such as data elements needed on physical DFDs but not logical DFDs, the purpose of structure charts, different types of modules on structure charts, and the differences between structured and event-driven programming. It also provides a scenario about a dentist office system and tasks the reader with drawing DFDs and a structure chart for it and creating a program specification and pseudocode for checking appointment availability.

Uploaded by

Kelvin Chaula
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

ITU07203: Systems Analysis & Design II

Tutorial 2

1. What are some of the system-related data elements and data stores that may be needed on
the physical DFD that were not a part of the logical DFD?

2. What is the purpose of the structure chart in program design?

3. Distinguish between a control module, subordinate module, and library module on a


structure chart. Can a particular module be all three? Why or why not?

4. What is the difference between structured programming and event-driven programming?

5. Whenever new patients are seen for the first time, they complete a patient information
form that asks their name, address, phone number, and brief medical history, all of which
are stored in the patient information file. When a patient calls to schedule a new
appointment or change an existing appointment, the receptionist checks the appointment
file for an available time. Once a good time is found for the patient, the appointment is
scheduled. If the patient is a new patient, an incomplete entry is made in the patient file;
the full information will be collected when the patient arrives for the appointment.
Because appointments are often made so far in advance, the receptionist usually mails a
reminder postcard to each patient two weeks before his or her appointment.
Required:

(a) Draw a logical and physical level 0 data flow diagram (DFD) for the above dentist
office system.

(b) Create a structure chart based on the data flow diagrams (DFDs) that you created in
part (a) above.

(c ) Create a program specification for module ‘check the appointment file for an
available time’.

(d) Create pseudocode for the program specification that you wrote in part (c )

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy