Evaluating the use of model-based requirements verification method: A feasibility study

Aceituna, Daniel; Do, Hyunsook; Walia, Gursimran Singh; Lee, Seok-Won

doi:10.1109/empire.2011.6046248

Cited by 18 publications

(17 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Determine the right requirements for the system is a very critical in the system development life, hence, there is a need to consider this phase carefully. References [3] and [14] contended that the requirement is one of the most critical stages in the development life cycle of any new system, thus, it should be carefully implemented to build high quality and reliable system.…”

Section: A System Requirement Concept and Typesmentioning

confidence: 99%

See 1 more Smart Citation

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Alsaleh¹,

Haron²

2016

LNSE

View full text Add to dashboard Cite

Abstract-This qualitative study aims to explore and describe the most important functional requirements (FR) and non-functional requirements (NFR) of knowledge sharing system (KSS) used at a Malaysian public academic institution. The strategy used is a single case study which aims to gather deeper insights on the requirements of the KSS. Data were collected through semi-structured interviews. A total of fifteen renowned academicians were interviewed. Content analysis method was used to extract the requirements from the qualitative data. The study identified twelve FR and NFR that academicians as an end users believe should be included in the KSS. The FR include alert user about new added; be able to categorize contents, have an efficient search process; offer information about experts; offer a consultation service; and provide interconnections among disciplines. The NFR include support multi-media, ensure accessibility; provide interactivity; be reliable; easy to use; and multi-level. The research comprehensive analysis and findings would expand an area of systems FR and NFR being used for knowledge sharing in academic institutions which may still theoretically and empirically not sufficiently covered.Index Terms-Academicians, functional requirement, non-functional requirement, knowledge sharing system.

show abstract

Section: A System Requirement Concept and Typesmentioning

confidence: 99%

“…It was emphasized that when conducting a qualitative research, the researcher should consider the finding validity [14]. For this study, to ensure the validity of the findings, steps were taken in a credible scholarly.…”

Section: Lecture Notes On Software Engineering Vol 4 No 2 May 2016mentioning

confidence: 99%

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Alsaleh¹,

Haron²

2016

LNSE

View full text Add to dashboard Cite

show abstract

“…Our Contribution: This paper is substantially expanded from the previous published results [37], and the new contributions are highlighted as follows:…”

Section: Introductionmentioning

confidence: 99%

“…Section 4 briefly discusses the experiment 1 design and summarizes the major results that have been reported earlier [37]. To reduce duplication, some of the experiment design details are presented in Section 4 that are common to both experiments.…”

Section: Difficulty Levelmentioning

confidence: 99%

“…The results showed that, during the translation of NL requirements into STD-BBs, the subjects were able to find a larger number of incomplete requirements as compared to the fault checklist based inspection. Also, the results from the experiment helped us revise the NLtoSTD-BB translation process to help improve its effectiveness when applied on NL [37].…”

Section: Difficulty Levelmentioning

confidence: 99%

See 1 more Smart Citation

Model-based requirements verification method: Conclusions from two controlled experiments

Aceituna

Walia

et al. 2014

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Context: Requirements engineering is one of the most important and critical phases in the software development life cycle, and should be carefully performed to build high quality and reliable software. However, requirements are typically gathered through various sources and are represented in natural language (NL), making requirements engineering a difficult, fault prone, and a challenging task. Objective: To ensure high-quality software, we need effective requirements verification methods that can clearly handle and address inherently ambiguous nature of NL specifications. The objective of this paper is to propose a method that can address the challenges with NL requirements verification and to evaluate our proposed method through controlled experiments. Method: We propose a model-based requirements verification method, called NLtoSTD, which transforms NL requirements into a State Transition Diagram (STD) that can help to detect and to eliminate ambiguities and incompleteness. The paper describes the NLtoSTD method to detect requirement faults, thereby improving the quality of the requirements. To evaluate the NLtoSTD method, we conducted two controlled experiments at North Dakota State University in which the participants employed the NLtoSTD method and a traditional fault checklist during the inspection of requirement documents to identify the ambiguities and incompleteness of the requirements. Results: Two experiment results show that the NLtoSTD method can be more effective in exposing the missing functionality and, in some cases, more ambiguous information than the fault-checklist method. Our experiments also revealed areas of improvement that benefit the method's applicability in the future. Conclusion: We presented a new approach, NLtoSTD, to verify requirements documents and two controlled experiments assessing our approach. The results are promising and have motivated the refinement of the NLtoSTD method and future empirical evaluation.

show abstract

Goal-Oriented Requirements Engineering for Research-Intensive Complex Systems: A Case Study

Woldeamlak¹,

Diabat²,

Svetinovic³

2016

Syst Eng

View full text Add to dashboard Cite

Complex systems in research and development exhibit important characteristics that might present significant systems engineering challenges due to lack of clear customers, system goals, previous development experience, etc. Such systems are characterized through the existence of multiple proposed preliminary architectures, no implemented prototypes, and no agreed upon standards and protocols. We refer to these systems as Research-Intensive Complex Systems (RICS). RICS requirements are not well-defined, and RICS are exposed to a wide variety of risks and uncertainties. The main source of the RICS domain knowledge, requirements, and goals are research publications and reports. There is often a lack of clear goals, and many goals are ambiguous or conflicting. This paper evaluates the effectiveness of the Knowledge Acquisition in autOmated Specification (KAOS) method applied to smart metering system, as an example of a sustainability-related RICS. The evaluation is performed using a set of qualitative criteria with respect to KAOS's ability to elicit and specify goals for RICS in comparison to the implemented goal models. C⃝ 2016 Wiley Periodicals, Inc. Syst Eng 19: 322-333, 2016

show abstract

Evaluating the use of model-based requirements verification method: A feasibility study

Cited by 18 publications

References 27 publications

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

The Most Important Functional and Non-Functional Requirements of Knowledge Sharing System at Public Academic Institutions: A Case Study

Model-based requirements verification method: Conclusions from two controlled experiments

Goal-Oriented Requirements Engineering for Research-Intensive Complex Systems: A Case Study

Contact Info

Product

Resources

About