Research architecture requirements and needs, identify and resolve trade-offs
From atwg
| Description | Starting from user stories and work flows, identify requirements. Based on available technology and resources, identify constraints. Present trade-offs to PMs and C-Level management for resolution. NOTE: This informs the re-design and refactoring of the API layer, MW core, as well as auxilliary aspects such as Varnish, RESTbase, and EventBus. |
|---|---|
| Associated Outputs | [[Output:1.1|]] |
| Type | Research |
| Primary Team | MediaWiki Platform |
| Collaborating Teams | WMDE, Reading Infrastructure, Services, TechCom, Performance, Parsing |
| Start Year | 0 |
| End Year | 0 |
| Duration (months) | 3 |
| Depends On Tasks | |
| Risks | |
| Contingencies | |
| Benefits | |
| Assumptions | |
| Implications | |
| Notes |
