版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领
文档简介
1
Agent-OrientedSoftwareEngineering
NicholasR.JenningsandMichaelWooldridge
DepartmentofElectronicEngineering
QueenMary&WestfieldCollege
UniversityofLondon
LondonE14NS,UnitedKingdom
{N.R.Jennings,M.J.Wooldridge}@qmw.ac.uk
Abstract
Agent-orientedtechniquesrepresentanexcitingnewmeansofanalysing,designingandbuildingcom-plexsoftwaresystems.Theyhavethepotentialtosignificantlyimprovecurrentpracticeinsoftwareengineeringandtoextendtherangeofapplicationsthatcanfeasiblybetackled.Yet,todate,therehavebeenfewseriousattemptstocastagentsystemsasasoftwareengineeringparadigm.Thispaperseekstorectifythisomission.Specifically,itwillbearguedthat:(i)theconceptualapparatusofagent-orientedsystemsiswell-suitedtobuildingsoftwaresolutionsforcomplexsystemsand(ii)agent-orientedapproachesrepresentagenuineadvanceoverthecurrentstateoftheartforengineeringcomplexsys-tems.Followingonfromthisview,themajorissuesraisedbyadoptinganagent-orientedapproachtosoftwareengineeringarehighlightedanddiscussed.
1.Introduction
Designingandbuildinghighqualityindustrial-strengthsoftwareisdifficult.Indeed,ithasbeenclaimedthatsuchdevelopmentprojectsareamongthemostcomplexconstructiontasksunder-takenbyhumans.Againstthisbackground,awiderangeofsoftwareengineeringparadigmshavebeendevised(e.g.,proceduralprogramming,structuredprogramming,declarativeprogramming,object-orientedprogramming,designpatterns,applicationframeworksandcomponent-ware).Eachsuccessivedevelopmenteitherclaimstomaketheengineeringprocesseasierortoextendthecomplexityofapplicationsthatcanfeasiblybebuilt.Althoughthereissomeevidencetosup-porttheseclaims,researcherscontinuallystriveformoreefficientandpowerfulsoftwareengi-neeringtechniques,especiallyassolutionsforevermoredemandingapplicationsarerequired.
Thispaperwillarguethatanalysing,designingandimplementingsoftwareasacollectionofinteracting,autonomousagents(i.e.,asamulti–agentsystem
[26][39]
)representsapromisingpointofdepartureforsoftwareengineering.Whilethereissomedebateaboutexactlywhatcon-stitutesanautonomousagentandwhatconstitutesinteraction,thisworkseekstoabstractawayfromparticulardogmaticstandpoints.Instead,wefocusonthosecharacteristicsforwhichthereissomeconsensus.Fromthisstandpoint,thepaper’scentralhypothesiswillbeadvanced:forcertainclassesofproblem(thatwillbedefined),adoptingamulti-agentapproachtosystemdevelopmentaffordssoftwareengineersanumberofsignificantadvantagesovercontemporarymethods.Notethatwearenotsuggestingthatmulti-agentsystemsareasilverbullet
[4]
—thereisnoevidencetosuggesttheywillrepresentanorderofmagnitudeimprovementinsoftwareengineeringproduc-
2
tivity.However,webelievethatforcertainclassesofapplication,anagent-orientedapproachcansignificantlyimprovethesoftwaredevelopmentprocess.
Inseekingtodemonstratetheefficacyoftheagent-orientedapproach,themostcompellingformofanalysiswouldbetoquantitativelyshowhowadoptingsuchtechniqueshadimproved,accord-ingtosomestandardsetofsoftwaremetrics,thedevelopmentprocessinarangeofprojects.However,suchdataissimplynotavailable(asitisstillnotformoreestablishedmethodssuchasobject-orientation).However,therearecompellingargumentsforbelievingthatanagent-orientedapproachwillbeofbenefitforengineeringcertaincomplexsoftwaresystems.Theseargumentshaveevolvedfromadecadeofexperienceinusingagenttechnologytoconstructlarge-scale,real-worldapplicationsinawidevarietyofindustrialandcommercialdomains
[20
].
Thecontributionofthispaperistwofold.Firstly,despitemulti-agentsystemsbeingtoutedasatechnologythatwillhaveamajorimpactonfuturegenerationsoftware(“pervasiveineverymar-ketbytheyear2000”
[17]
and“thenewrevolutioninsoftware”
[14]
),therehasbeennosystem-aticevaluationofwhythismaybethecase.Thus,althoughthereareanincreasingnumberofdeployedagentapplications(see
[5]
,
[19]
,
[20]
,
[27]
forareview),nobodyhasanalysedpreciselywhatmakestheparadigmsoeffective.Thisisclearlyamajorgapinknowledge,whichthispaperseekstoaddress.Secondly,therehasbeencomparativelylittleworkonviewingmulti-agentsys-temsasasoftwareengineering.Thisshortcomingisrectifiedbyrecastingtheessentialcompo-nentsofagentsystemsintomoretraditionalsoftwareengineeringconcepts,andbyexaminingtheimpactonthesoftwareengineeringlife-cycleofadoptinganagent-orientedapproach.
Theremainderofthepaperisstructuredasfollows.Sectiontwomakesthecaseforanagent-ori-entedapproachtosoftwareengineering.Itanalysesthetypeofcomplexitypresentinindustrial-strengthsoftware,characterisesthekeyconceptualmechanismsoftheagent-orientedapproach,andexplainshowthesemechanismsarewellsuitedtotacklingthecomplexitypresentinsoftwaredevelopment.Sectionthreeexaminestheimpactofadoptinganagent-orientedapproachonthesoftwareengineeringlifecycle—focusinginparticularonthespecification,implementationandverificationphases.Sectionfourdealswiththepragmaticsofagent-orientedsoftwareengineeringbypresentingsomecommonpitfallsthatfrequentlybedevilagent-orienteddevelopments.Sectionfiveconcludesbyidentifyingthemajoropenissuesthatneedtobeaddressedifagent-orientedtechniquesaretoreachthesoftwareengineeringmainstream.
2.TheCaseforanAgent-OrientedApproachtoSoftwareEngineering
Thissectioncharacterisestheessentialnatureofreal-worldsoftwaresystems(section2.1)andthengoesontopresentexactlywhatwemeanbythenotionofagent-orientedsoftware(section2.2).Usingthesecharacterisations,argumentsareadvancedastowhyagent-orientedtechniquesarewellsuitedtodevelopingcomplexsoftwaresystems(section2.3).
3
2.1TheNatureofComplexSoftwareSystems
Industrial-strengthsoftwareiscomplexinnature:itistypicallycharacterisedbyalargenumberofpartsthathavemanyinteractions
[37]
.Moreoverthiscomplexityisnotaccidental
[4]
:itisaninnatepropertyofthetypesoftasksforwhichsoftwareisused.Theroleofsoftwareengineeringisthereforetoprovidestructuresandtechniquesthatmakeiteasiertohandlethiscomplexity.For-tunately,thiscomplexityexhibitsanumberofimportantregularities
[37
]:
•Complexityfrequentlytakestheformofahierarchy1.Thatis,thesystemiscomposedofinter-relatedsub-systems,eachofwhichisitselfahierarchy.Theprecisenatureoftheorganisationalrelationshipsvariesbetweensub-systems,althoughsomegenericforms(suchasclient-server,peer,team)canbeidentified.Organisationalrelationshipsarenotstatic:theycan,andfrequentlydo,varyovertime.
•Thechoiceofwhichcomponentsinthesystemareprimitiveisrelativelyarbitraryandisdefinedverymuchbytheobserver’saimsandobjectives.
•Hierarchicsystemsevolvemorequicklythannon-hierarchiconesofcomparablesize.Inotherwords,complexsystemswillevolvefromsimplesystemsmuchmorerapidlyiftherearestableintermediateforms,thaniftherearenot.
•Itispossibletodistinguishbetweentheinteractionsamongsub-systemsandtheinterac-tionswithinsub-systems.Thelatterarebothmorefrequent(typicallyatleastanorderofmagnitudemore)andmorepredictablethantheformer.Thisgivesrisetotheviewthatcomplexsystemsarenearlydecomposable.Thus,sub-systemscanbetreatedalmostasiftheyareindependentofoneanother,butnotquitesincetherearesomeinteractionsbetweenthem.Moreover,althoughmanyoftheseinteractionscanbepredictedatdesigntime,somecannot.
Drawingtheseinsightstogether,itispossibletodefineacanonicalviewofacomplexsystem(figure1).Thesystem’shierarchicalnatureisexpressedthroughthe“composedof”links,compo-nentswithinasub-systemareconnectedthrough“frequentinteraction”links,andinteractionsbetweencomponentsareexpressedthrough“infrequentinteraction”links.Thevariablenotionofprimitivecomponentscanbeseeninthewaythatatomiccomponentsatonelevelareexpandedouttoentiresub-systemsatsubsequentlevels.
1.Heretheterm“hierarchy”isnotusedtomeanthateachsub-systemissubordinatedbyanauthorityrelationtothesystemtowhichitbelongs.Rather,itshouldbeinterpretedinabroadsensetomeanasystemthatisanalysableintosuccessivesetsofsub-systems.
4
sub-system
sub-systemcomponent
>composedof
frequentinteractioninfrequentinteraction
Figure1:ViewofaCanonicalComplexSystem
Giventheseobservations,softwareengineershavedevisedanumberofpowerfultoolsinordertomanagethiscomplex
ity.Theprincipalmechanismsinclude[3]:
•Decomposition:Themostbasictechniquefortacklinganylargeproblemistodivideitintosmaller,moremanageablechunkseachofwhichcanthenbedealtwithinrelativeiso-lation(notethenearlydecomposablesub-systemsinfigure1).Decompositionhelpstacklecomplexitybecauseitlimitsthedesigner’sscope:atanygiveninstantonlyaportionoftheproblemneedstobeconsidered.
•Abstraction:Theprocessofdefiningasimplifiedmodelofthesystemthatemphasisessomeofthedetailsorproperties,whilesuppressingothers.Again,thistechniqueworksbecauseitlimitsthedesigner’sscopeofinterestatagiventime.Attentioncanbefocusedonthesalientaspectsoftheproblem,attheexpenseofthelessrelevantdetails.
•Organisation2:Theprocessofidentifyingandmanagingtheinter-relationshipsbetweenthevariousproblemsolvingcomponents(notethesub-systemandinteractionlinksoffig-ure1).Theabilitytospecifyandenactorganisationalrelationshipshelpsdesignerstacklecomplexityintwoways.Firstly,byenablinganumberofbasiccomponentstobegroupedtogetherandtreatedasahigher-levelunitofanalysis.Forexample,theindividualcompo-nentsofasub-systemcanbetreatedasasingleunitbytheparentsystem.Secondly,byprovidingameansofdescribingthehigh-levelrelationshipsbetweenvariousunits.Forexample,anumberofcomponentsmayneedtoworktogetherinordertoprovideapartic-ularfunctionality.
2.Boochusestheterm“hierarchy”forthisfinalpoint
[3]
.However,hierarchyinvariablygivestheconnotationofcontrol,hencethemoreneutralterm“organisation”isusedhere.Organisationscanbearrangedsuchthattheycorre-spondtocontrolhierarchies,howevertheycanalsocorrespondtogroupsofpeers,andanythingthatfallsin-between.
5
Theprecisenatureandwayinwhichthesetoolsareusedvariesenormouslybetweensoftwareparadigms.Hencewhencharacterisinganewparadigm,suchasagent-orientedsoftware,clearpositionsneedtobedeterminedoneachoftheseissues(section2.2).Moreover,whenassessingthepowerofaparadigm,argumentsneedtobeadvancedastowhythechosenwayofdealingwiththeseissueshelpssoftwareengineersbuildsystemsmoreeffectively(section2.3).
2.2WhatisAgent-OrientedSoftware?
Atpresent,thereisagreatdealofongoingdebateaboutexactlywhatconstitutesanagent,yetthereisnothingapproachingauniversalconsensus.However,anincreasingnumberofresearch-ersfindthefollowingcharacterisationuseful
[41
]:
anagentisanencapsulatedcomputersystemthatissituatedinsomeenvironment,
andthatiscapableofflexible,autonomousactioninthatenvironmentinorderto
meetitsdesignobjectives
Thereareanumberofpointsaboutthisdefinitionthatrequirefurtherexplanation.Agentsare:(i)clearlyidentifiableproblemsolvingentitieswithwell-definedboundariesandinterfaces;(ii)situ-ated(embedded)inaparticularenvironment—theyreceiveinputsrelatedtothestateofthatenvi-ronmentthroughtheirsensorsandtheyactontheenvironmentthroughtheireffectors3;(iii)designedtofulfilaspecificrole—theyhaveparticularobjectivestoachieve,thatcaneitherbeexplicitlyorimplicitlyrepresentedwithintheagents;(iv)autonomous—theyhavecontrolbothovertheirinternalstateandovertheirownbehaviour;(v)capableofexhibitingflexible(context-dependent)problemsolvingbehaviour—theyneedtobereactive(abletorespondinatimelyfashiontochangesthatoccurintheirenvironmentinordertosatisfytheirdesignobjectives)andproactive(abletoopportunisticallyadoptnewgoalsandtaketheinitiativeinordertosatisfytheirdesignobjectives)
[42]
.
Whenadoptinganagent-orientedviewoftheworld,itsoonbecomesapparentthatasingleagentisinsufficient4.Mostproblemsrequireorinvolvemultipleagents:torepresentthedecentralisednatureoftheproblem,themultiplelociofcontrol,themultipleperspectives,orthecompetinginterests.Moreover,theagentswillneedtointeractwithoneanother,eithertoachievetheirindi-vidualobjectivesorelsetomanagethedependenciesthatensuefrombeingsituatedinacommonenvironment.Theseinteractionsrangefromsimplesemanticinteroperation(theabilitytoexchangecomprehensiblecommunications),throughtraditionalclient-servertypeinteractions(theabilitytorequestthataparticularactionisperformed),torichsocialinteractions(theabilitytocooperate,coordinateandnegotiateaboutacourseofaction).Whateverthenatureofthesocialprocess,however,therearetwopointsthatqualitativelydifferentiateagentinteractionsfrom
3.Typicallyeachagenthasapartialviewoftheenvironment(thatmayormaynotoverlapwiththatofothers)andalimitedsphereofinfluencethroughwhichitcanaltertheenvironment.
4.Itcanbearguedthatthereisnosuchthingasasingleagentsystem;everythinginvolvesmultipleagents.
6
thosethatoccurinothersoftwareengineeringparadigms.Firstly,agent-orientedinteractionsgen-erallyoccurthroughahigh-level(declarative)agentcommunicationlanguage(typicallybasedonspeechacttheory
[1]
).Consequently,interactionsareusuallyconductedattheknowledgelevel
[25]
:intermsofwhichgoalsshouldbefollowed,atwhattime,andbywhom(cf.methodinvoca-tionorfunctioncallsthatoperateatapurelysyntacticlevel).Secondly,asagentsareflexibleproblemsolvers,operatinginanenvironmentoverwhichtheyhaveonlypartialcontrolandobservability,interactionsneedtobehandledinasimilarlyflexiblemanner.Thus,agentsneedthecomputationalapparatustomakecontext-dependentdecisionsaboutthenatureandscopeoftheirinteractionsandtoinitiate(andrespondto)interactionsthatwerenotnecessarilyforeseenatdesigntime.
Inmostcases,agentsacttoachieveobjectivesonbehalfofindividualsorcompanies.Thus,whenagentsinteractthereistypicallysomeunderlyingorganisationalcontext.Thiscontexthelpsdefinethenatureoftherelationshipbetweentheagents.Forexample,theymaybepeersworkingtogetherinateam,onemaybethebossoftheothers,ortheymaybeinvolvedinaseriesofemployer-subcontractorrelationships.Tocapturesuchlinks,agentsystemsoftenhaveexplicitconstructsformodelingorganisationalrelationships(e.g.,peer,boss,etc.)andorganisationalstructures(e.g.,teams,groups,coalitions,etc.).Itshouldbenotedthatinmanycases,theserela-tionshipsmaychangewhilethesystemisoperating.Socialinteractionmeansexistingrelation-shipsevolve(e.g.,anagentawardsanewcontract)andnewrelationsarecreated(e.g.,anumberofagentsmayformateamtodeliveraparticularservicethatnooneindividualcanoffer).Thetemporalextentoftheserelationshipscanvaryenormously:fromjustlongenoughtodeliveraparticularserviceoncetoapermanentbond.Tocopewiththisvarietyanddynamicity,agentresearchershaveexpendedconsiderableeffort:devisingprotocolsthatenableorganisationalgroupingstobeformedanddisbanded,specifyingmechanismstoensuregroupingsacttogetherinacoherentfashion,anddevelopingstructurestocharacterisethemacrobehaviourofcollectives.
Drawingthesepointstogether(figure2),itcanbeseenthatadoptinganagent-orientedapproachtosoftwareengineeringmeansdecomposingtheproblemintomultiple,interacting,autonomouscomponents(agents)thathaveparticularobjectivestoachieve.Thekeyabstractionmodelsthatdefinethe“agent-orientedmindset”areagents,interactionsandorganisations.Finally,explicitstructuresandmechanismsareoftenavailablefordescribingandmanagingthecomplexandchangingweboforganisationalrelationshipsthatexistbetweentheagents.
7
Organisationalrelationship
.A3
A4
A2
Interaction
AiAgenti
A1
viewofenvironment/sphereofinfluence
A5
Environment
Figure2:Canonicalviewofamulti-agentsystem
2.3TheCaseforanAgent-OrientedApproach
Havingcharacterisedcomplexsystemsanddescribedagentsoftware,wenowconsiderwhysuchagent-orientedtechniquesarewellsuitedtodevelopingsuchsoftwaresystems.Thisargumenthasthreeparts:
•showthatagent-orienteddecompositionsareaneffectivewayofpartititioningtheprob-lemspaceofacomplexsystem(section2.3.1);
•showthatthekeyabstractionsoftheagent-orientedmindsetareanaturalmeansofmodel-ingcomplexsystems(section2.3.2);
•showthattheagent-orientedphilosophyforidentifyingandmanagingorganisationalrela-tionshipsisappropriatefordealingwiththedependenciesandinteractionsthatexistinacomplexsystem(section2.3.3).
Tomakethecaseforagent-orientedsoftwareengineeringevenmorecompelling,thefinalstepistoarguethatagent-orientedtechniquesrepresentagenuineadvanceoverthecurrentstateoftheart.Tothisend,theagent-orientedapproachwillbecomparedwithleading-edgetechniquesfrommainstreamsoftwareengineering(section2.3.4).Inparticular,thisinvolvescomparisonswithobject-orientedanalysisanddesign(systemisbuiltoutofinteractingobjectsthatencapsulatebothdataandtheproceduresthatoperateonthatdata
[3],[23])
andwithcomponent-ware(systemisbuiltbyassemblingpre-existingcomponentsintosomeoverallstructure
[38
]).
2.3.1Agent-OrientedDecompositions
Complexsystemsconsistofanumberofrelatedsub-systemsorganisedinahierarchicalfashion(figure1).Atanygivenlevel,thesub-systemsworktogethertoachievethefunctionalityoftheirparentsystem.Moreover,withinasub-system,theconstituentcomponentsworktogethertodelivertheoverallfunctionality.Thus,thesamebasicmodelofinteractingcomponents,working
8
togethertoachieveparticularobjectivesoccursthroughoutthesystem.
Giventheabovesituation,itisentirelynaturaltomodularisethecomponentsintermsoftheobjectivestheyachieve5.Inotherwords,eachcomponentcanbethoughtofasachievingoneormoreobjectives.Asecondimportantobservationisthatcurrentsoftwareengineeringtrendsaretowardsincreasingthedegreesoflocalisationandencapsulationinproblemdecompositions
[27]
.Applyingthisphilosophytoobjective-achievingdecompositionsmeansthattheindividualcom-ponentsshouldhavetheirownthreadofcontrol(i.e.,componentsshouldbeactive)andthattheyshouldencapsulatetheinformationandproblemsolvingabilityneededtomeettheseobjectives.Sincethecomponentstypicallyhavetooperateinanenvironmentinwhichtheyhaveonlypartialinformation,theymustbeabletodetermine,atrun-time,whichactionstheyshouldperforminpursuitoftheirobjectives.Inshort,componentsneedautonomyovertheirchoiceofaction.
Inorderfortheactiveandautonomouscomponentstofulfilboththeirindividualandcollectiveobjectives,theyneedtointeractwithoneanother(recallcomplexsystemsareonlynearlydecom-posable).Howeverthesystem’sinherentcomplexitymeansthatitisimpossibletoaprioriknowaboutallthepotentiallinks:interactionswilloccuratunpredictabletimes,forunpredictablerea-sons,betweenunpredictablecomponents.Forthisreason,itisfutiletotryandpredictoranalyseallthepossibilitiesatdesign-time.Itismorerealistictoendowthecomponentswiththeabilitytomakedecisionsaboutthenatureandscopeoftheirinteractionsatrun-time.Fromthisitfollowsthatcomponentsneedtheabilitytoinitiate(andrespondto)interactionsinaflexiblemanner.
Thepolicyofdeferringtorun-timedecisionsaboutcomponentinteractionsfacilitatestheengi-neeringofcomplexsystemsintwoways.Firstly,problemsassociatedwiththecouplingofcom-ponentsaresignificantlyreduced(bydealingwiththeminaflexibleanddeclarativemanner).Componentsarespecificallydesignedtodealwithunanticipatedrequestsandcangeneraterequestsforassistanceiftheyfindthemselvesindifficulty.Moreoverbecausetheseinteractionsareenactedthroughahigh-levelagentcommunicationlanguage,couplingbecomesaknowledge-levelissue.This,inturn,removessyntacticlevelconcernsfromthetypesoferrorscausedbyunexpectedinteractions.Secondly,theproblemofmanagingcontrolrelationshipsbetweenthesoftwarecomponents(ataskthatbedevilsmoretraditionalfunctionaldecompositions)issignifi-cantlyreduced.Allagentsarecontinuouslyactiveandanycoordinationorsynchronisationthatisrequiredishandledthroughinter-agentinteraction.Thus,theorderingofthesystem’stop-levelgoalsisnolongersomethingthathastoberigidlyprescribedatdesigntime.Rather,itbecomessomethingthatcanbehandledinacontext-sensitivemanneratrun-time.
Fromthisdiscussion,itisapparentthatanaturalwaytomodulariseacomplexsystemisintermsofmultiple,interacting,autonomouscomponentsthathaveparticularobjectivestoachieve.Inshort,agent-orienteddecompositionsmakeiteasiertodevelopcomplexsystems.
5.Theviewthatdecompositionsbaseduponfunctions/actions/processesaremoreintuitiveandeasiertoproducethanthosebasedupondata/objectsisevenacknowledgedwithintheobject-orientedcommunity(see,forexample,
[23]
pg44).
9
2.3.2TheAppropriatenessoftheAgent-OrientedAbstractions
Asignificantpartofalldesignendeavoursistofindtherightmodelsforviewingtheproblem.Ingeneral,therewillbemultiplecandidatesandthedifficulttaskispickingthemostappropriateone.Turningtothespecificcaseofdesigningsoftware,themostpowerfulabstractionsarethosethatminimisethesemanticgapbetweentheunitsofanalysisthatareintuitivelyusedtoconceptu-alisetheproblemandtheconstructspresentinthesolutionparadigm.Inourcase,theproblemtobecharacterisedconsistsofsub-systems,sub-systemcomponents,interactionsandorganisationalrelationships.Takingeachoftheseinturn:
•Thecaseforviewingsub-systemcomponentsasagentshasalreadybeenmadeabove(sec-tion2.3.1).
•Theinterplaybetweenthesub-systemsandbetweentheirconstituentcomponentsismostnaturallyviewedintermsofhigh-levelsocialinteractions:“atanygivenlevelofabstrac-tion,wefindmeaningfulcollectionsofobjectsthatcollaboratetoachievesomehigherlevelview”
[3]
pg34.Thisviewaccordspreciselywiththeknowledgelevel(orevensociallevel
[18]
)treatmentofinteractionaffordedbytheagent-orientedapproach.Agentsystemsareinvariablydescribedintermsof“cooperatingtoachievecommonobjectives”,“coordinatingtheiractions”or“negotiatingtoresolveconflicts”.Thus,theagent-orientedmindsetisentirelyappropriateforcapturingthetypesofinteractionthatoccurincomplexsystems.
•Complexsystemsinvolvechangingwebsofrelationshipsbetweentheirvariouscompo-nents.Theyalsorequirecollectionsofcomponentstobetreatedasasingleconceptualunitwhenviewedfromadifferentlevelofabstraction.Again,thisviewmatchescloselywiththeabstractionsprovidedbytheagent-orientedmindset.Thus,facilitiesaretypicallypro-videdforexplicitlyrepresentingorganisationalrelationships.Interactionprotocolshavebeendevelopedforformingnewgroupingsanddisbandingunwantedones.Finally,struc-turesareavailableformodelingcollectives.Thelatterpointisespeciallyusefulinrelationtorepresentingsub-systemssincetheyarenothingmorethanateamofcomponentswork-ingtogethertoachieveacollectivegoal.
2.3.3TheNeedforFlexibleManagementofChangingOrganisationalStructures
Complexsystemsinvolveavarietyoforganisationalrelationships,rangingfrompeerstocontrolhierarchies,fromtheshort-termtotheongoing.Theserelationshipsareimportantfortwomainreasons.Firstly,theyallowanumberofseparatecomponentstobegroupedtogetherandtreatedasasingleconceptualentity.Secondly,theyenablethehigh-levellinksbetweenthedifferententi-tiestobecharacterised.Giventheinfluenceandimpactoforganisationalrelationshipsandstruc-turesonsystembehaviour,theimportanceofprovidingexplicitsupportforflexiblyspecifyingandmanagingthemisself-evident.Moreover,giventhattheserelationshipsfrequentlychange,theabilitytodynamicallyadapttoprevailingcircumstancesisalsoessential.
10
Asalreadyindicated,organisationsarefirst-classentitiesinagentsystems.Thusexplicitstruc-turesandflexiblemechanismsarecentraltotheagentparadigm.Thisrepresentationalpower,whencoupledwiththesupportingcomputationalmechanisms,enablesagent-orientedsystemstoexploittwofacetsofthenatureofcomplexsystems.Firstly,thenotionofaprimitivecomponentcanbevariedaccordingtotheneedsoftheobserver.Thusatonelevel,entiresub-systemscanbeviewedasasingleton,alternativelyteamsorcollectionsofagentscanbeviewedasprimitivecomponents,andsoonuntilthesystemeventuallybottomsout.Secondly,suchstructuresprovideavarietyofstableintermediateforms,that,asalreadyindicated,areessentialfortherapiddevel-opmentofcomplexsystems.Theiravailabilitymeansthatindividualagentsororganisationalgroupingscanbedevelopedinrelativeisolationandthenaddedintothes
温馨提示
- 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
- 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
- 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
- 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
- 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
- 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
- 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
最新文档
- 《GBT 34690.7-2017 印刷技术 胶印数字化过程控制 第 7 部分:计算机直接制版》专题研究报告
- 《GBT 33290.5-2016 文物出境审核规范 第 5 部分:仪仗》专题研究报告
- 《GB-T 21021.1-2021无源射频和微波元器件的互调电平测量 第1部分:一般要求和测量方法》专题研究报告
- 《GBT 32581-2016 入侵和紧急报警系统技术要求》专题研究报告
- 《AQ-T 2035-2023金属非金属地下矿山供水施救系统建设规范》专题研究报告
- 《宠物鉴赏》课件-雪纳瑞
- 《Python语言程序设计》课件-7.2 理解数据的维度
- 《智慧景区服务与管理》课件-第二章 任务一 旅游景区票务服务
- 施工现场起重吊装隐患识别及安全技术应用
- 数字文旅景点导览信息服务协议
- (完整文本版)日文履历书(文本テンプレート)
- 国家开放大学《管理英语4》边学边练Unit 5-8(答案全)
- 时尚·魅力-大学生魅商修炼手册智慧树知到期末考试答案章节答案2024年南昌大学
- 《金牌店长培训》课件
- 电工培训触电急救课件
- 宜昌市点军区2023-2024学年七年级上学期期末数学综合测试卷(含答案)
- 井下单项、零星工程管理制度模版
- 道路危险货物运输企业安全生产标准化评价实施细则
- ESD静电防护检测及管控标准
- 卧床病人的护理即翻身技巧课件
- 智能信报箱系统施工方案
评论
0/150
提交评论