IBM-Rational-统一开发流程-RUPPPT课件

©2004IBMCorporation杰傲科技（中国）有限公司－软件部软件开发圣经-IBMRational统一开发RUPRational用户组–www.sdp.com.cn胡杰章Fox.Hu@jeyo.com.cn*Updated@v2003.06.12SR2IBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*软件开发所面对的问题和挑战 不能准确理解用户的需求； 对不断变化的需求束手无策； 系统各部分难于集成； 软件难于维护和扩充； 一些严重错误到项目后期才发现； 软件质量太差； 软件性能太低； 项目组成员的工作互相牵制，无法了解谁在何时、何地、为何改变了什么； 不可靠的建立(Build)－发布过程。IBMRationalsoftware*关于流程的定义 流程定义了应该由谁、在什么时候、从事什么样的开发活动、产生什么样的开发结果，来完成整个项目的开发目标需求系统开发流程RUP/XP/瀑布/原型法RUP=RationalUnifiedProcess*Itcanbeverydifficulttoexplainwhataprocessis,ifpeoplearen’tfamiliarwithit.Ifthisisthecase,useaninformalexamplemostpeoplecanrelateto,suchastheprocessofbalancingacheckbookattheendofthemonth.Mostofushavedevelopedaprocessweuse:thesamestepseverymonth.Itshortensthetimerequiredtoaccomplishthetaskandensuresthatwedonotforgetanysteps.Thesameappliestoasoftwareengineeringprocess.Wewantittoberepeatableandtoensurethatallrequiredtasksareaccomplishedwhenrequired.Ofcourse,asoftwareengineeringprocessismuchmorecomplexthanbalancingacheckbook,andthereisatremendousamountofinformationcontainedintheRUP.IBMRationalsoftware*RUP内容和导航图RUP把开发活动、角色、工件分为9类(Discipline)每一个迭代都会涉及到9个DisciplineIBMRationalsoftware*RUP的主要特点 迭代化开发 以架构为中心 风险驱动 用例驱动*Examples: Thedynamicstructure(phasesanditerations)ofRationalUnifiedProcesscreatesthebasisofiterativedevelopment. TheProjectManagementdisciplinedescribeshowtosetupandexecuteaprojectusingphasesanditerations. TheUse-CaseModeloftheRequirementsdisciplineandtheRiskListdeterminewhatfunctionalityyouimplementinaniteration. TheWorkflowDetailsoftheRequirementsdisciplineshowtheactivitiesandartifactsthatmakerequirementsmanagementpossible. Theiterativeapproachallowsyoutoprogressivelyidentifycomponents,decidewhichonetodevelop,whichonetoreuse,andwhichonetobuy. TheUnifiedModelingLanguage(UML)usedintheprocessrepresentsthebasisofVisualModelingandhasbecomethedefactomodelinglanguagestandard. Thefocusonsoftwarearchitectureallowsyoutoarticulatethestructure:thecomponents,thewaysinwhichtheyintegrate,andthefundamentalmechanismsandpatternsbywhichtheyinteract.IBMRationalsoftware*迭代化开发IBMRationalsoftware*迭代化开发可以降低项目风险增加可预见性确定开发优先级和项目范围更早地发现设计缺陷提高最终软件质量迭代化开发RequirementsAnalysis&DesignImplementationTestBusinessModelingPlanningInitialPlanningConfiguration&ChangeManagementEnvironmentEvaluationDeployment快速适应业务需求变化创造策略化的竞争优势业务系统需要高可靠性、可扩展性和可管理性DevelopIteratively 采用灵活的软件开发流程 每个迭代都产生可运行的结果 每个迭代都要收集用户需求反馈和做好质量控制*Lastupdated:1/19/04Thefirstsoftwaredevelopmentimperativeis“developiteratively”.Bythiswemeanthatsoftwareteams: Adoptacommondevelopmentprocesssothatallteammembersunderstandhowsoftwareiscreated,tested,andreleased. Createsuccessiveiterationsofreleasesthatyoucanuse–notprototypes,butactual,executablereleases. Checkinwithstakeholderswitheveryiteration,toensurethatuserrequirementsandqualityservicelevelsarebeingmet.Aniterativedevelopmentprocessyieldsincreasinglyimprovedversionsofasoftwaresystemuntilthesoftwaresystemisreadyfordeployment.Eachiterationincludesamixofanalysis,design,construction,andtesting,resultinginademonstrableformofthesoftware.Developmentteamsstartbyaddressingalimitedsetoffunctionspertainingtothehigh-riskareasoftheproject.Eachiterationverifiesthesystemarchitecture,theapplication’sabilitytosatisfyitsrequirements,andthequalityofthesoftware.Byadoptinganiterativedevelopmentprocess,softwareteams:ReduceprojectriskandincreasepredictabilityIterativedevelopmentallowsteamstofocusonthehardthingsfirst.Withallmajorrisksaddressedearlyon,fewer“show-stopper”mistakesarelikelyinthelaterphasesoftheproject,anddeadlinesaremoreeasilymet.Inaddition,iterativedevelopmentkeepstheultimateusersoftheapplicationapprisedofprogress,sinceaworkingversionofthesystemunderdevelopmentisalwaysavailable(demonstrable)forinspection. Shouldthebusinessenvironmentchangeornewrequirementsemerge,softwareteamscanmorereadilyincorporaterequiredchangesinthenextsoftwareiteration.Prioritizeandscopeprojectseffectively.Iterativedevelopmentallowsprojectmanagerstoscopeeachnewsoftwareiterationwithincrementalimprovements,insteadofscopingtheentireprojectfromitsinceptiontocompletion.Thisensuresthattheteamsfocusonthemostimportantaspectsoftheapplication–thosewhichcreatestrategicbusinessadvantage.Uncoverdesignflawsanderrorsearlierintheprocess--Byaddressingandmitigatingthehighestrisksfirst,andbycontinuousverificationofsoftwarequalitythroughiterativetesting,softwareprojects--includingintegrationefforts,newapplications,andextensionstolegacysystems--yieldhigherqualityapplicationsthataremorereliableandscalable.IBMRationalsoftware*风险驱动－尽早降低风险时间风险瀑布式开发风险定义阶段风险管理阶段IBMRationalsoftware*以架构为中心:模型驱动开发设计时就为将来的变化而考虑降低复杂度在合适的抽象层次工作保证架构的一致性和整个系统的质量系统业务应用信息实施 采用基于构件和面向服务的架构 快速应用开发 软件资产重用以架构为中心可以业务系统需要快速适应业务需求变化创造策略化的竞争优势高可靠性、可扩展性和可管理性*Lastupdated:1/19/04TheRUPfamilyiscustomizabletoyourteam,role,andtechnology.StartingwiththecommonmethodologyincoreRUPprovidesasharedunderstandingofterminology,deliverables,andresponsibilitiesYoucancustomizeRUPtoaddyourownprocessassetsTailorRUPtomeettheneedsofsmall,medium,orlargeteamsTeamsworkingwithspecifictools,technologies,domains;Rolesorsubteamswithspecificprocessviews.NewprocessdeliverytoolsnowenableyoutopersonalizeRUPbydeliveringthecontentmostrelevanttoyourteam.IBMRationalsoftware*以架构为中心:用可视化建模技术搭建系统架构 促进团队沟通 为软件设计提供蓝图 促进软件重用 帮助管理系统复杂度分层的模型适当地隐藏细节，帮助管理复杂度CodeClassesSubsystems*Lastupdated:1/19/04Requirementsdrivetheiterativedevelopmentapproach.Allmembersofthedevelopmentteamneedtounderstandwhattheprojectwillaccomplish,whathaschanged,andwhichrequirementshavepassedorfailedqualityobjectives.ProjectManagersandAnalystsneedtogetthelatestprojectrequirementsouttotheteam.Developers,testers,andwritersneedstoknowwhattobuild,test,anddocument.AndexecutivesandManagersneedtoknowwhat’shappeningwiththeirprojects.IBMRationalRequisiteProprovidesfast,intuitiveaccesstoallofaproject’srequirementsfromacentralizedlocation,makingiteasytostayinformedandontrack.IntegratingrequirementsmanagementwithothertoolsintheIBMSoftwareDevelopmentPlatformsavestimeandavoidsrework.WithintheIBMSoftwareDevelopmentPlatform,requirementsareintegratedwithdefecttracking,visualdevelopment,andtestingtoolstojumpstartactivitiesandprovideeachroleontheteamwithadirectwindowintoenduserneeds.Projectmanagerscanviewandcreateprojectrequirements(directlyfromIBMRationalClearQuest)andcantrackrequirementsbacktotheiroriginalsourcesasenhancementrequests.Developerscanreviewrequirementsandusecases(directlyfromwithinIBMRationalRoseXDE)whiletheyaredesigningsoftware.Testerscangetajumpstartontestingactivitiesbyviewingprojectrequirementsdirectlyfromtheirtestmanagementenvironment.Andadministratorscanincluderequirementswhencreatingprojectbaselines.Thisintegratedapproachensuresthatactivitiesallshareacommongoal:endusersatisfaction.IBMRationalsoftware*用例驱动IBMRationalsoftware*用例驱动－细节 用户插入ATM卡 系统要求输入合法的密码 用户输入正确密码,如果用户输入的密码有误,转至备选事件流A1. 系统提示用户选择“存款”或者“取款” 用户选择“取款” 系统提示用户输入取款金额 用户输入(合理)取款金额并确认,如果取款金额不合理,转至备选事件序列A2 系统从帐户中扣除取款金额,提示用户“打印收据”或者“不打印收据” 用户要求不打印收据,如果要求打印收据,转至备选事件序列A3 系统显示“交易结束”UseCase立足用户视角的描述,为具体的需求提供了充分的上下文信息,是衔接用户和开发者的纽带和沟通方式基本事件序列(BasicFlow)备选事件序列(AlternativeFlows) A1.... A2.... ...IBMRationalsoftware*RUP的核心概念 软件工程流程 角色 活动 步骤 工件 检查点 工作指南 工作流程 核心工作流程 工作流程明细IBMRationalsoftware*工程流程IBMRationalsoftware*RUP的内容结构-WorkflowBusinessModelingWorkflowRequirementsWorkflowIBMRationalsoftware*工作流程和细节Example:RequirementsWorkflowIBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*RUP角色定义和工件 角色 分析员 开发人员 测试员 经理 其他 工件IBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*RUP四个阶段 先启 精化 构建 产品化IBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*RUP9个工作流 业务建模 需求 分析设计 实施 测试 部署 配置管理 项目管理 环境IBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*关于RUP的一些误解RUP太庞大、太复杂了我们没有时间来实施RUPRUP只适用于新项目RUP只适用于大项目*Whatkindsofthingshaveyouheardwhentalkingaboutdevelopmentprocesses?[usethisasanopportunitytosolicitaudiencefeedback]IBMRationalsoftware*RUP太庞大、太复杂了 一切源于对RUP不够了解 RUP产品本身并不是一本适合通读的书，更多的用于参考和查阅 RUP将开发活动、角色和工件分为9个Discipline来进行组织管理 IBM提供了关于RUP的培训 PRJ270:EssentialsofRationalUnifiedProcess PRJ480:MasteringtheManagementofIterativeDevelopmentIBMRationalsoftware*RUP只适用于大项目 RUP适用于任何规模的项目 很多RUP项目都是中小规模的 RUP本身就带有适用于中小型项目的流程配置 RUPforsmallprojects RUPConfigurationfor.NETDevelopers RUPConfigurationforJ2EEDevelopers RUP在实施前必须进行裁剪 RUPBuilder可以帮助你对RUP内容进行裁剪–只留下你需要的! 包括了中小型配置的模板和正式／非正式工件的插件 可以在IBM网站上找到很多2-6人,3-4个月的小型项目的成功案例IBMRationalsoftware*RUP只适用于新项目 RUP既适用于新项目，也适用于在老系统上改进功能的项目 所有的软件项目基本上都可以采用基于RUP的流程来控制项目风险，保证开发进度和提高软件质量 一些参考案例 以RUP为基础开发的EPIC(EvolutionaryProcessforIntegratingCOTS-BasedSystems)流程http://www.sei.cmu.edu/publications/documents/02.reports/02tr009.html “UsingRUPtoEvolveLegacyProjects…”,PhilippeKruchtenhttp://www.therationaledge.com/content/may_01/t_legacy_pk.htmlIBMRationalsoftware*我们没有时间来实施RUP 如果你没有时间来实践一个正确的开发流程，一个不恰当的流程有可能浪费你更多的时间和资源? 解决方法之一:把RUP当作一个知识库 不带任何强制的命令，因而具有最少的风险和代险 就象是一些普通的培训、书和杂志一样 解决方法之二:实践RUP时专注于产生最快的效果 配合以培训和指导(mentoring)采用渐增式的实践方法来不断地改变现有的开发行为 不要追求大而全，专注于一些关键的开发领域 使用导师或咨询顾问来加速整个过程 实践RUP是一个持续的过程IBMRationalsoftware*内容 RUP概述 RUP的特点 RUP的核心概念 RUP的角色定义和工件 RUP的4个阶段 RUP的9工作流 RUP的误解 RUP实施流程IBMRationalsoftware*RUP实施流程－在组织中实施流程审慎方法典型方法快速方法IBMRationalsoftware*RUP实施流程－在项目中实施流程IBMRationalsoftware*总结:RUP是一个经过实践考验的、实用并且灵活的软件开发流程 RUP是一个可定制的流程平台框架，它可以帮助开发团队解决以下问题： 管理人员 在所有的项目中实践总结的最佳实践经验和工具，从而获得一致而稳定的结果 项目经理 根据项目的具体需要来制定相应的开发流程 实践者 获取完成工作的指南 个性化流程内容来表述特定的开发挑战、技术和工具*Akeyfactorinprojectsuccessistodefine,anduse,arepeatablewaytodevelopsoftware.Arepeatableprocessmeansmoreefficiency,lessreworkandconfusion,andbetterquality.RUPprovidestheframeworkforsuchaprocess.Itsuppliestheimportantcomponentsthatshouldcompriseanyprocess:whodoeswhat(roles);whattheydo(activities);howtheydoit(toolmentors);andwhattheyproduce(artifacts).WeknowthatorganizationsthathaveaprocessinplacemaywanttousethebestfromRUPbutalsoincludetheirowninformation.SowemadeRUPconfigurable.ItispossibletomodifyRUPtomeetyourneeds,fromsmallchangestolargeones.Andweprovidetoolstohelp.Therearemanypainsaroundsoftwaredevelopmentfromexecutivestoprojectmanagertopractitioners.Forexecutivesthebestpracticesencapsulatedintheprocess,alongwithit'sabilitytobemodifiedmeanthatanorganizationcanhaveconsistentresultsacrossallprojects.ForprojectmanagerstheRUPBuilderandPlug-insmeansitispossibletoconfigureRUPtomeettheneedsofeachproject.Andforpractitioners,theonesonthe"frontline",therole-specificcontentandtheirabilitytoseejustwhattheywantviaMyRUPmeantheygettheguidancetheyneedtodotheirjobwell.TheRationalUnifiedProcessisprovenandpractical:ithasbeenusedonthousandsofprojectworldwide.Thatwouldnothavebeenpossibleifitwerenotflexible,havingtheabilitytoadaptyouyourprocessandyourculture.IBMRationalsoftware*推荐两本关于RUP书IBMRationalsoftware*杰傲科技（中国）有限公司http://www.jeyo.com.cn/*IBMRationalsoftware*关于杰傲科技－www.jeyo.com.cn IBMRational在华南区合作伙伴 提供Rational以下服务 主办每月的Rational公开课 提供Rational收费深入培训 提供Rational实施和咨询顾问服务 业务范围和产品 为国内外企业提供软件外包开发、支持服务 拥有实现ITIL的JeyoiServiceDesk产品系列 拥有企业协作平台产品，SmartOA、EnterpriseCollaborationPlatform*Updated@v2003.06.12SR2*Itcanbeverydifficulttoexplainwhataprocessis,ifpeoplearen’tfamiliarwithit.Ifthisisthecase,useaninformalexamplemostpeoplecanrelateto,suchastheprocessofbalancingacheckbookattheendofthemonth.Mostofushavedevelopedaprocessweuse:thesamestepseverymonth.Itshortensthetimerequiredtoaccomplishthetaskandensuresthatwedonotforgetanysteps.Thesameappliestoasoftwareengineeringprocess.Wewantittoberepeatableandtoensurethatallrequiredtasksareaccomplishedwhenrequired.Ofcourse,asoftwareengineeringprocessismuchmorecomplexthanbalancingacheckbook,andthereisatremendousamountofinformationcontainedintheRUP.*Examples: Thedynamicstructure(phasesanditerations)ofRationalUnifiedProcesscreatesthebasisofiterativedevelopment. TheProjectManagementdisciplinedescribeshowtosetupandexecuteaprojectusingphasesanditerations. TheUse-CaseModeloftheRequirementsdisciplineandtheRiskListdeterminewhatfunctionalityyouimplementinaniteration. TheWorkflowDetailsoftheRequirementsdisciplineshowtheactivitiesandartifactsthatmakerequirementsmanagementpossible. Theiterativeapproachallowsyoutoprogressivelyidentifycomponents,decidewhichonetodevelop,whichonetoreuse,andwhichonetobuy. TheUnifiedModelingLanguage(UML)usedintheprocessrepresentsthebasisofVisualModelingandhasbecomethedefactomodelinglanguagestandard. Thefocusonsoftwarearchitectureallowsyoutoarticulatethestructure:thecomponents,thewaysinwhichtheyintegrate,andthefundamentalmechanismsandpatternsbywhichtheyinteract.*Lastupdated:1/19/04Thefirstsoftwaredevelopmentimperativeis“developiteratively”.Bythiswemeanthatsoftwareteams: Adoptacommondevelopmentprocesssothatallteammembersunderstandhowsoftwareiscreated,tested,andreleased. Createsuccessiveiterationsofreleasesthatyoucanuse–notprototypes,butactual,executablereleases. Checkinwithstakeholderswitheveryiteration,toensurethatuserrequirementsandqualityservicelevelsarebeingmet.Aniterativedevelopmentprocessyieldsincreasinglyimprovedversionsofasoftwaresystemuntilthesoftwaresystemisreadyfordeployment.Eachiterationincludesamixofanalysis,design,construction,andtesting,resultinginademonstrableformofthesoftware.Developmentteamsstartbyaddressingalimitedsetoffunctionspertainingtothehigh-riskareasoftheproject.Eachiterationverifiesthesystemarchitecture,theapplication’sabilitytosatisfyitsrequirements,andthequalityofthesoftware.Byadoptinganiterativedevelopmentprocess,softwareteams:ReduceprojectriskandincreasepredictabilityIterativedevelopmentallowsteamstofocusonthehardthingsfirst.Withallmajorrisksaddressedearlyon,fewer“show-stopper”mistakesarelikelyinthelaterphasesoftheproject,anddeadlinesaremoreeasilymet.Inaddition,iterativedevelopmentkeepstheultimateusersoftheapplicationapprisedofprogress,sinceaworkingversionofthesystemunderdevelopmentisalwaysavailable(demonstrable)forinspection. Shouldthebusinessenvironmentchangeornewrequirementsemerge,softwareteamscanmorereadilyincorporaterequiredchangesinthenextsoftwareiteration.Prioritizeandscopeprojectseffectively.Iterativedevelopmentallowsprojectmanagerstoscopeeachnewsoftwareiterationwithincrementalimprovements,insteadofscopingtheentireprojectfromitsinceptiontocompletion.Thisensuresthattheteamsfocusonthemostimportantaspectsoftheapplication–thosewhichcreatestrategicbusinessadvantage.Uncoverdesignflawsanderrorsearlierintheprocess--Byaddressingandmitigatingthehighestrisksfirst,andbycontinuousverificationofsoftwarequalitythroughiterativetesting,softwareprojects--includingintegrationefforts,newapplications,andextensionstolegacysystems--yieldhigherqualityapplicationsthataremorereliableandscalable.*Lastupdated:1/19/04TheRUPfamilyiscustomizabletoyourteam,role,andtechnology.StartingwiththecommonmethodologyincoreRUPprovidesasharedunderstandingofterminology,deliverables,andresponsibilitiesYoucancustomizeRUPtoaddyourownprocessassetsTailorRUPtomeettheneedsofsmall,medium,orlargeteamsTeamsworkingwithspecifictools,technologies,domains;Rolesorsubteamswithspecificprocessviews.NewprocessdeliverytoolsnowenableyoutopersonalizeRUPbydeliveringthecontentmostrelevanttoyourteam.*Lastupdated:1/19/04Requirementsdrivetheiterativedevelopmentapproach.Allmembersofthedevelopmentteamneedtounderstandwhattheprojectwillaccomplish,whathaschanged,andwhichrequirementshavepassedorfailedqualityobjectives.ProjectManagersandAnalystsneedtogetthelatestprojectrequirementsouttotheteam.Developers,testers,andwritersneedstoknowwhattobuild,test,anddocument.AndexecutivesandManagersneedtoknowwhat’shappeningwiththeirprojects.IBMRationalRequisiteProprovidesfast,intuitiveaccesstoallofaproject’srequirementsfromacentralizedlocation,makingiteasytostayinformedandontrack.IntegratingrequirementsmanagementwithothertoolsintheIBMSoftwareDevelopmentPlatformsavestimeandavoidsrework.WithintheIBMSoftwareDevelopmentPlatform,requirementsareintegratedwithdefecttracking,visualdevelopment,andtestingtoolstojumpstartactivitiesandprovideeachroleontheteamwithadirectwindowintoenduserneeds.Projectmanagerscanviewandcreateprojectrequirements(directlyfromIBMRationalClearQuest)andcantrackrequirementsbacktotheiroriginalsourcesasenhancementrequests.Developerscanreviewrequirementsandusecases(directlyfromwithinIBMRationalRoseXDE)whiletheyaredesigningsoftware.Testerscangetajumpstartontestingactivitiesbyviewingprojectrequirementsdirectlyfromtheirtestmanagementenvironment.Andadministratorscanincluderequirementswhencreatingprojectbaselines.Thisintegratedapproachensuresthatactivitiesallshareacommongoal:endusersatisfaction.*Whatkindsofthingshaveyouheardwhentalkingaboutdevelopmentprocesses?[usethisasanopportunitytosolicitaudiencefeedback]*Akeyfactorinprojectsuccessistodefine,anduse,arepeatablewaytodevelopsoftware.Arepeatableprocessmeansmoreefficiency,lessreworkandconfusion,andbetterquality.RUPprovidestheframeworkforsuchaprocess.Itsuppliestheimportantcomponentsthatshouldcompriseanyprocess:whodoeswhat(roles);whattheydo(activities);howtheydoit(toolmentors);andwhattheyproduce(artifacts).WeknowthatorganizationsthathaveaprocessinplacemaywanttousethebestfromRUPbutalsoincludetheirowninformation.SowemadeRUPconfigurable.ItispossibletomodifyRUPtomeetyourneeds,fromsmallchangestolargeones.Andweprovidetoolstohelp.Therearemanypainsaroundsoftwaredevelopmentfromexecutivestoprojectmanagertopractitioners.Forexecutivesthebestpracticesencapsulatedintheprocess,alongwithit'sabilitytobemodifiedmeanthatanorganizationcanhaveconsistentresultsacrossallprojects.ForprojectmanagerstheRUPBuilderandPlug-insmeansitispossibletoconfigureRUPtomeettheneedsofeachproject.Andforpractitioners,theonesonthe"frontline",therole-specificcontentandtheirabilitytoseejustwhattheywantviaMyRUPmeantheygettheguidancetheyneedtodotheirjobwell.TheRationalUnifiedProcessisprovenandpractical:ithasbeenusedonthousandsofprojectworldwide.Thatwouldnothavebeenpossibleifitwerenotflexible,havingtheabilitytoadaptyouyourprocessandyourculture.*