Affective Embedded Systems: a Requirement Engineering Approach

Carvalhaes, Millys F. A.; Rocha, Adson Ferreira da; Vieira, Marcus Fraga; Barbosa, Túlio

doi:10.14445/22312803/ijctt-v8p113

Cited by 6 publications

(7 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…At the architectural phase, existing works address quality attributes variability jointly with the variability of base applications. [16] propose the RiPLE-DE (RiSE Product Line Engineering -Design Engineering) process approach presenting the variability of quality attributes in feature diagrams and to derive the desired quality attributes the diagrams are enhanced with information of the base application (e.g., the system's response measure). The variation of attributes is presented in form of numerical values that will be used in the evaluation of the resulting architecture designing SPL architectures that involve the systematic transformation of functional requirements and quality.…”

Section: Architectural Based Quality Attributes Integration Approachesmentioning

confidence: 99%

Embedding Quality into Software Product Line Variability Artifacts

Daniel¹,

Nderu²,

Kimwele³

2021

IJSEA

View full text Add to dashboard Cite

The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

show abstract

Section: Architectural Based Quality Attributes Integration Approachesmentioning

confidence: 99%

Embedding Quality into Software Product Line Variability Artifacts

Daniel¹,

Nderu²,

Kimwele³

2021

IJSEA

View full text Add to dashboard Cite

show abstract

“…At the architectural phase existing works address quality attributes variability jointly with the variability of base applications. [16] propose the RiPLE-DE (RiSE Product Line Engineering -Design Engineering) process approach presenting the variability of quality attributes in feature diagrams and in order to derive the desired quality attributes the diagrams are enhanced with information of the base application (e.g., the system's response measure). The variation of attributes is presented in form of numerical values that will be used in evaluation of the resulting architecture designing SPL architectures that involve systematic transformation of functional requirements and quality.…”

Section: Architectural Based Quality Attributes Integration Approachesmentioning

confidence: 99%

Integrated Specification of Quality Requirements in Software Product Line Artifacts

Daniel¹,

Nderu²,

Kimwele³

2021

Computer Science &Amp; Information Technology (CS &Amp; IT)

View full text Add to dashboard Cite

There are many calls from software engineering scholars to incorporate non-functional requirements as first-class citizens in the software development process. In Software Product Line Engineering emphasis is on explicit definition of functional requirements using feature models while non-functional requirements are considered implicit. In this paper we present an integrated requirements specification template for common quality attributes alongside functional requirements at software product line variation points. This approach implemented at analytical description phase increases the visibility of quality requirements obliging developers to consider them in subsequent phases. The approach achieves weaving of quality requirements into associated functional requirements through higher level feature abstraction method. This work therefore promotes achievement of system quality by elevating nonfunctional requirement specification. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

show abstract

“…Requirements grouped into three categories, including: functional requirements, non-functional requirements, and affective requirements [17]. Both non-functional requirement and affective requirement wil described in this section, and functional requirement defined system functionalities will describes in section of system sesification.…”

Section: A Requirement Analysismentioning

confidence: 99%

A Design of Intelligent Agent for Research Reminder and Logbook using GAIA Method

Aziz¹,

Pranolo²,

Setiadi³

2015

IJCTT

View full text Add to dashboard Cite

This research aims to design an intelligent agent that can provide the reminder, receive, and manage the logbook research. The system will be built is can be accepted the input through form of research schedule information via the website interface, and send the reminder to user via SMS gateway. The Agent will send the reminder based on schedule activities, conducted the logbook, and provide a report when it requested. GAIA (Graphical Analysis for Interactive Assistance) method used for the analysis and design of agents. This method consists of two main parts, namely: 1) Analysis, aims to analyze role models, and analyze models of interaction model; and 2) design, which is to agent models, services model, and acquaintance models. The results of this work are: 1) The analysis of a collection of system requirements, 2) analysis of environmental models, 2) role models, 3) interaction model that includes: a) the association relationship between objects and their interactions, and b) the message exchange model between researchers and agent, 4) a model class diagram, and 5) the design system.

show abstract

Affective Embedded Systems: a Requirement Engineering Approach

Cited by 6 publications

References 10 publications

Embedding Quality into Software Product Line Variability Artifacts

Embedding Quality into Software Product Line Variability Artifacts

Integrated Specification of Quality Requirements in Software Product Line Artifacts

A Design of Intelligent Agent for Research Reminder and Logbook using GAIA Method

Contact Info

Product

Resources

About