DOC PREVIEW
Toronto CSC 340 - Interface Objects

This preview shows page 1-2-3 out of 10 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 1XXIV. Interface ObjectsXXIV. Interface ObjectsThree-Tier ArchitecturesThe Presentation layerSequence Diagrams for User Interface ClassesPrototyping the User InterfaceUser Interface Class and Package DiagramsModel-View-Controller Architecture RevisitedStatechart Diagrams for Dialogue Dynamics© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 2The Three-Tier Architecture,The Three-Tier Architecture,RevisitedRevisited User interfaces for an information system are part of thepresentation layer in a three-tier architecture. The three-tier architecture separates cleanly userinterfaces from application logic/business classes andfrom data storage components of the system. Business classes “know nothing” about how their (business)objects will be presented to the users.© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 3Check Campaign BudgetCheck Campaign Budget© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 4Add a Dialog Box ObjectAdd a Dialog Box Object© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 5Prototyping the DialoguePrototyping the Dialogue Prototyping can be used to determine what the interface willlook like.© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 6Class Diagram for Interface ClassesClass Diagram for Interface ClassesComposition specifiesthat a dialogue box ismade up of othercomponentsCBWindow Dialog Button Choice Label TextField 21 21 11 21© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 7Another Class DiagramAnother Class DiagramCBWindow can alsobe represented as aclass with thegraphical componentsthat make it up asattributes.CBWindowclientLabelcampaignLabelbudgetLabelcheckButtoncloseButtonbudgetTextFieldclient ChoicecampaignChoice© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 8Packages for Interface ClassesPackages for Interface Classes Package diagrams show the dependencies among interfaceclasses in different packages.© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 9Revised Class Diagram Composition showsthat a dialogue boxis made up of othercomponents fromthe AWT package.CBWindow AWT::Dialog AWT::Button AWT::Choice AWT::Label AWT::TextField 31 21 11 21 (Java)AbstractWindowing Toolkit© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 10Prototyping the Dialogue There are several ways for entering the Client and Campaignname: Use a separate look-up window for each class; Allow the user to enter a part of a name, then have thesystem return a list of close matches; Use a tree data structure to show clients and campaigns in atree-like hierarchy.© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 11 Separatewindowfor look-upAlternative Dialogue Prototypes© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 12Alternative Dialogue Prototypes:Alternative Dialogue Prototypes: Three View Control Three View Control© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 13Updating the Sequence Diagram Choice:Client (CL)Campaign (CA)Lookup© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 14Updating the Class Diagram© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 15Model-View-Controller:Model :View User Event :Controller 1: Broadcast 5: Ask What Has Changed 6: Notify Change 2: Update self 3: Notify Change 4: Update Presentation 7: Request Model data© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 16:ActionListener any:Class User Event :Component 1: ActionPerformed (ActionEvent e) 3: [Event of Interest] Notify Class of Event 2: Inspect Event 4: Update Self The Java ActionListener Approach© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 17Modelling the Dynamic Behaviourof the Interface The sequence diagrams show the sequential view of the userworking through the fields on the screen from top to bottom. But in GUI interfaces the user can click on the interface objectout of sequence. What happens if the user clicks on the Check button before aclient and a campaign have been selected? To specify what happens, we can use Statechart diagrams!© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 18Clientlistbox,CampaignListbox,Cursor© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 19CheckButton, BudgetTextbox© 2002 Jaelson Castro and John MylopoulosCSC340Information Systems Analysis and DesignObject-Oriented Interface Design -- 20Additional Readings Bennett S, Farmer R and McRobb S (1999) Object-OrientedSystems Analysis and Design Using UML. McGraw-Hill.Chapter 16 - Designing interface objects. Larman C (1998) Applying UML and Patterns. Prentice-Hall.Chapter 22 - Issues in System


View Full Document

Toronto CSC 340 - Interface Objects

Documents in this Course
Scoping

Scoping

10 pages

Load more
Download Interface Objects
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Interface Objects and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Interface Objects 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?