<z>RUP Template : Business Case
<Project Name>
Business Use-Case Specification: <Business Use-Case Name>
<o:p> </o:p>
Version <1.0><o:p></o:p>
<o:p> </o:p>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]
[Note: If you are not using Rational RequisitePro, then this document template should be used to capture the actual Business Use Case including the workflow, special requirements, and performance goals of the Business Use Case. This file should be linked to the corresponding business use case in the Rational Rose model.
If you use Rational SoDA, then this document is used as input to the business use-case report that combines this content with use-case diagrams from Rose.]
Revision History
Date<o:p></o:p> |
Version<o:p></o:p> |
Description<o:p></o:p> |
Author<o:p></o:p> |
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p>
Table of Contents
<!---->1. Introduction <!---->2<!----><!----><o:p></o:p>
1.1 Purpose <!---->2<!----><!----><o:p></o:p>
1.2 Scope <!---->2<!----><!----><o:p></o:p>
1.3 Definitions, Acronyms, and Abbreviations <!---->2<!----><!----><o:p></o:p>
1.4 References <!---->2<!----><!----><o:p></o:p>
1.5 Overview <!---->2<!----><!----><o:p></o:p>
2. Business Use-Case Name <!---->2<!----><!----><o:p></o:p>
2.1 Brief Description <!---->2<!----><!----><o:p></o:p>
3. Goals <!---->2<!----><!----><o:p></o:p>
4. Performance Goals <!---->2<!----><!----><o:p></o:p>
4.1 <name of performance goal> <!---->2<!----><!----><o:p></o:p>
5. Workflow <!---->2<!----><!----><o:p></o:p>
5.1 Basic Workflow <!---->2<!----><!----><o:p></o:p>
5.1.1 <name of workflow step> <!---->2<!----><!----><o:p></o:p>
5.2 Alternative Workflows <!---->2<!----><!----><o:p></o:p>
5.2.1 <name of workflow step> <!---->2<!----><!----><o:p></o:p>
6. Category <!---->2<!----><!----><o:p></o:p>
7. Risk <!---->2<!----><!----><o:p></o:p>
8. Possibilities <!---->2<!----><!----><o:p></o:p>
9. Process Owner <!---->2<!----><!----><o:p></o:p>
10. Special Requirements <!---->2<!----><!----><o:p></o:p>
10.1 <Name of Special Requirement> <!---->2<!----><!----><o:p></o:p>
11. Extension Points <!---->2<!----><!----><o:p></o:p>
11.1 <Name of Extension Point> <!---->2<!----><!----><o:p></o:p>
<!---->
<!---->Business Use-Case Specification: <Business Use-Case Name><!---->
<!---->1. <!---->Introduction
[The introduction of the Business Use-Case Specification provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Business Use-Case Specification.
Note: If you are not using Rational RequisitePro, then this document template should be used to capture the actual Business Use Case including the workflow, special requirements, and performance goals of the Business Use Case. This file should be linked to the corresponding business use case in the Rational Rose model.
If you use Rational SoDA, then this document is used as input to the business use-case report that combines this content with use-case diagrams from Rational Rose.]
<!---->1.1 <!---->Purpose
[Specify the purpose of this Business Use-Case Specification.]
<!---->1.2 <!---->Scope
[A brief description of the scope of this Business Use-Case Specification; what Use Case model(s) it is associated with and anything else that is affected or influenced by this document.]
<!---->1.3 <!---->Definitions, Acronyms, and Abbreviations
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Business Use-Case Specification. This information may be provided by reference to the project’s Glossary.]
<!---->1.4 <!---->References
[This subsection provides a complete list of all documents referenced elsewhere in the Business Use-Case Specification. Identify each document by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
<!---->1.5 <!---->Overview
[This subsection describes what the rest of the Business Use-Case Specification contains and explains how the document is organized.]
<!---->2. <!---->Business Use-Case Name
<!---->2.1 <!---->Brief Description
[The description briefly conveys the role and purpose of the business use case. A single paragraph will suffice for this description.]
<!---->3. <!---->Goals
[A specification of the measurable goals or objectives of the business use case.]
<!---->4. <!---->Performance Goals
[A specification of the metrics relevant to the business use case and a definition of the goals you want to achieve by using those metrics.]
<!---->4.1 <!----><name of performance goal>
[A brief description of the performance goal.]
<!---->5. <!---->Workflow
[A textual description of the workflow the business use case represents. The workflow describes what the business does to deliver value to a business actor, not how the business solves its problems.
Only one level of workflow steps is indicated in the subsections below, but you may add more levels if necessary.]
相关推荐
02use case补充内容.ppt<br>4e-03sequence-collaboration.ppt<br>4e-04class-object-package.ppt<br>4e-05状态-活动-构件-配置图.ppt<br>4e-06Web建模.ppt<br>4e-07Rose开发工具.ppt<br>4e-08UML与设计模式.ppt<br>...
银行业的应用 17<br>界面设计指导原则 19<br>论开放系统应用的互操作性 20<br>基于RUP的软件过程及应用 20<br>长春经济技术开发区的网络安全建设 25<br>基于 B/S 结构的电子政务信息系统的研究与开发 29<br>基于J2EE...
一个rup协议,能解决如下问题: <br>1. lost; never delivered <br>2. partially destroyed (data corruption) <br>3. delivered out of order <br>4. duplicated <br>参看...
5.1.1 <用例名> 4 6. 逻辑视图 6 6.1 对架构重要的模型元素 6 6.1.1 <类名> 6 6.1.2 <包名> 6 6.2 架构视图 – 包和子系统分层 6 6.2.1 <类名> 7 6.2.2 <包名> 7 7. 进程视图 7 7.1 <类图名> 8 7.1.1 <进程元素名> 8...
现在RUP如日中天,需求分析是第一步,可以看作是高级系统分析员的必备知识,那么,如果用面向对象的分析技术来描述需求呢?你还在为怎么建模而烦吗?你还不知道如果开始您的系统用例分析吗?那么强烈建议您看看这本...
软件开发过程产生的背景 <br/>软件开发过程是什么<br/>RUP是什么 <br/>ISO9001是什么<br/>CMM是什么 <br/>UML是什么<br/>XP是什么 <br/>软件开发过程的比较<br/>测试在软件开发过程中的地位<br/>
在RUP的"ATLAS TDAQ <sub-group> <component> Requirements"模板中,我们可以看到以下关键组成部分: 1. **文档信息**:包括文档版本(如1.0)、文档ID(ATLAS-TDAQ-2002-XXX)、日期和状态(草案或最终)。这些...
<1>管理员类型:安装管理控制台,管理工具,网络服务,使用程序,和基本的客户端软件。 <2>运行时类型:只安装应用开发程序,网络服务,基本客户软件 <3>自定义:自己决定的组件安装。 (4) Oracle ...
后续的,总共3部分的!<br>
2. 包图是用来组织和管理系统的组件,关系包括`<<use>>`(使用)、`<<access>>`(访问)、`<<trace>>`(跟踪),不包括`<<stub>>`。 3. 类图中,继承关系通常用带空心箭头的实线表示,选项C符合描述。 4. 类图中,...
《RUP用例模型调查(更新)》 这篇文章聚焦于软件过程管理中的迭代开发方法,特别是在细化(Elaboration)阶段的文档制作。它源于作者在英国科夫大学(Coventry University)学习期间完成的一份作业,主要讨论了...
2. **包图中的关系**:包图中的关系有`<<use>>`(使用)、`<<access>>`(访问)和`<<trace>>`(追踪),但没有`<<stub>>`。 3. **继承关系的表示**:在类图中,继承关系通常由一个空心的三角形指向基类,表示子类...
RUP模板,为开发者努力此文档的目的是收集、分析和定义<<系统名>>的高层次需求和特性。它侧重于涉众和目标用户所需的功能以及这些需要存在的原因。<<系统名>>如何满足这些需要的详细情况记录在用例和补充规约中。
总的来说,"RUP课件中英文版本.7z"提供了全面的RUP学习资源,无论你是初学者还是经验丰富的开发者,都能从中受益。通过系统地学习和应用RUP,你可以更好地掌握软件开发的全过程,从而提高你的专业素养和项目成功率。
在包图中,存在多种关系,如`<<use>>`、`<<access>>`和`<<trace>>`,但不包括`<<stub>>`(D)。`<<stub>>`通常与代理模式相关,而不是包之间的关系。 #### 3. 类图中的继承关系 类图是UML中最常用的图之一,用于描述...
**RUP(Rational Unified Process)模板详解** RUP,全称为 Rational Unified Process,是由IBM公司开发的一种软件开发过程框架,它提供了一种结构化的方法来管理软件开发生命周期中的各个阶段。RUP模板是RUP过程的...
每个特征通常表述为<行动><结果><对象>的形式,便于理解和实施。 在实际应用中,考虑到上手难度和理论成熟度,本文作者选择了用例分析技术作为首选实践。用例分析技术由Ivar Jacobson在1967年提出,其核心是用例...
### Rational Unified Process (RUP) 最佳实践 #### 什么是Rational Unified Process (RUP)? Rational Unified Process(简称RUP)是一种软件工程过程,它为软件开发团队提供了一个结构化的方法来指导整个软件开发...
RUP,全称为 Rational Unified Process,是IBM公司开发的一种软件开发过程框架,它提供了一种结构化的方法来管理和构建复杂的软件项目。RUP的核心理念是迭代和增量开发,强调了软件开发过程中的灵活性、可适应性和...
《RUP导论》一书深入浅出地介绍了Rational Unified Process(RUP)这一软件开发过程,它是Rational公司开发的一种系统化的软件工程过程,旨在帮助开发团队在规定的时间和预算内开发出符合用户需求的高质量软件产品。...