Listing 1 - 2 of 2 |
Sort by
|
Choose an application
This book presents a comprehensive survey of the Vesta system for software configuration management (SCM). Vesta, unlike other SCM systems, is specifically designed to handle very large software projects comprising tens of millions of lines of code and beyond. Researchers in the field of software engineering and specialists in the construction of software development tools will especially benefit from this work, but it will also appeal to those responsible for designing and deploying configuration management solutions for large software systems. Three important but hard-to-achieve properties lie at the heart of Vesta's unique approach to software configuration management: Every build is repeatable Every build is incremental Every build is consistent To realize these properties in a practical SCM system, Vesta provides a novel repository to store the versions of the files that make up an evolving software system and a flexible language for writing modular configuration descriptions that define how the system is put together. This book explains in depth these facilities and the suite of tools that supports them, together with a methodology for applying them in practice. Readers who seek more information about Vesta may download the entire system as well as other publications, reference documents, and user documentation from the Vesta home page at http://www.vestasys.org.
Computer Science. --- Software Engineering. --- System Performance and Evaluation. --- Software Engineering/Programming and Operating Systems. --- Computer science. --- Computer system performance. --- Software engineering. --- Informatique --- Génie logiciel --- 681.3*D29 --- Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64} --- Information Technology --- Software Engineering --- Software configuration management. --- Software configuration management --- Engineering & Applied Sciences --- Computer Science --- 681.3*D29 Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64} --- Computer software configuration management --- Computer system failures. --- Computers. --- Application software. --- Theory of Computation. --- Computer Appl. in Administrative Data Processing. --- Configuration management --- Information theory. --- Information systems. --- Computer software engineering --- Engineering --- Communication theory --- Communication --- Cybernetics --- Computer failures --- Computer malfunctions --- Computer systems --- Failure of computer systems --- System failures (Engineering) --- Fault-tolerant computing --- Application computer programs --- Application computer software --- Applications software --- Apps (Computer software) --- Computer software --- Automatic computers --- Automatic data processors --- Computer hardware --- Computing machines (Computers) --- Electronic brains --- Electronic calculating-machines --- Electronic computers --- Hardware, Computer --- Machine theory --- Calculators --- Cyberspace --- Failures
Choose an application
Between July 1999 and June 2005 a group of European companies, research institutes, and universities executed the EUREKA-ITEA projects ESAPS, CAFÉ, and FAMILIES on the topic of product line engineering. The projects originated from the need of the industry to improve software engineering performance by organizing product development in product lines. The results obtained within the projects have been implemented in several large industries (e.g., automotive, e-business, medical systems, and mobile phones). They involve a radical shift in software construction and production. The most important research results of the projects are collected in this book. Product line engineering was already applied within industry in the 1980s and presumably earlier. In the 1980s, good architects in many telecommunications c- panies based their architectures on the ideas of David Parnas, who published on the subject of program families . They were facilitated by the CHILL language widely used by the telecommunications companies. This language deploys the same modularity principles as the Modula programming language family. Modularity is a crucial ingredient for implementing systems with a component-based architecture. Being able to compose the products of components is an important mechanism in all product line architectures. In the 1990s, the product line ideas started to gain ground in other industries. Around 1995, the company experiences reached the academia and since then people in companies and academia have collaborated widely on this subject. The ESAPS, CAFÉ, and FAMILIES projects manifest an institutionalized form of this collaboration.
Computer software --- Software engineering. --- Development. --- Computer science. --- Management. --- Industrial management. --- Information technology. --- Business --- Economic policy. --- Computer Science. --- Software Engineering. --- IT in Business. --- Innovation/Technology Management. --- R & D/Technology Policy. --- Computer software engineering --- Engineering --- Economic nationalism --- Economic planning --- National planning --- State planning --- Economics --- Planning --- National security --- Social policy --- Electronic data processing --- IT (Information technology) --- Technology --- Telematics --- Information superhighway --- Knowledge management --- Business administration --- Business enterprises --- Business management --- Corporate management --- Corporations --- Industrial administration --- Management, Industrial --- Rationalization of industry --- Scientific management --- Management --- Industrial organization --- Administration --- Industrial relations --- Organization --- Informatics --- Science --- Data processing. --- Development of computer software --- Software development --- Information Technology --- Software Engineering --- Software engineering --- 681.3*D210 --- 681.3*D211 --- 681.3*D213 --- 681.3*D21 --- 681.3*D29 --- 681.3*K63 --- 681.3*K63 Software management: software development; software selection; software maintenance --- Software management: software development; software selection; software maintenance --- 681.3*D210 Design: methodologies; representation (Software engineering) --- Design: methodologies; representation (Software engineering) --- 681.3*D29 Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64} --- Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64} --- 681.3*D21 Requirements/specifications: languages; methodologies; tools (Software engineering)--See also {681.3*D31} --- Requirements/specifications: languages; methodologies; tools (Software engineering)--See also {681.3*D31} --- Development --- Software architectures: data abstractio, domain-specific architectures, information hiding, languages (e.g. description, interconnection, definition), patterns (e.g. client/server, pipeline, blackboard) --- Reusable software: domain engineering; reusable libraries; reuse models --- Business—Data processing. --- Computer software - Development
Listing 1 - 2 of 2 |
Sort by
|