- To
validate the system partially i.e. to determine if the system under
consideration fulfills the portability requirements and can be ported to environments
with different :-
Friday, September 13, 2013
What is Portability Testing?
Posted by
Sunflower
at
9/13/2013 06:42:00 PM
0
comments
Labels: Application, Code, Components, Conditions, Design, Environment, Objectives, Operating System, Platform, Portability Testing, Process, Processor, Re-usable, Requirements, Software, System Testing, Testing
![]() | Subscribe by Email |
|
Wednesday, September 11, 2013
What are transport and application gateways?
Posted by
Sunflower
at
9/11/2013 10:16:00 PM
0
comments
Labels: Acknowledgement, Application, Application gateways, Code, Connection, Design, Destination, Gateways, Layers, Networks, Ports, Protocols, Request, Server, Source, System, TCP/IP, Transport, Transport gateways
![]() | Subscribe by Email |
|
Thursday, August 8, 2013
Flooding - a kind of static algorithm
- Systems that require bridging, systems
like use net.
- Peer to peer file
sharing.
- Used as a part of the
routing protocols such as the DVMRP, OSPF etc.
- Used in protocols used for
the adhoc wireless networks.
- Each node in the network
might act as both receiver and the transmitter.
- The incoming message is
forwarded by the receiving node to each of its neighboring nodes except
the one which is the source code.
Advantages and Disadvantages of Flooding Algorithm
- If it is possible for
delivering the packet, it will be delivered but a number of times.
- In flooding algorithm every
path in the network is naturally utilized and so the shortest path is also
used.
- The implementation of the
flooding algorithm is quite simple.
- The cost of the flooding
algorithm can be very high because a lot of bandwidth is wasted. Even if
there is one destination of the message, it will be sent to all the hosts
on the network unnecessarily. If in case there occurs a denial of service
attack or a ping flood, the reliability of the whole network will be
affected badly.
- In the computer network, the
message might get duplicated. This in turn can increase the load on the bandwidth
of the network. This will call for increasing the complexity of the
processing for rejecting the duplicates of the messages.
- The packets that are
duplicate might keep on circulating forever, if the following precautions
are not taken:
Posted by
Sunflower
at
8/08/2013 11:33:00 PM
0
comments
Labels: Advantages, Algorithms, Application, Code, Design, Destination, Disadvantages, Flooding Algorithm, Graph, Links, Message, Messages, Network, Packets, Routers, Routing, Source, Static, System
![]() | Subscribe by Email |
|
Wednesday, July 17, 2013
What are network layer design issues?
- Services
provided to the layer 4 i.e., the transport layer.
- Implementation
of the services that are connection oriented.
- Store
– and - forward packet switching
- Implementation
of the services that are not connection oriented.
- Comparison
of the data-gram sub-nets and the virtual circuits.
- They
should be independent of the router technology.
- Shielding
from the type, number and topology of the routers must be provided to the
transport layer.
- The
network addresses that are provided to the transport layer must exhibit a
uniform numbering plan irrespective of whether it’s a LAN or a WAN.
Posted by
Sunflower
at
7/17/2013 05:30:00 PM
0
comments
Labels: Communication, Connection, Data, Datagram, Design, Hosts, Issues, Layers, Model, Network, Network layer, OSI, Packets, Processes, Routes, Routing, subnet, Tasks, Transport layer, Virtual Circuits
![]() | Subscribe by Email |
|
Wednesday, June 26, 2013
Encouraging a creative team member to assist in the UI designer duties
- Ask for and get more testers and/or developers, and take on this quantity of work
- Ask for and not get more testers and/or developers, and decline work beyond the amount that can be done with the team that you have
- The third one is the most problematic. The team does not get additional testers or developers, but there is a lot of pressure built to take on the additional work. One would not like to think of such a scenario, but it does happen, and eventually the team either gives up the additional work or takes on a lot of stress, and maybe even has a reduced quality in terms of their deliverable.
However, twice in the past 4 years, we have come across a situation which is not easily solvable, and for which we did not get any additional support. What was this case ? This was the case where the release we were doing had a number of features that required the support of a workflow designer / UI designer. In a typical release, we have a certain number of such resources assigned to the team, based on an expectation that the amount of workflow and UI required will be of a certain % (let us assume that 60% of the work being done by the team needs the support of the workflow / UI team - the reason for it being 60% is that the remaining 40% is where the team does some kind of tweaking / modification which does not require any workflow changes or UI changes).
However, this gets badly affected when there was a release where the estimation of the amount of work where the workflow / UI designer is needed was around 80%, and it was pretty clear that the team that was doing the workflow / UI design was not staffed for this extra work, and even if we had got allocation of budget for the extra work (which was not 100% certain by itself), it takes months to hire somebody with this skill set. Hence, there was no getting around the fact that we had a puzzle on our hands - we had estimated work for which we had enough developers and testers, we did not have enough designers. What to do ?
When we were discussing with the senior members of the team, we came across an interesting suggestion. Over the past, the team had noted that there were some members of the team who were more easily able to comprehend the designs put out by the designer team and understood the way that they were doing their reasoning. Given that we really did not have a choice, we went ahead with the open offer to team members who wanted to give open flow to their creative juices, and prepare the design, with rounds of review by the designer team (we found that this amount of effort could be accommodated), and then present to this team. One of the main persons we expected did not volunteer, but another person who was also seen a prospect volunteered, and we pulled her off her current responsibilities and got her temporarily assigned to the designer team. Over the next few weeks, we did a close watch on this arrangement, and while it was not as good as the design done by the designer team, our Product Manager was satisfied with this, and so was the design team, and we went with the design that she produced and the team accepted. Now, this was not a long term arrangement, but in the scenario described above, it seemed to work.
Posted by
Ashish Agarwal
at
6/26/2013 09:18:00 PM
0
comments
Labels: Design, Designer, Replacement, Shortage of resources, Team member, UI design, Workflow, Workflow design
![]() | Subscribe by Email |
|
Friday, June 21, 2013
Explain about the Paged Memory and Segmentation techniques?
What is Paging?
- Determining the location of
the requested data from the auxiliary storage.
- Obtaining a page frame in
the main memory that is empty to be used for storing the requested data.
- Loading the data requested
in to the empty page obtained above.
- Making updates to the page
table so that new data is only available.
- Returning the control
interrupting program and retrying to execute the same instruction that
caused the fault.
What is Segmentation?
Posted by
Sunflower
at
6/21/2013 08:51:00 PM
0
comments
Labels: Address, Contiguous, Control, Data, Design, Flags, Memory, Modules, Object, Operating System, Page Fault, Paged, Paging, Primary, Secondary, Segmentation, Segments, System, Techniques, Virtual
![]() | 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 |
|
Wednesday, April 17, 2013
What are Real-time operating systems?
- The soft real –time operating system: It
produces more jitter.
- The hard real – time operating system: It
produces less jitter when compared to the previous one.
- Minimal interrupt latency and
- Minimal thread switching latency.
- Time sharing design: As per
this design, the tasks are switched based up on a clocked interrupt and events
at regular intervals. This is also termed as the round robin scheduling.
- Event – driven design: As per
this design, the switching occurs only when some other event demands
higher priority. This is why it is also termed as priority scheduling or
preemptive priority.
- Running or executing on CPU
- Ready to be executed
- Waiting or blocked for some
event
Posted by
Sunflower
at
4/17/2013 07:05:00 PM
0
comments
Labels: Algorithms, Applications, Data, Design, Events, Factors, Features, Hard, Multi-tasking, Operating System, OS, Priority, Process, Real time Operating system, Scheduling, soft, System, Tasks, Throughput, Types
![]() | Subscribe by Email |
|
Friday, March 22, 2013
What is an Artificial Neural Network (ANN)?
- Statistics
- Cognitive
psychology
- Artificial
intelligence
- Computational
neuroscience
- Theoretical
neuroscience
- Supervised
learning
- Un –
supervised learning
- Reinforcement
learning
Posted by
Sunflower
at
3/22/2013 08:39:00 PM
0
comments
Labels: Algorithms, ANN, Application, Approach, Artificial, Artificial Neural Network, Behavior, Design, Elements, Global, Information, Inputs, Network, Neural Networks, Neurons, Outputs, Practical, System, Units
![]() | Subscribe by Email |
|