SRS is said to be perfect if it covers all the needs that are truly expected from the system.

This suggests that each element is uniquely interpreted.

The SRS is ranked for importance and stability if each requirement in it has an identifier to indicate either the significance or stability of that particular requirement.

SRS should be made as modifiable as likely and should be capable of quickly obtain changes to the system to some extent.

SRS is correct when the specified requirements can be verified with a cost-effective system to check whether the final software meets those requirements.

The SRS is traceable if the origin of each of the requirements is clear and if it facilitates the referencing of each condition in future development or enhancement documentation.

This depends upon each requirement explicitly referencing its source in earlier documents.

This depends upon each element in the SRS having a unique name or reference number.

An SRS should be written in such a method that it is simple to generate test cases and test plans from the report.

An end user may be an expert in his/her explicit domain but might not be trained in computer science.

The SRS report should be concise and at the same time, unambiguous, consistent, and complete.

The SRS document should define the external behavior of the system and not discuss the implementation issues.

All requirements of the system, as documented in the SRS document, should be correct. 

This activity reviews all requirements and may provide a graphical view of the entire system.

It identifies the entities outside the proposed system that interact with the system.

One effective way to find out what the customer wants is to construct a design, something that looks and preferably acts as part of the system they say they want.

This process usually consists of various graphical representations of the functions, data entities, external entities, and the relationships between them.

It shows relationships among system objects.

It is the description of functions that enable the transformations of system objects.

A manner in which software responds to events from the outside world.

It is a data modeling method used in software engineering to produce a conceptual data model of an information system.

It is used to connect the logical structure of the database to users.It is used to connect the logical structure of the database to users.

It is denoted as a rectangle in an ER diagram.

It is a collection of related types of entities.

It is an attribute or collection of attributes that uniquely identifies an entity among the entity set.

A set of attributes that collectively identifies an entity in the entity set.

An entity set may have more than one key attribute.

A minimal super key is known as a super key.

It key is one of the candidate keys chosen by the database designer to uniquely identify the entity set.

An attribute that is a combination of other attributes.

It is a valued attribute contain a single value.

It is an attribute that can have more than one value.

An attribute that does not exist in the physical database, but their values are derived from other attributes present in the database.

It is the association among entities and represented by the diamond-shaped box.

It is also called recursive relationships.

It is a relationship between the instances of one entity type.

 It is a relationship between the instances of two entity types.

It is a relationship amongst instances of three entity types.

It describes the number of entities in one entity set, which can be associated with the number of entities of other sets via relationship set.

It is one entity from entity set A can be contained with at most one entity of entity set B and vice versa.

When a single instance of an entity is associated with more than one instances of another entity then it is called ______. 

More than one entity from entity set A can be associated with at most one entity of entity set B, however an entity from entity set B can be associated with more than one entity from entity set A.

One entity from A can be associated with more than one entity from B and vice-versa.

It is a traditional visual representation of the information flows within a system.

It is used to connect process to each other to source or sinks the arrow head indicates direction of the flow.

It indicates that the data is stored which can be used at a later stage or by the other processes in a different order.

It performs some transformation of input data to yield output data.

It is an external entity and acts as a source of system inputs or sink of system outputs.

It is also known as fundamental system model, or context diagram represents the entire software requirement as a single bubble with input and output data denoted by incoming and outgoing arrows.

This process may be repeated at as many levels as necessary until the program at hand is well understood.

It can be used to project or record the specific/necessary detail about the system's functioning

No process can have only outputs or only input, processes must have both outputs and inputs.

Process labels should be noun phrases.

In source or sink data moves directly between external entities without going through a process.

Data flow from a process to a data store means update (insert, delete or change)

Data flow from a data store to a process means retrieve or use.

Data flow labels should be verb phrases.

Many data moves directly between external entities without going through a process.

It is a file or a set of files that includes a database's metadata.

It hold records about other objects in the database, such as data ownership, data relationships to other objects, and other data.

It include other names by which this data item is called DEO for Data Entry Operator and DR for Deputy Registrar.

It is a textual description of what the data item is used for or why it exists.

It capture relationships between data items e.g., total_marks must always equal to internal_marks plus external_marks.

Range of values records all possible values, e.g. total marks must be positive and between 1 to 100.

Aliases capture the name of processes that generate or receive the data items.

If the data is itself a data aggregate, then data structure form capture the composition of the data items in terms of other data items.

Data flow capture relationships between data items e.g., total_marks must always equal to internal_marks plus external_marks.

The data dictionary is an essential component of any relational database because of its importance and it is invisible to most database users.

It is a specification for a specific software product, program, or set of applications that perform particular functions in a specific environment.