Rosa María Torres de Paz RUP Agil Trabajo para la asignatura Metodología y técnicas en proyectos software para la Web Rosa María Torres de Paz

¿De dónde viene? The Agile Manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

¿De dónde viene? The Agile Manifesto Working software is the primary measure of progress. Agile processes promote sustainable development.The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

¿De dónde viene? Agile Modeling (AM) Home Page http://www.agilealliance.com/   Agile Modeling (AM) Home Page Effective Practices for Modeling and Documentation http://www.agilemodeling.com/ Copyright 2001-2006 Scott W. Ambler Page last updated on April 30, 2006 This site owned by Ambysoft Inc.

¿Qué es? Active Stakeholder Participation Apply the Right Artifact(s) Collective Ownership Create Several Models in Parallel Create Simple Content Depict Models Simply Model in Small Increments Model With Others Prove it With Code Single Source Information Use the Simplest Tools Apply Modeling Standards Apply Patterns Gently Discard Temporary Models Formalize Contract Models Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems.  Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner.  As you see AM is meant to be tailored into other, full-fledged methodologies such as XP or RUP, enabling you to develop a software process which truly meets your needs. Assume Simplicity Embrace Change Enabling the Next Incremental Change Maximize Stakeholder Investment Model With a Purpose Quality Work Rapid Feedback Software Is Your Primary Goal Content is More Important Than Representation Open and Honest Communication Communication Simplicity Feedback Courage Humility

¿Qué es AUP? Enterprise Unified Process (EUP)

¿Qué es AUP?

Serial in the large

Iterative in the small

Serial in the large: Inception Identify the initial scope of the project, A potential architecture for your system, To obtain initial project funding and stakeholder acceptance.

Serial in the large: Elaboration To prove the architecture for the system to be developed. The point is to ensure that the team can actually develop a system that satisfies the requirements, and the best way to do that is to build a end-to-end, working skeleton of the system called an "architectural prototype".  To write high-quality, working software which meets several high risk (from a technical point of view) use cases to show that the system is technically feasible.

Serial in the large: Construction To develop the system. To prioritizing and understanding the requirements, model storming a solution, and Coding and testing the software.

Serial in the large: Transition Delivering the system into production. Fine-tuning of the product Rework to address significant defects.

Deliverables

Deliverables

Gracias