о뷢չ
JOURNAL OF COMPUTER RESEARCH AND DEVELOPMENT
1999ꡡ3610ڡVol.36No.101999



Ϊòõģ
硡з
ժҪñΪΣʺЧ;.оĽϵṹضܹкܴĸĽ.ʶ𡢲׽֯ͱʾϢȷϵṹܺ͹֧õ̹̣ǽĹؼ֮һ.ضУѾַ֤ЧػϢһ;.нĸķ͹̼乤Ʒ.
ؼʡ򹤳̣ģͣ
ͼšTP311
DOMAIN ANALYSIS:
PRODUCING USEFUL MODELS FOR SOFTWARE REUSE
LI Qing-Ru and MAI Zhong-Fan
Department of Computer Science and Engineering, Beijing University of Aeronautics and Astronautics, Beijing 100083
AbstractSoftware reuse is regarded as an effective way to solve software crisis and to improve software productivity and quality. Recently efforts on software reuse show that architecture-based, domain-specific reuse can yield great improvements. Domain analysis is a software engineering process that identifies, captures, organizes, analyzes, and represents information about a software domain to determine software architecture, framework, and components, and to support the reuse of software components. This method is one of the key techniques to solve the reuse problem. It has been proved to be an effective and efficient way to get the information needed for the design of domain-specific software. Conceptions about domain analysis and related field, as well as method, process, and products of domain analysis are also introduced. 
Key wordsdomain analysis, domain engineering, domain model, reuse
1
չҪĿ֮һΪ˽⣬۴ͳĿΪﵽһĿĶŬ.ڵҪͨùܿĽϣδͲϵĽϴĽ.оĽϵṹضܹкܴĸĽ1.
ҪΣҪװġõ.ҪﵽһĿľͱȷϵṹܺ͹ӶʵһϵӦԺǿĲƷϵproduct familyǹܡĳûĲƷ.Ʒϵǻһͨʲ(software asset)Ʒ.ⲻҪܵͨûģʽҪӦߵı׼淶.ͬʱһܺöҲЧõĹؼ.
һ(domain)ǹһͨõġɿƹܵϵͳӦóҲΪƷߣproduct line.ЩͨõĹǶڸ֮.һ֧õ̹.Ϊʶ𡢲֯ӦϢͨʮѵģӦõעضӦ.
ɵģΪýеĿdevelopment for reuseýеĿdevelopment with reuseֱӦΪ򹤳̺Ӧù.ΪЧؽãҪϵͳķָ.
˶ܹעҵ󡢿ܺģʽüҲʲļָ.Ĵù̿ܿʼһϵй̵̹Ļ.Ϊ˽Ϣһ֮ص򹤳̵ĸϸػͲƷ.󣬼򵥵ؽܴģ͵ϵṹ.
2ÿ
ǴѶΪƵĲйϵͳĹ.Уָܳеи׶εĲƷ.֪ĴãԣоڶϵͳԼСĵط󣬶ΪϵͳƵϵṹϵͳԼСԻϵṹġضöԲƷشĽ.
ʺģǲڵģͬĽɫԼ͹ߵְ.һõĹȴʮȷĿ꣺ȷɹ.ΪˣSTARSĿù̿ĸܣ2ݣ԰ͬ֯˽ǵù.3ɣʲʲʲ.ɹҪʲĿߣԱߣʹԱԼõĹ֧.ʲɵĹߡĵģ壬һضΪù̻κеĲƷ.ʲ̰ݽģ͡ϵṹȣʲ̰á֯ʲ԰û˽θЧʲʲֵ֧ʲ²Ʒ.̵㣬ͼ1еãù̹дʲʲʲ3̻һĽָģҵĿ.


