Wednesday, November 20, 2013

What you should do in Section-B (Avionics) which you don’t know.

I came across many situations where AeSI recent graduates have to walk together with the engineering graduates of Electronics background in order to get selected in an interview. I know it is damn difficult but not impossible. The fact remains the same that many Avionics engineers are working as an Embedded Software/Hardware engineer. Henceforth it is very much essential to learn the basics of various safety, security and mission critical standards, software and hardware. Unfortunately it is not a module of your Section-B syllabus however by spending few hours a week; one can certainly assure that he gets a job after completing his engineering degree.

Case study: I have recently joined a company where it is very much essential to know the basics of reliability, availability, maintainability and safety. I certainly wasn’t aware about these terminologies hence I have started taking advantage of social media. I have downloaded certain videos from YouTube on reliability basics and then I have downloaded couple of white papers about various methods of reliability predictions. No doubt, I wasn’t able to grab all things in one time but I certainly have learned new things. One should always remember that learning is an ongoing process.
I strongly recommend you to learn the basics of following modules before you start job hunting:
  1. Requirements Engineering: Learn the basics of requirements engineering.
  2. Design, Modeling and Simulation basics: You can learn many things at Mathworks website.
  3. You have C, C++ as a module in Microprocessor & Software Engineering subject of Section-A. However getting is the right answer can never make you a good programmer. It is very much essential that you should know the art of writing software code. MISRA – C, C++ can help you in doing the same. There are various technical FAQ and discussion threads available on official website of MISRA.
  4. Basics of Software Testing. Specially modules like static analysis, unit testing, code coverage.
  5. Basics of In Circuit Emulators and hardware debuggers.
  6. Reliability Prediction standards such as MIL-HDBK-217, NPRD 95, etc.  How organizations predict reliability and do impact analysis. Google modules like Fault Tree Analysis, Reliability Block Diagrams, Failure Mode Effect Analysis, etc.
  7. Hardware Debuggers
  8. Basics of compilers, IDE, RTOS, middleware, etc.
I know that being a student, it is very difficult to learn these many things but if you know at least the basics so I am sure that nobody can stop you in getting a good job.

Start asking “W” questions like
What is it?
Why is it used?
What are the methods?
Which companies are the best in each area?
How the knowledge of it can help me in my career?
& many more. 

Happy Learning! Please let us know if you require any additional support or information from our side. You may mail your queries as a comment below. 


Search This Blog