answersLogoWhite

0

How do you evaluate quality of SRS?

Updated: 12/18/2022
User Avatar

Wiki User

11y ago

Want this question answered?

Be notified when an answer is posted

Add your answer:

Earn +20 pts
Q: How do you evaluate quality of SRS?
Write your answer...
Submit
Still have questions?
magnify glass
imp
Continue Learning about Engineering

Draw the figure about when the preparation of the SRS document can begin?

Q#3: Draw the figure about when the preparation of the SRS document can begin.[5]


Srs for employee management system?

SRS for employee management system is quite effective as it contains quite a number of features like tracking time for employees and so many others. SRS stands for Software Requirements Specification.


Define an expression that evaluates to true when i equals j?

In Java, or C, the expression is simply:i == jIf the two are equal, this expression will evaluate to true; if not, it will evaluate to false.In Java, or C, the expression is simply:i == jIf the two are equal, this expression will evaluate to true; if not, it will evaluate to false.In Java, or C, the expression is simply:i == jIf the two are equal, this expression will evaluate to true; if not, it will evaluate to false.In Java, or C, the expression is simply:i == jIf the two are equal, this expression will evaluate to true; if not, it will evaluate to false.


What is SRS in software engineering?

SRS in context of Software Engineering stands for System Requirements Specification. It is a document that specifies the complete description of the behavior of the system. For example, if the group of software engineers are to design a software for a bank. Assuming they are provided with BRD (Business Requirement Design), the engineers first need to describe and design the behavior of the software. The various entities the software has to react with, the various properties it should possess and so on. These specification can be a type of SRS.


When the preparation of the SRS document can begin?

SRS if I am assuming correct a Software Requirement Specification Document, can begin from day 1. One can start taking rough notes, and with more functional information gathered , the SRS can be continually refined. Though at the same time, the Business Analyst should consider the limitations of the technology used for development or depending on the reqs an appropriate platform must be chosen. After a thorough analysis of functional and technical scope an SRS can move towards finalization and can be later signed off by business users and Technical Project Managers I hope that helps