Contoh Pengembangan SIM

Project Management

Expectation Management Matrix

Initial Expectation

Adjusting Expectation

Changing Priorities

Problem Definition

Cause-Effect

Candidate System Matrix

Feasibility Matrix

Requirement Analysis

Data Flow

Process Logic Modeling

Process Logic Modeling Structured Procedure 1. For each CUSTOMER NUMBER in the data store CUSTOMERS: a. For each LOAN in the data store LOANS that matches the above CUSTOMER NUMBER: 1) Keep a running total of NUMBER OF LOANS for the CUSTOMER NUMBER. 2) Keep a running total of the ORIGINAL LOAN PRINCIPAL for the CUSTOMER NUMBER. 3) Keep a running total of CURRENT LOAN BALANCE for the CUSTOMER NUMBER. 4) Keep a running total of AMOUNTS PAST DUE for the CUSTOMER NUMBER. b. If the TOTAL AMOUNTS PAST DUE for the CUSTOMER NUMBER is greater than $100.00 then: 1) Write the CUSTOMER NUMBER and all their data attributes as described in the data flow LOANS AT RISK. Else 1) Exclude the CUSTOMER NUMBER and data from the data flow LOANS AT RISK.

Overview Diagram Overview Diagram

Create-Read-Update-Delete MAtrix

Association Matrix

Context Diagram

Decomposition Diagram

Data Flow Diagram

Detailed Data Flow Diagram

Primitive Data Flow Diagram

Entering a Data Flow Using a CASE Tool

Entering an Elementary Process Using a CASE Tool

Entity Relationship

Data Modeling Purpose Discover system entities Discover entity keys Discover entity subsetting criteria Discover attributes and domains Discover security and control needs Discover data timing needs Discover generalization hierarchies Discover relationships? Discover cardinalities Candidate Questions What are the subjects of the business? What unique characteristic (or characteristics) distinguishes an instance of each subject from other instances of the same subject? Are there any characteristics of a subject that divide all instances of the subject into useful subsets? What characteristics describe each subject? Are there any restrictions on who can see or use the data? How often does the data change? Are all instances of each subject the same? What events occur that imply associations between subjects? Is each business activity or event handled the same way, or are there special circumstances?

Entity Discovery Entity Name Agreement Member Member order Transaction Product Promotion Business Definition A contract whereby a member agrees to purchase a certain number of products within a certain time. After fulfilling that agreement, the member becomes eligible for bonus credits that are redeemable for free or discounted products. An active member of one or more clubs. Note: A target system objective is to re-enroll inactive members as opposed to deleting them. An order generated for a member as part of a monthly promotion, or an order initiated by a member. Note: The current system only supports orders generated from promotions; however, customer initiated orders have been given a high priority as an added option in the proposed system. A business event to which the Member Services System must respond. An inventoried product available for promotion and sale to members. Note: System improvement objectives include (1) compatibility with new bar code system being developed for the warehouse, and (2) adaptability to a rapidly changing mix of products. A monthly or quarterly event whereby special product offerings are made available to members.

Context Entity Relationship Diagram

Key-based Entity Relationship Diagram

Generalization on Entity Relationship Diagram

Detailed Entity Relationship Diagram

Normalization on Entity Relationship Diagram

Object Oriented

Use Case Diagram

Use Case Narrative

Use Case Dependency Diagram

Revised Use Case Diagram

Highlighted Use Case Narrative DESCRIPTION: PRE-CONDITION: TRIGGER: This use case describes the event of a member submitting a new order for SoundStage products via the world wide web. The member selects the items they wish to purchase. Once they have completed their shopping, the member s demographic information as well as their account standing will be validated. Once the products are verified as being in stock, a packing order is sent to the distribution center for them to prepare the shipment. For any product not in stock, a back order is created. On completion, the member will be sent an order confirmation. The individual submitting the order must be an active club member. The member must login in to the system (provide identification) to enter an order. This use case is initiated when the member selects the option to enter a new order. TYPICAL COURSE Actor Action System Response OF EVENTS: Step 1: The member requests the option to enter a new order. Step 3: The Member browses the available items and selects the ones they wish to purchase along with the quantity. Step 5: The member verifies demographic information (shipping and billing addresses). If no changes are necessary they respond accordingly (to continue). Step 7: The member verifies the order. If no changes are necessary they respond accordingly (to continue). Step 2: The system responds by displaying the catalogue of the SoundStage products. Step 4: Once the member has completed their selections the system retrieves from file and presents the member s demographic information (shipping and billing addresses). Step 6: For each product ordered, the system verifies the product availability and determines an expected ship date, determines the price to be charged to the member, and determines the cost of the total order. If an item is not immediately available it indicates that the product is backordered or that it has not been released for shipping (for pre-orders). If an item is no longer available that is indicated also. The system then displays a summary of the order to the member for verification. Step 8: The system checks the status of the member s account. If satisfactory, the system prompts the member to select the desired payment option (to be billed later or pay immediately with a credit card).

Potential Object List

Proposed Object List

Object Association Matrix

Generalization/Specialization Hierarchies

Class Responsibility Collaboration Card

Class Diagram

Statechart Diagram

Sequence Diagram

Activity Diagram

Interface, Control & Entity Object

Ideal Model Object Diagram

Component Diagram

Deployment Diagram

ANY QUESTION?