Computer Science Question

I need help with Part C Data Dictionary. I will attach two data dictionary pdf documents and an instruction pdf document. Also I will attach an assignment homework Word document that was created in Part A & Part B.

Part C: WORTH 20 POINTS— Data Dictionarya. Create a Data Dictionary for Level 1.b. Use the sample in the module as a guide.Note: The Data Dictionary must include a detailed description of all data elements in theDFD Level 1.c. Use MS Word to generate the table and content for your Data Dictionary. CPT264 ASSIGNMENT #5
(System Design Specification Sheet)
ASSOCIATED READING

Read Chapter 2 and Chapter 3 in your “Systems Analysis and Design” Textbook
Report Guidelines and Group Communication (10 points):
1.
2.
3.
4.
5.
6.
Your member name(s), date, and assignment # must be at the top of each page.
Each new section/part of your paper needs to have a title.
Text must be double-spaced.
Bullet points must be used where appropriate.
Insert page numbers at the bottom of each page.
There should be NO spelling, writing or grammar errors. Do not use slang or short-hand. Proper
grammar and sentence structure count.
7. The Group Discussion thread must be up-to-date and meet all reporting guidelines.
Part A: WORTH 30 POINTS—Context Level Data Flow Diagram (DFD)
a. Create a complete and accurate Context Level Data Flow Diagram of your intended
Information system.
b. Use the instructions and illustrations in your textbook and the sample in the module as a
guide.
c. Use MS Word to generate the correct shapes and arrows for your diagrams.
Part B: WORTH 35 POINTS— Level 1 Data Flow Diagram (DFD)
a. Create a complete and accurate Level 1 Data Flow Diagram of your intended Information
system
b. Use the instructions and illustrations in your textbook and the sample in the module as a
guide.
c. Use MS Word to generate the shapes and arrows for your diagram.
Part C: WORTH 20 POINTS— Data Dictionary
a. Create a Data Dictionary for Level 1.
b. Use the sample in the module as a guide.
Note: The Data Dictionary must include a detailed description of all data elements in the
DFD Level 1.
c. Use MS Word to generate the table and content for your Data Dictionary.
Part D: WORTH 5 POINTS – Member Contribution Report
1. Create a new page to document the contribution(s) of each member of your team to this
assignment. For each team member list:
a. Who (group member name)
b. What they contributed to this assignment
Assignment Submission Steps:
1. Save your document with name, Group#_Assignment#
2. Submit in the Assignment folder in D2L.
a. All items (Context Level Data Flow Diagram, Level 1 Data Flow Diagram, Data Dictionary
and Member Contribution Report) MUST be comprised in a single Word file.
REMINDER: Only the Group Leader submits group assignment files; in the assignment dropbox.
1
Project Name: Invoice and inventory Systems Analysis
Date: August 4, 2016
Systems Analyst: Jane Smith
Course: CPT264 Summer 2016
Context DFD
HITS
ORDER
CUSTOMER
WEBMASTER
REQUEST
0
WEB
SITE
PAGE
PRODUCT DATA
INVOICE
STORE
Level 0 DFD
REQUEST
CUSTOMER
HITS
PAGE
WEBMASTER
ORDER
INVOICE
D1
2
1
PROCESS
ORDER
PHP
REQUEST
HANDLER
DATABASE
PRODUCT DATA
PRODUCT DATA
INVOICE
STORE
1
2
Data Dictionary (this sample has three pages)
Data Elements DescriptionNAME: Package List
FILE: packages.xml
SOURCE: Webmaster
TYPE/LENGTH: XML datasheet/~20KB
RESPONSIBLE USER: Webmaster
SECURITY: Webmaster and Store Owner
PURPOSE: Contains a database table of packages, separate items, and additional add-ons.
NAME: Invoices
FILE: invoices.xml
SOURCE: Webmaster
TYPE/LENTH: XML datasheet/~6KB
RESPONSIBLE USER: Webmaster
SECURITY: Webmaster and Store Owner
PURPOSE: Lists customers’ purchases of packages and items. Also lists credit card authorizations
and order numbers.
NAME: Hits
FILE: requests.txt
SOURCE: PHP Request Handler
TYPE/LENGTH: Text file/8KB
RESPONSIBLE USER: Webmaster
SECURITY: Webmaster and Store Owner
PURPOSE: Report that shows the number of page requests (a.k.a. hits) from web browsers
NAME: Pages
FILE: main.php
SOURCE: PHP Request Handler
TYPE: PHP server script
RESPONSIBLE USER: Webmaster
SECURITY: Webmaster
PURPOSE: Server script that processes page requests and sends them to the browser(s).
NAME: Credit Card
ALIAS: CC
SOURCE: Customer
TYPE/LENTH: 12N and 4N
RESPONSIBLE USER: Webmaster
SECURITY: Webmaster
PURPOSE: Credit Card number and 4 digit expiration
2
3
Data Flow DescriptionNAME: Product Data
ORIGIN: Webmaster
DESCRIPTION: XML formatted data table
DESTINATION: Database and PHP Request
Handler
VOLUME AND FREQUENCY: ~10/week
COMMENTS: Contains information about package ensembles, individual items, additional add-ons,
size availability, image url and pricing
NAME: Hits
DESCRIPTION: Text file
ORIGIN: PHP Request Handler
DESTINATION: Webmaster
VOLUME AND FREQUENCY: 1-4KB daily at midnight
COMMENTS: Provides information on number of browser hits for each website
NAME: Request
DESCRIPTION: Browser page request
ORIGIN: Customer
DESTINATION: PHP Request Handler
VOLUME AND FREQUENCY: ~20/day
COMMENTS: Sends PHP header information which will be used to generate a product list
NAME: Page
DESCRIPTION: HTML page
ORIGIN: PHP Request Handler
DESTINATION: Customer
VOLUME AND FREQUENCY: ~20/day
COMMENTS: Sends formatted HTML page dependent on the header information that was sent from
browser
NAME: Invoice
DESCRIPTION: XML formatted data table
ORIGIN: Process Order
DESTINATION: Customer and Store
VOLUME AND FREQUENCY: ~5/month
COMMENTS: XML file that lists customer’s purchase, authorization number and order number
NAME: Order
DESCRIPTION: XML formatted data table
ORIGIN: Customer
DESTINATION: Process Order
VOLUME AND FREQUENCY: ~5/month
COMMENTS: XML table sent into the request header for the API to process
3
4
Process Description ID: 0
NAME: Web Site
PURPOSE: Increase online sales revenue and show a catalog of items
INPUT: Product Data, Order, Request
OUTPUT: Page, Invoice, Hits
DESCRIPTION: Online web site for item viewing and purchases with credit card
ID: 1
NAME: PHP Request Handler
PURPOSE: Accept page requests and send formatted HTML page
INPUT: Product Data, Request
OUTPUT: Page, Hits
DESCRIPTION:
ID: 2
NAME: Process Order
PURPOSE: Accept credit card information, create invoice and authorize transaction
INPUT: Order
OUTPUT: Invoice
DESCRIPTION: API is sent form Customer’s browser and processed
Data Store LABEL: D1
ENTRY TYPE: FTP binary upload from
Webmaster
DESCRIPTION: XML nodes of size, name, price, and jpg. url attributes
COMPOSITION: XML file
LONG NAME: Database
4
Data Dictionary for Library System
Entity Description
Name: Student
Kind: Entity
Type: ID number + first name + middle initial + last name + status
Description: Corresponds to students who are registered in or who have recently passed the
course
Data Elements Description
Name: first name
Kind: Attribute
Type: string
Description: A non-key attribute of Student
Name: ID number
Kind: Attribute, Data Flow
Type: integer
Description: A key attribute of Student; should be exactly eight digits long
Name: last name
Kind: Attribute
Type: string
Description: A non-key attribute of Student
Name: middle initial
Kind: Attribute
Type: character
Description: A non-key attribute of Student
Name: status
Kind: Attribute
Type: [ `current’ | `alumni’ ]
Description: A non-key attribute of Student
Data Flow Description
Name: book name
Kind: Data Flow
Type: Book
Description: Title of Book
Name: book status
Kind: Data Flow
Type: [ `available’ | `borrowed’ ]
Description: Status of book availability
Name: student request
Kind: Data Flow
Type: [ `borrow’ | `return’ ]
Description: Type of Student request
Name: student name
Kind: Data Flow
Type: first name + middle initial + last name
Description: Name of Student
Data Process Description
Name: Book Information
Kind: Process
Type: book name + book author + year
Description: Full description of the Book
Name: Book Status
Kind: Process
Type: [ `available’ | `borrowed’ ]
Description: Status of book availability
Data Store Description
Name: Book Information
Kind: Data Store
Type: Book
Description: