Complete Codegear tutorial on Use Case diagrams, including "More Details" and Self Test
Download and install Visual Paradigm UML Community (free download for non-commercial use) or use another UML tool with which you are familiar
Create a simple Use Case diagram for asking someone for change for a dollar bill
Exericse 2: Modeling logic
On page 142 of the Marakas text, there is a description of logic for determining discounts, penalties, and credit-worthiness at Flexible Products, Inc.
Carefully read the description on Marakas page 142, number 5. Be sure you understand the logic.
Use a word or text processor to create Structured English to describe the logic.
Use a word processor or spreadsheet program to describe the logic using a Descision Table.
Use any drawing tool you like to create a Decision Tree describing the logic.
Email the three files to the Instructor (krieg@wccnet.edu).
Choose any two of the following. Create a high-level Use Case Diagram for each of the two, including documentation.
Fire alarm system
ATM
Airport security
Automobile ignition system
E-commerce site
Exercise 4: NOMAS logical
information system
proposal
Use the information in NOMAS Memo 5 (emailed separately) to propose a logical system design for new NOMAS data operations.
Don't be distracted by management issues or processes for handling the business except as they impact the logical information model
Focus on data processing for these subsystems:
order acceptance
direct order fulfilment
retail sales
inventory
accounting
You will not be required to do a presentation or produce a report: only the following well-documented diagrams, which should be emailed to the instructor:
Detailed Use Case Diagrams for each of the systems listed above
Level 0, 1, and 2 Data Flow Diagrams encompassing the above systems
Entity-Relationship Diagrams (normalized) for the corporate database
Each team is to produce a complete set of diagrams; work should be divided among team members so that each individual produces at least one diagram, with the possible exception of the normalized ERD, which may be the product of two people working together.
Although team members are to produce their own diagrams (with the exception mentioned in the preceding item), each team should discuss and agree upon an overall strategy for NOMAS data processing. All diagrams from a team should reflect the same stretegy.
During Class 14 when these are due, there will be an informal discussion. Each person will be asked to state briefly what they found most challenging in this exercise. In addition, everybody will be asked to summarize briefly what they learned working on the NOMAS project.
