Listing 1 - 10 of 485 | << page >> |
Sort by
|
Choose an application
Programming --- Object-oriented programming (Computer science) --- 681.3*D15 --- 681.3*D15 Software: object-oriented programming --- Software: object-oriented programming --- Computer programming --- Object-oriented methods (Computer science) --- Document Object Model (Web site development technology)
Choose an application
Choose an application
Computer software --- UML (Computer science) --- Logiciels --- UML (Informatique) --- Development --- Congresses. --- Congresses --- Développement --- Congrès --- Computer Science --- Engineering & Applied Sciences --- 681.3*D2 --- Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Information Technology --- Software Engineering --- 681.3*D2 Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Unified Modeling Language (Computer science) --- Computer science. --- Computer programming. --- Software engineering. --- Programming languages (Electronic computers). --- Computer simulation. --- Management information systems. --- Computer Science. --- Programming Techniques. --- Software Engineering. --- Programming Languages, Compilers, Interpreters. --- Simulation and Modeling. --- Management of Computing and Information Systems. --- Modeling languages (Computer science) --- Object-oriented methods (Computer science) --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Management --- Computer modeling --- Computer models --- Modeling, Computer --- Models, Computer --- Simulation, Computer --- Electromechanical analogies --- Mathematical models --- Simulation methods --- Model-integrated computing --- Computer languages --- Computer program languages --- Computer programming languages --- Machine language --- Electronic data processing --- Languages, Artificial --- Computer software engineering --- Engineering --- Computers --- Electronic computer programming --- Electronic digital computers --- Programming (Electronic computers) --- Coding theory --- Informatics --- Science --- Communication systems --- Programming --- Information Systems.
Choose an application
The documentation is missing or obsolete, and the original developers have departed. Your team has limited understanding of the system, and unit tests are missing for many, if not all, of the components. When you fix a bug in one place, another bug pops up somewhere else in the system. Long rebuild times make any change difficult. All of these are signs of software that is close to the breaking point.Many systems can be upgraded or simply thrown away if they no longer serve their purpose. Legacy software, however, is crucial for operations and needs to be continually available and upgr
Programming --- Object-oriented programming (Computer science) --- Software reengineering. --- Software patterns. --- Object-oriented programming (Computer science). --- Information Technology --- General and Others --- Software reengineering --- Software patterns --- 681.3*D15 --- 681.3*D210 --- 681.3*D22 --- 681.3*D210 Design: methodologies; representation (Software engineering) --- Design: methodologies; representation (Software engineering) --- 681.3*D15 Software: object-oriented programming --- Software: object-oriented programming --- 681.3*D22 Tools and techniques: decision tables; flow charts; modules and interfaces; programmer workbench; software libraries; structured programming; top-down programming; user interfaces (Software engineering) --- Tools and techniques: decision tables; flow charts; modules and interfaces; programmer workbench; software libraries; structured programming; top-down programming; user interfaces (Software engineering) --- Computer programming --- Object-oriented methods (Computer science) --- Document Object Model (Web site development technology) --- Computer software reengineering --- Reengineering of software --- Software renewal --- Software renovation --- Software engineering --- Software maintenance --- Patterns, Software --- Computer software --- Development
Choose an application
The ECOOP '91 Workshop on Object-Based Concurrent Computing was organized toprovide a forum on concurrent, distributed and open-ended computing. The emphasis was on conceptual, theoretical and formal aspects, as well as practical aspects and sound experience, since such a viewpoint was deemed indispensible to investigate and establish a basis for future development. This volume contains 12 papers selected from 25 presented at the workshop, together with a paper by J.A. Goguen, who was an invited speaker at the workshop. The papers are classified into four categories: Formal methods (1): three papers are concerned with the formal semantics of concurrent objects based on process calculi. Formal methods (2): four papers are concerned with various formal approaches to the semantics of concurrent programs. Concurrent programming: three papers. Models: three papers areconcerned with models for concurrent systems.
681.3*D15 --- Object-oriented programming --- Parallel programming --- 681.3*D13 --- 681.3*D32 --- 681.3*D33 --- Software: object-oriented programming --- Concurrent programming --- language classifications: applicative languages; data-flow languages; design languages; extensible languages; macro and assembly languages; nonprocedural languages; specialized application and very high-level languages (Programminglanguages) --- Languages constructs: abstract data types; concurrent programming structures;control structures; coroutines (Programming languages) --- 681.3*D33 Languages constructs: abstract data types; concurrent programming structures;control structures; coroutines (Programming languages) --- 681.3*D32 language classifications: applicative languages; data-flow languages; design languages; extensible languages; macro and assembly languages; nonprocedural languages; specialized application and very high-level languages (Programminglanguages) --- 681.3*D13 Concurrent programming --- 681.3*D15 Software: object-oriented programming --- Object-oriented programming (Computer science) --- Parallel programming (Computer science) --- Congresses --- Object-oriented programming - Congresses. --- Software engineering. --- Computer science. --- Software Engineering/Programming and Operating Systems. --- Programming Techniques. --- Programming Languages, Compilers, Interpreters. --- Informatics --- Science --- Computer software engineering --- Engineering
Choose an application
Choose an application
Computer science --- Programming --- Computer architecture. Operating systems --- Computer. Automation --- programmeren (informatica) --- programmeertalen --- software engineering --- computernetwerken
Choose an application
The documentation is missing or obsolete, and the original developers have departed. Your team has limited understanding of the system, and unit tests are missing for many, if not all, of the components. When you fix a bug in one place, another bug pops up somewhere else in the system. Long rebuild times make any change difficult. All of these are signs of software that is close to the breaking point. Many systems can be upgraded or simply thrown away if they no longer serve their purpose. Legacy software, however, is crucial for operations and needs to be continually available and upgraded. How can you reduce the complexity of a legacy system sufficiently so that it can continue to be used and adapted at acceptable cost? Based on the authors' industrial experiences, this book is a guide on how to reverse engineer legacy systems to understand their problems, and then reengineer those systems to meet new demands. Patterns are used to clarify and explain the process of understanding large code bases, hence transforming them to meet new requirements. The key insight is that the right design and organization of your system is not something that can be evident from the initial requirements alone, but rather as a consequence of understanding how these requirements evolve. * Describes how to reverse engineer a monolithic system to understand how it really works and how to identify potential problems. * Includes reengineering patterns that tackle well-known reengineering techniques often encountered in object-oriented programming, such as introducing polymorphism, factoring out common behavior, detecting duplicated code, and understanding design. * Shows how to build a culture of continuous reengineering for achieving flexible and maintainable object-oriented systems.
Choose an application
"This volume contains the proceedings of the seventh European Conference on Object-Oriented Programming (ECOOP '93). The conference attracted 146 submissions from around the world, and the selected papers range in topic from programming language and database issues to analysis and design and reuse, and from experience reports to theoretical contributions. The volume opens with an abstract of the keynote address, "Intimate computing and the memory prosthesis: a challenge for computer systems research?" by M.G. Lamming, and continueswith selected papers organized into parts on framework and reuse, concurrency and distribution, types and subtypes, languages and inheritance, time-dependent behavior, object-oriented analysis and design, and reflection. The volume also contains an invited talk, "The OSI manager-object model" by C. Ashford, and the position statements from a panel discussion."--PUBLISHER'S WEBSITE.
Object-oriented programming (Computer science) --- Congresses --- Object-oriented programming languages --- Object-oriented languages (Computer program languages) --- OO languages (Computer program languages) --- OOLs (Computer program languages) --- OOP languages (Computer program languages) --- Programming languages (Electronic computers)
Choose an application
Component-based software development is the next step after object-oriented programmingthatpromisesto reducecomplexityandimprovereusability.These advantages have also been identi?ed by the industry, and consequently, over the past years, a large number of component-based techniques and processes have been adopted in many of these organizations. A visible result of this is the number ofcomponentmodels thathavebeendevelopedandstandardized.These models de?ne how individual software components interact with each other and simplify the design process of software systems by allowing developers to choose from previously existing components. The development of component models is a ?rst step in the right direction, but there are many challenges that cannot be solved by the development of a new component model alone. Such challengesare the adaptation of components, and their development and veri?cation. Software Composition is the premiere workshop to advance the research in component-based software engineering and its related ?elds. SC 2005 was the fourth workshop in this series. As in previous years, SC 2005 was organized as an event co-located with the ETAPS conference. This year's program consisted of a keynote on the revival of dynamic l- guages given by Prof. Oscar Nierstrasz and 13 technical paper presentations (9 full and 4 short papers). The technical papers were carefully selected from a total of 41 submitted papers. Each paper was thoroughly peer reviewed by at leastthreemembers oftheprogramcommittee andconsensusonacceptancewas achieved by means of an electronic PC discussion. This LNCS volume contains the revised versions of the papers presented at SC 2005.
Computer science --- Programming --- Computer architecture. Operating systems --- Computer. Automation --- programmeren (informatica) --- programmeertalen --- software engineering --- computernetwerken
Listing 1 - 10 of 485 | << page >> |
Sort by
|