ͼ1̹
3򹤳
Ϊ˽ϢҪ˽֮ص򹤳̵ĸ.
ָһķΧҪ߶ƵӦϵͳ㲻ͬû3.֮һһصϵͳصķǹơ񡢹͹Ϣϵṹ.ӿضҵܣͻĴҲضҵͣг.һխӦóΧƷߣҲɿҵ.򻮷֣ʹ֮ڹӶЧʵ.
ϵͳĿԲȡͬԵĿģʽûĽǶȿԽ仮Ϊ3ࣺһûһûڶͬû2ͼʾ.3ֲͬϵͳУϵͳı߽͹Ųͬص.ݵͻͬƵĲƷûָģڵϵͳ߽Ҳϵͳ.ڶͬûĲƷڵϵͳ߽ҲϵͳģͬƷĴ.һƵûϵͳмشһ߽Ϳùǽһϵͳһϵͳ.һϵͳвѰκεϵͳṩԴûϺõĽ.ЩضͻȺϵͳȺض.򹤳λ.


ͼ2ģʽ
򹤳ʶʹһĿùḶ́3.򹤳ǲƷĻӰһһϵͳϵĿάԡ˽ԡʹԺͿ.򹤳Ϊ򿪷ģͺͨϵṹģͺͨϵṹʶù.򹤳̵3ɲǣ塰ռ䡱ͨϵṹĿƣռĿܡʵ֣ʵġռ䡱ͼ3ʾ.


ͼ3򹤳̺Ӧù()
򹤳Ϊ.ʶռ֯ͱʾϢǶϵͳǿʷоרһõ֪ʶгֵļо.Ʒģ.
ʹռ֪ʶ򹤳ʦһͨϵṹ.ǰ̸õעӦضӦͨϵṹҲضϵṹ(domain specific software architectures, DSSA)ϵͳиֹ֮ĽϵĹԺͲ죬һвƷߵͨϵṹ.򹤳ʦĿùൽÿУӦùʦ.ΪĿǻͨõϵṹԸûϵṹΪĵ.һϵͳϵͳһȷҪĺںӣЩϵͳùϵͳǾͿԴؼٿһϵͳ/ϵͳķ.ġ׳ơĸʵϵͳ.
򹤳̺Ӧụ̀
򹤳̺Ӧù̹ͬụ̀ͼ3õ棬ҷӳ򹤳̵Ӧù̵ĹϵпԿڵĻͲƷĹϵ.
򹤳̻Ӧù̻ƣǼһ׹ԭ֧ϵͳơ.򹤳ʲһһӦóģӦùΪӦѽ.⣬ӦùṩˡĽ򹤳̶ϵͳĹܷΧԼϵͳʵֵضܣпܱϵͳΧС.
֮򹤳̻ĲƷɱӦùãӦù̵ĻַӰδ򹤳̻.Ӧù̵صǵϵͳ򹤳̵صһڶϵͳͨƶһϵͳϵĽ֧ӦùеĵϵͳϵͳĽ죬߷ԤϵͳΪ.
Ҫ˵ǣܶн򹤳̺ݾʹãȻΪ򹤳֮ǰֵ򹤳ȴںinclusive.ܶоԱͨʲô͡ 뿪һЩ˽ΪʲôǷĶ׶.ʵָ֡򹤳̵ĺĽ׶Σ5.Ҫصⶨͷ׶Σ潫ϸؽһйظͷѧ.
4
ʲҪϰ֮һΧʲĲȷԣشʲԭʼcontextµΪΣµĳµΪΣӦԽӰΪЩ.üƣĵ׼ӦԼȣΪ˽Щ.ȻΪҪȷʲѷΧĸϵͳʲãǲûṩȫĽ.
򹤳̺ǿЩȫģ˭ʲĿû˭ҵstakeholderʲôĽޣʲôһʱģɣΰղͬʹó仯νṹʲӦͬʹó.
4.1Ķ
80James Neighborsˡһ6ݣΪǡʶһضһϵͳĶͲĻ򹤳ڵһֻʶ𡢲׽֯һڿϵͳʹõϢʹڴϵͳʱ.
кܶƵĶ壺
Kang1990ʶռ֯ʾһеĻϵͳоǵķչʷϢרһȡ֪ʶϵͳĻۣ³ֵļ7ݣ
Prieto Diaz3Ϊʶ𡢲׽֯ڿϵͳеϢرǴϵͳʱõϢĹ.һϵͳķһϵͳ.
֮ǱʶͲ׽ضϵͳйϢںͽҪʹõϵͳϢͨھڹɼϢЧ֯γȷģ͵Ļ.
ϵͳƵģǵĲ֮ͬϵͳضϵͳеضӦежĶرǿ÷.ˣҪעֺⷢͿϵͳĹԺͿɱ.
4.2Ŀ
ռʲϢ򹤳ʦʲĿ.磬пĵ漰ڿõƾǱڵûãܸݴƶЧþ.
һϵϵͳģ͵ĹԺͿɱԽзھʲصĳϢصĻԭ.ش磺Ϊʲôϵͳϵͳв˲ͬԷʲôĿӰЩߣУνʷתΪ¿ϵͳ˵Եָϵ.ڹоһһϵͳֵܷ.
һضУܹͨΪ̲һͨϵṹ.˵Ŀȷ޶Ҫõʲô.ͬвͬ͹ܣҲвͬòص.
֮ĿǶȷĿõ󡪡ģͣӶΪõʲṩϵͳĻ.
4.3ʾģ
ģ͵ʽʾʽģͺͷʽϢǰֽ֧ȷӳ䣬߸ı.
ΪʹĽṩõ֧֣ϵͳķʽ׽ʾͨģʽرʾõ֪ʶģ.ģΪδϵͳĿãҲΪάϵͳļƻ.ģδ.
ģͰԺж֮Ļϵ.ģͣһЩͬԲͬģͣӲͬ淴ӳϢ.ģ͵ͨʾУʵϵԺ˹ܣ硢ܺ͹򣩵.ʹͨõıʾͳһģUMLܸõṩ֪ʶ;.
4.4Ĺ
ӦνУûй̶Ĺ򣬹ؼǶķΧϸ޶ϵͳԣҪͿɱԣѡ֯˽иԪ֮Ĺϵһõķʾ˽֪ʶ3.
ǸӵҪרҡϵͳĽüй֪ʶûõԴԼδлϢ.ѾõЩԱרҺ򹤳ʦҰһĹԭָƷ.ͬķͬռĲģҲͬΪҪһЩ֪ʶķࡢģ͡ضԻĳЩ׼ȣΪ֪ʶ.Ҫη󾫣Ӷض˽⣬ģͺ֪ʶ.ͼ4һ.


