|
Written by Edvin Eshagh
|
How long should a software module be? How many lines of code should a file have? These are some of the questions that my colleague and I were discussing regarding software engineering practices; and I thought it was worth posting. In our dialog, I mentioned that a module size, in general, should not exceed 200-400 lines of codes. If you count comments and white spaces, you can probably double this number. In this posting I will share with you why I think a module size should not exceed 400-800 lines (including comments and whitespace), and why a file should not exceed 4000 lines of code. |
|
Read more...
|
|
|
Written by Edvin Eshagh
|
|
C# .NET follows different coding conventions than Java. For example, .NET interface names are prefixed with the letter "I", whereas in java libraries the prefix is not used. |
|
Read more...
|
|
Written by Edvin Eshagh
|
|
IEEE 829 defines a systematic approach for software testing, which result in effective testing (test plans, test design, test cases, test procedures, better coverage), effective follow-up to track and minimize rework, Reuse documented test cases/procedures by other personal, and proof that testing was conducted to reach a quality level.
|
|
Read more...
|
|
|
Written by Edvin Eshagh
|
|
There are many types of software testing strategies; thus, organizations must be selective in determining which testing strategy meets their need. Below outlines over 30 different software testing strategies, which by no means is comprehensive. |
|
Read more...
|
|
Written by Edvin Eshagh
|
|
Both Black-Box and White-Box software testing strategies have their strength and weaknesses. Each requires specific implementation strategy to maximize testing efforts. |
|
Read more...
|
|
|
|
|
<< Start < Prev 1 2 3 4 Next > End >>
|
|
Page 1 of 4 |