GCE APPLIED ICT A2 COURSEWORK TIPS

Transcription

1 GCE APPLIED ICT A2 COURSEWORK TIPS

2 COURSEWORK TIPS A2 GCE APPLIED ICT If you are studying for the six-unit GCE Single Award or the twelve-unit Double Award, then you may study some of the following coursework units: A2 UNIT 8 DATABASE DEVELOPMENT A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT A2 UNIT 10 MULTIMEDIA TECHNOLOGY A2 UNIT 11 APPLICATION SOFTWARE DEVELOPMENT A2 UNIT 12 VISUAL PROGRAMMING A2 UNIT 14 IMPLEMENTING a BUSINESS SOLUTION This booklet will give you advice on preparing for these A2 coursework units.

3 A2 UNIT 8 DATABASE DEVELOPMENT This unit is meant to demonstrate your understanding of the importance of database technology and develop database skills. It will show your knowledge of database technology and modelling concepts. You will need to demonstrate skills such as normalisation to 3NF, relational database structures, querying databases and the development of a relational database model. You will have to design, implement, test and document a database solution to a problem of your choice. You must show evidence of project management skills. The documentation you present in your portfolio should have a professional feel to it and should demonstrate an appropriate style for work at this level. YOUR COURSEWORK PORTFOLIO SHOULD BE BOUND APPROPRIATELY. A2 UNIT 8 DATABASE DEVELOPMENT

4 In this Unit you must produce a working relational database system which you have designed to meet your user s specified requirements. It is strongly recommended that your portfolio should be presented using the following format and headings: Candidate Record Sheet This document should be signed by both you and your teacher. Contents Page If you choose to include a contents page with accurate page numbers it will significantly enhance your work. It will demonstrate a style commonly found in reports of this nature. Working database system The project should begin by you giving an in depth description of the current system as it exists. This should set the scene for the work that is to follow. Before you can build a new system, you must thoroughly understand how the current system works. This section should describe in detail what the current system does and what problems it contains. (It is possible to show this using DFD (symbols are listed on Page 84 of the specification) which display the context and overviews of the current system.) Users Needs Based on your investigation of the current system, a clear statement of users needs should be listed. As far as possible these should be quantitative. Examples of users needs: The system should produce a report for all customers who are more that 60 days overdue in their payments. The system should be able to list all customers who live in Lisburn and are under 21 years of age. The system should list all the appointments for all employees for each working day. The system should allow new users details to be entered. It will be possible to find out a complete customer order history from this system. It will be possible to find out details of an order if an order code is input A2 UNIT 8 DATABASE DEVELOPMENT

5 Examples of user s needs that should avoided include: The system will be fast The system will find a record in 10 seconds The system will be user friendly The system will use macros to print out reports The system will use complex queries to. The system will use tables to hold data or similar non-quantitative objectives or objectives that use technical language. Remember these objectives are a wish list of what the user wants and so should be expressed in non-technical lay-persons language. The reason for producing the users requirements in a quantitative list is that it will allow, in the evaluation section (later), you to comment on whether the requirements were met (or not). Project Plan This is a plan that you should set out at the beginning of your work. It will be a programme of activities and resources you will use within a timeframe over the life time of the project design. You should use a recognised project management tool to document this. An example of a project management tool would be a GANTT chart (examples of GANTT charts can be found on the exemplar paper 7 Investigating Systems (a synoptic unit)). See CCEA website at rtdocs/appliedict_unit7_exemplar_paper.pdf Other Gantt chart examples can be found at: It is also possible to use EXCEL as a project management tool see A2 UNIT 8 DATABASE DEVELOPMENT

