La structure du RFP UML 2.0 Divided UML 2.0 Effort into multiple RFPs Infrastructure Superstructure OCL Diagram interchange Requirements modularly separated into cohesive units to preserve architectural integrity, to facilitate distributed collaborations, and to facilitate final integration
{"Image DocumentName": "Rappel: Processus d adoption des technologies propos\u00e9e par l OMG", "Image ImageDescription": "Board Approval. DTC or PTC Recommendation. Final AB Review. Evaluation. The OMG technology adoption process is based on government-like Request for Proposal cycles: Since adopted technology must be based on commercially-available software, an RFI is issued to establish what technology will shortly be commercially available, and what requirements OMG should and could put on specifications. Then a specific RFP (with a set of requirements) is sent out. Responses comprise both a specification for perusal by the TC, and a set of terms and conditions of license, used by the Architecture Board. The AB is responsible for internal consistency of all OMG specs (existing and proposed), in the contect of business, market and technical realities. After parallel evaluation and recommendation processes within the DTC and PTC, the OMG Board of Directors makes a final decision. RFI. RFP. AB Review (Architecture Board) DTC = Domain Technical committee. PTC = Platform Technical committee. Task Force.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}