According to Greenfield and Short, software branch is "a software artefact band that configures all-encompassing tools, processes, and agreeable application a software branch arrangement based on a software branch action to automate the development and aliment of variants of an archetypal artefact by adapting, assembling, and configuring framework-based components." 1
Wednesday, February 22, 2012
Description
In software engineering and action software architecture, a software branch is an authoritative anatomy that specializes in bearing computer software applications or software apparatus according to specific, externally-defined end-user requirements through an accumulation process. A software branch applies accomplishment techniques and attempt to Software Development to actor the allowances of acceptable manufacturing. Software factories are about complex with outsourced software creation.
Since coding requires a software engineer, (or the alongside in acceptable manufacturing, a accomplished craftsman) it is alone from the action at the appliance layer, the software is created by accumulating predefined apparatus instead of appliance acceptable IDE'sclarification needed. Acceptable coding, is larboard alone for creating new apparatus or services. Like acceptable manufacturing, the engineering is larboard to the conception of the apparatus and the requirements acquisition for the system. A blended appliance is the end aftereffect of accomplishment in a software factory.
Software factory–based appliance development addresses the botheration of acceptable appliance development area applications are developed and delivered after demography advantage of the ability acquired and the assets produced from developing agnate applications. Abounding approaches, such as training, documentation, and frameworks, are acclimated to abode this problem; however, appliance these approaches to consistently administer the admired ability ahead acquired during development of assorted applications can be an inefficient and error-prone process.2
Software factories abode this botheration by encoding accurate practices for developing a specific appearance of appliance aural a amalgamation of chip advice that is simple for activity teams to adopt. Developing applications appliance a acceptable software branch can accommodate abounding benefits, such as bigger productivity, superior and change capability.2
Since coding requires a software engineer, (or the alongside in acceptable manufacturing, a accomplished craftsman) it is alone from the action at the appliance layer, the software is created by accumulating predefined apparatus instead of appliance acceptable IDE'sclarification needed. Acceptable coding, is larboard alone for creating new apparatus or services. Like acceptable manufacturing, the engineering is larboard to the conception of the apparatus and the requirements acquisition for the system. A blended appliance is the end aftereffect of accomplishment in a software factory.
Software factory–based appliance development addresses the botheration of acceptable appliance development area applications are developed and delivered after demography advantage of the ability acquired and the assets produced from developing agnate applications. Abounding approaches, such as training, documentation, and frameworks, are acclimated to abode this problem; however, appliance these approaches to consistently administer the admired ability ahead acquired during development of assorted applications can be an inefficient and error-prone process.2
Software factories abode this botheration by encoding accurate practices for developing a specific appearance of appliance aural a amalgamation of chip advice that is simple for activity teams to adopt. Developing applications appliance a acceptable software branch can accommodate abounding benefits, such as bigger productivity, superior and change capability.2
History
The aboriginal aggregation to accept this appellation was Hitachi in 1969 with its Hitachi Software Works. Later, added companies such as System Development Corporation in 19753, NEC, Toshiba and Fujitsu in 1976 and 1977 followed the aforementioned authoritative approach.456
Cusumano 7 suggests that there are six phases for software factories:
Basic alignment and administration anatomy (mid-l960s to aboriginal 1970s)
Technology dressmaking and acclimation (early 1970s to aboriginal 1980s)
Process mechanization and abutment (late 1970s)
Process clarification and addendum (early 1980s)
Integrated and adjustable automation (mid-1980s)
Incremental artefact / array advance (late 1980s)
Cusumano 7 suggests that there are six phases for software factories:
Basic alignment and administration anatomy (mid-l960s to aboriginal 1970s)
Technology dressmaking and acclimation (early 1970s to aboriginal 1980s)
Process mechanization and abutment (late 1970s)
Process clarification and addendum (early 1980s)
Integrated and adjustable automation (mid-1980s)
Incremental artefact / array advance (late 1980s)
References
^ Jack Greenfield, Keith Short , Steve Cook, Stuart Kent, Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools, 2004, ISBN 0-471-20284-3
^ a b MSDN, Software Factories
^ H. Bratman, T. Court, The Software Factory, Computer, 8(5), 1975, pp.28-37
^ Michael A. Cusumano, The Software Factory: A Historical Interpretation, IEEE Software, March 1989
^ M. L. Griss, Software reuse: From library to factory, IBM SYSTEMS JOURNAL, VOL 32, NO 4, 1993
^ Ivan Aaen, Peter Bøttcher & Lars Mathiassen, The Software Factory: Contributions and Illusions. In: Proceedings of the Twentieth Information Systems Research Seminar in Scandinavia, Oslo, 1997.
^ Michael A. Cusumano, Branch Concepts and Practices in Software Development, Annals of the History of Computing, 13(1), 1991
Jack Greenfield, Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (Microsoft, 2004)
Jack Greenfield, Keith Short, Software Factories: Assembling Applications with Patterns, Models,Frameworks and Tools In: OOPSLA’03, October 26–30, 2003, Anaheim, California, USA.
^ a b MSDN, Software Factories
^ H. Bratman, T. Court, The Software Factory, Computer, 8(5), 1975, pp.28-37
^ Michael A. Cusumano, The Software Factory: A Historical Interpretation, IEEE Software, March 1989
^ M. L. Griss, Software reuse: From library to factory, IBM SYSTEMS JOURNAL, VOL 32, NO 4, 1993
^ Ivan Aaen, Peter Bøttcher & Lars Mathiassen, The Software Factory: Contributions and Illusions. In: Proceedings of the Twentieth Information Systems Research Seminar in Scandinavia, Oslo, 1997.
^ Michael A. Cusumano, Branch Concepts and Practices in Software Development, Annals of the History of Computing, 13(1), 1991
Jack Greenfield, Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (Microsoft, 2004)
Jack Greenfield, Keith Short, Software Factories: Assembling Applications with Patterns, Models,Frameworks and Tools In: OOPSLA’03, October 26–30, 2003, Anaheim, California, USA.
Subscribe to:
Posts (Atom)