September 20th, 2017
Are you a requirements engineer but your main goal is to provide well organized documentation? Do you have a great knowledge about the industry, business analysis and systems but you are struggling with the shape and look of your documentation? Do you still hear, for instance, that the specification document is not easy to read and difficult to use?
Requirements are the starting point of all other activities in a project lifecycle. So the specification document is crucial for the project. The document has many audiences such us stakeholders, designers, verification engineers and other groups involved in the project. This forces the author of the document to take care of the structure and organization of the document. It is not a big deal to prepare such a document. The problem is that the document has to be modified many times. The requirements are constantly changing, with new features appearing, some being modified and some being removed. Reclassification and reorganization must be repeated many times. In which case, I am pretty sure you will be contending with issues such as auto numbering, indentation, paragraph styles as well as tables and drawings that just do not fit the page.
Another kind of trouble comes from collaboration. Requirements should be developed by more than one engineer but working together on the same document is really a challenge. Forgetting to enable Track Changes, using the wrong version of a document or even using different version of Office tools are the most common collaboration issues.
Finally, there may be a situation in which you focus on a document’s structure and aesthetics more than its content. In the end your document may be well prepared but there is a serious risk that the requirements will be ambiguous, incomplete and/or inconsistent. This can happen when huge amounts of energy are spent solely on keeping the document organized and current. For the rest of this article, visit the Aldec Design and Verification Blog.
What about embedded Linux?
September 18, 2017 by Colin Walls
Somebody asked me: “What is the plural of Linux?” Maybe it is Linuxes. That sounds a bit messy, which seems rather appropriate really…
Prakash Narain is a long-standing member of the EDA community, having helped found Real Intent in 1999. In August 2016, I interviewed Dr. Narain at length about the technology at the core of the company. This week we spoke again, starting with an update of the company’s announcements around DAC in June, which involve further advancements in clock-domain crossing analysis and sign-off.
Real Intent must be doing something right, because Narain seems as enthused about the prospects for his company as someone who has just launched a tech start-up. It takes stamina and courage to sustain that optimism, and market success. Narain says his organization has both.
In a unique new partnership between the ESD Alliance and San Jose State University, SJSU alum and legendary EDA VC Jim Hogan will be speaking on campus this coming Wednesday evening, September 20th, at 7:00 pm.
Hogan’s topic is revolutionary, the Cognitive Era, and the official message behind his talk is all things bright and beautiful:
“Cognitive science is a diverse field which is unified and motivated by a single basic inquiry: How does my education, career and life change in the Cognitive Era? How do people, animals or computers ‘think,’ act and learn? To understand the mind and brain, cognitive science brings together methods and discoveries from neuroscience, psychology, linguistics, philosophy and data/computer science.”
The unofficial message, however, ain’t so cheery. That’s because we already know how people think, act and learn. They do it all around us all the time, and so do we. We don’t need the sciences of neurology, psychology, linguology, philology, or digital-ology to explain it to us.
What we do need is for those disciplines to protect us from all that science and engineering has produced, the stuff that’s now overwhelming our sense of wholeness and health, sanity and serenity.
Imagine traveling back in the time to the early human ages. It’s going to be both scary and interesting when you meet a person who probably cannot speak or if they do you won’t be able to understand them. Clearly, communication will not be possible until you find a mutual way to convey your respective meanings/intentions. The same principle applies in the world of electronics as there are various types of interfaces among electronic devices. Therefore, a standard communication protocol eases the transformation of data in a system, especially in a System-on-Chip (SoC) system which consists of different systems.
SoC FPGAs such as Xilinx® Zynq™ establishes the ARM Advanced Microcontroller Bus Architecture (AMBA) as the on-chip interconnection standard to connect and manage the functional blocks within the SoC design. The Advanced eXtensible Interface (AXI) is designed for FPGAs based on AMBA as a protocol for communication between blocks of IP.
You are registered as: [firstname.lastname@example.org].
CafeNews is a service for EDA professionals. EDACafe.com respects your online time and Internet privacy. Edit or Change my newsletter's profile details. Unsubscribe me from this newsletter.
Copyright © 2017, Internet Business Systems, Inc. — 25 North 14th Steet, Suite 710 San Jose, CA 95112 — +1 (408) 882-6554 — All rights reserved.