Software design

Top PDF Software design:

ArchBot: Chatbot für Software Design und Review (SA)

ArchBot: Chatbot für Software Design und Review (SA)

Projektplan Chatbot für Software Design und Review 3. Risikomanagement Um das Risiko des Projektfehlschlags zu minimieren sind Teilrisiken im Projekt identifiziert wor- den. Die Risikoaufzählung umfasst die wahrscheinlichsten technischen Risiken, erhebt jedoch keinen Anspruch auf Vollständigkeit. Der abgeschätzte gewichtete Schaden der Risiken wird bei der Zeit- planung als Reserve miteinbezogen. Dieser wird aus allen berücksichtigten Risiken berechnet. Die Gesamtlaufzeit des Projekts wird um diese Reserve verlängert, ohne jedoch die Schätzung einzelner Arbeitspakete anzupassen. Die Risiken werden im Gitlab Wiki geführt und ständig aktualisiert. Der Vorteil dieser Lösung ist, dass das Wiki git-basiert ist und somit eine erleichterte Übersicht der Risikoentwicklung über die gesamte Projektlaufzeit bietet.
Mehr anzeigen

82 Mehr lesen

Model Transformation For Validation Of Software Design

Model Transformation For Validation Of Software Design

The counter example details why the model doesn’t satisfy the specification. By studying the counter example, we can pinpoint the source error in the model, correct the model, and try again. The idea of this iterative process is to ensure that the model satisfies enough system properties. There are several model checking tools such as SPIN [Hol04b], FDR [(Lt], UPPAAL [BLPY97], and NuSMV [Nus02]. SPIN is one of the most popular software tool that can be used for the for- mal verification of distributed software systems [Hol04b]. SPIN uses a high-level language to specify system descriptions, called PROMELA. SPIN has also been used to trace logical design errors in distributed systems design, such as operating systems, data communications protocols etc. The tool checks the logical consistency of a specification. It reports on deadlocks, un- specified receptions, flags incompleteness, race conditions, and unwarranted assumptions about the relative speeds of processes. SPIN and the model checkers mentioned above do not ac- cept software design directly, but use logic and automata formalisms for describing models and specifications.
Mehr anzeigen

217 Mehr lesen

Software engineering whispers : The effect of textual vs. graphical software design descriptions on software design communication

Software engineering whispers : The effect of textual vs. graphical software design descriptions on software design communication

explaining approaches in the two groups. On the one hand, the Explainers of a TSD tended to explain the three modules of the MVC sequentially: Firstly the model entities, then the controllers, and lastly the views, as these modules are orderly presented in the textual doc- ument. We think that this trend is intrinsically imposed by the nature of textual descriptions where the knowledge is presented sequentially on a number of consecutive ordered pages. On the other hand, the Explainers of the GSD had more freedom in explaining the design. Indeed according to their explaining preferences, the Explainers of the GSD tended to jump back and forth between the three MVC modules when explaining the design. Based on this, we suggest that a GSD has an advantage over the TSD in unleashing Explainers’ expres- siveness when explaining the design, as well as in helping navigation and getting a better overview of the design. However, developers might not have this advantage when explain- ing many GSDs (e.g., many UML diagrams) spread on different pages within a software design documentation.
Mehr anzeigen

45 Mehr lesen

ArchBot: Chatbot für Software Design und Review (BA)

ArchBot: Chatbot für Software Design und Review (BA)

Projektplan Chatbot für Software Design und Review 3. Risikomanagement Um das Risiko des Projektfehlschlags zu minimieren sind Teilrisiken im Projekt identifiziert wor- den. Die Risikoaufzählung umfasst die wahrscheinlichsten technischen Risiken, erhebt jedoch keinen Anspruch auf Vollständigkeit. Der abgeschätzte gewichtete Schaden der Risiken wird bei der Zeit- planung als Reserve miteinbezogen. Dieser wird aus allen berücksichtigten Risiken berechnet. Die Gesamtlaufzeit des Projekts wird um diese Reserve verlängert, ohne jedoch die Schätzung einzelner Arbeitspakete anzupassen. Die Risiken werden im Gitlab Wiki geführt und ständig aktualisiert. Der Vorteil dieser Lösung ist, dass das Wiki git-basiert ist und somit eine erleichterte Übersicht der Risikoentwicklung über die gesamte Projektlaufzeit bietet.
Mehr anzeigen

82 Mehr lesen

Extensible Software Design of a Multi-Agent Transport Simulation

Extensible Software Design of a Multi-Agent Transport Simulation

Unfortunately, invisibility is not reached. This paper explains which methodology and set-up was chosen in the last years in order to improve the first prototypical version of MATSim from 2007. Motivated by the domain-specific perspectives on the software the main goals are Modularity, Reusability and Extensibility. As most users come with a non computer science background practical solutions for achievement of goals are needed. Full knowledge of [1, 2, 3] can not be expected, thus a subset of these concepts is required. This paper reviews the chosen subset. Two software design patterns, i.e. Abstract Factory and Observer [1], in conjunction with some other standard software design approaches improve the main design goals. As example for an extension of the MATSim core algorithm the paper shows how a traffic signal implementation can be attached to MATSim.
Mehr anzeigen

9 Mehr lesen

Coupled model transformations for QoS enabled component-based software design

Coupled model transformations for QoS enabled component-based software design

One approach could be to include the design alternatives in the source model, i.e., by introducing different types of connectors in the model. However, this idea undermines the abstraction property of a model as defined by Stachowiak (1973). Due to the goal-driven abstraction of a model, unimportant details of the modelled objects are omitted. As a consequence, there can be different objects having an equal model. Looking at figure 4.2, this is depicted on the left hand side. There, three different objects have the same model as they only differ in attributes abstracted away by the model’s abstraction rule. The omitted information is irrelevant for the model’s aim. In our example, this means that a RMI based implementation and a SOAP-based implementation have the same model as given in figure 4.1 when aiming at presenting the conceptual structure of the system by removing its realisation details. Abstracting from the concrete connector implementation keeps the model comprehensible and does not overload it with information. Additionally, it may even be infeasible to add all possible types of connector implementations that exist to the model’s constructs as it would imply to include all connector types of all existing and also all future implementations. As a way out, the OMG introduced PIM and PSM models (c.f. section 2.2.3) to separate implementation (platform) dependent aspects from implementation (platform) independent ones.
Mehr anzeigen

320 Mehr lesen

Visualisierung von analytischen Business-Intelligence-Ergebnissen mit SAP-Software (Design Studio, Lumira, SAPUI5 usw.) auf verschiedenen Endgeräten

Visualisierung von analytischen Business-Intelligence-Ergebnissen mit SAP-Software (Design Studio, Lumira, SAPUI5 usw.) auf verschiedenen Endgeräten

Um einen Eindruck zu vermitteln, erfolgte auch eine praktische Umsetzung von Dashboards mit den Programmen SAPUI5, SAP Lumira Discovery sowie SAP Analytics Cloud. Bei den [r]

1 Mehr lesen

Coupled model transformations for QoS enabled component-based software design

Coupled model transformations for QoS enabled component-based software design

• Missing Information in the Source Model: The PCM’s central aim is to allow the creation of architectural models for QoS analysis. To reach this aim, the PCM uses abstractions of middleware specific architectures. Especially, the technical realisa- tion of an architecture is omitted intentionally from PCM model instances. For example, the PCM only contains the information that two components communi- cate but not which communication technology is used to realise it, e.g., SOAP or RMI. In the sense of the OMG’s MDA standard, this kind of information is platform- dependent and hence, has to be added by the respective platform transformation. For this transformation, platform-specific mapping options may exist which config- ure how to map elements in the source model. Either the transformations contains a set of hard-coded options or the software architect can specify them using mark models. In the communication technology example, a mark model could specify which protocol to use on each of the AssemblyConnectors. Depending on the selec- tion of options different extra-functional properties emerge, which will be included into the analysis model by the Coupled Transformations method.
Mehr anzeigen

281 Mehr lesen

Correction to: Software engineering whispers : The effect of textual vs. graphical software design descriptions on software design communication

Correction to: Software engineering whispers : The effect of textual vs. graphical software design descriptions on software design communication

Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium o[r]

1 Mehr lesen

Integrating the aspect of sustainability in methods of software product design

Integrating the aspect of sustainability in methods of software product design

Basically, all participants of the study addressed people related challenges corresponding to mindset, motivation, company culture and work environment. Several interviewees highlighted that the implementation of the guidelines should not be too much effort for the teams as they are used to working with non-functional requirements frameworks and some of the recommendations were already existent in agile methods. (A, G) However, it was emphasized that a new quality attribute requires individual motivation to adapt new routines, processes, paradigms and habits. (A, C, D) Naturally, there are people eager to learn and curious for new impressions, aware of the benefits coming with change. Others may request for incentives to step out of their comfort zone and take the extra mile. (A) As this is a rather sensitive topic, closely related to awareness and mindset, interviewees argue that it should be implemented as a bottom-up approach rather than with top-down regulations. (E) Still, this is highly dependent on the working environment, that is oftentimes volatile and influential, putting a high pressure on development teams that limits their autonomy of decision making. (B, C, D) In order to omit tensions in the team, the successful implementation of sustainability considerations in software design requires an open mindset that encourages their developers to engage and contribute. (E) Further it was mentioned the fact, that expectations may vary widely as people come from different backgrounds and their decision making is different. (I)
Mehr anzeigen

74 Mehr lesen

Design and Implemetation of FPGA based Software Defined Radio Using Simulink HDL Coder

Design and Implemetation of FPGA based Software Defined Radio Using Simulink HDL Coder

are hardware defined with little or no software control; they are fixed in function for mostly consumer items for broadcast reception. They have a short life and are designed to be discarded and replaced [1]. Over the last few years, analog radio systems are being replaced by digital radio systems for various radio applications in military, civilian and commercial spaces. In addition to this, programmable hardware modules are increasingly being used in digital radio systems at different functional levels. Commercial wireless communication industry is currently facing problems due to constant evolution of link-layer protocol standards (2.5G, 3G, and 4G), existence of incompatible wireless network technologies in different countries inhibiting deployment of global roaming facilities and problems in rolling-out new services/features due to wide-spread presence of legacy subscriber handsets [2].
Mehr anzeigen

14 Mehr lesen

Software

Software

Dieser wurde ins Deutsche als Fremdwort übernommen, umgangssprachlich vielleicht sogar rascher als in der Fachliteratur. Die älteren Lehrbücher führen das Wort noch nicht im Sachregister, 8 bis es dann doch vereinzelt in Informatik-Einfüh- rungen erwähnt und erläutert wird: »Als Software bezeichnet man alle Teile einer ADVA [Automatischen Datenverarbeitungsanlage], die in Form von Programmen vorliegen.« 9 Spätestens ab diesem Zeitpunkt aber wurde das Fremdwort so sehr zu

7 Mehr lesen

Design Options for Long-lasting, Efficient and Open Hardware and Software

Design Options for Long-lasting, Efficient and Open Hardware and Software

Sustainable public procurement The public sector has a prominent role to play in implement- ing the policy recommendations for sustainable hardware and software: Tendering and procurement criteria for public au- thorities should be structured in a way that ensures that com- prehensive environmental criteria are taken into account. This means that it gives preference to free and open-source software and devices as well as to those that provide open interfaces and modular designs. The production processes should take place under fair conditions, be transparent and traceable. Second- hand equipment should be used wherever possible. The use of environmental criteria and open standards must become man- datory in all public services and outstanding regulations and standardisation processes must be supported by public author- ities. A paradigm shift towards free and open-source software is particularly important in the area of critical infrastructure. At EU level, for example, it is necessary to derive and implement concrete measures from the EU Commission’s open-source strategy. For European projects such as the creation of a trust- worthy cloud environment (GAIA-X), it is also imperative to include binding sustainability criteria (an example here is the Blue Angel for data centres) in the call for tenders, thereby set- ting technological standards at European level that give high priority to environmental protection.
Mehr anzeigen

5 Mehr lesen

Plausibility in Architectural Design - Software Support for the Architect-oriented Design of Colour Schemes for Interiors and Buildings

Plausibility in Architectural Design - Software Support for the Architect-oriented Design of Colour Schemes for Interiors and Buildings

A good knowledge of colour systems and their effects within particular spatial situations, in conjunction with particular materials and surface qualities and the influence of light on colour and atmosphere are only some aspects necessary for professional design of colour schemes. The tools and working methods are in principle relatively simple and have not changed significantly over the years: interior rooms or exterior elevations, perspectives or isometric representations are drawn to scale and coloured as a means of exploring (for the designer) and communicating (for other participants) colour schemes. Colour scheme variants, detailed vignettes, colour samples and colour collages form the basis for planning decisions. Very often such decisions are often made independent of other design aspects such as spatial organisation, environment, the atmosphere of a space, its use, material or construction.
Mehr anzeigen

10 Mehr lesen

Automated design of self-adaptive software with control-theoretical formal guarantees

Automated design of self-adaptive software with control-theoretical formal guarantees

06, HME10]. We address this need by presenting a methodology which automatically builds suitable system models and then uses those models to synthesize a controller suitable for the self- adaptive management of non-functional application requirements. Given a software sys- tem and a non-functional requirement (e.g., performance, accuracy, energy), our method- ology first uses a training phase to generate a linear model of the system and then synthe- sizes a configurable controller. The controller overcomes potential non-linearities using a Kalman filter to adapt the linear model dynamically. In addition, for drastic changes in system behavior, the controller incorporates a change-point detection strategy to trigger an online model rebuilding phase. This methodology allows non-expert users to apply control theoretic techniques, without requiring a priory knowledge about system’s behavior. We evaluated our methodology in two ways. First, we performed a formal assessment of the guarantees it provides. Second, we performed an empirical assessment of the method- ology on three different software applications: video compression, energy efficient re- source provisioning, and dynamic binding and delegation. Details on the approach and its evaluation can be found in [FHM14].
Mehr anzeigen

