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

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


相关文章:
课程名称-英文(软件工程)
课程名称-英文(软件工程)_英语学习_外语学习_教育专区。体育 4-1 Physical Education Ⅳ-1 艺术欣赏Ⅰ Appreciation of Art Ⅰ 大学英语 3-1 College English Ⅲ...
ISO9001:2015 English Version
ISO9001:2015 English Version_企业管理_经管营销_专业资料。ISO 9001:2015 Quality management systems —Requirements Introduction 0.1 General The adoption of a ...
软件工程规范
【名词定义】 软件开发工程化:按照近代科学继产业形成的一套工程化方法和思想,把软件开发看作是一个过程, 先进性可行性论证,进行调查分析,再进行逻辑设计,物理设计...
NDA-English Version
NDA-English Version_法律资料_人文社科_专业资料 暂无评价|0人阅读|0次下载|举报文档NDA-English Version_法律资料_人文社科_专业资料。Confidentiality agreement ...
致会员有关停车流程事宜english version
致会员有关停车流程事宜english version_生产/经营管理_经管营销_专业资料 暂无评价|0人阅读|0次下载|举报文档致会员有关停车流程事宜english version_生产/经营管理...
软件工程(第2版)_在线作业_1
( t) ? ? 纠错得分: 5 知识点: 4.3 软件结构优化准则 6. (5 分) 软件结构图是精确表达程序结构的图形表示法。因此,有时也可以将软件结构图当作程 序流程...
软件工程教学大纲(正式版)
英文名称名:Software Engineering 总学时:54 学时 学分:3 课程类别:专业必修课...开发软件项目的 工程化的方法和技术及在开发过程中应遵循的流程准则、标准...
软件工程第一二三章习题参考答案
第一章 软件工程概述软件是计算机程序及其有关的数据和文档的结合。 软件危机是...它确定软件开发的各个阶段,规定每一阶段的活动、 产品、验收的步骤和完成准则。...
软件工程 重点归纳
化 主要特征:按工程管理的方法管理整个软件开发过程...软件测试准则 1、以用户需求为基准 2、严格执行测试...小学五年级英语教学工作总结 大学教师个人工作总结 小学...
软件工程文档模板(完整规范版)
交通局开发软件项目的过程, 通过规范软件项目承 担...还应该为牠取—個简短地英文名称, 该英文名称应该符合...49 4.2.4 文档质量地度量准则 ......
更多相关标签: