softwarezen.wordpress.com
Software Zen | Page 2
https://softwarezen.wordpress.com/page/2
June 22, 2010. While I will write a set of posts on my experience in turning around projects, I would like to illustrate here how metrics can be used to analyze the depth of the problem and also provide a very quick plan for stabilizing the project very quickly. A simple defect analysis based on the cause of the defects can shed light on what are the key areas that need to be addressed. From → Software Metrics. IT- The Future is Here. June 15, 2010. Anyone remember using these? Read the full article here.
softwarezen.wordpress.com
bhupinder singh | Software Zen
https://softwarezen.wordpress.com/author/readerswords
Posts by bhupinder singh. August 3, 2011. This blog has moved. Subscribe to Software Zen by Email. This blog has moved. Tips and Tricks (6). Ravi Pandey at NIIT. Software Engineering Best Practices. Udayan Banerjee at NIIT. Venkat Karri's SharePoint Blog. Create a free website or blog at WordPress.com. Create a free website or blog at WordPress.com. Follow “Software Zen”. Get every new post delivered to your Inbox. Build a website with WordPress.com.
softwarezen.wordpress.com
Whitepaper on Software Testing Metrics | Software Zen
https://softwarezen.wordpress.com/2011/02/14/whitepaper-on-software-testing-metrics
Whitepaper on Software Testing Metrics. February 14, 2011. You can now download this free whitepaper on Software Testing Metrics. That I wrote some time back. Comments are welcome. From → Software Metrics. Larr; Software Metrics- V. This blog has moved →. Leave a Reply Cancel reply. Enter your comment here. Fill in your details below or click an icon to log in:. Address never made public). You are commenting using your WordPress.com account. ( Log Out. Notify me of new comments via email.
softwarezen.wordpress.com
Estimating Test Effort | Software Zen
https://softwarezen.wordpress.com/2010/07/13/estimating-test-effort
July 13, 2010. One of the best known techniques are the ones provided by Caper Jones and David Longstreet. According to Caper Jones,. Number of test cases = (Count of Function Points) raised to the power of 1.2. David Longstreet provides a similar formula for computing the number of UAT test cases:. Total number of UAT. Test cases, which is = 1.2 x (Count of Function Points). Total Number of test cases = (Function Point Count) raised to the power 1.05. Unit Test Cases : 13,000. System Test Cases : 13,000.
softwarezen.wordpress.com
Managing by Exception | Software Zen
https://softwarezen.wordpress.com/2010/07/08/managing-by-exception
July 8, 2010. As a techie who grew through the ranks, starting as a programmer to project lead to project manager and then a program manager, I have had no management training as such. It came naturally, the learning happened either by burning one’s own hands or by the guidance of a knowledgeable manager. This observation came to my help much later. In my role as a program manager, I had to manage multiple projects- often in multiple technologies and across different types of projects. Leave one →. Even ...
softwarezen.wordpress.com
Software Development is… | Software Zen
https://softwarezen.wordpress.com/2010/07/08/software-development-is
Software Development is…. July 8, 2010. Results of a fun poll that I conducted over at Linkedin. From → Software Engineering. Larr; Reverse Engineering for Software Systems. Managing by Exception →. Leave a Reply Cancel reply. Enter your comment here. Fill in your details below or click an icon to log in:. Address never made public). You are commenting using your WordPress.com account. ( Log Out. You are commenting using your Twitter account. ( Log Out. Notify me of new comments via email.
softwarezen.wordpress.com
Software Metrics- V | Software Zen
https://softwarezen.wordpress.com/2010/07/22/software-metrics-v
July 22, 2010. Here are the definitions of some of the metrics that pertain to software testing. Total Weighted Defects / Size (in Function points or kLOC). Defect Containment Efficiency (%DCE). Total number of weighted defects observed before release * 100 / (Total weighted defects reported before release Total weighted defects reported after release). Average Defect Age (ADA). Sum of Defect ages of all defects / Total number of defects. Effort Spent on Rework / Total Effort. Measure of redundant effort.
softwarezen.wordpress.com
bhupinder | Software Zen
https://softwarezen.wordpress.com/author/softwarezen
February 14, 2011. Whitepaper on Software Testing Metrics. July 22, 2010. July 13, 2010. July 8, 2010. July 8, 2010. Software Development is…. June 30, 2010. Reverse Engineering for Software Systems. June 22, 2010. Laquo; Older Entries. Subscribe to Software Zen by Email. This blog has moved. Tips and Tricks (6). Ravi Pandey at NIIT. Software Engineering Best Practices. Udayan Banerjee at NIIT. Venkat Karri's SharePoint Blog. Blog at WordPress.com. Create a free website or blog at WordPress.com.
softwarezen.wordpress.com
This blog has moved | Software Zen
https://softwarezen.wordpress.com/2011/08/03/this-blog-has-moved
This blog has moved. August 3, 2011. To Bhupinder Singh’s Blog on Software Engineering. From → Uncategorized. Larr; Whitepaper on Software Testing Metrics. Leave a Reply Cancel reply. Enter your comment here. Fill in your details below or click an icon to log in:. Address never made public). You are commenting using your WordPress.com account. ( Log Out. You are commenting using your Twitter account. ( Log Out. You are commenting using your Facebook account. ( Log Out. Notify me of new comments via email.
softwarezen.wordpress.com
Reverse Engineering for Software Systems | Software Zen
https://softwarezen.wordpress.com/2010/06/30/reverse-engineering-for-software-systems
Reverse Engineering for Software Systems. June 30, 2010. In its most rudimentary form, reverse engineering can be defined as “going backwards through the development cycle”. It has its origins in espionage when rival countries would break apart a product from the opposite country and figure out its mechanism in order to build a similar product. Wikipedia defines reverse engineering. The major challenges I see with reverse engineering are:. Even if the source code is readable, it may be dependent on hard ...