Architects & PM Guide – project Kick-off template/checklist

Repeatability is the key for the success of IT projects and this can be otherwise termed as “well-defined process”. In this post, I am sharing what I follow in all of my greenfield software development projects as simple checklists which I and my team are following nearly a decade. I am continuously refining, refactoring or tweaking the checklist as per the changes in the technology and infrastructure.

I would strongly recommend trying if you don’t have one. I tried listed in chronological order without any supporting explanations but for anyone who is Project / Account Managers, Solutions / Technical Architects or Software engineers can easily understand

1. Project Code

2letter client name + 3 letter project name + D or M or T + 1 to N

D – Development
M – Maintenance
P – Porting
T – Testing

1 – N = Phase 1, 2 … N

Example: CWCMPD1 [Chance World Car Market Place D 1]

2. Git Hub Repository

  1. <appname>.web
  2. <appname>.mobile
  3. <appname>.wireframe
  4. <appname>.web.html
  5. <appname>.mobile.native.IOS
  6. <appname>
  7. <appname>.mobile.web
  8. <appname>.mobile.web.html
  9. <appname>.server
  10. <appname>.devops

3. CI/CD & Infra setup

  1. Web.Build
  2. Mobile Android
  3. Mobile iOS
  4. Test flight set up
  6. Appliance setup – Dockers in virtual box (& direct install in the PC or EC2 Linux)
  7. AWS / AZURE cloud configuration (As applicable)
    1. IAM
    2. Access permission
    3. VPC
  8. Monitoring
    1. Infra Cost
    2. Servers & Disk space
  9. Failover
  10. Backup and restore
  11. Vulnerability patch management

4. Rest Endpoint links with some naming conventions (Start with dev first then Test or Staging and Production)

  1. api.<appname>
  2. api.<appname>
  3. api.<appname>
  4. web.<appname>
  5. web.<appname>
  6. web.<appname>
  7. m.<appname>
  8. m.<appname>
  9. m.<appname>

5. Paper work

  1. NDA
  2. MSA
  3. SOW / Work order

6. Database (in Postgres)

  1. dev.<appname>
  2. stg.<appname>
  3. prd.<appname>

Username: user

Password: password

Admin user: admin

Admin password: password

7. Collaboration

  • Slack named as <ProjectCode>

8. Team structure

  1. Designer
  2. Front-end developer web/mobile
  3. Test engineer (functional, Security, performance,)
  4. DevOps Engineer
  5. DBA
  6. Project manager
  7. Architect
  8. Technical writer

9. Tools used

  1. Bitrix / JIRA / Github Projects etc.
  2. Invision
  3. Github
  4. AWSCloud/docker
  5. Docker
  6. Mockaro /faker
  7. Virtual box

10. Project Setup in PM tools like Github Projects / Bitrix / JIRA

  1. Project Creation
  2. Team member allocation
  3. Client contacts
  4. Sprint or Milestone setup (For each sprint)
    1. List all Business functions
    2. List all test casesi. Functional

      ii. Security

      iii. Performance

    3. Defects / Bugs (Cycle 1, Cycle 2, Cycle 3)
    4. Devops Tasks
    5. Wireframe Tasks
    6. HTML Tasks
    7. Backend / Server / API Tasks
    8. Front-end tasks – Web
    9. Front-end tasks – Mobile website
    10. Front-end tasks – IOS Mobile
    11. Front-end tasks – Android Mobile
  5. Wiki page setup (in GitHub as markdown pages or Bitrix template)
    1. Getting Started
    2. Environment Setup
    3. Release links
    4. Business Architecture
    5. Process Flows
    6. Technical Architecture
    7. Software & Hardware Requirement
    8. Open Source Libraries & Frameworks
    9. Technical Deep Dive
    10. Data dictionary
    11. Project Dashboard in Kibana (as bitrix in-app)
    12. Weekly Status Reports
    13. Steering Committee Reports
    14. User Guide
    15. Releases (with release notes)
    16. References

11. Miscellaneous

  1. Project wiki
  2. Rest end points
  3. Mock data creation
  4. Kibana reports
  5. Repo permissions

Front-End (Web and Mobile) development workflow

Sharing here my time-tested agile front-end development methodology I have been using in all my greenfield development projects with success with my team comprises of:

  • UI/UX Engineers with business and creative acumen
  • HTML programmers
  • Front-End engineers experienced in building Angular and React.JS mobile and web applications of any size
  • REST API (Backend) developers
  • DevOps engineers.