6 Design specification This section of your report should show bottom up data modelling activities you have carried out to produce your database design. Data Normalisation This will include listing all your data and applying a bottom up process known as data normalisation. You should apply the normalisation process up to 3NF only. See Entity Relationship modelling This section of your report should show top down data modelling activities you have carried out to produce your database design. See It is important to emphasise here that you must develop and name your entities and also name the relationships between them. Both of these activities are known as logical design models. These data modelling processes are used to produce the same physical model i.e. a model that will include tables and relationships. Output Design This section will include the design of your final physical model. Processes This section will include the processes that your system will use to achieve the user requirements. It will describe how data is manipulated to produce output. Implementation This is final evidence that your system has been finished and is working. You will need to produce annotated screen dumps of your application i.e. screen dumps on which you describe what is going on. Only code you have written yourself should be annotated and included. (Please do NOT include pages of code which has been produced by the code generator!) A2 UNIT 8 DATABASE DEVELOPMENT

7 User Documentation This is a separate document which you will produce for a naïve user to allow them to use the system. This naïve user will be assumed to have no knowledge of your system. This naïve user should NOT be able to amend or have access to raw data. For some advice on this see You must also provide evidence that THREE users have tested your system using your user guide. You must also evaluate how your system meets its original objectives. This could be evidenced by a signed questionnaire. Technical Documentation This is a separate document which you will produce to allow a TECHNICAL user to maintain or upgrade the system. Technical Documentation is written for people will maintain the system once it is installed and being used. Remember - All systems evolve. This means that the user will need the system to do things better, faster or even in a different way. Some things may have even been overlooked or forgotten. The user will only realise that improvements need to be made once they start using the system. Maintaining the system means keeping it running well and doing what the user needs it to do. Technical guides may use technical language and system diagrams if they are needed. Examine A technical Guide may include the following: Technical details such as the type of system being used technical details such as type of computer system, RAM, printer etc. Explanations may include o how to load the software, upgrade a sub-system, make a user interface, add fields, validate and verify data, amend the database structure, fault find etc. o How to produce a query or report. o How to edit a macro or change some code. You may also put in a FAQ section or contact details ( support address, web site support address, telephone support line numbers.) A2 UNIT 8 DATABASE DEVELOPMENT

8 You must also provide evidence that THREE users have tested your system using your technical guide. You must also evaluate how your system meets its original objectives. This could be evidenced by a signed questionnaire. Test Documentation You should provide a comprehensive test plan with evidence that testing has been carried out. Test plans should include evidence of: Navigation Data capture Data manipulation Data output Reports produced Evaluation This section is where you describe your solution and reflect on how it meets the quantitative user requirements specified at the beginning. It should comment on the data modelling and this section should also report on future improvements. You must also mention how your time management skills were used as well as the interaction between yourself and the user while you developed your data models. There should be evidence of discussion of your project plan and the use of project management tools. Statements such as My user wanted the following requirements (the list). which is then followed by an in depth discussion of these requirements is good practice. Remember it may not have been possible to satisfy all users requirements why? maybe this something for future consideration? You should concentrate on your initial project management plan did everything go according to plan do you deliver when you said you would? if not? - why not? did things take longer than expected? why? were there any unforeseen events that slowed the project? what were they and how did you cope or catch up? You should reflect on the future of the project are there any enhancements that you could add later give reasons for them. Statements such as I thought I did well. There were no real problems at all should be avoided it is unrealistic to expect everything to run smoothly. Statements such as Everything was fine, but if I had to do it again I d do it differently should also be avoided. It s contradictory. A2 UNIT 8 DATABASE DEVELOPMENT

9 A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT This unit allows you to demonstrate your skills in developing and designing websites using appropriate tools. You will demonstrate your knowledge about performance issues, how you ve used a range of media and how you have developed interactive features. You should show evidence of advanced and or dynamic content on both your website presentation and management. You should show evidence of developing, testing, documenting, maintaining and evaluating websites. You should show evidence of project management techniques. The documentation you present in your portfolio should have a professional feel to it and should demonstrate an appropriate style for work at this level. YOUR COURSEWORK PORTFOLIO SHOULD BE BOUND APPROPRIATELY. A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT

