branddocs Technology edocument Solutions V V

Transcription

1 branddocs Technology V V edocument Solutions

2 Contents 1.- Branddocs' Development Technology Development Technology Features Technical Architecture Description of Technical Architecture Web Architecture Web In-House Architecture Web Cloud Architecture Web Cloud+In-House Architecture 11

3 1.- Branddocs' Development Technology: Branddocs' solutions have been developed with the following technology: Framework.NET v4 (Visual Studio 2012). SQL Server 2008 R2 Database: Relational Model. FileStream used to store files. Critical data encrypted with SHA-256: passwords, document route, etc. C# programming language. ASP.NET for the presentation layer.

4 2.- Development Technology Features: The main features of their development technology are the following: The application is web-based and accessible through all the major browsers: Internet Explorer, Google Chrome, Firefox, Safari and Opera. It allows any type of web architecture scenario with its components stored in: 1. The Servers of the Client Company (In-House). 2. On the Cloud. 3. On the Cloud and the Client's Servers (Cloud + In- House). Architecture is reusable and easily integrated through its API. It has a multi-language interface (English and Spanish are already included).

5 3.- Technical Architecture: In terms of their technical architecture, Branddocs' solutions are logically divided into four layers, one of them the transversal and a tier. However they can be separated into more tiers based on the organization's needs or performance demands.

6 4.- Technical Architecture Description: 1. Cross-Cutting Transversal Layer: For the interaction between the layers. The data model is based on entities EF (Entity Framework: use of domain specific objects) to guarantee the abstraction from the DBMS. Own framework of exception is used. 2. Data Access Layer: The ORM Entity Framework 4 is used (map objectrelation to create a database oriented to virtual objects, over the relational database), using the LINQ for queries. A Repository Pattern implementation is used (a Façade that abstracts the layer of Business from the persistence) adapts to the necessities of the project. 3. Business Layer: Classic business layer to perform the operations and pertinent validations. Document encryption and data encryption.

7 4. Presentation Layer: HTML5 and independent CSS3 style sheets. Responsive Web Design. Conducted with ASP. NET Webforms with Master Pages, URL Routing (with personalized slugs for entity) and multi-language resource pages. Interface with AJAX functionalities. Use of JQuery for diverse functionality on the client side. Personalized security through Forms Authentication. Encrypted symmetric algorithms to send and receive messages from the user. Handlers for visualization of images and downloading of documents. 5. Services Layer (API): External access layer based on application functions, through protocols SOAP and JSON. Prepared for other platforms (ios, Android ). 6. Windows Services Layer: Windows services with programmed test in.net (connection Dropbox, subscription verification ).

8 4.1- Web Architecture: In terms of their Web Architecture, five fundamental elements are applied in Branddocs' solutions: 1. Internet Web Application: Branddocs application in any of its versions (Doccuban, Doccupol, Doccunet...) developed in.net. 2. Branddocs' SQL Database: the database of the records generated in Branddocs' solutions whose entity does not belong to the database of users of the Single Sign On (SSO). 3. Documents' Table: the table of the documents transferred between different users of Branddocs' solutions and the company. It contains the records related to these documents such as the route where they are found. It's within the SQL Database. 4. Documents: the documents of the users (normally in PDF). 5. Web Single Sign-On Data Base. Database of the users, property of the client company. Others: Intranet or Extranet of the company. End User, the user that connects to the application.

9 Web In-House Architecture: In the modality of the Web Architecture stored in the client company or In-House: The applications are installed in the servers of the company. Requirement: web applications server.net compatible. The Branddocs' solutions SQL Databases are also installed in the client company servers. Requirement: database server compatible with SQL Server. The documents will be stored in the servers of the company. Requirement: storage server. The end users will connect to the applications according to the company installation and its existing web page. Web Single Sign-on (Web SSO) and intranet/extranet connection. All the before mentioned can be different servers or not, depends on the company's facilities. The recommendation is for different servers for scalability and performance. Main advantage of the Web In-House Architecture: everything is housed in the company's machines. Disadvantage: the company has to be responsible for storage. In the Web In-House Architecture all of the components are installed in the servers of the company:

10 Web Cloud Architecture: In the modality of Web Architecture housed in the Cloud: The applications are on the cloud. If it is in Amazon it's with an EC2 platform. The database is on the cloud. If it is in Amazon it's with a RDS platform, or stored in the actual EC2 of the application. The documents are on the cloud. If it is in Amazon it's with the S3 platform, or stored in the actual EC2 of the application. The end users connect to the application via the cloud through the web browser. Web Single Sign-On (Web SSO) is available through an intranet/extranet connection. Main Advantage: The client company has everything housed on the cloud: velocity and scalability. Disadvantage: This architecture may go against the security policies and established systems. Diagram of the Web Architecture Housed in the Cloud:

11 Web Cloud+In-House Architecture: In the modality of mixed housing of Cloud and Company: Normally the Application will be on the cloud. Normally the database will be in the company servers. Normally de documents will be in the company servers, in the same server as the database (or not). If the application is on the cloud, the end users will connect through the browser. Otherwise, they connect to the application through company facilities such as the preexisting webpage. Web Single Sign-on (Web SSO) and connection with the intranet/extranet. Main Advantage: location flexibility for the various components. Disadvantage: performance and connectivity. It is the least efficient scenario. Diagram of the Web Architecture Housed in Cloud +In-House:

12 411 Lafayette Street. Suite New York, NY Tel: Parque Empresarial La Finca Paseo Club Deportivo 1, Edificio 15A, Planta Pozuelo de Alarcón, Madrid. Spain