Hello, nice to meet you!

Francisco Jr

Front-end Developer Back-end Developer Mobile Developer Infrastructure Analysist Portugal is my passion Photography is another passion Cooking too!

About me

Hello

I'mFrancisco Jr

Full stack developer and more

I have been working with computers since I was 16 years old. I started doing support for my friends, soon making it my profession. I attended my second degree in electronics, then I graduated in computer networking and finally postgraduate in analysis, project and systems management.
I have worked in several companies over the last 20 years, such as Atos Origin, Accenture, BRQ and Stefanini, with Petrobras as customer, where I spent 15 years working in the Exploration and Production (E&P) area.
I worked in one of the company's main systems, Siplex, where I worked in more than 22 systems and countless tasks, from infrastructure, back-end development, front-end development and project coordination.

English Curriculum Vitae:

Normal Europass

Portuguese Curriculum Vitae:

Normal Europass More about me

experience

Front-End Web Development

2003-2016

I worked with Bootstrap and jQuery UI, using grid systems, responsive design, media queries, HTML 5 and CSS 3. Knowledge of Javascript, ES6 and Typescript, in addition to working and prospect components like Highcharts and Google Maps.

UI/UX Design

2003-2016

Creation of sketches and prototypes in paper and HTML to determine, according to the requirements survey or use case, the best interface for the user, focusing on usability and reduction of clicks. Using Photoshop to create and edit images.

Back-End Development

2003-2016

Knowledge of several programming languages, such as C #, Python, Java and SQL, as well as Oracle database and SQL Server. Use of ORM tools and frameworks such as nHibernate and Entity Framework.

Infrastructure

2003-2016

Advanced knowledge of Windows and IIS servers, as well as Team System as code repository. Automation knowledge with VBS and PowerShell scripting as well as development of Windows service applications.

Mobile Apps

2015-2016

Development of WAP, UWP and Android applications, as well as adaptation of web sites for responsiveness in mobile devices.

Other Things

2003-2016

Knowledge of Scrum, Kanban and ITIL. I participated in external and internal audits and generated documentation for the system, training and infrastructure.

40000

LINES OF CODE

18

PROGRAMMING LANGUAGES

21

YEARS PROGRAMMING

34

PROJECTS

4

AWARDS AND ACKNOWLEDGMENTS

15

COMPANIES I SERVED

Portfolio

Showing posts with label Scrum. Show all posts
Showing posts with label Scrum. Show all posts

2011 - Siplex ForUs


ForUs was born from the idea of ​​facilitating the development of new prototypes and applications, creating a unique and consistent interface with several custom plugins, avoiding the need for the developer to adapt new components or change the design of the application. He was inspired by the article "How to Enhance Forms Using jQuery UI".

It is a non-obstructive framework, which uses three grid systems (12, 16 and 24 columns), using Css and HTML features along with jQuery and jQuery UI to create themes that are common and reusable for various ForUs applications. These applications also perform similarly across browsers, as well as adorning the good usability and interface practices used by Petrobras' team of designers.

Below is a diagram of the proposed architecture:

ForUs architeture

.Net layer:
Triggers calls from the Asp.Net WebForms and Asp.Net MVC server code to the Popup and Message components. In addition, there was a feature called Time Machine, which sent from the client to the server an HTML with formatting and data populated by the user, notifying some problem to the development team.

User Interface layer:
Where were the various ForUs components that interact with the user. They are configured through a basic setup and triggered according to the developer's need. For example, you can call the message component by writing two lines of code.

Data Format layer:
They are the general configuration points of ForUs, defining the basic grid system setup, font size, field validators, application theme and more.

jQuery UI ForUs Theme

Infrastructure layer:
It contains the ForUs Log system, which shows in the browser console the problems that occur and the ForUs APIs, which are called support methods, such as writing and reading a browser cookie or retrieving a parameter from the query string.

ForUs error page and log system

The project has been adopted by several modules of Siplex (Prodex, Drilling Rigs Schedule, etc.) and continues in use until today, but no more evolutions, only corrective maintenance due to the adoption of Bootstrap and increase the team's maturity in jQuery coding and JavaScript, facilitating the adoption of components available on the Internet.

For legal reasons, interfaces can not be readable.

Project start year: 2011
Duration: 2 years (Interleaved)
Position: Consultant, Sr Consultant
Role: Developer, System Analyst, Designer, Front-end, Back-end
Working for: Accenture, BRQ
Client: Petrobras
Technologies: C# .Net, Asp.Net, Asp.net MVC, Css3, HTML5, Xml, Web Services, TFS, Nuget, jQuery, jQuery UI, Json, JavaScript, Scrum, Kanban

