The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
This paper describes the modeling phase of the Aspect-oriented Model-Driven Engineering for Real-Time systems (AMoDE-RT) design approach for embedded real-time system. A Crisis Management System (bCMS) has been modeled with the Unified Modeling Language (UML) and AMoDE-RT modeling guidelines, including the non-functional requirements specification using aspect-oriented concepts by means of using Distributed...
This paper presents the content required for the selection of the modeling approach, a description of the modeling approach sufficient to understand the submitted model, and a description of the submitted model.
This paper presents a feature-oriented approach to requirement and design modeling using the FAMILIAR Domain Specific Language. This language is aimed at being used within different phases of software development, from early requirement definition to high-level design and in certain cases until runtime. Some experiments also demonstrate its usage when reverse engineering domain or technical variability...
Getting the right software requirements under the right environment assumptions is a critical precondition for developing the right software. KAOS is a goal-driven, model-based approach for elaborating a complete, adequate, consistent, and well-structured set of measurable software requirements and environment assumptions. The modeling language and method cover the intentional, structural, functional,...
This paper presents how business and IT requirements are captured with the Systemic Enterprise Architecture Methodology (SEAM). The method is applied to the Car Crash Management System (CMS) — Software Product Line (SPL) case study. The existing business situation is analyzed. We identify the problems and list relevant solutions. We select one of these solutions for which we define the business and...
This paper gives an overview of the Unified Requirements Modeling Language (URMLTM) and shows how it integrates concepts from the hazard analysis, product line modeling, and goal modeling domains. The meta-model is explained by example diagrams showing the concepts and notation of the language. The notation is explained and its major icons are presented. The presentation of the language is followed...
When developing Self Adaptive Systems (SAS), their highly adaptiveness has to be taken into account as early as the requirements elicitation. Because such systems modify their behaviour at run-time in response to changing environmental conditions, Non Functional Requirements (NFR's) play an important role. One has to identify as early as possible the requirements that are adaptable. Because of the...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.