Software engineering: a practitioner's approach (2nd ed.)
Software engineering: a practitioner's approach (2nd ed.)
Decision support systems engineering
Decision support systems engineering
Object-oriented modeling and design
Object-oriented modeling and design
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
A graph traceability approach for software change impact analysis
A graph traceability approach for software change impact analysis
Application of domain analysis to object-oriented systems
Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications (Addendum)
Analysis patterns: reusable objects models
Analysis patterns: reusable objects models
Object technology and product lines
Addendum to the 1997 ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications (Addendum)
Visual modeling with Rational Rose and UML
Visual modeling with Rational Rose and UML
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The unified software development process
The unified software development process
Breakdowns in controls in automated systems
Breakdowns in controls in automated systems
Semantic matching across heterogeneous data sources
Communications of the ACM - The patent holder's dilemma: buy, sell, or troll?
Theoretical reflections on agile development methodologies
Communications of the ACM - Emergency response information systems: emerging trends and technologies
ACM Transactions on Software Engineering and Methodology (TOSEM)
ER'10 Proceedings of the 2010 international conference on Advances in conceptual modeling: applications and challenges
| Hi-index | 0.00 |
Development of software intensive systems (systems) in practice involves a series of self-contained phases for the lifecycle of a system. Semantic and temporal gaps, which occur among phases and among developer disciplines within and across phases, hinder the ongoing development of a system because of the interdependencies among phases and among disciplines. Such gaps are magnified among systems that are developed at different times by different development teams, which may limit reuse of artifacts of systems development and interoperability among the systems. This article discusses such gaps and a systems development process for avoiding them.