--- title: "Multimedia application development life cycle" subject: "Multimedia System" chapter: 1 key: "semester_8/multimedia_system:app-development-life-cycle" source: https://www.bctengineer.com/q/semester_8/multimedia_system/app-development-life-cycle site: BCT Engineering --- # Multimedia application development life cycle Multimedia System · Chapter 1: Introduction - Asked in: 2076 Bhadra, 9 marks; 2074 Bhadra, 3+6 marks; 2073 Bhadra, 9 marks; 2075 Bhadra, 4 marks (asked 4 times) - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_8/multimedia_system/app-development-life-cycle - Whole chapter: https://www.bctengineer.com/md/semester_8/multimedia_system/chapter-1 ## Question Explain the life cycle (stages/phases) of multimedia application development with an example. ## Short answer The life cycle has seven iterative phases: conceptualisation/analysis, design, content collection and creation, authoring, testing, delivery, and maintenance. For example, an interactive "Learn Nepali History" CD moves from storyboard and media creation to Flash authoring, testing, and delivery. ## Answer A multimedia application development life cycle is the ordered set of phases a team follows to take a multimedia product from an initial idea to a delivered, maintained product. It is similar to the software life cycle, but it has an extra stage for collecting and creating media content (text, audio, images, video, animation). ```text Conceptualisation / Analysis | Design <-------------+ | | Content collection & creation | feedback | | Authoring / Implementation | | | Testing -------------+ | Delivery (CD, web, kiosk) | Maintenance ``` #### Phases 1. **Conceptualisation and analysis.** Identify the need, the target audience, the purpose (teach, inform, sell, entertain), the platform, budget, time and team. Output: a project proposal and a feasibility study. 2. **Design.** Decide the content outline, navigation structure and look and feel. Typical outputs are a flowchart of screens, a **storyboard** (sketch of each screen with media and interaction), a script, and the interface design (menus, buttons, colour, fonts). 3. **Content collection and creation.** Gather or produce all media elements: write text, record and edit audio, shoot video, scan or draw images, build animations. Convert them to suitable formats and compress them. 4. **Authoring (implementation).** Integrate the media into a single product with an authoring tool (Adobe Director, Flash/Animate, Authorware, Toolbook) or a programming language. Links, timing, synchronisation and interactivity are added here. 5. **Testing.** Check that the product works as specified: functionality, links, media quality, synchronisation, speed, and compatibility on target machines. Usability tests with real users are done. Errors send the team back to design or authoring. 6. **Delivery.** Package and release the product on CD/DVD, web server, kiosk or mobile app, with an installer and user guide. 7. **Maintenance and evaluation.** Fix errors, update content and release new versions based on user feedback. #### Example: an interactive "Learn Nepali History" CD - Concept: a CD for school students, covering kings and events with pictures and narration. - Design: storyboard of each chapter screen, main menu with timeline navigation. - Content: scan old photographs, record narration in a studio, draw maps, make short animations of battles. - Authoring: assemble in Flash/Director with a Next/Back button and quiz at the end of each chapter. - Testing: run on Windows machines in a lab, check audio-video sync and quiz scoring. - Delivery: master CD with an auto-run installer; Maintenance: update the content for the next syllabus. #### Key points of the cycle - The process is **iterative**: problems found in testing or reviews send the team back to design or content creation, so phases overlap. - **Documents produced** at each stage (proposal, storyboard, flowchart, media asset list, test report) allow the client to approve work before the next stage, which controls cost. - **Team roles:** project manager, content/subject expert, instructional or graphic designer, audio and video producers, programmer/author and tester. - **Prototyping:** a small working sample of the main screens is often built after design so the client can judge the look and navigation early. - **Documentation and user help** are prepared before delivery, with a readme and installation guide. - **Risk areas:** copyright of media, file size against storage or bandwidth, and playback differences between computers. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. How does the multimedia development life cycle differ from the ordinary software life cycle? A. It has no testing stage B. It has an extra stage for collecting and creating media content C. It has no design stage D. It is not iterative Answer: B. The multimedia cycle adds a content collection and creation stage for text, audio, images, video and animation. (Key point: Extra stage in the life cycle) 2. Which output of the design phase is a sketch of each screen showing its media and interaction? A. Feasibility study B. Test report C. Storyboard D. Installer Answer: C. A storyboard sketches every screen with its media and interaction; it is a typical design-phase output. (Key point: Storyboard in design) 3. What happens in the authoring (implementation) phase? A. Media is integrated into one product using an authoring tool, adding links, timing, synchronisation and interactivity B. The target audience and budget are identified C. Narration is recorded in a studio D. The CD is packaged with an installer Answer: A. Authoring tools such as Director or Flash assemble the media and add links, timing, synchronisation and interactivity. (Key point: Authoring phase) 4. If errors are found during testing, what does the life cycle expect the team to do? A. Release the product anyway and fix it in maintenance only B. Go back to design or authoring to fix them C. Restart from the delivery stage D. Skip the remaining phases Answer: B. The process is iterative: problems found in testing send the team back to design or authoring. (Key point: Iterative nature) ## Related in Multimedia System - [Application, system and device domain](https://www.bctengineer.com/question.md?key=semester_8%2Fmultimedia_system%3Aapplication-system-device-domain) — Multimedia System, chapter 1 - [CMYK colour model and application](https://www.bctengineer.com/question.md?key=semester_8%2Fmultimedia_system%3Acmyk-colour-model) — Multimedia System, chapter 3 ## Related in other subjects - [Project development life cycle phases](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Aproject-development-life-cycle) — ICT Project Management, chapter 1 - [Project life cycle phases and activities](https://www.bctengineer.com/question.md?key=semester_7%2Fproject_engineering%3Alife-cycle-phases-activities) — Project Engineering, chapter 1, asked 5× - [Scope of CM and project life cycle phases](https://www.bctengineer.com/question.md?key=semester_8%2Fconstruction_management%3Ascope-lifecycle-phases) — Construction Management, chapter 1, asked 4× - [Stages of hydropower development cycle](https://www.bctengineer.com/question.md?key=semester_7%2Fhydropower_engineering%3Adev-cycle-stages) — Hydropower Engineering, chapter 2