RMM - Relationship Management Model

Size: px

Start display at page:

Download "RMM - Relationship Management Model"

Brice Banks
5 years ago
Views:

1 RMM - Relationship Management Model By Qasim Hasan & Sandeep Jauhal Monday November 22 nd, 2004 About RMM Developed at New York University s Stern School of Business by Isakowitz & others A design model and a set of specified design steps which aim to provide a methodology for creating hypermedia applications Hypermedia is the mechanism for managing the relationships between information objects. About RMM The Big Picture RMM Concepts RMM will be most useful in applications which have both a high degree of structure and high volatility of information p.479 RMM is work in progress Author acknowledges this Recently added application diagram & m-slices Eg. Product catalogues, digital libraries, DB High volatility? Degree of structure? Focuses only on design & implementation stages of development process

RMDM: Design Model Relationship Management Data Model (RMDM) Used to represent the design of hypermedia apps Based on three types of modelling primitives E-R Domain Primitives RMD Domain Primitives

2 RMDM: Design Model Relationship Management Data Model (RMDM) Used to represent the design of hypermedia apps Based on three types of modelling primitives E-R Domain Primitives RMD Domain Primitives Access Primitives E-R Domain Primitives Entity Represent abstract or physical objects Attributes belong to entities Associative relationships Represent domain level associations between entities Represent information about the domain which is application independent RMD Domain Primitives Slices are used to group attributes within an entity together Eg. Student entity with attributes sid, name, gpa, address, phone number Prof may view sid, name, gpa in one context Student may view name, address, phone number

3 Access Primitives Used to model navigation and application specific access structures Unidirectional and bidirectional links Grouping Conditional Index, Guided Tour, and Indexed Guided Tour Access Primitives : Grouping Contributors Articles Keywords Main Menu Menu-like mechanism which supports access to other parts of the application p.484 Contributor Index Contributors since 1984 Abdel-Hamid, Tarek Abdul-Gader, Abdullah H. Adam, Nabil R. Keywrod Index List of Keywords: Acounting ISs Adoption of IS Automatred Reasoning Access Primitives : Conditional Index Ronald M. Lee Ronald M. Lee Univesrity of Texas, Austin JMIS Publications since Spring 1984 DX: A Deontic Expert System Sunro Lee Journal of Management Information Systems Vol. 12 No. 1, Summer 1995 Sunro Lee JMIS Publications since Spring 1984 A Framework for Linking the Structure of Information Systems with Organizational Contributor Index Requirements for John Information A. Lehman Sharing Journal of Management Information Systems Lee, Ronald, M. Vol. 8 No. 4, Spring 1992 John A. Lehman Lee, Sunro JMIS Publications since Spring 1984 Lehman, John Organizational Size and Information System Sophistication Leidner, Dorothy Journal of Management Dorothy Information E. Leidner Systems Vol. 2 No. 3, Winter 1986 Dorothy E. Leidner JMIS Publications since Spring 1984 Conditional Guided Tours How about conditional indexed guided tours? Spring 1996 Issue GUIDED TOUR ARTICLES ON SPRING 1996 ISSUE FIRST ARTICLE LAST ARTICLE Editorial Introduction Editorial Introduction By Vladimir Zwass DATA QUALITY Beyond is a persistent Accuracy and serious problem, underlying untrustworthiness of many information systems... Beyond Accuracy: What Data Quality Means to Data Consumers By Richard Y. Wang and Diane M. Strong A field survey was Key conducted Dimensions to determine key organizational factors that facilitate and/or inhibit Key Dimensions the development of Facilitators... and Inhibitors for the Strategic Use of Information Technology by William R King and Thompson Sian Hin Teo A field survey Impact was conducted of Competitive to determine key organizational factors that facilitate and/or inhibit Impact the of development Competitive of Strategy strategic and Information applications Technology... Maturity on Firm's Strategic Response to Globalization by Jahangir Karimi, Yash P. Gupta and Toni Somers Recently the globalization of competition has caused many firms in the financial services Executive Information Systems: Their impact on Executive Decision Making Journal of Management Information Systems Vol. 10 No. 3, Winter 1994

Limitations Solution : m-slices Unable to model certain types of structures Information from multiple entities cannot be combined into a single presentation unit Suggested solution : m-slices Model

4 Limitations Solution : m-slices Unable to model certain types of structures Information from multiple entities cannot be combined into a single presentation unit Suggested solution : m-slices Model encourages a top-down approach, which can be highly undesirable Critique : top-down or bottom-up? Suggested solution : application diagram It is not the interface itself, nor does it contain info about the interface, but it is in fact the data which can be used in the presentation of the interface Splits and organizes entities into meaningful slices Each slice groups one or more attributes of an entity Each m-slice groups attributes of collections of entities Solution : m-slices Solution : Application diagrams Slice from same Entity Aimed at explicitly showing the presentation units and the interconnections between these units, which go to make up the application p.487 The addition of application diagrams also means that Steps 2 and 3 can be performed together. The result is that this phase of the design can be bottomup, top-down, or a combination of the two p.490 Slice from different Entities

RMM Method Steps Step 1 : E-R design Step 2 : Slice design Step 3 : Navigation design Step 4 : Conversion protocol design Step 5 : User interface design Step 6 : Run-time behaviour design Step 7 :

