您好,欢迎光临有路网!
软件需求管理(用例方法)(英文版)(第2版)
QQ咨询:

软件需求管理(用例方法)(英文版)(第2版)

  • 作者:(美)Dean Leffingwell
  • 出版社:机械工业出版社
  • ISBN:9787111137870
  • 出版日期:2004年02月01日
  • 页数:502
  • 定价:¥55.00
  • 城市
    店铺名称
    店主联系方式
    店铺售价
    库存
    店铺得分/总交易量
    发布时间
    操作

    新书比价

    网站名称
    书名
    售价
    优惠
    操作

    图书详情

    内容提要
    作者采用一种易于接受的风格,讲述他们自己的实战经历,列举大量的案例研究,向我们展示了分析人员和开发人员如何把用例技术和传统的需求表达形式结合起来高效地确定需求。书中还说明了一些经过证明的用以确定、实现、验证和确认需求的技术,并给出了在项目的整个生命周期中,管理需求的六大团队技能:分析问题、理解用户需要、定义系统、管理范围、细化系统定义、构建正确系统。本书还强调不断地管理变更,描述了确保成功定义项目范围并使所有风险承担人达成共识的过程。
    目录
    ForewordPrefacetotheSecondEditionPrefacetotheFirstEditionIntroductionChapterITheRequirementsProblemTheGoalofSoftwareDevelopmentALookattheDataTheRootCausesofProjectSuccessandFailureTheFrequencyofRequirementsErrorsTheHighCostofRequirementsErrorsSummaryChapter2IntroductiontoRequirementsManagementDefinitionsWhatIsaSoftwareRequirement?WhatIsRequirementsManagement?ApplicationofRequirementsManagementTechniquesTypesofSoftwareApplicationsSystemsApplicationsTheRoadMapTheProblemDomainStakeholderNeedsMovingTowardtheSolutionDomainFeaturesoftheSystemSoftwareRequirementsSummaryChapter3RequirementsandtheSoftwareLifecycleTraditionalSoftwareProcessModelsTheWaterfallModelTheSpiralModelTheIterativeApproachLifecyclePhasesIterationsDisciplinesRequirementsintheIterativeModelSummaryChapter4TheSoftwareTeamSoftwareDevelopmentasaTeamActivityRequisiteTeamSkillsforEffectiveRequirementsManagementTeamMembersHaveDifferentSkillsTheOrganizationofSoftwareTeamsTheCaseStudyBackgroundfortheCaseStudyTheHOLISSoftwareDevelopmentTeamSummaryTeamSkill1AnalyzingtheProblemChapter5TheFivestepsinProblemAnalysisStep1:GainAgreementontheProblemDefinitionTheProblemStatementStep2:UnderstandtheRootCauses--TheProblemBehindtheProblemAddressingtheRootCauseStep3:IdentifytheStakeholdersandtheUsersStep4:DefinetheSolutionSystemBoundaryStep5:IdentifytheConstraintstoBeImposedontheSolutionSummaryLookingAheadChapter6BusinessModelingThePurposeofBusinessModelingUsingSoftwareEngineeringTechniquesforBusinessModelingChoosingtheRightTechniqueTheUnifiedModelingLanguageBusinessModelingUsingUMLConceptsFromtheBusinessModeltotheSystemsModelWhentoUseBusinessModelingSummaryLookingAheadChapter7SystemsEngineeringofSoftware-IntensiveSystemsWhatIsSystemsEngineering?PragmaticPrinciplesofSystemsEngineeringTheCompositionandDecompositionofComplexSystemsRequirementsAllocationinSystemsEngineeringOnDerivedRequirementsAQuietRevolutionWhenGenerationsCollide:GrayingBabyBoomerMeetsGenerationX-erAvoidingtheStovepipeSystemProblemWhenSubsystemsAreSubcontractsAddressingtheConundrumTheCaseStudy:SystemsEngineeringforHOLISPreliminaryUserNeedsProblemAnalysisHOLIS:TheSystem,Actors,andStakeholdersHOLISSystemsEngineeringTheSubsystemsofHOLISSummaryTeamSkill1SummaryroutTeamSkill2UnderstandingUserandStakeholderNeedsChapter8TheChallengeofRequirementsElicitationBarrierstoElicitationThe"Yes,But"SyndromeThe"UndiscoveredRuins"SyndromeThe"UserandtheDeveloper"SyndromeSummaryChapter9TheFeaturesofaProductorSystemStakeholderandUserNeedsFeaturesManagingComplexitybyPickingtheLevelofAbstractionAttributesofProductFeaturesSummaryChapter10InterviewingContext-FreeQuestionsSolutions-ContextQuestionsTheMomentofTruth:TheInterviewCompilingtheNeedsDataTheAnalyst'sSummary:10+10+10;e30TheCaseStudyANoteonQuestionnairesSummaryChapter11RequirementsWorkshopsAcceleratingtheDecisionProcessPreparingfortheWorkshopSellingtheConceptEnsuringtheParticipationoftheRightStakeholdersAttendingtoLogisticsProvidingWarm-UpMaterialsChoosingtheFacilitatorSettingtheAgendaRunningtheWorkshopProblemsandTricksoftheTradeBrainstormingandIdeaReductionProductionandFollow-UpSummaryChapter12BrainstormingandIdeaReductionLiveBrainstormingIdeaReductionPruningIdeasGroupingIdeasDefiningFeaturesPrioritizingIdeasWeb-BasedBrainstormingTheCaseStudy:TheHOLISRequirementsWorkshopTheAttendeesTheWorkshopTheSessionTheAnalysisofResultsSummaryChapter13StoryboardingTypesofStoryboardsWhatStoryboardsDoToolsforStoryboardingTipsforStoryboardingSummaryTeamSkill2SummaryTeamSkill3DefiningtheSystemChapter14AUseCasePrimerTheBenefitsofUseCasesUseCaseBasicsOnActorsUseCaseAnatomyAStep-by-StepGuidetoBuildingtheUse-CaseModelStep1:IdentifyandDescribetheActorsStep2:IdentifytheUseCasesandWriteaBriefDescriptionStep3:IdentifytheActorandUse-CaseRelationshipsStep4:OutlinetheIndividualUseCasesStep5:RefinetheUseCasesOnUseCases,Storyboarding,andUserInterfaceDesignUseCasesandUserInterfacesUseCasesandStoryboardingAUseCaseStoryboardExampleTheCaseStudy:TheHOLISUseCasesFindtheHOLISActorsFindtheHOLISUseCasesAssociatetheActorsandUseCasesOutlinetheUseCasesSummaryChapter15OrganizingRequirementsInformationOrganizingRequirementsofComplexHardwareandSoftwareSystemsOrganizingRequirementsforProductFamiliesOn"Future"RequirementsTheCaseStudy:OrganizingtheHOLISRequirementsSummaryLookingAheadChapter16TheVisionDocumentComponentsoftheVisionDocumentTheDeltaVisionDocumentTheVisionDocumentforVersion1.0TheVisionDocumentforVersion2.0TheDeltaVisionDocumentinaLegacySystemEnvironmentSummaryChapter17ProductManagementTheRoleoftheProductChampionTheProductManagerinaSoftwareProductCompanyPrimaryActivitiesforaProductManagerDrivingtheVisionMaintainingtheProductRoadMapDefiningtheWholeProductPlanSponsoringtheUse-CaseModelandSupplementaryRequirementsTestingtheProductConceptCompletingtheUserExperienceDefiningCommercialTermsPositioningandMessagingSupportingActivitiesBrandingandProductLabelingEndUserTrainingMaterialsProductDemoSalesandMarketingCollateralTheProductChampioninanIS/ITShopSummaryTeamSkill3SummaryTeamSkill4ManagingScopeChapter18EstablishingProjectScopeTheProblemofProjectScopeTheHardQuestionTheRequirementsBaselineSettingPrioritiesAssessingEffortAddingtheRiskElementReducingScopeAReasonableFirstEstimateSummaryChapter19ManagingYourCustomerEngagingCustomerstoManageTheirProjectScopeCommunicatingtheResultNegotiatingwiththeCustomerManagingtheBaselineOfficialChangesUnofficialChangesSummaryTeamSkill4SummaryTeamSkill5RefiningtheSystemDefinitionChapter20Softwaregequirements---AMoreRigorousLookLookingDeeperintoSoftwareRequirementsTheRelationshipbetweenSoftwareRequirementsandUseCasesTheRelationshipbetweenFeaturesandSoftwareRequirementsTheRequirementsDilemma:WhatversusHowExcludingProjectInformationExcludingDesignInformationMoreonRequirementsversusDesignIteratingRequirementsandDesignAFurtherCharacterizationofRequirementsFunctionalSoftwareRequirementsNonfunctionalSoftwareRequirementsDesignConstraintsSummaryLookingAheadChapter21RefiningtheUseCasesHowUseCasesEvolveTheScopeofaUseCaseTheCaseStudy:AnatomyofaSimpleUseCaseReviewingtheActorsReviewingtheNameRefiningtheDescriptionDefiningandRefiningtheFlowofEventsIdentifyingthePre-andPost-conditionsIdentifyingSpecialRequirementsSummaryofOurRefinedUseCaseExtendingUseCasesIncludingUseCasesinOtherUseCasesSummaryLookingAheadChapter22DevelopingtheSupplementarySpecificationTheRoleoftheSupplementarySpecificationExpressingFunctionalRequirementsintheSupplementarySpecificationExploringNonfunctionalRequirementsUsabilityReliabilityPerformanceSupportabilityUnderstandingDesignConstraintsSourcesofDesignConstraintsHandlingDesignConstraintsAreDesignConstraintsTrueRequirements?IdentifyingOtherRequirementsLinkingtheSupplementarySpecificationtotheUseCasesTemplatefortheSupplementarySpecificationSummaryLookingAheadChapter23OnAmbiguityandSpecificityFindingthe"SweetSpot"MaryHadaLitfieLambTechniquesforDisambiguationSummaryChapter24TechnicalMethodsforSpecifyingRequirementsPseudocodeFiniteStateMachinesDecisionTablesandDecisionTreesActivityDiagramsEntity-RelationshipModelsSummaryTeamSkill5SummaryTeamSkill6BuildingtheRightSystemChapter25FromUseCasestoImplementationMappingRequirementsDirectlytoDesignandCodeTheOrthogonalityProblemObjectOrientationTheUseCaseasaRequirementManagingtheTransitionModelingSoftwareSystemsTheArchitectureofSoftwareSystemsTheRoleoftheUse-CaseModelinArchitectureRealizingUseCasesintheDesignModelStructuralandBehavioralAspectsofCollaborationsUsingCollaborationstoRealizeSetsofIndividualRequirementsFromDesigntoImplementationSummaryLookingAheadChapter26FromUseCasestoTestCasesATester'sPerspective:MusingsontheBigBlackBoxIsaUseCaseaTestCase?CommonTestingTermsRelationshipsofTestArtifactsTheRoleoftheTestCasesUse-CaseScenariosDerivingTestCasesfromUseCases:AFour-StepProcessStepl:IdentifytheUse-CaseScenariosStep2:IdentifytheTestCasesStep3:IdentifytheTestConditionsStep4:AddDataValuestoCompletetheTestCaseManagingTestCoverageBlack-BoxversusWhite-BoxTestingwithUseCasesSummaryChapter27TracingRequirementsTheRoleofTraceabilityinSystemsDevelopmentTheTraceabilityRelationshipAGeneralizedTraceabilityModelTracingRequirementsintheSystemDefinitionDomainTracingRequirementstoImplementationTracingfromRequirementstoTestingUsingTraceabilityToolsProceedingwithoutTraceabilityToolsSummaryChapter28ManagingChangeWhyDoRequirementsChange?ExternalFactorsInternalFactors"WeHaveMettheEnemy,andTheyIsUs"AProcessforManagingChangeStep1:RecognizeThatChangeIsInevitable,andPlanforItStep2:BaselinetheRequirementsStep3:EstablishaSingleChanneltoControlChangeStep4:UseaChangeControlSystemtoCaptureChangesStep5:ManageChangeHierarchicallyRequirementsConfigurationManagementTool-BasedSupportforChangeManagementElementsImpactedbyChangeAuditTrailofChangeHistoryConfigurationManagementandChangeManagementSummaryLookingAheadChapter29AssessingRequirementsQualityinIterativeDevelopmentSoftwareProjectQualityAssessingQualityinIterativeDevelopmentRequirementsArtifactsSetsPerformingtheAssessmentQualityAssessmentChecklistsforRequirementsSummaryTeamSkill6SummaryLookingAheadGettingStartedDedicationWhatYou'veLearnedSoFarIntroductionTeamSkill1:AnalyzingtheProblemTeamSkill2:UnderstandingUserandStakeholderNeedsTeamSkill3:DefiningtheSystemTeamSkill4:ManagingScopeTeamSkill5:RefiningtheSystemDefinitionTeamSkill6:BuildingtheRightSystemChapter30AgileRequirementsMethodsMitigatingRequirementsRiskwithEffectiveRequirementsPracticesMethodologyDesignGoalsDocumentationIsaMeanstoanEndAnExtremeRequirementsMethodAnAgileRequirementsMethodARobustRequirementsMethodSummaryChapter31YourPrescriptionforRequirementsManagementSelectingYourRequirementsApproachTheSimplifyingAssumptionsThePrescriptionOntotheNextRelease!AppendixesAppendixAHOLISArtifactsAppendixBVisionDocumentTemplateAppendixCUse-CaseSpecificationTemplateAppendixDSupplementarySpecificationTemplateAppendixERequirementsManagementintheRationalUnifiedProcessAppendixFRequirementsManagementintheSEI-CMMandwithinISO9000:2000BibliographyIndex
    编辑推荐语
    许多软件项目失败的根本原因在于开发人员没有正确理解客户的真正需求。各类应用程序的开发人员都应该读一读这本书。 ——Grady Booch
    为每个开发团队面临的需求难题提供全方位的解决方案。通过阅读本书,所有开发人员都可以开阔视野,获得真知灼见。 ——lvar Jacobson
    当今,尽管开发的知识和经验不断丰富,可利用的工具也不断增多,但仍然有相当多的软件项目失败了,原因常常是在开始时没有正确地确定和定义需求,或者随着项目的展开没有正确地管理需求。本书聚焦于这一导致项目失败的关键原因,提出了一个经过证明的实用方法,帮助我们在预算内按时提交一个符合客户需要的系统。
    作者采用一种易于接受的风格,讲述他们自己的实战经历,列举大量的案例研究,向我们展示了分析人员和开发人员如何把用例技术和传统的需求表达形式结合起来高效地确定需求。书中还说明了一些经过证明的用以确定、实现、验证和确认需求的技术,并给出了在项目的整个生命周期中,管理需求的六大团队技能:分析问题、理解用户需要、定义系统、管理范围、细化系统定义、构建正确系统。
    本书还强调不断地管理变更,描述了确保成功定义项目范围并使所有风险承担人达成共识的过程。
    北京 天津 河北 山西 内蒙古 辽宁 吉林 黑龙江 上海 江苏 浙江 安徽 福建 江西 山东 河南 湖北 湖南 广东 广西 海南 重庆 四川 贵州 云南 西藏 陕西 甘肃 青海 宁夏 新疆 台湾 香港 澳门 海外