系统架构.docx
- 文档编号:26349390
- 上传时间:2023-06-18
- 格式:DOCX
- 页数:13
- 大小:36.32KB
系统架构.docx
《系统架构.docx》由会员分享,可在线阅读,更多相关《系统架构.docx(13页珍藏版)》请在冰豆网上搜索。
系统架构
SystemArchitectureDesignDocument
No:
010-XXXXXX-XXRev:
XX
Revision#
ECO#
Revision#
ECO#
Title:
EnterDocumentTitleHere
Product(s):
EnterPartNumber(s)ofApplicableProduct(s)Here
NOTE:
EnterFieldinformation(shadedareas)bydouble-clickingonthefield,thenentertheinformationintheDefaultTextBox.
Don’tworryabouttheserednotes,theyWILLNOTPRINTonyourprinter.
Preparedby:
EnterNameHere
NOTE:
EnterFieldinformation(shadedareas)bydouble-clickingonthefield,thenentertheinformationintheDefaultTextBox.
Don’tworryabouttheserednotes,theyWILLNOTPRINTonyourprinter.
Prep’dDate:
(m/d/y)
m/d/YYYY
NOTE:
EnterFieldinformation(shadedareas)bydouble-clickingonthefield,thenentertheinformationintheDefaultTextBox.
Don’tworryabouttheserednotes,theyWILLNOTPRINTonyourprinter.
DetailedRevisionHistory
Rev
DescriptionofChanges
1
1.Describeeachchangetothedocumentwithitsownitemnumber.Describewherethechangeditemislocatedinthedocument(whatsection),whatitemchanged,whatitchangedfromandwhatitchangedto.Forexample:
“Insection3.2changed‘shallusePhilips-headscrews’to‘shallusemachine-headscrews’.”Iftherearemorethanadozenchangestoadocumentthenitispermissibletostate“Substantialchanges.Seedocument.”Insteadoflistingthemallseparately.
TableofContents
1.DocumentInformation5
1.1.Purpose,ScopeandIntendedAudience5
1.2.DocumentConventions5
1.3.CIM-SpecificAcronymsandAbbreviations5
1.4.ApplicableDocuments5
1.5.ReferenceDocuments6
2.SystemArchitecture7
2.1.OverviewofProduct(s)/System7
2.2.PhysicalDescriptionandBreakdown7
2.3.FunctionalDescriptionandBreakdown8
2.4.PrimaryRequirementFlow-downs8
2.4.1.Power9
2.4.2.Input/OutputSignalProcessing10
2.4.3.PhysicalStructureandIndustrialDesign10
2.4.4.HarnessingandInterconnects10
2.4.5.HeatManagement11
2.4.6.EMCManagement11
2.4.7.Manufacturability11
2.4.8.Serviceability11
2.4.9.Environmental11
2.4.10.Reliability11
2.4.11.SafetyandRegulatory11
2.4.12.Cost12
3.ModuleandMajorComponentDescriptions12
3.1.ModuleA12
3.2.ModuleB12
3.3.ModuleC12
AppendixA:
Architecture-SpecificDesignPrinciplesandStandards13
AppendixB:
Industry-StandardAcronymsandAbbreviations14
TableofFigures
Figure1.Thisisacaption.8
ListofTables
Table1.ApplicableDocuments6
Table2.ReferenceDocuments7
Table3.Harnesses13
1.DocumentInformation
1.1.Purpose,ScopeandIntendedAudience
Statewhythedocumentexists,howitshouldbeused,whatitcovers(inbrief)andwhoitwaswrittenfor.
1.2.DocumentConventions
Thissectionstatesthewritingconventionsusedinthebodyofthedocument.Useverbatimthe“boilerplate”textbelowthissentenceanddeleteboththissentenceandtheonethatprecedesit:
Thetermsusedinthisdocumentaredefinedasfollows:
∙“Shall”or“must”isusedtoindicateamandatoryrequirement.
∙“Will”isusedtoindicateintent.
∙“Should”isusedtoindicateapreferredalternativeordesigngoal,butisnotmandatory.
∙“May”isusedtoindicateanoption.
TheNoteStyle(“Note:
”)isusedforcommentsthathelpexplainastatementorotherelementofthedocument.Commentsthathelpexplainarequirementshallnotthemselvescontainadditionalrequirements.
1.3.CIM-SpecificAcronymsandAbbreviations
Thisisalistexpandingorexplainingthemeaningofcodenames,acronyms(includinginitialisms)andabbreviationsappearinginthedocumentthatareonlyusedwithinCIM,includingthosethatarecreatedfortheproductswhosearchitecturesaredescribedinthisdocument.TheyusuallyrefertoaCIMproduct,moduleorcomponent.Descriptionsshouldbekeptbrief.
1.4.ApplicableDocuments
AnapplicabledocumentisanydocumentyoureferencethatispartofadesignrequirementstatedintheSystemArchitecturedocument.Listallsuchdocumentsinthissection.Alldocumentsthatarenotreferencedaspartofadesignrequirementgointhe“ReferenceDocuments”sectionbelow.
Forexample,itmightbestatedthatallmechanicalpartsinthesystemaretobedesignedaccordingtospecificguidelinesstatedinaCIMMechanicalDesignGuidelinesdocument.Inotherwords,specificquidelinesfromthatdocumentbecomeactualdesignrequirements.Consequently,theCIMMechanicalDesignGuidelinesbecomesanapplicabledocument.
AnyrequirementgivenintheSystemArchitecturedocumentshallstrictlyconcernhowthesystemisdesigned.WhenperformancespecificationsandfunctionalrequirementsaredescribedintheSystemArchitecturedocumenttheyaretobeconsideredasreferenceonly;thecorrectdocument(s)inwhichtostatethemasrequirementsaretherelevantProductSpecification(s).
NotethatModuleSpecificationdocumentsarenotapplicabledocuments;theyarereferencedocuments.AModuleSpecificationdocumentcontainsalltherequirementsforaparticularmodule.Sincemostofthose“flowdown”fromthesystemarchitecturetheycan’tbeconsideredrequirementsforthatarchitecture;theyareeffectsofthearchitecture,notthecause.However,anyrequirementimposedonamoduleintheSystemArchitecturedocument,suchastheexampleaboveofmechanicaldesignrequirements,mustberestatedasarequirementintherelevantModuleSpecification.
Usethefollowingtableformattolistapplicabledocuments.Foreachdocument,thetablelistsaPartNumber,aversionnumberandaDescription,thelattertypicallythenameofthedocument.Prefacethetablewiththefollowingtext(omittingthequotes):
“Thefollowingapplicabledocumentsformapartofthisspecificationtotheextentspecifiedherein.”
Iftherearenoapplicabledocuments,eplacetheentiretablewiththewords“Notapplicable.”anddeletethetablecaption.
Table1.ApplicableDocuments
DocumentNo.
Version
Name/Description
1.5.ReferenceDocuments
Thissectioncontainsatablethatlistsallthedocumentsreferencedlaterinthedocumentotherthanapplicabledocuments.
Usethefollowingtableformatforreferencedocuments.Notethatwhileaversionnumberisnotmandatoryitshouldbestatedwhenknown;itisunderstoodthattheremaybemorerecentversionsthanarestatedinthetable.NotethattherelevantProductSpecificationdocumentsandModuleSpecificationdocumentsaremandatoryreferencedocuments.
Prefacethetablewiththefollowingtext(omittingthequotes):
”Thereferencedocumentsshallbeconsideredasprovidingbackgroundinformationorreferencematerialonly,andshouldnotbeconsideredaspartofthisspecification.”
Table2.ReferenceDocuments
DocumentNo.
Version
Name/Description
2.SystemArchitecture
2.1.OverviewofProduct(s)/System
Thissectionbrieflydescribestheproductorproducts(inthecaseofaproductfamily)orsystemofproducts(inthecaseofmultipleproductsthatformasystem)thatthesystemarchitectureappliesto.Providehereonlyenoughdetailforthereadertogetagoodunderstandingofwhatthesystemarchitectureistryingtoaccomplishintermsoffeatures,functionsandperformance.
Anyproductrequirementsstatedinthissectionaretobeconsideredbythereaderasbeingprovidedforreferenceonly.TheofficialsourceforalltherequirementsoftheproductistherelevantProductSpecificationdocument,whichmustbelistedintheReferenceDocumenttable.
2.2.PhysicalDescriptionandBreakdown
Thissectiononlyappliestoandhenceisonlyrequiredforphysicalsystems.Itisnotrequiredforasystemthatispurelysoftware(e.g.,applicationsoftware).
Thissectiondescribeshowthesystemisorganizedintophysicalmodulesandcomponentsaswellashowthosevariouspiecesareconnectedandassembledtogether.Atabletolistthemodulesandmajorcomponents
Touseahealthmonitoringsystemasanexample,manyofthemoduleswillbeelectricalinnatureandbasedoncircuitboards.Somecomponentsareelectro-mechanicalinnature.Othercomponentsarestrictlymechanicalinnaturesuchastheframe,skins,brackets,etc.
Thedescriptionmustalsoincludeanyharnessesinthesystem.Ingeneraltermsdescribethekindsofsignalstheycarryaswellasthekindandnumberofconductorsandtheterminatingconnectorsused.DetailsoftheharnessesshouldnotbedescribedherebutinaseparateInterfaceControlDocumentor,ifthesystemisverysimple(withveryfewharnesses),inalatersection.
Ablockdiagramofthemajormodulesandcomponentsshowinghowtheyconnectshallbeincludedinthissection.Thediagramshouldidentifythekindsofsignalsflowingbetweenthemodules/componentsandtheirdirections.However,unlessthesystemisofverylowcomplexitythediagramshouldnotshowdetailsdowntothelevelofpart-numberedharnesses.ForsuchdetailsreferenceshouldbemadetoanInterfaceControlDocument(ICD)and/oradetailedinterconnectdiagram.
Atextboxisusuallythebestwaytoinsertdiagramsintodocuments.Afterinsertingapicturetoreplaceanytextinthebox,rightclickonthetextboxmarginanduseFormatTextBox…tooptionallychangehowthepictureappearswiththesurroundingtext(Layout)and,alsooptionally,removetheborderbyselecting“Nocolor”forLineunderColorsandLines.
Figure1.Thisisacaption.
Copyitforotherdiagrams.Replacethetextonthecaptionlinewithyourown.Trytokeepthecaptionshort.Deletethesesentencesbelowthecaption.Resizethetextboxasrequiredtofityourcaptiontext.
2.3.FunctionalDescriptionandBreakdown
Thissectiondescribesthefunctions
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- 系统 架构