DOCSLIB.ORG

November 6, 2002

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
November 6, 2002 Volume 7 November 2002 Issue date: November 6, 2002 Source: http://www.csa-intl.org/english/infoupdate/main_en.asp Info Update, 2002 No. 7 ISSN 1182-0187 November 6, 2002 Canadian Standards Association Making Standards Work for People and Business The Canadian Standards Association has been a leader in standards development since 1919. Accredited by the Standards Council of Canada, we have published over 2000 standards for the safety, design and performance of a wide range of products and services. Many of our standards are cited in legislation at federal, provincial, state and municipal levels across North America. Many are internationally or regionally harmonized. All of our standards are the result of the knowledge and expertise of our members who develop the standards. Our 9,000+ members are at the heart of the CSA process for the development of standards. They come from all walks of life and include scientists, academics, environmentalists and technicians. They represent government, industry, labour and consumers. All CSA standards are developed following principles of consensus, so that all viewpoints receive a fair hearing with no one interest group dominating. There are two different types of membership; volunteer committee membership and sustaining membership. Our committee members contribute time and expertise to the process of standards development, and our sustaining members support this work through the payment of annual dues. CSA is funded through the sale of information products, membership, and from interested stakeholders. At the Canadian Standards Association, we know the power of standards to effect change and are committed to making standards work for people and business. For more than 80 years, the Canadian Standards Association has developed standards to create a better, safer world – and we will continue to touch people's lives in positive ways for many years to come. Visit our web site at www.csa.ca and find out just how convenient and efficient it is to access all the latest information. Communications/Information CAN/CSA-ISO/IEC 8859-8:02, 1st edition Information Technology–8-bit single-byte coded graphic character sets–Part 8: Latin/Hebrew alphabet (Adopted ISO/IEC 8859-8:1999) Informatique et télécommunications CAN/CSA-ISO/CEI 7498-3-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Modèle de référence de base : Dénomination et adressage (norme ISO/CEI 7498-3:1997 adoptée) CAN/CSA-ISO/CEI 10164-14-01, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Gestion-systèmes : Catégories de tests de confiance et de diagnostic (norme ISO/CEI 10164-14:1996 adoptée) CAN/CSA-ISO/CEI 10181-4-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Cadres de sécurité pour les systèmes ouverts : Non-répudiation (norme ISO/CEI 10181-4:1997 adoptée) CAN/CSA-ISO/CEI 10181-5-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Cadres de sécurité pour les systèmes ouverts : Cadre de confidentialité (norme ISO/CEI 10181-5:1996 adoptée) CAN/CSA-ISO/CEI 10181-6-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Cadres de sécurité pour les systèmes ouverts : Cadre d’intégrité (norme ISO/CEI 10181-6:1996 adoptée) CAN/CSA-ISO/CEI 10181-7-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Cadres de sécurité pour les systèmes ouverts : Cadre d’audit et d’alarmes de sécurité (norme ISO/CEI 10181-7:1996 adoptée) CAN/CSA-ISO/CEI 10918-3-00, 1re édition Technologies de l’information–Compression et codage numériques des images fixes à modelé continu : Extensions (norme ISO/CEI 10918-3:1997 adoptée) CAN/CSA-ISO/CEI 11179-3-00, 1re édition Technologies de l’information–Spécifications et normalisation des éléments de données– Partie 3 : Attributs de base des éléments de données (norme ISO/CEI 11179-3:1994 adoptée) CAN/CSA-ISO/CEI 11179-4-00, 1re édition Technologies de l’information–Spécifications et normalisation des éléments de données– Partie 4 : Règles et directives pour la formulation des définitions des données (norme ISO/CEI 11179-4:1995 adoptée) Volume 7 – November 2002 Issue Date: November 6, 2002 New Standards in this Issue – page 2 of 6 Informatique et télécommunications (suite) CAN/CSA-ISO/CEI 11586-1-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Sécurité générique des couches supérieures : Aperçu, modèles et notation (norme ISO/CEI 11586-1:1996 adoptée) CAN/CSA-ISO/CEI 11586-2-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Sécurité générique des couches supérieures : Définition du service assuré par l’élément de service d’échange de sécurité (SESE) (norme ISO/IEC 11586-2:1996 adoptée) CAN/CSA-ISO/CEI 11586-3-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Sécurité générique des couches supérieures : Spécification du protocole d’élément de service d’échange de sécurité (SESE) (norme ISO/CEI 11586-3:1996 adoptée) CAN/CSA-ISO/CEI 11586-4-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Sécurité générique des couches supérieures : Spécification de la syntaxe de protection du transfert (norme ISO/CEI 11586-4:1996 adoptée) CAN/CSA-ISO/CEI 11586-5-00, 1re édition Technologies de l’information–Interconnexion de systèmes ouverts (OSI)–Sécurité générique des couches supérieures : Formulaire de déclaration de conformité d’instance de protocole (PICS) de l’élément de service d’échange de sécurité (SESE) (norme ISO/CEI 11586-5:1997 adoptée) CAN/CSA-ISO/CEI 11588-1-00, 1re édition Technologies de l’information–Gestion des systèmes de messagerie (MHS)–Partie 1 : Modèle et architecture (norme ISO/CEI 11588-1:1996 adoptée) CAN/CSA-ISO/CEI 13712-1-00, 1re édition Technologies de l’information–Opérations distantes : Concepts, modèle et notation (norme ISO/CEI 13712-1:1995 adoptée) CAN/CSA-ISO/CEI 13712-2-00, 1re édition Technologies de l’information–Opérations distantes : Réalisations OSI–Définition du service de l’élément de service d’opérations distantes (ROSE) (norme ISO/CEI 13712-2:1995 adoptée) Construction Products and Materials S136-01, 6th edition North American Specification for the Design of Cold-Formed Steel Structural Members Produits et matériaux de construction B45 Série-99, 4e édition Appareils sanitaires B602-99, 3e édition Joints mécaniques pour tuyaux d'évacuation, de ventilation et d'égout Volume 7 – November 2002 Issue Date: November 6, 2002 New Standards in this Issue – page 3 of 6 Produits et matériaux de construction (suite) O86-01, 8e édition Règles de calcul des charpentes en bois W117.2-01, 4e édition Règles de sécurité en soudage, coupage et précédés connexes (Élaborée en collaboration avec le Bureau canadien de soudage) Electrical/Electronics C22.2 No. 141-02, 3rd edition Unit Equipment for Emergency Lighting CAN/CSA-CEI/IEC 61000-4-8:02, 1st edition (bilingual) Electromagnetic Compatibility (EMC)–Part 4-8: Testing and Measurement Techniques–Power Frequency Magnetic Field Immunity Test (Adopted CEI/IEC 61000-4-8:1993+A1:2000, edition 1.1, without modification) CAN/CSA-CEI/IEC 61000-4-9:02, 1st edition (bilingual) Electromagnetic Compatibility (EMC)–Part 4-9: Testing and Measurement Techniques–Pulse Magnetic Field Immunity Test (Adopted CEI/IEC 61000-4-9:1993+A1:2000, edition 1.1, without modification) CAN/CSA-CEI/IEC 61000-4-16:02, 1st edition (bilingual) Electromagnetic Compatibility (EMC)–Part 4-16: Testing and Measurement Techniques–Test for Immunity to Conducted, Common Mode Disturbances in the Frequency Range 0 Hz to 150 kHz (Adopted CEI/IEC 61000-4-16:1998+ Amendment 1:2001, first edition, without modification) CAN/CSA-CEI/IEC 61000-4-17:02, 1st edition (bilingual) Electromagnetic Compatibility (EMC)–Part 4-9: Testing and Measurement Techniques–Ripple on D.C. Input Power Port Immunity Test (Adopted CEI/IEC 61000-4-17:1999+Amendment 1:2001, first edition, without modification) CAN/CSA-E60730-1:02, 3rd edition (bilingual) Automatic Electrical Controls for Household and Similar Use–Part 1: General Requirements (Adopted CEI/IEC 60730-1:1999, third edition, with Canadian deviations) Électricité et électronique C22.2 n° 112-97 (C2002), 8e édition Sécheuses électriques (norme binationale avec UL 2158) CAN/CSA-CEI/IEC 61000-4-8:02, 1re édition (bilingue) Compatibilité électromagnétique (CEM)–Partie 4-8 : Techniques d’essai et de mesure– Essai d’immunité au champ magnétique à la fréquence du réseau (norme CEI/IEC 61000-4-8:1993, y compris l’Amendement 1:2000, édition 1.1, a été adoptée sans modifications) Volume 7 – November 2002 Issue Date: November 6, 2002 New Standards in this Issue – page 4 of 6 Électricité et électronique (suite) CAN/CSA-CEI/IEC 61000-4-9:02, 1re édition (bilingue) Compatibilité électromagnétique (CEM)–Partie 4-8 : Techniques d’essai et de mesure– Essai d’immunité au champ magnétique impulsionnel (norme CEI/IEC 61000-4-9:1993, y compris l’Amendement 1:2000, édition 1.1, a été adoptée sans modifications) CAN/CSA-CEI/IEC 61000-4-16:02, 1re édition (bilingue) Compatibilité électromagnétique (CEM)–Partie 4-8 : Techniques d’essai et de mesure– Essai d’immunité aux perturbations conduites en mode commun dans la gamme de fréquences de 0 Hz à 150 kHz (norme CEI/IEC 61000-4-16:1998, y compris l’Amendement 1 :2001, 1re édition, a été adoptée sans modifications) CAN/CSA-CEI/IEC 61000-4-17:02, 1re édition (bilingue) Compatibilité électromagnétique
Load more