I pictorially depicted the development process. It has 5 major steps

Web &amp; Mobile App Workflow

  1. Entire application visuals, pages, forms etc. etc. created in Invision with exactly how we wanted the finished application would look like with the ability to navigate each screen by clicking on action buttons as-if we are using the real application. We can collect feedback on each screen within the invision with comments coach marks.
  2. Once the visuals are approved, the base application or skeleton application built in clean HTML and CSS by professional HTML programmers. You need highly skilled HTML programmers, not the ones who can create an APP using Twitter bootstrap or copycats.
  3. Then, build React.JS and REST API simultaneously
    1. Create the React.JS or Angular.JS application using the just created HTML and CSS templates and wire-up each screen with mock JSON Data
    2. Build the REST APIs using the programming language and framework of our choice. I use Node.JS (Sails.JS) or Java (Spring) or Python (Flask) as lambda functions and exposes it thru API gateway. Before the actual development, we finalize every endpoint mapped to the user interface with mock data leveraging integration response in AWS API Gateway. We also use Mockaroo or Facker.js to generate synthetic data to mimic production data.
  4. then, integrate the Front-end and Back-End and continue to deploy and test the application. 90% of the time, there will  (should)  not be any changes in the REST Endpoints between mock and actual REST API. It should be a black box for the front end developers.
  5. Go-live from the day we completed step # 2. Our DevOps automate the build and deployment process and release the packaged code as docker image as well as host it in AWS S3. We create 3 main environments with various configurations (we follow conventions over configuration approach)
    • Development – Every day or alternate days we release current dev. branch version with new web links without destroying previous dev. releases
    • Staging – Every week we release staging deployment for the client to test and collect feedback
    • Production – Case by case basis, we release production version when we do Staging release to make sure the code works in production as expected without any last minute hassles.



We Use Buddy Works for Continuous Integration workflow from Github code pull to Build to package, version bump, deploy, back-up & roll-back, slack notification and sending emails the build URL to project team members and stakeholders.


createlyNote: The diagram I used in this post is created using creatly. You can get the original editable diagram from my GitHub as part of giving back to the opensource community.






How to write Techno Commercial proposal for a large software projects?

digital_leftWriting software technical proposal is art and it requires experience and expertise from different skill sets however IMHO any software architects should be able to create such proposals individually but the reality is not true.

In large organizations, there is a dedicated team called “Presales” whose job is to create proposals and respond to RFP & RFI’s, participate in war rooms, running thru proposal presentations, participate in requirements understand and Q&A sessions. Usually the Pre-sales team comprises of Business Development executives, Software Architects / Leads, Engineers / Developers / QA Specialists, Technical Writers, Business Analysts, Business Finance Executives, Project Managers etc. etc. but the role of the Architect is crucial and everything revolves around his deliverables i.e. estimates, solution architecture etc. and based on that the rest of the team arrives with effort, cost and schedule estimates.

Finally, the packaging of the proposal requires documentation, organizing and presentation skills and in my experience many companies and individuals struggle to make one nice proposal due to lack of experience, confidence and finally lack of templates hence I wanted to open source the work I have been doing for many years as Architect and sharing the skeleton proposal template that can be downloaded from my public GitRepo

A preview of the Techno-Commercial  proposal’s Table Of Contents is given here



How we built our cloud based physician portal web, mobile and HL7 Interface engine – 01

AZ-Tech Radiology is one of the leading medical imaging organization that provides the highest quality imaging services utilizing state-of-the-art equipment and technologies in Arizona.  Our primary goal is “Keeping the referring physician happy”, all roads lead to the ease of delivery of “radiology reports” to them and their sending of orders to the lab”

In order to meet the goal, we have to have state of the art technological solution which drove us to build the new cloud based connected IT systems:

  1. Radiology Information System
  2. HL7 Interface Engine which connects all of our modalities, external EMR and Insurance companies, pushing data to the cloud in a secure manner.
  3. Promotional Website @
  4. Physician Portal to delivering the reports @
  5. Physician mobile app @

In this blog post I would like to share the Architecture we came up with which powers our IT systems.

HL7 Interface of our Modalities (Imaging equipment) with RIS



Industry standard HL7 messages going out from RIS & coming in to Helen RIS

