Opening up access to online documents using essentiality tracks

Atkinson, Matthew T.; Dhiensa, Jatinder; Machin, Colin H. C.

doi:10.1145/1133219.1133222

Cited by 5 publications

(4 citation statements)

References 5 publications

(13 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Essentiality ratings and tracks were first proposed to treat the problem of information overload in large documents and webpages [88]. The essence of the concept is that sections of content are marked with a rating of essentiality on a numerical 1-10 scale, and/or for a specific intended audience (i.e., a track), e.g., for a 'UI developer'.…”

Section: Reducing Problems In Current Projects (Where Ur-sysr Repetitmentioning

confidence: 99%

Repetition between stakeholder (user) and system requirements

et al. 2015

View full text Add to dashboard Cite

Stakeholder requirements (also known as user requirements) are defined at an early stage of a software project to describe the problem(s) to be solved. At a later stage, abstract solutions to those problems are prescribed in system requirements. The quality of these requirements has long been linked to the quality of the software system and its development or procurement process. However little is known about the quality defect of redundancy between these two sets of requirements. Previous literature is anecdotal rather than exploratory, and so this paper empirically investigates its occurrence and consequences with a case study from a UK defence contractor. We report on a survey of sixteen consultants to understand their perception of the problem, and on an analysis of real world software requirements documents using natural language processing techniques. We found that three quarters of the consultants had seen repetition in at least half of their projects. Additionally, we found that on average, a third of the requirement pairs' (comprised of a system and its related stakeholder requirement) description fields were repeated such that one requirement in the pair added only trivial information. That is, solutions were described twice while their respective problems were not described, which ultimately lead to suboptimal decisions later in the development process and reduced motivation to read the requirements set. Furthermore, the requirement attributes considered to be secondary to the primary 'description' attribute, such as the 'rationale' or 'fit criterion' fields had considerably more repetition between UR-SysR pairs. Given that the UR-SysR repetition phenomena received most of its discussion in the literature over a decade ago, it is interesting that the survey participants did not consider its occurrence to have declined since then. We provide recommendations on preventing the defect, and describe the freelyavailable tool developed to automatically detect its occurrence and alleviate its consequences.

show abstract

Section: Reducing Problems In Current Projects (Where Ur-sysr Repetitmentioning

confidence: 99%

Repetition between stakeholder (user) and system requirements

et al. 2015

View full text Add to dashboard Cite

show abstract

“…A number of technologies are under development that will enable users to be presented with information that is more relevant to their needs and in the formats they prefer [11,12]. These tools, if brought into the mainstream could dramatically improve the accessibility -really usability, as we are concerned with all users -of web-based documents.…”

Section: Web-based Formats -Html and Xmlmentioning

confidence: 99%

Improving library services to people with print disabilities: the role of technology in public libraries

Atkinson¹,

Dhiensa²

2007

Improving Library Services to People With Disabilities

Self Cite

View full text Add to dashboard Cite

“…One of the ways this can be tuned is by reducing the complexity of document structures (e.g., removing phrase element tags from DocBook structures) and associated XLink relations. Also, essentiality tracks techniques [2] can be further applied to adapt content to user's requirements.…”

Section: Content Processingmentioning

confidence: 99%

Leveraging rich accessible documents on the web

Lopes

Carriço

2007

Proceedings of the 2007 International Cross-Disciplinary Conference on Web Accessibility (W4A) - W4A '07

View full text Add to dashboard Cite

This paper presents a new approach on leveraging accessibility for rich document delivery to the Web. The proposal entails a profile modeling task, where multidisciplinary teams can discuss users, devices, and usage scenarios, in order to grasp and synthesise the different document delivery scenarios. A document production framework is presented, which can be configured according to modeled profiles. By using this approach, documents are tailored to users in such a way that rich interaction capabilities are maintained, without sacrificing content accessibility.

show abstract

Opening up access to online documents using essentiality tracks

Cited by 5 publications

References 5 publications

Repetition between stakeholder (user) and system requirements

Repetition between stakeholder (user) and system requirements

Improving library services to people with print disabilities: the role of technology in public libraries

Leveraging rich accessible documents on the web

Contact Info

Product

Resources

About