Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
812
FORM: A feature-oriented reuse method with domain-specific reference architectures
- Annals of Software Engineering
, 1998
"... Systematic discovery and exploitation of commonality across related software systems is a fundamental technical requirement for achieving successful software reuse. By examining a class/family of related systems and the commonality underlying those systems, it is possible to obtain a set of referenc ..."
Abstract
-
Cited by 239 (8 self)
- Add to MetaCart
the domain artifacts produced from the domain engineering. FORM starts with an analysis of commonality among applications in a particular domain in terms of services, operating environments, domain technologies, and implementation techniques. The model constructed during the analysis is called a &
Understanding the Requirements for Developing Open Source Software Systems
- IEE Proceedings - Software
, 2002
"... This study presents an initial set of findings from an empirical study of social processes, technical system configurations, organizational contexts, and interrelationships that give rise to open software. The focus is directed at understanding the requirements for open software development efforts, ..."
Abstract
-
Cited by 174 (49 self)
- Add to MetaCart
to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing open software systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for open source software
Determining the provenance of software artifacts
"... Software clone detection has made substantial progress in the last 15 years, and software clone analysis is starting to provide real insight into how and why code clones are born, evolve, and sometimes die. In this position paper, we make the case that there is a more general problem lurking in the ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
in the background: software artifact provenance analysis. We argue that determining the origin of software artifacts is an increasingly important problem with many dimensions. We call for simple and lightweight techniques that can be used to help narrow the search space, so that more expensive techniques
A Domain-Specific Software Architecture Engineering Process Outline
- ACM SIGSOFT Software Engineering Notes
, 1993
"... "In order to reuse software, there needs to be software to reuse." -- Tracz [9] One of the dilemmas that has prevented software developers from reusing software is the lack of software artifacts to use or the existence of artifacts that are difficult to integrate. Domain-Specific Software ..."
Abstract
-
Cited by 103 (0 self)
- Add to MetaCart
"In order to reuse software, there needs to be software to reuse." -- Tracz [9] One of the dilemmas that has prevented software developers from reusing software is the lack of software artifacts to use or the existence of artifacts that are difficult to integrate. Domain-Specific Software
Assessing traceability of software engineering artifacts
"... Abstract The generation of traceability links or traceability matrices is vital to many software engineering activities. It is also person-power intensive, time-consuming, error-prone, and lacks tool support. The activities that require traceability information include, but are not limited to, risk ..."
Abstract
- Add to MetaCart
analysis, impact analysis, criticality assessment, test coverage analysis, and verification and validation of software systems. Information Retrieval (IR) techniques have been shown to assist with the automated generation of traceability links by reducing the time it takes to generate the traceability
Consistency Management of Heterogeneous Software Artifacts
"... The development of complex software systems involves the participation of many stakeholders (e.g. customers, users, analysts, designers, and developers) who collaborate in publishing numerous heterogeneous software artifacts such as source code, analysis models and design, unit tests, XML deployment ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
The development of complex software systems involves the participation of many stakeholders (e.g. customers, users, analysts, designers, and developers) who collaborate in publishing numerous heterogeneous software artifacts such as source code, analysis models and design, unit tests, XML
An Analysis of Network Configuration Artifacts
"... Computer networks and the Internet have become necessary tools in many daily activities; as such, they share the expectation to be “always on ” and highly available. Throughout a decades-long evolution of increasing reliance, campus/enterprise networks and Wide-Area Networks (WANs) have been enginee ..."
Abstract
-
Cited by 4 (0 self)
- Add to MetaCart
operations as there has to that of software engineering. In this work, we analyze the deployment and operation of two large networks over a period of five to ten years. Our analogy-based approach is to apply software source code artifact analysis techniques to network device configurations. Specifically, we
Understanding Software Systems Using Reverse Engineering Technology -- Perspectives from the Rigi Project
, 1993
"... Software engineering research has focused mainly on software construction and has neglected software maintenance and evolution. Proposed is a shift in research from synthesis to analysis. Reverse engineering is introduced as a possible solution to program understanding and software analysis. Present ..."
Abstract
-
Cited by 95 (4 self)
- Add to MetaCart
Software engineering research has focused mainly on software construction and has neglected software maintenance and evolution. Proposed is a shift in research from synthesis to analysis. Reverse engineering is introduced as a possible solution to program understanding and software analysis
Functional Fixedness in the Design of Software Artifacts
"... A common rule of thumb to make components reusable is to "make components generic". But software engineers tend to design in a way that solves the particular problem at hand, and in a way that they do not easily see opportunities to reuse existing components. We call such solutions "f ..."
Abstract
- Add to MetaCart
;functionally fixed". Domain analysis prior to system design can help a great deal here, but for most software engineers fighting functional fixedness is still a constant and uphill battle. It seems to us that designers need more experience in recognizing functional fixedness when it is "staring them
Results 1 - 10
of
812
