scholarly journals Managing DO-178 Compliance with IBM Rational Platform / Zarządzanie Zgodnością Z DO-178 Przy Użyciu Platformy IBM Rational

2013 ◽  
Vol 25 (1) ◽  
pp. 59-74
Author(s):  
Mehmet Kerim Çakmak
Keyword(s):  
Software Engineering ◽  
Change Management ◽  
Requirements Engineering ◽  
Aerospace Industry ◽  
Engineering Process ◽  
Design And Development ◽  
Validation And Verification ◽  
Roles And Responsibilities ◽  
Software Product ◽  
Software Engineering Process

Abstract DO178 is a standard for avionic software for the aerospace industry which can be used as a guidance to determine if the software product will perform reliability in airborne environment. The standard has 5 different certification levels each of which has a certain set of objectives. The certification levels are determined depending on how critical the system or subsystem is. To address DO- 178 objectives, companies need a defined systems and software engineering process that can delineate workflows, inputs, outputs, roles and responsibilities. The major objectives outlined in the DO-178 standard include; - Requirements engineering - Design and development. - Validation and verification - Engineering tasks, such as configuration and change management In this presentation, we will try to explain the main principles of the DO178 standard very briefly and try to give an insight about how the objectives of this standard can be satisfied.

Displaying Hidden Information in Glossaries

2018 ◽  
pp. 7411-7421 ◽  
Author(s):  
Marcela Ridao ◽  
Jorge Horacio Doorn
Keyword(s):  
Data Mining ◽  
Software Engineering ◽  
Requirements Engineering ◽  
Point Of View ◽  
Human Being ◽  
Engineering Process ◽  
Hidden Information ◽  
Software Engineering Process ◽  
Epistemological Point ◽  
Universe Of Discourse

Requirements Engineering is frequently seen as the activity of the Software Engineering process with fewer tools. Usually there are only available graphic and text editing aids. This is supported by the perception that it is a human being intensive task. This chapter is based on the understanding that such perception is just partially true. Models used along the Requirements Engineering process have underlying structures holding semantic information difficult to be seen by the reader. In fact, models created with well defined objective, were designed to maximize their expressiveness for that objective. However they may hold some useful shadowed information. Here is where a specialized tool may become valuable. From an epistemological point of view, this situation is similar to what happens in data mining. In this chapter, a tool able to make visible any clustering existing in Universe of Discourse glossaries is described. It is based on the automatic constructions of graphs using references embedded in the glossary itself.

Displaying Hidden Information in Glossaries

2019 ◽  
pp. 1373-1385
Author(s):  
Marcela Ridao ◽  
Jorge Horacio Doorn
Keyword(s):  
Data Mining ◽  
Software Engineering ◽  
Requirements Engineering ◽  
Point Of View ◽  
Human Being ◽  
Engineering Process ◽  
Hidden Information ◽  
Software Engineering Process ◽  
Epistemological Point ◽  
Universe Of Discourse

Requirements engineering is frequently seen as the activity of the software engineering process with fewer tools. Usually there are only available graphic and text editing aids. This is supported by the perception that it is a human-being-intensive task. This chapter is based on the understanding that such perception is just partially true. Models used along the requirements engineering process have underlying structures holding semantic information difficult to be seen by the reader. In fact, models created with well-defined objectives were designed to maximize their expressiveness for that objective. However, they may hold some useful shadowed information. Here is where a specialized tool may become valuable. From an epistemological point of view, this situation is similar to what happens in data mining. In this chapter, a tool able to make visible any clustering existing in universe of discourse glossaries is described. It is based on the automatic constructions of graphs using references embedded in the glossary itself.

scholarly journals Linguistics-Based Modeling Methods and Ontologies in Requirements Engineering

2012 ◽  
pp. 236-252 ◽  
Author(s):  
Florian Lautenbacher ◽  
Bernhard Bauer ◽  
Tanja Sieber ◽  
Alejandro Cabral
Keyword(s):  
Software Engineering ◽  
Requirements Engineering ◽  
Engineering Process ◽  
Modeling Methods ◽  
Requirements Specifications ◽  
The People ◽  
Software Engineering Process

Developing new software based on requirements specifications created by business analysts often leads to misunderstanding and lack of comprehension, because of the different backgrounds of the people involved. If requirements specifications instead have a clearly defined structure and comprehensive semantics, this obstacle can be resolved. Therefore, we propose to structure the requirements specifications using existing linguistics-based modeling methods and annotate the used terms with ontologies to enhance the understanding and reuse of these documents during the software engineering process.

scholarly journals Linguistics-Based Modeling Methods and Ontologies in Requirements Engineering

2010 ◽  
Vol 6 (1) ◽  
pp. 12-28
Author(s):  
Florian Lautenbacher ◽  
Bernhard Bauer ◽  
Tanja Sieber ◽  
Alejandro Cabral
Keyword(s):  
Software Engineering ◽  
Requirements Engineering ◽  
Engineering Process ◽  
Modeling Methods ◽  
Requirements Specifications ◽  
The People ◽  
Software Engineering Process

Developing new software based on requirements specifications created by business analysts often leads to misunderstanding and lack of comprehension, because of the different backgrounds of the people involved. If requirements specifications instead have a clearly defined structure and comprehensive semantics, this obstacle can be resolved. Therefore, we propose to structure the requirements specifications using existing linguistics-based modeling methods and annotate the used terms with ontologies to enhance the understanding and reuse of these documents during the software engineering process.

A Security Requirements Engineering Tool for Domain Engineering in Software Product Lines

2011 ◽  
pp. 73-92
Author(s):  
Jesús Rodríguez ◽  
Eduardo Fernández-Medina ◽  
Mario Piattini ◽  
Daniel Mellado
Keyword(s):  
Requirements Engineering ◽  
Software Product Lines ◽  
Product Line ◽  
Security Requirements ◽  
Engineering Process ◽  
Product Lines ◽  
Requirements Engineering Process ◽  
Security Requirements Engineering ◽  
Software Product ◽  
Automated Support

The concepts of Service-Oriented Architectures and Software Product Lines are currently being paid a considerable amount of attention, both in research and in practice. Both disciplines promise to make the development of flexible, cost-effective software systems possible and to support high levels of reuse, and may sometimes be complementary to each other. In both paradigms, security is a critical issue, although most of the existing product line practices do not comprise all the security requirements engineering activities or provide automated support through which to perform these activities, despite the fact that it is widely accepted that the application of any requirements engineering process or methodology is much more difficult without a CARE (Computer-Aided Requirements Engineering) tool, since it must be performed manually. Therefore, this chapter shall present a tool denominated as SREPPLineTool, which provides automated support through which to facilitate the application of the security quality requirements engineering process for software product lines, SREPPLine. SREPPLineTool simplifies the management of security requirements in product lines by providing us with a guided, systematic and intuitive manner in which to deal with them from the early stages of product line development, thus simplifying the management and the visualization of artefact variability and traceability links and the integration of security standards, along with the management of the security reference model proposed by SREPPLine.

Sign in / Sign up

Export Citation Format

Share Document