An Agile UP Introduction

25 530 0
  • Loading ...
    Loading ...
    Loading ...

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Tài liệu liên quan

Thông tin tài liệu

Ngày đăng: 14/09/2012, 10:51

An Agile UP Introduction Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 1www.craiglarman.comwww.valtech.comCopyright © 2002 Craig Larman. All rights reserved.AnAnAgile UP:Agile UP:IntroductionIntroductionCraig LarmanCraig LarmanCopyright © Craig Larman. www.craiglarman.com2speaker backgroundspeaker backgroundAgile and Iterative Development: A Manager’s GuideUnderway:?www.craiglarman.com?Roles at IntellAgile & Valtech. . .Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 2www.craiglarman.comwww.valtech.comCopyright © 2002 Craig Larman. All rights reserved.UP UP OverviewOverviewCopyright © Craig Larman. www.craiglarman.com4Defining our Terms: UP and RUPDefining our Terms: UP and RUP? The RUP process framework is a detailed, updated refinement of the more general UP process framework.? RUP lead architect: Philippe Kruchten.? Some use the term “UP” for “UP family” —those related to (and consistent with) the UP process framework, especially the RUP. Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 3Copyright © Craig Larman. www.craiglarman.com5inc. elaboration construction transitioniteration2-6 weeksphaseUP Practice #1: UP Practice #1: Develop IterativelyDevelop IterativelyWork in early iterations emphasize:• Risk• Criticality (high business value)• Coverage (many components are touched)Copyright © Craig Larman. www.craiglarman.com6inc. elaboration construction transitionReqs Design ImplementThrowawayPrototypeUP Practice #1: UP Practice #1: Develop IterativelyDevelop IterativelyAgile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 4Copyright © Craig Larman. www.craiglarman.com7UP Practice #2: UP Practice #2: Continuously Verify QualityContinuously Verify QualityCopyright © Craig Larman. www.craiglarman.com8UP Practice #3: UP Practice #3: Build a Cohesive ArchitectureBuild a Cohesive ArchitectureAgile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 5Copyright © Craig Larman. www.craiglarman.com9UP Practice #4 and #5: UP Practice #4 and #5: Manage Requirements and Manage ChangeManage Requirements and Manage ChangeCopyright © Craig Larman. www.craiglarman.com10UP Practice #6: UP Practice #6: Model VisuallyModel VisuallyAgile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 6Copyright © Craig Larman. www.craiglarman.com11Other Key UP IdeasOther Key UP IdeasIterationsUP DisciplinesRequirementsDesignImplementationTestDeployment Discipline Optional ArtifactsCopyright © Craig Larman. www.craiglarman.com12Other Key UP IdeasOther Key UP IdeasAgile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 7Copyright © Craig Larman. www.craiglarman.com13DomainModelRequirementsBusinessModelingDesignDesign ModelUse-CaseModelDataModelCopyright © Craig Larman. www.craiglarman.com14Useful, Common UP ArtifactsUseful, Common UP ArtifactsSupplementarySpecificationRequirementsVisionUse CasesSoftwareArchitecture Doc.DesignProjectManagementRisk ListAgile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 8Copyright © Craig Larman. www.craiglarman.com15When Work Products are Needed When Work Products are Needed use the UP Vocabulary use the UP Vocabulary ?Vision?Use Case Model?Supplementary Specification?Software Architecture DocumentCopyright © Craig Larman. www.craiglarman.com16: SystementerItem(id, quantity) .Process Sale1. Customerarrives .2. Cashiermakes newsale.3. .Use CasesSystem Sequence DiagramsmakeNewSale()SaletimeStampRegister .11ProductCatalog. . .domain conceptssystemeventsDomain ModelUse-Case ModelDesign Model: RegisterenterItem(id, quantity): ProductCatalogspec := getSpecification( id )addLineItem( spec, quantity ): Sale. . .use-caserealization withinteractiondiagramsmakeNewSale()create()Register .makeNewSale()enterItem( .) .ProductCatalog .getSpecification( .) : ProductSpecification .the designclassesdiscoveredwhile designingUCRs can besummarized inclass diagramsCashierProcessSaleUse Case Diagrams: Cashier11. . . .Captured-onDeveloperor AnalystSubjectMatterExpertDeveloperor AnalystSubjectMatterExpertDeveloperProducersDeveloperDeveloperDeveloperConsumersDataArchitect. . .Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 9Copyright © Craig Larman. www.craiglarman.com17UseUse--Case ModelCase Model: SystementerItem(id, quantity) .Process Sale1. Customerarrives .2. Cashiermakes newsale.3. .Use CasesSystem Sequence DiagramsmakeNewSale()systemeventsCashierProcessSale: CashierUse Case DiagramHandle Returns1. Customerarrives .2. . . .3. . . .Copyright © Craig Larman. www.craiglarman.com18Domain ModelDomain ModelRegisterItemStoreaddressnameSaledatetimePaymentamountSalesLineItemquantityCashierCustomerManagerProductCatalogProductSpecificationdescriptionpriceitemIDStocks*Houses1 *Used-by*Contains1 *Describes*Captured-onContained-in1 *Described-by*Records-sale-of0 1Started-byPaid-byInitiated-byLogs-completed?*? Records-sales-on111111 *1111111111 11Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 10Copyright © Craig Larman. www.craiglarman.com19Design ModelDesign Model: RegisterenterItem(id, quantity): ProductCatalogspec := getSpecification( id )addLineItem( spec, quantity ): Sale. . .makeNewSale()create()Log4JTechnical ServicesDomainPricingPersistenceDBFacadeTaxes«interface»ITaxCalculatorAdapterServicesFactorySalesRegister SalePaymentsCreditPayment«interface»ICreditAuthorizationServiceAdapterServiceAccessInventory«interface»IInventoryAdapterJessPOSRuleEnginePOSRuleEngineFacadeSOAPRegister .makeNewSale()enterItem( .) .ProductCatalog .getSpecification( .) : ProductSpecification .11Copyright © Craig Larman. www.craiglarman.com20Data ModelData Model«Table»ProductSpecification«PK» OID : char(16)Description : varchar(100) .«FK» Manu_OID : char(16)«Table»Manufacturer«PK» OID : char(16)Name : varchar(100)City : varchar(50)*1PK - primary keyFK - foreign keyApplies a UML Profile[...]... www.craiglarman.com9 UP Practice #4 and #5: UP Practice #4 and #5: Manage Requirements and Manage ChangeManage Requirements and Manage ChangeCopyright © Craig Larman. www.craiglarman.com10 UP Practice #6: UP Practice #6: Model VisuallyModel Visually Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 22Copyright © Craig Larman. www.craiglarman.com43Define basic.. .Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 1www.craiglarman.comwww.valtech.comCopyright © 2002 Craig Larman. All rights reserved. An An Agile UP: Agile UP: Introduction IntroductionCraig LarmanCraig LarmanCopyright © Craig Larman. www.craiglarman.com2speaker backgroundspeaker background Agile and Iterative Development: A Manager’s... www.craiglarman.com4Defining our Terms: UP and RUPDefining our Terms: UP and RUP? The RUP process framework is a detailed, updated refinement of the more general UP process framework.? RUP lead architect: Philippe Kruchten.? Some use the term UP for UP family” —those related to (and consistent with) the UP process framework, especially the RUP. Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved.... PhaseTransition ? Integration/QA Phase Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 24Copyright © Craig Larman. www.craiglarman.com47How to Fail with the UPHow to Fail with the UP ?Creating too many artifacts.?Focusing on learning or doing UP minutiae rather than the grasping the big ideas.Copyright © Craig Larman. www.craiglarman.com48You know you didnYou... with the UP ?Big bang process adoption?Leaders implementing iterative development and the UP don’t have direct experience working as developers in iterative development and object technology projects.?Defining changes or “enhancements” to the UP, when have not yet practiced and mastered the basics.Copyright © Craig Larman. www.craiglarman.com46How to Fail with the UPHow to Fail with the UP ?First... 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 13Copyright © Craig Larman. www.craiglarman.com25 UP AdaptationUP Adaptation? In at least 4 areas:1. Requirements2. Design3. Plan4. ProcessGreat moments in evolutionCopyright © Craig Larman. www.craiglarman.com26Adaptive Planning in the UPAdaptive Planning in the UP A, BC, DE, FG, HI, J K, MN, OP. . . .A, BC, DE,... Craig Larman. www.craiglarman.com37History and RationaleHistory and Rationale? The UP has rapidly emerged as a world-wide de facto industry standard for modern process.? Groups within many leading companies are adopting it.? IBM, Chase-Manhattan, Telia, Valtech, Alcatel, MCI, British Aerospace, Sprint, Volvo, Intel, Merrill, E&Y, Deloitte, Ericsson, . . .Copyright © Craig Larman. www.craiglarman.com38History... cycle”iteration#1#2#3www.craiglarman.comwww.valtech.comCopyright © 2002 Craig Larman. All rights reserved.Why the Why the UP? UP? Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 21Copyright © Craig Larman. www.craiglarman.com41Warning: Superimposing Waterfall ThinkingWarning: Superimposing Waterfall Thinking? There are books that give the impression of being a source of UP advice. ? They are based... www.craiglarman.com38History and RationaleHistory and RationaleWhy acceptance??It is good—combines most popular modern best practices (e.g., iterative development)?Perceived as coming from modern process experts.?It is cohesive and well documented?HTML based RUP product ?Books Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 18Copyright © Craig Larman.... rest•Minor reqchanges•Prep for deploy•Pilot testsIter12 wk. . .Iter202 wk. . .Incep-tion•Vision & biz case•Scope•Lo-fi plan & est.•“10%” reqs•Candidate arch.•Reqworkshop 1•Macro-estimation2 wk Agile UP 9/27/2002Copyright (c) 2002 Craig Larman. All rights reserved. www.craiglarman.com 16Copyright © Craig Larman. www.craiglarman.com31Follow the UP PhasesFollow the UP Phases?The . Craig Larman. All rights reserved.AnAnAgile UP :Agile UP: IntroductionIntroductionCraig LarmanCraig LarmanCopyright © Craig Larman. www.craiglarman.com2speaker. Manage Requirements and Manage ChangeManage Requirements and Manage ChangeCopyright © Craig Larman. www.craiglarman.com1 0UP Practice #6: UP Practice #6: Model
- Xem thêm -

Xem thêm: An Agile UP Introduction, An Agile UP Introduction, An Agile UP Introduction

Từ khóa liên quan