Thoughts on System Architecture

System:

A system is defined as a set of different elements so connected or related as to perform unique function not performable by the elements alone

Architecture:

The term ‘architecture’ is widely understood and used for what it is – a top down description of the structure of the system

- System Architecture definition by Eb Rechtin

System Architect is one of the crucial jobs in embedded industry and to reach there one should have various skills required apart from solid domain level skills. The essay (link below) by Dr. Koopman covers in detail the core competency required to become System Architect, they are as follows

1. Must have an appreciation for the full breadth of complexity in the lifecycle of a system.

This would require years of experience working in various domains within a system and only then one can appreciate inherent complexities.

2. Must have experience/knowledge of the strengths and weaknesses of various architectural approaches as well as ways to combine them.

This could be learned by knowing various approaches and should know when one can be used in particular system.

3. Must have the ability to cope with significant amounts of complexity while creating or modifying architecture.

This is also very difficult skill to learn, would require working knowledge of various tools and to help deal with complexity.

4. Must be able to articulate the essence of particular system architecture to others.

System Architect role is a of a leader, and excellent communication skills are expected from him. He should sell his vision and idea to the team, customers and all the stakeholders.

5. Must be able to deal with systems that are evolved/composed rather than designed from scratch.

This is important as many of the systems or products are getting evolved, no one is designing everything from scratch.

6. Must have good “taste” to create a “clean” architecture that scales well and ages gracefully in the face of unforeseeable changes.

Sometime the need comes to design entire thing from scratch, and here he has to play a crucial role.

Link:
1. Essay by Dr. Philip Koopman http://www.ece.cmu.edu/~koopman/system_architecture/00_04_system_architecture.pdf

Basic Skills Required

Embedded Systems* is a really huge industry and a very much diversified one too. The application area varies from designing a mobile phone, set top box device to industrial control, robotics etc. and also it requires interdisciplinary skill set for development. The various application areas and skills set for each could be another topic, which I would have in future posts.

For this post, I would limit my self to skills required for a basic Software Engineer in this domain. Similar to kind of job which I am doing in Bangalore for past two years.

Kind of Job profile:
You would be working on a particular product (such as Mobile Phones, Set top box or related to automobiles), and responsible for maintaining, development of various modules in any particular domain. The domain could vary from Telecom, Video, Audio, Drivers, Multimedia or UI development. Initially domain skills are not necessary but over the years you are expected to become master in one particular domain, thus after some time you cannot easily jump over multiple domains.

Companies:
Motorola, Samsung, Qualcomm, STMicro, NXP, LG Software etc. etc. (all in Bangalore)

Basic Skills:
a. Good coding skills in C (or C++): Very good knowledge of C language is good starting point. Suggested books are K&R, Expert C programming etc. Have a good hold on pointers, memory allocations and bit manipulation.

b. Debugging and Problem solving: This is very crucial skill in this domain, as most time is spent debugging other persons code. As an good engineer, you would be having essential skills to start up with.

c. Operating Systems concepts: A basic undergraduate level course would do, better if you know about Real time system and kernels but not mandatory.

d. Computer Architecture: Especially knowledge of any RISC architecture,recommended is to know ARM architecture, as most of the embedded devices use ARM IP in their SOC.

Other Advanced skills required are based upon domain you wish to work, such as Wireless or DSP. For this its better to have understanding of Wireless Communications (mainly protocols) and DSP (Audio and Video).

Thats all for today, in future I wish to write upon detailed job profile, exact skills and how to develop and nurture career in this space.

* When I say Embedded Systems, I restrict myself to developing Embedded Products

Hello world!

embsystems is my new blog, specifically dedicated to perspectives and thoughts on Embedded Systems area. Specifically I want to cover following points,

1. Various application areas

2. List of companies active in this space (I know this is huge, but want to classify and maintain the list)

3. Graduate level education in this space, especially American and European university.

4. Types of job and skills required for it, to give a brief idea to any budding aspirant.

5. My personal experience and learnings working in this field (in past two years).