I'd like to vote for #3. OpenUP is architecture-centric and risk-driven, so it's ideal application profile is "Greenfield" projects with moderate to high architectural complexity.
For instance, a simple website with a few forms is probably not very architecturally significant, so an iterative process without an explicit Elaboration phase might work well for that project using nothing but 2-week sprints. By contrast, a broker project to orchestrate disparate financial systems with web services needs a "focus on the architecture to retire risks early." Thanks, Nate -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jaana Nyfjord Sent: Wednesday, March 21, 2007 11:08 PM To: [email protected] Subject: [epf-dev] Vote on architecture principle Hi all! The vote is now open. There are twelve eminent proposals of how to present the core architecture principle. Please, vote on the formulation you want to represent the core architecture principle. Send your vote by quoting the number of the formulation to this list ([email protected]). The vote will be open from Thursday March 22 and end Tuesday March 27 (Pacific Time). Depending on the results of the vote of this round, there may be another round to nail the preferred formulation. 1. "Focus on articulating the architecture" (currently on the web) 2. "Focus on the architecture to promote a shared view of the solution" 3. "Focus on articulating the architecture to retire risks early in the project lifecycle" 4. "Focus on the architecture to retire risks early" 5. "Explore/articulate the architecture to address technical risks early" 6. "Focus on capitalizing on risk as an opportunity to advance current capabilities in the project". 7. "Focus on architecture to exploit risk as an opportunity to advance current capabilities in the project." 8. "Focus on the architecture early to minimize risks and organize development" 9. "Focus on architecture in early iterations to achieve overall system stability" 10. "Focus on eliminating technical risk early to increase stability and predictability" 11. "Express and mature the architecture while reducing the risk in the solution" 12. "Focus on the architecture to both promote a shared view of the solution and capitalize on risk as an opportunity to advance current capabilities in the project" Cheers, Jaana Nyfjord _______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev _______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
