ISBN : 978-81-963532-2-3 (E-Book) visible behavior of the system. For this reason, the SRS document is also called the black-box specification of a system. • Conceptual integrity. It should show conceptual integrity so that the reader can easily understand it. • Response to undesired events. It should characterize acceptable responses to undesired events. These are called system response to exceptional conditions. • Verifiable. All requirements of the system as documented in the SRS document should be verifiable. This means that it should be possible to determine whether or not requirements have been met in an implementation. Problems without a SRS document The important problems that an organization would face if it does not develop a SRS document are as follows: • Without developing the SRS document, the system would not be implemented according to customer needs. • Software developers would not know whether what they are developing is what exactly required by the customer. • Without SRS document, it will be very much difficult for the maintenance engineers to understand the functionality of the system. • It will be very much difficult for user document writers to write the users’ manuals properly without understanding the SRS document. Problems with an unstructured specification • It would be very much difficult to understand that document. • It would be very much difficult to modify that document. • Conceptual integrity in that document would not be shown. • The SRS document might be unambiguous and inconsistent. DECISION TREE 25 Software Engineering Keerthana P, Manasa KN, Ganga D Bengal
31 Publizr Home