J. Fairclough, R. Blake, I. Alexander, J. Wheadon, C. Mazza
{"title":"Graduating from a defined software development process to a managed process -a case history","authors":"J. Fairclough, R. Blake, I. Alexander, J. Wheadon, C. Mazza","doi":"10.1109/SESS.1993.263971","DOIUrl":"https://doi.org/10.1109/SESS.1993.263971","url":null,"abstract":"The Software Cost and Resources Assessment Tool (SOCRAT) project was initiated by the European Space Operations Centre (ESOC) in October 1991 to investigate the factors that affect dedicated control system (DCS) costs and to construct a prototype cost estimation tool. Logica were contracted to perform the study and delivered the first SOCRAT in April 1992. The SOCRAT project is important because it shows what organisations can do once they have established a software development process model, and design their systems around reusable software components. Humphreys (1989) characterised the transition from the 'defined process' to the 'managed process' by the attempt to cost the steps in the development process. The paper gives a practical demonstration of how this can be done.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"380 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122924160","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":"Safety assessment test for automated ground transportation systems' software","authors":"R. Rizzo, M. Speciale","doi":"10.1109/SESS.1993.263935","DOIUrl":"https://doi.org/10.1109/SESS.1993.263935","url":null,"abstract":"Software (SW) quality evaluation standards are oriented to every type of SW package or product; there are specific applications that need particular tests to certify the fail-safety and fault tolerance. The proposed testing method is a boundary one, and follows a general philosophy: the input signal set is divided into two subsets: the admissible subset and the non-admissible subset. The second subset contains both signals whose value is greater (or smaller) than the admissible limit, and signals that are contradictory or unstable. Practically it is possible to do this starting from a cause-effect graph, from which it derives the matrix whose rows will report every status and the columns will report every possible class of data input. An example of micro controller electrical drive code is reported.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133731103","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":"Developing a structured set of standards (software engineering)","authors":"R. Stevens, A. Scheffer","doi":"10.1109/SESS.1993.263969","DOIUrl":"https://doi.org/10.1109/SESS.1993.263969","url":null,"abstract":"Standards need to be short, coherent, readable and easy to change. In practice, these goals are hard to achieve, because the underlying information is complex and interrelated. Common mistakes in developing standards include over-large documents, unreadable style, mixed levels of abstraction, lack of structure across sets of documents, and repetition of information across different standards. The European Space Agency (ESA) has been developing a structured set of software engineering standards, and the experience is abstracted to help future standards writers. Many principles were followed subconsciously while developing the ESA standard, but have become clearer in retrospect. A systematic approach should make for a better product with less effort.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131070194","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":"Intelligence in network management: methodological approach","authors":"Simon Znaty, Dept Rbeaux","doi":"10.1109/SESS.1993.263955","DOIUrl":"https://doi.org/10.1109/SESS.1993.263955","url":null,"abstract":"Network management is rapidly becoming one of the most pressing problems in data communications as networks continue to grow at a rapid pace, new network technologies are introduced, and more varied network services are offered. Advanced technologies must be used to provide the software and tools needed to create, operate, control and manage these networks. The article proposes a methodology which utilizes the object as a unique and continuous support from analysis to implementation of network management applications.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"79 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115167273","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":"Process thru Pictures","authors":"S. Hegde, S. Ryburn","doi":"10.1109/SESS.1993.263965","DOIUrl":"https://doi.org/10.1109/SESS.1993.263965","url":null,"abstract":"The paper describes a process re-engineering technique designed to deliver high-quality software products in less time than using other methods. It describes how a 'Process thru Pictures (PtP)' technique was developed and applied to re-engineer processes at Bull Information Systems. It summarizes results, lessons learned, and plans, and includes an illustration of PtP use. Based on the success of this technique, the authors recommend that colleagues in the software industry focus on pictorial techniques to re-engineer processes.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121265600","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":"Using abstractions to build standardized components for enterprise models","authors":"B. Work, A. Balmforth","doi":"10.1109/SESS.1993.263954","DOIUrl":"https://doi.org/10.1109/SESS.1993.263954","url":null,"abstract":"Architectural methods, such as information engineering, are the most comprehensive and intellectually rigorous means of information systems planning. Despite their many virtues though, there remain difficulties with both their theory and their practice. In particular, there are numerous problems associated with enterprise modeling which is at the heart of these methods. Current techniques are inflexible, cumbersome, and lack theoretical underpinning. But, most of all, they are laborious and time-consuming. One reason why enterprise modeling takes so long is that traditional techniques begin with 'a blank sheet of paper'. Instead it might be possible to use standardized components in order to compile a draft model. Since these components may be used again and again, they need a rigorous basis. Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116754230","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":"Industrial acceptance of software quality assurance standards","authors":"C. J. Davis, J. B. Thompson, P. Smith","doi":"10.1109/SESS.1993.263950","DOIUrl":"https://doi.org/10.1109/SESS.1993.263950","url":null,"abstract":"Research programmes are currently being undertaken at the University of Sunderland in the area of Commercial and Industrial Practices within the UK with regard to software production. These programmes have involved extensive surveys of current approaches to software development and quality assurance. The paper reviews the developments that have taken place within the UK during the last 10 years in the field of quality assurance related to software production and presents major findings from surveys and research investigations. This includes information on the actual use and adoption of quality assurance approaches, and the use of first, second and third party quality assurance standards. The paper finally presents proposals relating to the greater acceptance of quality assurance standards within organisations.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123117636","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":"Quality standards: the role of Software Process Assessments","authors":"S. E. Miller, G. T. Tucker, A. Verducci","doi":"10.1109/SESS.1993.263940","DOIUrl":"https://doi.org/10.1109/SESS.1993.263940","url":null,"abstract":"Software Process Assessments (SPA) are used by organizations in AT&T to develop an organizational baseline and to drive continuous process improvement. They also play an important role in the establishment of quality standards for both the organization and AT&T. The paper describes the assessment process and discusses how the findings of an assessment support quality initiatives within the organizations, as well as across AT&T. The assessment findings provide a detailed evaluation of the software processes used by an organization and the effectiveness of those processes. While the primary purpose of an assessment is to drive process improvement, the findings can also be used to help establish quality standards and to prepare for a quality system audit.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125083415","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":"AUSTERE: a system for AUtomated STandard softwarE REview","authors":"S. Fabrizi, R. Procopio, D. Russo","doi":"10.1109/SESS.1993.263936","DOIUrl":"https://doi.org/10.1109/SESS.1993.263936","url":null,"abstract":"Since 1988 the Banca d'Italia has had a software quality system, based on UNI EN 2900x standard (derived from ISO 9000), which defines methods, techniques and tools required for the production process and software control. The paper describes a prototype (AUSTERE) for quality control automation and standardization.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132210013","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":"Specifying joint behavior of objects: formalization standardization","authors":"H. Kilov, Bellcore, Laura, Redmann","doi":"10.1109/SESS.1993.263948","DOIUrl":"https://doi.org/10.1109/SESS.1993.263948","url":null,"abstract":"To understand a large and complicated system, its specifier and user should be able to separate essential concerns from irrelevant details. To do that, specification of behavioral semantics-as opposed to just signatures (i.e., syntax)-is essential. Abstract and precise specifications are the corner stones of object modeling. However, object modeling has usually considered only behavior of isolated objects. Real-world enterprises do not consist only of isolated objects. It is the joint behavior of associated objects that defines the object model of the enterprise and therefore makes the business understandable. The paper show how semantics of an information model (the result of analyzing the system) can be specified in an abstract and precise manner, by reusing programming methodology concepts, and how this approach to specification is used in standardization activities.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129083881","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}