ͼ4һ
4.5
ѧǻ.һִԵЧֶ.ʹóԭ򽵵͸ԣЧشһϵӦгȡƷƷͿԿеضӦ.֮⣬Ӧֶ֧пϢ⡢ʾģ.
ΪֹкܶоԱ˲ͬ.ÿһԼص㣬ȡҪض⣬ЩġӦģҲ֪ʶʾ.ЩѧԱıҲӰЩѧ.
Ĳ죬ǴڼϵͳУ̶ͬȵǶЩؼضϵͳģ͡Ƽƣ󷽷.һЩӰ
(1) FODAfeature-oriented domain analysis710
FODASholom CohenЭSEIΪĿһֿһFODAǻڱʶϵͳɫ3׶Σģͺϵṹģ.
FODAѾҵ;ӦóӦãƶNORTELĵԶʾӦ.
(2) ֯ģODMorganization domain modeling򷽷311
ODMģ͵ͨ÷ƻģ͡ϵṹ̺ʲ̵֯սԷ򹤳̷߼оĿƻDARPASTARSĿΪ/Ʒ߷һֿ.
ODMԻΪ3׶Σƻѡ޶ͶĿ򣩡ģ򡢹ʲضĿͻ󣬹̻һЩɱӼʲϣ.ODMǻģͣǿdescription˵(prescription)ģ.
HP޸ڵODMģʺڱ˾֯Ŀ꣬򹤳ҵֲ.վCARDSĿڼͬӦODMԶϢϵͳAMHSΪHanscom AFBΧһֵĲƷ߷.ODMγɾSTARSĿ򹤳̷.
(3) ƹ(DADP)3
ƹ̼ǿϵͳΪһӲԱغϵͳⲿӰ.Coad-Yourdonʾŵ.ĲƷģͣǿҪһ±ʾ.⣬չַĹؼ.̵ķպ̳еķնȷɹǺҪ.ǵḶ́ʱ䷢չø.
5Ʒ
Ĺ̲һϵйƷʾͬӽǡͬȵ˽.ͬĲƷ̶ͬȵرʾҵ֪ʶӾ.һƷģ.ʾģƵϢĿĲͬ.ģȫͼרҡϵͳδȡ֪ʶʾ˷Ա˽.ĸ߲ͼ˿ӶԺͷ߲-ֽṹ߲ͨ-ṹͶͼ.ֵǶ˽ƷҪб.
ռǼ˽ͳȡģȴǺܸӵ.һܼӵḶ߽́дϸϢͨ.
5.1
ĿǰûȷЩĽڿϵͳǷ.ЩĶͼõĳ.
ҪȷǷϵͳУ.ʶĹϵ.Ҫ壺ӿڡͨӿṩķ߽硢ҪԪغṩķ.
5.2ģ
ģռ֯ͱʾϢʲĻ.ڳʼ֮󣬿޸ģҪṩһռ֯ϢĿ.
ģ͵ĿǱʾռ.Ϊ˰û˽ģͿһֳͼʾʶĹϵͷ.Ϊ˰ûӦЩܣģͱЩͨأԼʱʹÿֹܵԭ.һ˵ģͱҪ֡ͳ()ͳࣩ֮ĹϵࣩԺơЩࣩṩķ񡢶̬ΪĳѡһʵѡĻԭա⣨ܡ׶Եȣͳʹ.
Ŀǰģ͵ͼûͳһ׼ַ඼ǻڲͬͼӸȥչʾϵͳϢ.Ǵ漸ȥ̻еɼɵϵṹʲϵͳʵ.⼸ģҵģ͡Ϣģ֯͡ģ͡Ӧģͺͼģ.
ҵģ(business model)ҵνУһ֯ҵλʵʩϢϵͳ.ҵģΪĿĽһȷسʶеҵ.ЩҵƷ֯еĹߣ˭ʲƺʵߣ˭Щʲ˭Щʲ.ͨҵģ֤ͣĿҵĿ꣬ʹСЧعҵ֮佨ϵȷǵ.
Ϣģ(information model)ͷʵӦó֪ʶ.֪ʶصĿѧۺ͹ʵϵͳͿԡȥϵͳĿά鼰Ʒ.ϵͳĿǰʵǵĹϵʾ֪ʶʹڲϵṹģеĶݶп.ϢģͿʵϵERģ͡ģ.ϢģҪΪԱʹãԱ֤ϵͳõʵݳͷֽ.
֯ģ(organization model) ֯Σӳ䵽ҵ̣һλ֯Ļ֧ڲҪ֡ͬߡרҵȣйصĿЧҪ֯.
Ӧģ(application model) ֯ҪӦóʲôָ롢׼ģͨ͡ܣָϵͳڲƣ˱׼桢ʩҵҪӦģͣڸҵϢģϣʲôӦģ͡ӿڡʩչЩӦ.
ģ(technology model) ΪÿһҵҪѡõļʵҵ̣֧ҵĿ꣬ʵЧϵͳϵͳ.λͺҵɫڵ㣬ȷӦúݵķֲʶҪļʶڸڵҪ.
5.3ģ͵ݽ
ڴӿ󿪷ϵͳУһЩδģЩкܴüֵʱҪʵ޸ĿòƷ.磬ϵͳµ󣬾ͱʵģ.򹤳̵ƺʵֽ׶Ҳˣ޸Ŀ֧.ȫԤδӦһݽƣõݽӦԴһɹӦÿʼ.ͼ5ʾģ򹤳бӦùʹãӦùвı仯ٴθ.


