Information System Design IT60105

Slides:



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

ACM/JETT Workshop - August 4-5, :Design of Classes using CRC cards.
GCSE ICT By the end of this session, you will be able to: Explain main features of ATM machines Identify features of credit cards, debit cards, smart cards.
Chapter 4: Requirements Engineering
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 3 - Software Systems and Requirements.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.
Lecture 8 Electronic Commerce Modelling Techniques
Information System Design IT60105 Lecture 3 System Requirement Specification.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
1 Classes. 2 Finding classes w Choosing classes is first step in defining essence of problem w If you can recognize an abstraction, you’ve found a candidate.
Lecture 9 Object-Oriented Analysis
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML
ATM User Interface Design. Requirements A bank customer is able to access his or her account using an automatic teller machine. To be able to use an ATM.
Interaction Diagrams Activity Diagram State Machine Diagram
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Recordkeeping & Accounting
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements 2.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
(Usually have to be 18 years old to open & get ATM or debit card)
2013.  Reconcile your checking account  Create bank reconciliation reports  Find errors during reconciliation  Correct errors found during reconciliation.
3. 18 Methods of making and receiving payments Methods of making and receiving payments Banks and bank accounts  All businesses have bank accounts.
Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.
Object-oriented Design CSCI 5801: Software Engineering.
Merijn Benjamin Christina
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
Part 2: Design Methodology Object-Oriented Modeling and Design
CS212: Object Oriented Analysis and Design Lecture 4: Objects and Classes - I.
CS 160: Software Engineering September 10 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
Faculty of Computer & Information Software Engineering Third year
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
ICT and Banks Banks use mainframe computers to maintain customer accounts. They store a record of each customer’s withdrawals and deposits. Each bank mainframe.
MCS 270 Spring 2014 Object-Oriented Software Development.
Object oriented classification Classification is the process of checking to see if an object belongs to a category or a class, is regarded as a basic attribute.
MODULE 3 Analysis and system design
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
January Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, Implement the ProductSpecification and Payment classes in any OO.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
ATM Adv. SW Engineering
Computerization of a bank  Automatic Teller Machines  Net Banking  Phone Banking  Savings/ Current/ Fixed Deposit/ Recurring Deposit  Loans against.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
GOALS BUSINESS MATH© Thomson/South-WesternLesson 3.2Slide 1 3.2Electronic Banking Record electronic banking transactions Find account balance when banking.
Building: Knowledge, Security, Confidence Check It Out FDIC Money Smart for Young Adults.
Learning Intentions Explain what an ATM is and the facilities offered Identify the stages of withdrawing cash from an ATM List the advantages and disadvantages.
1 LAB What is Collaboration diagram? 4 Collaboration diagrams illustrate the interaction between the objects, using static spatial structure. 4.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Dr D. Greer, Queens University Belfast Four 1 Software Engineering Chapter 4: Software Design Unified Modelling Language.
Identification of Classes. Object Oriented Analysis (OOA) OOA is process by which we identify classes that play role in achieving system goals & requirements.
CHAPTER Section 14.1 Recordkeeping Section 14.2 Accounting Systems Recordkeeping & Accounting.
Bank Reconciliation Chapter 4. PAGE REF #CHAPTER 4: Bank Reconciliation SLIDE # 2 Objectives Reconcile your checking Create bank reconciliation reports.
Requirements Document for the Banking System
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
1 Case Study and Use Cases for Case Study Lecture # 28.
IT’S ALL ABOUT THE INTERFACES Jeffrey Eyster Indianapolis, IN.
Teaching Innovation - Entrepreneurial - Global
CMPE 280 Web UI Design and Development August 29 Class Meeting
Structured Analysis and Design Technique
ATM OO Design and Implementation Case Study
Dynamic Modeling of Banking System Case Study - I
Credit, Debit, and ATM Cards
Object-Oriented Static Modeling of the Banking System - I
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Real-Time Structured Analysis and Design Technique (RSTAD)
Uses of Telecommunications & ICT
Presentation transcript:

