Home/ Questions/Q 596111
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T16:08:11+00:00

An SRS should specify logical requirements but not start design. My problem is in

  • 0

An SRS should specify “logical requirements” but not start “design”.

My problem is in the IEEE SRS document (IEEE Std 830-1998) section 5.3.4 says:

5.3.4 Logical database requirements

This should specify the logical requirements for any information that is to be placed in a database. This may include the following:

  • a) Types of information used by various functions;
  • b) Frequency of use;
  • c) Accessing capabilities
  • d) Data entities and their relationships
  • e) Integrity constraints
  • f) Data retention requirements

So does d) mean drawing the ERD is ok? When does specifying the system to this level in REQUIREMENTS bleed in to DESIGN?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A Logical Data Diagram does not define actual data storage. It defines the Entities at a conceptual level. It’s up to somebody else to figure out how to store those Logical Entities.

    …so yes, an ERD would be acceptable.

    This kind of activity would start to bleed into Design if you began to specify actual storage requirements (which data belongs in which tables, data types, etc.) rather than just defining the Entities at the conceptual level.

    • 0