Modules, description

Since the CTSA process is applicable to numerous industry sectors, the module descriptions were developed to provide basic information suitable for a wide audience with a broad range of information needs (see fig. 8.2 and tables 8.3 through 8.8). 

The vernier model also turned out to be an approximation. It is now clear that although the metal atoms in these stmctures are similar to that found in the fluorite parent structure, the anion array is continuously modulated, and expands or contracts throughout the structure to fill the space optimally with respect to the chemical and crystallographic constraints that apply. Although for some modulation wavelengths the anion array is well described in terms of a square net or a hexagonal net, this is not universally correct, and the modulated description is a more accurate representation of the anion substructure. 

Module architecture Module descriptions Module interfaces... 

Module Table I SECS Program Modules Description... 

Slot no. Module Description No. of channels used Cable ... 

Standards for software identification and traceability (e.g., for each software item—unique name/reference, version, project/ product reference, module description, list of build files, change history, traceability to design document) (see Appendix C, section 5, Item 1.2)... 

Module description does not include input, output, processing or limitations Module has multiple entrances or multiple exits Database is too large Database is not compartmentalized Functions are duplicated Existence of global data... 

Each software module identified in the software architecture should be described in the detailed design. The particular content of the description will depend on the module type. In general, a module description should completely define its interface with other modules and should completely define the module function and its function in the overall software. 

Module generation using parameterized, procedural module descriptions. 

---