QRA: A Quality Requirements Analysis Approach for Service Systems

2013 ◽  
Author(s):  
Jie Sun ◽  
Liping Zhao ◽  
Pericles Loucopoulos ◽  
Bo Zhou
Keyword(s):  
Requirements Analysis ◽  
Service Systems ◽  
Analysis Approach ◽  
Quality Requirements

PROQRASS: A PROCESS-BASED APPROACH TO QUALITY REQUIREMENTS ANALYSIS FOR SERVICE SYSTEMS

2013 ◽  
Vol 23 (07) ◽  
pp. 943-962
Author(s):  
YE WANG ◽  
XIAOHU YANG ◽  
XINYU WANG ◽  
ALEKSANDER J. KAVS
Keyword(s):  
Business Process ◽  
Business Processes ◽  
Systematic Approach ◽  
Requirements Analysis ◽  
Service Systems ◽  
Process Models ◽  
Functional Requirements ◽  
Quality Requirements ◽  
Business Process Models ◽  
Equity Trading

Satisfying quality requirements for service systems is quite crucial and challenging. However, there is a gap between quality requirements analysis and quality requirements design in service systems. In order to bridge this gap, we provide a systematic approach — ProQRASS — to model and analyze quality requirements of services based on business processes, which are frequently used to model services. ProQRASS consists of five steps: (1) constructing business process models; (2) associating quality requirements with functional requirements of services in business process models; (3) identifying potential conflicts and cooperation among quality requirements; (4) filtering out false conflicts and cooperation; (5) resolving conflicts among quality requirements. We illustrate ProQRASS through an equity trading service system. We also evaluate its capability through the comparison with other approaches and conduct a usability investigation involving industrial experts. The result shows that ProQRASS is effective and useful.

Quality Requirements: Analysis of Utilization in the Systems of a Financial Institution

2019 ◽  
Author(s):  
T. S. Angelica Calazans ◽  
Roberto Avila Paldes ◽  
Edna Dias Canedo ◽  
T. S. Eloisa Masson ◽  
Fernando de A. Guimares ◽  
...  
Keyword(s):  
Financial Institution ◽  
Requirements Analysis ◽  
Quality Requirements

A Customer's Requirements Analysis Approach for Kano’s Model

2013 ◽  
Vol 753-755 ◽  
pp. 3140-3143
Author(s):  
Quan Shan ◽  
Yan Chen
Keyword(s):  
Mass Customization ◽  
Air Conditioning ◽  
Modular Design ◽  
Requirements Analysis ◽  
Analysis Approach ◽  
Kano Model ◽  
Air Conditioning System ◽  
Kano’S Model ◽  
Vital Factor

Modularity has been recognized as a vital factor to implement mass customization. To obtain the optimization project of modular design, customer's requirements must be gained firstly. There has different level for each customer's requirement. So, the classification technology of customer's requirements, which using KANO model investigate questionnaire, is expatiated in this paper. Then, the attribute class of customer's requirements can be gained. A questionnaire, which using the household hanging air-conditioning system as an example, is proposed in this paper. The result, which using KANO theory to analyze, demonstrates the feasibility of the proposed approaches.

scholarly journals Safety Requirements Analysis using Misuse Cases Method

2021 ◽  
Vol 7 (1) ◽  
pp. 1-9
Author(s):  
Ryo Alif Ramadhan ◽  
Dana Sulistyo Kusumo ◽  
Jati Hiliamsyah Husen
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Security Analysis ◽  
Safety Analysis ◽  
Requirements Analysis ◽  
Software Requirements ◽  
Analysis Approach ◽  
Analysis Method ◽  
Safety Requirements ◽  
Software Product

Safety requirements analysis is an activity inside software requirements engineering that focuses on finding and solving safety gaps inside a software product. One method to do safety requirements analysis is misuse cases, a technique adopted from the security analysis method. Misuse cases provide a safety analysis approach which allows detailed steps from different stakeholders' perspective. In this research, we evaluate the misuse cases method's understandability by implementing it to analyze safety requirements for an electric car's autopilot system. We assessed the developed models using the walkthrough method. We found differences between how the model understood from someone with experience in software development and those who don't.

Sign in / Sign up

Export Citation Format

Share Document