Senior Staff

To work and be recognized as a professional software architect, specifically as an BUSINESS AND ENTERPRISE APPLICATION/TECHNO-DOMAIN ARCHITECT.

To use latest research, tools and technologies in domain of Business Applications and to develop a custom Business Application Framework based on Metadata, Processes and Rules.

To earn a reasonable and a decent living for my family through fair and honest means.

Analysis, Design and Architecture of Business Applications

Conceptual and ontological analysis and modeling.

Distributed Business Application development.

Business Processes and Business Rules.

ERP/Financial Applications.

Metadata, Business Processes and Business Rules.

In business application(BA)software development perspective, I have expertise in two dimensions. First is to develop business applications using prevalent tools, technologies and methodologies. In this perspective I am basically a backend professional. I am strong in understanding complex business domains, user requirements, elaborating, refining, transforming user requirements into functional requirements and then designing suitable modeling and design abstractions. Thus architecting such scalable technical design that leads to successful software product. I have designed many relational databases and respective business layers for systems that are running successfully in production for over a decade. Frontend expertise are limited to basic technologies like Html, CSS and typescript/JavaScript. Work on frontend only when there is compelling need.

The second dimension is research, knowledge and experience in domain neutral/specific business semantics and metadata, process and rule-based generic business application development. My expertise in this area are still not perceptible in my environment. I am in process of developing and implementing a custom BA development methodology/Framework using above mentioned knowledge areas.

I have been working (slowly as I am in Job) for last many years to coin a custom Rapid Development Methodology and now this work is almost 70 % complete. In current circumstances it will take about 6 months may be more for me to get remaining 30 % work completed.

It is very hard and complex to explain in writing what I have been trying to accomplish but it can be said that it is an integrated development framework based on use of Integrated Metadata of Storage, Business and UI layers. Some major functional areas are listed below.

• Custom Dependency Injection.
• Custom ORM layer.
• Custom Flow Engine.
• Custom Inference/Rules Engine.
• Custom UI Framework
• Custom Code Generation Layer

Once this framework gets completed the normal development time/effort of a .Net based application can be easily reduced to 50%. Also, applications built on top of this framework will be highly configurable and scalable. If anybody reading this feels interest he can contact me and I can try to further explain.

During 20 years of my IT career, for many years I have remained actively engaged in a tedious and exhaustive research and development exercise for developing a comprehensive FRAMEWORK that can assist and can be used as base for building ENTERPRISE level BUSINESS APPLICATIONS. This endeavor has helped me in gaining knowledge and insight of numerous theories, methodologies and technologies which have been used in past, are being used now and will be applied in future for building ENTERPRISE LEVEL BUSINESS APPLICATIONS. Particularly the emphasis remained on applying Agile theories and methodologies for building an open ended framework. Also during this time I have gained a sufficient understanding of most general business concepts and specifically which are common across various business domains.

I possess comprehensive insight and knowledge of following stable and emerging disciplines and areas of computer sciences and specifically Software and Information Engineering Approaches related to enterprise level agile business applications.

• Conceptual Modelling.
• Distributed application architecture.
• Client server architecture
• Logically distributed n-tier application architecture.
• Physically distributed n-tier application architecture.
• Service Oriented Architecture.
• UML
• Object oriented Modeling, and Adaptive Object Modeling.
• Relational Data Modeling and Business Rules Modeling.
• Semantics of Business Vocabulary and Rules (SBVR).
• Business, Domain, Process and General Ontologies.
• Business Process Definition Meta Model(BPDM) and BPMN.
• Business Rules based modeling and Design.
• Web Mark-Up languages like XML, WSDL.
• Rule Mark-Up languages like RuleML.
• Business Processes languages like BPDM, BPML.
• RDF (Resource Description Framework)
• Information Semantics and Ontologies.
• Business Processes.
• Business Rules.
• Complex Events / Situations.
• Meta data Driven, Model Driven and Domain Driven approaches.
• Adaptive Object Modeling.
• Agent oriented Modeling.
• Aspect Oriented Programming.
• Semantic Web Technologies.
• RDBMS Design, Models and SQL