Tool support for requirements analysis

Kramer, Jeff; Ng, Keng; Potts, Colin; Whitehead, Ken

doi:10.1049/sej.1988.0011

Cited by 20 publications

(8 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This process is divided into three phases which are: elicitation, specification and validation of the requirements [47]. SE and HCI techniques and methods are combined to obtain, formalize and validate the accessibility requirements.…”

Section: Action Taking : Proposed Solutionmentioning

confidence: 99%

Accessible chats for computer supported collaborative learning environments in mobile devices: Doctoral consortium paper

Calvo

2013

IEEE 7th International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

Abstract:The use of chats in Mobile Devices (MD) for learning environments is being increased in the last decade. However, they present many accessibility barriers that prevent people from using them. As a result, some people do not have the same opportunities to learn. This research aims to solve the accessibility barriers of chats in learning environments for its use in MDs. Thus, this paper presents the proposal of an model-based design and the strategy development process to create an accessible chat.

show abstract

Section: Action Taking : Proposed Solutionmentioning

confidence: 99%

Accessible chats for computer supported collaborative learning environments in mobile devices: Doctoral consortium paper

Calvo

2013

IEEE 7th International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

show abstract

“…RequisitoPro was selected because of its flexibility for defining tool-based standards and its ease of use. 1 Note that there may be different distributors for one and the same tool and vice versa. 2 The scoring system must be very simple to rule out subjective considerations.…”

Section: Tool Evaluationmentioning

confidence: 99%

“…This job must be managed correctly and automated [1] to assure that the knowledge gained is not merely assimilated, at best, by the participants in the requirements definition phase, but is a lasting and contractual entity and a consistent, clear, complete and manageable reference framework for the entire development process and, yet more importantly, for maintenance.…”

Section: Introductionmentioning

confidence: 99%

Creation of an automated management software requirements environment: A practical experience

Andrade

Ares²,

Dieste³

et al. 1999

Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99

View full text Add to dashboard Cite

A software process improvement programme is under way at a Spanish financial institution. A structured methodology, supported by formal and informal techniques and tools, is being established by a Methodological Support Group, as a starting point for the improvement. This paper centres particularly on the methodological and automated management of software requirements analysis. This process was previously performed in a not formal manner, and the most direct consequence was the high costs in maintenance. The methodology developed includes actions to obtain, refine and validate the software requirements. It also includes an organisational Software Requirements Specification (SRS) standard, implemented on a commercial tool which was selected as a result of a formal evaluation process. Additionally, a procedure was defined for working with the SRS and the tool. The results of this practical experience show an improvement in SRS quality, and work is no longer duplicated, since more correct and complete specifications are obtained.

show abstract

“…In addition, the status of each individual ViewPoint (reflected in its workrecord) could be monitored in order to gain insight into the current status of the project. This form of status monitoring of the partitioned parts of a method were successfully prototyped in the TARA project [13,14] for the r requirements method CORE (see figure 15, which marked each part asfollows: blank-not needed for elaboration, shaded-not started, ?-started but not completed or consistent, √-completed).…”

Section: Tool Support: Graphical Configuration Monitoring and Managementmentioning

confidence: 99%

A configurable framework for method and tool integration

Kramer

Finkelsteiin

1991

Software Development Environments and CASE Technology

Self Cite

View full text Add to dashboard Cite

There is an urgent need to provide a sound generic framework for method and tool integration, where many differing notations are used, software development is distributed and management support for the software development process is provided. This paper argues that there is much to be learnt from proven practical techniques for software construction, particularly those that support distributed software integration, heterogeneity and software management. Configuration Programming is one such approach which advocates the use of a separate, declarative configuration language for the description of system structure. It has been used in the Conic Environment for the development of distributable software, and is being extended for the configuration of heterogeneous components programmed in different programming languages. A number of software tools exist for the development, construction and management of Conic systems. This paper shows how an analogous set of the principles, practice and tools from configuration programming can be combined with recent work on ViewPoints 1 to provide a configurable framework for method and tool integration.

show abstract

Tool support for requirements analysis

Cited by 20 publications

References 2 publications

Accessible chats for computer supported collaborative learning environments in mobile devices: Doctoral consortium paper

Accessible chats for computer supported collaborative learning environments in mobile devices: Doctoral consortium paper

Creation of an automated management software requirements environment: A practical experience

A configurable framework for method and tool integration

Contact Info

Product

Resources

About