A systematic Approach to Software Evolution : Dissertation (1. Aufl. 2013. XXV, 394 S. zahlr. Abb. u. Tab. 24 cm)

個数:

A systematic Approach to Software Evolution : Dissertation (1. Aufl. 2013. XXV, 394 S. zahlr. Abb. u. Tab. 24 cm)

  • 在庫がございません。海外の書籍取次会社を通じて出版社等からお取り寄せいたします。
    通常6~9週間ほどで発送の見込みですが、商品によってはさらに時間がかかることもございます。
    重要ご説明事項
    1. 納期遅延や、ご入手不能となる場合がございます。
    2. 複数冊ご注文の場合は、ご注文数量が揃ってからまとめて発送いたします。
    3. 美品のご指定は承りかねます。

    ●3Dセキュア導入とクレジットカードによるお支払いについて
  • 【入荷遅延について】
    世界情勢の影響により、海外からお取り寄せとなる洋書・洋古書の入荷が、表示している標準的な納期よりも遅延する場合がございます。
    おそれいりますが、あらかじめご了承くださいますようお願い申し上げます。
  • ◆画像の表紙や帯等は実物とは異なる場合があります。
  • ◆ウェブストアでの洋書販売価格は、弊社店舗等での販売価格とは異なります。
    また、洋書販売価格は、ご注文確定時点での日本円価格となります。
    ご注文確定後に、同じ洋書の販売価格が変動しても、それは反映されません。
  • 製本 Paperback:紙装版/ペーパーバック版
  • 商品コード 9783868880533

Description


(Text)
In this thesis, we present a method to systematically perform software evolution. The focus is set on the early phases, i.e., analysis and design. The basic idea is to adjust an existing software development process so that evolution is supported.We propose to perform a replay of the original method, adding some support for software evolution. We achieve this by defining a corresponding evolution step for every existing step of the original process.These evolution steps address the special needs arising in software evolution by providing evolution operators. The operators define rules, i.e., what has to be done in order to incorporate the requested changes into the existing documents or to create, when necessary, additional ones by defining pre- and post-states for the used model. Hence, the operators assist engineers in evolving given documents.They also help in the reuse of related development documents in successive development phases. However, a complete replay of the processsteps for all model elements is not desirable. Only model elements that may be affected by the evolution task should be considered. Therefore, it is necessary to locate the relevant parts within the overall system that need to be modified or where additions are necessary. To identify those relevant parts, we establish relations between the existing requirements and those being introduced by the evolution task. We then tag the relevant documents. This enables us to decrease the effort for performing the evolution by determining only a subset of relevant documents that have to be considered.We illustrate the applicability of our approach by a simple vacation rentals system serving as running example.Furthermore, we illustrate how the architecture approach used in the evolution method can be enhanced by introducing evolution patterns for layered software architectures and derive architectures adhering to a specific kind of design pattern based on the software architecture derived inthe early stages of the design phase.

最近チェックした商品