10 In this Unit you must produce a project plan that describes how you will manage your time and resources and how you will schedule the activities involved. A professional website that fully meets the needs of client - a business or official organisation. It is strongly recommended that your portfolio should be presented using the following format and headings: Candidate Record Sheet This document should be signed by both you and your teacher. Contents Page If you choose to include a contents page with accurate page numbers it will significantly enhance your work. It will demonstrate a style commonly found in reports of this nature. Feasibility of the project There should be a detailed investigation of the clients current business and you should investigate your clients requirements for the website. It is important to discuss these requirements thoroughly and present the client with a well presented written outline. This outline should include a portfolio of ideas and an outline of site structure, making reference to timescale and financial costs. You must remember that the client will consider you to be the expert so it is essential you provide technical information such as domain and hosting issues in an easy to understand format. Storyboarding is evidence of good practice. This site should include advanced content such as dynamic scripting or media and be suitable for the audience concerned. This task will give you experience of planning a website implementation for a client as well as looking at methods that allow the site to be managed directly by the client. A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT

11 Project Plan This is a plan that you should set out at the beginning of your work. It will be a programme of activities and resources you will use within a timeframe over the life time of the project design. You should use a recognised project management tool to document this. An example of a project management tool would be a GANTT chart (examples of GANTT charts can be found on the exemplar paper 7 Investigating Systems (a synoptic unit)). See CCEA website at rtdocs/appliedict_unit7_exemplar_paper.pdf Other Gantt chart examples can be found at: It is also possible to use EXCEL as a project management tool see A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT

12 Site specification The site specification should include the following sections: Audience considerations. Domain Name and Hosting Issues Site Management Issues Site Structure Ideas Dynamic content requirements (e.g. scripted content) Dynamic content is content generated by some server process e.g. a list of web sites matching the search criteria on a search engine site, the content of a shopping cart on an e-commerce site, a personalized news page, a message on a bulletin board or the result of a database query. Before it is sent to the browser, the dynamic content needs to be combined with regular HTML elements into a page with the right layout, navigation bars, the company logo etc. Use of and embedding of media content such as animation / movies. Content Requirements from client Accessibility Issues Legal Issues (Data Protection Act if applicable) Site scalability proposals Financial Issues Timescales Each page on the site should be described to show evidence of: Webpage screen shot Fonts / styles and colours used. Meta tags used and why they were employed. Navigation Issues. Use of text layout tools such as layers, tables or frames Use of images and if applicable how they were created. Use of multimedia and if applicable how created and embedded to page. Downloadable content. Advanced content Accessibility issues considered. Some other issues that need to be addressed in your portfolio include: Auditing issues Web hosting Your website must be hosted. A2 UNIT 9 WEBSITE DESIGN AND MANAGEMENT

13 A2 UNIT 10 MULTIMEDIA TECHNOLOGY This unit is meant to demonstrate your understanding of the importance of multimedia technology and the use hardware and software in your given context. You must evidence of the design, description and presentation of a multimedia solution using a range of techniques including animation and video. You must show evidence of project management skills in your portfolio. The documentation you present in your portfolio should have a professional feel to it and should demonstrate an appropriate style for work at this level. YOUR COURSEWORK PORTFOLIO SHOULD BE BOUND APPROPRIATELY. A2 UNIT 10 MULTIMEDIA TECHNOLOGY

14 In this Unit you must produce an interactive multimedia presentation including one piece of video or animation which includes a piece of edited audio supported by design sketches, storyboards and flow charts to meet your user s specified requirements. It is strongly recommended that your portfolio should be presented using the following format and headings: Candidate Record Sheet This document should be signed by both you and your teacher. Contents Page If you choose to include a contents page with accurate page numbers it will significantly enhance your work. It will demonstrate a style commonly found in reports of this nature. Project Plan This is a plan that you should set out at the beginning of your work. It will be a programme of activities and resources you will use within a timeframe over the life time of the project design. You should use a recognised project management tool to document this. An example of a project management tool would be a GANTT chart (examples of GANTT charts can be found on the exemplar paper 7 Investigating Systems (a synoptic unit)). See CCEA website at rtdocs/appliedict_unit7_exemplar_paper.pdf Other Gantt chart examples can be found at: It is also possible to use EXCEL as a project management tool see A2 UNIT 10 MULTIMEDIA TECHNOLOGY

