(1) A process - to define activities or tasks to achieve the goal of the methodology
(2) A vocabulary - to describe the process and work products created during the process application.
(3) Rules and guidelines - to define the quality of the process and the work products
The four methodologies are shown in the table below along with their strengths and weaknesses.
| Domain | RUP | Shlaer-Mellar | CRC | XP |
| Emphasis | - Incremental and iteration | - Execution for verification | Scenarios and simplicity | Simplicity, design through integration and refactoring |
| Strengths | - Comprehensive - Well Defined artifacts and roles - Incremental deliveries | - Simulation capability - Well defined testing rules - Well defined transition from one step in the process to another - Real-time system support | - Simplicity - Easy to use to transition from procedural to object oriented concepts - Focuses on object value, leading to optimized system | - Focuses and cares about the programming environment - Supports and requires close relationship between clients and developers - Accounts for changes in the development process |
| Weakness | - Large and difficult - Complicated rules - Customization is not straight-forward - Limited vendors supporting the process | - Considerable learning curve - Focuses too much on state modeling. - Limited vendors supporting the process | - Supports primarily classes - Requires a facilitator | - Relies on an ideal development environment - Depends extensively on client commitments - Requires high quality human interaction among development team - The system is in a constant state of maintenance |
No comments:
Post a Comment