SWE 621: Software Modeling and Architectural Design. Lecture Notes on Software Design. Lecture 14 - Course Review

Transcription

1 SWE 6: and Architectural Design Lecture Notes on Design Lecture 4 - Course Review Hassan Gomaa Dept of Computer Science George Mason University it Fairfax, VA Copyright 0 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written permission of the author. This electronic course material may not be distributed by or posted on any other World Wide Web site without the prior written permission of the author. Copyright 0 Hassan Gomaa Overview Collaborative Object and architectural design method (COMET) Object Oriented Analysis and Design Method Uses UML (Unified Language) notation Standard approach for describing a software design COMET = UML + Method Provides steps and guidelines for and Design From Use Case Models to Architecture H. Gomaa, and Design: UML, Use Cases, Patterns, and Architectures, Cambridge University Press, February 0 Copyright 0 Hassan Gomaa

2 Figure. COMET software life cycle model User Requirements Analysis 4 Throwaway 3 Design 6 Construction 7 Integration 3 0 System Testing 4 Copyright 0 Hassan Gomaa 3 Object-Oriented Life Cycle Requirements Requirements Use Case Define software functional requirements in terms of use cases and actors Figure. Banking System use case model Withdraw Funds «include» Query Account «include» «include» Validate PIN ATM Transfer Funds Add Cash Startup Shutdown ATM Operator Copyright 0 Hassan Gomaa 4

3 Object-Oriented Life Cycle Analysis Analysis consists of Static Dynamic State Machine modeling using statecharts Object interaction modeling Figure. COMET object-oriented software life cycle model User Requirements Analysis 4 Throwaway 3 Design 6 Construction 7 Integration 3 0 System Testing 4 Copyright 0 Hassan Gomaa Copyright 006 H. Gomaa Object-Oriented Life Cycle Analysis Static Define structural relationships between classes Depict classes and their relationships on class diagrams Figure.3 Banking System class context diagram ATM «external I/O..* CardReader s To ATM Operator Outputs «external output To..* Outputs ReceiptPrinter ATM Keypad/Display To Interacts With..* Outputs To «external output..* CashDispenser «software system» Banking System Interacts With..* Operator Copyright 0 Hassan Gomaa 6

4 Object-Oriented Life Cycle Analysis Static Define structural relationships between classes Depict classes and their relationships on class diagrams Figure.4 Conceptual static model for Banking System entity classes Figure. Conceptual static model for Banking System Bank Manages Maintains..* Has..* Owns Provides..* Owns..* 0.. Access to..* *..* DebitCard Account, Modifies * ATMInfo * ATM Identifies Bank bankname: String bankaddress: String Account customername: String customerid: String customeraddress: String CheckingAccount DebitCard cardid: String PIN: String startdate: Date expirationdate: Date status:integer limit: Real total: Real SavingsAccount CardAccount Checking Account Savings Account Withdrawal Query Transfer PINValidation accountnumber: String balance: Real lastdepositamount: Real interest: Real 0 Copyright 0 Hassan Gomaa 7 Object-Oriented Life Cycle Analysis Dynamic Define statecharts for state dependent control objects Figure. Top level statechart for ATM Control Card Inserted / Get PIN Insufficient Cash / Closed Down Eject Entry / Display System Down After(Elapsed Time) [Closedown Requested] Closedown Startup Idle Entry / Display After(Elapsed Time)[Closedown not Requested] Welcome Processing Third Invalid, Stolen / Confiscate,Update Status Cancel / Eject, Display Cancel Terminating Transfer Selected / Request Transfer, Display Wait Query Selected / Request Query, Display Wait Processing Rejected / Eject, Display Apology Transfer Ok / Print Receipt, Update Status Query Ok / Print Receipt, Update Status Withdrawal Selected / Request Withdrawal, Display Wait Copyright 00 H. Gomaa Withdrawal Ok / Dispense Cash, Update Status fsm 3 Copyright 0 Hassan Gomaa

5 Object-Oriented Life Cycle Analysis Dynamic Defines how objects participate in use cases using communication diagrams or sequence diagrams Copyright 0 Hassan Gomaa Steps in Using COMET/UML Develop Requirements Model Develop Analysis Model 3 Develop Design Model Design Overall Architecture (Chapter, 3) Design Distributed Component-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Figure. COMET software life cycle model User Requirements Analysis 4 3 Throwaway Design 6 Construction 7 Integration 3 0 System Testing 4 Copyright 006 H. Gomaa Copyright 0 Hassan Gomaa 0 0

6 Object-Oriented Life Cycle Design Overall Architecture (Chapter, 3) Design Distributed ib t dcomponent-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Design Copyright 0 Hassan Gomaa Object-Oriented Life Cycle Design Overall Architecture (Chapter, 3) Design Distributed ib t dcomponent- based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Design Figure. Subsystem interfaces high level communication diagram for Banking System : ATM KeypadDisplay : Operator operator customer display Information operator Information cardreader «software system» : BankingSystem «external I/O : CardReader «client» «subsystem» : ATMClient printer Output cardreaderoutput ATM bankresponse dispenser Output «service» «subsystem» : BankingService «external output : ReceiptPrinter «external output : CardDispenser Copyright 0 Hassan Gomaa

7 Object-Oriented Life Cycle Design Overall Architecture (Chapter, 3) Design Distributed ib t dcomponent-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes Card Reader «event driven» (Chapter 4) «external I/O : CardReader Card Reader Develop Detailed Design Output Design Figure. Task architecture initial concurrent communication diagram for ATM Client subsystem «service» «subsystem» : BankingService ATM Bank s Responses «client» «subsystem» Dispenser : ATMClient «demand» Output «passive» «output» «output : CashDispenser : Cash Interface Dispenser Card Inserted, «event driven» Dispense Cash Card Ejected, Cash «I/O» (Cash Amount) Cash Card Confiscated Withdrawal : CardReader Amount Response Interface «data abstraction» Eject, «demand» : ATMCash Card Confiscate «state dependent control» Start Up, Cash Data : ATMControl Closedown Added Operator Events «event driven» Information «data ( «user abstraction» details) Display interaction» : ATMCard Prompts : Operator : Operator Interaction Operator Update Receipt Card Card Printed Status Data Request (Amount, Balance), Update Print PIN Status Receipt «event driven» : ATM KeypadDisplay Display Information «event driven» «user interaction» : Interaction Info., Selection Details «data abstraction» : ATM Data Request «demand» «output» : ReceiptPrinter Interface Printer Output «passive» «output : Receipt Printer Copyright 0 Hassan Gomaa 3 Object-Oriented Life Cycle Design Overall Architecture (Chapter, 3) Design Distributed ib t dcomponent-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Design Copyright 0 Hassan Gomaa 4

8 Object-Oriented Life Cycle Design Design Overall Architecture (Chapter, 3) Design Distributed ib t dcomponent-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Example of cooperating tasks using connectors Copyright 0 H. Gomaa Copyright 0 Hassan Gomaa Steps in Using COMET/UML Develop Requirements Model Develop Use Case Model (Chapter 6) Develop Analysis Model Develop static model of problem domain (Chapter 7) Structure system into objects (Chapter ) Develop statecharts for state dependent objects (Chapter 0) Develop object interaction diagrams for each use case (Chapter, ) 3 Develop Design Model Design Overall Architecture (Chapter, 3) Design Distributed Component-based Subsystems (Chapter 3,) Structure Subsystems into Concurrent Tasks (Chapter ) Design Information Hiding Classes (Chapter 4) Develop Detailed Design Copyright 0 Hassan Gomaa 6