ADT A28 Add person information
ADT A31 Update person information
ORM O01 Order message
ORU R01 Unsolicited transmission of an Observation message
SIU S12 Notification of new appointment booking
SIU S14 Notification of appointment modification
SIU S15 Notification of appointment cancellation

End-to-end HL7 interface engine – on-prem to cloud connectivity


Industry standard HL7 messages going out from RIS & coming in to Helen RIS

  1. Available On Web And Mobile
  2. Highly Secure With Two Factor Authentication
  3. Immediate Near Real Time Access To Reports
  4. Text/Email Notification When Stat Report Is Ready
  5. Reports Can Be Searched By Dob, Patient Name, Date Etc.
  6. Reports Can Be Filtered By Stat
  7. Lightning Fast Free Text (Natural Language) Search Against Reports Powered By Elasticsearch & Lucene Index
  8. Cross The Border – (we call Inter State) : Multi Location Clinics Can Search Reports /Patients Across Their Locations Served
  9. Cross The Border – (we call Inter Country) : Providers Can View Reports Of Other Providers With Online Consent
  10. Reports In Hl7 Format Can Be Exported To Import Into Their EHR System
  11. Orders Can Be Placed Online – Hl7 Upload And Forms Based Upload
  12. High Resolution Diagnostic Images Can Be Viewed Online Without Any Client Tools Installation.
  13. Real-Time Analytics / Kpi Dashboard For Clinic Administrators
  14. Create And Manage Your Users & Roles Online
  15. View Who Did What, When?
  16. Free Integration With our partner’s EHR / EMR Software’s For Orders And Reports
  17. HIPAA Compliance ready


End result

After we implemented the solutions in phased manner starting from Jan 2018 uptil now, following are the benefits we gained

  1. Average speed of our report delivery time reduced from days to minutes
  2. Cost of the delivery of reports reduced multi-fold otherwise we enagened half a dozen employees faxing the reports to the physician office manually
  3. We can deliver the reports to physican hands thru our mobile solution
  4. We automated the sending of Fax (reports) to the clinics who still needs paper copy of the reports
  5. Customer satisfaction thru enhanced user experience in the form of simple to use web and mobile application
  6. Powers 1000’s of reports per day with ability to auto-scale to handle more reports in the future

How we built our blazing fast promotional website in Angular.JS SPA

I just wanted to share how we built our public facing Radiology website  developed using our homegrown minimalistic, lean & mean CMS framework called as “Helen CMS” built on top of Angular.js and Node.JS libraries


Features of our home grown Helen CMS

  • Built for speed of the development
  • Blazing fast
  • Clean code separation
  • Template driven user interface
  • Highly scalable
  • Multilingual
  • No database required
  • Deploy by git / Gulp tasks
  • First class support for AWS Deployment
  • Hosted in server less environment AWS S3
  • Can run in AWS free tier – Zero operating cost
  • App in appliance (Container ready) for xcopy deployment on local server (on-premise) or on the cloud
  • 100% offline capabilities implemented through advances cache, Local Storage and Index DB with automatic cache busting and refresh
  • RESTAPIs can be built on any programming language of your choice, we use Node.JS deployed as Lambda Services and exposed through API Gateway
  • Each lambda services built on SRP (Single responsibility Principle) design principles and they are completely loosely coupled
  • Built on Micro services architecture
  • User actions persisted in lightweight database for analytics
  • Fluid page rendering without freezing the UI


React.JS for beginners – Recommended starting point video tutorials

Though I have been using and advocating Angular.JS for nearly 5+ years but fell in love with React.JS due to its simplicity, performance, adoption by developer communities and enterprises. When it comes to teaching newcomers to learn React.JS, always struggled with where to start i.e. Pluralsight video,, google search etc. hence publishing this articles for newcomers and this is purely my personal preference.

As I said, there are hundreds of ways to start learn React.JS for beginners however the following 5 part video tutorial by Telmo Sampaio is my recommendation. This doesn’t cover backend interaction like Restful services but the environment setup, project creation, understanding the folder structure, UI components are covered pretty well.


1. Windows PowerShell or command line

2. Node.JS

3. IDE


Back On Blog writing

It’s been few years I didn’t get into blog writing on regular basis which I wanted to cut it out and get back to share all of my technical, business, techno marketing encounters from my past 2 ~ 3 years which helped me, my employer, my team here at onsite and offshore and the clients I worked with. It will be a series of blog posts and I am pretty sure all of them will be useful to the readers from various background and experiences.

