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.
Standard system engineering techniques provide a robust approach to the design, creation and operation of systems but the reliance of these techniques on the generation of text documents reduces understanding of system interactions, makes it difficult to communicate design intent and desired behavior, provides no ability to analyze and assess implementation in the design phase, and can be plagued...
Software systems that do not meet their timing constraints can cause risks. In this work, we propose a comprehensive method for assessing the risk of timing failure by evaluating the software design. We show how to apply best practises in software engineering and well-known Time Petri Net (TPN) modeling and analysis techniques, and we demonstrate the effectiveness of the method with reference to a...
Behavior Trees were invented by Geoff Dromey as a graphical modelling notation. Their design was driven by the desire to ease the task of capturing functional system requirements and to bridge the gap between an informal language description and a formal model. Vital to Dromey's intention is the idea of incrementally building the model out of its building blocks, the functional requirements. This...
Problem frames are an approach to requirements modeling that is gaining increasing attention and popularity. A few meta-models have already been proposed to precisely define the notation and -in some cases- to support the construction of tools. However, the meta-models proposed till now concentrate on modeling the single problem frame, without addressing the whole problem. This is particularly limiting,...
The modularity and customer centric approach of use cases make them the preferred methods for requirement elicitation, especially in iterative software development processes as in agile programming. Numerous guidelines exist for use case style and content, but enforcing compliance to such guidelines in the industry currently requires specialized training and a strongly managed requirement elicitation...
We describe a new paradigm for articulating need-to-protect and need-to-share policies that shows promise for enabling automated derivation of the downgrading rulesets needed to comply with these policies in systems that share data. This new paradigm is based on fine-grained semantic policy specifications in terms of context, content, Purpose, and Anti-purpose that are expressed in a machine-understandable...
This paper studies the problem of coverage management with two emerging formalisms in simulation based validation, namely formal specification of test points and the use of inline temporal assertions. We present methods for checking whether a test-bench with inline assertion covers a set of formal test points. This is particularly useful in developing verification IPs for standard on-chip protocols...
Process acquirement which is the core task of requirement elicitation, lays the foundation for the process modeling. This paper gives the formal description of business processes; additionally the formalized expression of the activity-related products in the C4ISR architecture framework is also given, from which, the elements required by business processes can be acquired. The approach of business...
The classic requirement engineering provides limited technology and inefficient methods for requirements evolution, which leads to great restriction on finish the task of requirements evolution with high-efficiency and high-quality. For resolving above problem, this paper presents a reflective requirements specification for requirements evolution. The reflective requirements specification divides...
In this paper we present an automated support for software model evolution using a formal language constructs. For this, we extended Object Constraint Language (OCL) with actions to define a new language - CAL (Constraint with Action Language), which gives users the ability to evaluate objects change a-priori. We have added a data type, directed acyclic graph (DAG) to CAL to automate model evolution...
Context is a significant factor in deciding the set of requirements relevant to a system (i.e., software product construction), the alternatives the system can adopt to satisfy these requirements, and the quality assessment of each alternative. By context we mean the conditions in the operating environment of an system that influences how the system should behave in different situations. However,...
Requirements engineering visualization is a rapidly growing field of research; however, the specific characteristics of what makes for effective visualizations during a particular engineering phase have not yet been distinguished. Visualizations, when coupled with traditional practices, augment the ability of resulting requirements artifacts to reach a wide range of stakeholders and provide for a...
For the development of new agent programs by reengineering available ones, we consider the artifact A&A metamodel based on the activity theory, and MADeM, using auctions for providing social feedback. The goal is to integrate two applications developed separately based on these models by using GALICIA, a tool based on formal concept analysis and relational concept analysis.
This paper presents the application of the use-case modelling approach in deriving software requirements for an ontology-driven requirements analysis tool, namely OntoRAT in the context of the ontology-driven requirements engineering methodology (OntoREM) project and following the spiral model in carrying out the respective requirements engineering process. In particular, this research has demonstrated...
In large-scale collaborative software projects, thousands of requirements with complex interdependencies and different granularity spreading in different levels are elicited, documented, and evolved during the project lifecycle. Non-technical stakeholders involved in requirements engineering activities rarely apply formal techniques; therefore it is infeasible to automatically detect problems in requirements...
There is a need for rigorous analysis techniques that developers can use to uncover security policy violations in their UML designs. There are a few UML analysis tools that can be used for this purpose, but they either rely on theorem-proving mechanisms that require sophisticated mathematical skill to use effectively, or they are based on model-checking techniques that require a ldquoclosed-worldrdquo...
It is very costly if a software project development has to recover from an error that is due to a mistake made in the construction of the requirements model. Validation of requirements model is thus always an effective means for detecting defects in the requirements model. In this paper, we present an approach to modeling requirements by UML with OCL, and the design of a tool EOC (executable OCL checker),...
Component-based development (CBD) is concerned with enabling the design of software systems by reusing pre developed components. One important activity in CBD is to analyze the business domain and identify potential reusable domain components. Identifying business components, however, can be challenging due to the different nature of the application requirements even within the same domain. Moreover,...
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.