Guidance+notes

In small groups, devise a course/module (minimum 20 HE credits corresponding to FHEQ levels) for delivery in one of the modes supported by your institution, e.g. traditional face-to-face (F2F) or blended delivery, etc. This must include some learning technology-enhancement. The group are expected to document evidence of their development process and contribute to the course discussion fora. You can access some guidance notes and resources by clicking ** HERE ** **//As a way of starting your group off in the process of designing a curriculum, we have developed some notes that you can read through. There are also some helpful exercises and activities to spark off discussion and action. You should also draw on the materials either in Moodle for each week’s topics, or what was presented in class.//**  The aim of this assessment will be to firstly develop a course. The course can be in any area or level you wish to work on as a group. We will provide some exemplars in the moodle site over the next few weeks. The course will need to be designed using the model course specification provided ** HERE ** . This template will help you make sure that all the essential information is covered (we have also provided some guidance notes on how to fill in a course specification pro-forma ** HERE ** . This kind of document (it can vary from institution to institution, we are using the University of Greenwich one) is usually presented to a panel of experts as part of a programme or course approval process. This panel (almost always comprised of people from within and outside the university) considers the documents provided. which include course specifications. in order to dtermine whether a course /programme should be allowed to run with an institutions scope. The second part of this assessment will be a mock validation event run by a panel of experts. Your group will need to present your course specification and be subject to questioning by the panel. The aim of this assessment is to replicate the process of approving or reviewing a course within a [|higher education] institution. Normally, a validation event looks at an entire programme, and considers course/modules within the programme. We will only be 'validating' a single course, but many of the processes and questions will be the same. You may be asked about a number of the aspects of your course design, including; The panel will decide if the course you propose has been approved or not approved. The panel can also impose some conditions and requirements that need to be implemented before or during the course first intake. These include;
 * has a rationale, aims and learning outcomes at the appropriate FHEQ level and will meet the needs of students and employers, and that the structure and content are such as to enable the aims and learning outcomes to be met
 * specifies the progressive knowledge and understanding, and the intellectual, practical and transferable skills that students will acquire and that it aligns with the relevant subject benchmarks
 * makes progressively greater demands in terms of levels of analysis and synthesis, and supports the student in moving towards increasingly independent forms of study, helps students develop their research skills and employability, and where appropriate, the potential for permeating the curriculum with an international/global dimension has been realised
 * involves an appropriate range of learning and teaching strategies
 * has a clear assessment strategy and that the proposed weight and methods of assessment relate to the stated aims and outcomes of the proposal(s)
 * is in line with the University’s policies (eg on credit, assessment, equal opportunities, access, diversity, graduate attributes and employability, medium of instruction etc), and, where appropriate, those of any professional body
 * has a full statement of the regulations for admission, progression and assessment, and details of management and quality assurance arrangements
 * is likely to result in a positive student experience

The panel decides whether the proposal should be:


 * //approved with **specific conditions** that must be met **before delivery commences** (with a deadline date for meeting the conditions that fits in with Banner deadlines); and/or//
 * <span style="font-family: 'Helvetica Neue',Helvetica,Arial,sans-serif; font-size: medium;">//approved with **requirements** that must be met during the programme’s first presentation; and/or//
 * <span style="font-family: 'Helvetica Neue',Helvetica,Arial,sans-serif; font-size: medium;">//approved with **recommendations,** which are normally addressed through the periodic monitoring process; or//
 * <span style="font-family: 'Helvetica Neue',Helvetica,Arial,sans-serif; font-size: medium;">//NOT approved//.

<span style="font-family: 'Helvetica Neue',Helvetica,Arial,sans-serif; font-size: medium;">The panel for your validation event will comprise two of the teaching and two of your colleagues from a different group.