Bài thuyết trình môn Phân tích & thiết kế hệ thống - Đề tài: Process specifications and structured decisions
Process Specifications
and
Structured Decisions
Learning Objectives
• Purpose of process specifications
• Difference between structured and
semi-structured decisions
• Use
• structured English,
• decision tables, and
• decision trees
to analyze, describe, and document structured
decisions
Overview
determine the users’ objectives
+
organization’s objectives
→ determine
human information requirements
of a decision analysis strategy
should follow top-down approach
to broad objectives of entire organization
Overview (cont.)
What for?
Data flow diagram
Process specifications
Class method (OOP)
Use case
- minispec
create
Overview (cont.)
What for?
• Reduce process ambiguity
• Obtain a precise description of what is
accomplished
• Validate the system design
Overview (cont.)
What don’t require specifications?
1. Physical input / output
Read / write ( ~ get / set in Class Diagram)
2. Simple data validation
3. Process using written code
~ libraries
(are either purchased / free)
Process Specifications Format
Process specifcations link a process to a data flow diagram,
and hence a data dictionary
Process Specifications Format (cont)
Includes:
• The process number
• The process name
• Uses prewritten code
• Process logic
description
• Description of what the
process accomplishes
• Logic method reference
• A list of input data flow
• Output data flows
• Type of process
• List any unresolved
issues
Process Specifications Format (cont)
Includes
• The pro
• The pro
itten code
ic
• Descript
process
od reference
• A list of
• Output
• Type of
resolved
Process Specifications Format (cont)
Number: match process ID
on data flow diagram
Name: the same with name
of process symbol
Description: brief description
of accomplishing
Input/Output:
- Using name found in data
flow diagram
- Name match with words in
data dictionary
Type: Online should have
ications Format (cont)
screen design; Manual
should have step-by-step
Subprogram: <if process
uses prewritten code>
Process Logic: business rules
in everyday language, not
computer language pseudo-
code
Refer to:
<if not enough room for
process logic>
Unresolved Issues: Issues of above
contents. These for next interview with
user/expert in team for clearance.
Writing Specifications
• Structured English
• Decision Table
• Decision Tree
Writing Specifications
• Structured English
• Decision Table
• Decision Tree
WRITING: Structured English
When?
• process logic involves formulas or iteration, or
• when structured decisions are not complex
WRITING: Structured English
WRITING: Structured English
Example 1
1. Divide into 4 type of logic
2. CAPITALIZE keywords
3. Indent blocks clearly
4. Underline words in data
dictionary
5. Clarify logic process,
specially in AND and OR
(avoiddoingincodingstage)
WRITING: Structured English
Example 1
WRITING: Structured English
Example 2
We process all our claims in this manner. First, we determine
whether the claimant has ever sent in a claim before; if not, we set
up a new record. The claim totals for the year are then updated.
Next, we determine if a claimant has policy A or policy B, which
differ in deductibles and copayments (the percentage of the claim
claimants pay themselves). For both policies, we check to see if the
deductible has been met ($100 for policy A and $50 for policy B). If
the deductible has not been met, we apply the claim to the
deductible. Another step adjusts for the copayment; we subtract the
percentage the claimant pays (40 percent for policy A and 60
percent for policy B) from the claim. Then we issue a check if there is
money coming to the claimant, print a summary of the transaction,
and update our accounts. We do this until all claims for that day are
processed.
WRITING: Structured English
Example 2
EXERCISE 1
Write Structured English
Clyde’s narrative of the reimbursement policies
“Our reimbursement policies depend on the situation.
Example 1
You see, first we determine if it is a local trip. If it is, we
only pay mileage of 18.5 cents a mile. If the trip was a
one-day trip, we pay mileage and then check the times
of departure and return. To be reimbursed for breakfast,
you must leave by 7:00 a.m., lunch by 11:00 a.m., and
have dinner by 5:00 p.m. To receive reimbursement for
breakfast, you must return later than 10:00 a.m., lunch
later than 2:00 p.m., and have dinner by 7:00 p.m. On a
trip lasting more than one day, we allow hotel, taxi, and
airfare, as well as meal allowances. The same times apply
for meal expenses.”
Tải về để xem bản đầy đủ
39 trang
25100
Free
Bạn đang xem 20 trang mẫu của tài liệu "Bài thuyết trình môn Phân tích & thiết kế hệ thống - Đề tài: Process specifications and structured decisions", để tải tài liệu gốc về máy hãy click vào nút Download ở trên
File đính kèm:
- bai_thuyet_trinh_mon_phan_tich_thiet_ke_he_thong_de_tai_proc.pptx