2010 - Siplex Propex


Propex was requested by Exploration's need to control the flow of information related to Blocks, controlling from its possible acquisition to the return or passage to production.

Between the four main stages (Acquisition, Exploration, Well Site/Well and Closing), decision meetings suggest continuity or not for the next step. The official documents of each stage are stored for a possible audit in the future.

In this system I have been involved in the requirements survey, front-end and back-end design development. The system is evolving according to the evolution of the workflow it represents.

For legal reasons, interfaces can not be readable.

Project start year: 2010
Duration: Almost 7 months
Position: Sr System Analyst
Role: Developer, System Analyst, Designer, Front-end, Back-end
Working for: Atos Origin
Client: Petrobras
Technologies: C# .Net, Asp.Net, Oracle, Css, HTML, TFS, Linq, Adobe Photoshop,  jQuery, Scrum

2009 - Siplex Classic Pangea


Pangea was born to be the georeferenced Exploration data display system. In addition to displaying Basins, Blocks and Wells, he still consolidated some data and colored, according to a selected theme, the items being displayed.

Classic Pangea interface
To start the system, a geometric features drawing component was created. This system was responsible for creating the polygons in the displayed images. By working through the generation of images at each iteration of the user, the system was slow, because if it was zoomed in or out, the whole image was recreated.

A few years later the system was rewritten and the feature design component was no longer used, passing the Google Maps API to be used instead.

Pangea ForUs interface
The system continues to be used, but now inside another larger data display system and has been named Classic Pangea.

I have been primarily at the front end of these systems and more recently I have worked on the backend to reconcile the functionality of Classic Pangea with the Pangea Panel, the new Data Visualization system from Exploration.

For legal reasons, interfaces can not be readable.

Project start year: 2009
Duration: Almost 1 year
Position: Sr System Analyst, Consultant, Sr Consultant
Role: Developer, System Analyst, Designer, Front-end, Back-end
Working for: Atos Origin, Accenture, BRQ
Client: Petrobras
Technologies: C# .Net, Asp.Net, Oracle, Css3, HTML5, Xml, Web Services, TFS, Linq, Nuget, Adobe Photoshop, Asp.net MVC 4, Bootstrap,  jQuery, Json, nHibernate, Ninject, Google Maps API, ForUs

2009 - Siplex Seismic Schedule


Encouraged by the success of the Drilling Rigs Schedule, a new system was created to control another important feature of the oil industry - seismic. The adoption of the new system was not as instantaneous as the Drilling Rigs Schedule, which eventually left the project with few evolutionary and corrective demands.

The project was recently rewritten under the name Geophysical Activities Tracking without the predecessor's drag-and-drop interface.

The original project was derived from the core of Drilling Rigs Schedule with the Java backend and jQuery UI interface.

For legal reasons, interfaces can not be readable.

Project start year: 2009
Duration: 6 months
Position: System Analyst, Senior System Analyst
Role: Designer, Front-end
Working for: Atos Origin
Client: Petrobras
Technologies: Java, Css, HTML, Oracle, Adobe Photoshop, jQuery, jQuery UI, Json, Scrum

2008 - Siplex Well Site


The Well Site module was initially designed to control technical meetings to approving or reject drilling of a well.

A few months later the initial purpose of the system became just one item in a larger workflow, the system being completely rewritten and moving to control the entire workflow of well site information until it was drilled.

First version user interface
In 2011 the database objects were mapped using nHibernate and the back end was rewritten to allow for integrations and greater scalability. This rewrite was a facilitator to consume and share data among various systems of Exploration.

I was actively involved in the initial two versions, getting distant at the time of nHibernate adaptation and re-acting during the adaptation of the Well Site Panel module.

For legal reasons, interfaces can not be readable.

Project start year: 2008
Duration: Almost 2.5 years all versions. Still in development.
Position: Sr System Analyst, Consultant, Sr Consultant
Role: Developer, System Analyst, Help Desk, Infrastructure Analyst, Designer, Front-end, Back-end
Working for: Atos Origin, Accenture, BRQ
Client: Petrobras
Technologies: C# .Net, Asp.Net, Oracle, Css3, HTML5, Xml, Web Services, TFS, WCF, Linq, Nuget, Adobe Photoshop, Web API, Asp.net MVC 4, Bootstrap, jQuery, Json, nHibernate, Ninject

2008 - Siplex Tracking Blocks


The purpose of this system is to follow up on a block acquired by Petrobras, showing the legal obligations assumed by the company, when it was carried out and the current state of the block for the company, indicating if there will be continuity or return of the block, for example.

My participation in this system was very punctual, setting up the basic interface of the first version and some punctual adjustments of design and usability, not acting on the back end.

