Learn now! Which SDLC Model seems Too complex?|

Dear IT Students !!!
That offers training courses to prepare students for employment in the industry. Our Courses are designed based on corporate-approved syllabus that includes technical training, aptitude classes, placement grooming, attitude development, soft skills training and real time internship experience.
We specialise in We have facilitated the smooth transition of several students from college to the workplace. At SLA we impart training and education in Software testing and other courses such as Dotnet, Java, And PHP at basic as well as advanced levels. Our students are placed at top organisations. Join us today for the right start to your IT career.
ABOUT SOFTWARE TESTING:
Testing is a process of identifying defects where a defect is any variance between actual and expected results. Find errors and ensure that all the functionalities are implemented and working as per user requirement.
Install/uninstall Testing: Quality assurance work that focuses on what customers will need to do to install and set up the new software successfully. It may involve full, partial or upgrades install/uninstall processes and is typically done by the software testing engineer in conjunction with the configuration manager.
Internationalization Testing: The process which ensures that product's functionality is not broken and all the messages are properly externalized when used in different languages and locale. It is usually performed by the testing teams.
Inter-Systems Testing: Testing technique that focuses on testing the application to ensure that interconnection between application functions correctly. It is usually done by the testing teams.
Keyword-driven Testing: Also known as table-driven testing or action-word testing, is a software testing methodology for automated testing that separates the test creation process into two distinct stages: a Planning Stage and an Implementation Stage. It can be used by either manual or automation testing teams.
Load Testing: Testing technique that puts demand on a system or device and measures its response. It is usually conducted by the performance engineers.
Localization Testing: Part of software testing process focused on adapting a globalized application to a particular culture/locale. It is normally done by the testing teams.
Loop Testing: A white box testing technique that exercises program loops. It is performed by the development teams.
Manual Scripted Testing: Testing method in which the test cases are designed and reviewed by the team before executing it. It is done by manual testing teams.
Manual-Support Testing: Testing technique that involves testing of all the functions performed by the people while preparing the data and using these data from automated system. it is conducted by testing teams.
executing the necessary artifacts to perform software testing. It is usually performed by testing teams.
Mutation Testing: Method of software testing which involves modifying programs' source code or byte code in small ways in order to test sections of the code that are seldom or never accessed during normal tests execution. It is normally conducted by testers.
Modularity-driven Testing: Software testing technique which requires the creation of small, independent scripts that represent modules, sections, and functions of the application under test. It is usually performed by the testing team.
Non-functional Testing: Testing technique which focuses on testing of a software application for its non-functional requirements. Can be conducted by the performance engineers or by manual testing teams.
Negative Testing: Also known as "test to fail" - testing method where the tests' aim is showing that a component or system does not work. It is performed by manual or automation testers.
Operational Testing: Testing technique conducted to evaluate a system or component in its operational environment. Usually it is performed by testing teams.
Orthogonal array Testing: Systematic, statistical way of testing which can be applied in user interface testing, system testing, regression testing, configuration testing and performance testing. It is performed by the testing team.
Pair Testing: Software development technique in which two team members work together at one keyboard to test the software application. One does the testing and the other analyzes or reviews the testing. This can be done between one Tester and Developer or Business Analyst or between two testers with both participants taking turns at driving the keyboard.
Passive Testing: Testing technique consisting in monitoring the results of a running system without introducing any special test data. It is performed by the testing team.
Parallel Testing: Testing technique which has the purpose to ensure that a new application which has replaced its older version has been installed and is running correctly. It is conducted by the testing team.
Path Testing: Typical white box testing which has the goal to satisfy coverage criteria for each logical path through the program. It is usually performed by the development team.
Penetration Testing: Testing method which evaluates the security of a computer system or network by simulating an attack from a malicious source. Usually they are conductedby specialized penetration testing companies.
Performance Testing: Functional testing conducted to evaluate the compliance of a system or component with specified performance requirements. It is usually conducted by the performance engineer.
Qualification Testing: Testing against the specifications of the previous release, usually conducted by the developer for the consumer, to demonstrate that the software meets its specified requirements.
Ramp Testing: Type of testing consisting in raising an input signal continuously until the system breaks down. It may be conducted by the testing team or the performance engineer.
Regression Testing: Type of software testing that seeks to uncover software errors after changes to the program (e.g. bug fixes or new functionality) have been made, by retesting the program. It is performed by the testing teams.
Recovery Testing: Testing technique which evaluates how well a system recovers from crashes, hardware failures, or other catastrophic problems. It is performed by the testing teams.
Requirements Testing: Testing technique which validates that the requirements are correct, complete, unambiguous, and logically consistent and allows designing a necessary and sufficient set of test cases from those requirements. It is performed by QA teams.
Security Testing: A process to determine that an information system protects data and maintains functionality as intended. It can be performed by testing teams or by specialized security-testing companies.
Sanity Testing: Testing technique which determines if a new software version is performing well enough to accept it for a major testing effort. It is performed by the testing teams.
Scenario Testing: Testing activity that uses scenarios based on a hypothetical story to help a person think through a complex problem or system for a testing environment. It is performed by the testing teams.
Scalability Testing: Part of the battery of non-functional tests which tests a software application for measuring its capability to scale up - be it the user load supported, the number of transactions, the data volume etc. It is conducted by the performance engineer.
Statement Testing: White box testing which satisfies the criterion that each statement in a program is executed at least once during program testing. It is usually performed by the development team.
Static Testing: A form of software testing where the software isn't actually used it checks mainly for the sanity of the code, algorithm, or document. It is used by the developer who wrote the code.
Stability Testing: Testing technique which attempts to determine if an application will crash. It is usually conducted by the performance engineer.
Smoke Testing: Testing technique which examines all the basic components of a software system to ensure that they work properly. Typically, smoke testing is conducted by the testing team, immediately after a software build is made .
Storage Testing: Testing type that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. It is usually performed by the testing team.
Stress Testing: Testing technique which evaluates a system or component at or beyond the limits of its specified requirements. It is usually conducted by the performance engineer.
Structural Testing: White box testing technique which takes into account the internal structure of a system or component and ensures that each program statement performs its intended function. It is usually performed by the software developers.
System Testing: The process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It is conducted by the testing teams in both development and target environment.
System integration Testing: Testing process that exercises a software system's coexistence with others. It is usually performed by the testing teams.
Top Down Integration Testing: Testing technique that involves starting at the stop of a system hierarchy at the user interface and using stubs to test from the top down until the entire system has been implemented. It is conducted by the testing teams.

