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 “large software systems”
J. R. Abrial · Cambridge University Press eBooks · 1996
A summary is not available for this content so a preview has been provided. Please use the Get access link above for information on how to access this content.
Cited by 0
George C · 2015
Developers turn ideas, designs and patterns into source code, then compile the source code into executables. De-compiling turns executables back into source code, and deprogramming turns code back into designs and pat-terns. In this paper we introduce DeP, a tool for depro-gramming software systems. DeP abstracts code into a dependency graph and mines this graph for patterns. It also gives programmers visual means for manipulating the program. We describe DeP’s use in several software engineering tasks: design pattern identification, source code refactoring, copy-paste detection, automated code documentation, and programmer fingerprint recognition. 1
Cited by 0
L. A. Belady · Lecture notes in computer science · 1982
Cited by 3
Turku Centre, Computer Science, Mikołaj Olszewski et al. · 2013
Cited by 0
C. V. Ramamoorthy, S. F. Ho · ACM SIGPLAN Notices · 1975
In the past few years, research has been actively carried out in an attempt to improve the quality and reliability of large scale software systems. Although progress has been made on the formal proof of program correctness, proving large scale software systems correct by formal proof is still many years away. Automated software tools have been found to be valuable in improving software reliability and attacking the high cost of software systems. This paper attempts to describe some main features of automated software tools and some software evaluation systems that are currently available.
Cited by 127Open access
Using The Uml Notation, Surendranath Ramasubbu, Surendranath Ramasubbu · 2001
Cited by 0
Gail E. Kaiser, Yoelle Maarek, Dewayne E. Perry et al. · Columbia Academic Commons (Columbia University) · 1987
This technical report consists of the three related papers. Living with Inconsistency in Large Systems describes CONMAN, an environment that identifies and tracks version inconsistencies, permitting debugging and testing to proceed even though the executable image contains certain non-fatal inconsistencies. The next two papers are both from the INFUSE project. Change Management for Very Large Software Systems presents the new non-Euclidean hierarchical clustering algorithm used by the INFUSE change management system to cluster modules according to the strengths of their interdependencies. Models of Software Development Environments presents a general model of software development environments consisting of three components - policies, mechanisms and structures - and classifies existing and proposed environments into the individual, family, city and state classes according to the size of projects that could be adequately supported.
Cited by 0Open access
R. Geoff Dromey · 2007
Summary form only given. There are four major threats to successfully building large-scale software-intensive systems: (1) a failure to control the complexity that arises during the development process (2) a failure to achieve early resolution of deficiencies in informal statements/knowledge of stakeholders' needs (3) failure to construct a system that satisfies stakeholders' needs, and (4) a failure to effectively organize the project team. All four of these threats can be very significantly reduced by making maximum and effective use of the requirements information that expresses stakeholders' needs. This is achieved by choosing a representation that supports rigorous formalization and composition of individual requirements one at a time into an integrated, state-based, graphical view. It amounts to building a system 'out of' its requirements. The justification for, the processes, representations and results of applying this constructive approach to tackling the core problems associated with developing large-scale, dependable systems is presented.
Cited by 4
Christof Ebert, Thomas Liedtke · 2007
: Quality improvement such as increased reliability and maintainability are of utmost importance in software development. In this field, which was previously ad hoc and unpredictable rather than customer oriented, increasing competition and decreasing customer satisfaction have motivated management to put more emphasis on quality issues. Failures in telecommunication systems recently showed that low software quality in such a sensible field has much more effect than defects located to a distinct application. This paper provides insight in techniques for reliability prediction as they are applied within the development of Alcatel 1000 S12 switching software. Release time prediction and field performance prediction are both based on tailored ENHPP reliability models. For the complete approach of criticality prediction recent data from the development of a switching system with around 2 MLOC is provided. The switching system is currently in operational use thus allowing for validation an...
Cited by 0
Christof Ebert, Thomas Liedtke, Ekkehard Baisch · Annals of Software Engineering · 1999
Cited by 7
Richard W. Selby · 2005
Cited by 3
Luqi, Berzins, Valdis · Calhoun: The Naval Postgraduate School Institutional Archive (Naval Postgraduate School) · 1987
Author-contributed print item
Cited by 0
Robert G. Munck · 1985
Cited by 0
G. A. Kohring · Advances in Complex Systems · 2009
Two large, open source software systems are analyzed from the vantage point of complex adaptive systems theory. For both systems, the full dependency graphs are constructed and their properties are shown to be consistent with the assumption of stochastic growth. In particular, the afferent links are distributed according to Zipf's law for both systems. Using the small-world criterion for directed graphs, it is shown that contrary to claims in the literature, these software systems do not possess small-world properties. Furthermore, it is argued that the small-world property is not of any particular advantage in a standard layered architecture. Finally, it is suggested that the eigenvector centrality can play an important role in deciding which open source software packages to use in mission-critical applications. This comes about because knowing the absolute number of afferent links alone is insufficient to decide how important a package is to the system as a whole, instead the importance of the linking package plays a major role as well.
Cited by 21
Zhen Ming Jiang · 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering · 2015
Large-scale software systems (e.g., Amazon and Dropbox) must be load tested to ensure that they can service thousands or millions of concurrent requests every day. In this technical briefing, we will describe the state of research and practices in the area of load testing. We will focus on the techniques used in the three phases of a load test: (1) designing a load test, (2) executing a load test, and (3) analyzing the results of a load test. This technical briefing is targeted at load testing practitioners and software engineering researchers interested in testing and analyzing the behavior of large-scale software systems.
Cited by 4
Balzer, Michael, Noack, Andreas, Deussen, Oliver et al. · KOPS (University of Konstanz) · 2004
Modern object-oriented programs are hierarchical systems with many thousands of interrelated subsystems. Visualization helps developers to better comprehend these large and complex systems. This paper presents a three-dimensional visualization technique that represents the static structure of object-oriented programs using landscape-like distributions of three-dimensional objects on a two-dimensional plane. The familiar landscape methaphor facilitates intuitive navigation and comprehension. The visual complexity is reduced by adjusting the transparency of object surfaces to the distance of the viewpoint. An approach called Hierarchical Net is proposed for a clear representation of the relationsships between the subsystems.
Cited by 6Open access
B.K. Patel, D.Y. Tamanaha, Laurel A. Rudzik · INCOSE International Symposium · 1993
Abstract This paper presents an overview of the real time system/software methodology approach being deployed within Hughes Aircraft Company. The Hatley‐Pirbhai Process for System Development (PSD) was chosen as the training standard for all systems and software engineers in a common engineering method to increase productivity, quality of design, and communications between various engineering disciplines. The approach that Hughes has taken is to adopt a well defined and proven methodology available from industry and to customize it to include specific extensions applicable to the types of systems developed by Hughes Aircraft product organizations. Two such extensions, information modeling and requirements traceability tooling, are discussed in this paper. In conclusion, the paper will discuss the lessons learned for using the integrated system development methodology and follow‐on activities that are being worked on today.
Cited by 2
Brown, Barbara, Kamel, Khaled · NASA Technical Reports Server (NASA)
This research was undertaken to provide NASA with a survey of state-of-the-art techniques using in industrial and academia to provide safe, reliable, and maintainable software to drive large systems. Such systems must match the complexity and strict safety requirements of NASA's shuttle system. In particular, the Launch Processing System (LPS) is being considered for replacement. The LPS is responsible for monitoring and commanding the shuttle during test, repair, and launch phases. NASA built this system in the 1970's using mostly hardware techniques to provide for increased reliability, but it did so often using custom-built equipment, which has not been able to keep up with current technologies. This report surveys the major techniques used in industry and academia to ensure reliability in large and critical computer systems.
Cited by 0Open access
Ashutosh Tiwary, Rajendra K. Raj, D. Lea et al. · 1995
article Free Access Share on Building large distributed software systems using objects Authors: Ashutosh Tiwary Boeing Information and Support Services, P.O. Box 24346, MS 7L-40, Seattle, WA Boeing Information and Support Services, P.O. Box 24346, MS 7L-40, Seattle, WAView Profile , Rajendra K. Raj Information Technology Department, Morgan Stanley, 750 7th Avenue, New York, NY Information Technology Department, Morgan Stanley, 750 7th Avenue, New York, NYView Profile , Douglas S. Lea Department of Computer Science, SUNY, Oswego, NY Department of Computer Science, SUNY, Oswego, NYView Profile , Christopher J. Bosch Advanced Information Technologies Center, The MITRE Corporation, 7525 Colshire Drive, McLean, VA Advanced Information Technologies Center, The MITRE Corporation, 7525 Colshire Drive, McLean, VAView Profile Authors Info & Claims ACM SIGPLAN OOPS MessengerVolume 6Issue 4Oct 1, 1995 pp 191–195https://doi.org/10.1145/260111.260279Published:01 October 1995Publication History 0citation295DownloadsMetricsTotal Citations0Total Downloads295Last 12 Months9Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF
Cited by 0
Ivica Crnković · 1999
This position paper consists of two parts. The first part gives an overview of a research project started by ABB and Mlardalen University. The project is concentrated on use of standards technologies and standard components in real-time industry-process systems. The main goal of the project is to increase the knowledge about software development based on standard components from both theoretical and practical points of view. The project can be an interesting case of practices of adopting CBSE, a case of an approach in managing component-based engineering. The second part of the paper points to some important aspects in use of components at the development, run-time, and maintenance phases. It is a problem of identification and configuration of components in software systems. Configuration Management (CM) disciplines, such as Version Management, Configuration and Build Management, Change Management, etc., are well established for the conventional development. In a component-based devel...
Cited by 2