Once your organization has embraced and implemented a DevOps approach to software development, the work shouldn’t end there. Your team may have a streamlined DevOps strategy that fosters a culture of continuous delivery, but they still need to avoid falling into the trap of a drifting or coasting mentality.
On the face of it, nobody should be using floppy disks in the 21st Century. Surprisingly, however, parts of the aviation industry still rely on these disks to manage airplane software.
While your calendar is flurried with holiday dates, you should already be aware of one deadline – Dec. 31, 2017. It’s the date by which anyone holding U.S. government data must comply with the security directives surrounding controlled unclassified information (CUI), known as National Institute of Standards (NIST) Special Publication (SP) 800-171, Revision 1.
Product development programs all start with great optimism regarding their potential to provide an excellent product to customers, along with excellent profits to the company. But research shows that a majority of product developments end in failure. The reasons for each failure are unique, but the overarching reason often can be described as the lack of systems engineering.
Product developments are becoming progressively more difficult. A primary reason for this is that the products being developed today aren’t just products — they’re complex, interconnected systems. A system is a collection of individual parts that work together to accomplish something that no single component could do on its own. The result of living in the “Systems Age” is nearly every product developed is both a system on its own, and works as part of a larger, interconnected system.
DevOps professionals often encounter clients who struggle with sorting through the “what”s and “how”s of where they are in their journey, and how they can either get started with—or improve upon—their current practices.
When the folks at Base2 Solutions are presented with an everyday challenge, you know they’ll attack it with a collective engineering mindset! Even something routine as BBQ was given the Systems Engineering treatment this past summer when a team of B2Sers used Industrial Process Automation to create a Smoker Process Controller.
Continuous Delivery is a DevOps practice where software is produced in short cycles, enabling software to be built, tested, and released faster and more frequently.
My wife and I recently bought a home. While I wouldn’t call it a fixer-upper, there was a long list of projects to be done to get the home into shape. Carpet removal, wood floor refinishing, new lighting, drywall replacement, paint everywhere, and small electrical and plumbing repairs. With guests arriving in a few short months, I had to get to work.
As standalone paper drawings of system diagrams and flowcharts become obsolete, Models Based Systems Engineering (MBSE) is being implemented in more and more organizations as cyber-physical systems become more complex.