Posts Tagged ‘interview’
April 8th, 2010 | 
Author: 
Official findings of the autopsy
1. The Bethesda autopsy physicians attempted to probe the bullet hole in the base of Kennedy’s neck above the scapula, but were unsuccessful as it passed through neck strap muscle. They did not perform a full dissection or persist in tracking, as throughout the autopsy, they were unaware of the exit wound at about the same level, at the front of the throat. Emergency room physicians had obliterated it when they performed the tracheotomy.
2. At Bethesda, the autopsy report of the president, Warren Exhibit CE 387 described the back wound as being oval, 6 x 4 mm, and located “above the upper border of the scapula” [shoulder blade] at a location 14 cm (5.5 in) from the tip of the right acromion process, and 14 cm (5.5 in) below the right mastoid process (the boney prominence behind the ear).
3. The concluding page of the Bethesda autopsy report, states: “The other missile [the bullet to the back] entered the right superior posterior thorax above the scapula, and traversed the soft tissues of the supra-scapular and the supra-clavicular portions of the base of the right side of the neck.
4. The report also reported contusion (bruise) of the apex (top tip) of the right lung in the region where it rises above the clavicle, and noted that although the apex of the right lung and the parietal pleural membrane over it had been bruised, they were not penetrated, indicating passage of a missile close to them, but above them.
The report noted that the thoracic cavity was not penetrated.
5. This missile produced contusions of the right apical parietal pleura and of the apical portion of the right upper lobe of the lung. The missile contused the strap muscles of the right side of the neck, damaged the trachea, and made its exit through the anterior surface of the neck.”
6. The single bullet theory of the Warren Commission Report places a bullet wound at the sixth cervical vertebra of the vertebral column, which is consistent with 5.5 inches (14 cm) below the ear. The Warren Report itself does not conclude bullet entry at the sixth cervical vertebra, but this conclusion was made in a 1979 report on the Kennedy assassination by the House Select Committee on Assassinations (HSCA), which noted a defect in the C6 vertebra in the Bethesda X-rays, which the Bethesda autopsy physicians had missed and did not note.
Even without this information, the original Bethesda autopsy report, included in the Warren Commission report, concluded that this bullet had passed entirely through the president’s neck, from a level over the top of the scapula and lung (and the parietal pleura over the top of the lung), and through the lower throat.
Claims that anyone on the commission “moved the wound” are subject to discussion, because Gerald Ford publicly admitted to re-naming the location of the wound, so as “to make things clearer”. The Bethesda autopsy had merely noted that JFK was hit in the upper thorax above the scapula (this is in the soft area at the top of the shoulder) and Ford changed this to “the base of the neck”
7. The Commission report, as amended by Ford, then found the bullet to have passed through the base of the neck, and not to have been in the back. However, Ford’s change is consistent with a bullet hit in the shoulder at the C6 vertebral body, where the HSCA and the photograph placed the wound on the basis of X-damage of the vertebrae and tiny lead fragments in that location. The neck formally begins (and thorax ends) at the level of C7, the first cervical vertebral body above the thorax, and thus the original autopsy report is technically in error.
1. The wound to the back of the head is described by the Bethesda autopsy as being a laceration measuring 15 x 6 mm, situated to the right and slightly above the external occipital protuberance. In the underlying bone is a corresponding wound through the skull showing beveling (a cone-shaped widening) of the margins of the bone when viewed from the interior of the skull.
2. The large, irregularly shaped defect in the right side of the head (chiefly to the parietal bone, but also involving the temporal and occipital regions) is described as being about 13 cm (5 inches) wide at the largest diameter.
3. Three fragments of skull bone were received as separate specimens, roughly corresponding to the dimensions of the large defect. In the largest of the fragments is a portion of the perimeter of a roughly circular wound presumably of exit, exhibiting beveling of the exterior of the bone, and measuring about 2.5 to 3.0 cm in diameter. X-rays revealed minute particles of metal in the bone at this margin.
4. Minute fragments of the projectile were found by X-ray along a path from the rear wound to the parietal area defect.
Duration : 0:8:51
Posted in defect tracking software | 
Tags: articles, Assassination, conference, Groden, gunman, harvey, head, Hospital, images, interview, Jama, JFK, JFK's, journal, Kennedy, Kennedy's, later, Lattimer, Lee, limousine, Livingstone, lone, Lundberg, Malcolm, Mannlicher-Carcano, motorcade, observed, occipital, Oswald, Parkland, pathologists, Perry, physicians, Posner, posterior, President, President's, press, published, re-enactment, rear, rifle, Robert, scientific, Secret, seen, service, theory | 
14 Comments »
We recently had a chance to sit down with TeamSupport CEO Robert Johnson for a discussion of their very interesting product. TeamSupport is both a help desk and bug tracking system which allows technology companies to integrate the customer service and product development teams.
As you’ll hear, TeamSupport is passionate about their product and the role it can play in helping technology companies better support their customers.
Duration : 0:3:46
Posted in bug tracking system |
Tags: bug tracker, bug tracking, help desk, interview, TeamSupport |
No Comments »
http://www.softwaretestingvideos.com/blog/
“Visit for FREE complete video training”
Get Software Testing Jobs just watching these Videos
As testers, we all agree to the fact that the basic aim of the Tester is to decipher bugs. Whenever a build appears for testing, the primary objective is to find out as many bugs as possible from every corner of the application. To accomplish this task as perfection, we perform testing from various perspectives. We strain the application before us through various kinds of strainers like boundary value analysis, validation checks, verification checks, GUI, interoperability, integration tests, functional — business concepts checking, backend testing (like using SQL commands into db or injections), security tests, and many more. This makes us to drill deep into the application as well as the business.
Duration : 0:7:50
http://www.softwaretestingvideos.com/blog/
“Visit for FREE complete video training”
Get Software Testing Jobs just watching these Videos
System Testing is conducted on a complete, integrated system to evaluate the system’s complain with its specified requirements. It should require no knowledge of the inner design of the code or logic. It is performed on the entire system.
Steps for Effective System Testing:
1)Test Coverage
2)Defect Tracking
3)Test Execution
4)Build Process Automation
5)Test Automation
6)Documentation
Duration : 0:6:18
http://www.softwaretestingvideos.com/blog/
“Visit for FREE complete video training”
Get Software Testing Jobs just watching these Videos
Integration Testing is the phase of software testing in which individual software modules are combined and tested as a group. The purpose of this testing is to verify functional, performance and reliability of the product.
Steps for Effective Integration Testing:
1)Software Configuration Management
2)Automate Build Process where necessary
3)Document
4)Defect Tracking
Duration : 0:5:45
http://www.softwaretestingvideos.com/blog/
“Visit for FREE complete video training”
Get Software Testing Jobs just watching these Videos
If a piece of Software is modified for any reason testing needs to be done to ensure that it works as specified and that it has not negatively impacted any functionality that it offered previously. This is known as Regression Testing.
Steps for Effective Regression Testing:
1)Test Automation
2)Selective Testing
3)Defect Tracking
Duration : 0:4:34
http://www.softwaretestingvideos.com/blog/
“Visit for FREE Complete Video Training”
Get Software testing Jobs just watching these Videos.Bug life cycle helps you understand the whole process involved in defect reporting.Testers are hired to find bugs & you need to know what happens when a bug in a software application is found.
In software development process, the bug has a life cycle. The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows:
The different states of a bug can be summarized as follows:
1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed
Description of Various Stages:
1. New: When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet approved.
2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”.
3. Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.
4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It specifies that the bug has been fixed and is released to testing team.
5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.
6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “REJECTED”.
7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.
8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “VERIFIED”.
9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “REOPENED”. The bug traverses the life cycle once again.
10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “CLOSED”. This state means that the bug is fixed, tested and approved.
While defect prevention is much more effective and efficient in reducing the number of defects, most organization conducts defect discovery and removal. Discovering and removing defects is an expensive and inefficient process. It is much more efficient for an organization to conduct activities that prevent defects.
Guidelines on deciding the Severity of Bug:
Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects.
A sample guideline for assignment of Priority Levels during the product test phase includes:
1. Critical / Show Stopper — An item that prevents further testing of the product or function under test can be classified as Critical Bug. No workaround is possible for such bugs. Examples of this include a missing menu option or security permission required to access a function under test.
2. Major / High — A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Bug. The workaround can be provided for such bugs. Examples of this include inaccurate calculations; the wrong field being updated, etc.
3. Average / Medium — The defects which do not conform to standards and conventions can be classified as Medium Bugs. Easy workarounds exists to achieve functionality objectives. Examples include matching visual and text links which lead to different end points.
4. Minor / Low — Cosmetic defects which does not affect the functionality of the system can be classified as Minor Bugs.
Duration : 0:2:41