Software development for flexible pavement thickness design based on aastho and road note 31

Nowadays, road and surface failure has become a critical issue in our country on the flexible pavement which reflects to a bad quality and error during design stage. The thickness design of flexible pavement has become crucial element in the overall efficiency of highway structure system to give a good performance and high serviceability under a traffic loading during the expected design period. The objectives of this study are to develop flexible pavement thickness design software for AASHTO and Road Note 31 by using Visual Basic 6.0. The result comparison between both methods was carried out shown in different of thickness and different percentage of cost evaluations between AASHTO and Road Note 31. This computer software could produce the design thickness of each layer for flexible pavement structure in graphical layout for both design methods. Therefore, the users can easily analyze and compared the result obtained to select the best design alternative between AASHTO and Road Note 31 based on cost and thickness different. The result analysis obtained from this computer software also can be saved and view in a report file to be printed or keep as soft copy for reference in the future. Besides, the result analysis obtained by this computer software is also been compared with the manual calculation (theory) and shown that the computer software has the same and exact result with the manual calculation (theory). Thus, the performance of this computer software was successful tested and validated. Therefore, computer software of flexible pavement thickness design is a very useful tool in highway engineering especially to design the thickness of flexible pavement. By applying the computer program, the design stage can be made in a very short time period of design process and help to minimize the error factor compare to manual calculation or conventional method. Computer software also can give a high accuracy and quality of result for pavement thickness design

Computer Software Management and Information Center

Computer programs for passive anti-roll tank, earth resources laboratory applications, the NIMBUS-7 coastal zone color scanner derived products, transportable applications executive, plastic and failure analysis of composites, velocity gradient method for calculating velocities in an axisymmetric annular duct, an integrated procurement management system, data I/O PRON for the Motorola exorcisor, aerodynamic shock-layer shape, kinematic modeling, hardware library for a graphics computer, and a file archival system are documented

Practical State Machines for Computer Software and Engineering

This paper introduces methods for describing properties of possibly very large state machines in terms of solutions to recursive functions and applies those methods to computer systems

Specifications and programs for computer software validation

Three software products developed during the study are reported and include: (1) FORTRAN Automatic Code Evaluation System, (2) the Specification Language System, and (3) the Array Index Validation System

Non rivalry and complementarity in computer software

In this paper we contend that – contrary to what argued by a vast part of the literature – computer software and, more in general, digital goods (i.e. symbolic strings on an electronic medium with some eco- nomic value) do not present the characteristics of a public good as they do not suffer from lack of rivarly and excludability any more than other durable goods which are regularly allocated on competitive markets. We argue instead that the “market allocation problem” – if any – with digital goods does not arise from their public nature but from some pe- culiar characteristics of the production technology. The latter presents the nature of a typical problem solving activity as far as the produc- tion of the first unit is concerned, this means that innovative activities in computer software are characterized by high degrees of interdepen- dencies, cumulativeness, sequentiality, path dependence and, more in general, sub-optimality arising from imperfect problem decompositions. As far as the production of further units is concerned, we observe in- stead high (but not infinite) expansibility and perfect codification (lack of any tacit dimension) which make diffusion costs rapidly fall. Given such claims, we argue that a standard “Coasian” approach to property rights, designed to cope with the externalities of semi-public goods may not be appropriate for computer software, as it may decrease both ex-ante incentives to innovation and ex-post efficiency of diffusion. On the other hand the institutional definition of property rights may strongly influence the patterns of technological evolution and division of labor in directions which are not necessarily optimal.Intellectual property; hierarchies; innovation; software; digital goods

State machines for large scale computer software and systems

A method for specifying the behavior and architecture of discrete state systems such as digital electronic devices and software using deterministic state machines and automata products. The state machines are represented by sequence maps $f:A^*\to X$ where $f(s)=x$ indicates that the output of the system is $x$ in the state reached by following the sequence of events $s$ from the initial state. Examples provided include counters, networks, reliable message delivery, real-time analysis of gates and latches, and producer/consumer. Techniques for defining, parameterizing, characterizing abstract properties, and connecting sequence functions are developed. Sequence functions are shown to represent (possibly non-finite) Moore type state machines and general products of state machines. The method draws on state machine theory, automata products, and recursive functions and is ordinary working mathematics, not involving formal methods or any foundational or meta-mathematical techniques. Systems in which there are levels of components that may operate in parallel or concurrently are specified in terms of function composition

Detection and avoidance of errors in computer software

The acceptance test errors of a computer software project to determine if the errors could be detected or avoided in earlier phases of development. GROAGSS (Gamma Ray Observatory Attitude Ground Support System) was selected as the software project to be examined. The development of the software followed the standard Flight Dynamics Software Development methods. GROAGSS was developed between August 1985 and April 1989. The project is approximately 250,000 lines of code of which approximately 43,000 lines are reused from previous projects. GROAGSS had a total of 1715 Change Report Forms (CRFs) submitted during the entire development and testing. These changes contained 936 errors. Of these 936 errors, 374 were found during the acceptance testing. These acceptance test errors were first categorized into methods of avoidance including: more clearly written requirements; detail review; code reading; structural unit testing; and functional system integration testing. The errors were later broken down in terms of effort to detect and correct, class of error, and probability that the prescribed detection method would be successful. These determinations were based on Software Engineering Laboratory (SEL) documents and interviews with the project programmers. A summary of the results of the categorizations is presented. The number of programming errors at the beginning of acceptance testing can be significantly reduced. The results of the existing development methodology are examined for ways of improvements. A basis is provided for the definition is a new development/testing paradigm. Monitoring of the new scheme will objectively determine its effectiveness on avoiding and detecting errors

NASTRAN distribution through COSMIC

The NASTRAN program package is one of the most important in terms of size and use in the COSMIC inventory at the University of Georgia. A brief history of the COSMIC facility as it relates to the NASTRAN program package is presented, followed by a discussion of the NASTRAN disseminations. COSMIC, which is the acronym for the Computer Software Management and Information Center, is operated by the University of Georgia's Computer Center under contract to NASA. The purpose of COSMIC is to make available to the public the computer software and documentation developed as part of the NASA program. It is, perhaps, best described as a clearinghouse for the NASA-sponsored computer software, although the functions specified under the contract go much further than simply duplicating the programs and documentation for distribution. A sizeable portion of the workscope involves screening the programs to insure that they are free of syntax errors, that all necessary subroutines are present, and that the documentation includes sufficiently detailed instructions to allow purchasers to install and operate the program or system

Development of a computer software for the monitoring of subsidence

A computer software has been developed at the Faculty of Geoinformation Science and Engineering, UTM for the purpose of detecting subsidence of ground surface or manmade structure by using Visual Basic 6.0 and FORTRAN computer languages. This software can be used for processing data from GPS and precise levelling methods. The software requires GPS baseline vectors (∆X, ∆Y, ∆Z). Relative ellipsoidal heights based on the WGS84 ellipsoidal surface must be derived from these baseline vectors. The derived relative ellipsoidal heights are then adjusted using least square estimation method. The adjusted heights will be used for further subsidence analysis. Stransformation is used to transform results from least square estimation using minimum constraints to a selected datum. This paper examines the method of subsidence using the iterative weighted transformation. In this method, the stability of reference points must be checked through a single point test. Stable points will then be adjusted again together with object points. Lastly, the stability of object points will be determined. User of this software requires little knowledge on deformation monitoring processing, as the user needs to follow the procedure of inputting data required by the software. The output from the software will give the stability of the all control points whether they have moved or otherwise