EHSS Preliminary Design.docx

1、EHSS Preliminary DesignDober GroupEnvironment Health Safety and Security (EHSS)Preliminary DesignPD Date: 04/18/2008Author: Project Manager: VersionDateDescriptionUpdated ByAffected Pages1.004/11/2008Draft for reviewAll pages1.105/05/2008Improve and increase some sections after reviewAll pages1.105/

2、21/2008Updated function modules image and added data modelPage 6,71.105/22/2008Improve some sections after review by GeorgeAll pagesSIGNATURESPrepared by:AuthorDate04/18/2008Approved by:Customer RepresentativeDateManagement/LeadDateStakeholderDateStakeholderDateStakeholderDateTABLE of CONTENTS1. Int

3、roduction 31.1 Document Purpose 31.2 Document Scope 31.3 Definitions, Acronyms, and Abbreviations 31.4 References 32. Running Environment 32.1 Software Environment 42.2 Hardware Environment 43. Architecture Design Criteria 44. Software Architecture Description 44.1 General Architecture 44.1.1 Overvi

4、ew 44.1.2 Basic Logical Architecture 55. System Function Design 55.1 General Model 55.1.1 Data Model 55.1.2 Function modules 75.1.3 Interface 75.2 Function Module Descriptions 85.2.1 Login module 85.2.2 User Role & Access Rights 85.2.3 Handle messages 105.2.4 Handle exception 115.2.5 Workflow 116. D

5、esign & Develop Environments 146.1 Operational Environments 146.1.1 Development 146.1.2 QC 147. Nonfunctional Requirement Design 157.1 Naming Conventions 157.2 Performance and speed 158. Technology 16Appendix A: Acronyms 161. Introduction 1.1 Document PurposeIn this phase we will do the preliminary

6、design of Dober EHSS system model based on the system requirements analysis. This is to outline the main solution to implement procedure module of the system requirements, including how to divide the system into several modules, decision of the modules Interface, information transmission, data struc

7、ture and design of the module structure, etc. In the next detail design stage, we will take the preliminary design as reference and work out a more specific detail design.1.2 Document ScopeThe design will cover the following main features. Manage EHSS Data Manage MSDS Manage Label Printing documents

8、 Security Interface1.3 Definitions, Acronyms, and AbbreviationsEHSSEnvironmental Health Safety SecurityMSDSMaterial Safety Data SheetJDEJD Edwards1.4 ReferencesNameURLDober Group Requirements_v1.7.doc Management/Dober Group Requirements_v1.7.docDober EHSS SRS.doc Management/Dober EHSS SRS.doc2. Runn

9、ing Environment2.1 Software EnvironmentOperating systemWindows server 2003 R2Web ServerIIS 6.0 or higherRuntime framework.Net framework 2.0DatabaseMS SQL Server 2000 standard edition with sp4BrowserIE or FirefoxOfficeMS Word, Adobe Reader professional2.2 Hardware EnvironmentDisk80Gb SATA drives x 2

10、RAID 1Memory2GB RAM3. Architecture Design Criteria Usability Performance Maintainability & Manageability Lower cost Reliability4. Software Architecture Description 4.1 General Architecture4.1.1 Overview Architecture：This system will be built as a web application by using 3-tier architecture with 2.0

11、 framework: A 3-tier architecture provides ability to scale as well separates business logic from the presentation (web browser pages).1. The Web user interface.It contains all things that are visible to the user. The UI layer has techniques like HTML, CSS, javascript, aspx2. Business Logic Layer Th

12、is is the core of the system. It contains all important rules and logic. This layer also invokes the Data layer for requests needed from the database or any third party interface to deliver to the Web User Interface.3. Data access and storage Layer.This layer takes care of persistence. An object fro

13、m the Data Access Layer can write itself to one or more tables. This main composition of this layer comprises of the database connection, SQL query strings and result sets. Framework:.NET Framework 2.0 Database:SQLServer 20004.1.2 Basic Logical ArchitectureSee below components diagram:Data transfer

14、between front-end and back-end5. System Function Design5.1 General Model5.1.1 Data ModelRefer to For more detail information, please see the link: 5.1.2 Function modules5.1.3 Interface JD Edwards will continue to house the products master which includes a unique product key that will be shared with

