1 / 8

Qwest Release Notification Enhancement

Qwest Release Notification Enhancement. Overview. Response to Co-Provider Industry Team request More information regarding a release sooner More formal communication regarding a release information Draft developer worksheets Disclosure document Lifecycle milestones

nigel
Download Presentation

Qwest Release Notification Enhancement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Qwest Release Notification Enhancement

  2. Overview • Response to Co-Provider Industry Team request • More information regarding a release sooner • More formal communication regarding a release information • Draft developer worksheets • Disclosure document • Lifecycle milestones • Draft and final point release notes • Enhance current CICMP Qwest Release Notification (RN) to incorporate Co-Provider Industry Team request • RNs may not apply to every OSS interface • RNs vary • Communication Mode (web page, email, fax, team meetings, etc.) • Receiver (public, current users, implementation teams, etc.) • Communicator (Training, CICMP Manager, and EDI Coordinator) • Timing (quarterly, days, months, life cycle dependent, etc.) • RN Log is CICMP web posted

  3. What are the possible RNs for an OSS interface? • Target Release Date • 12 Month Targeted OSS Interface Release Schedule • Target Release Life Cycle • Timeline -- 4 Phases • Initiate • Develop • Deploy • Retire • Co-Provider Change Request Options for a Release • For discussion at Co-Provider Industry Team Meetings • Release Baseline Candidates (i.e., release committed candidates) • For discussion at Co-Provider Industry Team Meetings • Initial set of enhancements, upgrades, and required code maintenance • Scope commitment has been made • Status updates at Co-Provider Industry Team Meetings

  4. RNs Con’t • Draft Developer Worksheets • Proposed fields and data requirements • Disclosure Document • Generic instructions • access responsibilities, hardware and software requirements, security procedures, transactions and data capabilities • Recertification Notice • Recertification requirements for moving to a new release • Disclosure Document Addendum • Changes which have occurred following a new release implementation • Release Notes Description • Description of what to anticipate in the upcoming Release Notes • Release Notes • Description of enhancements made to an upcoming interface release

  5. RNs Con’t • Point Release Notes Description • Description of what to anticipate in the upcoming Point Release Notes • Point Release Notes • Description of enhancements made to an upcoming interface point release

  6. Timing • Dependencies • Software lifecycle • Content within a release • Described as the typical number of days, weeks, or calendar months • Changes can occur

  7. IMA Matrix OSS Interface Communication Release Notification EDI/GUI/Both Method Timing Receiver Sender Target Release Date Both CICMP Web Page Quarterly Update Public CICMP Manager Target Release Life Cycle Both CICMP Web Page As soon as possible, usually 9 months prior to a target release date Public CICMP Manager Co-Provider Change Request Options for a Release Both Co-Provider Industry Team Member Email Distribution As soon as possible, usually 10 months prior to a target release date Co-Provider Industry Team CICMP Manager Release Baseline Candidates with Descriptions Both Co-Provider Industry Team Member Email Distribution During the Development phase after design (i.e., 1 week after scope commitment), usually targeted 120 days prior to a target release date Co-Provider Industry Team CICMP Manager Draft Developer Worksheets EDI As requested During the Development phase after design (i.e., 1 week after scope commitment), usually targeted 120 days prior to a target release date Current EDI Users or with an agreed upon project work plan EDI Coordinator Disclosure Document EDI Web Page Posting and CD Mailing 5 weeks prior to a target release date Public and CD dislosure document recipients EDI Coordinator Recertification Notice EDI Technical/Project Meetings and Meeting Minutes 21 days prior to a target release date Current IMA EDI Users moving to a new release EDI Coordinator Disclosure Document Addendum EDI Web Page Posting and CD Mailing As required following a target release date Public and CD dislosure document recipients EDI Coordinator Training Schedule GUI IMA Web Page Posting and fax/email/meetings 2 months prior to a target release date Current IMA GUI Users and Potential New GUI Users Training and Services Release Notes Description Both Co-Provider Industry Team Distribution Package -- CICMP Web Page 6 weeks prior to a target release date Public CICMP Manager Release Notes Both IMA/CICMP Web Page 21 days prior to a target release date Public Training and Services Point Release Notes Description Both Co-Provider Industry Team Distribution Package -- CICMP Web Page 21 days prior to a target release date Public CICMP Manager Point Release Notes Both IMA/CICMP Web Page 10 days prior to a target release date Public Training and Services

  8. Other OSS Interfaces Matrix

More Related