Software engineering and Ada in design

Modern software engineering promises significant reductions in software costs and improvements in software quality. The Ada language is the focus for these software methodology and tool improvements. The IBM FSD approach, including the software engineering practices that guide the systematic design and development of software products and the management of the software process are examined. The revised Ada design language adaptation is revealed. This four level design methodology is detailed including the purpose of each level, the management strategy that integrates the software design activity with the program milestones, and the technical strategy that maps the Ada constructs to each level of design. A complete description of each design level is provided along with specific design language recording guidelines for each level. Finally, some testimony is offered on education, tools, architecture, and metrics resulting from project use of the four level Ada design language adaptation

Software unit testing in Ada environment

A validation procedure for the Ada binding of the Graphical Kernel System (GKS) is being developed. PRIOR Data Sciences is also producing a version of the GKS written in Ada. These major software engineering projects will provide an opportunity to demonstrate a sound approach for software testing in an Ada environment. The GKS/Ada validation capability will be a collection of test programs and data, and test management guidelines. These products will be used to assess the correctness, completeness, and efficiency of any GKS/Ada implementation. The GKS/Ada developers will be able to obtain the validation software for their own use. It is anticipated that this validation software will eventually be taken over by an independent standards body to provide objective assessments of GKS/Ada implementations, using an approach similar to the validation testing currently applied to Ada compilers. In the meantime, if requested, this validation software will be used to assess GKS/Ada products. The second project, implementation of GKS using the Ada language, is a conventional software engineering tasks. It represents a large body of Ada code and has some interesting testing problems associated with automatic testing of graphics routines. Here the normal test practices which include automated regression testing, independent quality assistance, test configuration management, and the application of software quality metrics will be employed. The software testing methods emphasize quality enhancement and automated procedures. Ada makes some aspects of testing easier, and introduces some concerns. These issues are addressed

Defining Software Quality Measures: A Systematic Approach Embedded in the Objectives, Principles, Attributes Framework

Currently, software quality measures and metrics are being developed in isolation and often without the benefit of a guiding framework. In this paper we describe a systematic process for identifying measurement approaches and defining corresponding metrics that definitively support software quality assessment. That systematic process embodies five well-defined steps that reflect quality assessment within a framework which links the achievement of desirable software engineering objectives to the use of appropriate principles, and the use of principles to the manifestation of desirable product attributes. Ada is the language we have chosen to examine; the Ada package is used to illustrate the identification and definition process

Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

Software development: A paradigm for the future

A new paradigm for software development that treats software development as an experimental activity is presented. It provides built-in mechanisms for learning how to develop software better and reusing previous experience in the forms of knowledge, processes, and products. It uses models and measures to aid in the tasks of characterization, evaluation and motivation. An organization scheme is proposed for separating the project-specific focus from the organization's learning and reuse focuses of software development. The implications of this approach for corporations, research and education are discussed and some research activities currently underway at the University of Maryland that support this approach are presented

Pengukuran kualitas kode program berorientasi objek dengan menggunakan metrik chidamber dan kemerer dilihat dari aspek maintainability, efficiency understandability dan replaceability (studi kasus software accounting XYZ)

Peningkatan kualitas sebuah perangkat lunak mempunyai peran yang penting dalam praktek rekayasa perangkat lunak. Pendekatan engineering menginginkan bahwa kualitas perangkat lunak dapat diukur secara kuantitatif dalam bentuk angka yang dapat dipahami oleh orang lain. Object Oriented Programming (OOP) seringkali menjadi pilihan pengembang dalam membangun perangkat lunak. Pengukuran kualitas software berdasarkan aspek object oriented dengan menggunakan Metrik Chidamber dan Kemerer. Metrik tersebut mempunyai enam metrik di dalamnya yaitu Weighted Method per Class (WMC), Depth of Inheritance Tree (DIT), Number OF Children (NOC), Response For a Class (RFC), Coupling Between Object Classes (CBO) dan Lack of Cohesion Method (LCOM). understandability, reusability, dan maintainability/testability. Sehingga pengembang software dapat mengetahui sejauh mana kualitas konsep object oriented yang ada pada kode perangkat lunak tersebut. Hasil akhir yang diharapkan dari tugas akhir ini adalah perbaikan kode program berupa class diagram yang lebih baik berdasarkan kualitas yang telah dipilih. ============================================================================================================= Improving the quality of a software has an important role in the practice of software engineering. Engineering approach wants that the quality software can be measured quantitatively in the form of numbers that can be understood by others. Object Oriented Programming (OOP) is often the choice of the developer in building software. Quality measurement based on aspects of object-oriented software using Chidamber Metrics and Kemerer. Metrics Chidamber and Kemerer has six metric. The metric are weighted Method per Class (WMC), Depth of Inheritance Tree (DIT), Number OF Children (NOC), Response For a Class (RFC), Coupling Between Object Classes (CBO), and Lack of Cohesion Method (LCOM). Quality characteristics that can be measured using this metric is based on ISO / IEC 9126-1 are efficiency, understandability, reusability, and maintainability / testability. So the software developers can determine the quality of objectoriented concepts that exist in the software code. Final results are expected from this thesis are improvement of program code in the form of a better class diagram based on the quality that has been selected

Reverse Engineering of Computer-Based Navy Systems

The financial pressure to meet the need for change in computer-based systems through evolution rather than through revolution has spawned the discipline of reengineering. One driving factor of reengineering is that it is increasingly becoming the case that enhanced requirements placed on computer-based systems are overstressing the processing resources of the systems. Thus, the distribution of processing load over highly parallel and distributed hardware architectures has become part of the reengineering process for computer-based Navy systems. This paper presents an intermediate representation (IR) for capturing features of computer-based systems to enable reengineering for concurrency. A novel feature of the IR is that it incorporates the mission critical software architecture, a view that enables information to be captured at five levels of granularity: the element/program level, the task level, the module/class/package level, the method/procedure level, and the statement/instruction level. An approach to reverse engineering is presented, in which the IR is captured, and is analyzed to identify potential concurrency. Thus, the paper defines concurrency metrics to guide the reengineering tasks of identifying, enhancing, and assessing concurrency, and for performing partitioning and assignment. Concurrency metrics are defined at several tiers of the mission critical software architecture. In addition to contributing an approach to reverse engineering for computer-based systems, the paper also discusses a reverse engineering analysis toolset that constructs and displays the IR and the concurrency metrics for Ada programs. Additionally, the paper contains a discussion of the context of our reengineering efforts within the United States Navy, by describing two reengineering projects focused on sussystems of the AEGIS Weapon System

Experiments with Ada

A 1200-line Ada source code project simulating the most basic functions of an operations control center was developed. We selected George Cherry's Process Abstraction Methodology for Embedded Large Applications (PAMELA) and DEC's Ada Compilation System (ACS) under VAX/VMS to build the software from requirements to acceptance test. The system runs faster than its FORTRAN implementation and was produced on schedule and under budget with an overall productivity in excess of 30 lines of Ada source code per day

Annotated bibliography of software engineering laboratory literature

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory-software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. Subject and author indexes further classify these documents by specific topic and individual author

Annotated bibliography of software engineering laboratory literature

An annotated bibliography is presented of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. The bibliography was updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials were grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. Subject and author indexes further classify these documents by specific topic and individual author