当前位置:首页 >> 信息与通信 >>

软件工程流程与准则(English Version)


Engineering Process
? ? ? ? ?
Fundamentals Enhancement Process

Escalation Process
Bug Process

Question and Answer

Fundamentals - Process
? Products, not process, make money ? A process exists to produce quality
products
– A process which inhibits quality products is a bad process

? Process, whether defined or
understood, always exists

Fundamentals - Process
? Productivity and innovation decline at
either ‘end’ of formality spectrum

? Process must evolve to be successful

Fundamentals - Product Lifecycle
? COMPANY product lifecycle being
formalized

? Key elements
– Product life phases and phase transition requirements

– Release phases: new, evolving, maintenance, static

? Products in different stages are
managed differently

Fundamentals - Release Model
? Feature-driven releases
– Marketing (& sales, engineering, etc.) defines release requirements – Engineering defines product design, development plan & schedule

– Cross-functional group reviews
– Release must deliver all product requirements

Fundamentals - Release Model
? Date-driven releases
– Marketing (sales, engineering, etc.) defines release priorities – Engineering defines product design, development plan & schedule

– Cross-functional group reviews
– Release must complete in predetermined timeframe

Fundamentals - Release Model
? Products in ‘new’ phase may be featureor date-driven

? Products in ‘evolution’ phase are datedriven

? Products in ‘maintenance’ phase are
date-driven

Fundamentals - Quality Model
? Quality = Features + Robustness + Time to
Market

? Priority order:
– Time to market
– Features

– Robustness

? Consistent with fast, immature market ? Will evolve over time

Fundamentals - Commitments
? Formal commitments
– ‘Significant’ objectives

– On-time delivery required and expected
– Commitments flow bottom-up – Development plan, or alternate written execution plan, required

Fundamentals - Commitments
? Best-effort commitments
– Less formality required

? Formal commitments will always
override best-effort commitments, when required

? Formal commitments reviewed and
tracked by senior engineering team

? Formal commitments approved by one
source

Fundamentals - Resource Allocation
? Resource allocation is a CEO decision ? Input considered from many sources ? Allocation reflects revenue and strategy
priorities

? Resource allocation tracking ? Development to QA ratio = #-# to #

Fundamentals - Activity Types
? % of engineering resources allocated to:
– Enhancements

– Quality Improvements
– Escalations

? Allocation % is the key issue

Fundamentals - Product Types
? Flagship products
– Primary revenue vehicle

? Derivative products
– Different user community – Different channel

Enhancement Process
? Development stages
Planning
Inputs

Implementation
Release Maintenance
Process Management Tools

Outputs

Enhancement Process - Planning
? Process Tool
– Enhancement Change Request database

? Stages
– Feature Priorities and/or Requirements – Specifications – Designs – Scheduling

Enhancement Process - Planning
? Inputs
– Marketing Feature Priorities or Marketing Requirements Document – Quality objectives

? Outputs
– Development Plan – Schedule

– Formal Commitment

Enhancement Process - Planning
? Key Issues
– When will a XXX feature be delivered in the YYY release?
? Can’t answer, since releases are date-driven and based on priorities that are determined at beginning of release planning process

– Flagship products drive product features – Derivative products petition for specific features, but don’t drive the definition process

Enhancement Process
? Implementation
– Development

– Unit testing
– Integration – Integration testing

Enhancement Process
? Release
– Beta

– Build Verification and QA
– Release signoff process

Enhancement Process
? Key Issues
– Flagship versus derivative quality standards differ
? Flagships have formal betas, full QA, QC, and signoff ? Derivatives only have QC and signoff

Enhancement Process
? Key Issues
– Beta sites management
? Marketing and tech support select and manage marketing beta sites (10-25)
? Engineering selects and manages test partners (3-5)

Enhancement Process
? Maintenance
– Engineering Fixes

– Patches
– Inline

? Key Issues
– Customer issue tracking - see below – OEM release limitations - patch level release or greater

Escalation Process
? Process Tool
– Escalation database

? Inputs
– Sales - must validate legitimacy of account – 100K (or >) in revenue potential/loss in 60 days – Feature or bug driven issues