Thread Testing: A variation of top-down testing technique where the progressive integration of components follows the implementation of subsets of the requirements. It is usually performed by the testing teams.

Upgrade Testing: Testing technique that verifies if assets created with older versions can be used properly and that user's learning is not challenged. It is performed by the testing teams.
Unit Testing: Software verification and validation method in which a programmer tests if individual units of source code are fit for use. It is usually conducted by the development team.
User Interface Testing: Type of testing which is performed to check how user-friendly the application is. It is performed by testing teams.

Why Fu-vision?
Syllabus that Meets industry Demands
Get Trained in Technical and Soft Skills
Live Project Exposure
Fast Track Batches
More than 500 IT Client Base
Exclusive Placement Cell
Weekend Batches
Tailor-Made Curriculum
PLACEMENTS:

Fu-VISION has made an extensive research to learn the expectations of IT industry and our syllabuses are framed with that on grounds so as to make the entry or re-entry of any candidate a cakewalk. IT industry is vast, but the psychology is simple.
In order to make the HR consultancy more effective, Fu-VISION has a Placement Cell in all its offices. Every Placement Cell constitutes a team of sensible and prudent team of HR specialists headed by an expert Placement Co-ordinator.

In 2009-10, All leading MNC s are looking for Software Test Engineers. Fu-VISION Placed More Software Test Engineers for the Year 2009-10.Still more openings for Software Testing in IT Companies Globally.

For any further clarifications, feel free to contact us:

Cell no: 9360029290,9442173717,9003206648,9943129290
Mail us:[email protected]

Venue:
COIMBATORE: HEAD OFFICE
NO:96,HOPE COLLEGE BUS STOP,
OPP KRISHNA SWEETS,
PEELAMEDU,
AVINASHI ROAD,
COIMBATORE