Serwis Infona wykorzystuje pliki cookies (ciasteczka). Są to wartości tekstowe, zapamiętywane przez przeglądarkę na urządzeniu użytkownika. Nasz serwis ma dostęp do tych wartości oraz wykorzystuje je do zapamiętania danych dotyczących użytkownika, takich jak np. ustawienia (typu widok ekranu, wybór języka interfejsu), zapamiętanie zalogowania. Korzystanie z serwisu Infona oznacza zgodę na zapis informacji i ich wykorzystanie dla celów korzytania z serwisu. Więcej informacji można znaleźć w Polityce prywatności oraz Regulaminie serwisu. Zamknięcie tego okienka potwierdza zapoznanie się z informacją o plikach cookies, akceptację polityki prywatności i regulaminu oraz sposobu wykorzystywania plików cookies w serwisie. Możesz zmienić ustawienia obsługi cookies w swojej przeglądarce.
This paper proposes a structured approach for reviewing architecture documents using question sets. Given the critical importance of architecture to software project success, it follows that the architecture cannot be effective unless it is captured in documentation that allows the stakeholders to understand and use the architecture in the way it was intended. The approach does not assume a particular...
Software architecture is touted as essential for system development, but its benefits are almost never quantified. Further, architects are faced with decisions about architecture (such as deciding when an architecture has outlived its usefulness) that should be answered on an economic basis. This paper presents an simple economic modeling language that has been useful in the realm of software product...
This paper argues that software architecture has always been the enabler for the ever-upward spiral in software engineering of more powerful problem-space languages, and will continue to be so
Aspect-oriented software development has focused on the software life cycle's implementation phase: developers identify and capture aspects mainly in code. But aspects are evident earlier in the life cycle, such as during requirements engineering and architecture design. Early aspects are concerns that crosscut an artifact's dominant decomposition or base modules derived from the dominant separation-of-concerns...
This work describes a workshop that is intended to fill the void between variability requirements visible to those who deal with features and other product-level concerns, and the variability mechanisms visible to creators and consumers of a product line's core assets. The goal of the workshop is to begin to codify a body of knowledge for the informed and purposeful selection of variability mechanisms...
The "Software Architecture Documentation in Practice" working session at WICSA addressed practical issues concerning the creation, evolution, and uses of software architecture documentation. After paper presentations, discussion topics included enforcement/traceability, tooling, inhibiting factors to the widespread use of documentation, uses of architecture documentation, and UML as an architecture...
Maintenance of a computer-based system accounts for a large proportion of the total system cost. However, no well-established techniques exist for assessing the maintainability of such a system. This paper presents a case study in assessing the maintainability of a large, software intensive system. The techniques we used are described, and their strengths and weaknesses discussed.
Podaj zakres dat dla filtrowania wyświetlonych wyników. Możesz podać datę początkową, końcową lub obie daty. Daty możesz wpisać ręcznie lub wybrać za pomocą kalendarza.