Presentation is loading. Please wait.

Presentation is loading. Please wait.

Information System Design IT60105

Published byPrimrose Farmer Modified over 9 years ago

Similar presentations

Presentation on theme: "Information System Design IT60105"— Presentation transcript:

1 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

2 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

3 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

4 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

5 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

6 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

7 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

8 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

9 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

10 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

11 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

12 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

13 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

14 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

15 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

Download ppt "Information System Design IT60105"

Similar presentations

Introduction to Object Orientation System Analysis and Design

Introduction to Object Orientation System Analysis and Design
ACM/JETT Workshop - August 4-5, 2005 1 04:Design of Classes using CRC cards.

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.

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

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.

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.

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.

SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.
Lecture 8 Electronic Commerce Modelling Techniques

Lecture 8 Electronic Commerce Modelling Techniques
Information System Design IT60105 Lecture 3 System Requirement Specification.

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.

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.

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

Lecture 9 Object-Oriented Analysis
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML

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.

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

Interaction Diagrams Activity Diagram State Machine Diagram
January 200491.3913 Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Recordkeeping & Accounting

Recordkeeping & Accounting
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements 2.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements 2.
1 Lab-02. 2 Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.

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) 

Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 

Similar presentations

Ads by Google