Using tagging to identify and organize concerns during pre-requirements analysis

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.

show abstract

“…This helps in maintaining the requirements through the requirement phase. In [15], Ossher et al use tagging during the pre-requirement phase.…”

Section: Related Workmentioning

confidence: 98%

Tagging requirements for web application

Gupta

Goel

2012

Proceedings of the 5th India Software Engineering Conference

View full text Add to dashboard Cite

show abstract

“…In the early stages of software development, Ossher et al [14] propose tagging as a valuable approach to identify and organize concerns during early exploration in business analysis and explore how tags can be hardened as the analysis evolves. Treude and Storey [25][26][27][28] examined how tags are used by professional software developers to document work items, the different roles of tags, and how tagging mechanisms were adopted by developers.…”

Section: Tagging In Software Developmentmentioning

confidence: 99%

Can collaborative tagging improve user feedback? a case study

Alkadhi

Pagano²,

Bruegge³

2014

Proceedings of the 6th International Workshop on Social Software Engineering

View full text Add to dashboard Cite

User feedback is a rich source of information which can help developers to improve software quality and identify missing features. However, developers need to analyze user feedback in order to assess its relevance and potential impact, which bears several challenges due to its quantity, quality, structure, and content, particularly when feedback volume is high. In this paper we present the results of a case study to explore which role collaborative tagging can play to improve user feedback, in particular, its impact on the navigation within, understandability, and structure of user feedback. Our results indicate that collaborative tagging might contribute to decrease the pain when analyzing and organizing user feedback.

show abstract

“…While these dimensions apply to tagging systems used by software developers, studying tagging systems used by software developers such as ICICLE [1], TagSEA [6], IBM's Jazz, BITKit [3], Google Code 4 , ConcernMapper [5] and Concern Graphs [4] reveals additional dimensions on top of Marlow's taxonomy.…”

Section: Dimensions Of Tagging Systemsmentioning

confidence: 99%

The implications of how we tag software artifacts

Storey

2010

Proceedings of the 1st Workshop on Web 2.0 for Software Engineering

View full text Add to dashboard Cite

Social tagging has been adopted by software developers in various contexts from source code to work items and build definitions. While the success of tagging is usually attributed to the simplicity of tags, the implementation details of tagging systems vary significantly in terms of metadata, schemata and semantics. In this position paper, we argue that academia and industry should be aware of these differences and that we should start to examine their implications.

show abstract

Using tagging to identify and organize concerns during pre-requirements analysis

Cited by 14 publications

References 5 publications

Tagging requirements for web application

Tagging requirements for web application

Can collaborative tagging improve user feedback? a case study

The implications of how we tag software artifacts

Contact Info

Product

Resources

About