L03-S1 Stable Analysis Patterns 2003 SJSU -- CmpE Software Pattens Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.

Slides:



Advertisements
Similar presentations
L3-1-S1 OO Concepts © M.E. Fayad SJSU -- CMPE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
Advertisements

L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
L3-5c-S1 Object Diagrams © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department,
L16-S1 Object Diagrams 2003 SJSU -- CmpE Software Patterns Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
L28-S1 Interaction Diagrams 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
L19-S1 More on Class Diagrams 2003 SJSU -- CmpE Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
 Fayad SJSU – CmpE Software Engineering Management Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
L21-S1 Model-Based Arch SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
L3-5d-S1 Class Diagrams © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
L26-S1 Interactions 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
© M.E. Fayad SJSU -- CmpE Database Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San José.
SJSU -- CmpE © Dr. M. E. Fayad Database Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
L5-S1 Class Diagrams 2003 SJSU -- CmpE Software Patterns Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
L8-S1 CRC Cards 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
© M.E. Fayad SJSU -- CmpE Analysis Heuristics Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
Application Architectures Vijayan Sugumaran Department of DIS Oakland University.
© M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
L04-S1 Stable Design Patterns 2003 SJSU -- CmpE Software Patterns Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
L3-6b-S1 Sequence Diagrams © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
L6-1-S1Design Heuristics - 1 © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
The chapter will address the following questions:
Web application architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Lynn Grande COT6930 – Semantic Web Fall  The real-time adjustment of spectrum utilization in response to changing circumstances and objectives.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
MVC pattern and implementation in java
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
An Introduction to Software Architecture
Model-View-Controller Ku-Yaw Chang Assistant Professor, Department of Computer Science and Information Engineering Da-Yeh University.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
L4-S1 Modeling Concepts 2003 SJSU -- CMPE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
CHAPTER 5: MULTIMEDIA DATABASE MANAGEMENT SYSTEM ARCHITECTURE TOPIC : 5.1 DISTRIBUTED MULTIMEDIA DATABASE MANAGEMENT SYSTEM ARCHITECTURE GROUP MEMBERS:
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
1 CMPT 275 High Level Design Phase Modularization.
Design Reuse Earlier we have covered the re-usable Architectural Styles as design patterns for High-Level Design. At mid-level and low-level, design patterns.
Fall 2002 SJSU -- CMPE Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department – RM# College of Engineering San José.
L3-S1Analysis Heuristics 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
L1-S1 Infinite R-DB 2003 SJSU -- CmpE Database Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
Web Engineering CS-4513 Prepared By: Junaid Hassan Lecturer at UOS M.B.Din Campus
Advanced Object-Oriented Analysis & Design
Software Design and Architecture
Enterprise Application Architecture
Software Patterns Dr. M.E. Fayad, Professor
Component-Based & Software Reuse
Software System Engineering
Object-Oriented Analysis & Design
Advanced Object-Oriented Analysis & Design
Analysis models and design models
An Introduction to Software Architecture
Software System Engineering
Software System Engineering
Advanced Object-Oriented Analysis & Design
Object-Oriented Analysis & Design
Advanced Object-Oriented Analysis & Design
Component Based & Software Reuse
Advanced Object-Oriented Analysis & Design
Software System Engineering
Presentation transcript:

L03-S1 Stable Analysis Patterns 2003 SJSU -- CmpE Software Pattens Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San José State University One Washington Square San José, CA

L03-S2 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 2 Lesson 3: Stable Analysis Patterns

L03-S3 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Lesson Objectives 3 Explore Stable Analysis Patterns Examine Stable Analysis Patterns Discuss the following Stable Analysis Patterns: î Negotiation î Model-View-Mapping (MVM) î Searching

L03-S4 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 4 The concept of extracting patterns using software stability concepts Problem FIRST ABSTRACTION: Apply SSM concepts Define EBTs, BOs, and IOs Create SSM for the problem SECOND ABSTRACTION: Model each EBT using SSM concepts Build natural domain Stable Analysis Pattern

L03-S5 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Timeless Notion Pattern Generality: Generality Patterns Usability and Reusability Patterns Scalability Patterns Presentation of the Core Knowledge Patterns One Presentation of the Problem Space Patterns Configurability and Re-Configurability Patterns Adaptability Patterns Extensibility Patterns Accessibility Patterns Integratability Patterns 5 Stable Analysis Patterns’ Properties

L03-S6 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Contribute to Stable Architectures Aid True Problem Understanding Provide True Problem Modeling Enhance Team Dynamic 9 Stable Analysis Patterns Advantages

