Our long-term, regular CACI meeting location is no longer available. We are currently on the hunt for a new space. We hope to have this all worked out by ASAP. Please be patient with us and we look forward to seeing you soon!
We are always looking for speakers for our meetings. We request that preferences for topics, speakers, types of programs, and meeting locations be sent to JDAddelston@upstartsystems.com. If you are interested in helping DC SPIN by hosting or emceeing programs, please let Jonathan know.
We will hold our meeting at the Conference Facility at the Hilton Crystal City in Arlington, VA on one night of the Conference and DC SPIN members will have a 15% discount on the Conference Registration if they choose to attend. Our DC SPIN meeting attendance will be free, as usual. The speaker will be from the SEI's program to be selected jointly and to be announced soon.
We hope to arrange co-sponsorship and similar discounts for other DC area systems/software engineering related professional organizations as well. Please see the conference program accessible through the link provided above.
The conference should be very interesting to our members since you can expect answers to the following intriguing questions at the conference sessions:
* How might you measure the effect that system complexity would have on safety?
* What data would your present to senior leaders who are considering adopting Agile?
* What is technical debt and how can it be managed effectively?
* How can you elicit unstated needs from a variety of stakeholders?
* Can DoD organizations legally develop software using Agile?
* Is data more expensive to produce or to consume?
* How can misuse cases identify security requirements that have been overlooked?
* How can software determine what causes cause what effects, just based on reading your organization's data?
* How can systems engineering technical reviews (SETRs) be modified to make them compatible with both Agile and DoD requirements?
* What are the pros and cons of different methods for trading off software security methods?
* What factors need to be included when estimating the effectiveness of long-term software sustainment?
* How can a developer mitigate the risks inherent in an assembly-based software development strategy?
* How can classical integer programming be used to determine the least-cost (quickest) order for test configurations?
* How can attacks due to exploitation of common programming errors be mitigated? (NOTE: I kept this one because I think that attacks due to exploitation of programming errors are a subset of attacks in general. The tutorial is on secure coding and doesn't cover everything that CERT is concerned about, only attacks that result directly from programming errors.)
* How can architecture-centric virtual integration practice (ACVIP) Identify system-level issues early in development, making them much less expensive to mitigate?