I’ve been working on a project at work that involved looking at a software package to see how it can be used to solve some problems. I’ve learned several things but the driving point is that no matter what the software is you cannot use it for something that it is not designed to do. When the writer(s) of the software started to work on it, they went in with a vision of what they needed to accomplish with it, and in turn, designed it for that purpose(s).
Now, I know that it should go without saying, but a lot of times this is attempted and almost every time it fails, or at least ends up with a lot of unhappy people. The first step needs to be determining the intended use and building off of that. Once that is done an accurate view can be taken as to how it can be used.
By using a product for what it was designed, it will not only save time, but also frustration that comes with using something for something other than it was designed. I don’t usually write about this side of things, but it has been dominating the projects that I’ve been working on.
Filed under: Technology , design, implementation, software, testing
Recent Comments