Last post Sep 30, 2010 05:10 AM by aidoco
Sep 30, 2010 04:00 AM|kashifdotnet|LINK
Where should I define any application/database level constraint - In the Software Requirement Spefications (SRS) or Software Design Document SDD. e.g. An EmployeeID is unique OR If we update a particular value, a log entry is made. And in the respective
SRS or SDD, any particular section?
Sep 30, 2010 05:10 AM|aidoco|LINK
The SDD would be more appropriate.
Your 'business' requirements should be as agnostic of technology or implementation as possible.
The SRS should detail Function and non functional requirements
I would encourage you to create your use cases so they are sufficiently detailed , don't be afraid of text in use cases so that this text becomes similar to the 'user story' concept but includes a UML usecase diagram.
With regards to "An employeeID is unique" this belongs in Data Design, ideally represented by an Entity Relational Diagram with indication of this attribute is a primary key. ERD diagramming should suffice for this. The ERD is design, the data schema
or DDL is the implementation of that design.
With regards to "if we update a particular value, a log entry should be made" , this seems to be a Procedure so possibly belongs in 'Procedureal Design' of the SDD, i.e. there is a decision to log X when Y occurrs. It could be argued that this "logging"
could be specified in a SRS usecase as a 'Post Condition' of the particular update.
It is totally fine to have it in both places.