1. 1 SYSTEMS DESIGN Pertemuan 13 s.d 20 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006

2. 2 Models and Techniques Systems design –UML class diagram –Form layout –Input controls –Report layout –Use case diagram –Use case descriptions

3. 3 UML CLASS DIAGRAM A UML class diagram can be used to document: Tables in an AIS Relationships between tables Attributes of tables

4. 4 Four basic steps need to be taken to create a UML class diagram: Place the required transaction tables (files) on the UML class diagram Place the required master tables (files) on the UML class diagram Determine the required relationship between the tables Determine the required attributes

5. 5 Four guidelines for identifying relevant events for data design: Determine the events in the process Exclude events that do not need to be recorded in the computer system Exclude query & reporting events because the involve using data that have already been recorded in the AIS Exclude maintenance events

6. 6 Three important concepts for refining the initial design developed from event analysis: Primary keys Linking attributes Relationship cardinalities Attributes & Relationships

7. 7 FORM LAYOUT Three relationships between tables & forms are possible: One form for recording data in one table One form for recording data in two or more tables Two or more forms for recording data in one table

8. 8 Data can be entered in a form in the following four ways: An internal agent types in the data An internal agent selects data to be entered using a look up table, radio button or check box An internal agent scans the bar code of a product or the identification card of a customer A user enters the data using a form at the company’s Web site

9. 9 INPUT CONTROL Input controls are used to improve the accuracy and validity of data entry. The following ten controls can be built into an entry form to improve accuracy & efficiency of data entry: Look up feature Scanning Record checking Confirmation Referential integrity

10. 10 Format checks Validation rules Defaults Computer generated values Prompt user to accepts/reject data

11. 11 REPORT LAYOUT QUERY : An important element of relational databases. Queries are specified by stating: The attributes (fields) that are desired The tables that store the desired information The criteria & conditions used for deciding what records to retrieve

12. 12 TYPES OF REPORTS A report is a formatted presentation of information. Four types of report formats were: Simple lists Grouped detail reports Group summary reports Single entity reports

13. 13 Simple lists A simple event list or reference list (list of sales transaction, etc) Grouped detail reports A grouped detail status report or a grouped event detail report (list of sales trans. That are grouped by type of product sold, etc) Group summary reports Reports that summarize event data for a group of related records over a designated period (summary sales, etc). Single entity reports A report that provides details about only one entity (sales invoice, etc)

14. 14 Report layout : Report header (Name of report & company, date of report, number of pages). Page header Page footer (page number) Report detail Report footer (grand total)

15. 15 USE CASE DIAGRAM Use case diagram is A list of use cases that occur in an application and that indicate the actor responsible for each use case. In this session, use case diagram is design for the future.

16. 16 USE CASE DESCRIPTION Description of use case for the design application.