Blog

  • Getting Started With a Solution Architecture

    Getting Started With a Solution Architecture

    One of the first questions asked as I start or join a software project is what I think about the solution architecture. This question may either be an attempt to have the current architecture assessed or a first step in building the application. The answer can often be frustrating to the listener as it always begins with a question. Furthermore, there are questions that follow that first one. That does not mean there is no “template” for architecting a solution. However, I think it is important to look at what we are doing in order to take the proper steps.

    Define The Problem

    The most critical factor in creating a solution architecture is not the design of the architecture, it is the solution. Otherwise, you are setting up a classic cart-before-horse approach. There is just too much about a well-designed solution that hinges on the problem you are solving to not focus there first. I once heard it best described as a good architect keeps asking “and then what?” as they listen to someone walk through a problem. The first step is understanding the problem and related processes in detail so you can avoid designing yourself into a corner. A failure to properly understand this point counteracts the skills of even the best architects.

    Requirements and Constraints Drive Solution Architecture

    Everyone likes to start with an “it does everything” approach to define a solution. There is nothing wrong with this. However, a solution architecture that is the best fit requires us to drill deeper. Here are just a few key data points every modern solution needs to address.

    • Who is the Audience?
    • What is the size of the initial user base? (how many users?)
    • How frequently will this be used by the users?
    • What is the expected/useful time frame required to solve the problem?
    • Where does the user experience need to fall between form and function?
    • What sort of data is going to be captured?
    • How long does the data need to be retained?
    • How private or public is the solution and the data? (security concerns)
    • What current technical resources are available?
    • What is the “happy path” and what sort of exceptions might occur?
    • How should the user experience the “happy path” and exceptions?
    • What is the expected interface? (Desktop, mobile, phone, audio, visual, or others)
    • How is this expected to grow in user base, features, and access?

    As you can see, this is a lengthy list. It is also just the beginning. The definition of a good solution architecture includes one that is scalable, maintainable, stable, usable, and understandable. However, it also needs to properly and fully address the problem to be solved. Likewise, there is a context to the problem that needs to be understood as well. As an example, check out the sort of questions a building architect should ask: https://maxablespace.com/questions-an-architect-should-ask-a-client/

    Software Architecture Is Like Building Architecture

    I find the best examples to help understand software design and architecture is to look at building a house. There are a lot of ways to build a house. Therefore, there are a lot of questions to be answered before architecting a plan. The link above provides a list of such questions. Software is at least as complex as a physical building. Thus, it makes sense that we need to answer a lot of questions before designing a software solution.

    There is a lot of context around the solution that impacts architecture much like context impacts a building. Think about building a house on a beach and then think about that same house on a mountainside or uneven ground. Then think about the house in a field of empty acres as compared to the middle of a congested subdivision. Context means a lot when architecting a solution. Therefore a good architect will ask questions and dig deep to understand the context around the desired solution.

    Software Architects are a rare breed. There is only a small percentage of developers that grow into architects for a reason. There is a requirement to be able to fully grasp the business context for a solution and then translate that into the technical architecture. Thus, your best approach to starting a solution architecture is to do your homework and understand the problem to be solved and the proposed solution. Only then can you start on the system architecture.

    Check out this article for some more thoughts on getting started with your project: https://rb-sns.com/RB/blog/planning-and-design/

  • Preparing for a Security Audit

    Preparing for a Security Audit

    The topic of security comes up a lot in IT circles. We see headlines every day about breaches and fear that our company could be next. Ok, that may not be exactly our response. However, hackers are real and a threat to every business that is online. That makes the idea of a security audit attractive to many managers and business owners. They want to be comfortable with where they stand and any associated risks. This may even be a requirement as part of due diligence for an acquisition or investor.

    A Security Audit is Not Scary

    The word “audit” seems to strike fear in the hearts of many. I get it and feel the same trepidation every time I hear it. We seem to think an audit always points to our flaws, and that is a bad thing. To the contrary, an audit of this sort provides a way for us to get better. Yes, it points out flaws and weaknesses. However, it also provides feedback on how to eliminate or overcome those shortcomings. That means that we will be better off, more secure, once we go through an audit and learn from it. It also helps to go into an audit, knowing that imperfections will be highlighted. No system is perfect, so all we can do is look for ways to get better.

    Get Your Ducks In A Row

    The first step to take before a security audit is to clean up the flaws you already know about. This action will make the process more valuable. Less time will be spent on going over the “things you already know.” That means your time and money will be better spent. Why would you pay someone to tell you what you already know. There is another side effect of taking this action. Sometimes weaknesses or flaws are masked by another problem upstream. Think about a dirty window that blocks a view of a dirty room. You will not know about the room until you clean the window. Similarly, clean up the issues you know about, so there is less chance of hiding those flaws you need to understand. Security is a prime area of this sort of environment. By its nature, most IT security is built in layers or walls. Thus, it is by design that a flaw in one level may be masked or even corrected at another level.

    Ask The Experts

    We are not all security masters. That is not a problem. There are plenty of resources available on the Internet to guide us implementing best practices for security no matter what environment we have built. You can bring in security consultants, but you can save a lot of money by hitting some of the cornerstone security sites. One of the best sources of this information is the OWASP site. You can find white papers that cover overall security concerns as well as detailed tutorials for hardening your systems. Many of this documentation is source material for security audit procedures and processes. Therefore, you will be able to educate yourself about these measures while getting a head start on how the security audit will expect your environment to look.

    Yes, It Is That Simple

    You may be amazed at how short this article is. However, the details that you will find in those security tutorials can take hours or days (or more) to implement. The plan is simple. It is the execution that can be a challenge. Nevertheless, there are a lot of security recommendations that are quick and easy to implement. Even a little investment of time can make your security audit experience enjoyable and educational. That statement may seem laughable but do not take my word for it. Give it a shot and see how much more secure your systems are as your confidence about them soars.

  • Thank You For Your Business – Customer Appreciation Tips

    Thank You For Your Business – Customer Appreciation Tips

    Each year we enter a season of giving and thankfulness as it winds down.  One of the things that come out of this is a sort of season of customer appreciation.  The challenge in this attitude is finding the best way to show our appreciation without coming off too sappy.  We want to thank our customers and build loyalty, not overwhelm them with more selling.

    To Brand or Not To Brand

    The first decision to make with this customer appreciation “gifts” is whether we slap a logo or other brand label on them.  Do we give our customers a notebook with our logo on it? A nice drinking glass with our motto? Or some other knick-knack that is a glaring reminder of who gave it?  I think the answer to this question can be found in our other seasonal gifts.

    Do you buy your relatives a gift stamped with your name?  Do those gifts you give, scream the source of them?  No, you often give something that is about the recipient instead.  Now, there is a consideration of how to handle gift-giving from a company.  When you stamp your label on an item, it can be filed under marketing.  I think this is understood by most people, so it is not seen negatively.  Therefore, if you want to put a logo on an item, try to make it subtle.  There are good examples of this all over where a typical logo is replaced with one for marketing purposes.  You can fall back on the golden rule (sort of) in this situation.  Ask yourself if the emblem is unobtrusive or subtle enough that you would use the gift in public without feeling “odd.”

    Does Size Matter?

    The size or value of the gifts is always part of the consideration as well.  There are industries where limits are placed on gifts, and that makes it easy.  However, I find it far more common to be in a sort of Wild West of gift valuation.  In these situations, I think it is a heart decision.  How generous do you want to be?

    It is easy to use some sort of percentage of profits from a customer as a rule of thumb.  For example, take five percent of the profits earned and use that as a measure of what to give.  That feels a bit cold and calculated though.  I think you will find a better response when you focus on utility first and then find a value that fits.  A personal example was a gift of laptop bags for customers.  It started with the idea of those backpacks being desirable.  Heck, I even got one for myself that I use daily.  Then I looked at options that fit my rough budget.  The focus was the gift, not the sales appeal or monetary valuation of it.  This approach helps build a rapport as it shows thoughtfulness instead of simply a business relationship.  Customers like to be appreciated for more than just their wallet.

    The Moment of Truth

    The last facet of gift-giving I want to visit is the delivery.  I think we all agree that hand-delivering the gifts is always best.  It is a personal touch and a chance to show our sincerity.  You might also see it as a chance to sell to your customers.  I have seen this a lot from consulting companies.  The gift then becomes an excuse to get a few minutes of time from decision makers.  I recommend you avoid this at all costs.  You will get a lot more loyalty out of giving a gift with no strings (or sales) attached than one more shot at a sale.

    Business and personal life often coincide in the modern world.  The season of giving is no different.  Just make sure you come at it with the right attitude.