ͼ5ݻ
6ģ͵ϵṹ
˵ģһϵе⣬ϵṹһϵнķ.ĲƷתӳ䵽һʵֵĿܣͨΪϵṹϵṹͨϵṹֱӵϵͳƵĹ.һЩͨϵṹĲ裬ODM˵ģͺFODAģ.ЩԿһͨϵṹͨЩָ.
ȷһֿӦõͨϵṹҪעؼԾߣͨϵṹϵͳЩҪԣͨϵṹӦַͨϵṹӦϵṹԣADLһϵṹģͣͨϵṹܹٸϵͳЩϵͳı仯̶ΣͨϵṹṩʲôĹ֧֣ӦùԶУȵ.Ǳĵص㣬Բڴ.
7ܡ
ЧñĿĵشù.бزٵҪ׶Σض򡢻õġϵṹΪĵƷ߿иԶ.⣬AT & TGTEEricssonNECToshibaHP4Щ˾ɹþǣͨضһϵвƷĹԽгȡЧؿԣӶ֧һϵвƷãܴЧʣͿɱ.
ΪϵͳõһؼѾںܶĿϳɹӦˣ810ݣǴڲȫ״̬ǴڼϵͳУûȫض޶.
ִصҪȱ׼͹֧.ȱ׼Щʹòͬݵıʾ谭ϵͳ߹㷺Ĳ.ṩ֧ģ͵ĳͱʾı׼ܿϵͳеƷпUMLĳֱؽشٽķչ.
õȻѧĿ(Ŀ79770007).
߼飺磬Ů196812ʦҪоΪ̻.
зУ1936ڣҪоΪ̡ԡ󷽷ѧݿ.
ߵλպѧѧ빤ϵ100083
ο
1Patricia Collins Cornwell. HP Domain Analysis: Producing Useful Models for Reusable Software1996. www.hp.hpl.com
2STARS Reuse Concepts, Vo 1, Conceptual Framework for Reuse Processes (CFRP), Version 2. STARS Technology Center, Unisys STARS Technical Report: STARS-UC-05159/001/00, Arlington VA, 1992. www.asset.com
3Prieto-Diaz Ruben. Domain analysis: An introduction. ACM SIGSOFT Software Engineering Notes, 1990, 15(2)
4Domain engineering methods and tools handbook Vol IMethods comprehensive approach to reusable defense software (CARDS). Loral Defense Systems-Eagan Valley Forge Engineering Center, STARS-VC-K017R1/001/00, 1994
5Carma McClure. Software Reuse Techniques: A Guide to Adding Reuse to the Software Process. Extended Intelligence Inc, 1996. www. reusility.com
6Neighbors J. Software construction using components Ph D dissertation. Department of Information and Computer Science, University of California, Irvine, 1981
7Kang K C, Cohen S G, Hess J A et al. Feature-oriented domain analysis (FODA): Feasibility study. Software Engineering Institute, Technical Report: CMU/SEI-90-TR-21, 1990. www.sei.cmu.edu
8Cohen, Sholom G et al. Application of feature-oriented domain analysis to the army movement control domain. Software Engineering Institute, Carnegie Mellon University, CMU/SEI-91-TR-28, ADA 256590, 1992. www.sei.cmu.edu
9Schnell K, Zalman N, Bhatt Atul. Transitioning domain analysis: An industry experience. Software Engineering Institute, Carnegie Mellon University, CMU/SEI-96-TR-009. 1996. www.sei.cmu.edu
10Krut, Robert W Jr. Integrating 001 tool support into the feature-oriented domain analysis methodology. Software Engineering Institute, Carnegie Mellon University, CMU/SEI-93-TR-11, ESC-TR-93-188, 1993. www.sei.cmu.edu
11 Mark A, Simos. Organization domain modeling (ODM): Formalizing the core domain modeling life cycle. www.asset.com 
ԭյڣ1998-11-12
޸ĸյڣ1999-05-10.
