1. Skills needed to become a Good Software Engineer
Quality to work in a team
Good communication skills
know your field very well
must know c, c++,VB coding languages etc
Must have skills to think in all possible solutions you can provide to your software.
posses good programming skills
Must be able to learn project details given you clearly and accurately
Good analytical skill
Clean programmer
Quality to manage your work so as to finish in given timeline
Aware of new functionalities and technologies used in your platform so as to cop up with new designs

2. Knowledge of software engineering (flowcharting, Data flow
A good software engineer should have an analytical approach for a problem. A good software engineers should have following quality.
A sound thinking so that he/she can provide a quick and better solution for a particular work.
Knowledge of software engineering (flowcharting, Data flow
diagram and designing of an algorithm).
Knowledge of programming languages.
A good communication skill.
More cooperative so that he/she can work in a team.
More curious to learn new techniques for enhancement.

3. Human factors in Software Engineering.
Software engineering is an effort to reduce the cost of producing software by raising programming productivity and lowering maintenance effort and to increase the benefits of software by extending application areas and improving service. Human factors considerations can have a major impact on the software development process and the quality of the software produced. High-level languages have increased programmer productivity by removing from the programmer the burden of remembering what values are in what register and placing it on a software system which is much more suited to managing detail. Other programming methodologies and tools have been developed to reduce the cost of producing software: design methodologies, structured programming, chief programmer teams, disciplined coding conventions, etc.

4. Checklist
It was the goal of this study to develop a basic checklist that could be used by software safety engineers to use from the beginning, throughout the life cycle, and throughout deployment of a project. 
Checklist should provide a better understanding of the safety process. It will provide the ability to determine where in the life-cycle an error occurred. Using a tracking system, previous projects can provide information for new safety projects and intelligent decisions can be made from past experiences.