The following are the Interview questions related to the topics Understanding the requirements: Requirements Engineering, Establishing the groundwork, Eliciting Requirements, Developing Use Cases, Building the requirements model, Negotiating Requirements, Validating Requirements, Requirements Modeling(Scenarios, Information and Analysis Classes): Requirements Analysis, Scenario-Based modeling, UML Models that supplement the Use Case, Data Modeling Concepts, Class-Based Modelling, Requirements Modelling (Flow, Behavior, Patterns and WEBAPPS): Requirements Modeling strategies, Flow oriented Modeling, Creating a Behavioral Model, Patterns for Requirements Modeling, Requirements Modeling for WebApps.
1.Define “Requirements Engineering”?
A. “The process of providing the services based on the customer requirements from the system and constraints under which it operates and developed as well” is called as ‘Requirements Engineering’.
2.What are the ways to gather requirements?
A.We can gather requirements from the users through interviews, surveys, brain storming, task analysis, prototyping, studying the currently available/using version of software and also by observation.
3.List the objectives of Requirement Analysis.
The following are the objectives of Requirement analysis:
- Describing the customer needs.
- Establishes a base to model a software design.
- Defining requirements gathering which can be validated once building a software design is done.
4. What are the functions included in Requirements Engineering Process?
A.Inception, Elicitation, Elaboration, Negotiation, Specification, Validation and Management are the functions of Requirements Engineering Process.
5.What do you mean by Functional Requirements?
A.The functional features and specifications which are expected by users from the recommended software product are known as Functional Requirements.
6.What comes under Non-Functional requirements?
A.Non-Functional requirements are implicit. Security, performance, look and feel of user interface, Interoperability, cost and so on comes under Non-Functional requirements.
7.Mention the issues with Domain requirements.
A.”Understandability” and “Implicitness” are the major problems in Domain requirements. Under Understandability the Requirements are expressed in the language of the application domain. This is often not understood by software engineers developing the system. Under Implicitness the Domain specialists understand the area so well that they do not think of making the domain requirements explicit.
8.What are the elements does a Requirements document structure contains?
A.Requirements document structure contains Introduction, Glossary, definition of user requirements, System architecture, SRS (System Requirements Specification), System Models, System evolution, appendices and Index.
9.What are Use Cases?
A.Use-cases are a scenario based approach in the UML(Unified Modeling Language) which finds the actors in an interaction and also describes the interaction itself. A set of use cases should describe all possible interactions with the system. There might be a situation to use Sequence diagrams to include details to use-cases by showing the sequence of event processing in the system.
10.How the product requirements can be specified?
A. We can formulate some product requirements accurately based on Performance,Usability and Capacity of that product while the others are complex to quantify and, consequently, are often stated informally.
11.What are the key skills required in requirements gathering phase?
A. The key skills required are ability to catch the customer’s perception, awareness on upgraded technology, Domain expertise, excellent interpersonal skills and communication skills.
12.Give the dimensions of requirements gathering.
A.Responsibilities, current system needs, Targets and ongoing needs are the dimensions of requirements gathering.
13.How the system requirements are done classified?
A.The system requirements classification includes Functional requirements, performance requirements, Availability needs, security and Environmental definition.
14.Mention the elements of an analysis model.
A.The analysis model comprises of elements such as Data Dictionary, ER Diagram(Entity Relationship Diagram, Data Flow Diagram, State Transition diagram, Control Specification and Process Specification.
15.What do you mean by SRS?
A. SRS is abbreviated as “Software Requirement Specification”. SRS is a document which is produced during the process of requirements gathering. This SRS can also be considered as the procedure of refining requirements and documenting them as well.
16.What does a SRS document contain?
A.SRS includes Information description, Functional Description, Behavioral Description, Validation Criteria, Bibliography and Appendix and First user’s manual.
17.State the issues in Elicitations?
The following are the issues in Elicitations:
- Problem of Scope.
- Problem of Volatility.
- Problem of understanding.
18.List out the features of Software Requirement Specification (SRS)?
A.The features of SRS are Correctness, Unambiguous nature, Complete, Consistent, Specific and Traceable.
19.Define two types of Prototyping approaches in Software process.
A. a.Evolutionary prototyping – In this approach the initial prototype is made and then it is refined through number of phases to final phase.
b.Throw-away prototyping – In this approach a rough practical implementation of the system is produced. From this implementation the requirement issues are detected.
20.Mention some Rapid prototyping methods?
A.There exist various rapid prototyping techniques. Some of them are Dynamic high level language development, Database programming. Component and application assembly.