The Agile Unified Process (AUP) - Instituto De Computação
The Agile Unified Process (AUP) Scott W. Ambler Senior Consultant, Ambysoft Inc. www.ambysoft.com/scottAmbler.html Copyright 2001-2005 Scott W. Ambler 1
Scott W. Ambler Methodologist, Author, Consultant Services: Agile Model Driven Development (AMDD) RUP/EUP/AgileUP mentoring Agile Software Development Coaching/Mentoring Training Workshops Management SPI Workshops Internal Conference Keynotes Copyright 2001-2005 Scott W. Ambler 2
Overview Warning! The Unified Process Agile Software Development The AUP Disciplines Secrets of Success Copyright 2001-2005 Scott W. Ambler 3
Warning! I’m spectacularly blunt at times Many new ideas will be presented Some may not fit well into your existing environment Some will challenge your existing notions about software development Some will confirm your unvoiced suspicions Don’t make any “career-ending moves” Be skeptical but open minded Copyright 2001-2005 Scott W. Ambler 4
Observation: It’s the Same Cost Curve (JIT) Copyright 2001-2005 Scott W. Ambler 5
Rational Unified Process (RUP) Copyright 2001-2005 Scott W. Ambler 6
Agile UP www.ambysoft.com/unifiedprocess/agileUP.html Copyright 2001-2005 Scott W. Ambler 7
Agile UP Phases and Milestones Copyright 2001-2005 Scott W. Ambler 8
The Disciplines of the AUP Modeling Implementation Test Deployment Configuration Management Project Management Environment Copyright 2001-2005 Scott W. Ambler 9
The Modeling Discipline Copyright 2001-2005 Scott W. Ambler 10
Active Stakeholder Participation Project stakeholders should: Provide information in a timely manner Make decisions in a timely manner Actively participate in business-oriented modeling icipation.htm www.agilemodeling.com/essays/inclusiveModels.htm Copyright 2001-2005 Scott W. Ambler 11
Agile Model Driven Development (AMDD) Project Level (www.agilemodeling.com/essays/amdd.htm) Goals: Gain an initial understanding of the scope, the business domain, and your overall approach. Initial Requirements Modeling (days) Initial Architectural Modeling (days) Cycle 0: Initial Modeling Goal: Quickly explore in detail a specific issue before you implement it. Goal: Develop working software in an evolutionary manner. Model Storming (minutes) Reviews (optional) All Cycles (hours) Implementation (Ideally Test Driven) (hours) Cycle 1: Development Cycle 2: Development Cycle n: Development Copyright 2001-2005 Scott W. Ambler 12
Agile Software Requirements Management Changing Requirements Are a Competitive Advantage if You Can Act on Them: www.agilemodeling.com/essays/agileRequirements.htm Copyright 2001-2005 Scott W. Ambler 13
There is More to Modeling than UML Copyright 2001-2005 Scott W. Ambler 14
Agile Data www.agiledata.org The Agile Data (AD) method is a collection of philosophies that will enable IT professionals within your organization to work together effectively when it comes to the data aspects of software-based systems. Six philosophies: Data. Data is one of several important aspects of software-based systems. Enterprise issues. Development teams must consider and act appropriately regarding enterprise issues. Enterprise Groups. Enterprise groups exist to nurture enterprise assets and to support other groups, such as development teams, within your organization. Unique situation. Each development project is unique, requiring a flexible approach tailored to its needs. One software process does not fit all. Work together. IT professionals must work together effectively, actively striving to overcome the challenges that make it difficult to do so. Sweet spot. Avoid the black and white extremes to find the gray that works best for your overall situation. Copyright 2001-2005 Scott W. Ambler 15
The Implementation Discipline Copyright 2001-2005 Scott W. Ambler 16
Pair Programming Two programmers working side-by-side, collaborating on the same design, algorithm, code or test. The driver has control of the keyboard/mouse and actively implements the program. The observer continuously observes the work of the driver to identify tactical (syntactic, spelling, etc.) defects and also thinks strategically about the direction of the work. They periodically switch roles, working together as equals. On demand, the two programmers can brainstorm any challenging problem. Significant evidence exists which shows that pair programming is more effective, overall, than solo programming for the vast majority of developers. pairprogramming.com Copyright 2001-2005 Scott W. Ambler 17
Refactoring A refactoring is a small change to your code to improve your design that retains the behavioral semantics of your code. Two types: Code refactoring Database refactoring www.refactoring.com www.databaserefactoring.com Copyright 2001-2005 Scott W. Ambler 18
Continuous Integration Daily builds are a good start We update and test our code constantly Therefore we need to build the system constantly Copyright 2001-2005 Scott W. Ambler 19
Database Refactoring www.agiledata.org/essays/databaseRefactoring.html A database refactoring is a simple change to a database schema that improves its design while retaining both its behavioral and informational semantics. A database schema includes both structural aspects such as table and view definitions as well as functional aspects such as stored procedures and triggers. Database refactorings are a subset of schema transformations, but they do not add functionality. Copyright 2001-2005 Scott W. Ambler 20
Test Driven Design (TDD) www.agiledata.org/essays/tdd.html Copyright 2001-2005 Scott W. Ambler 21
The Test Discipline Copyright 2001-2005 Scott W. Ambler 22
Full Lifecycle Object-Oriented Testing (FLOOT) http://www.ronin-intl.com/publications/floot.html Requirements Testing - Model reviews - Prototype walkthroughs - Prove it with code - Usage scenario testing Analysis Testing - Model reviews - Prototype walkthroughs - Prove it with code - Usage scenario testing Architecture/ Design Testing - Model reviews - Model walkthroughs - Prototype walkthroughs - Prove it with code Code Testing System Testing - Black-box testing - Boundary value testing - Classintegration testing - Class testing - Code reviews - Coverage testing - Inheritanceregression testing - Method testing - Path testing - White-box testing - Function testing - Installation testing - Operations testing - Stress testing - Support testing User Testing - Alpha testing - Beta testing - Pilot testing - User acceptance testing (UAT) Regression Testing, Quality Assurance Copyright 2001-2005 Scott W. Ambler 23
The Deployment Discipline Copyright 2001-2005 Scott W. Ambler 24
Regular Deployment of Working Software How many projects have you seen that: Were “90% complete” for months? Delivered wonderful plans but no software? Delivered wonderful models, but no software? The only accurate measure of software development is the delivery of software Deliver something at the end of each cycle/iteration Iterations should be short At all points in time stakeholders can see what they’ve gotten for their investment to date Copyright 2001-2005 Scott W. Ambler 25
Deployment Strategy Frequent Deployment HighlyControlled Deployment Controlled Deployment Demo Sandbox Development Sandbox Project Integration Sandbox Production Test/QA Sandbox Highly Iterative Development Project-Level Testing System and Acceptance Testing Copyright 2001-2005 Scott W. Ambler Operations and Support 26
The Configuration Management Discipline Copyright 2001-2005 Scott W. Ambler 27
The Project Management Discipline Copyright 2001-2005 Scott W. Ambler 28
The Environment Discipline Copyright 2001-2005 Scott W. Ambler 29
Follow Guidance Guidance Standards and guidelines Agile developers prefer to develop highquality artifacts, and that includes ensuring that they are developed in a consistent manner XP practice Coding Standards AM practice Modeling Standards www.agilemodeling.com/style/ Copyright 2001-2005 Scott W. Ambler 30
Why Agile UP? Traditional Testing Code Inspections Full Lifecycle Testing Model and Document Reviews Big Requirements Up Front (BRUF) Pair Programming Model With Others Big Design Up Front (BDUF) Test Driven Design (TDD) Active Stakeholder Participation Agile Model Driven Development (AMDD) Copyright 2001-2005 Scott W. Ambler 31
Secrets of Success Focus on collaborative approaches, not processes and tools Recognize that people: Won’t read detailed process descriptions Want templates and examples Keep it simple www.ambysoft.com/unifiedprocess/agileUP.html Copyright 2001-2005 Scott W. Ambler 32
View publication stats Keep in Touch Scott W. Ambler www.ambysoft.com/scottAmbler.html Copyright 2001-2005 Scott W. Ambler 33
Agile Data www.agiledata.org The Agile Data (AD) method is a collection of philosophies that will enable IT professionals within your organization to work together effectively when it comes to the data aspects of software-based systems. Six philosophies: Data . Data is one of several important aspects of software-based systems. Enterprise issues .
2. Hindi 1. Amrit Hindi Pathmala – 2 (New) 2. Worksheet File 2 3. Jungle ke dost – Supplementary reader AUP AUP Manohar Puri 3. Maths 1. Grow with numbers – 2 2. Maths Worksheet File 2 (Revised) 3. Mental Maths 2 AUP AUP AUP 4. E.V.S. 1. My Vibrant Plane t – 2 AUP 5. Value Edu. 1. Grow with values 2 AUP 6. G.K. Internal Worksheets on .
May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)
Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .
On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.
̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions
Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have
1. The need for an agile way of working 6 2. The need for an agile way of working 9 3. Agile Core Values - Agile Project Management Vs. 10 Agile Event Management 4. Agile principles 12 _Agile Principles of Agile Project Management 13 _Agile Principles of VOK DAMS Agile Event Management 14 5. Agile Methods 16 _Scrum in Short 16 _Kanban in Short 18
AUP Students enjoy the safety of living in a small, secure campus located in the heart of Downtown Los Angeles and the freedom to explore the city in all its splendor. Boarding Boarding on campus is an integral part of the AUP expe-rience. AUP Residential Life is a significant comp
