Spelling suggestions: "subject:"softwareintensive systems"" "subject:"softwareintensiver systems""
1 |
Automated Architecture-Based Verification of Safety-Critical SystemsJaradat, Omar Tawffeeq Saleem January 2011 (has links)
Safety-critical systems require high quality and dependability levels, where system correctness and safety are major features to avoid any severe outcome. Time and cost are also important challenges that are imposed during the development process. Describing the behavior of a system in a high level provides a realistic vision and anticipation of the system. This presents a valuable opportunity for verifying the system before wasting the intended resources to develop the system. Architecture Description Languages (ADLs) provide the ability to comprise and represent the system level details of components, interactions and configuration. Architecture Analysis and Design Language (AADL) as a family member of ADLs proved its effectiveness in designing software intensive systems. In this report, we present a case study to validate “An Architecture-Based Verification Technique for AADL Specifications”. The technique involves a combination of model checking and model-based testing approaches adapted to an architectural perspective. The objectives of the verification process are 1) to ensure completeness and consistency of an AADL specification, and 2) to ensure conformance of an implementation with respect to its AADL specification. The technique has only been applied to small examples, and the goal of this thesis work is to validate it against a safety-critical system developed by a major vehicle manufacturer. Validation of the technique begins by investigating the system and specifying it in AADL. The defined verification criteria are subsequently applied to the AADL specification which drives the verification process. The case study presents interesting results while performing the model checking (the completeness and consistency checking). Conformance testing, on the other hand, could not be performed on the implemented system but is an interesting topic for future work.
|
2 |
Architecture-Based Verification of Software-Intensive SystemsJohnsen, Andreas January 2010 (has links)
<p>Development of software-intensive systems such as embedded systems for telecommunications, avionics and automotives occurs under severe quality, schedule and budget constraints. As the size and complexity of software-intensive systems increase dramatically, the problems originating from the design and specification of the system architecture becomes increasingly significant. Architecture-based development approaches promise to improve the efficiency of software-intensive system development processes by reducing costs and time, while increasing quality. This paradox is partially explained by the fact that the system architecture abstracts away unnecessary details, so that developers can concentrate both on the system as a whole, and on its individual pieces, whether it's the components, the components' interfaces, or connections among components. The use of architecture description languages (ADLs) provides an important basis for verification since it describes how the system should behave, in a high level view and in a form where automated tests can be generated. Analysis and testing based on architecture specifications allow detection of problems and faults early in the development process, even before the implementation phase, thereby reducing a significant amount of costs and time. Furthermore, tests derived from the architecture specification can later be applied to the implementation to see the conformance of the implementation with respect to the specification. This thesis extends the knowledge base in the area of architecture-based verification. In this thesis report, an airplane control system is specified using the Architecture Analysis and Description Language (AADL). This specification will serve as a starting point of a system development process where developed architecture-based verification algorithms are applied.</p>
|
3 |
Architecture-Based Verification of Software-Intensive SystemsJohnsen, Andreas January 2010 (has links)
Development of software-intensive systems such as embedded systems for telecommunications, avionics and automotives occurs under severe quality, schedule and budget constraints. As the size and complexity of software-intensive systems increase dramatically, the problems originating from the design and specification of the system architecture becomes increasingly significant. Architecture-based development approaches promise to improve the efficiency of software-intensive system development processes by reducing costs and time, while increasing quality. This paradox is partially explained by the fact that the system architecture abstracts away unnecessary details, so that developers can concentrate both on the system as a whole, and on its individual pieces, whether it's the components, the components' interfaces, or connections among components. The use of architecture description languages (ADLs) provides an important basis for verification since it describes how the system should behave, in a high level view and in a form where automated tests can be generated. Analysis and testing based on architecture specifications allow detection of problems and faults early in the development process, even before the implementation phase, thereby reducing a significant amount of costs and time. Furthermore, tests derived from the architecture specification can later be applied to the implementation to see the conformance of the implementation with respect to the specification. This thesis extends the knowledge base in the area of architecture-based verification. In this thesis report, an airplane control system is specified using the Architecture Analysis and Description Language (AADL). This specification will serve as a starting point of a system development process where developed architecture-based verification algorithms are applied.
|
4 |
Stakeholder analysis in software-intensive systems developmentKelanti, M. (Markus) 18 October 2016 (has links)
Abstract
A stakeholder analysis is commonly a part of the requirements engineering process in the development of software systems. It contributes to identifying, analysing, negotiating and validating requirements from multiple stakeholder viewpoints that do not necessary share the same views on a system under development and do not necessary express themselves using a similar language. Stakeholder analysis is often integrated into a used development method or practice and doesn’t necessarily appear as a separate process.
The increase in software size, availability and use in different appliances, however, requires more from the stakeholder analysis than has been recognized in Software Engineering literature. The increasing scale of software systems and connections to other systems increase the number of involved stakeholders complicating the stakeholder analysis. In addition, how the actual stakeholder analysis should be implemented in large scale software development and how it supports the development effort is problematic in practice.
The purpose of this thesis is to study the role and purpose of a stakeholder analysis in a large-scale software-intensive systems development. In this thesis, an empirical approach is taken to study the large-scale software-intensive systems development as phenomena in order to observe it as a whole. This approach allows this thesis to analyse the phenomena from different perspectives in order to identify and describe the nature and purpose of a stakeholder analysis in large-scale software-intensive systems development.
The contribution of this thesis is the following. First, the thesis contributes to both the practical and scientific community by describing the role of stakeholder analysis in the software-intensive systems development process. Secondly, it demonstrates how a stakeholder analysis can be implemented in a large-scale software-intensive systems development process. / Tiivistelmä
Sidosryhmäanalyysi on yleensä osa vaatimusmäärittelyprosessia ohjelmistojärjestelmien kehityksessä. Se edesauttaa vaatimusten tunnistamista, analysointia, sopimista ja vahvistamista useiden eri sidosryhmien näkökulmasta tilanteissa, missä eri sidosryhmät eivät välttämättä jaa samaa näkökulmaa kehitettävään järjestelmään ja eivät välttämättä käytä samaa kieltä ilmaistakseen itseään. Sidosryhmäanalyysi on usein integroitu suoraan käytettyyn kehitysmenetelmään tai käytäntöön ja ei välttämättä ilmene erillisenä prosessina.
Ohjelmiston koon kasvaessa ja yhteyksien lisääntyminen yhä useampiin laitteisiin on johtanut tilanteeseen, missä sidosryhmäanalyysilta vaaditaan yhä enemmän kuin kirjallisuudessa on aiemmin tunnistettu. Ohjelmistojärjestelmien alati kasvava koko ja yhteyksien lisääntyminen muihin järjestelmiin kasvattaa sidosryhmien määrää vaikeuttaen sidosryhmäanalyysin tekemistä. Lisäksi on ongelmallista, että miten sidosryhmäanalyysin tulisi tukea suuren mittakaavan ohjelmistotuotantoa ja miten se käytännössä toteutetaan tällaisessa ympäristössä.
Tämän väitöskirjan tavoitteena on tutkia sidosryhmän roolia ja tarkoitusta suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Tutkimus on toteutettu empiirisellä lähestymistavalla tarkkailemalla suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotantoa kokonaisuutena. Tämä lähestymistapa mahdollistaa kokonaisuuden analysoinnin eri näkökulmista, jotta sidosryhmäanalyysin luonne ja tarkoitus voidaan tunnistaa ja kuvata suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa.
Väitöskirjan tulosten kontribuutio jakautuu kahteen osaan. Ensimmäiseksi väitöskirjan tulokset auttavat sekä tiedeyhteisöä ja käytännön työtä tekeviä kuvaamalla sidosryhmäanalyysin suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Toiseksi tulokset havainnollistavat miten sidosryhmäanalyysi voidaan toteuttaa suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotekehitysprosessissa.
|
5 |
Decision Support for Product Management of Software Intensive ProductsKhurum, Mahvish January 2011 (has links)
Context: At the core of choosing what features and level of quality to realize, and thus offer a market or customer, rests on the ability to take decisions. Decision-making is complicated by the diverse understanding of issues such as priority, consequence of realization, and interpretations of strategy as pertaining to the short-term and long-term development of software intensive products. The complexity is further compounded by the amount of decision support material that has to be taken into account, and the sheer volume of possible alternatives that have to be triaged and prioritized; thousands or even tens of thousands of requirements can be the reality facing a company. There is a need to develop the functionality that is strategically most significant, while satisfying customers and being competitive, time efficient, cost effective, and risk minimizing. In order to achieve a balance between these factors, all the stakeholders, within an organization, need to agree on the strategic aspects and value considerations to be considered, and their corresponding relative importance. Objective: The objective of this thesis is to provide enhanced decision support for product managers faced with decision-making challenges. This involves, but is not limited to, enhancing the alignment between the product and portfolio management with respect to product strategies, and enabling the use of value as a basis for product management and development related decisions. Method: A number of empirical studies, set in industry, have been performed. The research methods used span from systematic mapping, and systematic reviews to case studies, all aligned to identify possibilities for improvement, devise solutions, and incrementally evaluate said solutions. Close collaboration with industry partners was at the core of the research presented in this thesis. Result: The MASS method presented in this thesis can be used to evaluate strategic alignment and identify possible root causes for misalignment. To strengthen strategic alignment, the Software Value Map and corresponding decision support material, proposed in the thesis, can be used by product managers for making effective and efficient strategic decisions in relation to portfolios, products and process improvement, following a systematic and aligned process. Conclusions: The area of software product management, in the context of market-driven software intensive product development, is a field with unique challenges. The specifics of the solutions are based on industry case studies performed to gauge state-of-the-art, as well as identify the main challenges. The decision support developed takes the form of maps and frameworks that support software product management on product and portfolio level decisions, strategic alignment, value-based requirements selection, and value-based process improvement.
|
6 |
Conception d’architecture de système-de-systèmes à logiciel prépondérant dirigée par les missions / Mission-driven Software-intensive System-of-Systems Architecture DesignFerreira silva, Eduardo 17 December 2018 (has links)
La formulation des missions est le point de départ du développement de systèmes-de- systèmes, étant utilisée comme base pour la spécification, la vérification et la validation d’architectures de systèmes-de-systèmes. Élaborer des modèles d’architecture pour systèmes-de-systèmes est une activité complexe, cette complexité reposant spécialement sur les comportements émergents, c'est-à-dire, des comportements issus des interactions entre les parties constituantes d’un système-de-systèmes qui ne peuvent pas être prédits même si on connaît tous les comportements de tous les systèmes constituants. Cette thèse adresse le lien synergique entre mission et architecture dans le cadre des systèmes-de-systèmes à logiciel prépondérant, en accordant une attention particulière aux comportements émergents créés pour réaliser les missions formulées. Nous proposons ainsi une approche pour la conception d’architecture de systèmes-de-systèmes dirigée par le modèle de mission. Dans notre approche, le modèle de mission sert à dériver et à valider les architectures de systèmes-de-systèmes. Dans un premier temps, nous générons la structure de l’architecture à l’aide de transformations de modèles. Ensuite, lors que l’architecte spécifie les aspects comportementaux, la description de l’architecture résultante est validée à l’aide d’une démarche conjointe qui comprend à la fois la vérification des propriétés spécifiées et la validation par simulation des comportements émergents. La formalisation en termes de logique temporelle et la vérification statistique de modèles sont les fondements formels de l’approche. Un outil mettant en œuvre l’ensemble de l’approche a été également développé et expérimenté. / The formulation of missions is the starting point to the development of Systems-of-Systems (SoS), being used as a basis for the specification, verification and validation of SoS architectures. Specifying, verifying and validating architectural models for SoS are complex tasks compared to usual systems, the inner complexity of SoS relying specially on emergent behaviors, i.e. features that emerge from the interactions among constituent parts of the SoS which cannot be predicted even if all the behaviors of all parts are completely known. This thesis addresses the synergetic relationship between missions and architectures of software-intensive SoS, giving a special attention to emergent behaviors which are created for achieving formulated missions. We propose a design approach for the architectural modeling of SoS driven by the mission models. In our proposal, the mission model is used to both derive, verify and validate SoS architectures. As first step, we define a formalized mission model, then we generate the structure of the SoS architecture by applying model transformations. Later, when the architect specifies the behavioral aspects of the SoS, we generate concrete SoS architectures that will be verified and validated using simulation-based approaches, in particular regarding emergent behaviors. The verification uses statistical model checking to verify whether specified properties are satisfied, within a degree of confidence. The formalization in terms of a temporal logic and statistical model checking are the formal foundations of the developed approach. A toolset that implements the whole approach was also developed and experimented.
|
7 |
A Proposed Model For Turkish Land Forces Command Software Intensive Systems Acquisition ProcessBilir, Nevzat 01 January 2003 (has links) (PDF)
Turkish Land Forces Command uses information technology opportunities to
satisfy its needs arising from the obligation for being a strong army. One of the main
difficulties in using information technologies is the acquisition of these systems.
This thesis reviews the fundamentals of software intensive systems
acquisition process and then proposes a new model for Turkish Land Forces
Command. Software acquisition process models are discussed and compared with
each other. The current Turkish Land Forces Command acquisition process is studied
to state the management, legal, resource, and industrial problems within the
comtemporary models& / #8217 / perspective. The focus of this thesis study is proposing an
acquisition model based on four international models, successes of which have been
proven.
|
Page generated in 0.0695 seconds