L03-S7 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad  Negotiation is a general concept that has many applications in various contexts.  In our every day life, there are various situations where negotiation usually takes place. For instance, buying or selling properties usually involves some sort of negotiation (e.g. buying or selling a home or a car).  In addition, negotiation can be used for solving social and political conflicts. 6 Negotiation Analysis Pattern (1)

L03-S8 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad  In software systems, Negotiation also appears frequently in the development of different applications.  For instance, developing software for online auctions and shopping might involve the negotiation of the price and/or the negotiation of different product aspects.  More technically, negotiation becomes an essential part in the development of next generation Web-based devices and appliances. 7 Negotiation Analysis Pattern (2)

L03-S9 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Today, devices that need to access the Web diverge greatly in their capabilities, making it highly desirable for the same resource to be available in several different representations (different languages for example). Negotiation algorithms play a fundamental role in aiding servers to decide which representation of a document a device should be given. In this case, the browser (or the client agent) will indicate its preferences by including a header in the request. 8 Negotiation Analysis Pattern (3)

L03-S10 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad  Pattern Name: Negotiation  Problem : How does one build a negotiation model that can be used to model the negotiation problem in any application? 10 Negotiation Analysis Pattern (4)

L03-S11 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad  Negotiation spans many contexts that are completely different in their natures.  The Negotiation process can take place between two or more persons, between persons and organizations, or between two non-human entities; in each case, the negotiator structure is completely different. How can we handle these different structures using a single model? 11 Forces (1)

L03-S12 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad The Negotiation entity can be an organization consisting of many persons, each having a role in the negotiation process. For instance, there can be one individual who is responsible for negotiating financial issues, another who is responsible for negotiating issues related to management, and so on. Therefore, our pattern should be flexible enough to handle different negotiator structures. 12 Forces (2)

L03-S13 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Negotiation can be conducted through one or more media either simultaneously or consecutively; thus, the pattern should handle the use of multiple media. Negotiation can be performed on one or more affairs at the same time. For instance, negotiation that takes place in the buying and selling context usually involves more than one subject to be negotiated. For example, in buying a car, one can negotiate the price, the warranty, and so on. Therefore, the pattern should be flexible enough to handle such situations. 13 Forces (3)

L03-S14 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad  The ultimate goal of any negotiation is to reach an agreement between the negotiators. However, the nature of this agreement varies tremendously from one application to another and from one context to another. An agreement that might be reached while negotiating a political conflict is completely different from that reached while buying a car. Therefore, the pattern should be able to handle these wide variations. 14 Forces (4)

L03-S15 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 15 Pattern Structure and Participants

L03-S16 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 16 CRC Cards (1) AnyNegotiation (Negotiation Descriptor) ResponsibilityCollaboration ClientsServer Describes the negotiation rules and regulations to the negotiating parties. AnyAgreement AnyParty AnyMediaAnyContext defineRules() AnyParty (Negotiation handler) ResponsibilityCollaboration Performs and finalizes the negotiation. ClientsServer AnyNegotiation AnyAgreement negotiate() approve() agree()

L03-S17 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 17 CRC Cards (2) AnyAgreement (Agreement) ResponsibilityCollaboration Describes agreement terms and conditions. ClientsServer AnyNegotiation AnyParty option()sign() execute() insert-option() Media (Connector) ResponsibilityCollaboration Communicates negotiation issues between negotiators. ClientsServer AnyNegotiation connect Parties() display() illustrate()

L03-S18 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 18 CRC Cards (3) Context (Motivator) ResponsibilityCollaboration Defines the reason of the negotiation process. ClientsServer AnyNegotiation defineBoundary() contextLimit()

L03-S19 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad STABLE MODEL-VIEW MAPPING PATTERN (MVM) 19

L03-S20 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Problem Overview Solution Requirements Current Solutions – Overview Current Solutions- Limitations Proposed Solution Stable Model-View Mapping [MVM] Pattern Stable MVM- Second Abstraction Level Stable MVM Pattern Instantiation Applicability Examples 20 Outline

L03-S21 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Today, very heterogeneous devices are required to access the same applications. PCs, PDAs, WAP phones, and interactive TVs, each has its own limitations and capabilities. Generating different version of the same application is impractical solution. [Cost, management, time,etc.] 21 Problem Overview (1)

L03-S22 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Problem Overview (2) Application 1 The Internet Wireless Network Server View 1 View 2 View 4 View 6View 5 View 3 Different views Problem: How to map models to different views!

