350 Part III • Acquiring Information Systems
InvoiceNumber VendorID
Contact Name
Contact Title
Vendor Phone
Vendor Fax
PONumber Vendor Name
PayablesStatus
InvoiceDate
Shipped Via
Shipping Cost
NEW
NEW
REMOVE
Click NEW button to add a new Detail, Click in Detail and REMOVE button to delete Detail SUBMIT FORM
CLEAR FORM
St/Province
City
Postal Code
Country
E-Mail
* Address
*
*
mm/dd/yyyy
Shipped To
Vendor Invoice Form * Indicates Required Field For existing Invoice, enter InvoiceNumber
For existing Vendor, enter VendorID
NEW
InvoiceDetailID *ItemNumber * Quantity * PricePerUnit PaymentTerms Discount
FIGURE 8.18 Vendor Invoice Maintenance Form
Check Register
Account Number 2936
482441
482442
482443
482444
482445
482446
482447
482448
8/3/10
8/3/10
8/3/10
8/3/10
8/4/10
8/4/10
8/4/10
8/4/10
C1523
1398752
E17982
175632
R1689
M568930
897532
C1527
A00702
C00321
E00052
C00323
B00824
B00825
A00704
D00376
7/20/10
7/24/10
7/23/10
7/24/10
7/27/10
7/28/10
7/28/10
7/30/10
TOTAL
TOTAL
178
52
104
89
13
97
152
178
1,925.50
408.92
1,500.00
10,328.72
14,163.14
505.17
12,327.18
765.15
1,534.83
15,132.33
29,295.47
CheckNumber CheckDate InvoiceNumber VendorID PONumber InvoiceDate InvoiceAmount PaidAmount
1,925.50
408.92
1,200.00
10,328.72
13,863.14
505.17
11,094.46
765.15
1,534.83
13,899.61
MONTHLY TOTAL 27,762.75
FIGURE 8.19 Check Register Report Layout with Sample Data
layouts. In the Logical To-Be modeling, the need for an
interface, as well as its frequency of use and information
content, was identified. In the Physical To-Be modeling,
the specific interface design is addressed.
Figures 8.18 and 8.19 show draft layouts for an input
screen and a report for the accounts payable system.
Layouts such as these are often developed in close consul-
tation between systems designers and the end users who
will be directly working with a computer display. Today’s
system building tools allow for easy prototyping of such
interfaces by end users before the system itself is actually
built. Systems today are also frequently built with some
flexibility, so that the user can directly control design
options for reports and data entry forms in order to adapt to
changing needs of the business or the user of the report.
You have now considered some of the techniques
used to capture system needs, document business rules,
and uncover hidden dependencies and relationships as part