- Create the context level data flow diagram for the Ecommerce system. Refer
to the Ecommerce JAD session (refer to the items below Exercise 2 to help
you create the diagram)..
- Create Diagram 0 for the Ecommerce system. Refer to the Ecommerce JAD session.
The following will help to create the diagram.
Possible external entities
Customer
Warehouse Operations and Shipping
Credit Card Company
Customer Service
Possible activities
Add new customer
Verify existing customer
Sending order confirmation to customer
Send shipped order confirmation to customer
Get credit card information
Receive customer return information
Select products for shopping cart
Looking up customer information in response to an inquiry
Producing statistical analysis reports
Possible data stores
Customer
Product
Order
Returned Items
Create the following data flow child diagrams
for the GEMS system. Diagram 0 is in the documentation found from a link
in Rabin's office. Refer to the process number that explodes to the diagram
for further information.
- Diagram 1.2, Update Requirements, used to add a new requirement to the Requirements
data store.
- Diagram 1.3, Update Tasks, used to update task information.
- Diagram 1.4, Update Milestones. This process adds new milestones for a project.
- Diagram 1.5, Update Leader Information, used to add or change leader records.
- Diagram 1.6, Close Completed Project. This process is responsible for closing
projects that have been finished.
- Diagram 2, Update Resources, used to add or change information about human
resources.
- Diagram 5.1, Produce Project Schedule. This process prints the Project Schedule
Report
- Diagram 6.1, Query Project Information, used to find and display project
information.
- Diagram 6.2, Query Milestone Information. This process displays a milestone
and the related Project, Task and Requirement information.
- Diagram 6.4, Query Task Information, displaying task and related requirement
information.
- Diagram 6.5, Query Requirement Information. Displays information about a
single requirement.
- Diagram 6.6, Query Resource Information. This process displays information
about a human resource and related tasks, milestones and projects.
- Diagram 6.7, Query Leader Information, displaying information about a single
leader.
- Add a new process (number 3) to Diagram 5. The process name is Print Missing
Resource Hours.
This process would report on all resources that have not entered their hours
worked for the week. Input is the Resource Work Completed transaction database
table, Assignment Record, the Resource Record and the Task Record. Output
would be the Incomplete Resource Project/Task Hours, showing the fields listed
in the Output Analysis description below. Refer to the prototype found in
Ketcham's office. Print diagram 5.
| Information Needed |
Screen or Report
Name |
Screen/Report Description |
| Late Project Information |
Incomplete Resource Project/Task Hours |
Resource Number, Resource Name, Resource Title, Telephone, Hours Worked,
Date Work Done, Task Number, Task Description, Total Hours Per Week.
Each resource may have many task lines, with the Total Hours Per Week
listed once at the end of the resource group of lines. |
- Create and print the child diagram of process 5.3. This diagram should
include sorting the Resource Work Completed transaction table (containing
Resource Number, Hours Worked, Date Work Done, and Task Number) to obtain
the right sequence. When creating the diagram, think about the execution sequence
of the processes. Partition the diagram by drawing dotted lines around the
processes that would go into each program. Refer to the report prototype found
in Ketcham's office.
- Add a process to Diagram 6 showing the online equivalent to the report produced
by the diagram in Exercise 17. Refer to the prototype found in Sherman's office.
- Create the child diagram for Exercise 18.
- Add a new process (process 7) to Diagram 0 that creates the Country data
store. This is a new database table used to keep track of information about
each country that MRE is thinking about doing business with. The data store
contains the following elements: Country Name, International Telephone Country
Code, Currency Name, Currency Exchange Rate, the name, address and other information
for a contact person, and a comment field (or fields) for keeping track of
specific zoning laws or other unique situations that would impact the completion
of MRE projects in a specific region of that country. Print the modified Diagram 0
- Create and print the child diagram for adding the Country data store. There
are many potential countries that MRE has the potential to do business with,
and it has been decided to use the Web to add countries. Data is gathered
and entered using a series of Web pages. One page is used to enter country
information, a second to add a contact person for the country, and a third
for regional information, such as zoning laws. The Country, Contact Person
and Regional database tables are updated.
- Add a new process (number 4) to Diagram 5. The process name is Print Client
Project Report. The output interface data flow is the Client Project Status
Report. Refer to the report prototype found in Ketcham's office. Print diagram
5.
A separate page should be printed for each client. The report should list
all projects for a client and include information from the Project Master,
Milestone Master, Task Master and Assignment data stores. It also uses a
Client Master data store that contains information about a client, such
as the Client Name, Address, etc. The primary key field is the Client Name.
- Create the child diagram for the Print Client Project Report process. Refer
to the report prototype found in Ketcham's office. Refer to Exercise 23 for
details.
- Add a new process to Diagram 6. The process name is Display Client Project
Information. Determine the data stores required for this process, based on
the prototype Web page found in Blandford's office. The output interface data
flow is the Client Project Web Page. Print diagram 6. Assume that the client
has logged on and is connected to a secure Web server (not a part of this
diagram).
- Create the child diagram for the Display Client Project Information process
found in Exercise 24.
A separate Web page should be displayed for each client project. The Web
pages should list all projects for a client and include information from
the Project Master, Milestone Master, Task Master and Assignment data stores.
It also uses a Client Master data store that contains information about
a client, such as the Client Name, Address, etc. The primary key field is
the Client Name.
Create and print the child diagram for the Display Client Project Web
Page process. Refer to the prototype found in . This diagram should include
using the Project Master to select records, reading the Client Master for
address information, reading the Milestone, Task, and Assignment data stores
for detailed information. Task totals, obtained using calculations based
on data from the Work Completed Data transaction table (mentioned in point
18) and the Resource Master data store should be displayed at the end of
each group of tasks.
Additionally, this Web page should display the Project Category and the
Task Status. The meaning of each of these coded fields should be displayed.
These codes are turned into meanings by using a code table (a database table
containing records with codes and code descriptions). Include these code
tables into the appropriate processes on the diagram.
-
Add a new process (process 1.7) to Diagram 1 that creates the Deliverable
data store. This is a new database table used to keep track of information
about each Deliverable. The data store contains the Deliverable Number,
Deliverable Name and Type of Deliverable (such as software, equipment, and
so on). Each project may have many deliverables, and each deliverable may
be for many projects. The process should enter the deliverable and then
select the project for the deliverable. No other database tables are used.
Print the final version of Diagram 1.
- Create the child diagram for Process 1.7. The input is the New Deliverable
Screen. Activities include validating the screen data, selecting a project
for the deliverable, confirming the screen data, writing a new Deliverable
Record, writing a Deliverable-Project Record, and writing a New Deliverable
Journal Record. Each deliverable has a code indicating the type of deliverable
such as software, equipment, etc. Include this code as a code table as an
input into the edit process. Print the final diagram.
- Add a new process to Diagram 6. The process name is Display Resource Task
Report. Determine the data stores required to print the report. The output
interface data flow is the Resource Task Report. Print the diagram 6. Refer
to the prototype found in Rabin's office.
- Create and print the child diagram for the Print Resource Task Report. This
diagram should include sorting the Assignment Master (by Resource) and then
using the Sorted Assignment Master to select records, reading the Resource
Master for Resource information, Reading the Task Record for task information,
reading the Milestone record to obtain the Project Number and reading the
Project Master for the Project Description. Resource totals should be displayed
at the bottom of each page.
A separate page should be printed for each Resource. The report should
list all projects that a resource is working on and the tasks not yet completed.
Include information from the Project Master, Milestone Master, Task Master
and Assignment data stores.
Additionally, this report should print the Fee Basis and the Project Priority.
The meaning of each of these coded fields should be displayed. These codes
are turned into meanings by using a code table (a database table containing
records with codes and code descriptions). Include these code tables into
the appropriate processes on the diagram.
- Add process 1.8, Add Client Record to Diagram 1. It adds a new record to
the Client Master data store and contains information about a client, such
as the Client Name, Address, etc. The primary key field is the Client Name.
The process uses a New Client Screen to enter the data, and produces a New
Client Record, sent to the Client Master. It also creates a New Client Journal
record, placed in the New Client Journal data store. Print the revised Diagram
1.
- Create and print the child diagram for process 1.8. This is an on-line process,
with activities to Edit the new client data, confirm the new client data,
write the client record and create a client journal record. The Client Record
also contains elements for the total amount spent by the client on projects
(initially set to zero), the number of projects worked on (also zero), a status
code for whether the client is currently working on a project, bidding a project,
in preliminary negotiations for a project or inactive. This code must be verified
(in the edit process) by reading a table of Status Codes. When adding a new
client, select the client country by reading the Country Master. Other code
tables used by the edit process are an Area Code table and a State Postal
Code table.
The following exercises are for child diagrams
of the Ecommerce System (refer to the link found in the Silver interview).
- Create a child diagram for the customer placing an order using the Internet.
Activities include placing items in a shopping cart, checking out, verifying
a valid credit card purchase, sending the customer a confirmation email, updating
customer and item database tables, creating an order record, and sending an
XML document to Terra Shipping.
- Create an Ecommerce system child diagram for the process that adds a new
customer. Use your own Web experience to reflect on the processes that might
be included.
- Create a child diagram for the Ecommerce system that depicts the steps necessary
to use the shopping cart to check out items that have been purchased. Use
your own experience with online ordering to decide what to include on the
diagram. Think about the data stores that would be involved.
- Create a CRUD matrix for the Ecommerce system. Use the following data stores:
Customer, Item, Order, Order Item. Processes would include Add New Order,
Add Customer, Change Customer Information, Add Item, Change Item Information,
Remove Item, Add Order, Change Order (change quantity, add another item, remove
item), Cancel Order, Print Order Picking Slip, Query Customer Information
(Customer information, Order details), Query Item, Display Item Selection
Web page, Check Out Customer Order Order, Print Item Sales Summary.
