Analysis for software projects is the act of gathering, curating, and collating enough detailed information about a set of given problems that people would like to use software to solve. If it is complete enough, then it can be used as the sole reference for people creating designs for these solutions. It has all of the answers to all of the questions that a designer will have.
All software systems are anchored by the data that they collect.
The usage of these systems is confined within the boundaries of the data that they have access to. In that sense, this data sets the foundation on which any other features or functionality are built.
If there is a problem for which one wants to use software to solve it, then obviously the first and foremost thing that needs to be done is to figure out what data is necessary.
Data comes in two basic forms: a) you collect it directly from people, b) you cross-reference it from somewhere else.
So analysis goes through each and every datum and tries very hard to list it out with proper names, some understanding of expected frequency, location, properties, etc.
The more you know about the data, the smoother the development process will be.
For some data, it is not worth collecting literally; you can get it from relatively easy computations based on other raw data. So, the analysis needs to specify any ‘derived’ data necessary and how to compute it from the underlying raw data.
Since the software is a ‘solution’, it is important to understand how people will use it in order to solve their problems. Most of the time it is not ‘log in and click a button’. It is a considerably more complex ‘workflow’ where the users leverage specific functionality in a bunch of features, over a multi-step process in order to make decisions or create specific artifacts that they share.
The analysis needs to list out all of the known workflows, in as much detail as possible. When there are misfits with using the software, they begin and end in these workflows. That is, if it is only possible to do half the work in the system to accomplish something, then the system isn’t a particularly tight fit. If you can do it all and there is just one button to press, it is really tight, but if there is a lot of functionality in the system, the problem switches to being able to find that button, not pressing it.
Presenting data for decisions is straightforward, but then minimizing the navigation after that decision is critical too. If someone decides that the data indicates a specific action, it would be best if the button to trigger that action was presented at the same time, or at least very close by. So, presentations need to be linked back to their lists of expected actions. That is, you need to know why the data needed to be presented in order to wire up the navigation for the decisions.
Creating new artifacts is similar. They are essentially manually triggered derived data, but the tools to create and edit them can be very complex. The tools need to be arranged in a way that matches the expected usage for creating stuff. And more importantly, the tools should leverage as much of the existing data as they can; the user should not have to retype things, just rearrange them.
For cross-referenced data, there are usually performance vs. quality decisions that need to be made. If you grab the data early and keep it around, there is a chance it can get stale before you update it. That would be worse than if the process of using or presenting the data is really slow. So, there are accuracy expectations for all cross-reference data that need to be taken into account.
The analysis of a set of problems should give enough details about people dealing with those problems that a solid design can be produced. Analysis is nearly timeless. If the business does not change, the “business logic” within does not change either, even if the system gets reimplemented with many different technologies over the years. So, the descriptions, references, tables, etc. in the document should not reference, rely on, or be tied to any technology. In order to deal with a problem, you need to collect data and work with it in the following ways. It’s the ‘what’ portion of the issues, where the design document is the ‘how’.
For example, you might need to know a derived metric like the ‘yield’ of a given bond in the financial markets. There are many different ways to calculate that, all based on the bond’s prospectus. The yield is a real number, which for many technologies is represented using floating-point variables, although there are lots of other ways of representing it.
Analysis should really only be done once for a new line of business, then updated over the years and decades as the underlying domain changes. In this sense, it is independent of any sort of software implementation, and the work to keep it up to date should be disconnected from any IT initiatives. A business should be constantly working through its own analysis in order to keep its own line of business operating as well as possible. If that were done, then software projects would start at ‘design’ instead of ‘analysis’, which would likely take less time and improve their quality.
No comments:
Post a Comment
Thanks for the Feedback!