Schema31 – Digital platforms for public sector

Schema31 – Public sector digital platforms & SOA architectures

Designing and leading complex, service-oriented solutions for public administration and training ecosystems

While employed at Schema31, the role covered Team Leader, Senior Analyst Programmer & acting Product/Project Lead on a portfolio of digital platforms for public and institutional clients. The work included the design and development of:

  • complete CRM solutions for managing relationships with citizens, companies and training providers
  • authentication providers for issuing and managing digital credentials
  • accreditation providers for training entities and educational services
  • monitoring systems for public projects and activities
  • electronic invoicing software integrated with public and institutional workflows

Beyond development, I was responsible for requirements analysis, architectural design, team coordination and technical documentation used in public tenders and contracts.

COMPANY

Schema 31 S.p.A.

DOMAIN

Public administration · Education & training · eGovernment

ROLE (AT THE TIME)

Gaetano Borgosano — Team Leader – Senior Analyst Programmer & acting Product/Project Lead

ENGAGEMENT

Employee working on multiple digital platforms for public and institutional clients

PERIOD

February 2012 – October 2016

STATUS

Several platforms delivered and used by public and institutional clients


Context & challenge

Building software for public and institutional environments means working with:

  • detailed regulatory and procedural frameworks
  • multiple stakeholders (administrations, training bodies, companies, professionals)
  • systems that must remain reliable, auditable and maintainable over time

Key challenges included:

  • translating laws, regulations and procedures into digital workflows and data models
  • designing platforms capable of handling large volumes of records and users
  • adopting SOA-style architectures to connect different services and data sources
  • coordinating a development team under fixed contractual constraints and deadlines
  • aligning technical solutions with the expectations and specifications of public tenders

Role & responsibilities

As Team Leader – Senior Analyst Programmer, my responsibilities included:

  • analysing requirements and designing complex systems for CRM, authentication, accreditation, monitoring and electronic invoicing
  • designing and implementing service-oriented architectures (SOA) to support integration between internal services and external systems
  • developing core modules and components across several platforms in the public sector portfolio
  • coordinating the development team, supporting task planning, mentoring, and code review
  • contributing to the selection and onboarding of technical resources
  • delivering training to developers and stakeholders on how to use and evolve the systems
  • writing functional specifications, user stories and product manuals
  • supporting the preparation of technical documentation for public tenders and software supply contracts

Approach

The work at Schema31 combined structured analysis, SOA design and agile-inspired practices focused on learning and iteration:

  • From regulation to working prototypes
    Started from legal and procedural requirements and quickly translated them into early prototypes, used to validate workflows and rules with stakeholders before committing to full-scale implementation.
  • Incremental and iterative delivery
    Broke down complex public sector systems into increments, delivering usable slices of functionality step by step so that feedback from real use could guide the evolution of CRM, accreditation, monitoring and invoicing features.
  • Pair programming and shared ownership
    Used pair programming sessions on critical components to spread knowledge across the team, reduce defects and keep architectural decisions consistent across different modules and projects.
  • Service-oriented design
    Designed platforms around clear service boundaries, so that CRM, accreditation, monitoring, invoicing and authentication components could interact while remaining independently evolvable and easier to maintain.
  • Automated testing and CI
    Introduced and promoted automated tests for backend components and user interfaces, integrating them into continuous integration (CI) pipelines to catch regressions early and keep changes under control.
  • Acceptance testing with public stakeholders
    Worked with project owners and institutional stakeholders to define and run acceptance tests, ensuring that delivered systems matched contractual requirements, regulations and the real operational needs of users in the field.

Results & impact

This experience contributed to:

  • the delivery of multiple digital platforms adopted by public and institutional clients for CRM, accreditation, monitoring and invoicing
  • the introduction and consolidation of SOA-oriented architectures in the solutions developed by the team
  • improved coordination and quality within the development team through structured analysis, design and review practices
  • stronger alignment between technical solutions, regulatory requirements and public sector constraints

For my practice, Schema31 was a key step in:

  • learning how to design software for regulated, public sector contexts
  • handling complex domains under contractual and procedural constraints
  • combining analysis, architecture, development and team leadership within the same role

Tecnologies & methods

  • Technologies: web-based information systems, service-oriented architectures (SOA), CRM-style platforms, backoffice and reporting components, integrations with external and institutional services
  • Methods: public sector requirement analysis, system and workflow design, team coordination, code review, documentation for tenders and contracts, user and stakeholder training

Status & next steps

  • Current status: The platforms delivered during this experience have been used by public and institutional clients to support CRM, accreditation, monitoring and electronic invoicing processes.
  • How this informs Integratia: This background gives Integratia a solid foundation for working with public administration and regulated domains, where governance, compliance and long-term maintainability are as important as pure implementation.

Your interest

Working with public administration or regulated environments and need someone who understands both the technical and procedural side?
Let’s talk about your context and explore how structured analysis, SOA thinking and solid team leadership can support your digital initiatives.