サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
パリ五輪
agilemodeling.com
Core Practices for Agile/Lean Documentation Ideally, an agile document is just barely good enough, or just barely sufficient, for the situation at hand. Documentation is an important part of agile software development initiatives, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall risk and
Class Responsibility Collaborator (CRC) Cards: An Agile Introduction A Class Responsibility Collaborator (CRC) model is a collection of standard index cards that have been divided into three sections, as depicted in Figure 1. A class represents a collection of similar objects, a responsibility is something that a class knows or does, and a collaborator is another class that a class interacts with
Lean/Agile Documentation: Strategies for Agile Teams Agile documentation, also referred to as lean documentation, is concise and sufficient for the needs of its readers. When I initially started work on Agile Modeling (AM) I wanted to focus solely on principles and practices for effective modeling but quickly discovered that this scope was not sufficient, that I also needed to consider the issue o
Introduction to the Diagrams of UML 2.X Understanding the thirteen diagrams of UML 2.x is an important part of understanding OO development. Although there is far more to modeling than just the UML the reality is the UML defines the standard modeling artifacts when it comes to object technology. There are three classifications of UML diagrams: Behavior diagrams. A type of diagram that depicts beha
UML Activity Diagrams: An Agile Introduction UML activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule. Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so t
Agile Model Driven Development (AMDD): The Key to Scaling Agile Software Development As the name implies, Agile Model Driven Development (AMDD) is the agile version of Model Driven Development (MDD). MDD is an approach to software development where extensive models are created before source code is written. The difference with AMDD is that instead of creating extensive models before writing source
このページを最初にブックマークしてみませんか?
『Agile Modeling Home - The Agile Modeling (AM) Method』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く