Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “software development environment”
ATLAS Software Development Environment Working Group · CERN Bulletin · 1996
The user requirements for the ATLAS software development environment are presented.It is intended that this environment should meet the needs of all software developers within ATLAS for the next two years.
Cited by 0Open access
Larysa Globa, T. N. Kot · 2008
The article deals with the compare of standard, new suggested information system (IS) development logical stages and realizing IS like system based on multithread processing. Developed systems, functioning in the telecommunication environment, which provides access to different services working separately and often being physically distributed, canpsilat be designed as single thread application. Standard and suggested stages are integrated; new CASE-toolkit is being developed for high-quality IS development in the shortest time. The main features of such toolkit is support of prototyping, early testing, analysis, easy reengineering, computing processes in distributed IS optimization and multithread computing in global environment including wireless channels. The work includes some new and fundamental approaches and suggests specific concepts to IS development.
Cited by 0
User's Manual Paul, Paul Z. Kolano · 2008
Cited by 0
William E. Riddle · NASA STI Repository (National Aeronautics and Space Administration)
The current status in the area of software development environments is assessed. The purposes of environments, the types of environments, the constituents of an environment, the issue of environment integration, and the problems which must be solved in preparing an environment are discussed. Some general maxims to guide near-term future work are proposed.
Cited by 0Open access
Káthia Marçal de Oliveira, Fábio Zlot, Ana Regina Rocha et al. · Journal of Systems and Software · 2003
Cited by 34
Michel Izygon · NASA STI Repository (National Aeronautics and Space Administration) · 2013
The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment
Cited by 0Open access
Rubens Machado, André Vital Saúde, Roberto Lotufo · LA Referencia (Red Federada de Repositorios Institucionales de Publicaciones Científicas) · 2003
This paper presents the Adesso, a computational environment for the development of scientific software. The Adesso environment leverages the reusable software component programming model to support the development and integration of components to several scientific programming platforms. The Adesso system is based on an XML component database and a set of XML document transformation tools for the automatic generation of component code, documentation and packaging. An authoring tool, built with the help of the Adesso transformation system itself, is provided to assist the user in the creation of components. The Adesso system has been used for the development of several image processing toolboxes and applications. Some of them are presented briefly in this paper.
Cited by 3Open access
Pornsiri Muenchaisri, Toshimi Minoura · 2003
We designed and implemented a prototype software development environment based on software component composition. Our software development environment, the Entity-Relationship Software Development Environment (ERSDE), uses extended entity-relationship diagrams (EERDs) as templates of executable programs. An EERD represents the component types and the relationship types among them within an application domain. The graphical editor of the ERSDE uses an EERD as a menu in constructing application software. An EERD used as a menu can enforce legitimate patterns of relationships among software components, in addition to providing an intuitive view of available components and possible relationships among them. Furthermore, as the ERSDE uses structural active objects as the components of a program, we can obtain an executable program if those components are instantiated and interconnected as dictated by an EERD. Two experiments conducted confirmed the effectiveness of our approach.
Cited by 0
Kuniko INOUE, Yoshitaka Miyazaki · Journal of the Japan Society for Precision Engineering · 1992
Cited by 0Open access
Zeynep Konuralp · OpenMETU (Middle East Technical University) · 2007
A software process improvement study is presented. The literature on software development processes and their improvement is reviewed. The current peer review process at Software Engineering Directorate of the X Company, Ankara, Türkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author’s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.
Cited by 1Open access
Diogo da Silva Amaral · Open Repository of the University of Porto (University of Porto) · 2018
Cited by 0Open access
Thomas J. Aird, D. G. Kainer · ACM SIGNUM Newsletter · 1978
IMSL has developed a set of macros and a file naming convention that automates the subroutine development and testing process over ten computer types. The IMSL software development system is implemented on a Data General Eclipse C330 computer with 256K bytes of central memory and 192M bytes of disk storage using the AOS Operating System. RJE activity is handled by a Data 100 communications computer. The system allows the programmer to work with basis decks. Distribution decks are generated, by the IMSL Fortran converter, as they are needed for testing and whenever the basis deck has been modified.
Cited by 3Open access
P. Heinicke, Tom Nicinski, P. Constanta-Fanourakis et al. · IEEE Transactions on Nuclear Science · 1987
Experimenters on over 30 DECnet nodes at Fermilab use software developed, distributed, and maintained by the Data Acquisition Software Group. A general methodology and set of tools have been developed to distribute, use and manage the software on different sites. The methodology and tools are of interest to any group developing and using software on multiple nodes.
Cited by 0
Falbo, Ricardo de Almeida, Natali, Ana Candida Cruz, Mian, Paula Gomes et al. · El Servicio de Difusión de la Creación Intelectual (National University of La Plata) · 2003
Software tools processing partially common set of data should share an understanding of what these data mean. Since ontologies have been used to express formally a shared understanding of information, we argue that they can be used to improve integration in Software Engineering Environments (SEE). In this paper we discuss an ontology-based approach to improve tool integration and present ODE, an ontology-based SEE.
Cited by 9Open access
David Hutchison, Jonathan Walpole · Lancaster EPrints (Lancaster University) · 1986
Eclipse is an integrated project support environment (IPSE) whose purpose is to support the development of software systems from the specification stage through to their operation and maintenance. It is being developed by a consortium of universities and companies with funding from the UK Science and Engineering Research Council and the national Alvey programme. Eclipse is a distributed IPSE using high-powered workstations and both local and wide area networks. This paper presents an overview of the Eclipse project and a more detailed description of Eclipse's distributed architecture.
Cited by 1
Richard M. Reese · OakTrust (Texas A&M University Libraries) · 1983
This paper presents the design and prototype implementation of a language directed Software Development Environment (SDE) which permits the hiding of developmental information, provides a flexible means of control of the system, and provides a framework for the support of various software development methodologies. This language directed SDE, which is based upon an underlying system framework called Design Plans (DP), provides flexible support to the user, and allows for the hiding of developmental information. Design plans are similar to procedures found in many high level languages. Design plans in the SDE developed in this research, however, interface closely with underlying Databases (DB). These DBs provide a means of storing and accessing environmental knowledge concerning the software project under development. The definition of the DB structure is given within the DPs in terms of components and elements which are the basic building blocks of the DB. Design plans are intended to be used in implementing software development methodologies in conjunction with the command language of the system and various support tools. It has been shown in this research that design plans can be constructed in such a manner so as to relieve the user of the necessity of entering many explicit commands. The language designed in this research for the implementation of DPs is divided into three groups. The first group is the command group which provides the primary interface to the SDE by the user. A DB access group provides query type access to the DB while the third, a programming language group, utilizes structured constructs to tie the DPs together. A prototype SDE was developed to demonstrate the hiding concepts and to provide insight into the design of a production SDE. The prototype was designed specifically to support simulation software development. It is implemented on a Texas Instruments 990/12 minicomputer in PASCAL. The support tools in the prototype include an integration of preexisting facilities with tools developed specifically for inclusion in this SDE. Sample scenarios using design plans and database components and elements are presented. Conclusions based on the experiences in this research are given along with suggestions for future work.
Cited by 1
Herbert Weber · Informatik-Fachberichte · 1985
Cited by 0
Madeline Wright, Carl J. Mueller · 2014
Abstract : The goal of this paper is that configuration management is a simple and cost effective method to secure the development environment without impeding innovation, creativity, or schedule. Software development is a business, and it is reasonable to assume both developers and customers want systems that are protected because there will always be attempts to gain access to software and the data/information residing in the computer systems.
Cited by 0
T. J. Aird, D. G. Kainer · 1979
IMSL has developed a set of macros and a file naming convention that automates the subroutine development and testing process over ten computer types. The IMSL software development system is implemented on a Data General Eclipse C330 computer with 256K bytes of central memory and 192M bytes of disk storage using the AOS Operating System. RJE activity is handled by a Data 100 communications computer. The system allows the programmer to work with basis decks. Distribution decks are generated, by the IMSL Fortran converter, as they are needed for testing and whenever the basis deck has been modified.
Cited by 0
P. Heinicke, Tom Nicinski, P. Constanta-Fanourakis et al. · 1987
Experimenters on over 30 DECnet nodes at Fermilab use software developed, distributed, and maintained by the Data Acquisition Software Group. A general methodology and set of tools have been developed to distribute, use and manage the software on different sites. The methodology and tools are of interest .to any group developing and using software on multiple nodes.
Cited by 0Open access