Survey of Existing Web Models Techniques to Design Web Application

More documents

Recommendations

Info

Anup Hande et al , Int.J.Computer Technology & Applications,Vol 4 (3),514-521 ISSN:2229-6093 9 HYPERTEXT MODELLING Besides transforming the Entities’ Attributes, in OO-H the Constructor(), Destructor(), and Modifier() operations must be defined for the Class as well. Likewise for each Relationship of an Entity the Relationer() and Unrelationer() operations have to be generated for the corresponding Class in the OO-H content model. 8.6 Content Structure Model [4] Figure 10 Content Structure Model Class Diagram [4] 9.2 Introduction Its purpose is to model the navigation paths available to users major UWE Artifacts[8] are Hypertext Structure Model which navigating among classes, Access Model which UML-compliant site map, Focuses on the structure of the hypertext & access elements Use “>” annotation to distinguish from content classes and it is based on content models main goals are to represent nodes and links of the hypertext structure, to design navigation paths, and to avoid disorientation and cognitive overload. Resultant we get navigation model which represented by a UML class diagram it uses specific modeling elements for Web concepts and Modeling elements are basic elements and access primitives. There are some other methodologies also available own notation for hypertext elements. Different diagram types are UML state diagram or own diagram type. The non-linearity of hypertext is one of the most important properties to be taken into account when modeling Web applications. Thus the hypertext structure has to be designed carefully. This can be achieved by using suitable access structures, i.e., navigation options, to avoid the risk of users getting lost and putting them under excessive cognitive stress. 9.3 Different Types of Links…[4] 9.3.1 HDM (Hypertext Design Model) • Structural links connect elements of the same node, • Perspective links put various views of a node in relation to each other. • Application links put different nodes in relation to each other, depending on the application. 9.3.2 WebML (Web Modeling Language) • Contextual links carry context information, • Non-contextual links have no associated context information. • Intra-page links are used when the source and the destination of a link belong to the same page. • Inter-page links are used when the source and the destination are on different pages. Based on the functional requirements of Web applications, the UWE modeling method defines the following types of links: • Navigation links are used to navigate between nodes, • Process links point to the start node of a process. • External links point to a node not directly belonging to the application. 9.3.3 The OO-H (Object-Oriented Hypermedia) modeling method defines five types of links as follows: • I-links (internal links) point to nodes inside the boundaries of a given navigational requirement. • T-links (traversal links) point to nodes covering other navigational requirements. • R-links (requirement links) point to a start of a navigational path. • X-links (external links) point to external nodes. IJCTA | May-June 2013 Available online@www.ijcta.com 519
Anup Hande et al , Int.J.Computer Technology & Applications,Vol 4 (3),514-521 ISSN:2229-6093 • S-links (service links) point (with their corresponding response links) to services. 9.3.4 HDM Structural links connect elements of the same node, Perspective links put various views of a node in relation to each other and Application links put different nodes in relation to each other, depending on the application. 9.3.5 WebML In Contextual links carry context information. Noncontextual links have no associated context information. With regard to the distribution of nodes on the hypertext level over pages on the presentation, Intra-page links are used when the source and the destination of a link belong to the same, and Inter-page links are used when the source and the destination are on different pages. 9.4 Navigation Access Model [4] In Hypertext structure models describe navigation, but not orientation. Access models describe both through Navigation patterns, used to consistently describe conventional elements. • (list of objects of the same type) • (list of heterogeneous objects) • (sequential links) • The hypertext structure model built so far alone is not sufficient to describe how nodes can be reached by navigation. To allow users to navigate to nodes the users need navigation and orientation aids. These are formulated in the form of access structures refining the hypertext structure model. Recurring access structures are described in as design patterns, also called “hypermedia design patterns” or “navigation patterns”. The use of these navigation patterns helps to increase the quality of the hypertext model tremendously. Figure 11 Navigation Acess Model for online PC shop IJCTA | May-June 2013 Available online@www.ijcta.com 10 COMPARISON AND ANALYSIS 10.1 Comparison of Existing Language to model Web site Features WebML UWE W2000 OOWS OOHD M Events Ok - Poor - - Broswer Control Lifecycles Users Security Databases Messaging UI Modelling Platform Independent Standards Meta-models Model Verification CASE Tool Poor - - - - Poor Good - - Good Poor Poor Poor - Ok Ok Poor - - Good Ok Poor Poor Poor Good Poor Ok - - Poor Ok Ok Poor Ok Excellent Excellent Good Excellen t Good Poor Excellent Excellent Ok Poor Poor Excellent Excellent Poor - Ok Ok - - - Good Ok Poor Ok - Figure 12 Feature Comparison of Existing Language to model Web site 10.2 Summary of the Requirements Specification Perspective Analysis Method Functional Req. Data Req. Navigational Req. OOHDM Use cases, - UIDs textual templates WSDM Natural language task diagram Natural language Natural language task diagram SOHDM Scope diagram, - - SACs UWE Web process use cases, stereotyped activity diagrams, use - Navigation use cases, stereotyped activity diagrams cases WebML User templates, activity diagrams, use Data dictionary Site specification templates cases OOH Use cases - Web requirements metamodel(WE- RMExt) OOWS W2000 NDT Task characterization templates, activity diagrams Functional use cases Use cases formatted templates Information templates Task taxonomy, activity diagrams - Navigational use cases Formatted Formatted templates templates Figure 13 Summary of the Requirements Specification Perspective Analysis 520
Page 1 and 2: Anup Hande et al , Int.J.Computer T
Page 3 and 4: Anup Hande et al , Int.J.Computer T
Page 5: Anup Hande et al , Int.J.Computer T

Survey of Existing Web Models Techniques to Design Web Application

Create successful ePaper yourself

Delete template?

Save as template?