The Relationship Between Version Control, DefectIssue 之间的版本控制的关系,defectissue.pptVIP

The Relationship Between Version Control, DefectIssue 之间的版本控制的关系,defectissue.ppt

  1. 1、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。。
  2. 2、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  3. 3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
  4. 4、该文档为VIP文档,如果想要下载,成为VIP会员后,下载免费。
  5. 5、成为VIP后,下载本文档将扣除1次下载权益。下载后,不支持退款、换文档。如有疑问请联系我们
  6. 6、成为VIP后,您将拥有八大权益,权益包括:VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
  7. 7、VIP文档为合作方或网友上传,每下载1次, 网站将根据用户上传文档的质量评分、类型等,对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档
查看更多
2004/05/13 Copyright 2004 Weatherall, Ltd. 2004/05/13 Copyright 2004 Weatherall, Ltd. The Relationship Between Version Control, Defect/Issue Management, Build Management, Release Management A Little History – VC Version Control (VC) has a mixed origin Development created the tools to version source code and later designs and documentation Quality developed the manual process to allow auditing of changes to first physical and later software items They continue to argue over who “owns” VC Infrastructure Support (IT) assumes they own the severs and tool installations A Little History – DIET Defect, Issue and Enhancement (DIET) tools and processes have evolved Tools were first created to report to Development Development was required to respond to items reported Management learned to capitalize on data and trends A Little More History – DIET Increased need for management decision support and a need for traceability caused tools to evolve to support a linkage between versions of items changed to individual DIET records Management desires for process and workflow management have led to the continued evolution of DIET tools Confusion over rolls, requirements and ownership of DIET tools and processes continues to grow A Little History – BM Build Management (BM) was created by Development Still considered a Development activity Quality realized this does not promote consistency for production builds No one wants to own, but also does not want someone else to own And a Last Bit of History – RM Release Management (RM) evolved from Production Control Barely recognized as separate from BM Often not even performed as a formal activity Considered by many beyond the bounds of classical Quality, especially in the realm of software SCM Components Visibility of SCM Components Viewed By Engineering Visibility of SCM Components Viewed By End User SCM Component Relationships Functional View Data Flow View So Why Should Ownership Reside with SCM? Quality cares that things work, SCM ca

文档评论(0)

cai + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档