1. A semiconductor device, comprising:
a semiconductor device;
a wiring layer provided on the semiconductor substrate;
a high frequency wiring provided in the wiring layer; and
plural dummy metals provided in the wiring layer apart from the high frequency wiring,
wherein the wiring layer in plan view includes a high frequency wiring vicinity region and an external region surrounding the high frequency wiring vicinity region,
wherein the high frequency wiring vicinity region includes a first region enclosed by an outer edge of the high frequency wiring, and a second region surrounding the first region,
wherein the plural dummy metals are disposed dispersedly in the high frequency wiring vicinity region and in the external region respectively, and
wherein an average interval between the dummy metals in the high frequency wiring vicinity region is wider than that in the external region.
2. The semiconductor device according to claim 1, wherein the second region is formed within a radius of 50 \u03bcm or more around the first region.
3. The semiconductor device according to claim 1, further comprising:
a guard ring surrounding the high frequency wiring in plan view, the guard ring being provided in at least the wiring layer,
wherein the high frequency wiring vicinity region is arranged inside the guard ring and is arranged between the external region and the high frequency wiring vicinity region.
4. The semiconductor device according to claim 2, wherein the wiring layer is a first wiring layer and the plural dummy metals are plural second dummy metals,
wherein the semiconductor device further comprises a second wiring layer provided between the first wiring layer and the semiconductor substrate, and
wherein plural second dummy metals are disposed dispersedly in the second wiring layer, the plural second dummy metals being provided in a region superposed on the high frequency wiring in plan view.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A computer program product, comprising:
a non-transitory computer-usable storage medium having stored therein computer-usable program code that, when executed by a computer, controls version branching within a software configuration management system (SCMS), the computer-usable program code include
computer-usable program code that, responsive to a user initiating a check-out operation of a file within the SCMS, identifies the file and a workspace of the user;
computer-usable program code that searches nodes of the repositories of the SCMS for a successor version of the file;
computer-usable program code that, when a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, outputs a notification that the successor version of the file is within the predetermined distance of the workspace of the user; and
computer-usable program code that, when a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, checks-out the file to the workspace of the user.
2. The computer program product of claim 1, wherein
the computer-usable medium further comprises computer-usable program code that determines a distance between the node comprising the successor version of the file and the workspace of the user according to a number of hops to be traversed along a path linking the node comprising the successor version of the file and the workspace of the user through the SCMS.
3. The computer program product of claim 2, wherein
the computer-usable medium further comprises computer-usable program code that assigns a measure of time to each hop of the path.
4. The computer program product of claim 1, wherein
the computer-usable medium further comprises computer-usable program code that, for at least one selected hop within the path, determines a measure of time to be assigned to the selected hop according to a declaration of availability of the successor version of the file.
5. The computer program product of claim 1, wherein
the computer-usable medium further comprises computer-usable program code that, for at least one selected hop within the path, determines a measure of time to be assigned to the selected hop according to a histogram of project transfers along the selected hop.
6. A system for controlling version branching, comprising:
a processor configured to initiate executable operations comprising:
responsive to a user initiating a check-out operation of a file within a software configuration management system (SCMS), identifying the file and a workspace of the user;
searching nodes of the repositories of the SCMS for a successor version of the file;
when a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, outputting a notification that the successor version of the file is within the predetermined distance of the workspace of the user; and
when a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, checking-out the file to the workspace of the user.
7. The system of claim 6, wherein
the processor is further configured to initiate an executable operation comprising determining a distance between the node comprising the successor version of the file and the workspace of the user according to a number of hops to be traversed along a path linking the node comprising the successor version of the file and the workspace of the user through the SCMS.
8. The system of claim 7, wherein
the processor is further configured to initiate an executable operation comprising assigning a measure of time to each hop of the path.
9. The system of claim 6, wherein
the processor is further configured to initiate an executable operation comprising, for at least one selected hop within the path, determining a measure of time to be assigned to the selected hop according to a declaration of availability of the successor version of the file.
10. The system of claim 6, wherein
the processor is further configured to initiate an executable operation comprising, for at least one selected hop within the path, determining a measure of time to be assigned to the selected hop according to a histogram of project transfers along the selected hop.
11. The system of claim 6, wherein
the processor is further configured to initiate an executable operation comprising receiving a user-input specifying a limitation on a number of nodes to be searched.
12. The system of claim 6, wherein
the processor is further configured to initiate an executable operation comprising representing the SCMS as a graph comprising nodes and hops representing allowable connections between nodes, wherein each hop is defined according to source-target relationships between nodes defined within the SCMS.
13. The system of claim 12, wherein
the processor is further configured to initiate executable operations comprising:
defining a plurality of accepted project nodes, wherein each accepted project node corresponds to a workspace of a single user, wherein each accepted project node stores only accepted projects; and
defining a plurality of accepted activity nodes, wherein each accepted activity node corresponds to a workspace of a single user, wherein each accepted activity node stores only accepted activities.
14. The system of claim 13, wherein
the processor is further configured to initiate an executable operation comprising defining a plurality of pending bucket nodes, wherein each pending bucket node corresponds to a workspace of a single user, wherein each pending bucket node stores unaccepted activities.
15. The system of claim 14, wherein
the processor is further configured to initiate an executable operation comprising defining a plurality of pending project nodes, wherein each pending project node represents a community repository storing at least one state of a project.
16. A system for controlling version branching, comprising:
a processor configured to initiate executable operations comprising:
representing the software configuration management system (SCMS) as a graph comprising a plurality of nodes and a plurality of hops, wherein each hop represents an allowable data transfer between two nodes, wherein each hop is defined according to source-target relationships between nodes within the SCMS;
responsive to a user initiating a check-out operation of a file within the SCMS, determining the file to be checked-out and a workspace of the user to which the file will be checked-out;
searching each node of the SCMS that is within a predetermined number of hops from a node representing the workspace of the user, according to the graph, for a successor version of the file;
when a successor version of the file is identified, outputting a notification that the successor version of the file is within the predetermined distance of the workspace of the user; and
when a successor version of the file is not identified, checking-out the file to the workspace of the user.
17. The system of claim 16, wherein searching each node of the SCMS that is within a predetermined number of hops from a node representing the workspace of the user, according to the graph, for a successor version of the file further comprises:
identifying a node comprising an activity or a project that comprises the successor version of the file; and
counting a number of hops connecting the node comprising the successor version of the file and the node representing the workspace of the user.
18. The system of claim 17, wherein
the processor is further configured to initiate an executable operation comprising assigning a measure of time to each hop of the path and summing the measures of time.
19. The system of claim 18, wherein
the processor is further configured to initiate an executable operation comprising, for at least one selected hop within the path, determining a measure of time to be assigned to the selected hop according to a declaration of availability of the successor version of the file.
20. The system of claim 18, wherein
the processor is further configured to initiate an executable operation comprising, for at least one selected hop within the path, determining a measure of time to be assigned to the selected hop according to a histogram of project transfers along the selected hop.