Please read
Upcoming SlideShare
Loading in...5
×
 

Please read

on

  • 568 views

 

Statistics

Views

Total Views
568
Views on SlideShare
568
Embed Views
0

Actions

Likes
0
Downloads
14
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Please read Please read Presentation Transcript

    • Architecture 2005-09-03 Frank Bergmann <frank.bergmann@project-open.com>
    • Content
      • The Big Picture
      • GUI Structure
      • Component Architecture
        • Component Use Overview
        • Component Conventions
      • Localization
      • Permission Model
      • Customization Concept
        • Application Lifecycle
        • Customization Options (1)
        • Customization Options (2)
    • Basics & Roadmap
      • ] project-open [ is a web-based “Project-ERP”.
      • It combines project collaboration (content & community ) with financial and management functionality (costs, invoicing, accounting, …)
      • ] project-open [ is based on the OpenACS (Open ArsDigita Community System) platform.
      • Most ] project-open [ modules are free or GPLed, except for specific customer functionality
      Platfrom Roadmap: V1.0 and V2.0 depended on Oracle, but V3.0 features PostgreSQL as a free database. 8i, 9i, Postgres 8i Oracle 8i (8.1.7) Data base OpenACS 5.1 OpenACS 5.0 ACS 3.4.9 Open-ACS V 3.0 V 2.0 V 1.0 P/O 10/2004 3/2004 11/2003 Date
    • Base GUI Structure
      • Main Pages with Business Objects
      • “ ListPages” with filters
      • New/Edit Pages
      Projects Home News Tickets Clients Project Calendar Details Project Team Tickets Costs File Space Tasks Details Client Interact Tickets Projects Customer Interaction History Team Costs Invoice Client Details Corp. Details Billable Tasks Ticket Details Assign to others Ticket History User Details Profiles Tickets Projects Clients Portrait Interactions Filters Project List Links Filters Client List Links Filters Invoice List Links Filters User List Links Filters Ticket List Links Details Details Details Details Details Admin-Pages
    • P/O Core Data Model country Office Object BizObject Group BizObject Object Infrastructure Business Objects Organization Customer physical location User BizObject UserContact parent_project customer Project office Customer project url ProjectUrlMap Category View UrlType view ViewColumn Profile Currency Country ComponentPlugin Menu object_one object_two Rel (OACS) BizObject Superclass of all biz objects. Manages permissions using acs_rel with users. object_type object_status
    • Component Architecture Home Project Client Invoice Ticket User Project Components -Project List
      • -ViewPage
      • ListPage
      • New/Edit
      -View: Project List (short) -New: Project List -List: Filter -View: Renderer -Print: Renderer -Project List -Project Select -Project Render -Client List -List: Renderer -List: Filter -Project List -Project/Task List -Project Filter -Project List -Project Select -Render Comp Client Components User Components Invoice Components - View: Invoice List
      • View Page
      • List Page
      • New/Edit
      Ticket Components
      • View Page
      • List Page
      • New/Edit
      • View Page
      • List Page
      • New/Edit
      Permissions -View: Perm+Estim -View: Key Accounts (perm) -View: Customer employees (perm) - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . - . . . Component Use Overview
    • Component Architecture
      • (GUI-) Components are used to render lists of objects, to render individual objects (in various variations) and to “filter” objects (restrict the elements of a SQL “where” clause).
      • These components have to deal with all important functions such as permissions, localization and design templates.
      • HTML pages are used to validate input variables, generate the page layout, and to “wire” the GUI-components together (glue-code).
      Component Conventions
    • ] po [ Overview SoftwareDevelopment Templates Trans-lation CRM Finance Controlling HR System Collaboration,Content & KM OOFrame Security Calendar OpenACSPermission Web Server Database FinanceBase Payroll Skill Database Filestorage OnlineDiscussions IncidentWorkflow BasicAuthentication LDAPAuthentication WorkflowEngine Chat PackageManager AutomaticSoftwareUpdates PostgreSQL Oracle 8i , 9i , 10g PageContracts SQLTemplates OO Model ObjectMetadata Localization Framework ContactMgmt. ReportingEngine Wiki Oracle Intermedia/Text TSearch2 Linux Solaris BSD Windows + CygWin Mac OS Operating System Search Engine AOLServer Pound Revers Proxy DynField Object Extensions Platform Services Profiling & Performance DebuggingSystem Application Modules FormBuilder Portal &Components Mail ServerIntegration ContentManagement Application Services DB-API TCL Quotes &Invoice Payments FinancialReporting Mail ServerIntegration CustomerWeb Reg. MarketingCampaigns CRMTracking AutomaticAudits ISDN TelIntegration ProjectMgmt. Project &Subprojects ProjectControlling TranslationWorkflow TMIntegration FreelanceInvoicing TimesheetInvoicing Available Documentation TimesheetMgmt. AutomaticInvoicing FinanceGuide Unix InstallGuide OpenACSInst. Guide Operations& Maint.Guide OpenACSDeveloperGuide ConfigurationGuide FilestorageGuide ForumGuide TranslationWorkflowGuide Full-TextSearch Automatic Testing BigBrother Sys Mgmt. Other Room Reservation E- Commerce CMS WebDAV SOAP & XML-RPC Surveys Glossary Web-Mail Blog Recruiting Workflow CVS Postfix / Sendmail Database Replication Mondrian Data- Warehouse
    • Localization
      • All numbers, currency amounts, dates, times and physical locations are rendered as a function of the chosen user locale
      • All currency amounts are preceded by a currency identifier. A system currency determines the default.
      • All static text used in pages and components is translated before rendering the HTML page. An English text in the target location is used as a default value in case of incomplete translations. The translation interface also specifies the target location to provide a context for translators.
      • Dynamic text (names and descriptions ob business objects) are not translated.
      • Future versions of ] project-open [ may contain accounting modules specific for individual countries.
    • Permission Model
      • Permissions are divided into profile-based permissions and role-based permissions
      • Profile-based permissions
        • Restrict the visibility of pages and modules to a user
        • Are modified as part of system administration
        • API: im_permission(user_id, token) : Validates that a user has access rights to the permission token.
      • Role-based permissions
        • Restrict the access to business objects (currently “Project” and “Client”)
        • Permissions can be modified by the creators of the respective objects, to configure project/client team.
        • API: im_has_role(user_id, object_id, role) : Validates that a user has been assigned the specifc role.
        • Roles are ordered hierarchically (administrator -> member -> specific_roles).
    • Profile Based Permissions
      • Predefined Profiles:
        • Manager
        • Project Manager
        • Employee
        • Finance
        • Client
        • Freelance
      • Access permissions to all critical data can be assigned to profiles
      • Additional profiles can be defined if necessary
      Project A Project B Project C Our Company (Project Matrix) Client Provider Managers Freelancers Project Managers Clients Finance Employees „ Vertical“ Permissions General Manager Project Man. Project Man. Sales Manager Operations Manager Project Director Project Man. General Manager Proj. Man. Manager Client Staff Free lance Free lance Free lance Finance
    • Project Based Permissions
      • Within a specific project, freelancers and clients may have the same rights as in-house staff. Freelancers may even have to act as project managers.
      • Predefined roles :
        • Sales/Presales
        • Project Manager
        • Analyst, Developer, Tester, ... (IT-Consulting)
        • Editor, Translator, Proof Reader, ... (Translation)
        • Texter, Designer, ... (Advertizing)
      Project A Project B Project C Our Company (Project Matrix) Client Provider Editor Editors Translators Translators Project Manager General Manager Project Man. Project Man. Sales Manager Operations Manager Finance Project Director Project Man. General Manager Proj. Man. Manager Client Staff Free lance Free lance Free lance
    • Application Lifecycle
      • ERP applications are not a static systems, but need to evolve continually with changes in the business processes of the client (customizations)
      • ERP applications need to integrate/communicate with other corporate applications
      • ERP applications have life-cycles of 5-20 years
      • The challenge is to maintain customizations when upgrading to the next release.
      Capture Require- ments Install Configu- ration Data Import Customi- zation Initial Implementation Capture Require- ments Install Data Conver- sion Upgrade Customi- zation Installation Retirement Upgrade Opera- tions Opera- tions
    • Extensible Architecture
      • A central core allows for extensions with different application modules
      • Different industry sectors need different configurations and modules
      • Customizations should be portable to the next version as easily as possible.
      … CRM Call Center Sales force Mgmt Project Mgmt Support Mgmt HR Project Reporting KM Projects Users Clients Invoices Expenses Account- ing Inventory Mgmt Recruit ing Perf.- Reviews Report- Generator … … … … … … … … IT/Consulting Engineering Translation Advertizing K- Profiles K- Mart Report- ing
    • Extensible Architecture
      • Not all modules are useful for all sectors
      • Some modules are different for every sector (for example invoicing)
      • Some of these modules may exist in several variants specific for each sector.
      • The Module architecture has to deal with the interdependencies between each other and over time.
      * =applicable, (*) =maybe applicable, + =customized modules
    • Customizable Items
      • GUI
        • Home-Page (module-specific status boxes)
        • The main menu
        • Submenus of business objects
        • Views of biz objects (Project, Client, User, …)
      • Categories (=workflow states and types)
        • Object status categories
        • Object type categories
      • Data Model
        • Add columns to existing BizObj tables (system modules)
        • BizObj extension tables (sectorial configuration modules)
      • TCL Libraries
      • Permission Model
        • Add new permission tokens
        • New system roles
        • New Object/Group specific roles
        • How can additional module change the “core”?
    • Customization (1)
      • Configurable Customization (100% preservation) The system has been designed for the particular customizations. The customization involves changes in the configuration file and/or database contents.
      • Future version of ] project-open [ maintain compatibility with these configurable options, possibly extending them.
      • Business Object Extensions (90% preservation) Business Object database tables can be extended to hold additional fields via the &quot;DynField&quot; SQL Metadata system. These extensions are not replaced during a system upgrade. Rendering of the fields is handled automatically by components in a new library.
      • Future version of ] project-open [ must not overwrite the extension tables. The client will have to integrate the modified components into the new View/List/Edit pages.
    • Customization (2)
      • New Custom Modules (80% preservation) The user may add new modules to the system, including their own data model and components.
      • Future version of ] project-open [ will not take into account the compatibility with custom modules. However, it is likely that the integration of the new modules with the new version will be easy to manage.
      • Custom Extensions (50% preservation) In some cases the client wants to modify the core business objects or component libraries.
      • Future version of ] project-open [ will not take into account the compatibility with custom extensions. That means that the client will have to port the extensions to the new version.
    • Participate!
      • Build _useful_ software
      • We teach you how to build real software
        • Learn about high-performance server applications
        • See why Java doesn’t work for _real_ software
        • Learn basics of SQL and Database Management
        • We have prepared some exercises that guide you through the process
        • Learn how to keep a web application running
      • Choose a module to concentrate
      • Study some background material and become an expert
      • Design a user-friendly GUIs and a solid data model
      • Being a leading developer with your module, clients will ask for your experience