If you order your custom term paper from our custom writing service you will receive a perfectly written assignment on Technology Choices. What we need from you is to provide us with your detailed paper instructions for our experienced writers to follow all of your specific writing requirements. Specify your order details, state the exact number of pages required and our custom writing professionals will deliver the best quality Technology Choices paper right on time.
Our staff of freelance writers includes over 120 experts proficient in Technology Choices, therefore you can rest assured that your assignment will be handled by only top rated specialists. Order your Technology Choices paper at affordable prices with Live Paper Help!In developing a project that is destined for both the Internet (or Intranet) and physical media (CD/DVD/Hard Disk) it can be extremely difficult to manage version forking (multiple variants of the same project) as development requirements may vary widely between the two. Physical media typically deals with executable applications targeted for a specific platform (Windows, Macintosh, Unix) in addition to media assets prepared for disk access (high-bandwidth) and mass-storage (CD/DVD).
Historically, CD/DVD projects are built using tools such as Macromedia Director or Authorware that create executable applications for a targeted hardware platform and runtime. Media authors using these tools are required to develop their projects using a proprietary workflow, format and methodology specific to each tool and runtime. A project built in one tool cannot easily be moved (ported) to anothers runtime, let alone ported to an Internet based distribution without significant reworking and reliance on a plug-in (Shockwave, Authorware Runtime Control).
Internet development on the other hand tends to embrace standards such as XHTML, CSS and the DOM (Document Object Model) accessed via ECMAScript (JavaScript) in a standard runtime - in addition to supporting plug-in/ActiveX media objects such as Flash, QuickTime and WindowsMedia. In many cases its much easier to adapt Internet technology to physical distribution than vice-versa. By using Internet technology its possible to re-use a large portion (if not all) content created for the web within a CD distributed application. The application runtime could be a shell incorporating either a web browser or a standalone version of Macromedias web-centric Flash Player. Additionally, functionality not provided by the browser or Flash Player such as the ability to save to disk or play full-screen video, could be plugged in to the application runtime as required.
When developing SCORM compliant content destined for a LMS there is a large amount of testing required to ensure that all content adheres to the standards defined in the specifications. Having to test multiple versions of the same content based on different runtimes, and potentially using different assets could result in significant overages in the project schedule and budget. It is also conceivable that these two versions (Internet and CD-ROM based) could look and perform radically differently, causing confusion to users. Maintenance is also complicated by having to maintain two (or more) different versions of the same content using two (or more) different tool sets. Training may also be required for people unfamiliar with specific toolsespecially Director and Authorware, as both have seen a decrease in user base over the past few years given the rise of Internet technologies such as Flash.
It would be our recommendation to develop this project in a single Internet based workflow utilizing a standards compliant web browser with the Macromedia Flash plug-in and Microsoft Windows Media component/plug-in installed. These technologies could then easily be repurposed in an off-line standalone version that could be deployed via CD-ROM using a shell/wrapper application to launch the content in a manner consistent with any Windows application.
In developing a project that is destined for both the Internet (or Intranet) and physical media (CD/DVD/Hard Disk) it can be extremely difficult to manage version forking (multiple variants of the same project) as development requirements may vary widely between the two. Physical media typically deals with executable applications targeted for a specific platform (Windows, Macintosh, Unix) in addition to media assets prepared for disk access (high-bandwidth) and mass-storage (CD/DVD).
Historically, CD/DVD projects are built using tools such as Macromedia Director or Authorware that create executable applications for a targeted hardware platform and runtime. Media authors using these tools are required to develop their projects using a proprietary workflow, format and methodology specific to each tool and runtime. A project built in one tool cannot easily be moved (ported) to anothers runtime, let alone ported to an Internet based distribution without significant reworking and reliance on a plug-in (Shockwave, Authorware Runtime Control).
Internet development on the other hand tends to embrace standards such as XHTML, CSS and the DOM (Document Object Model) accessed via ECMAScript (JavaScript) in a standard runtime - in addition to supporting plug-in/ActiveX media objects such as Flash, QuickTime and WindowsMedia. In many cases its much easier to adapt Internet technology to physical distribution than vice-versa. By using Internet technology its possible to re-use a large portion (if not all) content created for the web within a CD distributed application. The application runtime could be a shell incorporating either a web browser or a standalone version of Macromedias web-centric Flash Player. Additionally, functionality not provided by the browser or Flash Player such as the ability to save to disk or play full-screen video, could be plugged in to the application runtime as required.
When developing SCORM compliant content destined for a LMS there is a large amount of testing required to ensure that all content adheres to the standards defined in the specifications. Having to test multiple versions of the same content based on different runtimes, and potentially using different assets could result in significant overages in the project schedule and budget. It is also conceivable that these two versions (Internet and CD-ROM based) could look and perform radically differently, causing confusion to users. Maintenance is also complicated by having to maintain two (or more) different versions of the same content using two (or more) different tool sets. Training may also be required for people unfamiliar with specific toolsespecially Director and Authorware, as both have seen a decrease in user base over the past few years given the rise of Internet technologies such as Flash.
It would be our recommendation to develop this project in a single Internet based workflow utilizing a standards compliant web browser with the Macromedia Flash plug-in and Microsoft Windows Media component/plug-in installed. These technologies could then easily be repurposed in an off-line standalone version that could be deployed via CD-ROM using a shell/wrapper application to launch the content in a manner consistent with any Windows application.
In developing a project that is destined for both the Internet (or Intranet) and physical media (CD/DVD/Hard Disk) it can be extremely difficult to manage version forking (multiple variants of the same project) as development requirements may vary widely between the two. Physical media typically deals with executable applications targeted for a specific platform (Windows, Macintosh, Unix) in addition to media assets prepared for disk access (high-bandwidth) and mass-storage (CD/DVD).
Historically, CD/DVD projects are built using tools such as Macromedia Director or Authorware that create executable applications for a targeted hardware platform and runtime. Media authors using these tools are required to develop their projects using a proprietary workflow, format and methodology specific to each tool and runtime. A project built in one tool cannot easily be moved (ported) to anothers runtime, let alone ported to an Internet based distribution without significant reworking and reliance on a plug-in (Shockwave, Authorware Runtime Control).
Internet development on the other hand tends to embrace standards such as XHTML, CSS and the DOM (Document Object Model) accessed via ECMAScript (JavaScript) in a standard runtime - in addition to supporting plug-in/ActiveX media objects such as Flash, QuickTime and WindowsMedia. In many cases its much easier to adapt Internet technology to physical distribution than vice-versa. By using Internet technology its possible to re-use a large portion (if not all) content created for the web within a CD distributed application. The application runtime could be a shell incorporating either a web browser or a standalone version of Macromedias web-centric Flash Player. Additionally, functionality not provided by the browser or Flash Player such as the ability to save to disk or play full-screen video, could be plugged in to the application runtime as required.
When developing SCORM compliant content destined for a LMS there is a large amount of testing required to ensure that all content adheres to the standards defined in the specifications. Having to test multiple versions of the same content based on different runtimes, and potentially using different assets could result in significant overages in the project schedule and budget. It is also conceivable that these two versions (Internet and CD-ROM based) could look and perform radically differently, causing confusion to users. Maintenance is also complicated by having to maintain two (or more) different versions of the same content using two (or more) different tool sets. Training may also be required for people unfamiliar with specific toolsespecially Director and Authorware, as both have seen a decrease in user base over the past few years given the rise of Internet technologies such as Flash.
It would be our recommendation to develop this project in a single Internet based workflow utilizing a standards compliant web browser with the Macromedia Flash plug-in and Microsoft Windows Media component/plug-in installed. These technologies could then easily be repurposed in an off-line standalone version that could be deployed via CD-ROM using a shell/wrapper application to launch the content in a manner consistent with any Windows application.
Please note that this sample paper on Technology Choices is for your review only. In order to eliminate any of the plagiarism issues, it is highly recommended that you do not use it for you own writing purposes. In case you experience difficulties with writing a well structured and accurately composed paper on Technology Choices, we are here to assist you.Your cheap custom college paper on Technology Choices will be written from scratch, so you do not have to worry about its originality.
Order your authentic assignment from Live Paper Help and you will be amazed at how easy it is to complete a quality custom paper within the shortest time possible!
