21⟩ Described Stress testing?
We impose abnormal input to stress the capabilities of the software. Input data volume, input data rate, processing time, utilization of memory, etc. are tested beyond the designed capacity.
Associate Software Engineer
Home Computer Programming Associate Software Engineer
“Associate Software Engineer Frequently Asked Questions by expert members with experience in Associate Software Engineer. These questions and answers will help you strengthen your technical skills, prepare for the new job test and quickly revise the concepts”
41 Associate Software Engineer Questions And Answers
22⟩ What is software engineering?
Some basic definitions of software engineering are:
The application of a disciplined engineering approach to the development of software systems.
A body of knowledge and experience in software development practice and process.
23⟩ Described Objective Based Testing?
Some of the testing under this category and what they mean are as follows.
24⟩ Described Integration Testing?
According to IEEE, Integration Testing is An orderly progression of testing in which software elements, hardware elements, or both are combined and tested, to evaluate their interactions, until the entire system has been integrated. It Test against system design and Focuses on communication between modules start with one module, then add incrementally. Various Types of Integration Testing are: * big bang approach - Integrate Everything at once * top-down approach - Keep on breaking the system in parts one by one and than test each part. * bottom-up approach - Test the small parts first and than keep on integrating the system and keep on testing the bigger module of it. * mixed approach - Done by help of stubs (Dummy modules)
25⟩ Described Unit Testing?
The Tools used in Unit Testing are debuggers, tracers and is Done by Programmers. Unit testing verifies the functioning in isolation of software pieces which are separately testable.
26⟩ What are the types of Testing in Software Engineering?
As per Test Target, there is * Unit Testing * Integration Testing * System Testing As per Test Objective, there is * User Acceptance Testing * Installation Testing * Functional * Alpha / Beta testing * Regression * Performance * Stress * Usability * Configuration * Smoke (Sanity Test) Let's see them one by one.
27⟩ What is RUP?
RUP stands for Rational Unified Process
It deals with -
★ Iterative software development process.
★ Visual Modeling of Systems
★ Quality Management
★ Change Control Management
★ Deals with the role, the activity, and the artifact
★ For managing OO Software Development
28⟩ What is Testing in Software Engineering?
Testing is running the program(or product) under various circumstances and conditions to find errors and bugs in it. This is important as releasing a faulty product will not only cause serious problems to the end user, it will also harm the companies reputation. There are various kind of Testing conditions and which one to use depends on type of product.
29⟩ Described Functional Testing?
It checks that the functional specifications are correctly implemented. Can also check if Non Funcctional behavior is as per expectations.
30⟩ How to Design a Test Case?
This Question is often asked in microsoft of from any other company who is looking to hire you for testing work. A test case will have 5 section.
31⟩ Described Installation Testing?
System testing conducted once again according to hardware configuration requirements. Installation procedures may also be verified.
32⟩ Described User Acceptance Testing?
Testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is Done against requirements and is done by actual users.
33⟩ Described Security Testing?
It is ued toverify proper controls have been designed.
34⟩ What are the Functional and Non Functional Requirements in Software Engineering?
Functional Requirements are the Expected functionality or services from the system.
Non - Functional Requirements are System property and constraints. Now Constraints can be on requirements itself. Some examples are of Response time, 24X7 availability of the system etc.
35⟩ Which are main steps involved in developing a software?
The steps involved are Planning Analysis Design coding testing. After testing maintenance of the product in also involved.
36⟩ Define SRS?
SRS stands for Software Requirement Specification.
It establishes the basis for agreement between customers and contractors or suppliers on what the software product is expected to do, as well as what it is not expected to do.
Some of the features of SRS are -
★ It sets permits a rigorous assessment of requirements before design can begin.
★ It sets the basis for software design, test, deployment, training etc. It also sets pre-requisite for a good design though it is not enough.
★ It sets basis for software enhancement and maintenance.
★ It sets Basis for Project plans like Scheduling and Estimation.
37⟩ Described Requirement Engineering?
Software Requirements are Descriptions and specifications of a system-A requirementis a condition or capability to which the system must conform and Define. A system is designed with certain functionality in mind and to ome up with that functionality and its specification right at the beginning is Requirement Engineering. Requirements Engineering-Eliciting, organizing, and documenting the requirements of the system-The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed Software requirements should be:
★ Clear
★ complete
★ Unambiguous
★ Quantitative
38⟩ Described Usability Testing?
It evaluate the Human Computer Interface. Verifies for ease of use by end-users. Verifies ease of learning the software, including user documentation. Checks how effectively the software functions in supporting user tasks. Checks the ability to recover from user errors.
39⟩ Described Configuration Testing?
It is Used when software meant for different types of users. It also check that whether the software performs for all users.
40⟩ Described Sanity Test?
It is used to Verify whether the build is ready for feature/requirement based testing).
