by Anthony Tsakiris
Ford Motor Company
Architecture development activities as presented in books, articles, and classes are sometimes “heavy” – that is, they require a lot of time and people resources relative to what is available. That’s my view from an automotive embedded-control-systems environment. An argument can be made that that’s what it takes, but there’s another reality that time and resources are truly in short supply. It’s difficult to get stakeholders who are busy with multiple projects and production concerns to commit big chunks of their time to an activity like a Quality Attribute Workshop for a new project.
by Russell Miller
Vice President of Technology Services at Impulse.com
Co-host of Architectural Concepts podcast
At SATURN 2014 there were a number of excellent sessions on DevOps and Continuous Delivery; one of those was Dianne Marsh’s keynote entitled, “Engineering Velocity: Continuous Delivery at Netflix.” Dianne is the director of engineering tools at Netflix, a company that has led the way in terms of continuous delivery. Dianne’s main objective for the talk was to share details and philosophy from Netflix that the audience could consider for application in their organizations as a means to improve their velocity. She did a great job achieving that objective.
There's No Room for Deadlines: Allen Holub at Dr. Dobbs explains why a “culture of deadlines” can defeat an Agile team how the Agile Manifesto principle of working at a constant pace can produce better results.
Slow Down to Speed Up - It's All About Delivery: In this video, Matt Anderson of the Cerner Corporation recommends using Lean concepts so that Agile teams can deliver more with less effort.
The Hacker Way Meets Agile Architecture: Jason Bloomberg at DevXtra’s Agile Architecture Revolution contrasts “the Hacker Way” with The Enterprise and discusses how Agile architecture can bring them together.
What Every Company Should Know About Agile Software Development: Eric Wittman MIT Technology Review’s View from the Marketplace urges organizations that want to maintain a competitive edge to adopt agile software development practices.
Internet of Things
Being Forgotten in the Internet of Things: Nick Malik at Microsoft Developer Network’s Inside Architecture discusses a complication in European citizens’ new “right to be forgotten” and proposes a solution.
Nest: A Small Company and a Big Disruption Enabled by Cloud: Gery Menegaz at IBM’s Thoughts on Cloud explains how the Nest Learning Thermostat made innovative use of cloud technology to turn a profit, help power companies solve a problem, and satisfy a government mandate.
Microsoft Backs Open Source for the Internet of Things: Patrick Thibodeau at Computerworld reports that Microsoft has joined the AllSeen Alliance to help promote an open source code framework to standardize device communications.
Internet of Things Done Wrong Stifles Innovation: Frank Palermo at InformationWeek considers the “dark side” of the Internet of Things. How will the IoT address security and privacy?
At the Architectural Concepts Podcast, SATURN 2014 Technical Chair Michael Keeling discusses techniques for exploring and uncovering the shortest path to amazing architectures, mapping the idea of design modes to software architecture.
In the podcast, Michael also discusses the rapid software architecture workshop, based on these ideas, that he delivered at SATURN 2014.
June 12, 2014—From August 4–6, 2014, educators from leading institutions will gather at the SEI's Pittsburgh headquarters for the 11th annual Architecture-Centric Engineering (ACE) Workshop for Educators. The SEI hosts this annual event to foster an ongoing exchange of ideas among educators whose curricula include the subjects of software architecture and software product lines. The event is free of charge and open to any accredited, college-level educator.
Introducing new software languages, tools, and methods in industrial and production environments incurs a number of challenges. Among other necessary changes, practices must be updated, and engineers must learn new methods and tools. These updates incur additional costs, so transitioning to a new technology must be carefully evaluated and discussed. Also, the impact and associated costs for introducing a new technology vary significantly by type of project, team size, engineers’ backgrounds, and other factors, so that it is hard to estimate the real acquisition costs.
This blog post at the SEI blog presents research conducted independently of the SEI that aims to evaluate the safety concerns of several unmanned aerial vehiclesystems using the Architecture Analysis and Design Language (AADL) and the SEI safety-analysis tools implemented in OSATE.
"SATURN has become my favorite annual professional event," says Eltjo Poort at Eltjo's Solution Architect Blog. Read Eltjo's review of SATURN 2014.