ASIC_intl,
I am an ASIC/FPGA verification person. I view everything from a spec. As in, I test to ensure the specification(s) are met functionally.
"1. Does a specification mean to describe all the pins of the SOC or IP? Does it mean something else?"
The requirements document for an ASIC, or specification, needs to detail all functionality. For a SOC design, you would describe as much detail as you can. This could extend down into the register set, IP reuse details, power requirements, frequency requirements, physical pin requirements, detailed bus interface protocol descriptions, references to other specs for standard interfaces, functional requirements imposed by software, algrithmic requirements ..... Everything and anything that enables the functionality to be created and verified is what goes into a spec.
"2. What do you mean by product when you say "In my example product, I would assume there is some electronics between the edge of the box and the ASIC"? Is the product (IP SWITCH) and ASIC same? Is the box here and the product same?"
I have not worked on a device that will be used generically in unknown applicaitons. The designs I have verified have always been part of a larger design. In my example, I am not sure how popular it is to have an Optical interface directly connected to an ASIC. So, there has to be some kind of interface before the ASIC. It is rare that an ASIC device is just hanging in mid air, so I assume that there is a top level "product" specification that describes the "box" the ASIC is going into. So the Box I refer to is the product, the ASIC is the technology that enables it to be implemented as specified, small and low power. So, I guess it depends on your definition of a "product". If you are building a stand alone device for generic implementation, you need to detail its functionality so users can use it, i.e. the device specification, your product. If you are building a switch like my example, the top level requirements "shape" the ASCI requirements. Hence, you derive the basic requirements from the top level and finer grained requirements are derived from design decisions. I was trying to show the "trail" of requirements specifications that a product may have.
"3. When I posted my query at the beginning I talked of Engineering specification. Are you answering of engineering specification here?"
Functional specification - Wikipedia, the free encyclopedia
"4. What do you mean by top level specification?"
The Box I refer to is the product. The top level spec describes it. How it is implemented is not detailed, just the functions it is required to provide.
For my Box example, there may be 2 other specs besides the ASIC spec. How about a Board level spec, and a enclosure spec (the metal box). The top level spec does not say that an ASIC will be used, because what if it can be implemented with off the shelf parts, and meet the spec? Then there is no ASIC spec.
Box = 1U 19" Rack mount enclosure.
Product = a switch
ASIC = technology that enables Product to be realized in the Box.