使用分层体系结构管理分布式软件项目的可能角色.(IJITCS-V7-N7-7)

I.J.InformationTechnologyandComputerScience,2015,07,57-65PublishedOnlineJune2015inMECS()DOI:10.5815/ijitcs.2015.07.07Copyright©2015MECSI.J.InformationTechnologyandComputerScience,2015,07,57-65ManagementofPossibleRolesforDistributedSoftwareProjectsUsingLayerArchitectureYumnamSubadaniDevi,LaishramPrabhakarManipurInstituteofManagementStudies,ManipurUniversity,Canchipur,Imphal795003,Manipur,IndiaEmail:[e-mail],[e-mail]—SeveralmembersareinvolvedindevelopmentandmanagementoftheDistributedSoftwareProjects.Eachmemberneedstoknowtheresponsibilitiesofeachotherforpropermanagementoftheactivitiesofsuchdistributedprojectstoproducecoherentoutcomes.Distributionmiddlewaresoftwarehashigher-leveldistributedprogrammingmodelswhosereusableAPIs(applicationprogramminginterface)andcomponentsautomateandextendnativeoperatingsystemcapabilities.SoftwaremanagementtoolslikeWorkbreak-downstructure(WBS),Ganttchart,CriticalPathMethod,andCriticalChainMethodetc.doesnotfullyhelpthemanagerstomanagethemember'sresponsibilitiesduringthedevelopmentofdistributedapplications.Thelayeredarchitecturecanhelptodoso.Thisstylenotonlygivesthelayerleveldescriptionoftheactivityinvolved,italsodefinesanddirectsthegroupofworkforce.Bylistingthegroupsofworkforce,thedevelopmentteamaswellasthecustomercanknowtheactivityandthememberinvolvedtoworkonthosespecificactivities.Thislayeredarchitectureismuchbenefitedtodevelopmentteamandalsotonumbersofstakeholderofthelargedistributedproject.Theextendednewapproachoflayerpatternwith'ResponsibilityIndex'addsextravaluetomanageallthemembers'responsibilities.Managers,stakeholdersandotherscanhaveaneasymanagementsystem.Therequestorcomplaintfromthecustomercanbepassedtoappropriateteamwithoutmuchdelay.Mostimportantlythiswillgivefacilitytocollecttimelyfeedbackfromalllevelsofcustomers.IndexTerms—LayerArchitecture,ResponsibilityIndex,TeamManagement,CustomerService,DistributedProjectsI.INTRODUCTIONMostoftoday'ssoftwareprojectsaregeographicallydistributedwithlimitedface-to-faceinteractionbetweenparticipants.Atypicalsoftwaredevelopmentlifecyclehasseveralphases.Someofthephasesarerequirementanalysis,Designing,Implementationorcoding,Testing,DeploymentandMaintenance.Severalpeople(developmentteam)andstakeholdersandcustomersworkondifferentcycleorphaseofaproject.Agoodcontrolisrequiredtomaintainoverthelifeoftheprojectbyateamleadoraprojectmanager.Itcouldbeeasytomanagesuchaprojectifalltheevolvingpeopleareresidesinoneplaceorwithinsomedefinelocation.Howeveritwillbedifficulttomanageifmanypeopleworkfromdifferentlocationswithdifferenttimezoneandmovingfromplacetoplaceduringaphaseofproject.Managermuchusesappropriatetoolstocontrol,supportandmanagetheentireteam.Managermusthavefollowingknowledgetomanageadistributedprojectsanditsteamtobuildteamsacrosssitestobreakdownthetasksanddistributetoshareknowledgeaspertime,space,andotherdifferences,andtocoordinatetheworktoproducebestoutcomes[1].Thedistributedprojectshavedifficultyofcoordination.Managementbecomesmorechallengingandtroublesometomakethe'teams’toworkeffectivelyanddeliveringbetteroutcomesontimeandwithinbudget.Tomanagesuchdistributedprojects,thesoftwaredesignpatternsareused.Adesignpatternisatemplateofformalizedbestpracticestosolveaproblem.Differentpatternsareusedfordifferentactivitiesofmanagingasoftwaredevelopment.Layeredarchitectureisoneofcommondesignpatternusesforallocatingandmanagingthedifferentresponsibilitiesofateamduringalifecycleofsoftwaredevelopment[2].HoweverthetraditionalLayeredarchitecturedoesnothavefacilitytoupdatethestatusofprojectonsuddenchanges.Anynewchangesoftherolesofanymemberorupdateofthestatusoftheprojectshouldbeavailabletoentireteamforpropermanagementandcommonunderstanding.Thisstudyproposedanewconcept‘ResponsibilityIndex’toincorporatewithtraditionallayerarchitecturetomanagealltheresponsibilitiesofalargeproject.Thisconceptwillhelptomanagealltherolesorresponsibilitiesofmembersinvolvedinalargedistributedproject.TheIndexwillbeautomaticallyupdatedwhenarolechangesandteammemberwillknowroleofeachother.Itwillhelpthedevelopmentteam,stakeholderandcustomertocomecloser.Customerwillknowtheirdesignateddeveloper.Thiswillminimizedelaysinhandlingticket(complaints)bymaintenanceteams.Itwillimproverelationwithcustomerandstakeholder.Itwillalsohelpintimelycollectionoffeedbacksfromthecustomers.Thiswillhelptobringallinvolvingmemberscloserreducingthecommunicationgap.A.TheconceptofsoftwaredevelopmenttoolsTherearedifferentphasesinlifecycleofasoftwareprojectstartingfromrequirementgatheringtodeploymentandmaintenanceoftheproject.Theroleandresponsibilitiesaredifferentforexecutingdifferentphasesofthelifecycleofsoftware.Itmaynoteasytomanagealltherolesandresponsibilitiesforadistributedproject.SoftwaremanagementtoolslikeWorkbreak-58ManagementofPossibleRolesforDistributedSoftwareProjectsUsingLayerArchitectureCopyright©2015MECSI.J.InformationTechnologyandComputerScience,2015,07,57-65downstructure(WBS),GanttCharts,CriticalPathMethod,CriticalChainMethod,ProgramEvaluationan