hw computer science
3. Detailed Design
This section will define and describe the design details for each of the components in the application.
(The intent of this section is to prepare for the build phase. These detailed design specifications will become a program in your system)
3.1. Component/Module One (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.1.1 Processing Description
Provide a Primitive DFD (SAD) or a Use Case Diagram (OOAD) and a brief narrative
3.1.2 Interface Description
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.
3.1.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.
3.1.4 Modules Uses
If this component is a function that is called by other functions, such as a DB call to retrieve
data, insert data, update data or delete data, or some type of standard calculation used by
multiple modules, you will describe that here. If this section does not apply to the
component, simply delete the section.