Download miễn phí Đề tài Customer relation managerment software architecture and detailed design
TABLE OF CONTENTS
1 INTRODUCTION 7
1.1 How this document is organized 7
1.2 Purpose 7
1.3 Definitions, Acronyms and Abbreviations 7
1.4 Referenced Documents 8
2 ARCHITECTURE DESIGN 9
2.1 CRM Overview 9
2.1.1 External/Internal interfaces 9
2.1.2 Constraints and assumptions 9
2.1.3 Transaction management 10
2.1.4 Connection pooling 10
2.1.5 The .NET Framework 11
2.2 CRM System Architecture 12
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 18
2.4.3 DAO Package 18
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
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 28
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
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 54
Để tải bản Đầy Đủ của tài liệu, xin Trả lời bài viết này, Mods sẽ gửi Link download cho bạn sớm nhất qua hòm tin nhắn.
Ai cần download tài liệu gì mà không tìm thấy ở đây, thì đăng yêu cầu down tại đây nhé:
Nhận download tài liệu miễn phí
Tóm tắt nội dung tài liệu:
Framework does not take the lowest-common denominator approach used by other device programming platforms. Developers can get broad portability and reusability by writing to the common programming model, but the .NET Framework is also designed to be extended with class libraries that expose features unique to a family of devices, or even unique to a particular device model. This approach allows developers to create the best possible application experience on each specific device, while reusing skills and code.Enterprise-Class Features for More Capable Devices
The success of Microsoft Pocket PC devices is growing, in part, because they have the computing resources necessary to handle sophisticated business applications. The .NET Compact Framework takes advantage of the Pocket PC platform by providing enhanced frameworks that greatly simplify the process of developing enterprise applications on Pocket PC devices.
Robust Code, Secure Execution
The .NET Compact Framework offers a robust and secure environment for running client-side code. The managed code model supported by the .NET Compact Framework increases the reliability of code, thus reducing software defects. The managed code execution engine ensures that an ill-behaved application will not be able to "crash" the device. At the same time, the evidence-based security model built into the .NET Compact Framework ensures that malicious code will not be allowed to gain access to secure system resources. The security model also enables software updates to be delivered over the wireless network in a secure way, decreasing the possibility of a costly device recall.
Great Offline Application Support
With secure client-side code, the .NET Compact Framework enables responsive applications that can be used offline. This allows a smooth execution despite any intermittent connectivity problems that might occur when accessing the network. The developer can choose the right mix of client-side and server-side programming to deliver a rich and always interactive application.
Reduced Cost of Development Creates New Opportunities
This new ease of development provided by the .NET Compact Framework will lead to the creation of a broad new range of applications and services that will Giúp manufacturers windows greater market acceptance for their mobile devices and create new opportunities for developers. Many businesses that were unable to afford the cost or special developer training necessary for mobile development will be able to develop new mobile applications much more efficiently, which in turn can Giúp lower their costs of doing business, and increase their market opportunities.
CRM System Architecture
The architecture of CRM system will be designed to illustrate:
Transaction Data exchange between Insight host system and CRM machine
Architecture in CRM machine
From above information and flow constraints:
CRM client program is built upon .NET Framework 1.1
The communication via network FTP
Transaction management mechanism is ADO.NET
We provide the architecture of CRM system as follow:
CRM system architecture
Presentation layer:
Purpose of this layer is for user-interaction. In CRM system, Windows-based GUI application will be used for most business processes. Built upon System.Windows.Form package from .NET Framework, the interface is used for inputting complex data and displaying complex views. This layer will be containing some business actions that manual data in local database.
Business layer:
The Business layer manages all internal business logic. It will receive data\request from Presentation, process necessary business logic, access or update data from\to local DB on CRM Application.
Data layer:
This layer includes storage database, data access components and data conversion sub system
Data access component: ADO.NET (CRUD Methods – Create – Read – Update – Delete and orther methods) – Data access logic components retrieve data from database and save entity data back to the database.Data Access Logic Components also contain any business logic needed to achieve data – related operations.
Business Entities components: Data is used to represent real world business entities, such as products or order.there are numerous ways to represent these business entities in your application – for example , XML or DataSets or custom object – oriented classes – depending on the physical and logical design constraints of the application.
CRM MVC model
CRM System Logical Architeture
The CRM System was built exactly to resolve problem dispersion of Business unit,However database Store require common managerment.For this reason,we have been combined CRM Architeture Application and XML Web Service base on .NET Framework follow Multi tier Architeture and MVC model is sensible.
This Model is principle for CRM System.follow this Model:
Application will resolve business functions,user methods with unique presentation,application cover work under structure with user.
XML Web Service,supply Serviceses message- based that be called by Application through Business Layers tier of Application
CRM System has been built combine of Application components :
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 :supply Services about synchronous data,manipulate so far with data center
Module Hierarchy
CRM Modules
Below is the list of functions to be implemented in the application:
My Informations
My Customers
My Quote
My Order
My Tasks
My Products
My WareHouse
My Sales
My Inventory
Logical View
This session provide an overview of the logical packages of ROUTEPAD-PDA system. Details are described in Detailed Design session.
CRM Logical Package
UI Package
This package contains all business object classes which encapsulate business logic of the application. They will receive requests from Presentation layer, process business logic and call DAO layer to update/retrieve data to/from CRM Database.
BO Package
This package contains all business object classes which encapsulate business logic of the application. They will receive requests from Presentation layer, process business logic and call DAO layer to update/retrieve data to/from CRM Database.
DAO Package
This package contains classes which will be used for manipulating data on CMR Server.
Common Package
This package contains entity objects which are used for transferring data between internal modules in CRM program.
Controls Package
This package contains custom controls which are used for specific display purpose. These controls are consumed by UI components.
System Package
This package contains objects used for logging purpose and objects to download/upload files.
We will use Log4Net to log necessary information for later tracking. This library is open source, run very fast and reliable.
Deployment
CRM Side
Packages to be deployed on handheld device:
Package
Note
PC CRM Application
CRM application running on PC
CRM Database
SQL Server 2000 Service Pack 3
Other Sides
N/A
Hardware and Software requirement
Handheld Device
Configuration
Recommended
CPU
Intel Pentium IV
Memory
RAM 128 MB and ROM 64 MB
OS
Windows Server 2003,WinXP…
Software
Name
Purpose
.NET Framework v1.1
Development Framework
SQL Server 2000 Service Pack 3
Used for storing data on local CRM
Detailed Design
Detailed Design Methodology
In this detailed design document, UML is used as main 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.
Detailed Design Overview
ROUTEPAD-PDA Architecture Overview
As described in Figure 4, PDA application will have three layers- Presentation Layer, Business Layer, Data Access Layer and Value Objects Common package.
Presentation Layer contains User Graphical Components, UI Process Components (Form Package).
User Graphical Components and UI Process Components build screens to interact with users. They show the information to the user or capture data or actions from the user to call business layer in order to update into database.
Business Layers contains all Business Object classes that will encapsulate business logic of the application. They will receive requests from Presentation layer, process business logic and call DAO layer to update/retrieve data to/from PDA Database.
Data Access layer contains classes which will be used for manipulating data on PDA machine and synchronize data between insight host and PDA Database
Value Objects classes are used to contain data for transferring between inte...