These algorithms have been classified in to two major types:
- Non
– adaptive or static algorithms
- Adaptive
or dynamic algorithms
Articles, comments, queries about the processes of Software Product Development, Software Testing Tutorial, Software Processes .
Posted by
Sunflower
at
8/05/2013 08:27:00 PM
0
comments
Labels: Algorithm, Application, Communication, Cost, Data, Efficiency, Input, Link, Network, Nodes, Optimal, Optimality Principle, Principle, Process, Router, Routes, Routing, States, Techniques, Transmit
|
| Subscribe by Email |
|
Posted by
Sunflower
at
5/14/2013 05:02:00 PM
0
comments
Labels: Application, Communicate, computers, Concurrent, Distributed system, Features, Goals, Memory, Networks, Parallel, Principle, Process, Programming, Resources, System, Tasks, User
|
| Subscribe by Email |
|
Posted by
Sunflower
at
4/28/2013 10:13:00 PM
0
comments
Labels: Algorithms, Allocation, Chunk, CPU, Data, External, Fragmentation, Inefficient, Internal, Memory, Performance, Principle, program, Space, Storage, System, Types, Wastage
|
| Subscribe by Email |
|
Posted by
Sunflower
at
6/19/2012 03:15:00 PM
0
comments
Labels: Application, CBSE, CBSE process, Component, Component based development, Component based Software Engineering, Coordination, Data, Functionality, Functions, Interface, Principle, Software Components, Steps
|
| Subscribe by Email |
|
Posted by
Sunflower
at
5/02/2012 11:30:00 PM
0
comments
Labels: Benefits, Concepts, Cost, efficient, Features, Integration, Models, Open Source Test Case Management Tool, Peers, Principle, Purpose, Requirements, Software testing, STLC, Test cases, Test Scripts, TestLink, Time, Tool
|
| Subscribe by Email |
|
Ad hoc testing as the name suggests is the testing that is carried out without any formal planning and formal documentation though it can be used for scientific experimental studies.
- The ad hoc testing is meant to be carried out only once until and unless a defect is found.
- It would not be wrong if we call the least formal methodology of testing a software application or system.
- It has always been under criticism because of its uneven structure and also because the defects discovered through this kind of testing are difficult to reproduce due to a lack of written test cases.
However, there is still a plus point of ad hoc testing as important defects or bugs can be found quickly and easily without much efforts and pre planning.
Principle of Ad-hoc testing
The ad hoc testing is based on the principle of improvisation i.e., the software testers seek to find the errors and bugs by any means that seems appropriate to him/ her or we can say tests are performed according to the convenience of the tester.
Ad hoc testing can be appropriately called a primitive version of error guessing which itself is an un- sophisticated version of exploratory testing.
- Formal testing is carried out without any test cases and it proves to be a great help in deciding the duration and scopes for the other types of testing that have to be carried out upon the software system or application.
- This also helps the tester to learn more and more about the software system or application prior carrying out the other kinds of testing.
- It can be called as the least formal method of testing.
- The quick discovery of defects is the best use of ad hoc testing.
- Only reading the specifications and requirements doesn’t give a good sense of how the program or the software system or the application actually works and behaves.
- Even the documentation of the testings does not provide the feel of the software system or application.
- Ad hoc testing can be effectively used to find discrepancies in the testing strategies of the tester and the relations between the sub- systems of the software can be explored that would have been left un- exposed.
- In a way we can say that it serves a tool for checking the quality of our testing methodology.
- It helps in finding the missing cases and so these can be added to the list of test cases.
- Discovering new test cases with ad hoc testing is an indication that root cause analysis should also be performed.
While carrying out the ad hoc testing you should ask yourself and your team members “what other tests should we need to carry out in order to supplement this and make testing more effective?”
SOME IMPORTANT FACTS
- Defects or errors found during ad hoc testing provide examples of forgotten test cases.
- Determining the priority for carrying out other testing can also be thought as another use of ad hoc testing.
- For example, if a program allows the user to carry out some task and the ad hoc testing shows that this function works well, then the formal testing of this functionality might be postponed until the areas having problems are completed.
- On the other hand, if the ad hoc testing discovers any problem, then the formal testing for this functionality can be given highest priority.
- It is concerned with application testing without taking into considerations any rules and regulations.
- For carrying out ad hoc testing effectively the tester should have strong knowledge of the software system or application. Ad hoc testing is performed mainly to save time.
Posted by
Sunflower
at
1/15/2012 08:58:00 PM
0
comments
Labels: Ad hoc testing, Ad-hoc, Advantages, Application, Approach, Bugs, Compliance tests, Defect, Defects, Demerits, Errors, Formal methods, Merits, Methodology, Principle, Software testing, Test cases
|
| Subscribe by Email |
|
Barry Bohem suggested an approach that addresses project objectives, milestones and schedules, responsibilities, management and technical approaches and required resources. This is called W5HH principle. The questions that are answered in this principle are:
- Why is the system being developed?
- What will be done by When?
- Who is responsible for a function?
- Where are they organizationally located?
- How will the job be done technically and managerially?
- How much of each resource is needed?
WHY IS THE SYSTEM BEING DEVELOPED?
It enables the parties to assess the validity of business reasons for the software work. It justifies the expenditure of people, time, and money.
WHAT WILL BE DONE?
It specifies the task set required for the project.
WHEN WILL IT BE DONE?
It helps to determine the project schedule. It helps in determining when tasks are conducted and when milestones are reached.
WHO IS RESPONSIBLE FOR A FUNCTION?
It helps to accomplish the role and responsibilities of each member of the software team.
WHERE ARE THEY ORGANIZATIONALLY LOCATED?
The software team does not contain all the roles and responsibilities. The customers, users and stakeholders also have responsibilities.
HOW WILL THE JOB BE DONE TECHNICALLY AND MANAGERIALLY?
The management and technical strategy of project is defined once the scope of the product is established.
HOW MUCH OF EACH RESOURCE IS NEEDED?
It helps in deriving estimates based on the answers to the above questions.
Posted by
Sunflower
at
1/15/2011 10:32:00 PM
0
comments
Labels: Approach, Development, Functions, Location, Organization, Principle, Project, Project Management, Resources, Software, software engineering, Task set, Tasks, Technically, validity, W5HH principle
|
| Subscribe by Email |
|
A hub connects multiple devices together. Ethernet hubs, and are most commonly used in computers for networking purposes. Ethernet hubs are available in different types, depending on the speed of the network connection or broadband speed. The number of ports an Ethernet hub supports also varies. Older Ethernet hubs were relatively large in size and sometimes noisy as they contained built in fans for cooling the unit. Newer devices are much smaller, designed for mobility, and noiseless.
Posted by
Sunflower
at
3/02/2010 03:08:00 PM
0
comments
Labels: Bus network, computers, Ethernet hubs, Hardware, Hardware Components, Hubs, Multiple Devices, Networking concepts, Operating Systems, Principle, Purpose
|
| Subscribe by Email |
|