1 / 38
文档名称:

(Ebook-Pdf) Rational Software - Process Description And Workflows In Rup(1).pdf

格式:pdf   页数:38
下载后只包含 1 个 PDF 格式的文档,没有任何的图纸或源代码,查看文件列表

如果您已付费下载过本站文档,您可以点这里二次下载

(Ebook-Pdf) Rational Software - Process Description And Workflows In Rup(1).pdf

上传人:kuo08091 2013/12/23 文件大小:0 KB

下载得到文件列表

(Ebook-Pdf) Rational Software - Process Description And Workflows In Rup(1).pdf

文档介绍

文档介绍:RationalRational UnifiedUnified ProcessProcess
ProcessProcess DescriptionDescription andand WorkflowsWorkflows
Mike Fourman
2001-10-22 Cs2 Software Engineering
DescribingDescribing ProcessesProcesses
· The RUP uses four elements to describe
processes:
­ Workers – describe a role, some people have
many roles.
­ Activities – small, definable, reusable tasks
that can be allocated to a single worker.
­ Artifacts – usually process deliverables, like:
use cases, code, plans, test cases, test
results.
­ Workflows – coordinated sequences of
activities.
2001-10-22 Cs2 Software Engineering
RUPRUP WorkflowsWorkflows
· There are 9 workflows, 6 engineering workflows:
­ Business modelling
­ Requirements
­ Development & Analysis
­ Implementation
­ Test
­ Deployment
· And 3 supporting workflows:
­ Project management
­ Configuration and Change Management
­ Environment
2001-10-22 Cs2 Software Engineering
RequirementsRequirements WorkflowWorkflow
· Workflows are followed iteratively through each
iteration of each phase of the RUP.
· Effort expended in each workflow depends on the
phase.
· We describe the requirements workflow in more
detail
2001-10-22 Cs2 Software Engineering
Capturing/discoveringCapturing/discovering requirementsrequirements
· More difficult and more important than
writing code
· Users know what they have, not what
they need
­ They will better understand what
they need after they see it.
­ Nobody needed the y
saw it.
­ User cannot envision the possibilities
enabled by technology
Technology Functionality Requirements
Push Pull
2001-10-22 Cs2 Software Engineering
Capturing/discoveringCapturing/discovering requirementsrequirements
(continued)(continued)
· Developer is rarely the user
· Diversity of users
· Support the user’s mission, not only the user
· User needs and missions are constantly
changing
· The new system will impact the user’s needs,
res