scholarly journals T-Reqs: Tool Support for Managing Requirements in Large-Scale Agile System Development

Author(s):  
Eric Knauss ◽  
Grischa Liebel ◽  
Jennifer Horkoff ◽  
Rebekka Wohlrab ◽  
Rashidah Kasauli ◽  
...  
2021 ◽  
Vol 22 (11) ◽  
pp. 5793
Author(s):  
Brianna M. Quinville ◽  
Natalie M. Deschenes ◽  
Alex E. Ryckman ◽  
Jagdeep S. Walia

Sphingolipids are a specialized group of lipids essential to the composition of the plasma membrane of many cell types; however, they are primarily localized within the nervous system. The amphipathic properties of sphingolipids enable their participation in a variety of intricate metabolic pathways. Sphingoid bases are the building blocks for all sphingolipid derivatives, comprising a complex class of lipids. The biosynthesis and catabolism of these lipids play an integral role in small- and large-scale body functions, including participation in membrane domains and signalling; cell proliferation, death, migration, and invasiveness; inflammation; and central nervous system development. Recently, sphingolipids have become the focus of several fields of research in the medical and biological sciences, as these bioactive lipids have been identified as potent signalling and messenger molecules. Sphingolipids are now being exploited as therapeutic targets for several pathologies. Here we present a comprehensive review of the structure and metabolism of sphingolipids and their many functional roles within the cell. In addition, we highlight the role of sphingolipids in several pathologies, including inflammatory disease, cystic fibrosis, cancer, Alzheimer’s and Parkinson’s disease, and lysosomal storage disorders.


Author(s):  
Nenad Jukic ◽  
Miguel Velasco

Defining data warehouse requirements is widely recognized as one of the most important steps in the larger data warehouse system development process. This paper examines the potential risks and pitfalls within the data warehouse requirement collection and definition process. A real scenario of a large-scale data warehouse implementation is given, and details of this project, which ultimately failed due to inadequate requirement collection and definition process, are described. The presented case underscores and illustrates the impact of the requirement collection and definition process on the data warehouse implementation, while the case is analyzed within the context of the existing approaches, methodologies, and best practices for prevention and avoidance of typical data warehouse requirement errors and oversights.


2010 ◽  
Vol 1 (3) ◽  
pp. 66-76
Author(s):  
Nenad Jukic ◽  
Miguel Velasco

Defining data warehouse requirements is widely recognized as one of the most important steps in the larger data warehouse system development process. This paper examines the potential risks and pitfalls within the data warehouse requirement collection and definition process. A real scenario of a large-scale data warehouse implementation is given, and details of this project, which ultimately failed due to inadequate requirement collection and definition process, are described. The presented case underscores and illustrates the impact of the requirement collection and definition process on the data warehouse implementation, while the case is analyzed within the context of the existing approaches, methodologies, and best practices for prevention and avoidance of typical data warehouse requirement errors and oversights.


Author(s):  
Holger Giese ◽  
Stefan Henkler ◽  
Martin Hirsch ◽  
Vladimir Rubin ◽  
Matthias Tichy

Software has become the driving force in the evolution of many systems, such as embedded systems (especially automotive applications), telecommunication systems, and large scale heterogeneous information systems. These so called software-intensive systems, are characterized by the fact that software influences the design, construction, deployment, and evolution of the whole system. Furthermore, the development of these systems often involves a multitude of disciplines. Besides the traditional engineering disciplines (e.g., control engineering, electrical engineering, and mechanical engineering) that address the hardware and its control, often the system has to be aligned with the organizational structures and workflows as addressed by business process engineering. The development artefacts of all these disciplines have to be combined and integrated in the software. Consequently, software-engineering adopts the central role for the development of these systems. The development of software-intensive systems is further complicated by the fact that future generations of software-intensive systems will become even more complex and, thus, pose a number of challenges for the software and its integration of the other disciplines. It is expected that systems become highly distributed, exhibit adaptive and anticipatory behavior, and act in highly dynamic environments interfacing with the physical world. Consequently, modeling as an essential design activity has to support not only the different disciplines but also the outlined new characteristics. Tool support for the model-driven engineering with this mix of composed models is essential to realize the full potential of software-intensive systems. In addition, modeling activities have to cover different development phases such as requirements analysis, architectural design, and detailed design. They have to support later phases such as implementation and verification and validation, as well as to systematically and efficiently develop systems.


Author(s):  
Janis Stirna ◽  
Marite Kirikova

This paper analyses the potential of using Enterprise Modelling (EM) in agile information system development projects on the basis of a number of empirical findings. We outline the current issues and challenges that projects using agile development approaches are facing. To address these challenges we analyse what are the objectives of using EM in agile development projects and give recommendations concerning the modelling process and tool support.


1987 ◽  
Vol 16 (1) ◽  
pp. 57-64 ◽  
Author(s):  
Squy G. Wallace ◽  
Paul Sheffield

Application of the Instructional System Development (ISD) model to large scale training development projects has frequently been criticized for failing to develop and deliver training materials in a timely manner. This article discusses the advantage of using a computer-generated graphic portrayal of task analysis data and the use of computer macros to streamline the training development process.


2009 ◽  
Vol 55 (No. 1) ◽  
pp. 20-24 ◽  
Author(s):  
I. Rábová

Up to date business is managed by large-scale different rules that regulate how the business acts and how it is structured. We find the rules in law, regulation, business policy document, procedures manual, system documentation, memoranda etc. These reference resources may provide the specific basis for a rule or offer a background, context or explanation of the business rule. In the recent years, it has been discovered that business rules constitute an entire body of knowledge that has not been adequately addressed in either the analysis or design phases of the information system development. Typically, business rules have been buried in the program code or in the database structures. The article deals with the business rules approach and rule technology and helps to identify the business and technical opportunities they afford to the company. It offers the business process model and its integration with business rules. This approach could provide business analysts with an essential approach to understanding, redesigning and communicating what really happens in the business processes (in agricultural area). It serves to understand the business impact of any change in small and medium-sized organizations. We use the UML notation and its business model extension.


Sign in / Sign up

Export Citation Format

Share Document