标签: specification

Let me start with a story about peas -- more specifically, canned baby peas. While working for a semiconductor company in the 1970s, I had the opportunity to support a customer who developed industrial control systems for automating processing plants. He had a problem with one of our single-board computers used in a food processing factory.   We solved the problem, but in the process, I had the opportunity to tour the packaging line. Peas and liquid were metered into cans, which were then sealed and loaded into a giant retort canner. At the end of the cooking time, the cooled cans were sent through a labeling machine that applied product labels to the cans. I was shocked to see that the same peas, from the same process run, were having two different labels applied. One label was plain white paper with a cartoonish figure and the words "baby peas." The other was a beautiful silver foil with embossed letters that said "petit baby peas."   Now, I had often purchased the foil-labeled peas in the past. They were literally right next to the baby peas with the white paper label at my supermarket. What was the difference? Why were my peas priced double the other peas?   The answer was profound. I wasn't buying peas. I was buying a mental image of who I was and how I fit into society. The silver foil-labeled peas were man's peas. The white paper-labeled peas were for kids.   So marketing tells lies -- falsehoods -- things that serve to convey a false impression. Those are pretty strong sentiments that seem to damn marketing professionals.     Before my marketing friends hang me in effigy, however, we should note that, during the specification of an engineering product, a company's marketing team often finds itself in the role of a conduit for misleading or just plain false information to make its way from prospects to the engineering group. Some companies' marketing departments interpret prospect data to arrive at product requirements -- both positive and negative requirements. The question: How do we tell the essential truth from the "mushware" that inevitably comes along for the ride?   Like a great many things in engineering life, sorting the information into bins is the first step. But there is an important message that goes with this sorting: Don't drink your own Kool-Aid. Another way to look at this is to break everything down into objective measures. It may be easier to get to the essence of discerning fact from fiction by listing a few commonly used phrases.   I'll bet that you have heard this one: "Our products are ." When it comes to tangible qualities, this is mushware, pure and simple. Every person who hears this platitude should ask, "As measured by what?" Absent a statement that provides a quantifiable measure, statements like this should be approached cautiously (if at all). What they actually mean to me is "This product isn't actually ready for prime time, and we really hope you'll debug it for us." This may seem harsh, but it's all too real. A favorite tool for me is a red marker. I'll go through a product description and mark through all similar statements that are not backed up by objective measures. The more red, the more problems.   Then there are statements like "We developed our product with your business in mind." Another dose of mushware. How would you determine whether or not the person making this statement is telling the truth? And what is the truth?   These two examples may seem overly simplistic, but they illustrate the sort of mistruths that are propagated, sometimes by accident and sometimes by an inability to accept truths that create cognitive dissonance. It is your marketing team's job to figure out who the customers are (and will be), how to convey product information, and how to stake out a position in the prospects' minds.   Quantifiable, verifiable, and intrinsically fair -- these need to be the objectives of getting at the true facts used to drive engineering development. The way to get there is by using engineering principles. Now, marketing professionals are just that -- professionals. As engineers, we can work with marketing to ensure that the right followup questions are asked to guide us during the product specification and development phases. The purpose of our questions is to ensure that the product meets the customer needs. Marketing's purpose is gain answers for us in addition to determining how the product will be branded, positioned, and sold.   My past experience tells me that working with marketing to define a useful product and to then use that product specification to steer marketing interaction minimizes risk. The hard part is maintaining an objective viewpoint -- especially as an inventor or developer. Nevertheless, your company's future and your continued employment may well depend on your ability to remain fact-based.   Henry Davis is an independent contractor.

