Các tiêu chuẩn UML là một ký hiệu phổ biến mà có thể được áp dụng cho nhiều loại khác nhau của dự án phần mềm bằng cách sử dụng phương pháp rất khác nhau. Các biến thể xuất hiện trong việc sử dụng các phần mở rộng UML, như khuôn mẫu, và nhấn mạnh được đặt trên các sơ đồ khác nhau cho các loại khác nhau của dự án. 8. Các dấu ấn của RUP là hai thuật ngữ gia tăng và lặp đi lặp lại | 318 Appendix A 7. The UML standard is a common notation that may be applied to many different types of software projects using very different methodologies. The variations appear in the use of the UML extensions like stereotypes and the emphasis placed on different diagrams for different types of projects. 8. The hallmarks of RUP are the two terms incremental and iterative. The goal of the methodology is to deliver an executable release of a product an increment of the product for every pass or iteration through the process. The motivation for this approach is to keep delivery times short and deliveries frequent. This prevents the historical problem of projects that run for months or even years before they actually produce anything. It also supports early review and early problem detection. 9. The Shlaer-Mellor Method is based on an integrated set of models that can be executed for verification and an innovative approach to design that produces a system design through a translation of the analysis models. The method is built on a set of well-defined rules for the construction of the models and the translation of those models from analysis to design and finally to implementation. 10. The CRC card captures the information about one class. The class name is written on top of the card. The next two lines are reserved for the listing of superclasses and subclasses. The body of the card is divided in half. The left column or half lists the responsibilities of the class and the right column or half lists the other objects that it works with the collaborators to fulfill each responsibility. 11. The Use Case view consists of Use Case and Activity diagrams narratives and scenarios. It is tempting to include policies and procedures but policies and procedures are captured within a number of the models. Depending on the specific nature of the procedures or policies they may be captured in one or more of the static or dynamic view diagrams or even the physical models Component
