scholarly journals Development of scenario management and requirements tool (SMaRT): towards supporting scenario-based requirements engineering methodology

2018 ◽  
Vol 7 (2.14) ◽  
pp. 62
Author(s):  
Azlin Nordin ◽  
Amirul Ikhwan Omar ◽  
Megat Usamah Megat Mohamed Amin ◽  
Norsaremah Salleh
Keyword(s):  
Requirements Engineering ◽  
Real World ◽  
Management Process ◽  
Requirements Management ◽  
Software Environment ◽  
Document Generation

Scenario-based methodology has been applied in analyzing real world experience into representation in software environment. Nonetheless, capturing, documenting and managing scenarios are extremely labor-intensive. Hence, the generic aims of this project are to investigate, explore and analyze requirements management process towards supporting scenario-based requirements approach. Based on our analysis of the existing RE or Requirements Management (RM) tools, most of the tools had less focus or missing some significant RE features to facilitate scenario-based   methodology. We analyzed all the relevant features and developed a prototype i.e.  Scenario-based Requirements Tool (SMaRT) to demonstrate how scenario-based approach can be implemented to further supports scenario-based RE  methodology and  covers most of the RE process  i.e. elicitation,  analysis  and  negotiation, documentation, validation,   and  management. SMaRT improves the RE tool features i.e. project and requirements management, document generation and validation function to further supports scenario-based RE methodology and covers most of the RE process i.e. elicitation, analysis, negotiation, documentation, validation, and management.   

scholarly journals An 11-bit High Dynamic Range (HDR) Luminance Display and Its Use to Discover Contextual Mechanisms of Real-World Luminance Normalization for Visual Acuity and Target Discrimination

2019 ◽  
Author(s):  
Chou P Hung ◽  
Chloe Callahan-Flintoft ◽  
Paul D Fedele ◽  
Kim F Fluitt ◽  
Onyekachi Odoemene ◽  
...  
Keyword(s):  
Visual Acuity ◽  
Real World ◽  
Dynamic Range ◽  
High Dynamic Range ◽  
Automatic Target Recognition ◽  
Facilitation Effect ◽  
Software Environment ◽  
Temporal Precision ◽  
Central Target ◽  
High Dynamic

ABSTRACTLuminance can vary widely when scanning across a scene, by up to 10^9 to 1, requiring multiple normalizing mechanisms spanning from the retina to cortex to support visual acuity and recognition. Vision models based on standard dynamic range luminance contrast ratios below 100 to 1 have limited ability to generalize to real-world scenes with contrast ratios over 10,000 to 1 (high dynamic range [HDR]). Understanding and modeling brain mechanisms of HDR luminance normalization is thus important for military applications, including automatic target recognition, display tone mapping, and camouflage. Yet, computer display of HDR stimuli was until recently unavailable or impractical for research. Here we describe procedures for setup, calibration, and precision check of an HDR display system with over 100,000 to 1 luminance dynamic range (650–0.0065 cd/m^2), pseudo 11-bit grayscale precision, and 3-ms temporal precision in the MATLAB/Psychtoolbox software environment. The setup is synchronized with electroencephalography and IR eye-tracking measurements. We report measures of HDR visual acuity and the discovery of a novel phenomenon—that abrupt darkening (from 400 to 4 cd/m^2) engages contextual facilitation, distorting the perceived orientation of a high-contrast central target. Surprisingly, the facilitation effect depended on luminance similarity, contradicting both classic divisive and subtractive models of contextual normalization.

Requirements Traceability

2010 ◽  
pp. 102-120
Author(s):  
Elias Canhadas Genvigir ◽  
Nandamudi Lankalapalli Vijaykumar
Keyword(s):  
Software Development ◽  
Change Management ◽  
Requirements Engineering ◽  
Software Requirements ◽  
Requirements Management ◽  
Requirements Traceability

This chapter presents a research about the Software Requirements Traceability. The main elements of traceability, definitions, problems and prospects are presented. The chapter is organized by topics and its beginning is a review about requirements engineering, its categories (Elicitation, Analysis and Negotiation, Documentation, Validation, and Management) and its role in software development. Afterwards, the requirements management and its elements (Identification, Change Management and Traceability) are described. Traceability is discussed; its aspects and problems are exploited as well as its classifications, techniques, links, metrics and models. Finally the Conclusion presents the main points that can be explored in future researches.

A Novel Approach to Change Management in Requirements Engineering Context

2015 ◽  
Vol 7 (3) ◽  
pp. 18-44 ◽  
Author(s):  
Soumia Bendakir ◽  
Nacereddine Zarour ◽  
Pierre Jean Charrel
Keyword(s):  
Change Management ◽  
Requirements Engineering ◽  
Source Code ◽  
User Requirements ◽  
Requirements Management ◽  
Multi Agent System ◽  
Novel Approach ◽  
Requirements Change ◽  
Multi Agent ◽  
The Cost