The system was rewritten and gained a new interface in 2015, where again I acted punctually in some front-end settings. In the back end it has gained several services to provide data to the HDS.

For legal reasons, interfaces can not be readable.

Old Version
Project start year: 2008
Duration: Almost 7 months
Position: Sr System Analyst
Role: Developer, Designer, Front-end
Working for: Atos Origin
Client: Petrobras
Technologies: C# .Net, Asp.Net, Oracle, Css, Html, SourceSafe, Ajax Control Toolkit, Web Services, TFS, Linq, Adobe Photoshop

New Version
Project start year: 2015
Duration: Almost 7 months
Position: Sr Consultant
Role: Designer, Front-end
Working for: BRQ
Client: Petrobras
Technologies: C# .Net, Oracle, CSS 3, HTML 5, Web Services, TFS, WCF, Linq, Asp.Net MVC 4, Bootstrap,  jQuery, Json, nHibernate, Ninject, Scrum, Kanban

2007 - Siplex Start


Siplex Start is the module responsible for listing, according to the user profile, which modules the user has access to and which ones he can request through a justification to the coordinators.

Current Siplex Start interface
It has already had four different interfaces, but always maintaining the same functionality. This module is where the members of the Siplex team are listed as well as the Siplex user service phone.

I was responsible for the interface of the first three versions, and the current one is the creation of Eduardo Derbli, former designer of the team.

Project start year: 2007
Duration: 2 months
Position: Senior System Analyst
Role: Developer, Designer, Front-end, Back-end
Working for: Atos Origin
Client: Petrobras
Technologies: Asp.Net, Asp.net MVC 3, Css3, HTML 5, Bootstrap, Oracle,  SourceSafe, TFS, Linq, C# .Net, Adobe Photoshop, jQuery, JavaScript

2007 - Siplex Wallet


The Siplex Wallet module was part of Siplex in Visual Basic 6 and was migrated to Siplex Exploratory Projects during its rewriting. It was demanded by the managers that other actors were involved in the control of portfolio data, so the separation of the modules was necessary.

The survey of requirements and interface prototyping with users was carried out on my coordination.

It has adapted the entire access control system and new functionalities for project management and reporting. Another need was a hierarchical filter system with different access profiles and where the final result, the list of projects, could be saved and added to other results for possible scenario simulations. 

Over the years other functionalities have been aggregated, such as consolidation charts (with Highcharts) and a simulator of project scenarios. The interface is the same until today, with some screens being included with a slightly different design and Bootstrap support.

For legal reasons, interfaces can not be readable.

Project start year: 2007
Duration: 1 year
Position: System Analyst
Role: Developer, System Analyst, Help Desk, Infrastructure Analyst, Designer, Front-end, Back-end
Working for: Atos Origin
Client: Petrobras
Technologies: C# .Net, Asp.Net, Oracle, Css, Html, Xml, UML, SourceSafe, Ajax Control Toolkit, Web Services, TFS, WCF, Linq, Nuget, Adobe Photoshop, Highcharts, Bootstrap, JavaScript

2006 - Siplex Administration


The Siplex administration module was created to centralize the access control of users of the modules. It was possible to register new modules, access profiles and user roles.

A component was used to provide the complete user profile to the module, which utilized integrated authentication, to allow or deny user access to that module. Recently this information was made available through the model's ORM mapping (nHibernate) and Rest services.

The module had an interface update in 2008, remaining to this day.

For legal reasons, interfaces can not be readable.

Project start year: 2006
Duration: 8 months (created and adapt the other systems)
Position: System Analyst
Role: Developer, Designer, Front-end, Back-end
Working for: Atos Origin
Client: Petrobras
Technologies: Asp.Net, Css, HTML, jQuery, Oracle, Web Services, WCF, Asp.Net Web Api, Adobe Photoshop, nHibernate, ORM, Linq, Nuget, JavaScript

2006 - Siplex Community


The Siplex Community was born from the need to exchange technical information among Siplex users. It started as a forum where it was possible to post messages and files and users could comment. After a while, it became only a repository of files.

It was recently rewritten updating front-end and back-end.

For legal reasons, interfaces can not be readable.

Old Version
Project start year: 2006
Duration: 3 months
Position: System Analyst
Role: Developer, System Analyst, Designer, Front-end, Back-end
Working for: Atos Origin
Client: Petrobras
Technologies: Asp.Net, Css, HTML, Oracle, SourceSafe, TFS, C# .Net, JavaScript

