scholarly journals An Approach for Evolution-Driven Method Engineering

2011 ◽  
pp. 80-101 ◽  
Author(s):  
Jolita Ralyte ◽  
Colette Rolland ◽  
Mohamed Ben Ayed
Keyword(s):  
Software Requirements ◽  
Specific Method ◽  
User Requirements ◽  
Method Engineering ◽  
Evolutionary Perspective ◽  
Research Project ◽  
New Model ◽  
Meta Model ◽  
Method Model ◽  
Method Construction

This chapter considers the evolutionary perspective of method engineering. It presents an approach for method engineering supporting evolution of an existing method, model, or meta-model into a new one satisfying a different engineering objective. The authors hope that this approach could be helpful for a project-specific method construction. This approach proposes several different strategies to evolve from the initial paradigm model to a new one and provides guidelines supporting these strategies. The approach has been evaluated in the Franco-Japanese research project around the Lyee methodology. A new model called Lyee User Requirements Model has been obtained as an abstraction of the Lyee Software Requirements Model. The chapter illustrates this evolution case.

Traceability Guideline for Software Requirements and UML Design

2016 ◽  
Vol 26 (01) ◽  
pp. 87-113 ◽  
Author(s):  
Hyun-Seok Min
Keyword(s):  
South Korea ◽  
Software Architecture ◽  
Software Requirements ◽  
Software Developers ◽  
Process Step ◽  
Meta Model ◽  
Traceability Link ◽  
Software Requirement ◽  
Practical Guideline ◽  
Uml Diagrams

Traceability between software requirements and UML design helps requirement engineers and software developers understand the project goal and software architecture. However, the traceability mapping between the two elements is not well-defined and as a result there is no consistent way to make the traceability between two. A practical guideline is proposed for the traceability between software requirement and UML design. The guideline includes meta-model and process step. The process step defines detailed processes and most importantly, the Requirement-type and its mapping to UML diagrams. Requirements can be categorized based on their aspects and this categorization can be made as Requirement-type. This pre-defined Requirement-type is added to each requirement and this Requirement-type enforces to use certain types of UML diagrams as solutions. This mapping between each Requirement-type and UML diagram is the key of proposed guideline. With the help of the Requirement-type and mapping, traceability link can be made easily and checked automatically. The guideline was applied to the Missile Project and Helicopter Project of ADD (Agency of Defense Development) in South Korea.

scholarly journals Adaptive Concept Map Approach for Software Requirements Validation

2019 ◽  
Vol 4 (1) ◽  
pp. 37-46
Author(s):  
Ahmed A. Ahmed ◽  
◽  
Ayman E. Khedr ◽  
Sherif A. Kholeif ◽  
◽  
...  
Keyword(s):  
Software Requirements ◽  
User Requirements ◽  
Requirements Validation ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Graphical Technique ◽  
Graphical Notations ◽  
Description Languages ◽  
Requirements Document ◽  
Early Phases

Requirements validation is one of the most significant and critical parts of the requirements engineering. This activity ensures that the set of requirements is accurate, right, complete, and consistent. Requirements validation is considered as the key activity because mistakes found in a software requirements document can lead to extensive rework costs when they are discovered either during development or after the system is in service. There are some commonly used bases to validate user requirements such as: Natural language, Design description languages, Graphical notations and Mathematical specification languages. Whereas the graphical notations are the most suitable means to be used in software requirements validation because it is easy to understand, and it can be easily created by analyst and time took. Therefore, this paper adopts the map concept which is a graphical technique for discovering the hidden flaws in software requirements in the early phases of software development lifecycle.

scholarly journals Adding Temporal Characteristics to Geographical Schemata and Instances: A General Framework

2018 ◽  
Vol 1 ◽  
pp. 1-6
Author(s):  
Morishige Ota
Keyword(s):  
Real World ◽  
General Framework ◽  
General Feature ◽  
Geospatial Data ◽  
Feature Model ◽  
Current Application ◽  
New Model ◽  
Meta Model ◽  
Temporal Characteristics ◽  
Modeling Methods

This paper proposes the temporal general feature model (TGFM) as a meta-model for application schemata representing changes of real-world phenomena. It is not very easy to determine history directly from the current application schemata, even if the revision notes are attached to the specification. To solve this problem, the rules for description of the succession between previous and posterior components are added to the general feature model, thus resulting in TGFM. After discussing the concepts associated with the new model, simple examples of application schemata are presented as instances of TGFM. Descriptors for changing properties, the succession of changing properties in moving features, and the succession of features and associations are introduced. The modeling methods proposed in this paper will contribute to the acquisition of consistent and reliable temporal geospatial data.

scholarly journals Requirements Elicitation Problems: A Literature Analysis

10.28945/2211 ◽  
2015 ◽  
Vol 12 ◽  
pp. 071-082 ◽  
Author(s):  
Bill Davey ◽  
Kevin R. Parker
Keyword(s):  
Requirements Elicitation ◽  
Software Requirements ◽  
User Requirements ◽  
Literature Analysis ◽  
Software Projects ◽  
Problem Types

