development

Articles

Information Technology Predictions for 2013

While 2013 may appear calmer compared to 2012 due in part to fewer “big” events scheduled this year, the information technology (IT) industry and profession advances forward. The IT industry, interestingly enough, shapes events in addition to being shaped by events around the world.

James Sullivan
Designing Products for Users in Context

When designing software, you must look beyond simply knowing the goals of your users. It's far more useful to understand the context in which the product will be used.

Scott Sehlhorst's picture Scott Sehlhorst
Continuous Integration and the Automated Database Update Process

Developers must have good feedback to ensure productivity. Most shops have a continuous integration (CI) build process that allows the developer to quickly know if a build failed, and some shops have an automatic deploy of the CI build to provide website feedback. Lance Lyons writes about an approach to automating the update of databases in a CI environment.

Lance Lyons
Real-Time Problem Detection in Software Development

Designing and developing software, it's usually cheaper to prevent problems from ever occurring (by making a decision at design-time) rather than patching them as they happen. But detecting problems in real-time is a useful skill in many professions, including one as different as recording audio books.

Daniel Wellman's picture Daniel Wellman
How to Survive a Software Rewrite

Beware of the hidden sirens in your rewrite project. They will sing the words you want to hear--that the project is easy to complete. Don't be fooled: Sirens are mythological, but the lure of rewrite projects can be quite real. Rewrite may seem a simple task, but it isn't until you're deep into it that you'll start to realize the true nature of the project. In this article, James Shore offers some words of wisdom (and warning) to help guide your rewrite project in the right direction.

James Shore
The Definition of "Done" in Software Development

Getting all of the necessary people together to define what "done" means in a software development project will be difficult. Facilitating such a task will probably be a challenge, but there is nothing like working in an organization that works like a well-oiled machine, where everyone knows what is expected of him or her and just naturally does it.

Alan S. Koch
Software Development : How Good It Can Be

This article is dedicated to telling you how good developing software can be. Austin Hastings describes many software development practices working together, some of which you don't have. If you like an idea you see here, implement it. After your first implementation steps, you can return here to find yet another idea to implement.

Austin Hastings
Structure Marking

Structure marking is a programming technique that defends data against damage, especially from software bugs. It adds flags to data structures and checks them at each use to detect damaged data immediately.

Tom Van Vleck
Design and Code Inspection Metrics

In this study, historical inspection data from large real-time embedded systems were analyzed with the intention of improving the current review process.

Alison A. Gately's picture Alison A. Gately
The Future of Code Coverage Tools

Modern optimizing compilers  are becoming increasingly dependent on dynamic profile information. Because the profile information collected by these compilers also is sufficient for QA, it is likely that code-coverage analysis will become an integrated development environment option. This integration should help to simplify your code development and testing processes and should also improve the accuracy of your coverage information and the performance of your optimized code.

David  Sehr's picture David Sehr

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.