2016Unpublished venueRequires access

Thematic Track: Quality in ICT Requirements Engineering 2016

Maria Lencastre, Alberto Rodrigues da Silva

Open publisher page 0 citations

Abstract

Quality is often considered something that must be in conformance with system requirements. However, such requirements keep changing to be aligned with the business needs, thus making quality a moving target! Requirements engineering helps to elicit the stakeholders requirements (such in a form of general goals, user stories, use cases, constraints etc.) with respect to the system of interested, to prioritize such requirements and, ultimately, to reach a common ground with other stakeholders with conflicting requirements. Furthermore, it helps stakeholders from different backgrounds to communicate among them, and with even with the project team, with systems designers, developers, testers, etc. The former are not necessarily interested in the implementation technical details, while the latter are specialized in designing, building and testing such systems. Caught in-between, requirements engineers must also keep up with newer development approaches. The "Quality in ICT Requirements Engineering" Thematic Track 2016 has at its accepted papers a multitude of relevant topics such as: requirements elicitation and specification, requirements traceability, requirements prioritization, ontologies for embed systems, and requirements specification tools. This program includes five full papers and two work-in-progress papers.

About this research paper

What this paper is about

Quality is often considered something that must be in conformance with system requirements. However, such requirements keep changing to be aligned with the business needs, thus making quality a moving target! Requirements engineering helps to elicit the stakeholders requirements (such in a form of general goals, user stories, use cases, constraints etc.) with respect to the system of interested, to prioritize such requirements and, ultimately, to reach a common ground with other stakeholders with conflicting requirements. Furthermore, it helps stakeholders from different backgrounds to communicate among them, and with even with the project team, with systems designers, developers, testers, etc. The former are not necessarily interested in the implementation technical details, while the latter are specialized in designing, building and testing such systems. Caught in-between, requirements engineers must also keep up with newer development approaches. The "Quality in ICT Requirements Engineering" Thematic Track 2016 has at its accepted papers a multitude of relevant topics such as: requirements elicitation and specification, requirements traceability, requirements prioritization, ontologies for embed systems, and requirements specification tools. This program includes five full papers and two work-in-progress papers.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Quality is often considered something that must be in conformance with system requirements. However, such requirements keep changing to be aligned with the business needs, thus making quality a moving target! Requirements engineering helps to elicit the stakeholders requirements (such in a form of general goals, user stories, use cases, constraints etc.) with respect to the system of interested, to prioritize such requirements and, ultimately, to reach a common ground with other stakeholders with conflicting requirements. Furthermore, it helps stakeholders from different backgrounds to communicate among them, and with even with the project team, with systems designers, developers, testers, etc. The former are not necessarily interested in the implementation technical details, while the latter are specialized in designing, building and testing such systems. Caught in-between, requirements engineers must also keep up with newer development approaches. The "Quality in ICT Requirements Engineering" Thematic Track 2016 has at its accepted papers a multitude of relevant topics such as: requirements elicitation and specification, requirements traceability, requirements prioritization, ontologies for embed systems, and requirements specification tools. This program includes five full papers and two work-in-progress papers.

Key concepts: Requirements elicitation, Requirements engineering, Requirements management, Requirements analysis, Business requirements, Requirements traceability, Requirement, User requirements document

Related papers

Back to paper searchBrowse research topicsOriginal source
Thematic Track: Quality in ICT Requirements Engineering 2016 — Research Paper | ScholarLens