The IEEE Standard Appendix of Software Engineering terminology evaluates quality as, “The degree to which a system, component, or process meets specified requirements”.An individual software component is a software package, a web service, a web resource, or a module that encapsulates a set of related functions or data. Ownership of individual components is easier than running bulky tests to ensure the quality of a monolithic application before a release. Micro-services test automation has become popular because it offers a way to structure an application as a set of small services that can be developed, deployed, and managed independently. Each service is self-contained and has a specific responsibility. These services communicate with each other using well-defined APIs. This approach can help you build and deploy applications quickly and respond to changes in customer requirements.

However, this is easier said than done, and let’s face it, our working memory is limited. Researchers have found that learning a structure with many interaction components is more complex than learning a system with fewer interaction elements and requires more cognitive capacity to process. CLT, De Jong (De Jong, 2010) states that ‘cognitive load theory asserts that learning is hampered when working memory capacity is exceeded in a learning task’.

In the realm of software development, an elevation in cognitive load is directly linked to a decline in developer experience. Ever-increasing tools and technology choices in the last few years and changes in working practices such as DevOps have increased the cognitive load on software developers and SDETs. The question to be answered is ‘How can we improve an individual developer’s experience and software quality simultaneously?’ This talk attempts to answer this question by focusing on ways organizations can use Internal developer portals to improve developer experience and accelerate product innovation.

September 6 @ 09:45
09:45 — 10:30 (45′)

Srividhya Chandrasekaran