It’s been a while since I’ve checked in on enterprise architecture (EA). My last in-depth work with EA was around 2011 when I was on detail to the Office of Personnel Management’s Open Government Team. The EA model I worked with was the top-down organizational design of information technology assets, data assets, and business processes. Many of you are probably familiar with this traditional EA model. Six years later, it is predicted that in 2018 that “half of enterprise architecture (EA) business architecture initiatives will focus on defining and enabling digital business platform strategies.
We hope you are finding it easier to get the information you need on USDA.gov following the launch of our site redesign in March. We’ve already welcomed over 1 million visitors to the new site and we are pleased with the positive feedback we’ve received thus far. Our redesign makes it easier for you to get the news you care about quickly and get on with your busy life. Now, you can explore “USDA in Action,” an area designed to quickly share what’s happening across the department.
You may have heard of “serverless architecture” or Amazon Web Services (AWS) Lambda product and wondered what is unique about this new buzzword. As with many new digital cloud technologies, serverless architecture could mean two things. It may be applications that are built using third-party cloud applications. Or serverless architectures could be pieces of code that live in the cloud and only run when called on by a user: event-driven functions.
One day, at an unnamed agency, the Outlook server crashed. The server stayed down for the rest of the afternoon. Deprived of email and meeting calendars, employees wandered around trying to remember what meetings they had to attend. Other employees went searching for people who they ordinarily would email. There was confusion that made people realize just how dependent they were on a single software program. As the Federal government moves toward digital transformation, I have been thinking about how agencies can best weather the transition from legacy systems to cloud-based, agile applications.
This is the fifth in a series describing how the Social Security Administration is working towards a more modern IT infrastructure. You can find part 1 here, part 2 here, part 3 here and part 4 here. In the next three posts we will consider the problem of modernizing old legacy software. In this post we will start a discussion about why modernizing software is important and what is most important to think about first.