Class Diagrams Tutorial.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

Welcome to WebCRD.
Chapter 11 Designing the User Interface
Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
09/04/2015Unit 2 (b) Back-Office processes Unit 2 Assessment Criteria (b) 10 marks.
e-DMAS Consumer Web Order Entry (WEBOE8) An Enhancement For iSeries 400 DMAS from  Copyright I/O International, 2003, 2004, 2005 Skip Intro.
Business Analysis & Data Design ITEC-630 Spring 2008
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
USDA Advantage!
Library Online Catalog Tutorial Pentagon Library Last Updated March 2008.
GSA eBuy Buyer’s Tutorial This basic tutorial will take buyers step by step through the RFQ process. The tutorial will also point out many of the exciting.
January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.
Together and UML Greg Johnson CSE 230 – Software Engineering Spring 2007.
Requirements Analysis 1 Use Cases -> Class Diagrams Moving from the user towards the system.
Using the Book Cart. Step 1: Saving items to book cart in 4 ways. +
Use Case Modelling.
Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.
UML exam advice. Minimal, yet sufficient UML course 80% of modeling can be done with 20% of the UML. Which 20% was that again? We’re supposed to be “Use.
Chapter 13: Designing the User Interface
BSC Food Distribution 8181 NW 36 Street, Suite 14-D Doral, FL Phone: Fax:
Online Book Shop Conceptualization Bookshop: Books, MusicCDs, Software
Object Oriented Software Development
Quiz 1. Who is the guru of Extreme Programming?
WNS1.com Online Training How to use the Western Nevada Supply online store and tools.
VA Advantage!
CSE 441: Systems Analysis & Design
CHAPTER 2. FUNDAMENTAL OF ENTITY RELATIONSHIP (ER)
Your Name Here See Page Notes for Info about Hyperlinks.
Internet Software Development Putting it all together Paul J Krause.
Intro: Use Case and Use Case Diagram Documentation.
1 1 User Manual Purchase and Order Tracking on the SKF Giftzone.
MARKETING PORTAL PRESENTED TO YOU BY CABLES TO GO.
GSA Federal Supply Service VITM Virtual IT Marketplace
Faculty of Computer & Information Software Engineering Third year
Figures from Chapter 4 Form Storyboarding Dirk Draheim, Gerald Weber Form-Oriented Analysis Springer, October 2004.
Faculty of Computer & Information
CSC 8560Fall 2000 Computer NetworksBhargavi Balasubramanian & Bob Viola Project 1 Description: E-Commerce Objective:Build a web storefront to sell videos.
Dental Patients Management System By Ray Info Solutions Mob: – Off:
1 אירוע אמאזון. 2 שלבי הפיתוח עם דיאגרמות UML 3 אמאזון תרשים תוכן.
The link to the Custom Point Login is:
Registering and Joining a Course. What do I need to register? All students need:  A student access code An access code looks like this: SMPLE – FRILL.
Chapter 9 Applying UML and Patterns -Craig Larman
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
MSF Design Example Conceptual Design Logical Design Physical Design.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
SYSTEMSDESIGNANALYSIS 1 Chapter 22 Object-Oriented Design Jerry Post Copyright © 1997.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
Customer Views Home Page Your AccountView CartHelp Search for in Top-level list of catalogs, which will include “bikes,” “bike parts,” “clothing,” and.
Scenario A scenario is a sequence of steps describing an interaction between a user and a system. Use case is a set of scenarios tied together by a common.
Online Catalog Tutorial. Introduction Welcome to the Online Catalog Tutorial. This is the place to find answers to all of your online shopping questions.
Revision.
Text Name School Name Rep name ISBN of bookstore bundle.
Navigation: If the tutorial opens up in your web browser, simply click your mouse or your space bar to advance to the next slide. Use.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 17 Object-Oriented Design and Modeling Using the UML.
OO DomainModeling With UML Class Diagrams and CRC Cards Chapter 6 Princess Nourah bint Abdulrahman University College of Computer and Information Sciences.
Navigation: If the tutorial opens up in your web browser, simply click your mouse to advance to the next slide. Use the “Backspace”
Complete Ordering System for Promotional Literature and Samples Quick Reference and Training Guide.
Identification of Classes. Object Oriented Analysis (OOA) OOA is process by which we identify classes that play role in achieving system goals & requirements.
Go to my.tfc.edu Once here, you will put in your TFC user name and password. You should have received an including your TFC login credentials. If.
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
Classes, Sequence Diagrams and Triangulation
Webapp Design with System Sequence Diagrams
B2C Online Store. B2C Online Store Group Members Introduction Name: Muhammad Gulfam VU ID: MC Program: MCS Supervisor: Muhammad Qamar Usman.
OO Domain Modeling With UML Class Diagrams and CRC Cards
Signing up or logging in to your user account:
Object-Oriented Software Engineering
MIS2502: Data Analytics Relational Data Modeling 2
Presentation transcript:

Class Diagrams Tutorial

Conceptual class diagram-Online Bookstore An Informal Description "The system is an online, web-based bookstore. The bookstore sells books, music CDs, and software. Typically, a customer first logs on to the system, entering a customer ID and password. The customer can then browse for items or search by keyword(title, Author , Publisher, ISBN). The customer puts some of the items into a "shopping cart" which keeps track of the desired items. When the customer is done shopping, he/she confirms the order, shipping address, and billing address. The bookstore system then issues a shipping order, bills the customer, and issues an electronic receipt. At the end of the transaction, the customer logs off."

Online Bookstore A Scenario User logs on. System displays welcome message and requests customer ID and password. User enters customer ID and password. System validates the ID and password. User searches for a items by browsing or keyword search System displays information about the title. User selects a title to buy System adds items to the customer's shopping cart [Repeat 5-8 until done] User is done with shopping System displays shopping cart, shipping address, and billing address User confirms order and payment method. System processes order, notifies warehouse for shipping, and issues an electronic receipt. User logs

Identify the classes Look for important nouns: Objects, people, organizations, places, events, concepts. From the given scenario OnLineBookstore, Customer, Book, MusicCD, Software, order, shoppingCart are the classes

Class Attributes Analyze the requirements to find the attributes of each class A Customer has a name, customerID, password, shippingAddress, and billingAddress. An Address has a street, city, state, country, and postalCode.

Relationships Analyze the requirements to find relationships between classes. Draw relationships as lines between class boxes. Annotate the relationships: How many OrderItems for each Order are possible? Use symbols to indicate the kind of relationship: Generic, aggregation (has-a or owns-a), inheritance (is-a). For generic relationships, use an arrowhead to indicate whether the relationship is navigable: Does the source object know about the destination object? After identifying candidate classes, see if there are any commonalities between them that might be an IS-A relationship. It may make sense to factor the common parts into a super class, and create an inheritance relationship:

Finding Relationships

Class diagram

Conceptual class diagram-Programming Language Based on the following description of part of the syntax of a programming language, construct a class diagram showing the structure of programs written in the language and show the types of associations between the classes. - A module consists of a collection of features. A feature can either be a variable, a routine or a nested module. Routines consist of a declaration part and a statement part. Features local to the routine can be declared in the declaration part, and the statement part consists of a non-empty sequence of statements. Statements can be loops, conditionals or assignments, and each assignment contains a reference to the variable which is being assigned to.

Identify the classes Feature Variable Routine Module DeclarationPart Statement Part Statement Loop Conditional Assignment

Solution Class diagram

Hospital Information System Informal Description "The system is a hospital information system. A hospital has doctors and patients. Each patient is assigned to one doctor, but a doctor can have any number of patients. Patients check in to the hospital and assigned a doctor if they don't already have one. While in the hospital, doctors record various observations about each patient at various times. Examples of observations are blood pressure and temperature. The hospital keeps track of all the observations for a given patient until they check out of the hospital."

Scenario Patient checks in to hospital. Hospital assigns doctor to the patient. The doctor records a blood pressure measurement for the patient. The doctor records a temperature for the patient. The doctor prescribes medicine for the patient's condition. The patient checks out of the hospital.