Requirements elicitation is the process through which analysts determine the software requirements of stakeholders. Requirements elicitation is seldom well done, and an inaccurate or incomplete understanding of user requirements has led to the downfall of many software projects. This paper proposes a classification of problem types that occur in requirements elicitation. The classification has been derived from a literature analysis. Papers reporting on techniques for improving requirements elicitation practice were examined for the problem the technique was designed to address. In each classification the most recent or prominent techniques for ameliorating the problems are presented. The classification allows the requirements engineer to be sensitive to problems as they arise and the educator to structure delivery of requirements elicitation training.

scholarly journals ON THE NEW MODEL OF ADAPTIVE INTELLOGENCE

2021 ◽  
Author(s):  
А.Л. Катков
Keyword(s):  
General Theory ◽  
Religious Institutions ◽  
Adaptive Function ◽  
New Model ◽  
Meta Model ◽  
New Approaches ◽  
Intellectual Function ◽  
Scientific Ethics ◽  
Definition Of ◽  
Traditional Understanding

В статье рассматривается традиционное понимание адаптивной функции интеллекта, обоснованное в трудах Ж.Пиаже, Г.Култона и многих других авторов. Даются исчерпываю щие представления о принципиально новых подходах к пониманию адаптивно интеллектуальной функции, разработанных в контексте общей теории психотерапии. Приводится краткое и развернутое определение новой модели адаптивного интеллекта. Обсуждаются эвристическ ие следствия данной модели в психотерапии, в частности в мета модели социальной психотерапии, в сфере деятельности научных и религиозных институтов, а также в сфере научной этики. Делаются выводы о состоятельности и перспективности использования данной мод ели в науке и практике. The article examines the traditional understanding of the adaptive function of intelligence, substantiated in the works of J. Piaget, G. Coulton and many other authors. Exhaustive ideas about fundamentally new approaches to understanding the adaptive-intellectual function, developed in the context of the general theory of psychotherapy, are given. A short and detailed definition of a new model of adaptive intelligence is given. The heuristic consequences of this model in psychotherapy, in particular in the meta-model of social psychotherapy, in the field of activities of scientific and religious institutions, as well as in the field of scientific ethics are discussed. Conclusions are made about the consistency and prospects of using this model in science and practice.

scholarly journals Born to be OPTI. A new model for participatory museum management

1970 ◽  
pp. 105-123
Author(s):  
Lorena Sancho Queroi ◽  
Kalle Kallio ◽  
Linda Heinonen
Keyword(s):  
Cultural Citizenship ◽  
Management Tool ◽  
Management Model ◽  
Participatory Management ◽  
Cultural Institutions ◽  
Current Management ◽  
Research Project ◽  
Business World ◽  
New Model ◽  
Museum Management

Society in the Museum (SoMus) is a research project in the field of sociomuseology where culture is viewed as an essential axis of developmental processes and museums as key tools for the exercise of cultural citizenship. The project intends to identify, analyse, systematize and disclose some of the most interesting emerging models of participatory management underway in four European museums. In this article we present the anatomy, the strategy and the challenges of one of the Nordic partners, the Finnish Labour Museum, and its current management tool, the OPTI Participatory Management Model. The model has been adapted from the business world to serve as a critical museological tool and to enhance participation in cultural institutions. It is a response to the paradigmatic transition that museums face when actively engaging in a participative culture.

Requirements Specification using User Stories

2011 ◽  
pp. 71-89 ◽  
Author(s):  
V. Monochristou ◽  
M. Vlachopoulou
Keyword(s):  
Software Development ◽  
Interaction Design ◽  
System Development ◽  
Requirements Specification ◽  
Software Requirements ◽  
User Requirements ◽  
Agile Methodologies ◽  
User Stories ◽  
Software Requirements Specification ◽  
Waterfall Model

Collecting and analyzing user requirements is undoubtedly a really complicated and often problematic process in software development projects. There are several approaches, which suggest ways of managing user’s requirements; some of the most well-known are IEEE 830 software requirements specification (SRS), use cases, interaction design scenarios, etc. Many software experts believe the real user requirements emerge during the development phase. By constantly viewing functional sub-systems of the whole system and participating, in fact, in all phases of system development, customers/users can revise their requirements by adding, deleting, or modifying them. However, in order for this to become possible, it is important to adopt a totally different approach than the traditional one (waterfall model approach), concerning not only the management of user’s requirements, but also the entire software development process in general. Agile methodologies represent this different approach since the iterative and incremental way of development they propose includes user requirements revision mechanisms and user active participation throughout the development of the system. The most famous approach concerning requirements specification among the supporters of the agile methodologies is probably user stories. User stories and their main characteristics are thoroughly demonstrated in this chapter. After reading this chapter, the authors hope that the reader may have gained all the basic understanding regarding the use of user stories.

Sign in / Sign up

Export Citation Format

Share Document