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

软件工程流程与准则(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


相关文章:
软件工程复习资料_英文
软件工程复习资料_英文_工学_高等教育_教育专区。...模块独立性可用两个定量准则来度量: 耦合 (coupling...version else reject change request else reject ...
软件工程判断题
软件工程判断题_理学_高等教育_教育专区。1、软件就...既包括传统的程序设计风格准则,也包括为适应而面向...英文个人简历模板 创意简历模板汇集 推理型题分析与总结...
软件工程考试试题(含答案)
10. 大型软件测试包括 、 、确认测试和 四个步骤。 二、单项选择题(每小题 2 分,共 20 分) 1. 软件设计中划分模块的一个准则( )。 A、 低内聚低...
软件工程作业
软件工程作业_计算机软件及应用_IT/计算机_专业资料。第 1 章 概述 1.什么叫...2.面向对象分析的过程、遵循的准则是什么? 答:面向对象分析的过程:①发现对象...
软件工程第一二三章习题参考答案
第一章 软件工程概述软件是计算机程序及其有关的数据和文档的结合。 软件危机是...它确定软件开发的各个阶段,规定每一阶段的活动、 产品、验收的步骤和完成准则。...
软件工程基础(复习题及答案)
3.简述文档在软件工程中的作用。 答: (1) 提高软件开发过程的能见度 (2) ...模块设计的准则: (1) 改进软件结构, 提高模块独立性:在对初步模块进行合 并...
软件工程习题解答_图文
6.什么是软件结构?简述软件结构设计优化准则。 软件结构:软件系统的模块层次结构...答:软件配置管理:软件配置管理(SCM)用于整个软件工程过程,目标是表示变更,控制...
致会员有关停车流程事宜english version
致会员有关停车流程事宜english version_生产/经营管理_经管营销_专业资料 暂无评价|0人阅读|0次下载|举报文档致会员有关停车流程事宜english version_生产/经营管理...
软件工程随堂练习
软件工程过程是将软件工程( )综合起来以达到合理、及时地进行计算机软件开发的...准则 D. 基本原则 3、软件需求分析应从问题的信息域功能域出发。信息域应...
软件开发项目规范
详细说明这个项目中所应用的软件工程方法和技术。 对工程方法中的各种工作任务进行规范,明确执行的时机、流程和准则等。这 些工作任务包括: 常规开发活动(需求分析、...
更多相关标签:
english version | qq english version | wps english version | 360 english version | 百度 english version | map english version | 百度englishversion | didi english version |