15、the EHSS application. All interface lookups will utilize this unique key.EHSS interface with Dober systems:5.2 Function Module Descriptions5.2.1 Login moduleUsing AD(Microsofts Active Directory) authentication model, data source from within Dober domain accounts5.2.2 User Role & Access RightsAD (Act

16、ive Directory) can store the username, password, and the group name. But it will not store the user access rights in the EHSS system.There are 3 roles in the system:AD Group Name/ Role NameRole IDAccess Rights DescriptionauthorFrom AD Group IDAuthor role has the system admin right. such as create/ed

17、it EHSS data, export to pdf etc.viewerFrom AD Group IDViewer role can only view the published MSDS and label.labFrom AD Group IDEmployee in lab plays this role, and they can view all EHSS information, but can not modify（than the viewer to see some more, but not the author）Note: Theres a limitation i

18、n configuring AD groups to access the EHSS system in AD, three roles need to be created and mapped to an ID in the AD distribute the limits for different distinctions as described in the table above. In addition a user information extend table needs to be created for mapping AD user accounts and sto

19、ring individual customize information, such as “I do not like caution message when printing”. For enhancing the performance, you can determine if you want to create a new user account every time when you login, and then receive or update the users extent information.5.2.3 Handle messages5.2.4 Handle

20、 exception5.2.5 Workflow1. Data operational flow:1.0 Create EHSS Data2. Change the data status of draft and production 2.0 Export to MSDS/Label PDF1. Print documentsPrint MSDSPrint Label6. Design & Develop Environments 6.1 Operational Environments6.1.1 DevelopmentSoftware Environment (e.g. OS and ot

21、her related software, Language)Web Server:Operations System: Windows XP SP2 / Windows 2003 server RC2IIS Version: 6.0 or higherFramework: .Net framework 2.0Browser(compatibility):IE & FirefoxDatabase Server:Database: SQL Server 2000 standard edition with sp4Hardware Environment (e.g. Router and othe

22、r devices)PC( CPU= 2.8G, memory = 1G,hard disk =80G)6.1.2 QCSoftware Environment (e.g. OS and other related software, Language)Web Server:Operations System: Windows XP SP2 / Windows 2003 server RC2IIS Version: 6.0 or higherFramework: .Net framework 2.0Browser(compatibility):IE 6/7 & FirefoxDatabase

23、Server:Database: SQL Server 2000 standard edition with sp4Hardware Environment (e.g. Router and other devices)PC( CPU= 2.8G, memory = 1G,hard disk =80G)7. Nonfunctional Requirement Design7.1 Naming ConventionsReference to EHSS Coding Naming Rule.doc7.2 Performance and speed The following is a list o

24、f areas that we can invoke to harvest for techniques that we can use to develop a high performance ASP.NET application: Use database stored proceduresIf it is complex SQL statement and database transaction, must be use the storage process. CachingUsing the caching technique appropriately can improve

25、 the performance of web application more than using any other technique.Caching is so important and the ASP.NET framework gives a varity of caching mechanisms you can use to improve your application performance more and more. Some of those mechanisms are: Caching application data, Page output caschi

26、ng, Caching web forms, and Caching parts of web forms. Use HTML controls whenever possibleHTML controls is lighter than server controls especially if you are using server controls with its default properties. Server controls generally is easier to use than HTML controls, and on the other side they a

27、re slower than HTML controls. So, it is recommended to use HTML controls whenever possible and avoid using unnecessary server controls. Avoid round trips to server whenever possibleUsing server controls will extensively increase round trips to the server via their post back events which wastes a lot

28、 of time. You typically need to avoid these unnecessary round trips or post back events as possible. For example, validating user inputs can always (or at least in most cases) take place in the client side. There is no need to send these inputs to the server to check their validity. In general you s

29、hould avoid code that causes a round trip to the server. Disable the server control view state whenever possibleServer control by default saves all the values of its properties between round trips, and this increases both page size and processing time which is of course an undesired behavior. Disabl

30、e the server control view state whenever possible. For example, if you bind data to a server control each time the page is posted back, then it is useful to disable the controls view state property. This reduces page size and processing time. PagingIf you want to display a large number of page data, not a