JBPM Workflow project

Expense management system: Web based Workflow application (JBPM) running in a Linux virtual machine. The application should let the user to load Expenses in a browser, and a workflow is initiated. After approval, a web service must be called to generate the expense in another system (not included in this propposal). ## Deliverables The aim is to develop a WEB based application for uploading and approval of travel expenses, and then its automatic allocation in an ERP (not included in this proposal). SCOPE * Income Travel expense * Approval through Workflow * Generation of accounting records * Spending report WEB environment Modules: Workflow: the process required for approval of the Travel expense of the employee within the company. Reports: expenditure broken down by sector, employee, project, reason Input interface: the goal is to communicate with an ERP and get the results of the loaded documents, updates, documents and master data. Output Interface: The goal is to send the data collected on forms and in the workflow to the ERP for further processing (see Input Interface Module in ERP). FUNCTIONAL CHARACTERISTICS - Employee loads per diem expenses in the web form. The sysyem determines who?s the approver. - Automatic notification is sent by mail to the approver for approval and to determine the accounting entry (master data obtained in input interface). - The approver approves and determines GL account and cost center (GL Account and Cost Center ? master data obtained in input interface). - If necessary, approval of the second approver (matrix is derived from the amount and cost center - To be defined). - Once approved, information is sent to control input data and determine taxes. (WHO? WORKFLOW? - To be defined) - Using web service communicates with the ERP and information is sent. to load the invoices in the ERP.(developmente of web services in the ERP is not included in this proposal) - Mail is sent to the employee notifying him that the allowance was loaded and reminding him to send the paper invoice to HR. - Once the paper invoice is received, Accounts Payable gives the OK and sends information to the web. - A new process is generated in the ERP, which will unlock the bills. Information is sent to the workflow. TECHNICAL SPECIFICATIONS - Web development: Linux environment (RedHat) as a webserver running in a virtualized environment. - Workflow: JBPM (latest version available). - Information sent to the Workflow system (master data: qualified employees, approvers, accounts, cost centers, tax codes, approval matrix). This information should be loaded in an automatic and manual way. Ir must editable. - Programming Languages: For the workflow engine will be used [login to view URL] reflect the business process can start with graphical environment, but surely you must add code to achieve the desired objective. JBPM The language is [login to view URL] (Process definition language) for the graphical interface - Development Environment: Web Environment (avoids the need for installing software locally) Three different development environments must be created (Development, QA, Production). Database: MySQL Platform: Linux RedHat (latest version available). Methodology: OpenUP methodology based on Rational Unified Process. This methodology is iterative and incremental, is driven by use cases and put an early focus on the architecture of the system to minimize risk and deliver value to users through the frequent delivery of value through the release of versions. Persistence Framework: While the selection of frameworks used in the product development is deferred to the analysis and design stages of the first iterations of the project, the choice of Java technology enables the use of frameworks such as Hibernate, long history in the market, or JPA, which is the standard in the Java Community Process. Application Server: In the same sense as stated above with regard to selection of a persistence framework before the corresponding stage according to the methodology adopted, the choice will be server-oriented Java technology applications that allow the execution of the BPM Engine selected as well as the development frameworks needed to implement the activities defined in the specification of processes (workflows) mentioned in the scope. Tasks - Installing Linux environment (Redhat) - Install JBOSS - Installing JBPM - Configuration Engine - Other settings (email, permissions, etc.) - Development per diem charge (WEB) - Configuration of Workflow (WEB) - Development of reports (WEB) - Development Gateway Interface (ERP / WEB) - Report Development (WEB) - Development of output interface (WEB / ERP) - Technical Documentation Workflow - Functional Workflow Documentation - Instruction Manual - Documentation Development Reports - Documentation development input Interfces - Documentation development Interfces output