Register now to access 7 million high quality study materials (What's Course Hero?) Course Hero is the premier provider of high quality online educational resources. With millions of study documents, online tutors, digital flashcards and free courseware, Course Hero is helping students learn more efficiently and effectively. Whether you're interested in exploring new subjects or mastering key topics for your next exam, Course Hero has the tools you need to achieve your goals.
36 Pages
EC-22
Course: CS 577, Fall 2009School: USC
Rating:
Word Count: 2121
Document Preview
S USC C E University of Southern California Center for Software Engineering Software Productivity Perspectives, Paradoxes, Pitfalls, and Prospects Barry Boehm, USC Microsoft Presentation December 6,1999 boehm@sunset.usc.edu http://sunset.usc.edu USC C S E University of Southern California Center for Software Engineering Outline Software Productivity Goals and Metrics Productivity Paradoxes and Pitfalls...
Unformatted Document Excerpt
Coursehero >> California >> USC >> CS 577Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
S USC
C E
University of Southern California
Center for Software Engineering
Software Productivity Perspectives, Paradoxes, Pitfalls, and Prospects
Barry Boehm, USC Microsoft Presentation December 6,1999
boehm@sunset.usc.edu http://sunset.usc.edu
USC
C S E
University of Southern California
Center for Software Engineering
Outline
Software Productivity Goals and Metrics Productivity Paradoxes and Pitfalls Thoughts on Microsoft Opportunities
12/6/99
USC-CSE
2
USC
C S E
University of Southern California
Center for Software Engineering
Goals and Metrics: I
Goal More rapid market penetration Larger return from limited staff Higher quality
12/6/99
Metric Effective size Development time Effective size Development effort Delivered defect weight Effective size
USC-CSE
3
USC
C S E
University of Southern California
Center for Software Engineering
Reuse at HPs Queensferry Telecommunication Division
Time to Market (months) 70 60 50 40 30 20 10 0 86 87 88 89 Year
12/6/99
Non-reuse Project Reuse project
90
91
92
USC-CSE
4
USC
C S E
University of Southern California
Center for Software Engineering
Trends in Software Expansion (Bernstein, 1997)
Projection 1000
475 638
Expansion 100 Factor The ratio of machine lines of code to a 10 source line of code
3 30 15 37.5 47
113 75 81
142
Order of Magnitude Increase Every Twenty Years
1
1960
Machine Instructions
1965
Macro Assembler
1970
High Level Language
1975
Database Manager
1980
On-line
1985
Prototyping
1990
Subsecond Time Sharing 4GL
1995
Object Oriented Programming
2000
Large Scale Reuse
Regression Testing
Small Scale Reuse
12/6/99
USC-CSE
5
USC
C S E
University of Southern California
Center for Software Engineering
NASA-SEL Development Error Rates
16 14 12 10 8 6 4 2 0 1976 Fortran Ada
Errors per KDLOC
1978
1980
1982
1984
1986
1988
1990
1992
1994
Project Midpoint
12/6/99
USC-CSE
6
USC
C S E
University of Southern California
Center for Software Engineering
Goals and Metrics: II
Goal Higher development efficiency Metric Value-adding effort Total Effort
Customer satisfaction ratings Higher customer Total Cost satisfaction efficiency Higher return on investment Life cycle benefits realized Life cycle cost
12/6/99
USC-CSE
7
USC
C S E
University of Southern California
Center for Software Engineering
Software Development Value Chain (TRW, 1986)
Infrastructure Human Resource Management Technology Development
6 1 8 1 3 7 5 1
Management QA, CM
M a r k e t i n g & S a l e s
I n b o u n d L o g i s t I c s
1 4 3 8 5 11
Rework
30
O u t b o u n d L o g i s t i c s
Service
8 8 13 7
M a r g i n
Rqts
Prelim. Design
Detailed Design
Code and Unit Test
Integration and Test
Development (80%) 12/6/99
USC-CSE
8
USC
C S E
University of Southern California
Center for Software Engineering
Productivity Improvement Opportunity Tree
More effective people Make steps more efficient Eliminate steps Improve Productivity
Incentives, Staffing, Training Facilities Management, Teambuilding Software Tools, Environments Workstations, Groupware Office Automation Automated Documentation, Quality Assurance Automated Programming Risk Management Software Architectures, Front-End Languages Knowledge-Based Software Assistance Information Hiding, Modern Programming Practices Incremental Development Rapid Prototyping Process Models Product Line Architectures, Components
Eliminate rework
Build similar products Use bigger components
12/6/99
Application Generators Fourth-Generation Languages
USC-CSE
9
USC
C S E
University of Southern California
Center for Software Engineering
Pareto Analysis of Rework Costs
100 80
% of Cost to Fix SPRs
TRW Project B (1005 SPRs)
60 40 20 0
0 10 20 30 40
TRW Project A (373 SPRs)
50
60
70
80
90
Percentage of SPR's
12/6/99
10 0
USC-CSE
10
USC
C S E
University of Southern California
Center for Software Engineering
AIS Balanced Scorecard Process- CMU/SEI - 99 - TR - 027
Balanced Scorecard (BSC) Strategic Objectives Financial Customer Employee Internal Bus. Proc. Learning & Growth Employee Job Questionnaire Position Attributes
BSC Position Objectives
Position Description Self Evaluation & Feedback
Position Accountability Measurement of Core Outcomes & Performance Drivers
Professionalism Accountability
Position Knowledge & Skills
Broadening Assignments & Activities
Individual Training Goals Improvement Goals/ Summary Rating
Individual BA&A Goals
Training Director plan Individual Career Plan
Development Staffing Plan for BA&A
12/6/99
USC-CSE
11
USC
C S E
University of Southern California
Center for Software Engineering
Metric Definition Challenges: I
Product
Program, system (X3), product (X3), system product (X9) Application, infrastructure, support software
Effective Size
Source instructions, object instructions, function points
Time, Effort
Endpoints, labor categories, work hours
Defect Weight
Problems vs. improvements, criticality ratings
12/6/99
USC-CSE
12
USC
C S E
University of Southern California
Center for Software Engineering
Definition Checklist for Source Statements Counts
Definition name: __ ________________
Measurement unit: Statement type When a line or statement contains more than one type, classify it as the type with the highest precedence. 1 Executable 2 Nonexecutable 3 Declarations 4 Compiler directives 5 Comments 6 On their own lines 7 On lines with source code 8 Banners and non-blank spacers 9 Blank (empty) comments 10 Blank lines 11 12 How produced 1 Programmed 2 Generated with source code generators 3 Converted with automated translators 4 Copied or reused without change 5 Modified 6 Removed 7 8 Origin 1 New work: no prior existence 2 Prior work: taken or adapted from 3 A previous version, build, or release Order of precedence 1 2 3 4 5 6 7 8
Logical Source ( basic definition)
Statements __________
___Date Originator:_
:________________ COCOMO II ____
Physical source lines Logical source statements Definition 4
Data Array Includes Excludes
Includes Excludes
Definition
4
Data array
Excludes
Definition
4
Data array
Includes
4 Commercial, off-the-shelf software (COTS), other than libraries 5 Government furnished software (GFS), other than reuse libraries 6 Another product 7 A vendor-supplied language support library (unmodified) 8 A vendor-supplied operating system or utility (unmodified) 9 A local or modified language support library or operating system 10 Other commercial library 11 A reuse library (software designed for reuse) 12 Other software component or library 13 14
12/6/99
USC-CSE
13
USC
C S E
University of Southern California
Center for Software Engineering
Metric Definition Challenges: II
Value Adding Effort
Problems vs. improvements Reviews, inspections, testing, CM, QA, planning & control
Customer Satisfaction
Consistent sampling; receding horizons
Life Cycle Benefits
Multivariate criteria (-ilities); synergy effects
12/6/99
USC-CSE
14
USC
C S E
University of Southern California
Center for Software Engineering
Outline
Software Productivity Goals and Metrics Productivity Paradoxes and Pitfalls Thoughts on Microsoft Opportunities
12/6/99
USC-CSE
15
USC
C S E
University of Southern California
Center for Software Engineering
Paradox 1: More Software May Not Be Better
Product TRW UNAS 0.7 Size (SLOC) 12,200 Effort (PM) 28 SLOC/PM 436
TRW UNAS 0.9
5,200
38
137
Benjamin Franklin (paraphrased): My apologies for the length of this letter. Had I more time, it would have been shorter.
12/6/99
USC-CSE
16
USC
C S E
University of Southern California
Center for Software Engineering
Productivity Paradoxes 2, 3
Paradox 2: Cheaper software may not be better
More critical defects (Ariane V, Mars Climate Orbiter) Later to market (cube-root vs. square-root law)
Paradox 3: More reuse may not be better
Reusing obsolete software Gaming the metrics: localization as reuse
12/6/99
USC-CSE
17
USC
C S E
University of Southern California
Center for Software Engineering
Traditional Minimum-Cost Schedule
Months = 3 * 27 PM
3 Person-Months
9 months, average of 3 persons
Preferable RAD approach: 5.2 months, average of 5.2 persons
Square-root law
12/6/99
USC-CSE
18
USC
C S E
University of Southern California
Center for Software Engineering
Productivity Pitfalls
What WYMIWYG: you measure is what you get Weinberg data I One approach fits all situations Weinberg data II Asking for precise data will produce precise data Not if it takes much extra effort
12/6/99
USC-CSE
19
USC
C S E
University of Southern California
Center for Software Engineering
WYMIWYG: What You Measure Is What You Get*
Team Objective: Optimize Time To Complete No. of Statements Memory Required Program Clarity Output Clarity Resulting Rank on Performance** Time To Complete No. of Statements Memory Required Program Clarity Output Clarity
1 2-3 5 4 2-3
4 1 2 3 5
** 1=Best USC-CSE
4 2 1 3 5
5 3 4 1-2 1-2
3 5 4 2 1
*Weinberg-Schulman, 1974
12/6/99
20
USC
C S E
University of Southern California
Center for Software Engineering
Effect of Objectives on Productivity
(Weinberg-Schulman, 1974)
Team Objective: Optimize Number of Statements Personhours Productivity (State/PH)
Core Memory Number of Statements Program Clarity Programming, Man-hours Output Clarity
52 33 90 126 166
74 30 40 28 30
0.7 1.1 2.2 4.5 5.5
12/6/99
USC-CSE
21
USC
C S E
University of Southern California
Center for Software Engineering
Outline
Software Productivity Goals and Metrics Productivity Paradoxes and Pitfalls Thoughts on Microsoft Opportunities
12/6/99
USC-CSE
22
USC
C S E
University of Southern California
Center for Software Engineering
Thoughts on Microsoft Opportunities
People, Workplace, and Incentives
Good base already; always worth attention
Reuse and Product Line Management (PLM)
Large potential payoff; often hard to realize Start small; look for empowered PLMs
Reducing Rework (process)
Probably best place for initiative Look for Pareto 80-20s, early defect elimination
Tools and Environments
Worth pursuing for incremental gains Explore architecture-based tools (Rational Rose, Dashboard)
Rapid Application Development
Good base already; explore RAD Opportunity Tree
Closed-loop metric/model approach
12/6/99
USC-CSE
23
USC
C S E
University of Southern California
Center for Software Engineering
Example Productivity Strategy Analysis (DoD)
40 38 36 34 32 30 28 26 24 1992
12/6/99 Work-Avoidance Savings (SW Reuse) Working-Smarter (Process) Working-Faster (Tools) DoD Software Demand (Conservative)
1994
1996
1998 USC-CSE
2000
2002
2004
24
USC
C S E
University of Southern California
Center for Software Engineering
Product Line Domain Scope a Function of ROI, Scope of Empowered PL Manager
Return on Investment (ROI)
.
Breadth of Domain Scope of empowered PLM too few instances to generate payoff too general to be competitive
12/6/99
USC-CSE
25
USC
C S E
University of Southern California
Center for Software Engineering
Nonlinear Reuse Effects
1.0
Data on 2954 NASA modules [Selby, 1988]
0.70 0.55
1.0
0.75
Relative cost 0.5
0.25 0.046 0.25
Usual Linear Assumption
0.5
0.75
1.0
Amount Modified
12/6/99
USC-CSE
26
USC
C S E
University of Southern California
Center for Software Engineering
Candidate Rework Reduction Approach
Explore general rework reduction strategies
Risk identification checklists and reviews Architecture-based analysis Inspections Model Clashes
Obtain/analyze cost-to-fix data from problem reports
Distinguish rework from new features Look for Pareto 80-20s to pursue
12/6/99
USC-CSE
27
USC
C S E
University of Southern California
Center for Software Engineering
Flattening the Cost-to-Fix Curve (CCPDS-R)
n
Architecture-first MBASE/Rational Process approach Integration during the design phase Demonstration-based evaluation
70 60 50 40
Usual Trend
Design Changes
Person Hours 30 Change 20 10 Project Development Schedule
Maintenance Changes and ECPs Implementation Changes
15
20
25
30
35
40
12/6/99
USC-CSE
28
USC
C S E
University of Southern California
Center for Software Engineering
12/6/99
29
USC
C S E
University of Southern California
Center for Software Engineering
Users
Success Model-Clash Profiles: General
PD/S
Acquirers
S/S
Many features Changeable requirements Applications compatibility & control High levels of Service PP/PD Voice in acquisition PC/PC Flexible contract PC/PC Early availability
PC/PD
PD/PP PC/PD PP/S
PD/PP PD/PD PC/PC
Mission cost/effectiveness Limited budget, Schedule Government standards compliance Political correctness Development visibility & control Rigorous contract
PC/PC
Ease of transition Ease of maintenance Applications compatibility &control Voice in acquisition
PP/PD PC/PD
PC/PC
PC: Process PD: Product
PP: Property S: Success
Flexible contract Ease of meeting budget &schedule PC/PC Stable requirements Freedom of choice: process S/PC Freedom of choice: PD/PD team Freedom of choice: COTS/reuse
Maintainers
12/6/99
Developers USC-CSE
30
USC
C S E
University of Southern California
Center for Software Engineering
RAD Opportunity Tree
Eliminating Tasks
Business process reengineering Reusing assets Applications generation Schedule as independent variable (SAIV) Tools and automation Work streamlining (80-20) Increasing parallelism Reducing failures Reducing their effects Early error elimination
Reducing Time Per Task Reducing Risks of Single-Point Failures
Reducing Backtracking
Activity Network Streamlining
Process anchor points Improving process maturity Collaboration technology Minimizing task dependencies Avoiding high fan-in, fan-out Reducing task variance Removing tasks from critical path 24x7 development Nightly builds, testing Weekend warriors
Increasing Effective Workweek Better People and Incentives Transition to Learning Organization 12/6/99
USC-CSE
31
USC
C S E
University of Southern California
Center for Software Engineering
Closed Loop Metric/Model Approach: COCOMO II Example
Improved Corporate Parameters
Cost, Schedule, Quality drivers
Evaluate Corporate SW Improvement Strategies 12/6/99
USC-CSE
32
USC
C S E
University of Southern California
Center for Software Engineering
COCOMO II. 2000 Productivity Ranges
Productivity Range Development Flexibility (FLEX) Team Cohesion (TEAM) Develop for Reuse (RUSE) Precedentedness (PREC) Architecture and Risk Resolution (RESL) Platform Experience (PEXP) Data Base Size (DATA) Required Development Schedule (SCED) Language and Tools Experience (LTEX) Process Maturity (PMAT) Storage Constraint (STOR) Use of Software Tools (TOOL) Platform Volatility (PVOL) Applications Experience (AEXP) Multi-Site Development (SITE) Documentation Match to Life Cycle Needs (DOCU) Required Software Reliability (RELY) Personnel Continuity (PCON) Time Constraint (TIME) Programmer Capability (PCAP) Analyst Capability (ACAP) Product Complexity (CPLX) 1 1.2 1.4 1.6 1.8 2 2.2 2.4
12/6/99
USC-CSE
33
USC
C S E
University of Southern California
Center for Software Engineering
COCOMO II.2000 Productivity Ranges and Current Practice
2
CP LX AC AP PC AP TIM E PC ON RE LY SIT E DO CU AE XP TO OL PV OL ST OR PM AT SC ED LTE X DA TA PE XP RE SL PR EC RU SE TE AM FLE X
0.5
1
1.5
Average Multiplier for 1990s projects
12/6/99
USC-CSE
34
USC
C S E
University of Southern California
Center for Software Engineering
Relevant USC-CSE Materials Available
COCOMO Suite Web Page, http://sunset.usc.edu/COCOMOII/suite.html For Affiliates-only material, click on the horn, type Username: Millard Password: Fillmore Advanced text of COCOMO II book, USC COCOMO II. 2000 tool, experimental extensions such as Constructive Productivity Model (COPROMO) Project course Web Page (MBASE in action) http://sunset.usc.edu/classes/cs577a_99/ Other Web Page assets: electronic papers, tools, events, etc., http://sunset.usc.edu Other technical reports, including productivity analyses
12/6/99
USC-CSE
35
USC
C S E
University of Southern California
Center for Software Engineering
Thoughts on Microsoft Opportunities
People, Workplace, and Incentives
Good base already; always worth attention
Reuse and Product Line Management (PLM)
Large potential payoff; often hard to realize Start small; look for empowered PLMs
Reducing Rework (process)
Probably best place for initiative Look for Pareto 80-20s, early defect elimination
Tools and Environments
Worth pursuing for incremental gains Explore architecture-based tools (Rational Rose, Dashboard)
Rapid Application Development
Good base already; explore RAD Opportunity Tree
Closed-loop metric/model approach
12/6/99
USC-CSE
36
Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more.
Course Hero has millions of course specific materials providing students with the best way to expand
their education.
Below is a small sample set of documents:
Below is a small sample set of documents:
USC - CS - 577
1Guidelines for the Life Cycle Objectives (LCO) and the Life Cycle Architecture (LCA) deliverables for Model-Based (System) Architecting and Software Engineering (MBASE)Inception and ElaborationOperational Concept Description (OCD) System and Sof
USC - CS - 577
COCOMO II/Chapter 5/Boehm et al.-1-EXTRACTED COQUALMO SECTION WITH TABLES & FIGURES CHAPTER 5 EMERGING EXTENSIONS5.5 COQUALMOThis section describes the expert-determined Defect Introduction and Defect Removal sub-models that compose the quali
USC - CS - 577
Preparing Inception/Elaboration (LCA) packages for ConstructionGeneral Guidelines Broken down by categories Process Guidelines Tool Guidelines Formatting Guidelines . Refined Completion Criteria Overall Completion Criteria Completion Crite
USC - CS - 577
Date 1/28/00Author Dan PortVersion 1.1.003/01/00 03/04/00Ebru Dincel Dan Port1.1.1 1.1.2Changes made Elaborated and expanded most sections, corrections in numbering schemes and format Re-organized Construction sections Improved consist
USC - AME - 514
Progress in Energy and Combustion Science 28 (2002) 435475 www.elsevier.com/locate/pecsEdge-amesJ. Buckmaster*Department of Aeronautical and Astronautical Engineering, University of Illinois at Urbana-Champaign, 104 S. Wright Street, Urbana, IL 6
USC - AME - 514
Twenty-Seventh Symposium (International) on Combustion/The Combustion Institute, 1998/pp. 28152820FINGERING INSTABILITY IN SOLID FUEL COMBUSTION: THE CHARACTERISTIC SCALES OF THE DEVELOPED STATEORY ZIK and ELISHA MOSES Department of Physics of Com
USC - CSCI - 577
Life Cycle Plan (LCP)Version no 1.5Life Cycle Plan (LCP)USC CONIPMOTEAM No. 16Kumar Yalla Project Manager & Software Architect Gaurav Batra OCD Jenish Jariwala Prototyper Shivam Gupta Requirement Analyst Rashmi Shukla FRD Vinita Goyal L
USC - CSCI - 577
Feasibility Rationale Description (FRD)USC CONIPMOTeam No 16Kumar Yalla Project Manager & Software Architect Gaurav Batra OCD Jenish Jariwala Prototyper Shivam Gupta Requirement Analyst Rashmi Shukla FRD Vinita Goyal Life Cycle Planner Dav
USC - CSCI - 577
Team 16April 15th, 2008CSCI 577bSoftware Engineering II University of Southern CaliforniaProject 16 E-MentoringTeam Assignment Client Meeting Report# 10April 15th, 2008Submitted By: Team 161Team 16April 15th, 2008Project Name: E-M
USC - CSCI - 577
Project Indicators as of xx/yy/zzzzCumulative Project Effort500 400 300 200 100 0 WeekMan-hoursPlanned ActualProject ProgressCumulative no. of tasks 14 12 10 8 6 4 2 0 Week no.Late On Sched Completed PlannedWeekxx_PR_S02b_Txx.xls
USC - CSCI - 577
Team Number: Week: Program Size (SLOC) Base4 9COINCOMO 2.0Total New SLOCActual 2710 Added 50 Deleted Modified Reused # of COTS 2760 Planned 100update from CodeCountEffort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycl
USC - CSCI - 577
Plan SummaryTeam Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Ta
USC - CSCI - 577
USC CSCI577b Spring 2008 COINCOMO 2.0Team RolesName Amit Mange Hemali Shaw Ramin Moazeni Alexander Sharma Tom Ackenhausen Mithun Mohan Lakshmi Kodali Ian Serlin Email mange @ usc.edu hemalish @ usc.edu Moazeni @ usc.edu Alexander.sharma @ gmail.co
USC - CSCI - 577
Plan SummaryTeam Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Ta
USC - CSCI - 577
Team 16February 8th, 2008CSCI 577bSoftware Engineering II University of Southern CaliforniaProject 16 E-MentoringTeam Assignment Client Meeting Report# 2February 8th, 2008Submitted By: Team 161Team 16February 8th, 2008Project Name
USC - CSCI - 577
Team Number: Week: Program Size (SLOC) Base4 3COINCOMO 2.0Total New SLOCActual 6500 Added 200 Deleted Modified Reused # of COTS 200 Planned 100 Actual not I do not have the breakdown of hours into c 140.5Effort (Hours) Project Mgmt. Require
USC - CSCI - 577
Client Meeting Notes: 03-05-2008 We had an hour long meeting with our clients. Attendees: a) Jacqualine Zarate b) Mitch Arenas c) IT Department representative d) Yuwei Jiang e) Mithila Rao Velishala Meeting notes: a) The Core Capability Drivethrough
USC - CSCI - 577
Team 16January 30th, 2008CSCI 577bSoftware Engineering II University of Southern CaliforniaProject 16 E-MentoringTeam Assignment Client Meeting Report# 1January 30th, 2008Submitted By: Team 161Team 16January 30th, 2008Project Name
USC - CSCI - 577
Team 16April 9th, 2008CSCI 577bSoftware Engineering II University of Southern CaliforniaProject 16 E-MentoringTeam Assignment Client Meeting Report# 9April 9th, 2008Submitted By: Team 161Team 16April 9th, 2008Project Name: E-Mento
USC - CSCI - 577
ID 1% Complete Task Name 97% CSCI 577b Team 11 ProjectMilestone NoDuration 65 days?Start Mon 1/28/08Finish Fri 4/25/08PredecessorsResource NamesJan 27, '08 Feb 3, '08 Feb 10, '08 Feb 17, '08 Feb 24, '08 Mar 2, '08 Mar 9, '08 Mar 16, '
USC - CSCI - 577
Team Number: Week: Program Size (SLOC) Base4 6COINCOMO 2.0Total New SLOCActual 3382 Added 200 Deleted Modified Reused # of COTS 3582 Planned 100 Actual 52.5Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning
USC - CSCI - 577
ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 24 26% Complete Task Name 60% CSCI 577b Team 11 Project 65% 85% 85% 100% 80% 100% 100% 57% 100% 100% 100% 100% 50% 50% 50% 50% 50% 50% 50% Week 2 Client meeting 1 Client meeting 1 notes Te
USC - CSCI - 577
Team 16April 23rd, 2008CSCI 577bSoftware Engineering II University of Southern CaliforniaProject 16 E-MentoringTeam Assignment Client Meeting Report# 9April 23rd, 2008Submitted By: Team 161Team 16April 23rd, 2008Project Name: E-Me
USC - CSCI - 577
ID 1% Complete Task Name 97% CSCI 577b Team 11 ProjectMilestone NoDuration 60 days?Start Mon 1/28/08Finish Fri 4/18/08PredecessorsResource NamesJan 27, '08 Feb 3, '08 Feb 10, '08 Feb 17, '08 Feb 24, '08 Mar 2, '08 Mar 9, '08 Mar 16, '
USC - CSCI - 577
Team Number: Week: Program Size (SLOC) Base4 4COINCOMO 2.0Total New SLOCActual 2982 Added 100 Deleted Modified Reused # of COTS 3082 Planned 100 Actual not I do not have the breakdown of hours into c 133.9Effort (Hours) Project Mgmt. Requir
USC - CSCI - 577
Client Meeting NotesDate:September 28, 2007 Venue: Los Angeles Personnel Department Office, LAKey Issues related to the meeting: New Project Identifying the requirements Identifying Stake holders. Over all Modules for the systemIn Attendanc
USC - CSCI - 577
CLIENT MEETING NOTES Proctor and Test Site Tracking SystemDate: February 14, 2008 Time: 9:30-11:00 am In Attendance: Person Name Professor Barry W. Boehm Professor Winsor A. Brown Mr. Pongtip Aroonvatanaporn Mr. Frank Lim Ms. Kyren Harvey Mr. Mingoo
USC - CSCI - 577
Test Procedures and Results (TPR)Proctor and Test Site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojinki@usc.edu) Maged Boctor IV&V (mbocto
USC - CSCI - 577
Quality Management PlanVersion no 3.2Quality Management Plan (QMP)Proctor and Test site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojink
USC - CSCI - 577
Supporting Information Document (SID)Version 3.6SUPPORTING INFORMATION DOCUMENT (SID) Proctor and Test Site Tracking System Team 15 Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae Operational Conce
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Version 3.8System and Software Requirements Definition (SSRD) Proctor and Test Site Tracking SystemTeam # 15Name Mingoo Kim Heeseo Chae Soojin Kim Maged BoctorRole Project Manager (mingoo
USC - CSCI - 577
System and Software Support Plan (SSSP)Proctors and Test sites Tracking SystemTeam 154/12/2008SP_TRR_S08b_T15_V1.0.docVersion Date: 4/10/2008Support PlanVersion no 1.0Version HistoryDate 04/09/08 Author Soojin Kim Version 1.0 Changes
USC - CSCI - 577
Feasibility Rationale Description (FRD)Proctor and Test site Tracking SystemTeam 15NameRoleMingoo Kim Heeseo Chae Soojin Kim Maged Boctor Hsiu-hui HsuProject Manager (mingoo.kim@usc.edu) OCD & Developer (hchae@usc.edu) Architect & Developer
USC - CSCI - 577
Proctor and Test Site Tracking SystemTraining Materials (TM)Team 15Name Mingoo Kim Heeseo Chae Soojin Kim Hsiu-hui Hsu Maged BoctorRole Project Manager (mingoo.kim@usc.edu) Operational Concept Engineer (hchae@usc.edu) Prototype Manager (sooji
USC - CSCI - 577
Quality Management PlanVersion no 3.1Quality Management Plan (QMP)Proctor and Test site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojink
USC - CSCI - 577
System and Software Architecture Description (SSAD)Proctor and Test Site Tracking SystemTeam 15Name Mingoo Kim Heeseo Chae Soojin Kim Maged Boctor Hsiu-hui HsuRole Project Manager (mingoo.kim@usc.edu) OCD & Developer (hchae@usc.edu) Architect
USC - CSCI - 577
Transition Plan (TP)Proctor and Test Site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojinki@usc.edu) Maged Boctor IV&V (mboctor@usc.edu) Hs
USC - CSCI - 577
Operational Concept Description (OCD)Proctor and Test Site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae Operational Concept Engineer (hchae@usc.edu) Soojin Kim Prototype Manager (soojinki@usc.edu)
USC - CSCI - 577
Transition Plan (TP)Proctor and Test Site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojinki@usc.edu) Maged Boctor IV&V (mboctor@usc.edu) Hs
USC - CSCI - 577
Supporting Information Document (SID)Version 4.0SUPPORTING INFORMATION DOCUMENT (SID) Proctor and Test Site Tracking System Team 15 Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae Operational Conce
USC - CSCI - 577
Feasibility Rationale Description (FRD)Proctor and Test site Tracking SystemTeam 15NameRoleMingoo Kim Heeseo Chae Soojin Kim Maged Boctor Hsiu-hui HsuProject Manager (mingoo.kim@usc.edu) OCD & Developer (hchae@usc.edu) Architect & Developer
USC - CSCI - 577
System and Software Architecture Description (SSAD)Proctor and Test Site Tracking SystemTeam 15Name Mingoo Kim Heeseo Chae Soojin Kim Maged Boctor Hsiu-hui HsuRole Project Manager (mingoo.kim@usc.edu) OCD & Developer (hchae@usc.edu) Architect
USC - CSCI - 577
Software Users ManualVersion no 3.0Software Users ManualProctor and Test site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojinki@usc.edu)
USC - CSCI - 577
Quality Management PlanVersion no 2.0Quality Management Plan (QMP)Proctor and Test site Tracking SystemTeam 15Name Role Mingoo Kim Project Manager (mingoo.kim@usc.edu) Heeseo Chae OCD & Developer (hchae@usc.edu) Soojin Kim Developer (soojink
USC - CSCI - 577
E-Mentoring SystemTeam #1602/15/2008AgendaIntroduction Test/ Peer Review Plan OCD & Prototype & SSRD System Architecture Life Cycle Plan Feasibility Rationale Quality Management Iteration Plan Things Done Right!IntroductionProject name: E-M
USC - CSCI - 577
System and Software Architecture Description (SSAD)Web-Based XML Editing ToolTeam #13 Member Aoun, Adrian Panigrahi, Siddharth Su, Charles Dawei, Jia Lo, John Bhushan, Sudhanshu Michael Bailey Tanvi Khare Role System Architect Team Manager Operati
USC - CSCI - 577
Steps for Core Capabilities Drive ThroughTeam 10: Code Generator-Template Based April 6th, 2006 This document illustrates steps in checking core capabilities of the developed application. There are 7 scenarios as follows: scenario 1. Install and Run
USC - CSCI - 577
ClIENT MEETING NOTE: DATE: AUTHOR: ATTENDANCE:Discuss the file format, the convert process, and the prototype outlook 11/13/2005 LVL 3M PLACE: Hung-Fu Chang REVIEW: Aditya Mandarilli; Hung-Fu Chang (Aaron); Kai-Chen Huang (Angelo); Chi-Hsien Chiu (
USC - CSCI - 577
Sanjay Nair sanjaysn@usc.edu CSCI 5771, Fall 2005 IV&V HW #3 Evaluation of Quality Report (LCO Draft) 21 Oct 20051. OCD Quality review 1.1. Tab 1 (Areas of Concern Log)1. No individual quality report has been submitted. No way to figure out who i
USC - CSCI - 577
Client's Meeting Note February 22, 2006 Leavy Libaray, Room 3V Attendee Aditya Manadavilli Hung-Fu Chang Hsiao-Han Huang Supannika Koolmanojwong Chi-Hsien Chiu Woen-Kee Sohn Jiajing Liu 1. Client Project Manager & Life Cycle Planner Operation Concept
USC - CSCI - 577
Iteration Assessment Report (IAR)Code Generator Template basedTeam 10Hung-Fu Chang Hsiao-Han Huang Supannika Koolmanojwong Jiajing Liu Chi-Hsien Chiu Woen-kee Sohn Sonal Mane Armen Donigian Ravin SoniProject Manager Operational Concept Descr
USC - CSCI - 577
Date: Thursday, 17th Nov, 2005 Time: 4.00pm 4.30pm Place: USC Football Office, Heritage Hall, USC The Client: *Jared Blank USC Football The Team: Revati Kadu (Project Manager) *Akshay Aras (Project Coordinator) Abhishek Venkatesh Vivek Ganapathy Na
USC - CSCI - 577
Sanjay Nair sanjaysn@usc.edu CSCI 5771, Fall 2005 IV&V Evaluation of Quality Report (LCA Draft) 28 Nov 20051. Tab 1 (Areas of Concern Log) 1.1. General concerns1. Template used for filling in the Quality report is incorrect. Download it from the
USC - CSCI - 577
CSCI 577BTeam 23Product Delivery & Client Acceptance1) These are the documents with the version to be released to the client during the delivery: Document Operational Concept Description (OCD) System and Software Requirements Definition (SSRD) S
USC - CSCI - 577
User ManualVersion 1.2User ManualWeb Based XML editorTeam 13Member John Lo Nagesh Arkalgud Sudhanshu Bhushan Jia Dawei Arpitha Hegde Quan Pham Tanvi Khare Role Project Manager/Iteration Planner/Operational Concept Designer/Developer System Ar
USC - CSCI - 577
Life Cycle Plan (LCP)Version 1.5USC Football Recruitment Database(Team 6) ClientJared Blank USC FootballFeasibility Rationale Systems Architecture & Modeling System Operational Concept System Analysis and Prototypes UML Modeling Life cycle P
USC - CSCI - 577
Training Material(TM)HOpen Source XML Parser-Based Code Count ToolTeam 23Ali Afzal Malik Harsh Nayak Kunal Kulkarni Vannak Touch Naman Modi Matthew Benjamin Leonard Cayetano Elaine HuangProject Manager and Configuration Manager Tester and W
USC - CSCI - 577
System and Software Requirements Definition (SSRD)Version 2.0USC Football Recruiting Database(Team No 6)ClientJared Blank USC FootballThe TeamFeasibility Rationale Systems Architecture & Modeling Operational Concept and system analysis Sys
USC - CSCI - 577
Operational Concept Description (OCD)Open Source XML Parser based code count toolTeam 23Ali Afzal Malik Harsh Nayak Kunal Kulkarni Vannak Touch Naman Modi Matthew Benjamin Leonard Cayetano Elaine HuangProject Manager Developer/Tester System Ar
USC - CSCI - 577
Operational Concept Description (OCD)Code Generator Template based Team #10Aditya Mandavilli Hung-Fu Chang Jui-Yu TsaiPei-Hua Lu Jiajing Liu Chi-Hsien Chiu Kai-Chen Hung Keyur Vekaria Sanjay NairClient Manager Operational Concept Description
USC - CSCI - 577
System and Software Architecture Description (SSAD)Code Generator Template based Team #10Hung-Fu Chang Hsiao-Han Huang Supannika Koolmanojwong Jiajing Liu Chi-Hsien Chiu Woen-Kee Sohn Sonal Mane Armen DonigianProject Manager & Life Cycle Plann