15 Multimedia Portfolio Presentation The multimedia presentation should ensure all information is presented in a structured, coherent, concise manner showing continuity. It should demonstrate the proper use of technical language showing an understanding of the design and production process. It should present a detailed analysis of the production task. Your portfolio should demonstrate that you know: How digital technology works What hardware and software to use in multimedia projects How to design a multimedia project The standard techniques used to create multimedia content How to present multimedia content What are the standard ways of working This unit will allow you to demonstrate team work. Each member of the team should be actively involved in the design and production process. You, as a team member, should be fully aware of what all other members of the team are producing for the multimedia project. Each team member must be responsible, at some time, of leading and directing the team. Each team member must produce their own distinct portfolio. A2 UNIT 10 MULTIMEDIA TECHNOLOGY

16 A2 UNIT 11 APPLICATION SOFTWARE DEVELOPMENT This unit is meant to demonstrate your understanding of the importance of an e-portfolio, which you will design to support business functions in a given context. You must show evidence of how you used research, selection, evaluation and use of advanced features of software. You must show evidence of your understanding of the issues involved in the choice of software. A2 UNIT 11 APPLICATION SOFTWARE DEVELOPMENT

17 In this Unit you must produce an e-portfolio containing evidence of A digital training resource which will help a new member of an organisation understand the vision, aims and structure of an organisation. An automated database containing data that can be used by a spreadsheet and word processor. A digital briefing resource that explains e-communication tools. A two page document (or 2 minute video) evaluating your own performance. A2 UNIT 11 APPLICATION SOFTWARE DEVELOPMENT

18 A2 UNIT 12 VISUAL PROGRAMMING In this unit you were introduced to the fundamental concepts of modern programming in a visual language. You must show evidence that you have undertaken tasks in which you designed and created programmes (event driven in nature) prototyped applications using storyboarding as a design tool interacted with your user used procedures and functions developed a user interface design and utilised the software to produce GUI applications. You will develop a single application or undertake a set of tasks to design a set of GUI applications which meet a set of user requirements. You will be required to examine and apply standard ways of working in this context. The documentation you present in your portfolio should have a professional feel to it and should demonstrate an appropriate style for work at this level. YOUR COURSEWORK PORTFOLIO SHOULD BE BOUND APPROPRIATELY. A2 UNIT 12 VISUAL PROGRAMMING

19 WHAT YOU NEED TO DEMONSTRATE. Your portfolio should demonstrate that you know: How to design a visual interface; How to develop a prototype through storyboarding; How to use tools for building a GUI application; How to package and distribute a system; The importance of testing your user specified system; Technical and user documentation requirements; How to evaluate a user specified system; What the standard ways of working are. A2 UNIT 12 VISUAL PROGRAMMING

20 In this Unit you must produce a working system which has been designed to meet your user s specified requirements. It should be produced using a visual programming tool. It is strongly recommended that your portfolio should be presented using the following format and headings: Candidate Record Sheet This document should be signed by both you and your teacher. Contents Page If you choose to include a contents page with accurate page numbers it will significantly enhance your work. It will demonstrate a style commonly found in reports of this nature. Introduction This section must describe the current system in detail and the requirements for the new system. Project Plan This is a plan that you should set out at the beginning of your work. It will be a programme of activities and resources you will use within a timeframe over the life time of the project design. You should use a recognised project management tool to document this. An example of a project management tool would be a GANTT chart (examples of GANTT charts can be found on the exemplar paper 7 Investigating Systems (a synoptic unit)). See CCEA website at rtdocs/appliedict_unit7_exemplar_paper.pdf Other Gantt chart examples can be found at: It is also possible to use EXCEL as a project management tool see Design Documentation You must use storyboarding and state the data requirements and output to be produced by your system. You should use detailed sketches/ storyboards to present a graphical representation of the proposed system. The storyboards should include relevant controls e.g. labels, text boxes, list/combo boxes, images, menus and toolbars. Navigation through the system should also be represented. Along with the actual storyboards, details of the modular design of the programs should be explained. A2 UNIT 12 VISUAL PROGRAMMING

