1. Consider that you will be presenting for an internal review in your own consulting firm. We will critique your work and make suggestions for improvements. (Strongly) Suggested Components for Presentation 2 Quick summary of the business context (with numbers!), the business problem,and the proposed solution and benefits. Context diagram of proposed solution. Event Table. Must correspond to the context diagram and the Level 0. Level 0 DFD. Must correspond to the event table. Level 1 DFDs for the key events. Data Stores must correspond to ERD. ERD with attributes indicated (even if just listed to the side of entities). Tell us the extent to which you are automating versus reengineering. Hand out to the class: ERD; Level 0 DFD; Level 1 DFD for the most interesting events.

2. Data Modeling: Entity Relationship Diagrams Entities: things about which we store information (classes/types vs instances) Attributes: facts about properties or characteristics of an entity. Identifiers: unique identifiers of an instance of an entity Relationship: association between instances of one entity with instances of another entity. Multivalued attribute: attribute which can have one or more values for the same entity. Example: Employee may have more than one skill. How handle? (Repeated Groups?)

3. Data 1. identify the entities 2. identity the attributes for each entity 3. determine relationships (note notation differences with Watson) 4. refine entities to conform to normal form. Process: 1. Identify the events and triggers (level 0) 2. Break each event down into more detailed processes 3. Determine specific facts needed to carry out each processes 4. link processes, external entities and data stores with data flows Approach to design: Design Data and Process in Parallel.

4. Camp Snoopy: Mall of America Amusement Park Design a system that will allow Camp Snoopy to sell tickets to customers, and the tickets will have credits can be used over a long period of time. Customer information will be taken when the first ticket is purchased, and in general not after that. The ticket itself will only have a barcode identifier on it. Whenever a ride is taken, the attendant will scan the ticket with a barcode reader, the system will check and adjust credit levels for that ticket, and the particular ride taken by this customer will be recorded. Different rides require a different numbers of credits. Customers can find the balance on any ticket by having it scanned by multiple readers around the park for that purpose.