L03-S23 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Successful applications will be accessible from several devices. Complex applications should be built as a composite of multiple models, not as a single complex model. Therefore, the solution should deal with the situation of having multiple models within the applications. 23 Solution Requirements (1)

L03-S24 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Sometimes the required view is constructed from the isolation of different parts from several models within the application. Mapping mechanisms are not predefined. The pattern needs to be abstract and not tied to any specific technology. 24 Solution Requirements (2)

L03-S25 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Developers would prefer a solution that separates the presentation from the application logic. One common approach that has been suggested is to use the Model-View-Control (MVC) framework to address some of issues regarding multi-device interfaces. [For example: San Francisco, and Java platform for wireless Applications: J2EE and J2ME]. Others approaches propose the use of different design patterns such as: Pipe and Filter patterns. 25 Current Solutions- Overview

L03-S26 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad None of the current solutions consider the situation of having multiple models within the application. Therefore, they do not consider the composition of multiple models in a single view and vise versa. None of them have addressed the way by which an arbitrary numbers of views can be generated from a single abstract model. All existing solutions assume a predefined set of views associated with a single model 26 Current Solutions- Limitations

L03-S27 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad We propose the Stable Model-View Mapping (MVM) as a solution to the mapping problem. the Stable MVM is a collection of patterns that deal with the problem of mapping an abstract model to an abstract view. The pattern handles the situation of having more than one model within the same application. The pattern is general enough to to deal with mapping problem for different devices with different capabilities. 27 Proposed Solution (1)

L03-S28 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad No predefined models and predefined views Mapping of Passive Models, such as relations in RDB and Live Models, such as return of playMovie(). The pattern is applicable for multiple purposes, such scalability, simplicity, viewing, fitting, editing, etc.. The pattern provides a base for building multiple applications. 28 Proposed Solution (2)

L03-S29 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Pattern Structure

L03-S30 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad The participants of the Stable MVM pattern are divided into two kinds: Classes and Patterns. Classes Applicability. Describes the application and the purpose for which mapping is needed. Patterns AnyModel. Describes the models within the application. The model is a representation of the data within the application. 30 Participants (1)

L03-S31 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad AnyView. Represents the view of a collection of data (the model). AnyParty. Represents both the modeler and the viewer. The modeler is responsible for building the data models in the appropriate abstract level. The viewer requests the model and the mapped view of that model. AnyMedia. Defines the media upon which the models and views are mapped and transmitted. It also represents the media by which the views are to be displayed (Phone, PCs, etc.) 31 Participants (2)

L03-S32 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Mapping. Defines the mapping rules between the models and their views. It also determines how this mapping will be performed. Searching. Searches AnyMedia for the requested application, model, or view. AnyApplication. Represents the application that is requested by AnyParty. 32 Participants (3)

L03-S33 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 2 nd Level Of Abstraction How to build a model that can be used to present any media in any application? 33

L03-S34 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Weather Application The weather application provides several services, such as: the weather for all countries and their cities all over the world, the weather forecast for the next few days, satellite photos, current forecast on video, etc. In this application, the user wants to view the weather on different devices with different capabilities. weather applications is developed in terms of smaller models, since having one model that deals with all of these features will be hard to manage and adapt for different devices. Applicability with Illustrated Example 34

L03-S35 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Weather Application (1) Weather Application Weather information Warning reports Interactive map modelPhoto model Video modelText model One possible view For the weather application Weather application view on the PC

L03-S36 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Weather Application (2) Weather Application Weather information Warning reports Interactive map modelPhoto model Video modelText model One possible view For the weather application

L03-S37 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad To show the applicability of the Stable MVM pattern to the weather application, we show show an instance of the pattern. The pattern instantiation is useful in visualizing each component in the pattern in reality. The instantiation diagram shows also how the different component of the pattern interact with each other in real applications. Weather Application (3) 37

L03-S38 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Instantiation Symbols Description Represents the pattern name as given in the pattern object diagram Points to an instance of the pattern in the current application example. Represents the typical flow of the interactions within the application example. Represents a logical interaction between the different pattern within the application example. AnyView

L03-S39 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad

L03-S40 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad 1. Generate instance diagrams for another applications of MVM. 2. Model the following concepts: viewing, simplifying, searching, and scalability. 3. Use negotiation pattern to model the following concepts: diplomatic negotiation, negotiating peace settlement, and trade negotiation. 40 Discussion Questions

L03-S41 Stable Analysis Patterns 2003 SJSU – CmpE --- M.E. Fayad Task 1: Read chapters on behavior models. Task 2: Start work on your team Project #2. Task 3: Prepare for next Design Session. 41 Tasks for Next Lecture