Better Software Articles
The team is the basic design unit for software engineering processes. Within the team, reviewers can learn without having to admit to ignorance, and their learning is always relevant to the team's tasks. When there are multiple eyes, there are many more chances to see a fault. Learn how to create and get the most from your team.
Appreciating differences is critical for productive teams. Different approaches aid in finding solutions, and mutual respect dramatically improves group problem solving. Testers should not be judged according to developer criteria.
Why would you want to get published? Why take time out from doing real work to share your thoughts with others? After all, didn't we gladly leave writing behind when we got out of school? But when you share your experiences, you play a part in a larger picture, leaving your mark on the world, and advancing your field.
The explosion of personal information on the Web has made privacy a primary concern. Here are pointers on making sure your site works for security-conscious users, as well as information to help you avoid inadvertent compromises of privacy.
Taking development and business contexts into consideration can mean the difference between a correct assessment and a useful assessment. Here's information on how to provide an assessment that's both correct and effective.
The communication storm front is a real phenomenon that crops up in all development teams and in all organizations. You need not be the victim of such storms. You, as development manager, have the tools to reduce the power of the storm front and create a team that is ever more effective and efficient.
Developing software to meet users' specific needs can be a difficult task. Verification and validation activities can help ensure that you are building the right software right.
It doesn't matter when you deliver, if you build the wrong product. Development entails inferences and assumptions about the user, which are supposed to guide the build-process. However, even if development successfully matches the inferences and assumptions about the user, if those criteria don't match the Real User, the product fails. This article talks about how to incorporate the user into the requirements and design phase.
Test coverage is about insuring that test plans and test cases include information vital for successful testing of the program in the areas of functionality, performance, and the overall quality of the software. This article shows how to create a plan of attack to provide strong test coverage, determine the scenarios for the test plan, and manage the changes made to information used by testing.
The assumptions you make about the people you manage can shape your management style. Here's a detailed look at three distinct styles of management and how they apply to your software projects.