In: Computer Science
Summarize the differences between architectural and detailed design. Discuss the importance of requirements specification in the detailed design to the programmer that will create code to the specification.
#Part 1
#Part 2
A good requirement specification gives a strong base to the building blocks of a software development. It’s the only medium which can make a bridge between the thought of the client and the implementation of the developers. A good requirement specification not only gives the developers the guideline to develop a software, it also minimizes the queries of the developers regarding the development of the software.
Following are several reasons that will light up the value of such a document for a successful, time bound, profitable software.
Different Ideas
When the development team introduced with a project, they bring their own ideas into the product, which most of the time differs from the client’s need and expectations. The specification document brings a balance between the ideas. Client makes a listing about his requirements and ideas while developer team also suggests some part which can improve the base idea(through their experience).
The Graphics
A specification often contains diagrams of different levels, which gives a look and feel of the actual product and helps in different stages of decision taking. This diagrams can be, Use case diagram, ERD, DFD, UML as well, which gives an clear idea to the developer team while developing different modules of the software.
Maintenance
If coding gives life to a software, then the maintenance keeps it alive. Though a very small amount of coding is required in the maintenance phase, but this small coding fixes helps in running the software and keeps it alive in the ever changing world. A good specification always helps to guide the maintenance team for making any changes and upgradation of the software.