System development across the enterprise requires an integrated approach to meet enterprise needs. Smaller works forces, tighter budgets, a greater emphasis on shorter delivery cycles, and globalization have prompted many companies to commit themselves to the process and business-modeling path. .
Sophisticated regulatory requirements, once the concern of a limited number of industries, now affects every business. Regulatory issues are becoming more mission critical as government adjusts to the electronic information age and in particular document validation and security issues. .
All systems are global. All system development is local, regardless of the when, where, and who of the development teams. .
This guide provides general information about process and business modeling issues and offers suggestions for dealing with many of these issues.
The approach is a result of the following milestones:.
A common "project- language: The acceptance of the Unified Modeling Language (UML) as the defacto standard for cross system design and communication.
A phased project process: The standardization of a phased system process, in particular the Rational Unified Process (RUP) and the collected works of Steve McConnell, are widely accepted as a system engineering imperative.
Continuous iterative analysis and delivery cycles: Rapid development, extreme programming (XP) and the Agile process are highly focused system development processes with higher quality and shorted delivery requirements .
No other community faces exactly the same environmental issues, with the same constraints and the same resources. The tools in this guidebook, adapted for your situation, can help your community turn its environmental challenges into a positive force for the future. .