What type of document produce SRS.
WHAT type of document produce FS(functional spec.)
what type of document produce SDS(design spec.)
Please give me a hierarchy of process of document, which
the companies follow
- 3 Answers
- 11530 Views
- Aloha Technology, Microsoft, I also Faced
- E-Mail Answers
Answer Posted / anuradha
A software requirements specification is a document which is used as a communication medium between the customer
and the supplier. When the software requirement specification is completed and is accepted by all parties, the end of
the requirements engineering phase has been reached. This is not to say, that after the acceptance phase, any of the
requirements cannot be changed, but the changes must be tightly controlled. The software requirement specification
should be edited by both the customer and the supplier, as initially neither has both the knowledge of what is required
(the supplier) and what is feasible (the customer).
Types of Requirements
Whilst requirements are being collated and analysed, they are segregated into type categories. The European Space
Agency defined possible categories as [ESA ’87]:
Functional requirements,
Performance requirements ,
Interface requirements,
Operational requirements,
Resource requirements,
Verification requirements,
Acceptance testing requirements,
Documentation requirements,
Quality requirements,
Safety requirements,
Reliability requirements and
Maintainability requirements
Functional Requirements
Functional or behavioural requirements are a sub-set of the overall system requirements. These requirements are used
to consider trade-offs, system behaviour, redundancy and human aspects. Trade-offs may be between hardware and
software issues, weighing up the benefits of each. Behavioural requirements, as well as describing how the system will
operate under normal operation should also consider the consequences and response due to software failure or invalid
inputs to the system
The Software Design Specification (SDS) document will have two major releases:
Version 1 focuses on specifying a high-level view of the architecture of our system, and on the interaction between the user and the system.
Version 2 focuses on detailing a low-level view of each component of the software and how the components interact with each other.
| Is This Answer Correct ? | 3 Yes | 0 No |
Post New Answer View All Answers
Mention how validation activities should be conducted?
What are the differences between test strategy and test plan?
What is the strategy for automation test plan?
What are the various tools you have used in testing process?
Define Quality testing ?
Explain what is traceability matrix?
How is monkey testing different from adhoc testing?
How validation activities should be conducted?
What is a cause effect graph?
What is quality audit?
How to estimate testing effort ?
Explain the process of project tailoring.
What are the challenges you faced related to production environment bug?
Give me an example of the best and worst experiences you've had with QA.
What are the technical and environment risks u faced in ur testing career?
