Sicherheit in Low-Code-Entwicklung gewährleisten: Warum IT-Oversight wichtig ist

IT sollte sicherstellen, dass Composable Elements für Low-Code-Applikationen Company Security und Data Privacy Standards erfüllen.

Low-Code-Development bietet großartigen Weg für Companies, Apps schnell zu bauen. Big Selling Point: Low Code Offloads Tasks von IT/Developer Staff → Business Units/Citizen Developers Take Matters Own Hands. Result: Business Units/Individuals Develop Exactly What They Need – No Wait für Corporate Dev Resources.

Heißt das: IT hat No Role? Natürlich nicht. IT braucht Oversight für Several Reasons. Common Low Code Use Cases/Practices Examining erklärt Why.

Common Low Code Use Cases

Companies finden: Low Code Ideal für Couple Generic Classes Applications.

Eine Kategorie: Apps für Small-Scale Automation Capabilities. Prime Candidates: Automation Smaller Workflows – Tapping Into Database, Email, Transactional System → Task Perform Wie Human. Beispiel: App Checks IoT Data State System → Auto Send Email Alert If Threshold Value Exceeded.

Companies nutzen Low Code auch für Programs Analysis IoT Data. Low Code Developed App Might Ingest IoT Data → Trend Analysis/Anomaly Detection. Program Might Use Composable Elements: Predictive Analytics Perform oder Data Through Existing ML Model Run. Sophisticated Analysis Routines → Low Code Developers als Composable Element Available.

Siehe auch: Low Code Automates Industrial Processes Faster

Wo IT Oversight Reinkommt

Ein Area Where IT Involved: Managing Potential Security Risks. Low Code Enables Citizen Developers Apps Develop Without Waiting IT. Doesn't Replace IT Completely – Enterprises Still Need IT For Higher-Order Tasks: Governance, Data Ingestion, Cybersecurity.

Way To Manage/Contain Problems: IT Oversees Operations. Not Day-to-Day, Not Large Time Investment – Would Defeat Low Code Purpose. Rather: IT Should Ensure Composable Elements For Low Code Apps Meet Company Security/Data Privacy Standards. IT Also Can Impose Restrictions On Datasets Used In Low Code App. Particularly Important When App Touches Mission-Critical/Enterprise-Wide Systems.

Scalability Also Must Be Considered When Such Systems Incorporated Into Low Code Developed App. Here Again: IT Must Get Involved. Citizen Developers Tend Create Apps That Don't Scale Well (Harvard Business Review). Authors Suggest:

„Best Situation Often Hybrid Citizen/Professional Development Model: User Develops 80% Model → Hands Off To Developer For Polishing. Or User Develops Initial App Via Graphic Interface Tool → Gives To Developer To Program In Python/Other More Scalable Language. Either Case: Developer Records System Exists, Ensures Works Correctly, Connects To Needed Data/Transactional System.“

Approach Not Needed All Orgs. But Some Form Worth Considering If Citizen Developer Apps Adopted Throughout Org – Not Just Within Business Unit.

IT's Role Retaining Institutional Knowledge

Big Benefit Low Code: People With Intimate Knowledge How Things Work Get Tool To Do Things Better. Shop Floor Manager Quickly Puts Together Performance Monitoring App Based On Expertise. Similarly: Service Staff Member Builds Maintenance Scheduling App Factoring IoT Data Analysis Real-Time Equipment Status/Performance. Such Apps Essentially Capture Expert Knowledge Within Company → Others Benefit From Expertise.

Apps Fine, But: Person Who Developed App Leaves, Or Someone Wants Changes/Use App Other Purpose → Knowledge Leakage (Common Across Industries, Certainly Common Non-Low-Code Cases).

Increasingly: Companies Realize Need Implement Knowledge Capture/Retention Policies/Best Practices. IT Can Play Role: Helping Develop Best Practices Low Code Programming. Might Be Simple: Requiring Citizen Developer Fill Out Form Detailing: App Purpose, Data Sources Used, Components Used + Why.