"One of the things that we found with DoD and federal clients is that these principles are a little bit new. Some of them feel good—they feel like they fit within the DoD culture—and some of them don’t."
"When the project first starts out, initially we’re ticking off progress at a pretty regular basis…but what can happen as you start nearing completion—the 70, 80, 90 percent done—is that progress as measured can begin to stall out.
"A TRA is not a documentation review. There’s a lot of planning that goes into it, six months to a year’s worth of planning out front. You actually get into design details, engineering studies, & test reports. It’s really a heavy-duty engineering level review.
"The biggest fear is really vendor lock-in. People want to have the freedom to move from one cloud provider to another in case the relationship between them isn’t working, service-level agreements aren’t being met, other providers have better prices, or even if their provider goes out of business, which is not unusual in today’s world. If there aren’t standards, then moving between providers could be very difficult. "
"When people do the system-safety analysis, they are focused on the physical parts failing, and they understand that part. But the consequence of that in software today is still not very well understood. "
"Some people I've talked to, they really love agile. They love the techniques. And it's working really well for their team, for their project, but they are really having a hard time getting other projects in the organization to be just as successful as they are. That really is the key."
"Now imagine you're walking into a village in Afghanistan. There may be some people that you or your colleagues have made contact with before that you know are friendly. It would be very useful to know about those people. In addition, it would be very useful to know about where there are potential threats.
"If you make an architectural decision that promotes interoperability or modifiability, this can have a negative impact on other qualities such as availability, reliability, security, or performance. Making these trade-offs is one of the hardest parts of architecting and designing any system. "
"The idea is to be able to develop highly capable, rapidly evolving, innovative systems, but to do so in a way where the risk of completion of projects is within the bounds of acceptability for major systems developments.
"It's always going to cost you more to fix it after the fact, and it’s very hard to go back to the point of origin and correct data once it’s entered the system. Now, our specific research last year was to investigate the use of some statistical techniques, primarily associated with outlier detection. "
"Misaligned incentives usually occur in the absence of well-designed rules that control the rewards or penalties for participants. The underlying idea is that unless the rules incentivize them to do otherwise, people and organizations both tend to act in their own self interest, which may not always be what was wanted."
"In essence cloudlets are localized, lightweight servers, very lightweight, that are running one or more virtual machines. The idea is that soldiers can offload expensive computations from their handheld mobile devices onto these virtual machines. "
"Of course the other big question is, do we really need to go into a quantifiable aspect of debt, or is it good enough to just state in the metaphor realm? I tend to believe that if we can't measure it, we can't control it."
"The biggest problem today is software is getting bigger and bigger. The big question naturally is how do you scale? How do you make this work for larger organizations, for larger project sizes? Things that work within a small team, with people that can talk face-to-face, don't necessarily scale when you go to bigger projects."