April 13, 2004CS 562 - WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 –...
-
date post
21-Dec-2015 -
Category
Documents
-
view
217 -
download
2
Transcript of April 13, 2004CS 562 - WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 –...
April 13, 2004 CS 562 - WPI 1
CS 562Advanced SW Engineering
General Dynamics, NeedhamTuesdays, 3 – 7 pm
Instructor: Diane Kramer
April 13, 2004 CS 562 - WPI 2
Class Format for TodayReview General Course Info & SyllabusReview Assignments
Reading materialHomework handoutProject Discussion
Lecture #1: Intro to Software Cost EstimationExploring COCOMO II
April 13, 2004 CS 562 - WPI 3
General Course Info
Course Web Site:http://www.cs.wpi.edu/~cs562/e04
Lecture slides, handouts, announcements, etc.
Prerequisites, grading, assignmentsAcademic Integrity:
Cheating = not acknowledging the contributions of others
April 13, 2004 CS 562 - WPI 4
Goals for this CourseMain focus on SW cost estimationAlso look at project management from a number of different perspectivesReading list:
Boehm, et alYourdonBrooksOther – additional suggested reading material
April 13, 2004 CS 562 - WPI 5
Syllabus
Reading assignments:Read in advance for class assignedCome prepared to discuss
In class activities:Discussions on reading assignmentsOther exercises/activities
Everyone is expected to participate
April 13, 2004 CS 562 - WPI 6
Writing Assignments
Homework Handout4 essays on reading material3 have topics already assignedThe 4th is up to you
Submit proposal by week 5Include source material & topicSee course web site for suggested readings
April 13, 2004 CS 562 - WPI 7
Term ProjectInvent a SW project to plan/estimateFind something going on in your company (current or past), perhaps in a different dept
Try not to get any real costs (estimated or actual)These will bias your work
Submit proposal in 2 weeksMore info coming
April 13, 2004 CS 562 - WPI 8
Introduction toSoftware Cost Estimation
Boehm, et alChapter 1
April 13, 2004 CS 562 - WPI 9
Why Cost Estimations?Why do we need to plan out SW projects?
What can go wrong without a plan?
What data need to be considered?What goes into a project plan?What goes into a cost estimate?What happens when our estimates are wrong?
Have any of you done this before?What were your experiences?
April 13, 2004 CS 562 - WPI 10
COCOMO II Software
Use to help make software cost estimatesUser objectives
Review list on pages 1 – 2
Model objectivesReview list on pages 3 – 4
Evolution strategiesReview list on pages 4 – 5
April 13, 2004 CS 562 - WPI 11
Projected Future SW Practice
SW Development Roles: (Figure 1.1, page 6)
End user programmingInfrastructureIntermediate Sectors
Application GeneratorsApplication CompositionSystem Integration
How are each of these defined?Why do we care?
April 13, 2004 CS 562 - WPI 12
Cost DriversLife Cycle ModelsReusability, COTSDegree of understanding of:
Requirements, Architecture, Market window, Scheduling constraints, Required reliability, etc.
Granularity of available informationSee figure 1.2, page 10Point estimates vs. range estimates
April 13, 2004 CS 562 - WPI 13
Process Models
Early prototypingResolve high-risk issues, such as?
Early designExplore alternative software/system architectures
Post architectureActual development and maintenance
April 13, 2004 CS 562 - WPI 14
COCOMO II Software Reference
Manual
Boehm, et alAppendix E, page 391
April 13, 2004 CS 562 - WPI 15
IntroductionWhat does COCOMO stand for?Used by project managers or team leadersUsed to develop model(s) of projects to identify potential problems in:
Resources, personnel, budgets, schedules
Primary objectives:Review list on page 391
April 13, 2004 CS 562 - WPI 16
Estimation Equations
Effort estimation1.1.1, page 392
Schedule estimation1.1.2, page 393
Scale factors1.1.3, page 393Also see table 1.1, page 394
April 13, 2004 CS 562 - WPI 17
Sizing MethodsLines of Code (LOC)
Why is this difficult to measure?See SEI definition checklist, page 395
Guidelines for what to include/exclude
Function Points (FP)Identify user function types (Table 1-2, page 396)Classify by complexity levelDegree of influence
April 13, 2004 CS 562 - WPI 18
Adapting Existing Code
COCOMO supports cost estimations for modifications to existing codeReview list on page 397Also see Figure 1-6, page 403
April 13, 2004 CS 562 - WPI 19
Effort MultipliersLists on pages 397 – 398
Product attributes: constraints, requirementsPlatform attributes: hardware/OS limitationsPersonnel attributes: level of various skillsProject attributes: development conditions
16 factors with up to 6 ratings< 1 reduces effort, > 1 increases effortSee Figure 1-2, page 398
April 13, 2004 CS 562 - WPI 20
COCOMO User InterfaceCLEF: see Figure 1-3, page 399
UI descriptions, pages 399 – 406
Remaining contents of Appendix EChapter 2: File Menu (pages 407 – 425)Chapter 3: Edit Menu (pages 425 – 428)Chapter 4: Parameters Menu (pages 429 – 435)Chapter 5: Calibrate Menu (pages 435 – 439)Chapter 6: Phase Distribution (pages 439 – 456)Chapter 7: Maintenance (pages 457 – 466)
April 13, 2004 CS 562 - WPI 21
Accompanying CD-ROM
Boehm, et alAppendix F, page 472
April 13, 2004 CS 562 - WPI 22
Review Contents of CD
Greeting and book overview by BoehmCOCOMO II InstallationTutorials
My 1st COCOMO RunCan run off CD without full installation
Commercial COCOMO II – based tools
April 13, 2004 CS 562 - WPI 23
For Next Time
Review Chapter 1 of BoehmRead Yourdon – Death MarchWrite Paper 1Research & think about term project