Software Requirement Analysis and Specifications Interview Questions & Answers

5 avg. rating (100% score) - 1 votes

Software Requirement Analysis and Specifications Interview Questions & Answers

Want to switch your career to Software Requirement Analysis and Specifications? Then we will provide you with all the necessary details for you to clear the interview on Software Requirement Analysis and Specifications. With our jobs portal you will find the number of jobs related to you along with the software Requirement Analysis and Specifications Interview Questions and Answers. There are various leading companies that offer jobs in various roles like CE Modem Requirement Testing, System Specification Engineer, Software Requirements Engineer, and many other roles too. To save the time in searching for all the interview questions and answers on different site we have provided you all type of interview question and answers at one place. For more details on Software Requirement Analysis and Specifications jobs visit our site www.wisdomjobs.com.

Software Requirement Analysis And Specifications Interview Questions

Software Requirement Analysis and Specifications Interview Questions
    1. Question 1. What Is A Software Requirements Specification?

      Answer :

      A software requirements specification (SRS) is a description of a software system to be developed. It lays out functional and non-functional requirements, and may include a set of use cases that describe user interactions that the software must provide.

    2. Question 2. What Is Srs In Project?

      Answer :

      SRS stands for Software Requirements Specification, which is a document that fully describes the expected behavior of a software system. Functional requirements are documented in an SRS, as are non-functional requirements such as performance goals and descriptions of quality attributes.

    3. Question 3. What Is Requirement Specifications Of The System?

      Answer :

      A System Requirements Specification (abbreviated SyRS when need to be distinct from a Software Requirements Specification SRS) is a structured collection of information that embodies the requirements of a system.

    4. Question 4. What Is Srs In Software Engineering?

      Answer :

      A software requirements specification (SRS) is a document that captures complete description about how the system is expected to perform. It is usually signed off at the end of requirements engineering phase.

    5. Question 5. What Are The Requirements Of Software?

      Answer :

      Software Requirements is a field within software engineering that deals with establishing the needs of stakeholders that are to be solved by software.

    6. Question 6. What Are User Interface Requirements?

      Answer :

      UI is an important part of any software or hardware or hybrid system. A software is widely accepted if it is -

      • easy to operate.
      • quick in response.
      • effectively handling operational errors.
      • providing simple yet consistent user interface.

    7. Question 7. What Is The Requirement Gathering?

      Answer :

      In requirements engineering, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders. The practice is also sometimes referred to as "requirement gathering".

    8. Question 8. What Is The Need For An Srs Document?

      Answer :

      Software Requirements Specification is usually the first deliverable for any software project. As they say, first impression is the best impression!, and you should ensure that even the first draft of an SRS is of high quality.

      The benefits of a good SRS are :

      ● A contract between the customer and the software vendor – A good SRS document specifies all the features required in the final system including technical requirements and interface requirements. SRS document is used by the customer to determine whether the software vendor has provided all the features in the delivered software system. To the Software vendor it provides a solid foundation to fix the scope of the software system.

      ● Enables costing and pricing of the project – A well defined SRS enables software developers to accurately estimate the amount of effort required to build the software product. Function point analysis and SMC are some the techniques adopted for estimating effort.

      ● Input for detailed design – A good SRS enables experienced developers to convert the requirements directly to a technical design. For example, a well defined data dictionary can be easily converted to a database specification.

      ● Management of customer expectations – Since SRS precisely defines project scope, it ensures that customer expectations don’t change during software development. If they do, SRS can be modified and costing/pricing can be done again on the changes required. 

    9. Question 9. What Are The Contents Of An Effective Srs Document?

      Answer :

      There is no single precise template for writing good Software Requirement Specifications.

      The contents of an SRS document depends on the software product being developed and also on the expertise of the people doing the requirement elicitation. Different business/technology domains in a company usually have their own customized version of SRS template. Still a good Software Requirement Specification (SRS) usually contains project scope section, functional requirements, requirement analysis models, external interface requirements and non functional requirements.

    10. Question 10. How Many Types Of Software Requirements Are There?specify Them?

      Answer :

      Software Requirements : We should try to understand what sort of requirements may arise in the requirement elicitation phase and what kinds of requirements are expected from the software system.

      Broadly software requirements should be categorized in two categories:

      1. Functional Requirements.
      2. Non-Functional Requirements.

    11. Question 11. Explain Functional And Non Functional Requirements?

      Answer :

      Functional Requirements :Requirements, which are related to functional aspect of software fall into this category.They define functions and functionality within and from the software system.

      EXAMPLES -

      • Search option given to user to search from various invoices.
      • User should be able to mail any report to management.
      • Users can be divided into groups and groups can be given separate rights.
      • Should comply business rules and administrative functions.
      • Software is developed keeping downward compatibility intact.

      Non-Functional Requirements :Requirements, which are not related to functional aspect of software, fall into this category. They are implicit or expected characteristics of software, which users make assumption of.

      Non-functional requirements include -

      • Security
      • Logging
      • Storage
      • Configuration
      • Performance
      • Cost
      • Interoperability
      • Flexibility
      • Disaster recovery
      • Accessibility

       

    12. Question 12. What Is Prototyping?

      Answer :

      Prototyping is building user interface without adding detail functionality for user to interpret the features of intended software product. It helps giving better idea of requirements. If there is no software installed at client’s end for developer’s reference and the client is not aware of its own requirements, the developer creates a prototype based on initially mentioned requirements. The prototype is shown to the client and the feedback is noted. The client feedback serves as an input for requirement gathering.

    13. Question 13. What Is Brainstorming?

      Answer :

      An informal debate is held among various stakeholders and all their inputs are recorded for further requirements analysis.

    14. Question 14. What Is Domain Analysis?

      Answer :

      Every software falls into some domain category. The expert people in the domain can be a great help to analyze general and specific requirements.

    15. Question 15. What Is Task Analysis?

      Answer :

      Team of engineers and developers may analyze the operation for which the new system is required. If the client already has some software to perform certain operation, it is studied and requirements of proposed system are collected.

    16. Question 16. What Is Requirements Analysis?

      Answer :

      Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications.

    17. Question 17. What Are The Software Requirement Validations?

      Answer :

      Software Requirement Validation : After requirement specifications are developed, the requirements mentioned in this document are validated. User might ask for illegal, impractical solution or experts may interpret the requirements incorrectly. This results in huge increase in cost if not nipped in the bud. Requirements can be checked against following conditions -

      • If they can be practically implemented.
      • If they are valid and as per functionality and domain of software.
      • If there are any ambiguities.
      • If they are complete.
      • If they can be demonstrated.

    18. Question 18. What Are The Features Of Srs?

      Answer :

      SRS should come up with following features:

      • User Requirements are expressed in natural language.
      • Technical requirements are expressed in structured language, which is used inside the organization.
      • Design description should be written in Pseudo code.
      • Format of Forms and GUI screen prints.
      • Conditional and mathematical notations for DFDs etc.

    19. Question 19. What Is A Static Analysis Tool?

      Answer :

      Static program analysis is the analysis of computer software that is performed without actually executing programs (analysis performed on executing programs is known as dynamic analysis). In most cases the analysis is performed on some version of the source code, and in the other cases, some form of the object code.

    20. Question 20. What Is Meant By Static Code Analysis?

      Answer :

      Static program analysis is the analysis of computer software that is performed without actually executing programs (analysis performed on executing programs is known as dynamic analysis). In most cases the analysis is performed on some version of the source code, and in the other cases, some form of the object code.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Software Engineering Tutorial