Information System Design IT60105 Lecture #11: IT60105 13/9/2007 Information System Design IT60105 Lecture 12 Class Modeling 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Lecture #12 Domain class model Finding classes Keeping the right classes Finding associations Keeping the right associations Finding attributes Keeping the right attributes Finding methods Grouping classes into packages 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Case Study: ATM System 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Problem Statement Lecture #11: IT60105 13/9/2007 ATM System: Problem Statement Design the software to support a computerized banking network including both human cashiers and automatic teller machines (ATMs) to be shared by a consortium of banks. Each bank provides its own computer to maintain its own accounts and process transactions against them. Cashier stations are owned by individual banks and communicate directly with their own bank’s computers. Human cashiers enter account and transaction data. Automatic teller machines communicate with a central computer that clears transactions with the appropriate banks. An automatic teller machine accepts a cash card, interacts with the user, communicates with the central system to carry out the transaction, dispenses cash, and prints receipts. The system requires appropriate recordkeeping and security provisions. The system must handle concurrent accesses to the same account correctly. The banks will provide their own software for their own computers; you are to design the software for the ATMs and the network. The cost of the shared system will be apportioned to the banks according to the number of customers with cash cards. 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Finding Classes To find the relevant classes for objects from the problem domain Not all classes are explicit in the problem statement Some are implicit in the application domain or general knowledge We can find many classes by considering nouns 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Find Classes Lecture #11: IT60105 13/9/2007 ATM System: Find Classes Design the software to support a computerized banking network including both human cashiers and automatic teller machines (ATMs) to be shared by a consortium of banks. Each bank provides its own computer to maintain its own accounts and process transactions against them. Cashier stations are owned by individual banks and communicate directly with their own bank’s computers. Human cashiers enter account data and transaction data. Automatic teller machines communicate with a central computer that clears transactions with the appropriate banks. An automatic teller machine accepts a cash card, interacts with the user, communicates with the central system to carry out the transaction, dispenses cash, and prints receipts. The system requires appropriate recordkeeping and security provisions. The system must handle concurrent accesses to the same account correctly. The banks will provide their own software for their own computers; you are to design the software for the ATMs and the network. The cost of the shared system will be apportioned to the banks according to the number of customers with cash cards. 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Bad Classes Lecture #11: IT60105 13/9/2007 ATM System: Bad Classes 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Good Classes Lecture #11: IT60105 13/9/2007 ATM System: Good Classes 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Finding Associations Apply all or appropriates Find Verb phases Implicit verb phases Knowledge of problem domain 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Find Associations Lecture #11: IT60105 13/9/2007 ATM System: Find Associations Verb phases Banking Network includes cashier stations and ATMs Consortium Shares ATMs Bank provides bank computer Bank computer maintains accounts Bank computer process transaction against account Bank owns cashier Station Cashier station communicates with bank computer Cashier enters transaction for account ATMs communicate with central computer about transaction Central computer clears transaction with bank ATM accepts cash card ATM interacts with user ATM dispense cash ATM prints receipts System handles concurrent access Bank provide software Cost apportioned to banks 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Find Associations Lecture #11: IT60105 13/9/2007 ATM System: Find Associations Implicit verb phases Consortium consists of banks Bank holds account Consortium owns central computer System provides recordkeeping System provides security Customers have cash cards Knowledge of problem domain Cash card accesses accounts Bank employs cashiers 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

ATM System: Class Diagram Lecture #11: IT60105 13/9/2007 ATM System: Class Diagram 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Finding Attributes Consider attributes directly relevant to the application Get the most important attributes first Add fine details later Avoids attributes those are solely for implementation Be sure to give each attribute a meaning full name 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Keeping Right Attributes Lecture #11: IT60105 13/9/2007 Keeping Right Attributes Eliminate unnecessary and incorrect attributes with the following criteria Objects Careful about right objects as attributes in the class Qualifiers Which actually matters Names A name is an attribute when its use does not depends on context 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur

Information System Design IT60105, Autumn 2007 Lecture #11: IT60105 13/9/2007 Find Methods Decide the operations require to manipulate the members within and other objects Use other models as well Sequence diagrams Statechart diagrams 13 September, 2007 Information System Design IT60105, Autumn 2007 D. Samanta, SIT, IIT Kharagpur