- Page 1 and 2: A Technical History of the SEI Larr
- Page 3 and 4: Table of Contents Foreword Preface
- Page 5 and 6: The Consequence: Undergraduate Soft
- Page 7 and 8: References 131 Expanding the CMMI P
- Page 9 and 10: The Challenge: Configuration Suppor
- Page 11 and 12: References 275 Operational Support
- Page 13 and 14: Foreword Angel Jordan University Pr
- Page 15 and 16: to the SEI on a part-time basis as
- Page 17 and 18: Blaise Durante Deputy Assistant Sec
- Page 19 and 20: synergy between the TRA team’s ob
- Page 21 and 22: Preface This report chronicles the
- Page 23 and 24: Abstract This report chronicles the
- Page 25 and 26: 1 Introduction CMU/SEI-2016-SR-027
- Page 27 and 28: Introduction In December 1984, the
- Page 29 and 30: promulgate use of modern techniques
- Page 31 and 32: Interpreting the Charter In creatin
- Page 33 and 34: of Defense and flag officers from t
- Page 35 and 36: (CRADA) funding is available to exp
- Page 37 and 38: Another effective mechanism has bee
- Page 39 and 40: 2 Real-Time Embedded Systems Engine
- Page 41: Figure 3: Real-Time Embedded System
- Page 45 and 46: development language nevertheless n
- Page 47 and 48: tin’s simulator. Although this pr
- Page 49 and 50: Technology Center, called MetaH, sp
- Page 51 and 52: [Hefley1992] Hefley, William; Forem
- Page 53 and 54: Running the initial benchmark suite
- Page 55 and 56: [Meyers 1988] Weiderman, Nelson & M
- Page 57 and 58: could be used successfully in the a
- Page 59 and 60: In the handbook, significant emphas
- Page 61 and 62: Rate Monotonic Analysis The Challen
- Page 63 and 64: The SEI Contribution The SEI was in
- Page 65 and 66: Simplex Architecture The Challenge:
- Page 67 and 68: to integrate Simplex architecture w
- Page 69 and 70: The Consequence: Successful Demonst
- Page 71 and 72: Real-Time Multicore Scheduling The
- Page 73 and 74: The SEI work has triggered the inte
- Page 75 and 76: Integrated Methods for Predictive A
- Page 77 and 78: The benefits of the IMPACT methodol
- Page 79 and 80: Architecting Software-Reliant, Safe
- Page 81 and 82: The SEI Contribution As technical l
- Page 83 and 84: CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 86 and 87: Introduction to Education and Train
- Page 88 and 89: to the colleges’ broader student
- Page 90 and 91: Mellon’s faculty in areas such as
- Page 92 and 93:
Model Curriculum for Master of Soft
- Page 94 and 95:
[Ardis 1989] Ardis, M. & Ford, G.
- Page 96 and 97:
did not list software engineering a
- Page 98 and 99:
[Ford 1994] Ford, G. A Progress Rep
- Page 100 and 101:
The curriculum work was extended to
- Page 102 and 103:
[Mead 2010d] Mead, Nancy; Hilburn,
- Page 104 and 105:
CERT website. 11 Free downloadable
- Page 106 and 107:
Conference on Software Engineering
- Page 108 and 109:
ased conference sponsored by IEEE a
- Page 110 and 111:
The design studio was also implemen
- Page 112 and 113:
The Consequence: Improved Managemen
- Page 114 and 115:
ooks in the SEI Addison-Wesley Seri
- Page 116 and 117:
courses use video, animation, graph
- Page 118 and 119:
Technology for Cyber Workforce Deve
- Page 120 and 121:
training and job duties without one
- Page 122 and 123:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 124 and 125:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 127 and 128:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 129 and 130:
[Humphrey 1989, Fowler 1990, Kitson
- Page 131 and 132:
Integration of Maturity Modeling Th
- Page 133 and 134:
sults, including productivity impro
- Page 135 and 136:
[Davis 2003] Davis, Noopur & Mullan
- Page 137 and 138:
The Capability Maturity Model for S
- Page 139 and 140:
The SEI Contribution The ideas in t
- Page 141 and 142:
Appraisal Methods The Challenge: Pr
- Page 143 and 144:
Ultimately, the SEI’s work in est
- Page 145 and 146:
Maturity Profile The Problem: Lack
- Page 147 and 148:
[Zubrow 2003] Zubrow, David. “CMM
- Page 149 and 150:
improvement causes People CMM resul
- Page 151 and 152:
Managing Operational Resilience The
- Page 153 and 154:
The Consequence: Organizations Can
- Page 155 and 156:
Capability Maturity Model Integrati
- Page 157 and 158:
and suppliers so that quality solut
- Page 159 and 160:
[Kitson 2009] Kitson, David; Vickro
- Page 161 and 162:
tion University. Federal agencies,
- Page 163 and 164:
Engineering Capability Maturity Mod
- Page 165 and 166:
and performance comparisons, Naviga
- Page 167 and 168:
Software Risk Management The Challe
- Page 169 and 170:
[Alberts 2009]. In 2010, SEI resear
- Page 171 and 172:
Personal Software Process and Team
- Page 173 and 174:
An in-progress study of 214 TSP pro
- Page 175 and 176:
[Van Eps 2012] Van Eps, Scott & Mar
- Page 177 and 178:
techniques used in Six Sigma, such
- Page 179 and 180:
Developing a Measurement System Tha
- Page 181 and 182:
Analyze, Improve, Control (DMAIC) t
- Page 183 and 184:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 185 and 186:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 188 and 189:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 190 and 191:
DARPA and the SEI agreed that the S
- Page 192 and 193:
collects over one million pieces of
- Page 194 and 195:
CERT Coordination Center The Challe
- Page 196 and 197:
The Consequence: Knowledgeable Inci
- Page 198 and 199:
Vulnerability Analysis and Remediat
- Page 200 and 201:
System and network administrators a
- Page 202 and 203:
understand the relationship among t
- Page 204 and 205:
[Verton 1999] Verton, Daniel. “Me
- Page 206 and 207:
Secure coding standards give develo
- Page 208 and 209:
provements in how developers use bo
- Page 210 and 211:
The Consequence: Improved Situation
- Page 212 and 213:
Insider Threat The Challenge: Cyber
- Page 214 and 215:
which SEI insider threat experts us
- Page 216 and 217:
Information Security Assessments Th
- Page 218 and 219:
equirements to protect the privacy
- Page 220 and 221:
Cybersecurity Engineering The Chall
- Page 222 and 223:
also developed course descriptions
- Page 224 and 225:
[Mead 2005] Mead, Nancy; Hough, Eri
- Page 226 and 227:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 228 and 229:
government needs, and guidance for
- Page 230 and 231:
and Drug Administration issued draf
- Page 232 and 233:
as a key service and became a NIST/
- Page 234 and 235:
[Feiler 1989] Feiler, Peter H. “S
- Page 236 and 237:
were a few exceptions. For instance
- Page 238 and 239:
[Morris 1991] Morris, Ed; Feiler, P
- Page 240 and 241:
insight into costs, risks, quality,
- Page 242 and 243:
3. leveraging of other SEI work fro
- Page 244 and 245:
Building and Fielding Interoperatin
- Page 246 and 247:
Adoption, and Reuse Technique), whi
- Page 248 and 249:
[Smith 2008] Smith, D. & Lewis, G.
- Page 250 and 251:
Systems Command, and the Joint Engi
- Page 252 and 253:
[Brownsword 1998] Brownsword, L.; C
- Page 254 and 255:
Assurance Cases The Challenge: Conf
- Page 256 and 257:
medical devices. It is helping to c
- Page 258 and 259:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 261 and 262:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 263 and 264:
case). This structural modeling app
- Page 265 and 266:
ArchE (Architecture Expert), 2003.
- Page 267 and 268:
A measure of the influence of SEI a
- Page 269 and 270:
Carnegie Mellon University, 2002. h
- Page 271 and 272:
of abstraction to a FORTRAN-oriente
- Page 273 and 274:
[Lee 1988] Lee, K.; Rissman, M.; D
- Page 275 and 276:
Another group inferred the quality
- Page 277 and 278:
Reducing the Cost of Modifying the
- Page 279 and 280:
and in organizing an ad hoc working
- Page 281 and 282:
Even if two systems have the same g
- Page 283 and 284:
[Pittman 1990] Pittman, J. & Kitric
- Page 285 and 286:
tems and compilers. Later, this wor
- Page 287 and 288:
Architecture Tradeoff Analysis Meth
- Page 289 and 290:
DoD system acquisition [Bergey 2002
- Page 291 and 292:
Feature-Oriented Domain Analysis Th
- Page 293 and 294:
small components could be integrate
- Page 295 and 296:
understand the basis for product li
- Page 297 and 298:
Carnegie Mellon University, 1997. h
- Page 299 and 300:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 302 and 303:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 304 and 305:
In supporting law enforcement cases
- Page 306 and 307:
Operational Support for Digital Int
- Page 308 and 309:
[SEI 2009] SEI Year in Review. Soft
- Page 310 and 311:
allocated rapidly and can be flexib
- Page 312 and 313:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 314 and 315:
CMU/SEI-2016-SR-027 | SOFTWARE ENGI
- Page 316 and 317:
The SEI Role The SEI works with div
- Page 318 and 319:
Diverse experience in industry sugg
- Page 320 and 321:
judgments. These principles are mot
- Page 322 and 323:
tems. The SEI is implementing colla
- Page 324 and 325:
Leading the Community Charged with
- Page 326 and 327:
established an online training prog
- Page 328 and 329:
design of software-intensive system
- Page 330 and 331:
References [Firesmith 2010] Firesmi
- Page 332 and 333:
A Vision for the Future of Software
- Page 334 and 335:
Forensics Future of Software Engine