Reuse Alternatives based on the Sources of Software Assets

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages

The PARSE Programming Paradigm. Part I: Software Development Methodology. Part II: Software Development Support Tools

The programming methodology of PARSE (parallel software environment), a software environment being developed for reconfigurable non-shared memory parallel computers, is described. This environment will consist of an integrated collection of language interfaces, automatic and semi-automatic debugging and analysis tools, and operating system —all of which are made more flexible by the use of a knowledge-based implementation for the tools that make up PARSE. The programming paradigm supports the user freely choosing among three basic approaches /abstractions for programming a parallel machine: logic-based descriptive, sequential-control procedural, and parallel-control procedural programming. All of these result in efficient parallel execution. The current work discusses the methodology underlying PARSE, whereas the companion paper, “The PARSE Programming Paradigm — II: Software Development Support Tools,” details each of the component tools

Computer Aided Software Engineering (CASE)--environment issues.

The rising percentage of system costs attributed to software development and maintenance have resulted in the research by industry and academia into ways to improve the productivity of software professionals in all phases of the software lifecycle. Computer Aided Software Engineering (CASE) environments are one solution being pursued. This thesis attempts to coalesce, from various efforts to date, some general principles for such environments in order to assist decision makers who must procure them. This work is in support of the Missile Software Branch, Naval Weapon Center, China Lake, California (MSB), and their investigation of CASE environments to improve productivity. Problems of CASE development and use are discussed in this context. A general problem solving approach through abstraction of resources is proposed with a focus on an individual programmer productivity subset of a CASE environment.http://archive.org/details/computeraidedsof00freyLieutenant Commander, United States NavyApproved for public release; distribution is unlimited

Eine Entwicklungsmethodik für sicherheitsrelevante Elektroniksysteme im Automobil

Es wird eine neue Entwicklungsmethodik für sicherheitsrelevante Elektroniksysteme im Automobil vorgestellt. Die im Automobilbereich gängige Methodik wird um Inhalte bzgl. Sicherheit und Zuverlässigkeit erweitert, die an den Luftfahrt-Standard SAE ARP 4761 angelehnt an die Anforderungen im Automobilbereich angepasst wurden. Wesentliche Erweiterungen sind neben dem Einsatz einer Gefährdungsanalyse der intensive Einsatz von FTA und FMEA zum Nachweis der Sicherheitseigenschaften des Systems

Methoden- und Werkzeugunterstützung für evolutionäre, objektorientierte Software-Projekte

Die Software-Entwicklung verläuft in der Regel evolutionär, d.h. als eine Folge von Erweiterungs- und Anpassungszyklen, beruhend auf Erfahrung, Nutzung und Revision. Viele der bekannten Vorgehensmodelle, wie z.B. "Rational Unified Process" (RUP), berücksichtigen diesen evolutionären Aspekt der Software-Entwicklung ungenügend. Mit dem EOS-Modell, ein Vorgehensmodell für die evolutionäre, objektorientierte Software-Entwicklung (EOS), wird versucht, dieses Defizit zu überbrücken. In der ursprünglichen Fassung ist das EOS-Modell methodenunabhängig. Ein Ziel der Dissertation war es, konkrete Methoden für die EOS-Subprozesse Projektmanagement, Software-Entwicklung, Qualitätssicherung, Konfigurationsmanagement und Nutzung und Bewertung vorzuschlagen. Ausgehend von der Methoden-Definition wurde prototypisch ein Werkzeug implementiert, das eine systematische Unterstützung der definierten Methoden ermöglicht