Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Feature-oriented domain analysis
open-in-new
<h2 id="history">History</h2> <p>Feature-oriented domain analysis was first developed by the <a href="/facts/Software_Engineering_Institute/uMJyBSNj">Software Engineering Institute</a> in 1990.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> In the initial technical report, a study performed determined that feature oriented domain analysis was not only beneficial, but was described as a "necessary first step" for <a href="/facts/Software_reuse/DVohfy6U">software reuse</a>.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> The report introduced the concept of <a href="/facts/Feature_model/1NtTFuu7">feature models</a> to <a href="/facts/Domain_engineering/PGL9s7Ij">domain engineering</a> in an effort to represent the standard features within the family of systems in the domain as well as the relationships between those features.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> Since then, feature models have been characterized as "the greatest contribution of domain engineering to software engineering".<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> </p><p>Much of the work leading up to the development of FODA was sponsored by the <a href="/facts/U.S._Department_of_Defense/dWAvf7e3">U.S. Department of Defense</a> through research programs related to software reuse during the late 1980s. FODA was developed as a comprehensive analysis and refinement of technology developed from 1983–1990.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> While some aspects of FODA have changed, and it has become integrated with <a href="/facts/Model-driven_engineering/vznUHbSm">model-driven engineering</a>, FODA is still known as the method that initially introduced feature models to domain engineering.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <h2 id="purpose">Purpose</h2> <p>The intent of feature-oriented domain analysis is to support functional and architectural reuse. The objective is to create a domain model which represents a family of systems which can then be refined into the particular desired system within the domain<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> To do this, the scope of the domain must be analyzed (known as <i>FODA context analysis</i>) to identify not only the systems in the domain but also the external systems which interact with the domain.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> <i>FODA feature analysis</i> then analyzes the end-user's view of the configurable requirements and candidate systems within the domain.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> From the developed <a href="/facts/Feature_model/1NtTFuu7">feature model</a>, customers can select from configurable requirements to specify a final system.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> Through this process, feature-oriented domain analysis ensures that a business can meet customers' demands efficiently through reuse of technology.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> </p> <h2 id="bibliography">Bibliography</h2> <ul><li>Czarnecki, Krzysztof; Eiseneckerr, Ulrich W. (2000). <i>Generative Programming: Methods, Tools, and Applications</i>. <a href="/facts/Addison-Wesley/A7UFATEG">Addison-Wesley</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-201-30977-7.</li> <li>Kang, K.; Cohen, S.; Hess, J.; Nowak, W.; Peterson, S. (1990). <a href="https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=11231">Feature-Oriented Domain Analysis (FODA) Feasibility Study</a> (PDF) (Report). Pittsburgh: <a href="/facts/Software_Engineering_Institute/uMJyBSNj">Software Engineering Institute</a>, <a href="/facts/Carnegie_Mellon_University/XKd7L2KA">Carnegie Mellon University</a>.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Czarnecki, p.44 <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Kang, p.93 <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Kang, p.42 <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Czarnecki, p.82 <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Czarnecki, p.57 <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Czarnecki, p.44 <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Kang, p.26 <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Kang, p.36 <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>Kang, p.40 <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Kang, p.43 <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Czarnecki, p.43 <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> </ol>