21 Implementation You must show evidence of your implementation by including annotated screen dumps and code listings of the system you have built. This should be generated from user requirements. The initial prototype should only provide a snapshot of the proposed system, giving a flavour of the screens, navigation, controls used and output screens. The refinement of the prototyping should be carried as necessary taking into account user feedback each time. Forms should be fit for purpose, professional, original, intuitive, consistent and employ a variety of text, menus, controls and graphics. There should be evidence of e.g. combo box, scroll bar, list box, graphics, check box etc. Processing and Code - students should use appropriate programming structures e.g. Sequence, Selection and Repetition, Case statements, For to Next, and Nested If statements. A number of user-defined modules should be evident. The entire code should be printed out in full. Use of control arrays can reduce the amount of code keyed in. Processing and Printouts The programs produced should contain validation of controls, menus etc.. User Documentation This is a separate document which you will produce for a naïve user to allow them to use the system. The User Guide should be a separate document and have a title page and table of contents This naïve user will be assumed to have no knowledge of your system. This naïve user should NOT be able to amend or have access to raw data. For some advice on this see You must also provide evidence that THREE users have tested your system using your user guide. You must also evaluate how your system meets its original objectives. This could be evidenced by a signed questionnaire. A2 UNIT 12 VISUAL PROGRAMMING

22 Technical Documentation This is a separate document which you will produce to allow a TECHNICAL user to maintain or upgrade the system. Technical Documentation is written for people will maintain the system once it is installed and being used. Remember - All systems evolve. This means that the user will need the system to do things better, faster or even in a different way. Some things may have even been overlooked or forgotten. The user will only realise that improvements need to be made once they start using the system. Maintaining the system means keeping it running well and doing what the user needs it to do. Technical guides may use technical language and system diagrams if they are needed. Examine A technical Guide may include the following: Technical details such as the type of system being used technical details such as type of computer system, RAM, printer etc. Explanations may include o how to load the software, upgrade a sub-system, make a user interface, add fields, validate and verify data, amend the database structure, fault find etc. o How to produce a query or report. o How to edit a macro or change some code. You may also put in a FAQ section or contact details ( support address, web site support address, telephone support line numbers.) You must also provide evidence that THREE users have tested your system using your technical guide. You must also evaluate how your system meets its original objectives. This could be evidenced by a signed questionnaire. Test Documentation You should provide a comprehensive test plan with evidence that testing has been carried out. Test plans should include evidence of: Navigation Data capture Data manipulation Data output Reports produced A2 UNIT 12 VISUAL PROGRAMMING

23 Evaluation This section is where you describe your solution and reflect on how it meets the quantitative user requirements specified at the beginning. It should comment on the effectiveness of the use of prototyping and this section should also report your recommendations for future improvements. You must also mention how your time management skills were used as well as the interaction between yourself and the user during prototyping when extracting and refining your user s requirements. You should also discuss how your performance could be improved. You should concentrate on your initial project management plan did everything go according to plan do you deliver when you said you would? if not? - why not? did things take longer than expected? why? were there any unforeseen events that slowed the project? what were they and how did you cope or catch up? You should reflect on the usefulness of the prototyping approach to system development. You should reflect on the future of the project are there any enhancements that you could add later give reasons for them. Statements such as I thought I did well. There were no real problems at all should be avoided it is unrealistic to expect everything to run smoothly. Statements such as Everything was fine, but if I had to do it again I d do it differently should also be avoided. It s a contradiction in terms. A2 UNIT 12 VISUAL PROGRAMMING

