1. Pre-Production
- Concept definition
- Title goals
- Audience
- Title Genre - Doom type game, nonprofit web site, kiosk, etc.
- Marketing requirements
- Budget parameters
- Schedule requirements
- X factors
- Design
- Story/content/services
- Information architecture
- Visual and sound
- Technical
- Interaction
- Navigation
- Production plan
- Storyboarding/content outline
- Define the scope of the project--how many pages, sounds, animations, etc.
- Define the flow of the project--organization and navigation
- Out of this comes the information needed for the rest of the production plan
- Budgeting
- Production
- Content experts and other consultants
- Rights acquisition & clearance
- Testing
- Duplication or hosting of test versions
- Scheduling
- Rights acquisition & clearance
- Content production
- Content acquisition (video, text, images, etc.)
- Software engineering
- Testing
- Asset management
- Organization
- Naming conventions
- Revision management
- Backups
- Testing
- User testing
- Content testing
- Functional testing
- Staffing
- How many in-house staff
- How many contractors
- Who does what
- Payment milestones
- Documentation
- Design
- Production plan
- Assemble team
- Designer
- Producer
- Technical designer
- Art Director
- Audio producer
- Writers and editors
- Graphic artists
- Programmers/HTML coders
- Composers/sound designers/musicians
- Content specialists
- Technical assistants
- Production assistants
- Rights and researchers
- Lawyer
- Build prototype
- Test out design direction
- Prove out new technology components
- Get everyone on the same page about what the project is
- See how team works together
- Clear Rights
- Client sign-off and funding
2. Production
- Content Creation
- Graphics
- Text
- Animations
- Video
- Sound efx
- Music
- Content Processing
- Proofing
- Editing
- Assembly
- Formatting
- Compression
- Software Creation
- Authoring
- Custom software development
- Implementing the interaction behavior of title
- Implementing database and other backend services
- Integration of content and software, module by module
- Very close relationship between content and software
- One can't proceed very far without the other
- Succeeding versions of software and content passed back and forth, starting with simple placeholders
- Revise design
- Informal user testing
- Formal user testing
- Based on test results, revise design documents
- Freeze design
- Revise content and software according to final design
- Build Alpha version of complete title
- Functionality frozen, mostly complete implementation
- Integrate all modules in a complete build of title
- First testing and bug reporting for functional and content errors
- Evaluate bug reports and determine which will be fixed
- Revise software and content based on bug evaluation
- Complete remaining portions of title
- Build Beta version of complete title
- Full functionality, not fully tested
3. Post-Production
- Beta testing and bug reporting for functional and content errors
- Proof content - correct text, images, sound, credits, etc.
- Proof interaction - correct links, responses, actions
- Check for unexpected interactions - design is invariably incomplete and does not anticipate everything that can happen
- Check for crashes
- Evaluate bug reports and determine which will be fixed
- Revise software and content based on bug evaluation
- Repeat test, report, revise cycle until bugs reduced to acceptable level
- Release Golden Master to public web site or manufacturing
- Archive all production materials
- Source assets - photos, video & audio tapes, documents, etc.
- Master digital files - graphics, audio, text, video, and anything else in high resolution, editable formats
- Final assets
- Software
- Custom tools
- Documentation
- Deliver Archive & Documentation to client
- Promote site
0 komentar:
Posting Komentar