hw computer science
kzk11207
section_3_sample.pdf
3.2. Process Order Info (Change the name “Component/Module
One to be the actual name of the module you are designing. Repeat section 3.1 for ea. component)
3.2.1 Processing Description
Provide a Primitive DFD (SAD) or a Use Case Diagram (OOAD) and a brief
narrative
Customer
Sales Person
& Operations
Manager
Provide info
2.1
Create new
order
2.2
Update order
info
2.3
Search for
order
Order Data
Order Data
Search params
Order
Database
Invalid Data
Valid Order Info
Invalid search params
Search results
Valid search params
Search results
Valid Order Info
Invalid Data
Module 2.1 – Create new order
o Customer provides order information to Sales Person or Operations Manager (staff).
Staff enters data into system. If data is validated, system creates a new order in Order
Database and triggers Notification module. If data is invalidated, error message is
returned to Staff.
Module 2.2 – Update order info
o Customer provides order information to Staff. Staff enters data into system. If data is
validated, system updates order in Order Database. If data is invalidated, error message
is returned to Staff.
Module 2.3 – Search for order
o Staff enters order search parameters into system. If search parameters are validated,
system searches Order Database for order that fulfills search parameters and returns
search results to Staff. If system is unable to locate order that fulfills search parameters,
system will return failure message.
3.2.2 Interface Description
3.2.2.1 Module 2 – Process Order Info
There are several items that should be covered here:
If the component has a GUI, display the image of the GUI and define each
field, button, link on the GUI.
if the component receives data, describe the data coming in and where it
should go once it is processed (Input/Output)
If there is data to be passed to another component that should be listed This section will have a detailed written description of what each button, link, data
entry field etc., does on the page, with an image of the proposed page layout, for
each page.
WSC – Order Processing
search
Job type
Media type
Catalog #
Printing/Engraving content
Order Processing
Create New Order Search Orders Update Order
Name of Customer (#cust_id)
Cancel
Order ID #
Type of Job:
Type of Media:
Media Catalog #:
Content to Print/Engrave:
W2
WSC - Message
Insufficient/Incorrect information
entered. Please verify data and try
again.
W2m
OK
Module 2 – GUI Control Info
Control Name Control Type Control Data Control Description
lbl_msg Label Name of
lbl_cust_name Label cust_fname + cust_lname Display from Customer Database of customer first and last name concatenated
lbl_cust_id Label cust_id Display from Customer Database of customer ID number
lbl_ord_id Label Order ID #
txt_ord_id Textbox Search Enter Order ID # here to search for corresponding order from Order Database
lbl_job_type Label Type of Job
drp_job_type Drop Down Print; Engraving Required input for creating/updating an order
lbl_media_type Label Type of Media
drp_media_type Drop Down Clothing; Plaque; Trophy Required input for creating/updating an order
lbl_catalog_num Label Media Catalog #
txt_catalog_num Textbox Catalog # Required input for creating/updating an order
lbl_content Label Content to Print/Engrave
txtarea_content TextArea Printing/Engraving Content Required input for creating/updating an order
btn_create_orde r Button Create New Order Validates order info and then redirects to either window W2m or W2.1
btn_search_orde r Button Search Orders Validates search field and then redirects to either window W2m or W2.3
btn_update_ord er Button Update Order Validates order info and then redirects to either window W2m or W2.2
btn_cancel Button Cancel
3.2.2.2 Module 2.1 – Create New Order
There are several items that should be covered here:
If the component has a GUI, display the image of the GUI and define each
field, button, link on the GUI.
if the component receives data, describe the data coming in and where it
should go once it is processed (Input/Output)
If there is data to be passed to another component that should be listed This section will have a detailed written description of what each button, link, data
entry field etc., does on the page, with an image of the proposed page layout, for
each page.
W2 WSC – Order Processing
Order id #
Job type
Media type
Catalog #
Printing/Engraving content
Create New Order
Accept
Name of Customer (#cust_id)
Decline
Order ID #
Type of Job:
Type of Media:
Media Catalog #:
Content to Print/Engrave:
W2.1
WSC - Message
Order has successfully been
created and added to Order
Database
W2.1m
OK
Module 2.1 – GUI Control Info
Control Name Control Type Control Data Control Description
lbl_msg Label Name of
lbl_cust_name Label cust_fname + cust_lname
Display from Customer Database of customer first and last name concatenated
lbl_cust_id Label cust_id Display from Customer Database of customer ID number
lbl_ord_id Label Order ID #
lbl_ord_id_ Label Display data of txt_ord_id from window W2
lbl_job_type Label Type of Job
lbl_job_type_ Label Display data of drp_job_type from window W2
lbl_media_type Label Type of Media
lbl_media_type_ Label Display data of drp_media_type from window W2
lbl_catalog_num Label Media Catalog #
lbl_catalog_num _ Label Display data of txt_catalog_num from window W2
lbl_content Label Content to Print/Engrave
lbl_content_ Label Display data of txtarea_content from window W2
btn_accept Button Accept Passes data to Order Database and displays success alert W2.1m
btn_decline Button Decline Returns user to window W2
3.2.2.3 Module 2.2 – Update Order Info
There are several items that should be covered here:
If the component has a GUI, display the image of the GUI and define each
field, button, link on the GUI.
if the component receives data, describe the data coming in and where it
should go once it is processed (Input/Output)
If there is data to be passed to another component that should be listed This section will have a detailed written description of what each button, link, data
entry field etc., does on the page, with an image of the proposed page layout, for
each page.
W2 WSC – Order Processing
Order id #
Job type
Media type
Catalog #
Printing/Engraving content
Update Order
Accept
Name of Customer (#cust_id)
Decline
Order ID #
Type of Job:
Type of Media:
Media Catalog #:
Content to Print/Engrave:
W2.2
WSC - Message
Order has successfully been
updated.
W2.2m
OK
Module 2.2 – GUI Control Info
Control Name Control Type Control Data Control Description
lbl_msg Label Name of
lbl_cust_name Label cust_fname + cust_lname
Display from Customer Database of customer first and last name concatenated
lbl_cust_id Label cust_id Display from Customer Database of customer ID number
lbl_ord_id Label Order ID #
lbl_ord_id_ Label Display data of txt_ord_id from window W2
lbl_job_type Label Type of Job
lbl_job_type_ Label Display data of drp_job_type from window W2
lbl_media_type Label Type of Media
lbl_media_type_ Label Display data of drp_media_type from window W2
lbl_catalog_num Label Media Catalog #
lbl_catalog_num _ Label Display data of txt_catalog_num from window W2
lbl_content Label Content to Print/Engrave
lbl_content_ Label Display data of txtarea_content from window W2
btn_accept Button Accept Passes data to Order Database and displays success alert W2.2m
btn_decline Button Decline Returns user to window W2
3.2.2.4 Module 2.3 – Search For Order
There are several items that should be covered here:
If the component has a GUI, display the image of the GUI and define each
field, button, link on the GUI.
if the component receives data, describe the data coming in and where it
should go once it is processed (Input/Output)
If there is data to be passed to another component that should be listed This section will have a detailed written description of what each button, link, data
entry field etc., does on the page, with an image of the proposed page layout, for
each page.
W2 WSC – Order Processing
Order id #
Job type
Media type
Catalog #
Printing/Engraving content
Search Results
OK
Name of Customer (#cust_id)
Cancel
Order ID #
Type of Job:
Type of Media:
Media Catalog #:
Content to Print/Engrave:
W2.3
WSC - Message
No order found. Please try again.
W2.3m
OK
Module 2.2 – GUI Control Info
Control Name Control Type Control Data Control Description
lbl_msg Label Name of
lbl_cust_name Label cust_fname + cust_lname
Display from Customer Database of customer first and last name concatenated
lbl_cust_id Label cust_id Display from Customer Database of customer ID number
lbl_ord_id Label Order ID #
lbl_ord_id_ Label Display data of txt_ord_id from window W2
lbl_job_type Label Type of Job
lbl_job_type_ Label Display data of drp_job_type from window W2
lbl_media_type Label Type of Media
lbl_media_type_ Label Display data of drp_media_type from window W2
lbl_catalog_num Label Media Catalog #
lbl_catalog_num _ Label Display data of txt_catalog_num from window W2
lbl_content Label Content to Print/Engrave
lbl_content_ Label Display data of txtarea_content from window W2
btn_accept Button OK Returns user to window W2
btn_decline Button Cancel Returns user to window W2
3.2.3 Pseudocode
The processing rules for the component – in logical order. But remember, language
independent. (link to a great example) http://www.wiley.com/college/busin/icmis/oakman/outline/chap05/slides/pseudo.htm
Put things here if it is needed to help explain the business rule functionality of the screen.
For example if you need to check to make sure a customer has no outstanding balance past
60 days in order for them to generate another order identify what data values need to be used to do this and the math functions that need to be used.
If Customer Balance > 0 and Last Purchase Date < (current date – 60 days) then
Deny Purchase
Else Allow Purchase
You can break this down into functions or procedures if that is the best way to approach this
for your project.
Module 2.1 – Create New Order
BEGIN CREATE NEW ORDER
Enter order data (type of job, type of media, media catalog #, content)
BEGIN IF order data is incomplete or missing
Return error message to user
Return user to order data entry screen
ELSE order data is complete
Insert new order into Order Database
Return message to user that creation was successful
Return user to order data entry screen
Clear order data entry screen
END IF
END CREATE NEW ORDER
Module 2.2 – Update Order Info
BEGIN UPDATE ORDER INFO
Enter new order data
BEGIN IF new order data is incomplete or missing
Return error message to user
Return user to data entry screen
If new order data is complete
Display new order data summary for verification
BEGIN IF user disagrees
Return user to order data entry screen
ELSE user agrees
Update order in Order Database
Return message to user that update was successful
Return user to order data entry screen
Clear order data entry screen
END IF
END IF
END UPDATE ORDER INFO
Module 2.3 – Search For Order
BEGIN SEARCH FOR ORDER
Enter search parameters
BEGIN IF search parameters are incomplete or missing
Return error message to user
Return user to search screen
Clear data from search screen
ELSE search parameters are valid
Search Order Database
BEGIN IF search returns results FALSE
Return message of no results
Return user to search screen
ELSE search returns results TRUE
Display order data entry screen
Fill fields with search results
END IF
END IF
END SEARCH FOR ORDER