Recommended publications
  • Minimoog Model D Manual
    3 IMPORTANT SAFETY INSTRUCTIONS WARNING - WHEN USING ELECTRIC PRODUCTS, THESE BASIC PRECAUTIONS SHOULD ALWAYS BE FOLLOWED. 1. Read all the instructions before using the product. 2. Do not use this product near water - for example, near a bathtub, washbowl, kitchen sink, in a wet basement, or near a swimming pool or the like. 3. This product, in combination with an amplifier and headphones or speakers, may be capable of producing sound levels that could cause permanent hearing loss. Do not operate for a long period of time at a high volume level or at a level that is uncomfortable. 4. The product should be located so that its location does not interfere with its proper ventilation. 5. The product should be located away from heat sources such as radiators, heat registers, or other products that produce heat. No naked flame sources (such as candles, lighters, etc.) should be placed near this product. Do not operate in direct sunlight. 6. The product should be connected to a power supply only of the type described in the operating instructions or as marked on the product. 7. The power supply cord of the product should be unplugged from the outlet when left unused for a long period of time or during lightning storms. 8. Care should be taken so that objects do not fall and liquids are not spilled into the enclosure through openings. There are no user serviceable parts inside. Refer all servicing to qualified personnel only. NOTE: This equipment has been tested and found to comply with the limits for a class B digital device, pursuant to part 15 of the FCC rules.
    [Show full text]
  • International Standards, Approaches and Frameworks Relevant to Software Quality Management and Software Process Improvement
    International standards, approaches and frameworks relevant to Software Quality Management and Software Process Improvement To help organizations managing software quality and improving software processes several standards, models, approaches and frameworks have been developed during the last decades. The most widely known and recognized of them are presented in this document. • Capability Maturity Model (CMM) • CMM Integration (CMMI) • Personal Software Process (PSP) and Team Software Process (TSP) • ISO 9000 standards family • TickIT • ISO/IEC TR 15504 Information Technology - Software Process Assessment (SPICE) • ISO/IEC 12207 Information Technology - Software Life-Cycle Processes • BOOSTRAP • Rational Unified Process CMM Publication Date: Version 1.1 - February 1993 Description: The Capability Maturity Model for Software (SW-CMM or CMM) is a model used by organizations for appraising the maturity of their software processes and for identifying practices that will increase the maturity of those processes. It was developed by the Software Engineering Institute, in cooperation with industry representatives. The Software CMM has become a de facto standard for assessing and improving software processes. Through the SW-CMM, the SEI and community have put in place an effective means for modeling, defining, and measuring the maturity of the processes used by software professionals. The Capability Maturity Model for Software describes the principles and practices underlying software process maturity and is intended to help software organizations
    [Show full text]
  • A Stone Man Version
    Guide to the Software Engineering Body of Knowledge AA SSttoonnee MMaann Veerrssiioonn (Version 0.7) April 2000 A project of the Software Engineering Coordinating Committee (Joint IEEE Computer Society - ACM committee ) Corporate support by: Project managed by: Executive Editors: Alain Abran, Université du Québec à Montréal James W. Moore, The MITRE Corp. Editors: Pierre Bourque, Université du Québec à Montréal Robert Dupuis, Université du Québec à Montréal Chair of the Software Engineering Coordinating Committee Leonard L. Tripp, IEEE Computer Society Copyright © 2000, Institute of Electrical and Electronics Engineers, Inc. All rights reserved. PREFACE TO THE SWEBOK GUIDE 1. Software engineering is an emerging discipline but there are unmistakable trends indicating an 10. Purpose increasing level of maturity: 11. The purpose of this Guide is to provide a 2. w McMaster University (Canada), the consensually-validated characterization of the Rochester Institute of Technology (US), the bounds of the software engineering discipline University of Sheffield (UK), the and to provide a topical access to the Body of University of New South Wales (Australia) Knowledge supporting that discipline. The Body and other universities around the world now of Knowledge is subdivided into ten Knowledge offer undergraduate degrees in software Areas (KA) and the descriptions of the KAs are engineering. designed to discriminate among the various important concepts, permitting readers to find 3. w The Software Capability Maturity Model and ISO 9000 are used to certify their way quickly to subjects of interest. Upon organizational capability for software finding a subject, readers are referred to key engineering. papers or book chapters selected because they succinctly present the knowledge.
    [Show full text]
  • Guide to the Software Engineering Body of Knowledge
    Guide to the Software Engineering Body of Knowledge AA SSttoonnee MMaann VVeerrssiioonn (Version 0.5) October 1999 A project of the Software Engineering Coordinating Committee (Joint IEEE Computer Society - ACM committee ) Corporate support by: Project managed by: Co-Executive Editors: Alain Abran, Université du Québec à Montréal James W. Moore, The MITRE Corp. Editors: Pierre Bourque, Université du Québec à Montréal Robert Dupuis, Université du Québec à Montréal Project Champion: Leonard L. Tripp, IEEE Computer Society Table of Contents INTRODUCTORY TEXT FROM THE EDITORIAL TEAM KNOWLEDGE AREA DESCRIPTION : - Software Configuration Management - Software Construction - Software Design - Software Engineering Infrastructure - Software Engineering Management - Software Engineering Process - Software Evolution and Maintenance - Software Quality Analysis - Software Requirement Analysis - Software Testing APPENDIX A KNOWLEDGE AREA DESCRIPTION SPECIFICATIONS FOR THE STONE MAN VERSION OF THE GUIDE TO THE SOFTWARE ENGINEERING BODY OF KNOWLEDGE – VERSION 0.25 INTRODUCTORY TEXT FROM THE EDITORIAL TEAM The IEEE Computer Society and the Association for Computing Machinery are working on a joint project to develop a guide to the Software Engineering Body Of Knowledge (SWEBOK). This is the current draft (version 0.5 completed in September 1999) of the Stoneman version of the Guide1. Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. Without such a consensus, there is no way to validate a licensing examination, set a curriculum to prepare individuals for the examination, or formulate criteria for accrediting the curriculum. The project team is currently working on an update to this draft version of the Guide based on the results of the second review cycle.
    [Show full text]
  • Voluntary Voting System Guidelines VVSG 2.0 Recommendations for Requirements for the Voluntary Voting System Guidelines 2.0
    Voluntary Voting System Guidelines VVSG 2.0 Recommendations for Requirements for the Voluntary Voting System Guidelines 2.0 February 29, 202010, 2021 Prepared for the Election Assistance Commission At the direction of the Technical Guidelines Development Committee 1 Acknowledgements Chair of the TGDC: Dr. Walter G. Copan Director of the National Institute of Standards and Technology (NIST) Gaithersburg, MD Representing the EAC Standards Board: Robert Giles Paul Lux Director Supervisor of Elections New Jersey Division of Elections Okaloosa County Trenton, NJ Crestview, FL Representing the EAC Board of Advisors: Neal Kelley Linda Lamone Registrar of Voters Administrator of Elections Orange County Maryland State Board of Orange County, CA ElectionElections Annapolis, MD Representing the Architectural and Transportation Barrier, and Compliance Board (Access Board): Marc Guthrie Sachin Pavithran Public Board Member Public Board Member Newark, OH Logan, UT Representing the American National Standards Institute (ANSI): Mary Saunders Vice President, Government Relations & Public Policy American National Standards Institute Washington, DC Representing the Institute of Electrical and Electronics Engineers: Dan Wallach Professor, Electrical & Engineering Computer Science Rice University Houston, TX Representing the National Association of State Election Directors (NASED): Lori Augino Judd Choate Washington State Director of Elections State Elections Director Washington Secretary of State Colorado Secretary of State Olympia, WA Denver, CO 2 Requirements
    [Show full text]
  • NIST Time and Frequency Services (NIST Special Publication 432)
    Time & Freq Sp Publication A 2/13/02 5:24 PM Page 1 NIST Special Publication 432, 2002 Edition NIST Time and Frequency Services Michael A. Lombardi Time & Freq Sp Publication A 2/13/02 5:24 PM Page 2 Time & Freq Sp Publication A 4/22/03 1:32 PM Page 3 NIST Special Publication 432 (Minor text revisions made in April 2003) NIST Time and Frequency Services Michael A. Lombardi Time and Frequency Division Physics Laboratory (Supersedes NIST Special Publication 432, dated June 1991) January 2002 U.S. DEPARTMENT OF COMMERCE Donald L. Evans, Secretary TECHNOLOGY ADMINISTRATION Phillip J. Bond, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arden L. Bement, Jr., Director Time & Freq Sp Publication A 2/13/02 5:24 PM Page 4 Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY SPECIAL PUBLICATION 432 (SUPERSEDES NIST SPECIAL PUBLICATION 432, DATED JUNE 1991) NATL. INST.STAND.TECHNOL. SPEC. PUBL. 432, 76 PAGES (JANUARY 2002) CODEN: NSPUE2 U.S. GOVERNMENT PRINTING OFFICE WASHINGTON: 2002 For sale by the Superintendent of Documents, U.S. Government Printing Office Website: bookstore.gpo.gov Phone: (202) 512-1800 Fax: (202)
    [Show full text]
  • Pitch Vs Frequency There Is a Relationship Between Pitch And
    Pitch vs Frequency There is a relationship between pitch and frequency. The faster the vi- bration of something producing a sound, the higher the pitch we tend to perceive that sound to be. This section will discuss this relationship. Frequencies come in all values. between any two frequencies, no matter how close together they are, there is always some other frequency. However, for the purpose of music, this infinitude of possibilities it too great. Over the centuries, the set of all possible frequencies has been categorized into a finite set of frequencies which are used in the playing of music. The first and most important aspect of pitches, is that there, given one pitch, there is another, either higher or lower, which sounds most pleasing, most harmonious when played together with the first. This “interval” (a distance between pitches) is called the octave. Two voices or two instruments played an octave apart, blend together into one sound. In fact so tight is the relationship, that one often says that even if two voices sing a song an octave apart, they are really singing the same note. There is, to some extent, a sort of equivalence between notes an octave apart, so much so, that one says that there is an ”octave equivalence”– things an octave apart are really the same. (Obviously this equivalence is limited in scope, because there are also clearly differences between two sounds an octave apart). As was already discovered by Pythagoras, over 2000 years ago, there is also a very particular relationship between the frequencies of two notes an octave apart.
    [Show full text]
  • Appendix A: Quality Models and Verification Methods
    Appendix A: Quality Models and Verification Methods As indicated in previous chapters, we have excluded discussions on the various verification methods which still exist in many publications. The following table may be useful in researching appropriate methods to deal with the different artefacts in the product lifecycle. We do not claim completeness in the methods but have provided common verification methods which we apply in our projects. Artefact type Quality model Verification methods Documentation DocQMod • Peer Review • Structured Group Review • Inspection • Walk Through • Technical Review • Informal Review Business BPQMod • Peer Review processes • Structured Group Review • Formal Inspection (on business process models, e.g. swimlanes, business and application process models) • Walk Through • GUI Prototyping • Test Modelling (based on business processes) • Early Test Case Design • Usability Testing Requirements ReqQMod • Management Review • Peer Review • Structured Group Review • Audit • Inspection • Walk Through • Technical Review • Informal review • GUI Prototyping • Test Modelling (based on requirements) • Test Case Specification (based on requirements) (continued) M. Wieczorek et al., Systems and Software Quality, 165 DOI 10.1007/978-3-642-39971-8, © Springer-Verlag Berlin Heidelberg 2014 166 Appendix A: Quality Models and Verification Methods Artefact type Quality model Verification methods Architecture ArchQMod • Peer Review • Structured Group Review • Formal Inspection • ATAM • Prototyping (including functional and non-functional testing) • FMEA Database DataQMod • Formal Inspection (on e.g. normalisation) • Peer Review (on indexing, SQL statements, stored procedures) • Structured Group Review • Functional Testing (by application) • Non-functional testing (including performance and security) Source code CodeQMod • Peer Review • Walk Through • Formal Inspection (e.g. style guides, coding standards) • Static Source Code Analysis (tool based) • Profiling (e.g.
    [Show full text]
  • The Basics of Harpsichord Tuning Fred Sturm, NM Chapter Norfolk, 2016
    The Basics of Harpsichord Tuning Fred Sturm, NM Chapter Norfolk, 2016 Basic categories of harpsichord • “Historical”: those made before 1800 or so, and those modern ones that more or less faithfully copy or emulate original instruments. Characteristics include use of simple levers to shift registers, relatively simple jack designs, use of either quill or delrin for plectra, all-wood construction (no metal frame or bars). • 20th century re-engineered instruments, applying 20th century tastes and engineering to the basic principle of a plucked instrument. Pleyel, Sperrhake, Sabathil, Wittmeyer, and Neupert are examples. Characteristics include pedals to shift registers, complicated jack designs, leather plectra, and metal frames. • Kit instruments, many of which fall under the historical category. • A wide range of in between instruments, including many made by inventive amateurs. Harpsichords come in many shapes and designs. • They may have one keyboard or two. • They may have only one string per key, or as many as four. • The pitch level of each register of strings may be standard, or an octave higher or lower. These are called, respectively, 8-foot, 4-foot, and 16-foot. • The harpsichord may be designed for A440, for A415, or possibly for some other pitch. • Tuning pins may be laid out as in a grand piano, or they may be on the side of the case. • When there are multiple strings per note, the different registers may be turned on and off using levers or pedals. We’ll start by looking at some of these variables, and how that impacts tuning. Single string instruments These are the simplest instruments, and the easiest to tune.
    [Show full text]
  • Appendix G Systems General Requirements
    BROADWAY SUBWAY PROJECT Commercial in Confidence PROJECT AGREEMENT EXECUTION COPY SCHEDULE 4 Appendix G Systems General Requirements BROADWAY SUBWAY PROJECT Commercial in Confidence PROJECT AGREEMENT EXECUTION COPY SCHEDULE 4: APPENDIX G: SYSTEM GENERAL REQUIREMENTS - 2 - Table of Contents 1 APPENDIX G – Systems GENERAL REQUIREMENTS .................................................................. 7 1.1 Introduction .......................................................................................................................................... 7 1.2 Requirements Delivery ........................................................................................................................ 7 1.3 Standards .............................................................................................................................................. 8 1.4 Systems Plan ........................................................................................................................................ 8 1.5 Design Life of the Systems .................................................................................................................. 9 1.6 Systems Design Management .............................................................................................................. 9 1.6.1 Requirements Specification Overview ............................................................................................ 10 1.6.2 Requirements Analysis Overview ..................................................................................................
    [Show full text]
  • Base Station, A850/440 User Manual
    Base Station Telemetry Gateway A850 User Guide valid for A850 firmware release 1.0 SMART WIRELESS SOLUTIONS ADCO N TELEMETRY ADCON TELEMETRY GMBH INKUSTRASSE 24 A-3400 KLOSTERNEUBURG AUSTRIA TEL: +43 | 2243 | 38280-0 FAX: +43 | 2243 | 38280-6 http://www.adcon.at ADCON INTERNATIONAL INC 2050 LYNDELL TERRACE SUITE 120 CA-95616 DAVIS, USA TEL: +1 | 530 | 753-1458 FAX: +1 | 530 | 753-1054 http://www.adcon.at ADCON AUSTRALIA PTY. LTD. ENFIELD PLAZA SA 5058 PO BOX 605 ADELAIDE AUSTRALIA TEL: +61 | 8 | 8260-4682 FAX: +61 | 8 | 8260-4685 http://www.adcon.at Proprietary Notice: The Adcon logo, the A72x, A73x and A74x series, addIT™, addWAVE™, the A840 and A850 Telemetry Gateway, addVANTAGE®, and addVANTAGE Lite are trademarks or registered trade- marks of Adcon Telemetry. All other registered names used throughout this publication are trademarks of their respective owners. Neither the whole nor any part of the information contained in this publication may be repro- duced in any material form except with the prior written permission of Adcon Telemetry. This publication is intended only to assist the reader in the use of the product. Adcon Telemetry shall not be liable for any loss or damage arising from the use of any information in this publica- tion, or any error or omission in such information, or any incorrect use of the product. Document Release: 1.2, September 2007 Copyright ©2001—2007 by Adcon Telemetry GmbH. All rights reserved. CHAPTER 3 Chapter 1. Introduction ________________________________________________ 13 Scope ________________________________________________________________ 13 Conventions ___________________________________________________________ 14 What is the A850 Telemetry Gateway? ____________________________________ 15 Adcon's Telemetry Network _____________________________________________ 18 What's new on the A850 ?_______________________________________________ 20 Chapter 2.
    [Show full text]
  • The Evolution of Software Configuration Management
    ISSN 2278-3091 Syahrul Fahmy et al., International Journal of AdvancedVolume Trends 9, No.1. in Computer3, 2020 Science and Engineering, 9(1.3), 2020, 50 - 63 International Journal of Advanced Trends in Computer Science and Engineering Available Online at http://www.warse.org/IJATCSE/static/pdf/file/ijatcse0891.32020.pdf https://doi.org/10.30534/ijatcse/2020/0891.32020 The Evolution of Software Configuration Management 1 2 3 1 1 Syahrul Fahmy , Aziz Deraman , Jamaiah Yahaya , Akhyari Nasir , Nooraida Shamsudin 1University CollegeTATI, Malaysia, [email protected] 2Universiti Malaysia Terengganu, Malaysia 3Universiti Kebangsaan Malaysia, Malaysia processing and implementation status, and verify compliance ABSTRACT with specified requirements” [3]. Software Configuration Management (SCM) is a discipline in “a management activity that applies technical and software engineering for managing changes to software administrative direction over the life cycle of a product, its products using standard processes and tools. This article configuration items, and related product configuration presents the evolution of SCM since its inception, information. It provides identification and traceability, the highlighting the components, application to other areas, status of achievement, and access to accurate information in change management and software quality. Research and all phases of the life cycle” [4]. development in SCM are highly motivated by the problems at hand in software development. SCM process and activities are This paper presents the evolution of SCM, discussing its sound, guided by international standards and industry best components, application to other areas, change management practice. Commercial and proprietary tools are aplenty, and and software quality. the underlying techniques are no longer confined to SCM.
    [Show full text]