5 RMM Method Steps Step 1 : E-R design Step 2 : Slice design Step 3 : Navigation design Step 4 : Conversion protocol design Step 5 : User interface design Step 6 : Run-time behaviour design Step 7 : Construction and Testing Use of an application diagram can combine these steps Step 1 : E-R design The information domain of the application is analyzed and modeled using an entity-relationship diagram p.487 Helps identify important relationships Provides an application-independent view of the domain of interest Allows for low-level reuse Output: E-R Diagram Step 2 : Slice design How the information in the application will be grouped for presentation Links between slices in different entities represent associative links semantic relationships Links between slices in the same entities represent structural links different perspective of the same entity Output : E-R+ Diagram

Step 3: Navigation Design Old RMM Model: Each relationship in E-R+ is analyzed for correctness before conversion to access primitive Won t allow hard-coded links between entities Grouping of high

6 Step 3: Navigation Design Old RMM Model: Each relationship in E-R+ is analyzed for correctness before conversion to access primitive Won t allow hard-coded links between entities Grouping of high level access structures are done in this step, providing menu-like access Output: RMDM diagram Step 3: Navigation Design Step 4: Conversion Protocol Design New RMM Model: M-slices which are the target of a link in E-R+ are selected, including all links between them Allows for an iterative approach, combining topdown and bottom-up Develop a set of conversion rules Convert RMDM diagram into an appropriate object in the implementation environment Eg.How a slice is converted into an HTML page Output: Application diagram

Steps 5 & 6 User Interface design How the objects will be presented Look of anchors, button layouts, video & audio RM-CASE Run Time Behavior History lists, link traversal, search engines,

480 Figure 15-1 Effective Navigation & Browsing Since the structure is based on logical relationships between the information, it is more likely to be familiar to the user Consistent

7 Steps 5 & 6 User Interface design How the objects will be presented Look of anchors, button layouts, video & audio RM-CASE Run Time Behavior History lists, link traversal, search engines, etc Note: Steps 4, 5 & 6 run in parallel P.480 Figure 15-1 Effective Navigation & Browsing Since the structure is based on logical relationships between the information, it is more likely to be familiar to the user Consistent style of navigation and look and feel Information structure itself assists with navigation Clickable maps: Serves two purposes Lost in hyperspace Alternative means of navigation Limitation Limited functionality for history mechanisms, search engines, etc. RMM does not provide any indication of how these activities should be carried out

8 Cognitive Management during Browsing Two positive side effects Use of image maps reduces cognitive load during browsing Use of conversion protocol during design stage achieves interface consistency Users wont have to adjust to differences in interface Information Contextualization Associative relationships between entities Vs links between slices within a single entity Going from one entity to another will lead to a context change Signaled by change in background, etc Going from one slice to another slice within the same entity results in same local context Information Contextualization Another useful contextualization aid is that it becomes possible to see from which entity a given presentation unit (i.e. slice) is derived p.497 Is this really useful? Link and Content Validity Positive side effects Concepts are related and relevant to application because they have an E-R model Much less likely to incorporate irrelevant info Limitation Little support for sequences of information access Does provide support for guided tours, but only as an access structure, rather than a mechanism for designing sequences of presentation the mere fact of having design stages where the content and relationships are explicitly identified will in itself be more likely to result in valid content and links p.498 Is this always the case?

9 Link and Content Validity An opposite view Multiple design stages can introduce problems between initial content and final implementation Additional effort required to re-trace back to intermediate designs during updating Sequence of tranformations can reduce traceability of errors and can provide opportunities to introduce errors Information Structure Does not provide guidelines for designing the structure develops the structure using relationships among the information Bottom-up approach Guideline for slices Group related info and stay simple With m-slices, its trickier to identify related info since info is from different entities Author still commends m-slices because they provide a thought process for grouping Information Structure Does not provide guidelines for assisting in identifying suitable links. Although it does have an explicit stage where links are identified by author. Management of Different Media No support. synchronized text with images etc. Small number of structural building blocks. Forces user to be aware about types of navigation structures being used.

10 Process Issues : Application Maintenance No explicit maintenance but applications created are inherently more maintainable. Helped by separation of domain knowledge, application structure and implementation. Eg. Changing presentation environment from CD-ROM to web. only implementation needs to be changed. Process Issues : Application Maintenance Applications developed are more maintainable for content. Usage of templates to add new content from entities to presentation. Similar to xslt on the web generating info from xml. Process Issues : Reuse Claim: re-use is promoted by having intermediate deliverables (ie. ER diagrams). But RMM doesn t explicitly state how these reusable elements can be identified. m-slice and Application diagrams are mentioned as solutions to this problem. Captures info about presentation units Identifies low-level structures (popular for re-use) early in design process. Process Issues : Full life cycle and process management Not supported. Claim that they don t want to be jack of all trades and hence list other programs that can be used in those steps. Limitation: may not integrate well with iterative approach since it is mainly bottom-up.

Process Issues : Other Issues Fun and Games Cognitive management for Developers. Output for each stage with Old RMM? Specific set of steps guide developers.

11 Process Issues : Other Issues Fun and Games Cognitive management for Developers. Output for each stage with Old RMM? Specific set of steps guide developers. Supporting enhanced productivity Lack of content creation Lack of cross linking of info ER Design ER+ Design RMDM Design Highly structured so lack of links. Fun and Games Indexed, Guided or Guided Indexed? Output for each stage with New RMM? ER Design ER+ Design Application Diagram

12 Which row/column combo is recommended for RMM?

Adaptable and Adaptive Web Information Systems. Lecture 1: Introduction

Adaptable and Adaptive Web Information Systems School of Computer Science and Information Systems Birkbeck College University of London Lecture 1: Introduction George Magoulas gmagoulas@dcs.bbk.ac.uk October