1. Cultural Heritage in REGional NETworks REGNET

2. REGNET Development process

3. October 2001Project presentation REGNET 3 Why UP? Best practices: iterative development, architecture-driven,... Process = Define Who do What, When to do it, and How to reach the objectives Organizational cohesionshare a common: Processview of how to develop software Process tool and documents (RUP Tool) Terminology Set of models Designer / Developer Analyst Tester Database Administrator Performance Engineer Release Engineer Project Leader

4. October 2001Project presentation REGNET 4 UPSome Key Ideas Iterative development Architecture-centric Risk driven Careful requirements management and change control Continuous verification of quality Use case-driven

5. October 2001Project presentation REGNET 5 Development in short time-boxed cycles. An iteration includes all workflows UP Phases: Iterative Developement

6. October 2001Project presentation REGNET 6 Feedback and Adaptation Continuous feedback is a key ingredient for success. From the users, tests,... In each iteration, we adapt based on feedback and insight from the last iteration, and slowly converge on better: Design, plans, requirements, estimates

7. October 2001Project presentation REGNET 7 Phase and iterations Modifying needs Incep- tion Validating objectives Identifying major needs Macro-planning Analyzing and anticipating major risks Macro-estimates Macro-analysis of the architecture GO/NO GO for planning Boundaries Project organization Estimations Major needs Architecture Detailed estimates Requirements Formalizing requirements Detailed analysis, design and construction of basic architecture Implementing the project environment Reviewing plans, projections Micro-estimates Elaboration Operational solution Documentation Finish design and implementation Managing requests for changes Preparing deployment Tests Construction Deployed solution Testing and evaluation of beta version Deployment Training Transferring skills Capitalization Transi- tion

8. October 2001Project presentation REGNET 8 Risks R1: Failure to meet deadlines (major) R2: Over-ambitious specification (critical) R3: Difficulty of integration (critical) R4: Graphics interface not adapted (critical) R5: Choice of new technologies (critical) R6: Rejection by users (major) R7: Incompatibility with some of the browsers on the market (minor)