New Version
Project start year: 2014
Duration: 1 month
Position: Sr Consultant
Role: Developer, Designer, Front-end
Working for: BRQ
Client: Petrobras
Technologies: Asp.net MVC 3, Css3, HTML 5, Bootstrap, Oracle, TFS, Linq, C# .Net, Adobe Photoshop, jQuery, JavaScript

2003 - Siplex Exploratory Projects


The Siplex was an idealized system in the master's thesis of the geologists Reneu Rodrigues and Claudio Bettini in 1983 and written by the same ones in Fortran to Mainframe. It was adopted as a tool by the Exploration area of ​​Petrobras and TI assumed its maintenance and continuity. It is the system responsible for studies of the exploration areas, conducting commercial viability simulations and recording the geological parameters of the same. It is one of the main Petrobras Exploration systems in the world.

Fortran interface
In 2003 Siplex was a set of several programs in Fortran, with input and output of data through text files and a "friendly" interface written in Visual Basic 6 that triggered these various cores. This was the system used by geologists to record the information of an exploration phase and to generate simulation scenarios considering the various geological and commercial variables that could influence the exploration of the area.

I was hired by Accenture to work on the system, being responsible for the continuity and mainly the migration of the text files to the Oracle database when the new version of the system, fully rewritten in C # .Net was released.

Siplex 800x600 interface
In January of 2005 was released the new version, with its new interface, in popup format and 800x600 resolution . In January 2007 there was an adaptation of the interface, increasing the resolution to 1024x768. In this adaptation I began to play the design role for the team, being responsible for future systems interfaces until 2013.

Some years later, with the growth of the systems related to Siplex, this system became a module called Exploratory Projects, part of the workflow of exploratory project management. The name Siplex came to become the set of systems of this workflow, becoming SIPLEX - System of Planning and Exploratory Control.

Siplex 1024x768 interface
The development of the system is continuous, adding new technologies and functionalities depending on the demand of the managers.

After 10 years of using Siplex, some limitations began to appear due to the technologies used, which were already outdated, both in the backend and in the front end. Thinking about the continuity and growth of the project, with maintenance facilities, it was decided to rewrite the entire system, implementing technologies such as MVC, Rest, nHibernate and WCF for the back-end and Bootstrap, CSS 3, HTML 5 and Highcharts for the front-end.


In the market there are solutions that do what Siplex proposes, such as GeoX from Schulumberger, REP from Logicom E&P and prospect analysis software from Rose&Associates .

For legal reasons, interfaces can not be readable.

Old Version
Project start year: 2003
Duration: Almost 2 years to migrate
Position: Jr System Analyst, System Analyst
Role: Developer, System Analyst, Help Desk, Infrastructure Analyst, Designer, Front-end, Back-end
Working for: Accenture, Atos Origin
Client: Petrobras
Technologies: Visual Basic 6, C# .Net, COM+, VBScript, Asp.Net, Oracle, Css, Html, Xml, UML, System Architect, Rational Rose/XDE, Windows Performance Counters, SourceSafe, Ajax Control Toolkit, Web Services, TFS, WCF, Linq, Nuget, Adobe Photoshop

New Version
Project start year: 2014
Duration: Almost 1 years to migrate
Position: Sr. Consultant
Role: Developer, Designer, Front-end, Back-end, Infrastructure Analyst
Working for: BRQ
Client: Petrobras
Technologies: C# .Net, Oracle, CSS 3, HTML 5, Web Services, TFS, WCF, Linq, Nuget, Asp.Net MVC 5, Web API, Bootstrap,  jQuery, Json, nHibernate, Ninject, Scrum, Kanban, HighCharts

testimonial

Dear Francisco and staff, Our experience in the development of this solution was very rich. We were able to express our need and build the solution in a collaborative way with multidisciplinary TIC and EXP teams. The way of integrating the teams, using the collaborative resources (meeting room with stations and displays) facilitated the design of the application. The Well Site Panel (Painel de Locações) today is one of the main tracking tools for exploratory well planning. The speed of access, ease of navigation and the clarity of the information has aided the decision making process. In addition to the actual application, the constructive process provided corrections and improvements in the attributes of the well planning process, as well as improvements in correlated support tools. The Well Site Panel (Painel de Locações) has been and will be the catalyst for the improvement of other SIPLEX applications. A big hug and thanks for the partner.

Durval Borba

Manager @ Petrobras

Francisco is a complete professional, of those who "play in the 11". Infrastructure, back-end development, front-end development, nothing is a mystery to this competent and committed professional.

Eduardo Derbli

Designer @ IBGE and Triplin

Francisco added value to the project by developing a Framework to standardize the use of WEB interface resources of the applications developed by the team.

Carlos Eduardo

IT Consultant @ BRQ

SEND ME A MESSAGE