Tagging requirements for web application

Abstract

Tagging systems exist that support tagging of resources, like, web pages, web links, videos, images and blogs. In web applications, use of tag facilitates categorization of related content and improves search within a resource, like, searching a blog or a page. During the development of web application, there is a need for eliciting the requirements for the tagging functionality in the web application. In this paper, we present a requirement checklist for tagging, from the viewpoint of incorporating the tagging functionality in a web application. A use-case based approach has been followed to identify the requirements for tagging. We see that the requirements for tagging vary, depending on the kind of permission provided to the user for the purposes of tagging. Also, there is a need to include resource-specific features. Accordingly, we categorize user requirements based on user-permissions for tagging, and also list the resource-specific features. Our checklist is beneficial both for the web application and the developer during the requirement specification process. During testing, the requirement checklist for tagging is useful for the validation and verification purposes.

Software Engineering for Tagging Software

“…In [2], Gupta et al identify the actors of the tagging software based on their interaction with the tagging software in a web application. Using the use-case based approach, three kinds of actors have been identified as follows -…”

“…The Visitor Permissions sub-component allows the web application to select the level of flexibility to be provided to the visitor as defined in [2]. The three levels of flexibilities from which the web application can choose are UseTagResource (UsTR), UseTagResource_UpdateTag (UsTR_UpT) and UseTagResource_UpdateTagResource (UsTR_UpTR).…”

“…In our earlier paper [2], we have identified different type of users that access the tagging software in a web application. Also, we have identified the requirements of the tagging software and present them as a weighted requirement checklist in [1].…”

Framework for Tagging Software in Web Application

“…In [2], Gupta et al identify the types of users based on their interaction with the tagging software in a web application. Using the use-case based approach; three kinds of users have been identified as follows -…”

“…This process is carried out to determine the kind of restriction is required on the tags. The Visitor Permissions sub-component allows the web application to select the level of flexibility in usage to be provided to the visitor as defined in [2]. The three levels of flexibilities from which the web application can choose are UseTagResource (UsTR), UseTagResource_UpdateTag (UsTR_UpT) and UseTagResource_UpdateTagResource (UsTR_UpTR).…”