Design requirement Vs software requirement?
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1220
Printed Date: 21Jul2025 at 9:00pm
Topic: Design requirement Vs software requirement?
Posted By: Vedanti_kumer
Subject: Design requirement Vs software requirement?
Date Posted: 03May2007 at 5:24am
In short, the SRS should not include any design requirements. However,
this is a difficult discipline. For example, because of the
partitioning and the particular RTOS you are using, and the particular
hardware you are using, you may require that no task use more than 1 ms
of processing prior to releasing control back to the RTOS. Although
that may be a true requirement and it involves software and should be
tested – it is truly a design requirement and should be included in the
Software Design Document or in the Source code.
Consider the target audience for each specification to identify what goes into what documents.
Marketing/Product Management
Creates a product specification and gives it to Systems. It should define everything Systems needs to specify the product
Systems
Creates a System Specification and gives it to Systems/Software and Mechanical and Electrical Design.
Systems/Software
Creates a Software Specification and gives it to Software. It should define everything Software needs to develop the software.
Thus, the SRS should define everything explicitly or (preferably) by
reference that software needs to develop the software. References
should include the version number of the target document. Also,
consider using master document tools which allow you to include other
documents and easily access the full requirements.
|
|