24 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION This unit allows you to develop a software system from a User Requirements Specification. You will design, develop, test, document and evaluate a software solution to a specified problem. You will be required to demonstrate project management skills and to appreciate all aspects of the systems development life cycle. You will be required to develop a software solution to a business problem taking into consideration the needs of the end user. You will be required to explore and select appropriate design methods. You will be required to develop, test, document and demonstrate your solution. You will examine and apply standard ways of working in this context. A2 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION

25 WHAT YOU NEED TO DEMONSTRATE. Your portfolio should demonstrate that you know: How to use appropriate design methods to develop a software system to meet user requirements How to develop a functional software system from the design specification using a recognised development tool How to test the developed system How to produce the documentation How to evaluate the final system in terms of the User requirements What are the standard ways of working A2 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION

26 In this Unit you must design, develop, test, document and evaluate a software solution to a given problem. It is strongly recommended that your portfolio should be presented using the following format and headings: Candidate Record Sheet This document should be signed by both you and your teacher. Contents Page If you choose to include a contents page with accurate page numbers it will significantly enhance your work. It will demonstrate a style commonly found in reports of this nature. Project Plan This is a plan that you should set out at the beginning of your work. It will be a programme of activities and resources you will use within a timeframe over the life time of the project design. You should use a recognised project management tool to document this. An example of a project management tool would be a GANTT chart (examples of GANTT charts can be found on the exemplar paper 7 Investigating Systems (a synoptic unit)). See CCEA website at rtdocs/appliedict_unit7_exemplar_paper.pdf Other Gantt chart examples can be found at: It is also possible to use EXCEL as a project management tool see Introduction This section must describe the current system in detail and the requirements for the new system. Design The choice of design method applied to the development of a software system will reflect the nature of the problem under consideration. You must always consider the needs of the User and choose a design method that will help you to interact in an appropriate manner with the user of your developed system. You must show evidence that you understand how a range of design methods available e.g. Algorithms, Storyboards, Data flow diagrams, Data dictionaries can be applied in the development of a software solution. You should produce a specification of user requirements. A2 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION

27 Implementation Based on the specification of user requirements you must produce your solution, suitably annotated. Testing You must should detailed evidence that you understand the importance of software testing. You must document: - How you have tested the functionality of a system; - How you have tested the User interface; - How you have tested the original specification against the final product; - How you have produced a test plan for a developed system; User Documentation This is a separate document which you will produce for a naïve user to allow them to use the system. The User Guide should be a separate document and have a title page and table of contents This naïve user will be assumed to have no knowledge of your system. This naïve user should NOT be able to amend or have access to raw data. For some advice on this see You must also provide evidence that THREE users have tested your system using your user guide. You must also evaluate how your system meets its original objectives. This could be evidenced by a signed questionnaire. A2 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION

28 Technical Documentation This is a separate document which you will produce to allow a TECHNICAL user to maintain or upgrade the system. Technical Documentation is written for people will maintain the system once it is installed and being used. Remember - All systems evolve. This means that the user will need the system to do things better, faster or even in a different way. Some things may have even been overlooked or forgotten. The user will only realise that improvements need to be made once they start using the system. Maintaining the system means keeping it running well and doing what the user needs it to do. Technical guides may use technical language and system diagrams if they are needed. Examine A technical Guide may include the following: Technical details such as the type of system being used technical details such as type of computer system, RAM, printer etc. Explanations may include o how to load the software, upgrade a sub-system, make a user interface, add fields, validate and verify data, amend the database structure, fault find etc. o How to produce a query or report. o How to edit a macro or change some code. You may also put in a FAQ section or contact details ( support address, web site support address, telephone support line numbers.) Evaluation Your final system must discuss how you have met the User s Requirements. You must also mention how your time management skills were used You should concentrate on your initial project management plan did everything go according to plan do you deliver when you said you would? if not? - why not? did things take longer than expected? why? were there any unforeseen events that slowed the project? what were they and how did you cope or catch up? You should discuss the relative success or failure of your final product. You must include detailed analysis of results, conclusions and recommendations. You must comment on how your own performance could be improved. A2 UNIT 14 IMPLEMENTING A BUSINESS SOLUTION