2 Mehr lesen

Design and implementation of adaptive OFDM in a software defined radio framework

Design and implementation of adaptive OFDM in a software defined radio framework

Frequency band [GHz] Bandwidth [MHz] Sampling frequency [MHz] FFT size Subcarrier spacing [kHz] Payload modulation FEC BS Transmit EIRP [dBm] UE Transmit EIRP [dBm] Number of data subcar[r]

225 Mehr lesen

Design and Implementation of a Software-Defined Approach to Information-Centric Networking

Design and Implementation of a Software-Defined Approach to Information-Centric Networking

The Software-Definded Internet Architecture (SDIA) called design approach prom- ises to ease the adoption of new Internet architectures, like for instance ICN. Raghavan et al. criticize that any significant change to network layer protocols requires the substi- tution of all forwarding devices, since the forwarding logic is protocol specific and often times implemented in hardware. This implementation in hardware is done to speed up the processing but at the same time limits the flexibility for the evolution of the protocols. The design builds up on the separation of core and edge network addressing schemes like previously proposed for instance in [26, 27]. For the intra-domain design a “fabric-like” approach is proposed, which utilizes arbitrary and decoupled forwarding mechanisms in the core and at the edge of the network. Furthermore, the control plane protocols and mechanisms are independent per network domain. As a consequence of this claim, the three communication patterns edge-to-edge, edge-to-host and host-to- host have to be supported.
Mehr anzeigen

