não perca essa oportunidade de fazer um mini curso sobre sistemas embarcados. Começa na semana que vem.
consulte sempre um engenheiro eletrônico
- February 24 – Day 1: Introduction to the Embedded Software Design Cycle – This session will introduce what the embedded software design cycle is and why an engineer would want to follow the cycle. The session will also look at requirements in detail ‒ what a requirement is, how to solicit them, and how to track and maintain them. Tools and examples will be provided so that this first critical step in the design cycle may be executed flawlessly.
- February 25 – Day 2: Software Design Principles – This session will present concepts on how to design embedded software. It will start with a look at how to take requirements and develop a software architecture that meets those requirements. A brief look at available modeling tools such as UML will be examined. Techniques and design strategies such as structured and object-oriented design will be discussed.
- February 26 – Day 3: Implementation Strategies – This session will dig into the details of writing embedded software. The fundamentals will be discussed and include how to minimize complexity and anticipate change. Constructing for verification and design patterns will be explored. Techniques for writing the software will be covered, including design for reuse, modularity, and quality.
- February 27 – Day 4: Testing Your Way to Success – As much fun as designing and implementing software can be, at some point it must be proven that it meets requirements and does what it’s supposed to without any bugs! This session will cover software testing fundamentals. The difference between a fault and a failure will be explored in addition to testing effectiveness and objectives. Different levels of testing such as unit, integration, and system testing will be discussed.
- February 28 – Day 5: The Wonderful World of Software Maintenance – The software design cycle doesn’t end with the successful launch of the product. It simply marks the entry to the next stage of the cycle, which is to maintain the software. Over time, user expectations and needs change, and the software needs to be updated to continue to meet the users’ needs. This session explores this often neglected portion of the design cycle.