RUP Final ProjectInception

1
RUP Final Project--Inception

• CS4320Software Process
• Fall 2003

2
We want first to

• Define vision
• Make a business case
• Determine feasibility
• Make Buy/Build Decision
• Make estimate of project
• Make go/no go decision

3
Then

• Identify preliminary requirements
• Identify Candidate Architecture
• Identify External Actors
• Identify Use Cases
• Identify Development teams
• Prepare Plans

4
Vision
Develop a fully integrated, networked,
non-intrusive support tool for the Team Software
Process (TSP). This tool should be a major
enhancement of the existing TSP spreadsheet and
Dashboard products.
5
Business Case
Feasibility Technical Economic
See CBA Operational
Political
6
Business Case (Contd)
CBA Expected Pricing Structure NonCommerc
ial / Academic gt Free (0) Government
gt 50.00 / seat Commercial gt 75.00
/ seat or 5000 site Expected Sales
Income NonCommercial / Academic gt NA (0)
Government gt 5000 x 50 gt 250K
Commercial gt 10000x75 gt 750K
30x5000 gt 150K
7
Business Case
Expected Costs Overhead gt
15K Developmentgt 250K
Maintenancegt 60K
Site Customizationgt 60K
Marketinggt 10K
Supportgt (3_at_40) 120K
Total Income 1,150K Total Expense 505K
8
Should we build/buy?

• Option 1 Reuse PSP Dashboard, Greenfield TSP
• Option 2 Greenfield entire program (with reuse
  of open source modules as available)
• Option 3 Reuse PSP Dashboard and TSPi
  Spreadsheet tool

9
Houston Are we a go??
TSP
10
Preliminary Requirements
See Dash Project Requirements except
add Integration with development tools
(JBuilder 9 for initial release)
Priority of development PSP 0.1 support first
with team roll up
Simple project tracking
Team assignments
Time Log
Defect Log (May initially be manual)
PROBE worksheet and individual
estimates Roll-up
estimates into STRAT form
Divide work into iterations
Task/Schedule Sheets (Individual and
Team) Roll-Up of
Team Data into Weekly Reports
11
External Actor and Use Case ID

• We id these items at a high level
• Divide up between team members
• Each person elaborates a use case as an Analyst
• Each person designs a realization as a Designer
• We roll them up and finalize architecture

12
Conceptual (Preliminary) Architecture
13
Conceptual Architecture
14
Team Assignments

• Client Team
• JBuilder Open Tools SDK
• SWING, Forms, Visualization
• Server Team
• Computation (Betas, Std Dev)
• Data Comm
• Business Logic
• DB Team
• Table Design
• JDBC Wrappers
• SQL Query Design
• DB Admin
• Protocol Team
• Design Interactions

15
Whats Next

• Elaboration
• Detail 18 Use Cases, 1 per student
• Follow Analyst Role in Process
• Use 2335 Writeup format
• Then follow designer role and design realization
  of the use case