Tài liệu CUSTOMER RELATION MANAGERMENT Software Architecture and Detailed Design docx

CUSTOMER RELATION MANAGERMENT S o f t w a r e A r c h i t e c t u r e a n d D e t a i l e d D e s i g n Project Code: CRM Document Code: CRM_ Architecture_and_Detailed_Design_v1.0 Hanoi, january 2007 Routepad_Architecture_and_Detailed_Design v1.0 S3I Confidential 2/54/ Routepad_Architecture_and_Detailed_Design v1.0 RECORD OF CHANGE *A - Added M - Modified D - Deleted Effective Date Changed Items A* M, D Change Description New Version 19-Apr-06 A Initial version 1.0 S3I Confidential 3/54/ Routepad_Architecture_and_Detailed_Design v1.0 SIGNATURE PAGE ORIGINATOR: Phan Xuan Truong 04-Jan-2007 Architecture and Solution Design REVIEWERS: Phan Xuan Truong 04-Jan-2007 Project Director Phan Xuan Truong 04-Jan-2007 Project Leader APPROVAL: Phan Xuan Truong 04-Jan-2007 Project Director S3I Confidential 4/54/ Routepad_Architecture_and_Detailed_Design v1.0 TABLE OF CONTENTS 1 INTRODUCTION 8 1.1 How this document is organized 8 1.2 Purpose 8 1.3 Definitions, Acronyms and Abbreviations .8 1.4 Referenced Documents .9 2 ARCHITECTURE DESIGN .9 2.1 CRM Overview 9 2.1.1 External/Internal interfaces 9 2.1.2 Constraints and assumptions 10 2.1.3 Transaction management .10 2.1.4 Connection pooling 11 2.1.5 The .NET Framework 11 2.2 CRM System Architecture 13 2.3 Module Hierarchy .17 2.3.1 CRM Modules .17 2.4 Logical View 17 2.4.1 UI Package 18 2.4.2 BO Package .19 2.4.3 DAO Package .19 2.4.4 Common Package 19 2.4.5 Controls Package .19 2.4.6 System Package 19 2.5 Deployment 19 2.5.1 CRM Side .19 2.5.2 Other Sides .19 2.6 Hardware and Software requirement .19 2.6.1 Handheld Device 19 2.6.2 Software .20 S3I Confidential 5/54/ Routepad_Architecture_and_Detailed_Design v1.0 3 DETAILED DESIGN 20 3.1 Detailed Design Methodology 20 3.2 Detailed Design Overview .20 3.3 Use Cases View .22 3.4 Packages 22 3.4.1 DAO Package .22 3.4.2 Business Object Package 24 3.4.3 UI Package 25 3.4.4 Common Package 26 3.4.5 Controls Package .27 3.4.6 System Package 27 3.5 Exception Handling and Logging .28 3.5.1 Exception Handling 28 3.5.2 Logger 29 3.6 Diagrams 30 3.6.1 Logon 30 3.6.2 Route Management .31 3.6.3 Download 33 3.6.4 Import Data 35 3.6.5 Totals 36 3.6.6 Setup 37 3.6.7 Beginning of Day .39 3.6.8 Loads 41 3.6.9 Sales .44 3.7 Database 47 3.7.1 Relationship Diagram .47 3.7.2 CommProfiles table 47 3.7.3 Routes table 47 3.7.4 AppSettings table 48 3.7.5 SecurityCodes table .49 S3I Confidential 6/54/ Routepad_Architecture_and_Detailed_Design v1.0 3.7.6 Loads table 50 3.7.7 LoadDetails table .50 3.7.8 LiquorLicenses table 51 3.7.9 Messages table 51 3.7.10 Customers table .51 3.7.11 Surveys table .52 3.7.12 LookUp table .52 3.7.13 Vending table 52 3.7.14 DailyInfo table .52 3.7.15 Products table 53 3.7.16 Expenses table 53 3.7.17 RouteStop table .53 3.7.18 Orders table 53 S3I Confidential 7/54/ Routepad_Architecture_and_Detailed_Design v1.0 1 INTRODUCTION 1.1 How this document is organized Here are brief summaries for the parts of this document: Part 1: Introduction to the document, purpose, definitions and references Part 2: Architecture Design Part 3: Detailed Design 1.2 Purpose Architecture Design: Purpose of this document is to provide an architectural overview of CRM system. Through this document, project team and IT Department can have an overview and understand the whole system. They can know how CRM system will be developed and which systems CRM will have to integrate with. This document also describes all constraints that the design of the system must follow to meet the business and maintenance requirements. Detailed Design This document aims at to describe the details of Classes of CRM application. By studying this document, project team, developers and related groups can have an overview of the internal of CRM application and they can have more information to implement CRM application. 1.3 Definitions, Acronyms and Abbreviations Abbreviation Description GUI Graphical User Interface HTTP Hypertext Transfer Protocol PDA Personal Digital Assistance CRM Customer Relation Management S3I Confidential 8/54/ Routepad_Architecture_and_Detailed_Design v1.0 SRS Software Requirement Specification XML Extensible Markup Language CF Compact Framework GUID Global Unique Identifier FTP File Transfer Protocol 1.4 Referenced Documents MSDN.NET MSDN for Visual Studio .NET CRM-SRS-v1.0.doc Functional Specification of CRM application 2 ARCHITECTURE DESIGN 2.1 CRM Overview 2.1.1 External/Internal interfaces Figure 1. External/Internal interfaces of ROUTEPAD-PDA system S3I Confidential 9/54/ Routepad_Architecture_and_Detailed_Design v1.0 Component Interface type Connection type PDA <---> FTP Server Data will be download and upload via FTP Network FTP PDA ---> Printer Data will be print out on paper. Infra, Bluetooth, Serial port 2.1.2 Constraints and assumptions There are some key requirements and system constraints that have a significant bearing on the architecture. They are: 1. The server-side system: server will be enabled FTP Server. 2. CRM machine: Window Server 2003,XP OS and MS .NET Framework 1.1. 3. Database of CRM is SQL Server 2000 Service Pack 3 4. Local CRM will be authenticated against the locally stored security code. The locally security code must be securely stored and should be accessible to users and must not store in clear text. 5. Sensitive data held on the CRM must be held in such a manner to ensure that the data is not accessible before a CRM has been successfully authenticated. 6. If we need to scale beyond the target number of CRMs it should be capable of being scaled by the introduction of further CRM proxy processes and possibly further proxy machines without requiring code changes to any component. 7. The code dealing with the interaction with user input / output to-and-from the CRM should be abstracted to allow for the future upgrade to later version of the CRM operating system and replacement of the CRM hardware. 2.1.3 Transaction management The ROUTEPAD-PDA is developed using .NET Framework, so we will use manual transaction provided by ADO.NET. There isn’t complex calculation in Pocket Routepad system so that we don’t use COM+ as business layer. ADO.NET provides a powerful manual transaction management mechanism. You have to write some code to control the how the transaction should perform. That means with ADO.NET you have a flexible way to manage transaction processing. Transaction object can be passed (by reference) between method calls to build up a complex process in one transaction. However, it’s rather complicated to setup a model that is easy for maintenance. Distributed transaction is also S3I Confidential 10/54/ [...]... 2.6.1 Handheld Device Configuration S3I Confidential Recommended 19/54/ Routepad _Architecture_ and_ Detailed_ Design CPU RAM 128 MB and ROM 64 MB OS 2.6.2 Intel Pentium IV Memory v1.0 Windows Server 2003,WinXP… Software Name Purpose NET Framework v1.1 Development Framework SQL Used for storing data on local CRM Server 2000 Service Pack 3 3 DETAILED DESIGN 3.1 Detailed Design Methodology In this detailed design. .. on the physical and logical design constraints of the application S3I Confidential 14/54/ Routepad _Architecture_ and_ Detailed_ Design Figure 3 S3I Confidential v1.0 CRM MVC model 15/54/ Routepad _Architecture_ and_ Detailed_ Design Figure 4 v1.0 CRM System Logical Architeture The CRM System was built exactly to resolve problem dispersion of Business unit,However database Store require common managerment. For... on the left, right and center position Can display image Can display a 3D border around the panel Can display a currency symbol at the beginning of the text System Package Refer to Error Handling and Logging S3I Confidential 27/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.5 Exception Handling and Logging 3.5.1 Exception Handling 3.5.1.1 Data Access Layer Figure 14 Exception handling flow for... Routepad _Architecture_ and_ Detailed_ Design v1.0 development will be able to develop new mobile applications much more efficiently, which in turn can help lower their costs of doing business, and increase their market opportunities 2.2 CRM System Architecture The architecture of CRM system will be designed to illustrate: - Transaction Data exchange between Insight host system and CRM machine - Architecture. .. combine of Application components : S3I Confidential 16/54/ Routepad _Architecture_ and_ Detailed_ Design Figure 5  v1.0 CRM Components Model CRM clients Application(Windows forms) : supply Customer Relation Managerment and Business managerment tools,WareHouse for Enterprise  CRM Admin Application(ASP.NET Forms):supply Administrator tools and synthetize data business Process of Enterprise  CRM XML Web Service... S3I Confidential 31/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.6.2.2 Activity Diagram Figure 20 Route Management Activity Diagram S3I Confidential 32/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.6.2.3 Class Diagram Figure 21 Route Management Class Diagram 3.6.3 Download 3.6.3.1 Functional Overview This function downloads text files from FTP server to handheld device Then it calls Import... handheld device Then it calls Import Data function to import data in those files to database S3I Confidential 33/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.6.3.2 Activity Diagram Figure 22 Download Data Activity Diagram S3I Confidential 34/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.6.3.3 Class Diagram Figure 23 Download Data Class Diagram 3.6.4 Import Data 3.6.4.1 Functional Overview This... implemented in the application: - My Informations - My Customers - My Quote - My Order - My Tasks - My Products - My WareHouse - My Sales - My Inventory 2.4 Logical View This session provide an overview of the logical packages of ROUTEPAD-PDA system Details are S3I Confidential 17/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 described in Detailed Design session Figure 6 2.4.1 CRM Logical Package UI... Logic Layer Figure 15 Exception handling flow for BO objects S3I Confidential 28/54/ Routepad _Architecture_ and_ Detailed_ Design v1.0 3.5.1.3 Presentation Layer Figure 16 Exception handling flow for UI objects 3.5.2 Logger 3.5.2.1 Class Diagram Figure 17 Logger Diagram In the ROUTEPAD-PDA system, a third party component called Log4NET is used to trace business flows and log errors into a text file All... methodology to illustrate the structure of ROUTEPAD-PDA application Diagrams in this document are created in Visual Studio.NET 2005, Microsoft Visio 2003, and Rational Rose 3.2 Detailed Design Overview S3I Confidential 20/54/ Routepad _Architecture_ and_ Detailed_ Design Insight Server Server Side FTP v1.0 Network FTP FTP Client Side PDA Presentation Layer UI Components Business Layer Business Workflows Data Access . Architecture_ and_ Detailed_ Design_ v1.0 Hanoi, january 2007 Routepad _Architecture_ and_ Detailed_ Design v1.0 S3I Confidential 2/54/ Routepad _Architecture_ and_ Detailed_ Design. Routepad _Architecture_ and_ Detailed_ Design v1.0 Figure 5. CRM Components Model  CRM clients Application(Windows forms) : supply Customer Relation Managerment and