Requirements change management (RCM) is actually an inevitable task that might be considered in system development's life cycle, since user requirements are continuously evolving (some are added, others are modified or deleted). A large majority of studies have examined the issue of change, while most of them focused on the design and source code, requirements were often forgotten, even though, the cost of fixing the defect and introduced error due to the requirements is less higher compared to the cost of error in design and implementation. For this purpose, this work focuses on change issues in the requirements engineering (RE) context, which contains the complete initial specification. Properties such as adaptability, perception, and cooperation of the multi-agent system (MAS) allow managing changing requirements in a controlled manner. The main objective of this work is to develop an agent-oriented approach which will be effective in the requirements management to be adapted to changes in their environments.

Using a Common Information Model as a Methodological Basis for a Tool-supported Requirements Management Process

1999 ◽  
Vol 9 (1) ◽  
pp. 1437-1441 ◽  
Author(s):  
Gisela John ◽  
Matthias Hoffmann ◽  
Matthias Weber ◽  
Martin Nagel ◽  
Carsten Thomas
Keyword(s):  
Information Model ◽  
Management Process ◽  
Requirements Management ◽  
Methodological Basis ◽  
Common Information ◽  
Common Information Model

Developing and Implementing Ai-Based Classifier for Requirements Engineering

2021 ◽  
Author(s):  
Santeri Myllynen ◽  
Ilpo Suominen ◽  
Tapani Raunio ◽  
Rasmus Karell ◽  
Jussi Lahtinen
Keyword(s):  
Power Plant ◽  
Nuclear Power Plant ◽  
Requirements Engineering ◽  
Language Processing ◽  
Management System ◽  
Nuclear Power ◽  
Requirements Management ◽  
Related System ◽  
Data Comparison

Abstract In nuclear power plant projects, requirements engineering manages the sheer volume of requirements, typically characterized by descriptive and non-harmonized requirements. Large projects may have tens of thousands to hundreds of thousands of requirements to be managed and fulfilled. There are two main issues impeding requirements analysis; tortuous requirements to be interpreted, and humans' very limited ability to concentrate on a specific task. Therefore, it has been recognized that artificial intelligence (AI) algorithms could have potential to support designers' decision-making in classifying and allocating nuclear power plant requirements. This paper presents our work on developing an AI-based requirements classifier utilizing natural language processing (NLP) and its integration with the requirements management system. The focus is on the classification of nuclear power industry-specific requirements utilizing deep learning-based NLP. Three classifiers are compared with each other and the corresponding results are presented. The results include predetermined requirement classes, manually gathered and classified data, comparison of three models and their classification accuracies, microservice system architecture and integration of the established classifier with the requirements management system. As the performance of the requirements classifier and related system has been successfully demonstrated, future AI-specific development and studies are suggested to focus on atomizing multi-class requirements, combining similar requirements into one, checking requirements syntax and utilizing unsupervised learning for clustering. Furthermore, new and advantageous requirement classes and hierarchies are suggested to be developed while also improving current datasets both quantitatively and qualitatively.

Organizational and Funding Options for Markup Vocabulary Creation and Maintenance

2018 ◽  
Author(s):  
Todd Carpenter
Keyword(s):  
Decision Making ◽  
Intellectual Property ◽  
Organizational Structure ◽  
Real World ◽  
Management Process ◽  
Consensus Model ◽  
The Creation ◽  
Maintenance Selection ◽  
Volunteer Time ◽  
Selection Of

There are many ways to create a markup vocabulary and many forums in which it can be done. Creating and maintaining markup vocabularies requires significant ongoing volunteer time and effort, significant funding, or both. In light of this, it often makes sense for a multi-institution group to undertake the creation and management process, particularly when interchange is a goal. The community has examples of this consensus model, such as the TEI (which was created by a grant-supported project and is maintained by a consortium created for the purpose) and the STS (which was originally a derivative of JATS, further developed by ISO, and then donated to NISO for the establishment of consensus and for maintenance). Selection of an organizational home and source of funding can have marked effects on vocabularies. The organizational structure affects representation, who has a voice in the process, intellectual property concerns (e.g., patents, copyrights, other standards), and decision making policies. Costs involved in creating and maintaining markup vocabularies begin at conception and continue through development into maintenance and promotion. These costs include editing, hosting, publishing and distribution, and management of the standards process. Real-world examples of the organization and funding of successful markup vocabularies will provide patterns others may find useful.

Definitions and Applications of Augmented/Virtual Reality: A Survey

2021 ◽  
Vol 9 (3) ◽  
pp. 279-285
Keyword(s):  
Virtual Reality ◽  
Augmented Reality ◽  
Real World ◽  
Software Environment ◽  
The Real ◽  
Virtual And Augmented Reality ◽  
Over Time

Reality is shaped differently in software environments through Virtual Reality VR and augmented Reality AR, it has a remarkable position and an important background with its role of ensuring contact between the software environment and the user. It was popular in the entertainment sector, in particularly industry, but over time, it becomes apparent that there would be a much greater need for VR/AR technologies in different areas dealing with tasks/issues in the real world. In This article we provide an overview of virtual and augmented reality systems and their principal domains of applications.

Sign in / Sign up

Export Citation Format

Share Document