RationalUnifiedProcess Rational사에서 제시한 DevelopmentProcess Unified view * Process --> [[RUP]] * Notation --> [[UML]] * Methodology --> [[RUP]] || . |||||||| Phases || || Core process workflows || Inception || Elaboration || Construction || Transition || || Business modeling ||||||||.|| || RequirementAnalysis ||||||||.|| || ObjectOrientedAnalysis ||||||||.|| || ObjectOrientedDesign ||||||||.|| || Implementation||||||||.|| || Test||||||||.|| || Deployment||||||||.|| == Phases == 1. Inception phase * Identify all external entities with which the system will interact and define the nature of this interaction at a high level. * Identify all UseCase and describe a few significant ones 1. Elaboration phase * Analysis the problem domain * Establish a sound architectural foundation * Develop the project plan * Eliminate the highest rixk elements of the project 1. Construction phase * The software product integrated on the adequate platforms * The user manuals * A documentation of the current release 1. Transition phase * Beta testing to validate the new system against user expectations * Parallel operation with a legacy system that it is replacing * Conversion and/or migration of operational databases * Training of users and maintainers * Roll-out the product to the marketing, distribution, and sales teams == Static structure of the process == 1. Workers, the "who" * Project manager, Business Analyst, [GUI] designer, Features programmer, Chief user liaison, * Back-end programmer, System architect, Application architect, Database analyst, Information developmenr(매뉴얼개발자) * Quality assurance tester, Usability tester, Performance tester, Infrastructure coordinator, Development coordinator * System integrator, TQM engineer, RAS expert 1. Activities, the "how" * Plan an iteration, for the worker : Project manager * Find UseCase and actors, for the worker : System analyst * Review the design, for the worker : Design reviewer * Execute performance test, for the worker : Performance tester * Partition the system : Application architect * Define support and service laysers : System architect 1. Artifacts, the "what" * A model, such as the UseCase model or the design model * A model element, for example, an element within a model, such as a class, a UseCase or a subsystem * A document, such as business case or software architecture document * Source code * Excutables 1. Workflows, the "when" * Business modeling workflow * Requirements workflow * Analysis and design workflow * Implementation workflow * Test workflow * Deployment workflow