Skip to main content

Jefe



Jefe(The Spanish means for Boss) is the currently on going final year group project of our team.This is a research and development project which proceeds by combining the three distinct concepts; enterprise application integration architecture, business intelligence and software as a service.

Jefe is a Software Development Workflow Management System which unifies the enterprise information and intranet applications in the domain of the software development.As its name indicates Jefe (in Spanish means “Boss”) perform the role of a manager who monitors the workflow and supply the needed assistance to its users as all times.

The output of this project will fit to the real world Software Development Environment to resolve the existing issues regarding collaboration of each phases in software development process.

The framework of the Jefe is developed as a web based portal in which all the other applications can integrate to this framework as portlets and implement inter communication among those portlets in order to provide interactions among tools;which provides a single system to do all the tasks in the software engineering process.

In order to make Jefe is a complete solution all the necessary tools in the software development tools are integrated with the system.

Since Jefe is an integration of many isolated applications widely used in the domain of the Software Development, it improves the manageability, monitoring and the communication in the workflow of the software development process. So Jefe is helpful to the organisation to increase the productivity, effectiveness and collaboration while reducing the cost and development time at all the stages of the process.

For more details visit the web site of the project;
http://www.sdwms.webatu.com/jefe/

Comments

Post a Comment

Popular posts from this blog

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...
7 comments
Read more

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen;            a) Failures during message mediation process failure inside ESB [for example if you                use   dbreportmediator/lookup mediator inside mediation flow,some times failures can                happen due  to database connection failures]          b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss  ...
4 comments
Read more

TPP Journey through WSO2 Open Banking

Introduction 2018 is all set to be a game-changing year for European banking. The Revised Payment Services Directive (PSD2) has opened the door to new third party providers [TPPs] to connect with banks and manage finances of bank customers on behalf of them. The PSD2 regulation has mandated banks to expose their core-banking account data and payment services to authorized TPPs to consume. Thus as a bank it’s essential to have a solution which will securely expose their internal banking services to third party providers in a trusted manner. WSO2 Open Banking solution provides all required components to expose bank APIs in a well secured manner in order to become PSD2 compliant. This article explains about the importance of the TPP role in PSD2 domain, the requirements set that banks need to provide for TPPs by PSD2 regulations and how WSO2 Open Banking solution supports these requirements.  From my last blog ,I have given an introduction for PSD2 and WSO2 Open Banking soluti...
4 comments
Read more