Understanding The Specifications Puzzle
Setting the specifications for the design and development of systems and software is a bit like this song Gershwin classics and personally, what I as the biggest cause of confusion in the field of information technology, as long as I can remember, more than 30 Years in the industry. Some people say, specifications, should be based on the inherent properties of information, while others believe it is based on a screen or a report or a file, layout, others are still categorically think they should be focusing on the processes and data specifications. Interestingly, all are absolutely correct. The difference lies in the perspective of the person and work to complete. For example, how the specifications for the design of a car is certainly different, explain to us how a skyscraper. The same applies in the I.T. Area in which we have different things to be produced by different people, for example:
1st The programmer (also known as a software engineer) required to develop detailed specifications to the code for a program (source and destination). Normally it takes the form of processing requirements (for example, the hardware configuration, the types of transactions to process, volume, calendars, news, etc.) and the need for physical data (Input / Output file sent).
2nd DBA (Database Administrator) requires detailed specifications for a file, select technology management (eg DBMS) and generate the necessary data definition language (DDL). Normally it takes the form of a database that is the logical model of relations between the data.
3rd The analyst (Alias, a systems analyst, systems engineer, systems architect, Business Analyst) - requires specifications on the end user requirements in the aim of finding a solution to the system. This is normally on the basis of a definition of the users of the measures and / or decisions taken. According to the conception of the system, analyst goods to the specifications of the programmer and DBA in their part of the puzzle. In this perspective of the analyst is the translator between the users and programmers and administrators of databases.
Each part has its own unique point of view of the jigsaw and as such requires different “Pflichtenheft.” To address the problem, but the role of the analyst strongly decreased over the years, which helps programmers to try to determine what the needs of end users, a skill that they are generally not trained or adapted. To illustrate, I recall the history of the IT director at a company for the manufacture of footwear, a call by the Corporate Sales Manager, in order to ask for help on an urgent problem. The director of a programmer in his meeting with the Director of Sales and discuss the problem. Generally, the manager wanted an impression of all footwear sales prestige model ordered by volume, type, color, etc. The programmers immediately knew how to get access to the necessary data and are classified, carry a big impression (three feet high), reliably for the user.
The director of sales by the Director of the Bureau a few days later, to know if the programmer has adequately insured the user. The director of sales of programmers brackets granted to its power and pride quite impressively the impression of strength sits in his office. The director then asked how the operators of the paper. He explained that he had at home at the weekend, slowly through the gentle and erected a report which shows the evolution of sales.
“Did you tell the programmers do you?” asked the head of IT.
“No,” replied the director of sales.
“Are you not aware that we have your report for you and give you much time and effort?”
“No.”
It is a classic example of the blind leading the blind. The users do not know how to describe adequately the economic problem, and the programmer has the wrong questions. Remarkably, the Director of Sales and programming with the results were very satisfied. The IT Director shook his head in disbelief.
There are significant differences between the requirements of information under the order and software. Both have their place, but the two serve different purposes. Considering that a genuine investigation of the analyst company, the reason for the information, the control unit of life in the physical world and is only how the software works.
It is not rare to hear the programmers are complaining, “The users do not know what they want.” May you do not know about the physical or, as it should be made better, but the users know what they want of information aspects. Most programmers are simply not the right questions. Then again, they were not trained to do this to try and compensate for the absence of a genuine analysts.
Remarkably, the analyst knows a function increase in the industry that companies find that a person is the highest level is necessary to understand the company and a broader perspective of a society, systems and software. For example, the work process in general as follows:
1st Working with the users, the analyst studies of the company and helps the user, adapted to the needs of the information.
2nd The requirements, the analysts a concept of the system, either a new system and / or amendment of an existing system. Under the plan, the analyst defined:
* The logic of processing the data on the way, it must be collected, stored and retrieved.
* The process of the affairs, including the Parties implemented by the computer.
* The construction of the inputs and outputs.
* The development of the logical database model.
In examining the treatment, the analyst, which parties can be carried out or by a commercial programming.
3rd The design specifications are sent to the programming and implementation of the room.
4th From the logical database model, the DBA a physical designs and creates the necessary data definition language. The dba is on the physical layout file the programmer for implementation.
5th The programmer, the software specifications and determine an appropriate method of implementation, for example, the languages, with the appropriate tools and techniques of design.
To the graphics, see:
http://www.phmainstreet.com/mba/blog/ss080225.jpg
The actual beneficiary of such an approach is the programmer that the “working estimate” was removed around him. This May a simplification of the whole process, but it has to show that the essential role of analysts and how it is unlike the other participants. In the absence of such a person, the standard programmers necessarily the role of the analyst and it is here that the specification problems.
This shows the limits of “Agile” methods. In its resources, the proponents of these methods recognize that only the software, and especially by a single program. Here they try to speed up the process, global specification for the collection, to participate in the work of programming.
In addition to identifying the relationships between the various functions in development, there is also the problem of the development of a coherent and standard for the registration of specifications. This can be done through the mouth, but it is likely saved the technical documentation for the work to complete and as a way to check the finished product to see if they in fact do not meet the specifications. In the areas of engineering and construction standards were developed over the years to the specifications, such as Blue Printing. But in I.T. Have a variety of techniques were used with little or no standardization. For example, there are several types of graphics and technical quality, and the deposits and dictionaries database list and the specifications. Few, very few companies have standards for the collection of specifications.
CONCLUSION
The problem with the specifications in the conception and development of systems and software is primarily due to a lack of standardization in industry. There is a lack of standards in the following areas:
* Various types of products from the process of development and the format (including specifications).
* The various functions of the development processes involved and their relationships and the duties and responsibilities.
* Different prospects of development in view of the inherent properties of systems and software.
* Various methods, tools and techniques to the design and development.
Pending a lack of standardization in industry, there is yet another interpretation of what are the specifications and the best way to document. In other words, we will continue to say: “You like tomato and I like tomahto.” So, if we work together?Read more information by clicking the links below:
Music Blog | City Travel | Love Blog | Internet Nerds | Granaditas | Maldigras | About Cars | Nerve Crack | Gamer’s World | Perfect Diapason | Anime | Latest Buzz | Business | Creative Innovations | Sports Reviews | Creative Writing | Fashion Today | Blog Loan Online | Online Opportunities | Blog Addict | Site Submission | Make Money Online | Technology | Gadgets | Articles | Gizmos | Travel | Finance | Blogging | Opinions | Entertainment | Reviews | Websites | Money | Sugar Free Blog | Bonsang | Latest Videos | Globe Auto Load | Airsoft | BlogToMillion | Lifestyle | Shopping | Computer | Britney Spears | PC Games | Marketing | News | Web Design | Society | Benefits | Services | Papable | Blog | Internet Marketing | Real Estate | Earn Online | jSison |
