1. Discuss the relevance of the human factor in the design and development of information
systems. (The systems development methodology is not relevant in your response and therefore
is not to be discussed). Do not respond with one big long paragraph (blob of writing).
Respond with several meaningful paragraphs. Immediately, follow with references for
your response to question no 1.
2.Discuss (in detail) the three important/key post implementation activities (including what activities
are performed in each of the three important/key post-implementation activities) as stated in our
readings. Do not respond with one big long paragraph (blob of writing). Respond with
several1 meaningful paragraphs. You should respond with at least one paragraph for each of
the three post implementation activities. Immediately, follow with the references that were used
for your response to question No 2.
3. Draw the two Data Flow Diagrams as explained below. (25 points)
Use software to draw these DFDs. Do not draw/sketch them by hand. These two DFD
diagrams are to be copied/embedded into this Microsoft Word Final Exam file. Make sure
each DFD is large enough so I can read each one of them.
Early Diner wants to install a system to record orders for breakfast sandwiches and platters. When
regular customers call Early Diner on the phone, they are asked their phone number. When the
number is typed into a computer, the name, address, and last order date is automatically brought up

on the screen. Once the order is taken, the total, including tax and delivery, is calculated. Then the
order is given to the cook. A receipt is printed. Occasionally, special offers (coupons) are printed so
the customer can get a discount. Drivers who make deliveries give customers a copy of the receipt
and a coupon (if any). Daily totals are kept for comparison with last year’s performance. A summary
of business activities for taking an order at Early Diner is as follows:
3a. Draw a context-level data flow diagram for Early Diner.
3b. Explode the above context-level diagram by drawing the logical data flow diagram 0
showing all the major processes using the following items:
The following Processes, Data Stores, and Entities are to be used when drawing your DFDs.
Process names:
(1) Find and display customer record
(2) Take customer order
(3) Send order to cook
(4) Print customer receipt
(5) Deliver customer order
(6) Print weekly totals
Data stores:
(1) Customer Master
(2) Product File
(3) Coupons
(4) Sales history
Entities:
(1) Customer
(2) Management
(3) Cook
(4) Delivery Person
4. Draw the Entity Relationship Diagram (ERD) as explained below. Be sure to show cardinality in
both directions using Crows Foot notation. Do NOT include the fields/attributes or keys for each
entity. Do not include any additional entities and/or relationships to your ERDs than what is
described below.
(25 points)

Use software to draw the following ERD. Do not draw/sketch it by hand. The ERD is to be
embedded/copied into your final exam Microsoft Word file. You are NOT to submit a
separate file for this ERD. Make sure it is large enough so I can read it.
Dale University is divided into several schools: Law, Police Science, Technology. Each
SCHOOL is administered by a dean who is a PROFESSOR. Each professor can be the dean of
only one school and a professor is not required to be the dean of any school.
Each school comprises several departments. For example, the school of technology has a
forensic science department, a cyber security department, a database department, and a zoom
department. The smallest number of departments operated by a school is one, and the largest
number of departments is many (indeterminate). On the other hand, each DEPARTMENT
belongs to only a single school. That is, the minimum number of schools to which a department
belongs is one, as is the maximum number.
Each department may offer courses. For example, the database department offers courses such
as Introduction to Database, Microsoft Access, and Oracle. If Dale University had some
departments that were classified as “research only” they would not offer courses; therefore, the
COURSE entity would be optional to the DEPARTMENT entity.
A CLASS is a section of a COURSE. That is, a department may offer several sections (classes)
of the same database course. Each of those classes is taught by a professor at a given time in a
given place. CLASS is optional to COURSE.
Each department should have one or more professors assigned to it. One and only one of those
professors chairs the department, and no professor is required to accept the chair position.
Therefore, DEPARTMENT is optional to PROFESSOR in the “chairs” relationship.
Each professor may teach up to three classes; each class is a section of a course. A professor
may also be on a research contract and teach no classes at all.