130 likes | 265 Views
Production Cycle. Objectives: Identifying key phases for building up website Understanding the major goals and activities of each production process, Defining key roles and outputs for each stage of a project. Introduction. Planning. Time: 1/3
E N D
Production Cycle Objectives: • Identifying key phases for building up website • Understanding the major goals and activities of each production process, • Defining key roles and outputs for each stage of a project
Introduction Planning • Time: 1/3 • Requirement Specifications; goals, audience... • Contracts • Design(prototyping) • Roles Production • Time: 1/6 • Develop specifications- file naming • Structure ; vertical pass, horizontal pass… • Coding • Alpha Testing • Time: 1/4 for component Testing, • 1/4 for system-wide Testing • Test the system based on the specifications • Revisions • Beta Testing • Validation Testing Publishing • To launch the project • Performance monitoring Evaluation • To evaluate the process • Documentation
Planning • Good Planning? • Achievable timelines • Clearly defined workflow • Clear roles and responsibilities • Decision-making framework
Project Manager: Role of PM • Have budgets, resources and schedules approved • Bring the production team together • Draw up contracts or similar arrangements with the people involved in the production • Understand the scope of the project and what is required • Make some initial designs
Planning- what do we do?<1> • Stakeholder meeting: • Proposal / concept brief / response to tender • Budget or project resources approved • Team Meeting: • Roles , Responsibilities • Where are the workspaces – Physical and virtual • Types of files that will be produced • File naming conventions • Standards for production, documentation and access • Guidelines for production of content • Develop a list of what will be produced
Planning- what do we do?<2> • Information Architecture Process: • Goals • Audience scenarios • Content and functions • Metaphors • Flowcharts • Layouts
Planning- output • Requirement Specifications/Design Documents • Flowcharts:Storyboard • Layout Grids
Production • To consider all the structure of pages • vertical/horizontal pass • depth of each page • navigation • HTML/graphics/scripts/etc -- Production and integration • Usability /Component Testing (alpha testing)
Testing • Testing should be based on specifications. • Whether to conform certain standards and functions • To test performance • Testing is cyclical. • To revise and bugs. • Validation • Beta Testing
Publish • To monitor performance of your system • To prepare a maintenance guide • To conduct training for the users/operators
Evaluation • To check up documentation • Thank-you letters
Requirement Specifications • Description of project/product • Including ideas and issues raised through concept briefs, preliminary meetings, information architecture process, mockup sketches, flowcharts, requirements, market research, etc. • Basis of the contractual agreement between client and developer
Contracts • Agreement between the funder /client and production team • Fee • Position • What happens if there are additional fees and costs • Tasks • Performance indicators • Reporting • Schedule (timeline) • Signatures • Responsibilities • Maintenance • Source code document • Ownership