Here's a story about peas -- more specifically, canned baby peas. While working for a semiconductor company in the 1970s, I had the opportunity to support a customer who developed industrial control systems for automating processing plants. He had a problem with one of our single-board computers used in a food processing factory.   We solved the problem, but in the process, I had the opportunity to tour the packaging line. Peas and liquid were metered into cans, which were then sealed and loaded into a giant retort canner. At the end of the cooking time, the cooled cans were sent through a labeling machine that applied product labels to the cans. I was shocked to see that the same peas, from the same process run, were having two different labels applied. One label was plain white paper with a cartoonish figure and the words "baby peas." The other was a beautiful silver foil with embossed letters that said "petit baby peas."   Now, I had often purchased the foil-labeled peas in the past. They were literally right next to the baby peas with the white paper label at my supermarket. What was the difference? Why were my peas priced double the other peas?   The answer was profound. I wasn't buying peas. I was buying a mental image of who I was and how I fit into society. The silver foil-labeled peas were man's peas. The white paper-labeled peas were for kids.   So marketing tells lies -- falsehoods -- things that serve to convey a false impression. Those are pretty strong sentiments that seem to damn marketing professionals.     Before my marketing friends hang me in effigy, however, we should note that, during the specification of an engineering product, a company's marketing team often finds itself in the role of a conduit for misleading or just plain false information to make its way from prospects to the engineering group. Some companies' marketing departments interpret prospect data to arrive at product requirements -- both positive and negative requirements. The question: How do we tell the essential truth from the "mushware" that inevitably comes along for the ride?   Like a great many things in engineering life, sorting the information into bins is the first step. But there is an important message that goes with this sorting: Don't drink your own Kool-Aid. Another way to look at this is to break everything down into objective measures. It may be easier to get to the essence of discerning fact from fiction by listing a few commonly used phrases.   I'll bet that you have heard this one: "Our products are ." When it comes to tangible qualities, this is mushware, pure and simple. Every person who hears this platitude should ask, "As measured by what?" Absent a statement that provides a quantifiable measure, statements like this should be approached cautiously (if at all). What they actually mean to me is "This product isn't actually ready for prime time, and we really hope you'll debug it for us." This may seem harsh, but it's all too real. A favorite tool for me is a red marker. I'll go through a product description and mark through all similar statements that are not backed up by objective measures. The more red, the more problems.   Then there are statements like "We developed our product with your business in mind." Another dose of mushware. How would you determine whether or not the person making this statement is telling the truth? And what is the truth?   These two examples may seem overly simplistic, but they illustrate the sort of mistruths that are propagated, sometimes by accident and sometimes by an inability to accept truths that create cognitive dissonance. It is your marketing team's job to figure out who the customers are (and will be), how to convey product information, and how to stake out a position in the prospects' minds.   Quantifiable, verifiable, and intrinsically fair -- these need to be the objectives of getting at the true facts used to drive engineering development. The way to get there is by using engineering principles. Now, marketing professionals are just that -- professionals. As engineers, we can work with marketing to ensure that the right followup questions are asked to guide us during the product specification and development phases. The purpose of our questions is to ensure that the product meets the customer needs. Marketing's purpose is gain answers for us in addition to determining how the product will be branded, positioned, and sold.   My past experience tells me that working with marketing to define a useful product and to then use that product specification to steer marketing interaction minimizes risk. The hard part is maintaining an objective viewpoint -- especially as an inventor or developer. Nevertheless, your company's future and your continued employment may well depend on your ability to remain fact-based.   Henry Davis is an independent contractor.

各位大虾谁有这两个标准： CompactPCI Hot Swap Specification 2.1 IEEE1149.1/4 Standard Test Access Port and Boundary-Scan Architecture 麻烦共享下呀。 我的邮箱：luqiang200006@163.com 感激不尽啊。。。

熟悉3GPP技术规范，可以从23系列和25系列入手，23系列给出了各种技术的架构和要求，25系列则与无线技术有关。 All 3GPP specifications have a specification number consisting of 4 or 5 digits. (e.g. 09.02 or 29.002). The first two digits define the series, followed by 2 further digits for the 01 to 13 series or 3 further digits for the 21 to 55 series. Subject of specification series 3G and beyond / GSM (R99 and later)     General information (long defunct)       Requirements 21 series     Service aspects ("stage 1") 22 series     Technical realization ("stage 2") 23 series     Signalling protocols ("stage 3") - user equipment to network 24 series     Radio aspects 25 series     CODECs 26 series     Data 27 series     Signalling protocols ("stage 3") -(RSS-CN) and OAMP and Charging (overflow from 32.- range) 28 series     Signalling protocols ("stage 3") - intra-fixed-network 29 series     Programme management 30 series     Subscriber Identity Module (SIM / USIM), IC Cards. Test specs. 31 series     OAMP and Charging 32 series     Access requirements and test specifications       Security aspects 33 series     UE and (U)SIM test specifications 34 series     Security algorithms (3) 35 series     LTE (Evolved UTRA) and LTE-Advanced radio technolgy 36 series     Multiple radio access technology aspects 37 series     Note (1): The 13 series GSM specifications relate to European-Union-specific regulatory standards. On the closure of ETSI TC SMG, responsibility for these specifications was transferred to ETSI TC MSG, (Mobile Specification Group) and they do not appear on the 3GPP file server. Note (2): The specifications of these aspects are spread throughout several series. Note (3): Algorithms may be subject to export licensing conditions. See the relevant 3GPP page. See also the relevant ETSI pages. Note (4): The original GSM algorithms are not published and are controlled by the GSM Association. Technical Reports are of two classes: Those intended to be transposed and issued by the Organizational Partners as their own publications; and Those not intended for publication but which are simply 3GPP internal working documents, used, for example, for documenting planning and scheduling of work, or for holding the interim results of feasibility studies. The first category have numbers of the form: xx.9xx The second category have numbers of the form: xx.8xx (feasibility study reports, etc) or, more rarely, 30.xxx / 50.xxx (planning and scheduling) Missing Specs: Click here to see those Specs not yet available following the most recent round of TSG meetings. The 3GPP Specifications are stored on the file server as zipped MS-Word files. The filenames have the following structure: SM ]-V.zip where the character fields have the following significance ... S = series number - 2 characters (see the table above) M = mantissa (the part of the spec number after the series number) - 2 or 3 characters (see above) P = optional part number - 1 or 2 digits if present Q = optional sub-part number - 1 or 2 digits if present V = version number, without separating dots - 3 digits So for example: 21900-320.zip is 3GPP TR 21.900 version 3.2.0 0408-6g0.zip is 3GPP TS 04.08 version 6.16.0 32111-4-410 is 3GPP TS 32.111 part 4 version 4.1.0 29998-04-1-100 is 3GPP TS 29.998 part 4 sub-part 1 version 1.0.0