Submit Articles A Collection of Informative and Interesting Articles  

Qualities of a Good Software Engineer

BY: Mano Johnson | Category: Technology | Submitted: 2010-07-24 13:21:22
       No Photo
Article Summary: "Programmers need to do their best to be successful. The software programmer should have knowledge of the software areas to be used in the project..."

Share with Facebook Share with Linkedin Share with Twitter Share with Pinterest Email this article

The software programmer should have knowledge of the software areas to be used in the project. The software areas include system software, business software, real time software. Those who have software responsibility are under immense pressure to have accounts, use budgets, stick to schedules from being missed and improve quality. It is essential to use the Computer aided software engineering tools. It must be understood that software development is not a mechanistic process like manufacturing. Once this is understood, then it will be easy for the progress.


Project requirements continuously change but the change must be easily accommodated. It is true that software requirements change, but the impact of change varies with time to time at which it is introduced. It is essential to give serious attention to up front definition, early requests for change must be accommodated easily. The customer can review requirements and recommend modifications with relatively little impact on cost. When changes are requested during software design, the cost impact increases rapidly.

Need for change

Changes in function, performance, interface and other characteristics during implementation of code and test have effect on cost. Changes when requested after software is in production can be expensive than the same change requested earlier. A working program is only one part of software configuration that includes many elements. The proper documentation provides a foundation for successful engineering and guidance for the software support. Better quality leads to reduced rework. And reduced rework results in faster delivery times. The methods for poor management and technical practices should be avoided.

While designing the software, programmer must consider the following points.

• What is the problem needed to be solved?
• What characteristics are used to solve the problem?
• How will the solution be realized?
• What approach will be used to uncover errors that were made in the design and construction of the entity?
• How will be the entity be supported over the long term?

During definition, the software engineer attempts to identify what information to be processed, what function and performance are desired. In order to understand the nature of the program to be built, the software engineer must understand the information domain for the software.

Requirements for both the systems and the software are documented and reviewed with the customer. In code generation, the design must be translated into machine readable form. If design is performed in detailed manner, code generation can be accomplished mechanistically. The programmer must follow the testing strategies ensuring all statements have been tested. The tests are needed to uncover errors and ensure that defined input will produce actual results that agree with required results.

The programmer should notice that there will be change in software due to change in environment after it is delivered to the customer. Change will occur because errors may encountered, because the software must be adapted to accommodate changes in environment. The support and maintenance chart of manual instruction should be printed and provided to the user with the hard copy of the software.

About Author / Additional Info:

Comments on this article: (0 comments so far)

Comment Comment By Comment Date

Leave a Comment   |   Article Views: 6878

Additional Articles:
•   Briggs Family

•   Characteristic of Caveat Loans

•   In Mom's World

•   How to Keep Critters Out of Your Garden

Latest Articles in "Technology" category:
•   Security Robots on Patrol

•   Apple Pay Overview

•   Enterprise Mobility - Overview Part 1

•   M-OTA: Mobile 'Over-The- Air' (OTA) Overview

•   MDM: Mobile Device Management Overview

•   3M MAC Protocol Review

•   Build, Deploy and Test - Advanced Software Development Practice - Part 1

Important Disclaimer: All articles on this website are for general information only and is not a professional or experts advice. We do not own any responsibility for correctness or authenticity of the information presented in this article, or any loss or injury resulting from it. We do not endorse these articles, we are neither affiliated with the authors of these articles nor responsible for their content. Please see our disclaimer section for complete terms.
Page copy protected against web site content infringement by Copyscape
Copyright © 2010 - Do not copy articles from this website.
| Home | Disclaimer | Xhtml |