Please enable JavaScript.
Coggle requires JavaScript to display documents.
Caret: AL, AA, AC Understanding - Coggle Diagram
Caret: AL, AA, AC Understanding
Functional
AL: Customer portal offers the features to view and add notes, documents, events, view invoices etc.
AL: Mobile App gives access to contacts and matters/cases, notes related to them, events, and time tickets
AL: PDF forms app allows users to fill practice management forms manually or automatically through systems
AL and AA are Desktop Applications, while AC is on Cloud
AL: Practice management module provides features related to contacts, matters and events management
Integrations: O365, SFDC, HotDocs, Nextiva, APX
AL: Practice Mgmt has reporting engine to create column & Block reports - using predefined Crystal reports
AA: There is no reporting module in the application but it allows reports through SSRS that customer's tech team can use to build reports
-
Technical
AL: Customer Portal is on Angular 6 and 2, PDF forms on Visual XHarbour, Accounting program on VB6, Practice Mgmt on Harbour, Rest APIs, Mobile Work on Xamarin, DB migrated from Advantage to Postgres
-
-
Authentication: On AL and AA it happens through username and password with the option to map with domain user
DB: No up-to-date documentation available at Schema level and AL supports user defined tables and structures which vary from client to client
Logging: For AL and AA logging is happening but is on-premise, so, monitoring is not in scope. AC has internal logs on Blob Storage and on App Insights.
Scalability: AL and AA are desktop applications designed for smaller firms maxing out at 150 seats. AC faces issues beyond 20 users due MS throttling us out due to tight integrations with O365
Performance Monitoring: Less on AL and AA, but there on AC
AA: Desktop app on C# 4.8, WCF services, DB is MS SQL 2008 and above
AC: C# application using older Azure Classic services that will be deprecated, DB is MS SQL
Engineering Practices
-
-
No SCA tool configured, code reviews happen manually
Mature backlog management, scrum processes, defect triage practices followed on AL and AA side, AC is in maintenance mode
-
Some unit tests written for C# and Angular code but not Harbour and VB6 code (that part is tested using some test harnesses)
Test cases are documented at high level but categorized as sanity/smoke and regression tests in excels
50% of regression tests are automated in AA (using Ranorex), and 80% of core functionality automated in AL (using Java/WinAppDriver)
CI-CD in place for AL, AA, AC. AL uses Jenkins 2, Groovy Scripts and InstallAware; AA and AC use Azure Pipelines
Quarterly releases for AL and AA with 2-3 hotfixes between them; AC has adhoc patch release - about 10/year
Team
-
AL: 1 C# + Angular Dev (taking care of Rest APIs too), 2 C# + VB6 devs taking care of CI-CD pipeline (Jenkins 2, Groovy, Installaware), 2 Harbour Dev focused with some knowledge of C#
-
What about QAs and people with DB level expertise in AL where Advantage to Postgres transition happened recently?
-