P023 - Software Management 2002: Progress through Constancy
Auflistung nach:
Auflistung P023 - Software Management 2002: Progress through Constancy nach Erscheinungsdatum
1 - 10 von 20
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragOrganisatorische Implementierung im Informationssystem –Das Problem der Organisationsstrukturen bei der Konfiguration von Softwaresystemen(Software Management 2002: Progress through Constancy, 2002) Hildebrand, KnutThe paper outlines the problems of organizational changes in an information system and describes possible solutions. The central topic is the implementation of the company's organization structure (organization units, structure, correlations), which is often ignored, for instance at the deleting and merging of organization units.
- KonferenzbeitragManagement des Testprozesses von Anfang an – Das W-Modell(Software Management 2002: Progress through Constancy, 2002) Spillner, AndreasIn software development, 30 to 40 % of all software activities are testing related. That is why it is critical to launch testing activities at the beginning of the project rather than after the coding is completed. While new software development models such as the Rational Unified Process and eXtreme Programming (XP) continue to be popular with practitioners, the V-model has gained particularly wide acceptance. Based on the V-model, this paper describes a model that shows how the tasks for testing relate to the tasks in the development model. This model – the W-model – further clarifies the priority of the tasks and the dependence between the development and testing activities. Although as simple as the V-model, the W-model makes the importance of testing and the ordering of the individual testing activities clear. It also clarifies that testing and debugging are not the same thing.
- KonferenzbeitragModellierung von Architekturen(Software Management 2002: Progress through Constancy, 2002) Foegen, Malte; Atamaniuk, PatrickThis paper is based on our experience with medium and large software projects. It defines the term "architecture" and shows its relevance in software engineering. In its main part this paper describes the elements of an architecture and defines the work products produced during a software development project in order to model an architecture.
- KonferenzbeitragSoftware-Produktmanagement – Kurzfassung zum Tutorial(Software Management 2002: Progress through Constancy, 2002) Sneed, Harry M.Das halbtägige Tutorial richtet sich an Führungskräfte, die für die Wartung und Weiterentwicklung von Anwendungssystemen zuständig sind. Produktmanagement befaßt sich im Gegensatz zum Projektmanagement mit dem Lebenszyklus eines Systems. Projekte sind nur kurze Abschnitte im Leben eines Softwareproduktes. Entweder streben sie an, den Urzustand eines Produktes herzustellen, Entwicklungsprojekte, oder sie wandeln das Produkt von einem Zustand in einen anderen, Weiterentwicklungsprojekte. Ein Produkt wird im Laufe seines Lebens von vielen Projekten bearbeitet. Jedes Projekt will das Produkt verbessern. Ein Projekt ist aber räumlich und zeitlich begrenzt. Es hat ein festes Budget und eine feste Dauer. Die Projekte, bzw. die Aktivitäten sind immer wieder andere. Es gibt Prototypprojekte, Entwicklungsprojekte, Wartungsprojekte, Sanierungsprojekte und Migrationsprojekte. Das Produkt bleibt das gleiche. Produktmanagement ist also die Planung und Steuerung eines Produktlebenszyklus' nach der Erstentwicklung ab dem Zeitpunkt, an dem das Produkt in Produktion geht. Damit werden alle Aktivitäten - also Projekte - zur Wartung, Weiterentwicklung, Sanierung und Migration des Produktes geplant, organisiert, gesteuert und kontrolliert. Produktmanagement ist Evolutionsmanagement.
- KonferenzbeitragRisikomanagement in IT-Projekten – Vorschlag einer Vorgehensweise(Software Management 2002: Progress through Constancy, 2002) Gaulke, MarkusThe paper outlines the necessity for risk management in IT projects and describes a risk management process and methodology to identify the risks of an IT project in advance. The methodology has been developed 1999 within KPMG, and applied in many firms all over the world. In 2002 the risk management process and the methodology was revised and afterwards published by the author.
- KonferenzbeitragThemenzentrierte Interaktion in IT-Projekten(Software Management 2002: Progress through Constancy, 2002) Müller, ThomasIn IT-Projekten wird methodisch geplant, entworfen und entwickelt. Doch die Art und Weise, wie man im Team zusammenarbeitet, bleibt meist dem Zufall überlassen – mit manchmal katastrophalen Folgen: Motivationsverlust und Konflikte können den Projekterfolg ernsthaft gefährden. Das muss nicht sein: Themenzentrierte Interaktion (TZI) ist eine bewährte Methode, um die Zusammenarbeit von Menschen in Projekten effizient und anregend zu gestalten – auch in der nüchternen Welt der Informationstechnologie. Was TZI ist und wie man sie in IT-Projekten sinnvoll nutzt, das beschreibt der folgende Beitrag.
- KonferenzbeitragEin Verfahren zur Beurteilung der langfristigen Nutzbarkeit von Softwaresystemen(Software Management 2002: Progress through Constancy, 2002) Elzer, Peter F.; Löbbert, ArndLong-term usability of software systems is becoming an economically relevant issue. In particular it is important to assess it at an early stage in the development process. In this paper a method for such an assessment is proposed. It is based upon the calculation of a 'long-term-useability-index' from a number of defined properties of the modules of the software system under development. There are two versions of the method, that differ in the number of properties to be taken into account, the effort to be invested and the precision of the result. First tests have shown the viability of the method.
- KonferenzbeitragIntegrationsprojekte auf Basis von EAI-Technologie – Architektur und Entwicklung(Software Management 2002: Progress through Constancy, 2002) Buhrmann, Peter; Richter, Jan-PeterEnterprise application integration is often described as the use of some toolset that enables the rapid integration of legacy, packaged, and new applications into new business solutions and thus providing more flexibility. This paper is based on sd&m experiences in a project to integrate two packaged applications from SAP and Siebel. We present all architectural aspects of the developed solution with the main focus on the technical software architecture. We show that EAI toolsets provide technical software for the integration but error handling, process control and more important business logic has to be built within the project.
- KonferenzbeitragSicherheitsmanagement mit SAP R/3-Systemen – Vorgehensmodell zur Implementierung eines R/3- Berechtigungskonzeptes(Software Management 2002: Progress through Constancy, 2002) Hohnhorst, GeorgModern business IT applications pose, due to their complexity and their integration into various business processes, several formerly unknown issues and problems. In particular, the need to ensure that the new business processes are in line with implemented software functions, arises. Appropriately defined controls need to be in place in order to protect against unauthorized modification or usage of both, critical data and sensitive programs. This paper outlines, how a tailored authorization concept can provide support in reaching these targets. It relates to the standard ERP application SAP R/3. A framework which allows for the definition of detailed access controls within R/3 is described. In general, this paper focuses on a 10-step methodology to define and implement an authorization concept which is based on a workplace-approach to meet current security, business and legal requirements.
- KonferenzbeitragSPiCE in action – Experiences in Tailoring and Extension(Software Management 2002: Progress through Constancy, 2002) Völcker, Christian; Cass, Ann; Sutter, Philipp; Stienen, Hans; Dorling, AlecExperiences are reported in the use of ISO 15504 both in tailoring the standard for particular industrial sectors and in expanding the process assessment approach into new domains. In particular, three projects are discussed: SPiCE for SPACE, a ISO/IEC TR 15504 [IS98a] conformant method of software process assessment developed for the European space industry, SPiCE-9000 for SPACE, an assessment method for space quality management systems, based on ISO 9001:2000 [IS00], and NOVE-IT, a project of the Swiss federal government to establish and assess processes covering IT procurement, development, operation, and service provision. All three of these projects use the concepts of process assessment from ISO 15504; however, in each case, different strategies to apply the international standard were selected. Some of the issues faced in these different domains are described and their resolutions presented.