issues
search
postman-open-technologies
/
lifecycle
Defining the API lifecycle in a modular, reusable, and machine readable way that can help others learn about what the API lifecycle could be, as as define their own evolving API lifecycle.
https://apis.how/products/web-design/
Apache License 2.0
15
stars
9
forks
source link
Challenges / Solutions
#251
Open
kinlane
opened
2 years ago
kinlane
commented
2 years ago
Usability
(U1) Onboarding Friction / Onboarding Easy
(U2) No Documentation / Documentation
(U3) Inconsistent / Consistent
(U4) Not Repeatable / Repeatable
(U5) Complexity / Simple
(U6) Duplication / Efficient
Stability
(S1) Outages / Availability
(S2) Slow / Performant
(S3) Not Scalable / Scalable
(S4) Low Quality / High Quality
(S5) Breaking Change / Change
Trust
(T1) Unreliable / Reliable
(T2) Risk / Safety
(T3) Non-Compliant / Compliant
(T4) Vulnerable / Secure
(T5) Incidents / No Incidents
(T6) No Communication / Communication
Motion
(M1) Not Discoverable / Discoverable
(M2) No Change / Change
(M3) No Momentum / Momentum
(M4) Awkward / Agile
(M5) No Feedback / Feedback Loop
Advantage
(A1) Reactive / Proactive
(A2) Missed Opportunities / Opportunities
(A3) Stagnation / Innovation
(A4) Unknown Resources / Known Resources
(A5) Unknown Capabilities / Known Resources
Usability
Stability
Trust
Motion
Advantage