123 Mehr lesen

Preliminary specification and design documentation for software components to achieve Catallaxy in computational systems

Preliminary specification and design documentation for software components to achieve Catallaxy in computational systems

Friedrich August von Hayek (Hayek, Bartley et al.), and other Austrian economists under- stood the market as a decentralized coordination mechanism, as opposed to a centralized command economy (note that Austrian, or Neo-Austrian economics, describe an Economics line of thought, rather than only the geographical heritage of its prosponents). Apart from po- litical macroeconomic thoughts, his work also provides concrete insight on the working mechanisms of economic coordination. The emergence of software agent technology and in- creasing size of information systems leads to the possibility of implementing Hayek’s Catal- laxy concept and using the ensuing "spontaneous order” as a concrete proposal for both the design and coordination of information systems. However, a formal description of this self- organizing market mechanism does not so far exist.
Mehr anzeigen

75 Mehr lesen

Software-Komponentenmodelle

Software-Komponentenmodelle

file sizes, but also needs more computational time. Performance prediction is used to estimate a speedup. In [6], the design alternative is modeled using parametric dependencies. A usage profile for the use case “upload files” is created, specifiyng a probabilistic mass function (PMF) for the parameters “file size” and “number of files”. These data are collected by the Domain Expert, who has knowledge of typical user behaviour. Based on these parameters, a propability distribution is computed for the number of CPU operations. In combination with the actual hardware configuration from the allocation context, execution times are gained. These times are used to calculate response times in the scenarios with and without the additional components. The SEFFs of the two additional components are used to gain information on the internal control flow.
Mehr anzeigen