– Escalations submitted to NAME, engineering escalation manager

Escalation Process
? Outputs - Engineering fixes and patch
targets
– Engineering fixes - fix targeted for specific escalation customer; limited QA
– Patch targets - collection of engineering fixes, more sophisticated QA and deployment

Escalation Process
? Key Issues
– Escalation budget & overflow conditions
? Each engineering team budgeted for % of time for escalations
? When escalation efforts exceed budget, CEO approval required ? Overflow, when approved, results in schedule change or product release feature set change

Escalation Process
? Key Issues
– Patch and release management
? Engineering fixes are for verification purposes only, not for distribution or deployment; tech support will not support an engineering fix
? Patches are supported by tech support ? Every 60-75 days fixes will ‘roll up’ into a patch ? A patch is identified by its version: 4.5 refers to the ‘major release’; 4.5(2) refers to patch 2

Bug Process
? Process Tool
– Bug tracking database

? Inputs
– any and all product deficiencies – customers, sales, tech support, engineering, marketing, ...

Bug Process
? Inputs (cont.)
– customers submit via tech support, others via email to ‘QA – ‘blessed’ sources submit directly to bug tracking systems

? Outputs
– target patches and major releases – documented fix list for every patch and major release

Bug Process
? Key Issues
– When will xxx bug be fixed?
? For showstoppers that slip pass QA, immediate attention is given - a very rare circumstance
? For non-showstopper level bugs, can’t answer since fixes depend on number of higher priority bugs in system, which can change from day to day

– Patch and release management

Bug Process
? Key Issues
– Customer feedback loop
? Information systems don’t link bug numbers to customers
? Customers don’t know when bugs they submitted are fixed, unless they read release notes or try the latest patch


赞助商链接
相关文章:
软件工程课后作业
软件工程 第一章 1.1 答: 软件危机是指在计算机软件开发、 使用与维护过程中...针对所有关键的开发活动为每 个开发成员提供了必要的准则、 模版工具指导, 并...
软件工程课后题答案
软件工程课后题答案_理学_高等教育_教育专区。第一章 1 简述软件的发展过程。 ...针对所有关键的开发活 动为每个开发成员提供了必要的准则、 模板工具指导, 并...
软件工程试题与答案 (17)
设计质量的准则( ) A.SQIC B.SQMC C.SQRC D.SQDC 5.软件复杂性度量的...4.___工具在软件详细设计过程中不采用。 A.判定表 B.IPO 图 C.PDL D.DFD...
软件工程试题与答案
编制软件需求规格说明书、软件系统的验收测试准则和...可能的条件组合 3、根据用户在软件使用过程中提出的...他不允许自然语言如英语的词汇与某种结构化程序 设计...
sentence translation English version answer
sentence translation English version answer_英语考试_外语学习_教育专区。1. We are frequently confronted with statements about the alarming rate of loss of la...
软件工程课后习题答案第五版
结构化分析:使用数据流程图、数据字典、结构化英语、判定表判定树等工具,来...模块设计的准则? 模块化是按规定的原则将一个大型软件划分为一个个较小的、...
软件工程复习资料 英文
软件工程复习资料 英文_IT/计算机_专业资料。软件工程...1) 这种模型把软件过程划分成几个顺序的阶段。阶段...version else reject change request else reject ...
软件工程考试试题(含答案)
软件设计中划分模块的一个准则( )。 A、 低内聚低耦合 B、 低内聚高耦合...软件危机 软件工程 1、软件危机是指在计算机软件的开发和维护过程中所遇到的一...
软件工程题库及答案
A 数据流图 B 数据词典 C 结构化英语 D 判定表与判定树 34. 5:需求规格...A 对重要功能的描述 B 对算法的详细过程性描述 C 软件确认准则 D 软件的性能...
软件工程复习题及答案
10.软件项目管理过程一个关键的活动是__制定项目...模块设计的准则: (1) 改进软件结构, 提高模块独立...小学五年级英语教学工作总结 大学教师个人工作总结 小学...
更多相关标签: