Wednesday, September 25, 2013
What is meant by multiplexing?
Posted by
Sunflower
at
9/25/2013 02:58:00 PM
0
comments
Labels: Analog, Channels, Communication, Data, Demultiplexing, digital, Frequency, Messages, Multiple, Multiplexing, Multitasking, Networks, Performance, Physical, Process, Resources, Signals, Types
|
| Subscribe by Email |
|
Monday, August 19, 2013
What is meant by multi-destination routing?
- Effective routing algorithms have been developed that are capable of routing the messages from one source node to a number of receiving nodes i.e., the multiple destination nodes.
- These algorithms are termed as the multi – destination routing algorithms and the process is therefore called as the multi – destination routing.
- This type of routing has been developed for the minimization of the cost of the network i.e., NC (network cost).
- Network cost can be defined as the sum of all the links’ weights that consist of the routing path.
- There are many heuristic algorithms available for determining the NC min path.
- This problem falls under the category of the NP – complete problems.
- Heuristics are available for the traveling salesman problem and MST (minimum spanning tree) variations.
- Global information is used by both of them.
- Another set of such heuristics is available that uses only shortest paths for reaching the destinations.
- The best worst case performance is exhibited by the MST algorithm.
- However, one study revealed that effectiveness of the simpler heuristics is higher.
- The network cost (NC) is often compared with the destination cost (DC).
- Destination cost is the sum of the cost of all the shortest paths that lead to the destination.
- A scheme of algorithms has been developed for trading off between these two costs i.e., the NC and DC.
- The sender of the transmitted data cannot be taken as a single node in a network where the cooperative communication is supported.
- This asks for the re-investigation of the traditional link concept.
- Any routing scheme thus depending up on this link concept needs to be reconsidered.
- Also, the potential performance gain resulting because of the cooperative communication needs to be exploited.
- Routing often gets complicated for some networks where the selection of the paths is no longer the job of a single entity.
- Rather, a number of entities are involved in the selection of the paths.
- Multiple entities can even select specific parts of a path.
- If these selected paths are chosen by the entities for their own objectives optimization then it can lead to inefficiency or serious complications in the network since they may or may not conflict with the other entities’ objectives.
- This would become clear from the following example, consider traffic moving in a system of roads.
- Now here each driver selects a path that would minimize only his/her traveling time.
- In this kind of routing, there are longer equilibrium routes (i.e., longer than the optimal.) for almost all other drivers.
- This is often termed as the Braess paradox.
- Another example is of the routing the AGVs (automated guided vehicles) by a model on some terminal.
- For prevention of the simultaneous usage of the infrastructure’s same part reservations are made. - This is called as the context – aware routing.
- The internet is divided in to a number of divisions which are nothing but Ass i.e., the autonomous system like ISPs.
- All these systems have control over the routes that lie in their own network at various different levels.
Following steps are involved in multi – destination routing:
1. The BGP protocol is used for selecting the AS – level paths.
2. A sequence of autonomous systems is produced by the BGP protocol via which the packet flow will take place.
3. The neighboring Ass offer multiple paths for each of the AS from which it can choose. Paths are selected based up on the relationships between the neighboring systems.
4. Each selected path refers to multiple corresponding router level paths.
Posted by
Sunflower
at
8/19/2013 04:53:00 PM
0
comments
Labels: Algorithms, Communication, Cost, Destination, Entity, Links, Messages, Multi-destination Routing, Multiple, Network, Nodes, optimization, Paths, Performance, Process, Receive, Route, Routing, Source
|
| Subscribe by Email |
|
Monday, July 8, 2013
Explain Carrier Sense Multiple Access Protocols - CSMA
Posted by
Sunflower
at
7/08/2013 01:10:00 PM
0
comments
Labels: Access, Carrier Sense, Carrier Sense Multiple Access, Channels, Collision, CSMA, Data, Multiple, Packets, Protocols, Re-transmit, Signals, Stations, transmission, Transmit
|
| Subscribe by Email |
|
Saturday, June 15, 2013
What is Process State Diagram?
Process States
Posted by
Sunflower
at
6/15/2013 09:36:00 PM
0
comments
Labels: CPU, Diagram, Events, Input, Memory, Multiple, Multitasking, Operating System, Primary, Process, Process Sate Diagram, Processors, Queue, Ready, Secondary, States, Time, Transition, Waiting
|
| Subscribe by Email |
|
Tuesday, May 7, 2013
What is meant by Time sharing system?
- SDS 940
- PDP – 10
- IBM 360
Posted by
Sunflower
at
5/07/2013 09:30:00 PM
0
comments
Labels: Application, computers, Cost, Data, Design, efficient, Expensive, Interactive, Interface, Multi-programming, Multi-tasking, Multiple, Organization, program, Resources, System, Technology, Time sharing System, Users
|
| Subscribe by Email |
|
Sunday, February 17, 2013
Explain Rapise - Web Functional/Regression Test Tool
About Rapise
- Microsoft internet
explorer
- Mozilla firefox and
- Google chrome
- Ajax
- GWT
- YUI
- Flash/ flex
- AIR
- Silverlight and so
on.
Features of Rapise Testing Tool
- Learn and go
functionality: This lets you create test scripts rapidly. This works in a
more efficient manner than what traditional recording and playback methods
we have. The editing of the object takes place during the learning
process.
- Keyword driven testing and data driven
testing
- Windows and web
application testing
- Can be extended
using Javascript
- Adobe AIR and Flash
support
- Supports DevExpress,
Infragistics and telerik controls.
- Support for Qt
framework
- Integrated reporting
capabilities that are very powerful.
- Integration with SpiraTest for effective test management.
Posted by
Sunflower
at
2/17/2013 05:00:00 PM
0
comments
Labels: Application, Automatic, Browsers, Cross-browser, Data-driven, Environment, Flexible, Functional, Keyword, Multiple, Objects, Rapise, Record, Regression, Requirements, Test Scripts, Testers, Tests, Web, Web Application
|
| Subscribe by Email |
|
Friday, August 10, 2012
What are the benefits of creating multiple actions within any virtual user script?
What is Virtual User?
- Clicking
the mouse
- Hovering
or pointing the mouse over some object on the screen.
- Typing
the words and commands.
- Selecting
some object.
Benefits of creating multiple actions with virtual user script
- Creating
multiple actions within a VU script becomes quite effective when employed
in tests that are highly repetitive and consist of many variations.
- With
the multiple action feature, more and more tasks can be performed which
otherwise would be quite a tedious job to do for the human users. But for
a system it is possible since it does not bother itself with tiredness,
tediousness and thus proving itself as an ideal tester.
- Another benefit of
the multiple actions in one virtual user script is that such tests can be
created which can be run at almost every internal build of the software
system or application under question in the stages like:
- With a virtual user
script with multiple actions it can be easily verified that no
functionality was broken by the code changes that were made to the earlier
version of the software system or application.
- With the help of
multiple actions containing virtual user scripts, an automatic bug verification
mechanism can be set up by imitating the steps through which a bug can be
reproduced.
- The automatic big
verification test thus developed can be used to test each and every
release of the software system or application thus ensuring that the bug
has been fixed and there are no chances of it sneaking back in to the
program code.
- These multiple
actions scripts can be split in to single ones whenever required.
Posted by
Sunflower
at
8/10/2012 12:00:00 PM
0
comments
Labels: Actions, Application, Automatic, Bugs, Create, Functionality, Multiple, Scripts, Software System, Software testing, Steps, Tasks, Tester, Tests, Time, Users, Virtual, Virtual user, Virtual user script
|
| Subscribe by Email |
|
Friday, March 23, 2012
Multiple Condition Coverage is a white box testing technique - Explain?
There are so many types of the code coverage and the multiple condition coverage is also one of them and that is what has been discussed all about in this article.
What is code Coverage?
Code coverage as we all know is a process that aims at the following purposes:
- Creation of the additional test cases for increasing the coverage.
- Looking up for such areas of the software system or application code that have not been exercised by any of the test cases.
- Determination of the quantitative measure of the extent of the code coverage which can be thought of as an indirect measure of the software quality.
- Identification of the redundant test cases which does not affect the code coverage.
The whole process is a time consuming one and thus is helped by an automating tool called the code coverage analyzer.
What is Multiple Condition Coverage?
- Multiple condition coverage is a modification of the condition coverage type of the code coverage.
- As the term “multiple condition coverage” itself suggests that it implements almost all the possible combinations of the conditions in order to check whether those possible combinations do occur in the execution of the test cases or not.
- A large number of the test cases are required for carrying out a full multiple condition coverage of a decision and these are supplied by the truth tables of the logical operators obtained for that particular decision.
- The multiple condition coverage offers an added advantage in the languages such as C, C++, Java and so on which have short circuit operators which is that it helps in implementing a thorough testing.
- It in turn makes the multiple condition coverage in such languages very similar to the condition coverage.
Disadvantage of Multiple Condition Coverage
But, one should not think that the multiple condition coverage is void of any disadvantages.
- It does have one which is that the deciding up on the minimum number of test cases required for the coverage proves to be very difficult job.
- The problem worsens as the complexity of the boolean expressions implemented in the decisions increases.
- Another disadvantage adds to the problem of the test case designer which is that the minimum number of the test cases required for the coverage varies substantially from condition to condition having the similar level of complexity.
Lets take an example:
For example, in a decision, first condition may require 5 test cases while the second one may require 11 test cases and both the conditions are having the same number of operators and operands.
In contrast to the condition coverage that includes the decision coverage also, the multiple condition coverage does not include any decision coverage.
Now what about the languages like Pascal and visual basic that do not have short circuit operators? For such languages the multiple condition coverage is implemented in the form of the path coverage for logical expressions.
One point to be noted here is that the advantages and disadvantages remain the same in the path coverage form also since in the path coverage the number of each additional logical operator is doubled the number of the required test cases.
Multiple condition coverage takes in to consideration two or more conditions and then makes them in to a group and then they are tested. "Since the multiple condition coverage requires a very detailed knowledge of the software system or application’s code in order to understand all the decision aiming statements in that and in turn decide for the minimum requirement of the test cases, therefore it has been categorized under the white box testing techniques."
Posted by
Sunflower
at
3/23/2012 11:35:00 AM
0
comments
Labels: Advantages, Application, Branch Coverage, Code, Code Coverage, Combinations, Conditions, Decision, Disadvantages, Multiple, Multiple Condition Coverage, Paths, Test cases, White box testing
|
| Subscribe by Email |
|
Thursday, February 2, 2012
What are different aspects of Cross Browser Testing?
Cross browser can be defined as the ability of a web page, web site or web application to run easily on all the browsers i.e., the web site, web page or application should have a good browser compatibility.
Many people confuse between cross browser compatibility and multiple browser compatibility.
Multiple browser compatibility is the ability of a web site, web page or application to execute efficiently on many browsers simultaneously. If a web site, web page, or application is having good browser compatibility, it is able to run on all browsers and without any loss of performance.
Maintenance of standards of performance is essentially necessary. All the browsers are then able to render that particular web site or application.
1. Cross browser testing is a no new methodology and has been in use since the web development started.
2. But, nowadays cross browser testing is used rarely since the modern versions of the browsers already have built in support for scripts like CSS 1 and HTML and so the browsers do not require any kind of proprietary extensions to attain the quality of cross browsing.
3. Another reason is that nowadays DOM manipulation methodologies which are way more compatible than cross browser compatibility testing are being used for the development of client side scripts.
4. The main browsers that a web page, site, application or a script needs to support include the following:
- Internet explorer
- Netscape
- Mozilla Firefox
- Google chrome
- Safari and
- Opera
These days only a little of cross browser support is demanded. The emphasis is on improving compatibility. The World Wide Web consortium introduced in 1997 a browser scripting language called “ECMA script” which was supposed to improve the cross browser compatibility of the browsers. It was after this only that the W3C started working up on DOM techniques.
1. Cross browser testing forms an essential part of web testing or when application testing, so it needs to be focused up on.
2. There are several testing tools available in the market today to carry out automated cross browser testing.
3. There are so many web browsers available today, and so the end users are not using the same browser.
4. A variety of browsers are in user which calls a need for testing of web sites and applications.
5. This need can be fulfilled by cross browser testing.
6. Client components like applets, flex, flash programs, AJAX and java scripts may behave differently when accessed through different browsers.
7. Also for every browsers hands end user’s request in a way that is different from the other.
8. Web developers need to make sure that the web sites and applications they are making are compatible with all the browsers and deliver exactly the same performance on any browser.
9. Testing a website or application for a single browser is of course not beneficial.
10. Cross browser testing involves testing of web sites or applications on both the sides i.e., client side and server side.
There are following kinds of engines:
- Gecko is used in Mozilla Firefox browser.
- KHTML is used by conqueror web browser.
- Presto is developed by opera and is used for opera browser.
- Trident or MSHTML is used for Microsoft developed browser “internet explorer”.
- Web kit is used for Google chrome and safari. It supports other browsers also.
Layout engines play a very important role in cross browser testing. They are basic entity that needs to be tested when you want to improve the cross browser compatibility. A layout engine is a web component that takes web contents and formatting instructions as input and displays the formatted content on the web page.
Posted by
Sunflower
at
2/02/2012 02:59:00 PM
0
comments
Labels: Application, Browsers, Compatibility, Cross browser testing, Development, Multiple, Performance, Quality, Standards, Test Scripts, Web Applications, Web development, Web page, Web sites
|
| Subscribe by Email |
|
Saturday, April 16, 2011
Model-View-Controller (MVC) Design Pattern
Model View Controller design pattern is used to support multiple types of users with multiple types of interfaces. The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes:
- Model: The model locates all data information for the application. It does not care about how you interpret it or how process it. It divides functionality among objects involved in maintaining and presenting data to minimize the degree of coupling between the objects.
- View: The view manages the display of information. It is responsible for maintaining the consistency in its presentation when the underlying model changes.
- Controller: The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate. The actions performed on the model can be activating device, business process or changing the state of a model.
The MVC pattern allows any number of controllers to modify the same model. The strategies by which MVC can be implemented are as follows:
- For Web-based clients such as browsers, use Java Server Pages (JSP) to render the view, Servlet as the controller, and Enterprise JavaBeans (EJB) components as the model.
- For Centralized controller, a main servlet is used to make control more manageable.
Posted by
Sunflower
at
4/16/2011 03:14:00 PM
0
comments
Labels: Controller, Data, Design Pattern, Devices, Doamin, Information, Inputs, Interfaces, Model View Controller, Multiple, MVC, Outputs, Pattern, View
|
| Subscribe by Email |
|
Thursday, March 24, 2011
Overview of Aspect Oriented Software Development (AOSD)
Aspect oriented software development defines aspects that express customer concerns that cut across multiple system functions, features, and information. It provides a process and methodological approach for defining, specifying, designing, and constructing aspects - mechanisms beyond subroutines and inheritance for localizing the expression of a crosscutting concern.
Aspect Oriented Programming (AOP) provides the ability to intercept code execution with the purpose of inserting a process before, in place of, or after the code that would normally execute.
Predominant reasons for AOSD are:
- Help solve the issue of messy object architectures.
- Object oriented programming has difficulty dealing with global information.
- Also, functionality that requires the involvement of several different objects (possibly collected into a component) results in interdependency between those objects/components. This makes the application susceptible to the implementation changes of a dependent object/component.
- Maintenance and enhancement are also problems, as the interaction between these objects/components are typically hard coded within the containing object.
AOSD programming technologies (aspect-oriented programming, or AOP) provide linguistic mechanisms for separate expression of concerns, along with implementation technologies for weaving these separate concerns into working systems. Aspect-oriented software engineering (AOSE) technologies are emerging for managing the process of developing systems within this new paradigm.
Posted by
Sunflower
at
3/24/2011 01:53:00 PM
0
comments
Labels: AOSD, Approach, Aspect Oriented Software Development, Aspects, Code, Cross Cutting, Customer, Define, Development, Functionality, Functions, Multiple, Objects, Quality, Reasons, Software
|
| Subscribe by Email |
|