104 Mehr lesen

Software Zertifizierung

Software Zertifizierung

5.3 Bewertung Wenn man die SAAM bewerten will, sollte man sich als ersten Anhaltspunkt an- schauen, was man in die SAAM investieren muss, was man f¨ ur die Anwendung der Methode aufwenden muss und was man daf¨ ur am Ende zur¨ uckbekommt. Als Voraussetzung f¨ ur die SAAM ben¨ otigt man eine Softwarearchitektur. Sofern eine Beschreibung der Architektur nicht vorhanden ist, muss sie extra f¨ ur die SAAM erstellt werden. Dies bedeutet einen gr¨ oßeren Aufwand. Allerdings bietet eine Architekturbeschreibung auch unabh¨ angig von einer Evaluation einen Nutzen, wie in Kapitel zwei beschrieben. Die Kosten f¨ ur die SAAM selbst sind dagegen relativ gering. Das Ergebnis der SAAM ist eine Liste mit den wichtigsten An- forderungen an die Software, die von der bestehenden Architektur nicht erf¨ ullt werden. Mit anderen Worten eine Liste mit den Schwachstellen der Architek- tur bez¨ uglich der wahrscheinlichsten ¨ Anderungsanforderungen an die Software. L¨ asst man die Ergebnisse der SAAM in die Architektur miteinfließen erh¨ alt man also eine qualitativ hochwertigere Software, die sich wesentlich leichter an zu- k¨ unftige Anforderungen anpassen l¨ asst. Das heißt nicht zwangsl¨ aufig, dass die Software generell besser modifizierbar wird, sondern nur an den Stellen, die mit hoher Wahrscheinlichkeit auch ge¨ andert werden sollen. Wenn man sich an dieser Stelle nochmals vor Augen f¨ uhrt, dass bei einer Software der weitaus gr¨ oßte Teil der Kosten nicht durch die Erstellung, sondern durch Wartung und Modifikation entsteht [BaCK98, S.32], ist dies ein gewaltiger Kostenvorteil. Die Ergebnisse der SAAM h¨ angt zu 100% von den Szenarien ab. Diese wiederrum h¨ angen von den beteiligten Interessenvertretern ab. Dies ist auch die gr¨ oßte Gefahr. Wenn die Interessenvertreter keine guten Szenarien erheben, liefert auch die SAAM keine guten Ergebnisse. Allerdings sind in der Literatur keine F¨ alle bekannt, dass die- ser Fall schon einmal eingetreten w¨ are. Denn wer sollte die Anforderungen an eine Software besser kennen, als die Personen, die an ihr teilhaben. Selbst unab- h¨ angig von den Ergebnissen der SAAM liefert schon der Prozess alleine Vorteile. Wenn der Architekt in Schritt zwei die Architektur vorstellt und beschreibt, wird der Auftraggeber der Software, implizit ¨ uberpr¨ ufen, ob der Architekt alle seine Anforderungen und W¨ unsche, die er in der Anforderungsanalyse gestellt hat, in der Architektur realisiert hat. Des Weiteren verbessert die Kenntnis der Architektur bei allen Projektbeteiligten das Verst¨ andnis f¨ ur die Software und ih- re Arbeitsweise. Durch die Konfrontation mit den anderen Interessenvertretern bekommen alle Beteiligten ein umfassenderes Bild.
Mehr anzeigen

233 Mehr lesen

Show all 4830 documents...