Jak cię złapią, to znaczy, że oszukiwałeś. Jak nie, to znaczy, że posłużyłeś się odpowiednią taktyką.
11
An exchange made using an APT product line and an APZ source system 11 Plex-C 1 Chapter Summary After reading this chapter, please remember: • Plex is an acronym of Programming Language for EXchanges. It is a high-level language used in the central processor in AXE • AXE, system level 1, is divided into system level 2, subsystems, function blocks, and function units • the hardware configuration includes a central processor, regional processors, extension modules and hardware devices • the difference between a high-level and an assembly language • the purpose of program store, reference store and data store • differences between source system, product line and application system. 12 Chapter 2 Documents Introduction AXE software production involves several documents. This chapter describes the contents of the most important software (SW) documents and shows how these documents compile into the binary object code. Chapter Objectives After completing this chapter, you are familiar with: • document numbers and revisions for software documents • the contents of these software documents: − Source Program Information − Source Parameter List − Parameter List − Signal Description − Signal Survey • the contents of the ID sector • the compilation and object generation processes Figure 2.1 Chapter Objectives Document Numbers Every year, Ericsson staff produce thousands of documents. Identifying these documents with unique numbers is essential. Therefore, this chapter briefly discusses numbering of SW documents before looking at the documents themselves. Consider this document id: 190 55-CAA 107 1918 Rev. B. The following parts identify a document: • 190 55 the decimal class identifying the document type • CAA 107 1918 the product number identifying the product • Rev. B the revision identifying the version of the document The document number includes the decimal class and the product number. The document id includes the document number and the document revision. The revision is essential to identify the right version of a document. 13 Plex-C 1 Figure 2.2 shows decimal classes for some software documents. 190 55 Source Program Information 155 14 Signal Survey 190 59 Parameter List 190 73 Source Parameter List n/155 14 Signal Description Figure 2.2 Decimal classes of software documents Each product receives a unique number consisting of some letters, the ABC class, and a 3 to 7 digit number. The ABC class determines the product’s place in the AXE hierarchy. For example, the ABC class of a software unit is CAA, in both APT and APZ. ABC ABC Class Class AXE AXE AXE System Level 1 APZ APZ APT APT System Level 2 ANZ CPS MAS FMS SSS GSS NMS ANT Subsystem CNZ CJ KR LI CNT Function Block CAA CJU LIR LIU CAA Function Unit Figure 2.3 ABC classes and the system structure The ABC class is followed by several digits building the product number. The following rules apply. System level 1 has the ABC class AXE and the product numbers AXE 105 for traditional AXE systems and AXE 106 for systems using the Application Modularity architecture. 14 Documents System level 2 has different product numbers for APT and APZ systems, typical examples include APT 210 15 or APZ 212 30. Subsystems have numbers such as ANT 217 01, where 217 identifies the subsystem and 01 the version of the subsystem. Function blocks use the consecutive number for the subsystem followed by a number for the block. For instance, CNT 217 1234 identifies block 1234 in subsystem 217. Software function units have different number series for CP, RP, and EMRP. CP: CAA 107 3456 CAAZ 107 3456 (exception) CAAU 107 3456 (unit specific for US market) CAAP 107 3456 (unit specific for Australian market) RP: CAA 105 3456 EMRP: CAA 117 3456 where 3456 is a consecutive number. Note: the number serial CAAZ 107 ... is only used, if the ordinary number sequence CAA 107 ... ran out of numbers. Special rules apply for signal descriptions. Block-internal signals use block product numbers. Signals sent between blocks in one subsystem, for example KR and LI, use subsystem product numbers. Consider these examples. Document Number Document Type 190 55 - CAA 107 4567 SPI, Plex-C program for CP unit CAA 107 4567 155 14 - CAA 107 4242 Signal survey for unit CAA 107 4242 5/155 14 - CNT 219 1619 Signal description for a block internal signal Signal description for a signal sent between 42/155 14 - ANT 219 07 blocks of the same subsystem ANT 219 07 Table 2.1 Sample document numbers The revision identifies the version of the document. During the design work, designers use preliminary revisions (PA1, PA2, PA3, ..., PB1, PB2, ..., PC1, ...).
|
Wątki
|