{"text_format":"3","workbook":"xls","n_sheets":3,"sheets":["assumptions","baselines","plus 10 years"],"not_rendered":{"external_links":1},"read":"whole","date_system":"1904","formulas":"cached_only"}

{"sheet":"assumptions","index":0,"n_rows":4,"n_cols":1,"rows_kept":4,"flags":["formulas_cached_only"]}
["nasa-like application"]
["mission or safety critical real-time system"]
["typically, built by contractors (not built in-house)"]
["long life time (5 to 10 years)"]

{"sheet":"baselines","index":1,"n_rows":26,"n_cols":4,"rows_kept":26,"flags":["formulas_cached_only"]}
[{"$nulls":3},"now"]
["aa","automated analysis","this one refers to investment in automated analysis tools. Just to clarify, greater investment means that you \"detect and remove\" more defects rather than \"gets you more\" defects ",3]
["acap","analyst capability"," ",3]
["apex","analyst experience"," ",4.5]
["cplx","product complexity"," ",3]
["data","database size per LOC"," ",4]
["docu","required levels of documentation"," ",3]
["ett","execution-based testing and tools","not a cocomo factor but a factor in the coqualmo defect removal model.",2]
["flex","development ﬂexibility ","development ﬂexibility .  \"lo\" means development process rigorously. \"hi\" means only general goals defined ",3]
["ltex","language and tool experience","more experience = less development cost",4.5]
["pcap","programmer capability"," ",3]
["pcon","personnel continuity (% turnover per year)"," ",3]
["peer","peer reviews","not a cocomo factor but a factor in the coqualmo defect removal model.",2.5]
["plex","platform experience"," ",4.5]
["pmat","process maturity"," ",2.5]
["prec","precendentness","have we built this kind of thing before? (higher values means less familiarity)",4.5]
["pvol","platform volatility"," ",2]
["rely","required reliability"," ",2.5]
["resl","architectural or risk analysis"," ",3]
["ruse","reuse","is this product being developed with the intent that it is a reusable component?",4]
["sced","dictated development schedule","lower values means developers forced to deliver faster than they would like",3]
["site","multi-site development","\"lo\" means some contact: phone, mail; \"hi\" means multi-media ",4.5]
["stor","required % of available RAM"," ",3]
["team","team cohesion","lower values means more difficult interactions (e.g. sub-contractors working behind separate firewalls)",3.5]
["time","% of CPU"," ",3]
["tool","use of software tools","\"lo\" means just simple edit/debug cycles; \"hi\" means tools tightly integrated to the development cycle",3]

