lOMoARcPSD|16248954
1) Describe what is a SRS document.
A software requirements specification (SRS) is a document that describes what
the software will perform and how it will operate. It also specifies the functionality
that the product must have in order to meet the needs of all stakeholders
(business and users).
2) Discuss the difference between functional and non-functional requirements.
Functional requirements are statements of services the system should provide,
how the system should react to particular inputs, and how the system should
behave in particular situations. In some cases, the functional requirements may
also explicitly state what the system should not do. While non-functional
requirements are constraints on the services or functions offered by the system.
They include timing constraints, constraints on the development process, and
constraints imposed by standards. Non-functional requirements often apply to the
system as a whole rather than individual system features or services.
3) Enumerate and explain the two techniques for requirements elicitation
Interviewing where you talk to people about what they do and observation or
ethnography, where you watch people doing their job to see what artifacts they
use, how they use them, and so on,
1) Describe what is a SRS document.
A software requirements specification (SRS) is a document that describes what
the software will perform and how it will operate. It also specifies the functionality
that the product must have in order to meet the needs of all stakeholders
(business and users).
2) Discuss the difference between functional and non-functional requirements.
Functional requirements are statements of services the system should provide,
how the system should react to particular inputs, and how the system should
behave in particular situations. In some cases, the functional requirements may
also explicitly state what the system should not do. While non-functional
requirements are constraints on the services or functions offered by the system.
They include timing constraints, constraints on the development process, and
constraints imposed by standards. Non-functional requirements often apply to the
system as a whole rather than individual system features or services.
3) Enumerate and explain the two techniques for requirements elicitation
Interviewing where you talk to people about what they do and observation or
ethnography, where you watch people doing their job to see what artifacts they
use, how they use them, and so on,
