Quality doesn’t happen by accident. It is an intentional process. So how do you obtain quality software?

Using Software Engineering Methods – you need to have a reasonably complete understanding of the problem as well as a comprehensive design to be able to solve that problem.

A project manager must use good project management skills to estimate completion, schedule dependencies, and use risk management to ensure backup plans will work for the system.

You should use quality control and assurance to verify your models and make sure the infrastructure is in place to solve the problems.

Achieving Software Quality was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

Review Techniques

ByWalter Wimberly

Within the context of the software development, the terms defect and fault are synonymous. Both imply a problem that is discovered after the software has been released to end users. The book makes a distinction between error – a problem found before being released to the end user and defect or fault. However, in the real world,…

Component Level Design

ByWalter Wimberly

Component-level design occurs after the first iteration of architectural design has been completed. At this stage, the overall data and program structure of the software has been established. A component is defined in UML as: “a modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces.” However, different…