软件工程:Computer-BasedSystemEngineering.ppt_第1页
软件工程:Computer-BasedSystemEngineering.ppt_第2页
软件工程:Computer-BasedSystemEngineering.ppt_第3页
软件工程:Computer-BasedSystemEngineering.ppt_第4页
软件工程:Computer-BasedSystemEngineering.ppt_第5页
已阅读5页,还剩43页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

Chapter2 Computer BasedSystemEngineering SystemsEngineering Designing implementing deployingandoperatingsystemswhichincludehardware softwareandpeople Objectives ToexplainwhysystemsoftwareisaffectedbybroadersystemengineeringissuesTointroducetheconceptofemergentsystempropertiessuchasreliabilityandsecurityToexplainwhythesystemsenvironmentmustbeconsideredinthesystemdesignprocessToexplainsystemengineeringandsystemprocurementprocesses Topicscovered EmergentsystempropertiesSystemsandtheirenvironmentSystemmodellingThesystemengineeringprocessSystemprocurement Whatisasystem Apurposefulcollectionofinter relatedcomponentsworkingtogethertowardssomecommonobjective Asystemmayincludesoftware mechanical electricalandelectronichardwareandbeoperatedbypeople SystemcomponentsaredependentonothersystemcomponentsThepropertiesandbehaviourofsystemcomponentsareinextricablyinter mingled Problemsofsystemsengineering Largesystemsareusuallydesignedtosolve wicked problemsSystemsengineeringrequiresagreatdealofco ordinationacrossdisciplinesAlmostinfinitepossibilitiesfordesigntrade offsacrosscomponentsMutualdistrustandlackofunderstandingacrossengineeringdisciplinesSystemsmustbedesignedtolastmanyyearsinachangingenvironment Softwareandsystemsengineering Theproportionofsoftwareinsystemsisincreasing Software drivengeneralpurposeelectronicsisreplacingspecial purposesystemsProblemsofsystemsengineeringaresimilartoproblemsofsoftwareengineeringSoftwareis unfortunately seenasaprobleminsystemsengineering Manylargesystemprojectshavebeendelayedbecauseofsoftwareproblems Emergentproperties PropertiesofthesystemasawholeratherthanpropertiesthatcanbederivedfromthepropertiesofcomponentsofasystemEmergentpropertiesareaconsequenceoftherelationshipsbetweensystemcomponentsTheycanthereforeonlybeassessedandmeasuredoncethecomponentshavebeenintegratedintoasystem Examplesofemergentproperties TheoverallweightofthesystemThisisanexampleofanemergentpropertythatcanbecomputedfromindividualcomponentproperties ThereliabilityofthesystemThisdependsonthereliabilityofsystemcomponentsandtherelationshipsbetweenthecomponents TheusabilityofasystemThisisacomplexpropertywhichisnotsimplydependentonthesystemhardwareandsoftwarebutalsodependsonthesystemoperatorsandtheenvironmentwhereitisused Typesofemergentproperty FunctionalpropertiesTheseappearwhenallthepartsofasystemworktogethertoachievesomeobjective Forexample abicyclehasthefunctionalpropertyofbeingatransportationdeviceonceithasbeenassembledfromitscomponents Non functionalemergentpropertiesExamplesarereliability performance safety andsecurity Theserelatetothebehaviourofthesysteminitsoperationalenvironment Theyareoftencriticalforcomputer basedsystemsasfailuretoachievesomeminimaldefinedlevelinthesepropertiesmaymakethesystemunusable Becauseofcomponentinter dependencies faultscanbepropagatedthroughthesystemSystemfailuresoftenoccurbecauseofunforeseeninter relationshipsbetweencomponentsItisprobablyimpossibletoanticipateallpossiblecomponentrelationshipsSoftwarereliabilitymeasuresmaygiveafalsepictureofthesystemreliability Systemreliabilityengineering HardwarereliabilityWhatistheprobabilityofahardwarecomponentfailingandhowlongdoesittaketorepairthatcomponent SoftwarereliabilityHowlikelyisitthatasoftwarecomponentwillproduceanincorrectoutput Softwarefailureisusuallydistinctfromhardwarefailureinthatsoftwaredoesnotwearout OperatorreliabilityHowlikelyisitthattheoperatorofasystemwillmakeanerror Influencesonreliability Reliabilityrelationships HardwarefailurecangeneratespurioussignalsthatareoutsidetherangeofinputsexpectedbythesoftwareSoftwareerrorscancausealarmstobeactivatedwhichcauseoperatorstressandleadtooperatorerrorsTheenvironmentinwhichasystemisinstalledcanaffectitsreliability The shall not properties PropertiessuchasperformanceandreliabilitycanbemeasuredHowever somepropertiesarepropertiesthatthesystemshouldnotexhibitSafety thesystemshouldnotbehaveinanunsafewaySecurity thesystemshouldnotpermitunauthoriseduseMeasuringorassessingthesepropertiesisveryhard Systemsandtheirenvironment SystemsarenotindependentbutexistinanenvironmentSystem sfunctionmaybetochangeitsenvironmentEnvironmentaffectsthefunctioningofthesysteme g systemmayrequireelectricalsupplyfromitsenvironmentTheorganizationalaswellasthephysicalenvironmentmaybeimportant Systemhierarchies Humanandorganisationalfactors ProcesschangesDoesthesystemrequirechangestotheworkprocessesintheenvironment JobchangesDoesthesystemde skilltheusersinanenvironmentorcausethemtochangethewaytheywork OrganisationalchangesDoesthesystemchangethepoliticalpowerstructureinanorganisation Systemarchitecturemodelling Anarchitecturalmodelpresentsanabstractviewofthesub systemsmakingupasystemMayincludemajorinformationflowsbetweensub systemsUsuallypresentedasablockdiagramMayidentifydifferenttypesoffunctionalcomponentinthemodel Intruderalarmsystem Componenttypesinalarmsystem SensorMovementsensor doorsensorActuatorSirenCommunicationTelephonecallerCo ordinationAlarmcontrollerInterfaceVoicesynthesizer IanSommerville1995SoftwareEngineering 5thedition Chapter31 Slide ATCsystemarchitecture Functionalsystemcomponents SensorcomponentsActuatorcomponentsComputationcomponentsCommunicationcomponentsCo ordinationcomponentsInterfacecomponents Systemcomponents SensorcomponentsCollectinformationfromthesystem senvironmente g radarsinanairtrafficcontrolsystemActuatorcomponentsCausesomechangeinthesystem senvironmente g valvesinaprocesscontrolsystemwhichincreaseordecreasematerialflowinapipeComputationcomponentsCarryoutsomecomputationsonaninputtoproduceanoutpute g afloatingpointprocessorinacomputersystem Systemcomponents CommunicationcomponentsAworklinkingdistributedcomputersCo ordinationcomponentsCo ordinatetheinteractionsofothersystemcomponentse g schedulerinareal timesystemInterfacecomponentsFacilitatetheinteractionsofothersystemcomponentse g operatorinterfaceAllcomponentsarenowusuallysoftwarecontrolled Componenttypesinalarmsystem SensorMovementsensor DoorsensorActuatorSirenCommunicationTelephonecallerCoordinationAlarmcontrollerInterfaceVoicesynthesizer Thesystemengineeringprocess Usuallyfollowsa waterfall modelbecauseoftheneedforparalleldevelopmentofdifferentpartsofthesystemLittlescopeforiterationbetweenphasesbecausehardwarechangesareveryexpensive SoftwaremayhavetocompensateforhardwareproblemsInevitablyinvolvesengineersfromdifferentdisciplineswhomustworktogetherMuchscopeformisunderstandinghere Differentdisciplinesuseadifferentvocabularyandmuchnegotiationisrequired Engineersmayhavepersonalagendastofulfil Thesystemengineeringprocess Inter disciplinaryinvolvement Systemrequirementsdefinition ThreetypesofrequirementdefinedatthisstageAbstractfunctionalrequirements SystemfunctionsaredefinedinanabstractwaySystemproperties Non functionalrequirementsforthesystemingeneralaredefinedUndesirablecharacteristics UnacceptablesystembehaviourisspecifiedShouldalsodefineoverallorganisationalobjectivesforthesystem Systemobjectives FunctionalobjectivesToprovideafireandintruderalarmsystemforthebuildingwhichwillprovideinternalandexternalwarningoffireorunauthorizedintrusionOrganisationalobjectivesToensurethatthenormalfunctioningofworkcarriedoutinthebuildingisnotseriouslydisruptedbyeventssuchasfireandunauthorizedintrusion Systemrequirementsproblems ChangingasthesystemisbeingspecifiedMustanticipatehardware communicationsdevelopmentsoverthelifetimeofthesystemHardtodefinenon functionalrequirements particularly withoutanimpressionofcomponentstructureofthesystem Thesystemdesignprocess PartitionrequirementsOrganiserequirementsintorelatedgroupsIdentifysub systemsIdentifyasetofsub systemswhichcollectivelycanmeetthesystemrequirementsAssignrequirementstosub systemsCausesparticularproblemswhenCOTSareintegratedSpecifysub systemfunctionalityDefinesub systeminterfacesCriticalactivityforparallelsub systemdevelopment Thesystemdesignprocess Systemdesignproblems Requirementspartitioningtohardware softwareandhumancomponentsmayinvolvealotofnegotiationDifficultdesignproblemsareoftenassumedtobereadilysolvedusingsoftwareHardwareplatformsmaybeinappropriateforsoftwarerequirementssosoftwaremustcompensateforthis Sub systemdevelopment Typicallyparallelprojectsdevelopingthehardware softwareandcommunicationsMayinvolvesomeCOTS CommercialOff the Shelf systemsprocurementLackofcommunicationacrossimplementationteamsBureaucraticandslowmechanismforproposingsystemchangesmeansthatthedevelopmentschedulemaybeextendedbecauseoftheneedforrework Theprocessofputtinghardware softwareandpeopletogethertomakeasystemShouldbetackledincrementallysothatsub systemsareintegratedoneatatimeInterfaceproblemsbetweensub systemsareusuallyfoundatthisstageMaybeproblemswithuncoordinateddeliveriesofsystemcomponents Systemintegration EnvironmentalassumptionsmaybeincorrectMaybehumanresistancetotheintroductionofanewsystemSystemmayhavetocoexistwithalternativesystemsforsometimeMaybephysicalinstallationproblems e g cablingproblems Operatortraininghastobeidentified Systeminstallation WillbringunforeseenrequirementstolightUsersmayusethesysteminawaywhichisnotanticipatedbysystemdesignersMayrevealproblemsintheinteractionwithothersystemsPhysicalproblemsofincompatibilityDataconversionproblemsIncreasedoperatorerrorratebecauseofinconsistentinterfaces Systemoperation Systemevolution Largesystemshavealonglifetime TheymustevolvetomeetchangingrequirementsEvolutionisinherentlycostlyChangesmustbeanalysedfromatechnicalandbusinessperspectiveSub systemsinteractsounanticipatedproblemscanariseThereisrarelyarationalefororiginaldesigndecisionsSystemstructureiscorruptedaschangesaremadetoitExistingsystemswhichmustbemaintainedaresometimescalledlegacysystems Systemdecommissioning TakingthesystemoutofserviceafteritsusefullifetimeMayrequireremovalofmaterials e g dangerouschemicals whichpollutetheenvironmentShouldbeplannedforinthesystemdesignbyencapsulationMayrequiredatatoberestructuredandconvertedtobeusedinsomeothersystem Systemprocurement AcquiringasystemforanorganizationtomeetsomeneedSomesystemspecificationandarchitecturaldesignisusuallynecessarybeforeprocurementYouneedaspecificationtoletacontractforsystemdevelopmentThespecificationmayallowyoutobuyacommercialoff the shelf COTS system Almostalwayscheaperthandevelopingasystemfromscratch Thesystemprocurementprocess Procurementissues Requirementsmayhavetobemodifiedtomatchthecapabilitiesofoff the shelfcomponentsTherequirementsspecificationmaybepartofthecontractforthedevelopmentofthesystemThereisusuallyacontractnegotiationperiodtoagreechangesafterthecontractortobuilda

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论