EHSS Preliminary Design.docx
《EHSS Preliminary Design.docx》由会员分享,可在线阅读,更多相关《EHSS Preliminary Design.docx(18页珍藏版)》请在冰豆网上搜索。
EHSSPreliminaryDesign
DoberGroup
EnvironmentHealthSafetyandSecurity(EHSS)
PreliminaryDesign
PDDate:
04/18/2008
Author:
ProjectManager:
Version
Date
Description
UpdatedBy
AffectedPages
1.0
04/11/2008
Draftforreview
Allpages
1.1
05/05/2008
Improveandincreasesomesectionsafterreview
Allpages
1.1
05/21/2008
Updatedfunctionmodulesimageandaddeddatamodel
Page6,7
1.1
05/22/2008
ImprovesomesectionsafterreviewbyGeorge
Allpages
SIGNATURES
Preparedby:
Author
Date
04/18/2008
Approvedby:
CustomerRepresentative
Date
Management/Lead
Date
Stakeholder
Date
Stakeholder
Date
Stakeholder
Date
TABLEofCONTENTS
1.Introduction3
1.1DocumentPurpose3
1.2DocumentScope3
1.3Definitions,Acronyms,andAbbreviations3
1.4References3
2.RunningEnvironment3
2.1SoftwareEnvironment4
2.2HardwareEnvironment4
3.ArchitectureDesignCriteria4
4.SoftwareArchitectureDescription4
4.1GeneralArchitecture4
4.1.1Overview4
4.1.2BasicLogicalArchitecture5
5.SystemFunctionDesign5
5.1GeneralModel5
5.1.1DataModel5
5.1.2Functionmodules7
5.1.3Interface7
5.2FunctionModuleDescriptions8
5.2.1Loginmodule8
5.2.2UserRole&AccessRights8
5.2.3Handlemessages10
5.2.4Handleexception11
5.2.5Workflow11
6.Design&DevelopEnvironments14
6.1OperationalEnvironments14
6.1.1Development14
6.1.2QC14
7.NonfunctionalRequirementDesign15
7.1NamingConventions15
7.2Performanceandspeed15
8.Technology16
AppendixA:
Acronyms16
1.Introduction
1.1DocumentPurpose
InthisphasewewilldothepreliminarydesignofDoberEHSSsystemmodelbasedonthesystemrequirementsanalysis.Thisistooutlinethemainsolutiontoimplementproceduremoduleofthesystemrequirements,includinghowtodividethesystemintoseveralmodules,decisionofthemodulesInterface,informationtransmission,datastructureanddesignofthemodulestructure,etc.
Inthenextdetaildesignstage,wewilltakethepreliminarydesignasreferenceandworkoutamorespecificdetaildesign.
1.2DocumentScope
Thedesignwillcoverthefollowingmainfeatures.
●ManageEHSSData
●ManageMSDS
●ManageLabel
●Printingdocuments
●Security
●Interface
1.3Definitions,Acronyms,andAbbreviations
EHSS
EnvironmentalHealthSafetySecurity
MSDS
MaterialSafetyDataSheet
JDE
JDEdwards
1.4References
Name
URL
DoberGroupRequirements_v1.7.doc
Management/DoberGroupRequirements_v1.7.doc
DoberEHSSSRS.doc
Management/DoberEHSSSRS.doc
2.RunningEnvironment
2.1SoftwareEnvironment
Operatingsystem
Windowsserver2003R2
WebServer
IIS6.0orhigher
Runtimeframework
.Netframework2.0
Database
MSSQLServer2000standardeditionwithsp4
Browser
IEorFirefox
Office
MSWord,AdobeReaderprofessional
2.2HardwareEnvironment
Disk
80GbSATAdrivesx2RAID1
Memory
2GBRAM
3.ArchitectureDesignCriteria
●Usability
●Performance
●Maintainability&Manageability
●Lowercost
●Reliability
4.SoftwareArchitectureDescription
4.1GeneralArchitecture
4.1.1Overview
●Architecture:
Thissystemwillbebuiltasawebapplicationbyusing3-tierarchitecturewith2.0framework:
A3-tierarchitectureprovidesabilitytoscaleaswellseparatesbusinesslogicfromthepresentation(webbrowserpages).
1.TheWebuserinterface.
Itcontainsallthingsthatarevisibletotheuser.TheUIlayerhastechniqueslikeHTML,CSS,javascript,aspx
2.BusinessLogicLayer
Thisisthecoreofthesystem.Itcontainsallimportantrulesandlogic.ThislayeralsoinvokestheDatalayerforrequestsneededfromthedatabaseoranythirdpartyinterfacetodelivertotheWebUserInterface.
3.DataaccessandstorageLayer.
Thislayertakescareofpersistence.AnobjectfromtheDataAccessLayercanwriteitselftooneormoretables.Thismaincompositionofthislayercomprisesofthedatabaseconnection,SQLquerystringsandresultsets.
●Framework:
.NETFramework2.0
●Database:
SQLServer2000
4.1.2BasicLogicalArchitecture
Seebelowcomponentsdiagram:
Datatransferbetweenfront-endandback-end
5.SystemFunctionDesign
5.1GeneralModel
5.1.1DataModel
Referto
Formoredetailinformation,pleaseseethelink:
5.1.2Functionmodules
5.1.3Interface
●JDEdwardswillcontinuetohousetheproductsmasterwhichincludesauniqueproductkeythatwillbesharedwiththeEHSSapplication.Allinterfacelookupswillutilizethisuniquekey.
EHSSinterfacewithDobersystems:
5.2FunctionModuleDescriptions
5.2.1Loginmodule
UsingAD(Microsoft’sActiveDirectory)authenticationmodel,datasourcefromwithinDoberdomainaccounts
5.2.2UserRole&AccessRights
AD(ActiveDirectory)canstoretheusername,password,andthegroupname.ButitwillnotstoretheuseraccessrightsintheEHSSsystem.
Thereare3rolesinthesystem:
ADGroupName/RoleName
RoleID
AccessRightsDescription
author
FromADGroupID
Authorrolehasthesystemadminright.
suchascreate/editEHSSdata,exporttopdfetc.
viewer
FromADGroupID
ViewerrolecanonlyviewthepublishedMSDSandlabel.
lab
FromADGroupID
Employeeinlabplaysthisrole,andtheycanviewallEHSSinformation,butcannotmodify(thantheviewertoseesomemore,butnottheauthor)
Note:
●There’salimitationinconfiguringADgroupstoaccesstheEHSSsysteminAD,threerolesneedtobecreatedandmappedtoanIDintheADdistributethelimitsfordifferentdistinctionsasdescribedinthetableabove.
●InadditionauserinformationextendtableneedstobecreatedformappingADuseraccountsandstoringindividualcustomizeinformation,suchas“Idonotlikecautionmessagewhenprinting”.
●Forenhancingtheperformance,youcandetermineifyouwanttocreateanewuseraccounteverytimewhenyoulogin,andthenreceiveorupdatetheuser’sextentinformation.
5.2.3Handlemessages
5.2.4Handleexception
5.2.5Workflow
1.Dataoperationalflow:
1.0CreateEHSSData
2.Changethedatastatusofdraftandproduction
2.0ExporttoMSDS/LabelPDF
1.Printdocuments
PrintMSDS
PrintLabel
6.Design&DevelopEnvironments
6.1OperationalEnvironments
6.1.1Development
SoftwareEnvironment(e.g.OSandotherrelatedsoftware,Language)
WebServer:
OperationsSystem:
WindowsXPSP2/Windows2003serverRC2
IISVersion:
6.0orhigher
Framework:
.Netframework2.0
Browser(compatibility):
IE&Firefox
DatabaseServer:
Database:
SQLServer2000standardeditionwithsp4
HardwareEnvironment(e.g.Routerandotherdevices)
PC(CPU>=2.8G,memory>=1G,harddisk=80G)
6.1.2QC
SoftwareEnvironment(e.g.OSandotherrelatedsoftware,Language)
WebServer:
OperationsSystem:
WindowsXPSP2/Windows2003serverRC2
IISVersion:
6.0orhigher
Framework:
.Netframework2.0
Browser(compatibility):
IE6/7&Firefox
DatabaseServer:
Database:
SQLServer2000standardeditionwithsp4
HardwareEnvironment(e.g.Routerandotherdevices)
PC(CPU>=2.8G,memory>=1G,harddisk=80G)
7.NonfunctionalRequirementDesign
7.1NamingConventions
ReferencetoEHSSCodingNamingRule.doc
7.2Performanceandspeed
ThefollowingisalistofareasthatwecaninvoketoharvestfortechniquesthatwecanusetodevelopahighperformanceASP.NETapplication:
●Usedatabasestoredprocedures
IfitiscomplexSQLstatementanddatabasetransaction,mustbeusethestorageprocess.
●Caching
Usingthecachingtechniqueappropriatelycanimprovetheperformanceofwebapplicationmorethanusinganyothertechnique.
CachingissoimportantandtheASP.NETframeworkgivesavarityofcachingmechanismsyoucanusetoimproveyourapplicationperformancemoreandmore.Someofthosemechanismsare:
Cachingapplicationdata,Pageoutputcasching,Cachingwebforms,andCachingpartsofwebforms.
●UseHTMLcontrolswheneverpossible
HTMLcontrolsislighterthanservercontrolsespeciallyifyouareusingservercontrolswithitsdefaultproperties.ServercontrolsgenerallyiseasiertousethanHTMLcontrols,andontheothersidetheyareslowerthanHTMLcontrols.So,itisrecommendedtouseHTMLcontrolswheneverpossibleandavoidusingunnecessaryservercontrols.
●Avoidroundtripstoserverwheneverpossible
Usingservercontrolswillextensivelyincreaseroundtripstotheserverviatheirpostbackeventswhichwastesalotoftime.Youtypicallyneedtoavoidtheseunnecessaryroundtripsorpostbackeventsaspossible.Forexample,validatinguserinputscanalways(oratleastinmostcases)takeplaceintheclientside.Thereisnoneedtosendtheseinputstotheservertochecktheirvalidity.Ingeneralyoushouldavoidcodethatcausesaroundtriptotheserver.
●Disabletheservercontrolviewstatewheneverpossible
Servercontrolbydefaultsavesallthevaluesofitspropertiesbetweenroundtrips,andthisincreasesbothpagesizeandprocessingtimewhichisofcourseanundesiredbehavior.Disabletheservercontrolviewstatewheneverpossible.Forexample,ifyoubinddatatoaservercontroleachtimethepageispostedback,thenitisusefultodisablethecontrol'sviewstateproperty.Thisreducespagesizeandprocessingtime.
●Paging
Ifyouwanttodisplayalargenumberofpagedata,nota