{"title":"Project implementation of Software Configuration Management","authors":"C. Fredrick","doi":"10.1145/800003.807908","DOIUrl":"https://doi.org/10.1145/800003.807908","url":null,"abstract":"Have you or one of your programmers said: “The system ran yesterday; I only changed one line.” or “I spent my budget, but I'm not done.” or “I fixed that problem yesterday, but it's back now.” or “I thought it would be a nice feature for the operator, so I added it to the program.” or “Why was this line of code changed? Who did it and when?”?\u0000 If these or other similar statements are familiar, then Software Configuration Management is a subject that should interest you. Software Configuration Management (SCM) is a management method that establishes a discipline for the software development process and provides visibility to that process.\u0000 The step by step procedures used by a large software organization to resolve some of their development problems will be followed here. The result of their efforts was the formulation of a management method that significantly improved the quality of their software products and reduced the costs. It was learned later that other software organizations had gone through similar processes and arrived at similar results. This new tool is now known as Software Configuration Management.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"101 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129816558","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"An alchemical approach to brokerage","authors":"Dennis M. Earle","doi":"10.1145/1010627.807903","DOIUrl":"https://doi.org/10.1145/1010627.807903","url":null,"abstract":"The essence of the commodities business is the ability to react quickly to evolving market conditions. Mocatta, a N.Y. based bullion dealer, is a firm which uses its Data Processing to provide both front office (trading) flexibility and back-office capacity to handle large volume days. The business is characterized by the constant trade-off of time against money. Corporate philosophy is to spend money to react quickly rather than to react slowly but perhaps at lower costs.\u0000 The life cycle of a system in this environment normally begins with a marketing report reflecting a new market nitch which the firm can take advantage of. Data Processing is involved almost from the inception of the idea to provide an indication of what existing systems can do for this new opportunity. Because of the nature of the business, each new product offered is usually so unique as to make it impossible for existing systems to support a new product from a trading point of view. Back-office applications are somewhat more common across products, so existing systems can usually provide some support. The key point is that all we really know is that we want to market the new product. Some idea of the time frame in which the product is to be offered is also obtained. The exact workings of defining the product and determining the parameters under which it will be traded usually remain to be worked out prior to the offering date. This therefore means that we have, at the point of commitment, the necessity for evolving data processing support in the same time frame in which the definition is evolving about what it is that we are to support.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132819714","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Structured life-cycle assumptions","authors":"T. E. Bell","doi":"10.1145/800003.807901","DOIUrl":"https://doi.org/10.1145/800003.807901","url":null,"abstract":"New programmers, some managers, and lots of users don't understand the advantages of a structured software life-cycle. However, only a single experience with coding while designing will convince any incipient software engineer that a controlled process is needed from the time of system concept though the last maintenance phase. Software Configuration Management has become almost a religion, and EDP auditors have even encountered a few systems that appear to have been specified, then designed, then implemented, then tested, and finally installed—all before maintenance and redefinition occurred. Perhaps the millennium has finally arrived, and software people will soon live in a controlled world with rational practices.\u0000 If you are tempted to believe the foregoing prediction, read the latest issue of FORTUNE, the WALL STREET JOURNAL, or COMMERCE BUSINESS DAILY and note a few problems that may divert us from the path to Nirvana. Data Processing supports commercial, educational, industrial, and governmental activities that are frequently (and repeatedly) redirected. Under circumstances of a largely random environment with thorough business planning a rarity, a critical support activity can expect to be redirected frequently. New ideas will be sliced into partly-completely DP projects, and users “analytical analyses” will become DP systems as if by magic.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131302338","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Prototyping: An approach to information and communication system design","authors":"Mitchell G. Spiegel","doi":"10.1145/800003.807904","DOIUrl":"https://doi.org/10.1145/800003.807904","url":null,"abstract":"This paper describes prototyping, a state-of-the-art methodology to assist a design team in making a through definition and analysis of new requirements, feasibility, alternative selections, workload impact, system and/or application specification, implementation, and testing. Suggested prototype tools and techniques are presented, and guidance is included to aid a design team in obtaining accurate and timely results. This paper is not intended to be a complete text on design. It should be enhanced with a design team's expertise, consultation from sources with design experience, and reference to other design literature.\u0000 Prototyping is a process (the act, study, or skill) of modeling an information-communication system architecture in one or more levels of detail, using descriptive models, abstract models, and working models of the system and its component parts (synonym: archetyping).\u0000 This work was completed while the author was working with prior employers.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"650 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132023383","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Data space testing","authors":"M. Paige","doi":"10.1145/800003.807916","DOIUrl":"https://doi.org/10.1145/800003.807916","url":null,"abstract":"A complete software testing process must concentrate on examination of the software characteristics as they may impact reliability. Software testing has largely been concerned with structural tests, that is, test of program logic flow. In this paper, a companion software test technique for the program data called data space testing is described.\u0000 An approach to data space analysis is introduced with an associated notation. The concept is to identify the sensitivity of the software to a change in a specific data item. The collective information on the sensitivity of the program to all data items is used as a basis for test selection and generation of input values.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132741635","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"An approach to software configuration control","authors":"W. Bryan, S. Siegel, Gary L. Whiteleather","doi":"10.1145/800003.807907","DOIUrl":"https://doi.org/10.1145/800003.807907","url":null,"abstract":"The purpose of this paper is to discuss the process by which a system's life cycle and its associated life cycle products are managed to ensure the quality and integrity of the system. We call this process configuration control. Although many of the ideas in this paper are applicable to systems in general, the focus of this paper is on configuration control of systems with software content.\u0000 It is becoming apparent to many, in both government and private industry, that the high cost of maintenance of existing computer systems may be attributed to poor configuration control early in the system's life cycle. For example, in an article entitled \"A Corporate Road, Map for Systems Development in the '80s, the following claim appears,","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134498661","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Some experimental estimators for developmental and delivered errors in software development projects","authors":"V. Schneider","doi":"10.1145/800003.807925","DOIUrl":"https://doi.org/10.1145/800003.807925","url":null,"abstract":"Experimental estimators are presented relating the expected number of software problem reports (B) in a software development project to\u0000 the overall reported professional effort (E) in “man months”\u0000 the number of subprograms (n)\u0000 the overall count of thousands of coded source statements of software(S).\u0000 [equation]\u0000 These estimators are shown to be consistent with data obtained from the Air Force's Rome Air Development Center, the Naval Research Laboratory, and Japan's Fujitsu Corporation. Although the results are promising, more data is needed to support the validity of these estimators.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121363209","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A software study using Halstead metrics","authors":"C. Bailey, W. L. Dingee","doi":"10.1145/800003.807928","DOIUrl":"https://doi.org/10.1145/800003.807928","url":null,"abstract":"This paper describes an application of Maurice Halstead's software theory to a real time switching system. The Halstead metrics and the software tool developed for computing them are discussed. Analysis of the metric data indicates that the level of the switching language was not constant across algorithma and that software error data was not a linear function of volume.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121890041","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"On the relationships among three software metrics","authors":"S. Henry, D. Kafura, K. Harris","doi":"10.1145/800003.807911","DOIUrl":"https://doi.org/10.1145/800003.807911","url":null,"abstract":"Automatable metrics of software quality appear to have numerous advantages in the design, construction and maintenance of software systems. While numerous such metrics have been defined, and several of them have been validated on actual systems, significant work remains to be done to establish the relationships among these metrics. This paper reports the results of correlation studies made among three complexity metrics which were applied to the same software system. The three complexity metrics used were Halstead's effort, McCabe's cyclomatic complexity and Henry and Kafura's information flow complexity. The common software system was the UNIX operating system. The primary result of this study is that Halstead's and McCabe's metrics are highly correlated while the information flow metric appears to be an independent measure of complexity.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126768884","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Specification of a regression test for a mini computer operating system","authors":"Patricia R. Cox","doi":"10.1145/800003.807906","DOIUrl":"https://doi.org/10.1145/800003.807906","url":null,"abstract":"In this paper I describe the practical problems of designing a regression test set for an existing mini-computer operating system. The ideal regression test would test each function with all possible combinations of the options for each variation of the operating system. This is impractical if not impossible so the alternative is to choose the individual cases for maximum coverage. To do that the system is viewed both functionally and structurally and cases are selected for inclusion in the test set. The method of selecting the tests is described along with the tools that will be needed to measure the coverage and to maintain the test set.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122127880","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}