Software Engineer

I was responsible for frontend generally - desktop application. Fixing of Bugs/Coding of new Modules (LMS-Activity/Ladle Prepare Manager) in C# WPF / MVVM Pattern.

The project was based on 3 layers namely Presentation, Business and Data. See project structure:

I was responsible for Frontend and Backend as well as Project Management for a Team of 7, which involve the area of experties:

Planning
Project Management – Adding users stories to product backlog in JIRA / Agile SCRUM
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Agile SCRUM

Presentation layer
WPF/C# MVVM Pattern .Net 4.6

Business layer
WCF Service / LINQ To SQL / Data Transfer Object / .Net 4.6

Data layer
Oracle/MS SQL 
There were 2 different client using the product namely ALGOMA and NUCOR

My job was to train learners from different company’s base on the BCS Syllabus (Software Development raging from Level 3 to 4) and also prepare them for MTA (Microsoft Technology Associate) / MCSA (Microsoft Certified Solutions Associate exams.

I use to prepare lesson materials for training purposes. The students were either doing apprenticeships on some of the companies like ARGO, NHS, SKY, SHARP among others.

Trainings were based on these programs:

• Java Fundamentals
• C# Fundamentals
• Develop Software using SQL
• MTA Programming in C#
• MCSA Programming in C#
  • Module 1 - Review of Visual C# Syntax
  • Module 2 - Creating Methods, Handling Exceptions, and Monitoring Applications
  • Module 3 - Developing the Code for a Graphical Application
  • Module 4 - Creating Classes and Implementing Type-Safe Collections
  • Module 5 - Creating a Class Hierarchy by Using Inheritance
  • Module 6 - Reading and Writing Local Data
  • Module 7 - Accessing a Database
  • Module 8 - Accessing Remote Data
  • Module 9 - Designing the User Interface for a Graphical Application
  • Module 10 - Improving Application Performance and Responsiveness
  • Module 11 - Integrating with Unmanaged Code
  • Module 12 - Creating Reusable Types and Assemblies
  • Module 13 - Encrypting and Decrypting Data

TECHNOLOGY:

1. C# programming language
2. Java programming language
3. MS-SQL (Structure Query Language)
4. Oracle Database Relational Management System
5. Dot Net Framework
6. Integrated Development Environment
   1. Microsoft Visual Studio
   2. NetBeans

I started working for MedicalCommunications GmbH a subsidiary of Heidelberg Engineering Inc. Germany.

I was responsible for both backend and frontend generally - desktop application. In details, the product was formally written in C# WinForms and the client wanted it to be translated to C# WPF / MVVM Pattern.

I implemented Plugins for several areas in Ashvins-Product/HEYEX with Visual Studio 2015, say, Universal Search Control, Display of Patient Information Control, Login windows, Fixing bugs in the existing WinForms project.

After laying all foundations of the application personally, I was later assigned by the CSO to further merge Ashvins application modules with HEYEX application. So, I set up a team of 5 to assist in doing so.
 

TECHNOLOGY:

Technology breakdown on the application process are:

1. Presentation Layer
   1. The entire frontend in built upon WPF (Windows Presentation Foundation) which is of two-side coding principle, namely XAML otherwise known as (Extensible Application Markup Language) and C#.
   2. The Pattern used was MVVM otherwise known as (Model, View, ViewModel) in the sense of separating the VIEW from the application object logics.
2. Business Layer
   1. WCF otherwise known as (Windows Communication Foundation) was used for the data communication between frontend and backend of the entire application, which involves the likes of:
      1. EntityFramework library, where classes were generated and mapped to a database table as a result of implementing CRUD principle otherwise known as (CREATE, READ, UPDATE and DELETE) upon the database without writing any SQL query otherwise known as (Structured Query Language).
      2. Repository Design Pattern was also used for data accessing through the help of EntityFramework and ServiceContract/OperationContract of WCF in manipulating the data’s directly on the database.
      3. Classes otherwise known as Entities were also implemented based upon table structure in the database.
3. Data Layer
   1. MS SQL is used as the database storing mechanism.

SOFTWARE PROCESSING:

• V-Model (I can’t complain – well implemented).
• SVN otherwise known as Subversion for the application version control
• JIRA (The application was well documented by the then Project Manager which happens to be Me)

COMPONENTS:

• DevExpress v17.1
• DotNetBars v10.1
• MS SQL 2014

I was responsible for frontend generally - desktop application. In details, the product was formally written in C# WinForms and the client wanted it to be translated to C# WPF / MVVM Pattern. My main job was to lay the basic of the application so Marc Cain developers can carry on from there.
I was responsible for Frontend development as well as Project Management for Team of 5, which involves:

Planning
Project Management – Adding users stories to product backlog in TFS / Agile SCRUM
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Agile SCRUM

Presentation layer
UI: WPF/C# MVVM Pattern .Net 4.6

I was responsible for frontend only - desktop application. In details, the product was formally written in C# WPF v3.5 by a student and the client wanted it to be translated to C# WPF v4 higher / MVVM Pattern. I implemented the entire frontend from scratch since the client wanted all to be written in clean code with Visual Studio 2015.

My responsibilities are:

Planning
Team leader (Team of 4) – Adding user’s stories to product backlog in TFS / Agile SCRUM
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Agile SCRUM

Presentation layer
UI: WPF/C# MVVM Pattern .Net 4.6
DevExpress v15.2,

I was responsible for frontend (Module – Ware House Management on Touch device) - desktop application. In details, the product was formally written in C# WinForms and the client wanted it to be translated to C# WPF / MVVM Pattern with Visual Studio 2015.

My responsibilities are:

Planning
Team leader (Team of 5) – Adding user’s stories to product backlog in TFS / Agile SCRUM
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Agile SCRUM

Presentation layer
UI: WPF/C# MVVM Pattern .Net 4.6, DevExpress v15.2,

E&L is a subsidary of Nexus AG.
I was responsible for frontend - desktop application. The product was implemented in C# WPF / MVVM Pattern with Visual Studio 2013.

Responsibilities:
Planning
Team leader (Team of 8) – Adding user’s stories to product backlog in TFS / Agile SCRUM
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Agile SCRUM

Presentation layer
UI: WPF/C# MVVM Pattern .Net 4.5, DevExpress v15.2,

I was responsible for frontend - desktop application. The product was implemented in C# WPF / MVVM Pattern with Visual Studio 2013.

I was one of the members who implement Nexus NG application Framework (Container) alongside other programmers from Indian. The framework is the basics of Nexus NG where all libraries are being implemented for re-use. The Framework is also where ORM/WCF services are being stored.

I was responsible for the implementation of the Patient list Modules. A list of all patient appears to be seen on the product, where one can select a patient to be added to the application context for a re-use in other modules.

I was responsible for the implementation of Document management system (DMS Module). As the name implies, the module is being used to scan and store documents of the hospital day to day activity.

I was responsible for DEMO implementation when the company is on for an exhibition. Getting various modules together depends on the demand since the entire produce is built on plug and play scenario.

I was responsible for frontend - mobile app. The product was implemented with PhoneGap/Coffee Script. I was responsible for the frontend with the help of one professional web programmer newly employed in house.

As Team leader I was also responsible for:

Planning
Design – I usually create moqups/wireframe when approved then implementation comes in.
Model: Waterfall

Presentation layer
UI: WPF/C# MVVM Pattern .Net 4.0, Infragistics NetAdvantage v14.0, HTML5, Coffee Script/JavaScript, Bootstrap, Facebook React (Web Scenario- Mobile App)

Business layer
WCF Service / ORM / Data Transfer Object / .Net 4.0

I was responsible for both backend and frontend generally - desktop application – Leading Role (Team 7). In details, I implemented Plugins for several areas with Visual Studio 2010 as well as fixing bugs in the existing WinForms project.

Planning
Project Management – Adding user’s stories to product backlog on a white board
Model: Waterfall

Presentation layer
WinForms/VB.Net .Net 3.0 higher
DevExpress v12.1, Infragistics v12.1

Data layer
MS SQL Server 2008/2012

I was responsible for both backend and frontend generally - desktop application. In details, I implemented Plugins for several areas with Visual Studio 2010.

Model: Waterfall

Presentation layer
WinForms/VB.Net .Net 3.0
DotNetBars v10.1

Data layer
MS SQL Server 2008