{"sheet":"plus 10 years","index":2,"n_rows":26,"n_cols":17,"rows_kept":26,"flags":["formulas_cached_only"]}
[{"$nulls":3},"bumps","up","down","flat","rick","abstain","majority trend",null,"max","notes","questions","delta"]
["aa","automated analysis","this one refers to investment in automated analysis tools. Just to clarify, greater investment means that you \"detect and remove\" more defects rather than \"gets you more\" defects ",null,5,null,3,null,null,"up","Divided into subsystems. Mission-critical: Up(5), else: level (3).",5,{"$nulls":4},"up"]
["acap","analyst capability"," ",null,5,null,3,null,null,"up","ACAP – analyst capability, problem of people leaving companies early, everyone on Apollo retired. Though, that may relate more to APEX. In some ways, people’s capabilities are improving – people learning things in high school now. Argument that capability goes up, experience goes down. Vote: up(5), flat(3)",5,{"$nulls":4},"down"]
["apex","analyst experience"," ",null,null,7,1,null,null,"down","APEX – applications experience. Development platforms and missions continue to change.  Systems continue to get more complex .  This cannot help but go down over time as NASA engages in new unprecedented missions.   Vote: down(7), flat (1)",7]
["cplx","product complexity"," ",null,7,{"$nulls":4},"up","CPLX – just about any kind of complexity. Advocates for up. Voted: Up (7), flat(1)",7]
["data","database size per LOC"," ",{"$nulls":3},4,3,1,"anywhere","DATA –  is ratio of num items in database to loc. Do we need to change scale over time? “growth and data volume matched by technology improvements.” Advocacy for flat and bimodal. Voted: flat (4), rick (3), abstain(1)",4]
["docu","required levels of documentation"," ",{"$nulls":3},6,null,2,"flat","DOCU – documentation you are required to produce relative to what’s needed. Voted: flat (6), abstain(2)",6]
["ett","execution-based testing and tools","not a cocomo factor but a factor in the coqualmo defect removal model.",null,4,1,3,null,null,"anywhere","Some argument that as CPUs get cheaper, we will see more use of CPU-intensive simulation-based methods.     Voted: Up(4), down(1), flat(3)",4]
["flex","development ﬂexibility ","development ﬂexibility .  \"lo\" means development process rigorously. \"hi\" means only general goals defined ",null,8,{"$nulls":4},"up","FLEX – things less flexible than they were (thanks gvmt!), pushed to a 3, Tom – flexibility will decrease. Voted: up (8)",8," ","what is gvmt?"]
["ltex","language and tool experience","more experience = less development cost",null,null,3,5,null,null,"flat","LTEX – language/tool experience. Vote: down (3), flat (5)",5]
["pcap","programmer capability"," ",null,1,null,7,null,null,"flat","PCAP – programmer capability, vote: flat (7), up (1)",7]
["pcon","personnel continuity (% turnover per year)"," ",null,null,6,2,null,null,"down","PCON – personnel continuity, turnover. Vote: down (6), flat (2)",6]
["peer","peer reviews","not a cocomo factor but a factor in the coqualmo defect removal model.",null,7,null,1,null,null,"up","REVW – Code review. Another way to remove defects. If more people are using them, trend is up. Voted: Up(7), flat(1)",7]
["plex","platform experience"," ",null,null,2,6,null,null,"flat","PLEX – platform experience. Vote: flat(6), down(2)",6]
["pmat","process maturity"," ",null,7,null,1,null,null,"up","PMAT – upsies (7), flat(1)",7]
["prec","precendentness","have we built this kind of thing before? (higher values means less familiarity)",4,1,2,1,null,null,"up/down","PREC – going to remain fairly stable, might go up in long run. increasing level of uniqueness for some systems,  increasing levels of repeated simple components for others. Is there going to be a software crises? Maybe next 20, probably not next 10. Most don’t believe we will build extremely unprecedented software, Tom disagrees. Another theory- all are 6s or 2s. Voted: bumbs (4), up (1), down(2), level(1). ",4]
["pvol","platform volatility"," ",null,8,{"$nulls":4},"up","PVOL – platform volatility. Higher volatility (more changes) = up. More and more custom hardware, custom sensors, etc .Vote: Up(8)",8]
["rely","required reliability"," ",null,8,{"$nulls":4},"up","RELY – downsie = less concerned with reliability, argument for flat (we’ve launched all sorts of space missions, we’ll continue to do same thing), argument for up (demands go up for more reliable systems),. Bojan – things will be flat. Is rely effort into chasing reliability? RELY is actual system reliability. Voted: Up (8)",8]
["resl","architectural or risk analysis"," ",null,7,{"$nulls":3},1,"up","RESL - upsies (7), abstain (1)",7]
["ruse","reuse","is this product being developed with the intent that it is a reusable component?",1,2,2,2,null,1,"anywhere","RUSE – I’m investing money to make things reusable. Flat limited to unprecedented-ness, up based on pressure to build for reuse. Cost of building for reuse. Barry presses for bumpsies. Some projects are so unique that no once can reuse them. I have no idea what’s going on here. If desire to do it is high, cost will be high. Definition – putting effort into reuse. Voted: bump(1), abstain(1), down (2), up(2), flat (2)",2,"hard to define"]
["sced","dictated development schedule","lower values means developers forced to deliver faster than they would like",null,null,7,1,null,null,"down","SCED – schedule pressure, low=fast. Vote: down (7), flat(1)",7]
["site","multi-site development","\"lo\" means some contact: phone, mail; \"hi\" means multi-media ",null,null,7,1,null,null,"down","SITE – how spread out people are. Physical location % communication. More people working at home. Vote: down(7), flat(1)",7]
["stor","required % of available RAM"," ",7,{"$nulls":4},1,"up/down","STOR – see above, Voted: bumps (7), abstain(1)",7]
["team","team cohesion","lower values means more difficult interactions (e.g. sub-contractors working behind separate firewalls)",{"$nulls":3},8,null,null,"flat","TEAM – level (8)",8]
["time","% of CPU"," ",6,1,null,1,null,null,"up/down","TIME – has been going down, used to be constrained all the time. Resources fixed once something is launched. Voted: bumpsies (6), up(1), flat(1)",6]
["tool","use of software tools","\"lo\" means just simple edit/debug cycles; \"hi\" means tools tightly integrated to the development cycle",null,6,null,2,null,null,"up","TOOL – how good are tools? Ability to improve productivity. More use of tools like stateflow and auto code generation. up(6), flat (2)",6]