Headstart Microservices Architecture using AWS Lambda in your favorite programming language (Node.js or Python or JAVA)

The way we build software has changed stupendously from Monolithic Architecture (MLA) using single programming language to a Microservices Architecture (MSA) where pieces of code developed in multiple different programming language that fits the problem in hand. Microservice has numerous benefits and encourages Single Responsibility Principle (SLP) with quick deployment and easy to change lifecycle without impacting the fatty software.

AWS offers easy way to implement microservices through RESTful APIs wrapped against AWS Lambda functions in a server less backend that can auto scale with built in security via its IAM. AWS offers 12 months free tier which enable you to get hands-on experience with AWS Cloud Services.

To demonstrate the power of AWS API Gateway & Lambda, I quickly dropped my flicker photo search node.js code as lambda function wrapped in AWS API Gateway and exposed it as REST API Endpoint.


var Client = require('node-rest-client').Client;
var _ = require("underscore");
var json2xls = require('json2xls');
var fs = require('fs');
//API Explorer :
var flickr_api_endpoint = ";;
var flickerPhotos = [];
exports.handler = function (request, context) {
//1) Resolve input and execute REST calls
try {
var flickr_api_key = request.api_key;
var flickr_search_tags = request.search_tags;
var flickr_search_text = request.search_text;
var flickr_search_limit = request.search_limit;
var flickr_search_currentpage = request.search_currentpage;
flickr_api_endpoint = flickr_api_endpoint + "&api_key=" + flickr_api_key + "&tags=" + flickr_search_tags + "&text=" + flickr_search_text + "&per_page=" + flickr_search_limit + "&page=" + flickr_search_currentpage
var client = new Client();
client.registerMethod("flickrSearch", flickr_api_endpoint, "GET");
catch (e) {"Something wrong in the input! please check. [" + e.message + "]");
//2) Process REST call response and send it back to the client.
var args = { headers: { "Content-Type": "application/json", "Cache-Control": "no-cache" } };
client.methods.flickrSearch(args,function (res, rawdata) {
try {
console.log("Length = [" + + "]");
_.each(, function (item, index, list) {
//console.log("http://farm&quot; + + "" + item.server + "/" + + "_" + item.secret + "_b.jpg");
flickerPhotos[index] = "http://farm&quot; + + "" + item.server + "/" + + "_" + item.secret + "_b.jpg";
catch (e) {;
view raw flickerphotos.js hosted with ❤ by GitHub

AWS lambda does not support 3rd party npm so make sure to upload all of your 3rd party node_modules. AWS Lambda & API Gateway Getting Started guide will be your good head start.








RESTful API 10 Best Practices I follow

Following are the SILVER BULLETS when I create REST APIs. These were originally published here in the year 2014 and the credits goes to them but my true salute goes to OMAR AL ZABIR who published with sample source in C# in his blog post Build Truly RESTful API and Website using Same ASP.NET MVC Code way back in 2012 where he talked about RESTful services naming conventions and leveraged the Controllers  from ASP.NET MVC exported as REST API without using API.NET WEB API using content negotiation and http header (point # 5 below)



  1. Use nouns but no verbs
  2. GET method and query parameters should not alter the state
  3. Use plural nouns
  4. Use sub-resources for relations
  5. Use HTTP headers for serialization formats
  6. Use Hypermedia as the Engine of Application State (HATEOAS)
  7. Provide filtering, sorting, field selection and paging for collections
  8. Version your API
  9. Handle Errors with HTTP status codes
  10. Allow overriding HTTP method

Do not end here but head over to the above mentioned two blog posts to gain the internals.

AngularJS web app scaffold with YEOMAN, BOWER & GRUNT and deploy in SURGE.SH

There are number of ways one can create AngularJS web application and often times we search for seed projects for bootstrapping. For AngularJS plenty of seed projects out there in the web but the one from YEOMAN is lean, clean with outstanding code lab which is super simple for anyone from novice to advance.

yeoman  bower-phoenix-javascript-meetup-1-638 grunt




YEOMAN – Create New web projects

BOWER – Search, Add and Manage dependencies

GRUNT – Task runner i.e. watch, preview, bundle, build, test and the list goes

SURGEStatic web publishing for front-end developers. Using grunt-surge npm package, you can automate the deployment through grunt cli with the command grunt deploy