3.3. Doing Software Right: Enterprise Architecture Development
Solving complex problems with teams of people requires planning. For enterprise software systems, some of the most important planning is highly technical (i.e., planning system architecture).
Planning generates artifacts, but planning (as an activity) is much more important than project management plans, the typical artifacts. By this, we mean that document-driven process is not recommended because its priorities focus on paper artifacts, whereas the real product of any software development project is software. Instead, we view planning in a broader context, with multiple levels of formality and technical detail. For example, architecting is planning, and so are requirements analysis, ...
Get Software Architect Bootcamp now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
