BSc Computing Ordinary Top-Up Prog Doc (Mar 12)

8/13/2019 BSc Computing Ordinary Top-Up Prog Doc (Mar 12)

1/38

School of Computingand Mathematical Sciences

BSc Computing (Stage 3)

Programme Document

March 2012


2/38

BSc Computing Programme Document March 2012

2

Table of Contents

1 INTRODUCTION .............................................................. ........................................................... 4

2 PROGRAMME SPECIFICATION ...................................................... ...................................... 4

3 PROGRAMME STRUCTURE AND OVERVIEW ............................ ...................................... 4

4 DELIVERY OF THE PROGRAMME ............................................................ ........................... 5

5 COHORTS AND ASSESSMENT POINTS ................................................................ ................ 5

6 ENTRY QUALIFICATIONS ........................................................................... ........................... 5

6.1 STANDARD E NTRY QUALIFICATIONS .......................................................................... ................ 5 6.2 NON-STANDARD QUALIFICATIONS .................................................................. ........................... 5 6.3 LEVEL OF E NGLISH ............................................................................... ...................................... 6

7 ADMISSIONS PROCEDURE ..................................................................................... ................ 6

7.1 COLLABORATIONS ADMISSIONS PANEL ...................................................................................... 6 7.2 M INIMUM AGE ...................................................... ................................................................. ..... 6

8 SCHOOL ADMINISTRATION OF THE PROGRAMME ...................................................... 6

R OLES AND R ESPONSIBILITIES .............................................................. ................................................ 7 8.1.1 Director for International Collaborations ........................................................ ................ 7 8.1.2 CMS Regional Link Tutor ........................................................... ...................................... 7 8.1.3 CMS Collaborations Officer ....................................................... ...................................... 7

9 RESPONSIBILITIES OF APPROVED CENTRES .................................................................. 7

10 TAUGHT REGULATIONS AND APPEALS ............................................................................ 8

11 TEACHING AND ASSESSMENT STRATEGY ................................................................ ....... 8

11.1 ASSESSMENT ..................................................................................................................... ..... 9

12 ASSESSMENT PROCEDURE .................................................................................... ................ 9

12.1 EXAMINATION BOARDS .......................................................... ................................................ 9

13 LEARNER RESOURCES ............................................................ ................................................ 9

13.1 LEARNER RESOURCE MATERIALS ................................................................ ........................... 9 13.2 O N-LINE LECTURE MATERIALS ............................................................................................. 10 13.3 ADDITIONAL LEARNER RESOURCES ...................................................................................... 10 13.4 OFF-CAMPUS SERVICES CONTACT AND R EMOTE SUPPORT (OSCARS) ............................... 10

14 DEALING WITH STUDENT QUERIES ........................................................ ......................... 10 14.1 QUERIES RELATED TO THE TOP -UP PROGRAMME .................................................................. 10 14.2 QUERIES CONCERNING U NIVERSITY SERVICES ..................................................................... 11

15 INFORMATION FOR STAFF AND STUDENTS ............................................................... ... 11

15.1 WEB SITE FOR COLLABORATIONS ........................................................................................ 11 15.2 ELECTRONIC FORUMS ................................................................................. ......................... 11

16 CMS SCHOOL QA VISITS TO APPROVED CENTRES ..................................................... 11

17 OBTAINING STUDENT FEEDBACK ........................................................... ......................... 11

18 FEEDBACK ON ASSESSMENT .......................................................... .................................... 12

18.1 FEEDBACK TO TUTORS AT APPROVED CENTRES .................................................................... 12


3/38


3

18.2 FEEDBACK TO STUDENTS ................................................................................................ ..... 12

19 EXTERNAL EXAMINERS ....................................................................................................... 12

20 QAA SUBJECT BENCHMARKS ......................................................... .................................... 12

20.1 BENCHMARKING STANDARDS .............................................................................................. 13

20.1.1 Threshold level .................................................................... .................................... 13 20.1.2 Typical level ............................................................................................................. 13 20.1.3 Excellence .......................................................................................................... ...... 14

21 APPENDIX A - PROGRAMME SPECIFICATION ............................................................ ... 15

22 APPENDIX B - COURSE SPECIFICATIONS .......................................................... .............. 20

22.1 COURSE TITLE : SOFTWARE E NGINEERING .................................................. ......................... 21 22.2 COURSE TITLE : DATABASE DESIGN & IMPLEMENTATION ..................................................... 24 22.3 COURSE TITLE : DISTRIBUTED I NFORMATION SYSTEMS ........................................................ 27 22.4 COURSE TITLE : I NFORMATION SYSTEMS E NGINEERING ....................................................... 30 22.5 COURSE TITLE : IT PROJECT AND QUALITY MANAGEMENT .................................................. 33 22.6 COURSE TITLE : APPLICATION DEVELOPMENT FOR MOBILE DEVICES .................................. 35 22.7 COURSE TITLE : SYSTEMS PROGRAMMING .............................................................. .............. 37


4/38


4

1 Introduction

The BSc Computing (Stage 3) is an Ordinary Degree top-up programme developedfor delivery at FPT University in Vietnam. The programme consists of 60 credits atlevel 5 and 60 credits at level 6. The programme was designed as a top-up degree forstudents studying the APTECH Higher Diploma in Software Engineering at FPTAPTECH centres across Vietnam. The APTECH HDSE is rated as being equivalent tolevel 4 / level 5 which makes it unsuitable as a qualification for direct entry onto anhonours top-up degree. Although there was an option for FPT to offer the APTECHAdvanced Diploma in Software Engineering as a further year following on from theHDSE, the view was that students in Vietnam prefer to join a degree programmefollowing the HDSE and degree programmes in Vietnam (and also in Australasianuniversities) are normally three year degrees and are equivalent to a UK OrdinaryDegree. The decision to offer an ordinary Degree was therefore determined by the

prevailing market forces in Vietnam at that time.

2 Programme Specification

The programme specification is given in Appendix A.

3 Programme Structure and Overview

Level 6 Level 5

COMP1303Distributed Information Systems

(15 credits)

COMP1564Systems Programming

(15 credits)

COMP1304Information Systems Engineering

(15 credits)COMP1158

Software Engineering(30 credits)COMP1305

IT Project & Quality Management(15 credits)

COMP1302

Database Design & Implementation(15 credits)

COMP1550

Application Development forMobile Devices

(15 credits)

The level 5 and level 6 courses are validated courses on the BSc (Hons) Computingwhich has been offered in the School of Computing and Mathematical Sciences since1993. In 1998, in response to the demand from holders of Higher and AdvancedDiplomas in Computing and IT, it was decided to extend the delivery of the final yearto both on-campus and off-campus students.

The programme aims to be in-line with recent developments in computing and the


5/38


5

current market trends with requirements for new technologies and web-basedapplications in particular.

4 Delivery of the Programme

The normal duration of the programme is one academic year for full-time mode andtwo academic years for part-time mode. The School will agree an appropriate deliverystructure with each Centre, as well as the number of student intakes allowed eachyear. As a norm, it is expected that Centres will run a balanced number of coursesover the semesters in which the programme runs, and that students will be introducedto the project course at a point in the programme early enough to allow themsufficient time to prepare for their project.

5 Cohorts and Assessment Points

Each of the courses on the Ordinary degree programme is studied in a single semester.In order to allow centres to be flexible with their recruitment and programme delivery,there are two assessments points in the year, one in May/June and one in

November/December. Correspondingly, centres would have one or two intakes a yearwhich would normally be around Aug/Sep and Dec/Jan.

6 Entry Qualifications

Applicants with a recognised Higher Diploma in a Computing or IT related disciplinewill be considered for direct entry onto a top-up degree programme. Applicants mustalso be able to demonstrate an appropriate level of English.

6.1 Standard Entry QualificationsCertain entry qualifications are de signated as standard qualifications. Centres are

permitted to make offers to students with standard qualifications, which currentlyinclude:

APTECH Higher Diploma in Software EngineeringVietnamese Higher Diploma Computer Programming (Bang Cao Dang Lap Trinh May Tinh)

Other qualifications are evaluated and if they are considered to be at the right leveland compatible with the top-up degree in terms of their content then they are added tothe list of standard qualifications.

6.2 Non-Standard QualificationsStudents with qualifications that are considered to be of an appropriate standard andsuitable for entry to the final year of the BSc Computing will also be considered. Ifaccepted, the performance of these students will be monitored. Centres will be askedto provide an analysis of the performance of students accepted with non-standardqualifications in their Programme Monitoring Report (PMR) which is submitted to theUniversity each year. Additional qualifications may be added to the list of standardones as a result of the analysis provided in the PMRs.


6/38


6

6.3 Level of EnglishStudents who have not studied their entry qualification in English must have anappropriate English qualification such as IELTS 6.0, TOEFL (550) or equivalent, or

be able to demonstrate an equivalent level of English. A useful guide would be forexample, whether an applicant had studied their previous qualifications completely in

English, and if so, for how long. A minimum of two years is expected.

With approval from the CMS School, centres may carry out alternate English testslocally.

7 Admissions Procedure

With effect from September 2012, students will complete a special online applicationfor overseas collaborations. The Link Tutor at a centre will check the qualificationsuploaded to the admissions system and verify that the originals have been sighted.The CMS collaborations office will check forms and confirm eligibility via theElectronic Admissions System.

Centres will be permitted to make offers to students who meet the standard entryqualifications. Applications from students with non-standard entry qualifications must

be forwarded to the CMS School for a decision before teaching commences.

7.1 Collaborations Admissions PanelAll applications for CMS programmes made through the online admissions system areverified by the School as part of the admissions process.

A Collaborations Admissions Panel chaired by the Director for InternationalCollaborations (or his nominee) and consisting of one or more Link Tutors and/orCollaborations Officers, meets regularly to assess all non-standard applications andany applications which may require further consideration.

7.2 Minimum AgeThere is no minimum age for entry to the programme, however the University has aduty to safeguard the needs of students under 18 years of age. Centres recruitingstudents under the age of 18 will be asked to outline how their needs will beaccommodated. This information should be inserted into the relevant section of thestudent handbook template.

8 School Administration of the Programme

The School has an established Collaborations Office which deals with all the School- based administration needs of collaborative programmes. Academic staff manage theacademic side of Collaborations and carry out the roles of Regional Link Tutor,Programme Leader, and Director for International Collaborations.

Each approved centre is required to nominate a Link Tutor. This person is responsiblefor managing the programme locally and is the first point of contact for all queries andcommunications regarding the management and day-to-day running of the scheme.


7/38


7

Roles and Responsibilities

The School has identified a number of roles within the collaborations process:Director for International Collaborations, Link Tutor, Programme Leader, Course Co-ordinator and Collaborations Officer. Indicative responsibilities for these roles, and

for approved centres, are set out below.

8.1.1 Director for International Collaborations Liaise with the Universitys Educational Partnership Unit regarding the

Memorandum of Agreement and the Financial Memorandum Be responsible for instigating new collaborative proposals Oversee the task of keeping Programme Documents up-to-date. Oversee the approval of new centres Oversee all activities within the Collaborations Office Oversee the activities of all Regional Link Tutors and Programme Leaders for

collaborative programmes Act as the Schools representative on matters relating to computingcollaborations

Review the AMRs submitted by centres

8.1.2 CMS Regional Link Tutor Be responsible for collaborations at designated approved centres Make decisions on non-standard applications Liaise with Link Tutors at centres Carry out QA visits to centres

8.1.3 CMS Collaborations Officer Be responsible for the administration of the overall assessment process for

collaborative programmes which involves the timetabling, setting, markingand moderation of courseworks, examinations and projects

Liaise with the Student Records team in the Office of Student Affairs asneeded in order to keep students records accurate and up-to-date

Liaise with the Universitys Finance Office in order to raise fee invoices andrecover debt

Manage the admissions process and liaise with Admissions and the Office ofStudent affairs to ensure that students are properly registered

Provide administrative support to all aspects of collaborations managed by theSchool

Responsibility for courses and for programmes rests with the designated course coordinatorsand with the Programme Leaders appointed by the School.

9 Responsibilities of Approved Centres

The main responsibilities are normally set out in brief in the Memorandum ofAgreement. Responsibilities typically include:


8/38


8

Mark courseworks and examination scripts using the marking guides providedand send marked examination scripts to the CMS Collaborations Office formoderation;

Mark projects using the project assessment forms provided; Keep a record of the local marks for each course; Provide copies of minutes from all programme committee meetings; Seek approval from the CMS School for new staff to teach on the programme

and provide CVs for these staff Submit an Annual Monitoring Report in accordance with University of

Greenwich guidelines; Provide timetables and programme delivery information required for student

registration. Complete continuing student registration forms indicating whichcourses each student will take in each semester;

Advise students regarding extenuating circumstances and requests forassessments to be deferred; check all extenuating circumstances forms before

submission to the Collaborations Office; Advise students on what is meant by Withdrawal and Interruption of Studiesand whether and when they should apply for these.

A full list of responsibilities of all partners is listed in the relevant Annex of theMemorandum of Agreement.

10 Taught Regulations and Appeals

The University of Greenwich Regulations for Taught Awards will apply in addition toany CMS School Programme Regulations.

Information on regulations and appeals and where to find further details on theUniversitys Web site is given in the Student Handbook and on the CMSCollaborations Web site.

11 Teaching and Assessment Strategy

The teaching strategy should emphasise the importance of helping students to acquirethe necessary learning skills for study at final year undergraduate level. Studentsshould be able to develop both academic and practical skills and be able to apply

theory and practice in academic investigation and in the development and applicationof computer systems and technology in a business enterprise. Study at the level of afinal year honours degree should encourage analytical and evaluative skills that enablestudents to reflect critically on their work and the work of others.

Teaching methods will include lectures, small class tutorials and practical workshopand laboratory exercises. Students will be expected to engage in unsupervised study toa greater extent than at diploma and higher diploma levels. The Internet and othercommunication technologies (which may include broadcasting lectures using videoconferencing and other technologies) will be used where possible to support thedelivery of course material.


9/38


9

11.1 AssessmentCoursework and examinations will be used to assess the learning outcomes ofindividual courses. The assessment strategy for a course is set out in the coursespecification.

12 Assessment Procedure

Examinations and courseworks are set by academic staff in the CMS School. Centreswill mark courseworks and examination scripts, using the detailed marking guides

provided, and under guidance from the CMS School. Where a centre hasresponsibility for marking examination scripts the samples of examination scripts will

be sent to the CMS School for moderation together with a spreadsheet of the marks.The School reserves the right to require that all examination scripts be forwarded tothe CMS School.

Students will be required to submit their coursework in electronic format byuploading it to a server hosted by the CMS School. Full instructions on how to dothis, the deadlines for submission for each assessment and the penalties for latesubmission will be provided in the Student Handbook and will also be available fromthe CMS Collaborations Web site.

12.1 Examination BoardsThe University holds a Subject Assessment Panel (SAP) and a Progression andAwards Board (PAB) for each programme. The final marks for each course for a

programme will be presented to a Subject Assessment Panel for verification.Following the SAP, the full set of marks for each student on the programme will be

presented to a Progression and Awards Board which will decide whether a studentmay proceed to the next stage of the programme or in the case of a completingstudent, whether that student has met the requirements for an award. The PAB willalso determine whether a student may be deferred in one or more assessments, andwhether a student has failed one or more assessments and the manner of retrieval ofthe failed assessments.

SAPs and PABs will be held at the Maritime Greenwich Campus in July and Februaryeach year and staff at approved centres will be invited to attend.

13 Learner Resources

13.1 Learner resource materialsA set of teaching and learning support materials for each course is available on thecollaborations website. Course specifications giving the aims and learning outcomesfor courses, outline syllabus content, and learning and assessment strategy are

provided.

Most courses have been developed around a core text book which is normallysupported by additional materials provided by the publisher. These typically includeoverhead transparencies, instructors recourses, and students resources. Usernamesand passwords to instructors areas are available.


10/38


10

13.2 On-line lecture materialsCourse lectures developed using Microsoft PowerPoint are available to be viewed anddownloaded by staff and students. Students may download lectures in PDF formatwhilst staff may download lectures in PPT format to use in their lectures and to

modify them as they wish.

As an additional aid to teaching , presentations using Adobe Presenter with full audiocommentary from lecturers in the CMS School are available for level 6 courses tolecturers at centres.

13.3 Additional learner resourcesAdditional material available from the Collaborations web site includes;

Tutorial exercises recommended by the course coordinator Past examination papers from each previous assessment point Sample solutions for selected level 6 examination papers

13.4 Off-Campus Services Contact and Remote Support (OSCARS)The off- campus users support gro up OSCARS was created in 2004 in recognition ofthe distinctive support needs of this important and growing category of users.OSCARS is intended to complement and promote the many existing services andsupport arrangements for users working exclusively or predominantly away from theUniversitys campuses. It will develop new services for off -campus users and driveforward the equity of provision with on-campus users. OSCARS will provide a single

point of entry into the various existing and future information sources and services, in

effect transferring these to the users location. The OSCARS web site is at http://www.gre.ac.uk/offices/ils/ls/services/oscars . Enquiries can be made via an on-line form (students) or by email (staff):

Students should submit queries using the ILS support request form:www.gre.ac.uk/ils/helpme

Staff should submit queries by email to the IT Helpdesk: [email protected] .

14 Dealing with student queries

The School recognises the importance of making the learning experience of studentsat remote sites as similar as possible to students attending at the University ofGreenwich. Although off-campus students will enjoy the same rights as on-campusstudents with regard to contacting University staff and University Departmentsdirectly, it is desirable that students discuss any problems with their Link Tutor first.

14.1 Queries related to the top-up programmeThe Link Tutor may forward student queries to the CMS Collaborations Office foradvice. This will ensure that student queries are dealt with effectively by staff familiarwith collaborations in CMS. Further facilities for staff and students to contact tutors inCMS are provided through the CMS electronic forums for staff and students atapproved centres.
http://www.gre.ac.uk/offices/ils/ls/services/oscarshttp://www.gre.ac.uk/offices/ils/ls/services/oscarshttp://www.gre.ac.uk/ils/helpmehttp://www.gre.ac.uk/ils/helpmemailto:[email protected]:[email protected]:[email protected]:[email protected]://www.gre.ac.uk/ils/helpmehttp://www.gre.ac.uk/offices/ils/ls/services/oscars


11/38


11

14.2 Queries concerning University servicesStudents and staff should contact OSCARS directly. Alternatively, they may contactthe CMS Collaborations Office.

15 Information for staff and students

15.1 Web Site for CollaborationsThe CMS School maintains a Collaborations Web site for the staff and students atapproved centres. The Web site is used to provide general information such asexamination dates, links to University-wide information, programme-specificinformation and learner resource materials. There are separate staff and studentintranets requiring different login IDs and passwords.

The School now maintains a log of the accesses to the Web site made by each centre.The log differentiates between accesses made by staff and accesses made by students.These statistics can then be forwarded to centres.

15.2 Electronic ForumsTwo electronic bulletin boards have been set up, one for teaching staff at approvedcentres and one for students. These are intended to provide staff and students atdifferent centres with the opportunity to communicate on common subject areas andto disseminate examples of good practice. Likewise, students at different centres canalso discuss aspects of the programme and share ideas. Both bulletin boards will beaccessible to CMS staff who will be able to contribute to any discussion threads. Theforums will be monitored on a regular basis.

16 CMS School QA Visits to Approved CentresIn normal circumstances, academic staff in CMS will carry out annual qualityassurance visits but in the first year of running the programme it is normal toundertake at least two visits. CMS staff will talk to staff and students at the centre andmay contribute to the teaching or observe teaching taking place.

CMS staff will complete a report following each visit to a centre. The report willinclude an action plan to be followed up. A copy of the report will be sent to thecentre concerned.

The CMS School may hold video-conferencing sessions in addition to the annualvisits.

17 Obtaining Student Feedback

The School has an online survey system for students to give structured feedback at theend of each year, on the courses that they take. This system has been extended to allstudents on international collaborations. The survey results can be aggregated anddifferent views provided to designated managers within the School. Additionalmechanisms for obtaining students feedback include:

Meetings with students during annual QA visits to centres


12/38


12

Minutes of programme committees held at each centre Summarised comment provided in the Programme Monitoring Report

18 Feedback on Assessment

Course co-ordinators will complete a Course Monitoring Report on the collaborationsweb site which will include their comments by course, and by centre, on thecoursework and project marking carried out by tutors at centres as well the student

performance in examinations. The report will include reflective comment on student performance and may give additional guidance such as highlighting exam topics thatwere clearly understood and answered well and those where answers given weregenerally poor.

18.1 Feedback to tutors at approved centresCopies of the relevant result lists (and PAB reports upon request) will be sent to eachcentre following an assessment point. The Link Tutor at each centre will also be ableto view the marks for their students using BannerWeb.

Informal feedback may also be given by course co-ordinators or by the CMS LinkTutor as and when the need or opportunity arises. For example, student performancein a course may vary considerably across centres and it may be necessary to report oncentre-specific issues.

Student performance at each assessment point will be discussed with centres at thefollowing institutional visit.

18.2 Feedback to StudentsStudents will be sent a letter giving the progress decision or award made by the PAB.This decision and the individual marks for each course may also be viewed usingBannerWeb following the PAB. Completing students will also be sent a full transcriptof their results, and their degree certificate.

Feedback to students in various programme-related areas will also be given by usingthe Collaborations Web site for posting information on a regular basis and via thestaff and student forums.

19 External Examiners

The appointed External Examiners will scrutinise the moderation carried out byacademic staff in the CMS School and review samples of work from each teachinginstitution. The External Examiners will normally attend all SAPs and PABs.

The External Examiners Reports should include specific commentary on:

the marking carried out at different teaching institutions the performance of students across teaching institutions

20 QAA Subject Benchmarks


13/38


13

The QAA Subject Benchmark Statement for Computing specifies threshold andtypical standards for graduates of honours degrees. It specifies that students shouldmeet these standards in an overall sense, not necessarily in respect of each and everyone of the statements listed. The definitions are given below.

While at Ordinary degree level, the programme reflects the subject areasoutlined in the subject benchmark statement for computing and also meets thethreshold standards, as these cover subject knowledge rather than the criticalskills that the honours part of the programme brings.

Direct entrants to the BSc Computing (Stage 3) programme will have studiedcomputing the level of a Higher Diploma or equivalent qualification in Computingwhere C omputing may encompass a wide range of recognised subject titles such asComputer Science, Information Systems, Information Technology, SoftwareEngineering, Multimedia, Computer Systems and Networking and ComputerEngineering.

20.1 Benchmarking Standards

Benchmark standards are defined at threshold and typical levels and some furthercomments are made about excellence.

20.1.1 Threshold level

The threshold level is interpreted to mean that all students (taken over all years),graduating with an honours degree in the discipline of computing will have achievedthis level of performance.

On graduating with an honours degree in computing, students should be able to:

demonstrate a requisite understanding of the main body of knowledge for their programme of study

understand and apply essential concepts, principles and practice of the subjectin the context of well-defined scenarios, showing judgement in the selectionand application of tools and techniques

produce work involving problem identification, the analysis, the design or thedevelopment of a system with appropriate documentation, recognising theimportant relationships between these. The work will show some problem-

solving and evaluation skills drawing on some supporting evidence, anddemonstrate a requisite understanding of the need for quality

demonstrate transferable skills and an ability to work under guidance and as ateam member

identify appropriate practices within a professional, legal and ethicalframework and understand the need for continuing professional development

discuss applications based upon the body of knowledge.

20.1.2 Typical level

This is the average standard attained (taken over all years) of all the studentsgraduating with an honours degree in the discpline of computing.


14/38


14

On graduating with an honours degree in computing, students should be able to:

demonstrate a sound understanding of the main areas of the body ofknowledge within their programme of study, with an ability to exercise critical

judgement across a range of issues

critically analyse and apply a range of concepts, principles and practice of thesubject in an appropriate manner in the context of loosely defined scenarios,showing effective judgement in the selection and use of tools and techniques

produce work involving problem identification, the analysis, the design or thedevelopment of a system, with accompanying documentation, recognising theimportant relationships between these. The work will show problem-solvingand evaluation skills, draw upon supporting evidence and demonstrate a goodunderstanding of the need for quality

demonstrate transferable skills with an ability to show organised work as anindividual and as a team member and with minimum guidance

apply appropriate practices within a professional, legal and ethical frameworkand identify mechanisms for continuing professional development and lifelonglearning

explain a wide range of applications based upon the body of knowledge.

20.1.3 Excellence While the benchmark standards above are defined for just threshold and typical levels,it is nevertheless expected that programmes in computing will provide opportunitiesfor students of the highest calibre to achieve their full potential.

Such students will be:

creative and innovative in their application of the principles covered in thecurriculum, and may relish the opportunity to engage in entrepreneurialactivity

able to contribute significantly to the analysis, design or the development ofsystems which are complex, and fit for purpose, recognising the important

relationships between these able to exercise critical evaluation and review of both their own work and the

work of others.

6.8 In as much as human ingenuity and creativity has fostered the rapid developmentof the discipline of computing in the past, programmes in computing should not limitthose who will lead the development of the discipline in the future.


15/38

21 Appendix A - Programme Specification


16/38

16

UNIVERSITY OF GREENWICH: PROGRAMME SPECIFICATION

1. Awarding Institution 2. Teaching Institution 3. School/Department 4. UCAS Code:FPT University CMS/Computing and Information

SystemsN/A

5. Final Award 6. Programme Title 7. Accredited by:

BSc Computing (Stage 3)

8. Quality Assurance Agency (QAA) Benchmarking Group(s)

Benchmarking statements for the subject you are studying define what a studen t is expected to learn from studying that subject. They are defined by academicstaff in the field and provided to students and universities by the Quality Assurance Agency (QAA). Benchmarking statements are explained and described onthe Agencys website at: http://www.qaa.ac.uk/academicinfrastructure/benchmark/default.asp

9. Educational Aims of the Programme and Potential Career Destinations of Graduates [Maximum 150 words]:

To produce graduates that are educated in the theory, technology, practice and application of computing. To enable students to have an appreciation of the context in which computing takes place. To deliver a coherent and integrated learning experience relevant to the needs of future computing professionals. To give students skills which are life-long and transferable between disciplines and careers. To provide a proper foundation for the pursuit of professional qualifications and higher degrees.

To ensure that students can work effectively both independently and as part of a team. Graduates will be able to gain employment as a computing/IT professional in the IT industry

10. Summary of Skills Development for Students within the Programme [Maximum 150 words]:Students will gain knowledge of computing skills and applications, and modern practices in information systems engineering. Students will be able to designand Implement solutions to business problems. They will also gain an understanding of emerging technologies. There will be hands-on training in varioussystem modelling and programming tools.
http://www.qaa.ac.uk/academicinfrastructure/benchmark/default.asphttp://www.qaa.ac.uk/academicinfrastructure/benchmark/default.asphttp://www.qaa.ac.uk/academicinfrastructure/benchmark/default.asphttp://www.qaa.ac.uk/academicinfrastructure/benchmark/default.asphttp://www.gre.ac.uk/


17/38

17

11. The programme provides opportunities for you to achieve the followingoutcomes:

These are related to the benchmarking statements for the subject you arestudying, described under 8 above.

The following teaching, learning and assessment methods are used toenable you to achieve and demonstrate these outcomes:

A. Knowledge and understanding of: A. Teaching and learning methods:

1. Analysis and modelling techniques for software requirements.2. Techniques, tools and technologies for building computer systems.3. Hardware and software capabilities, advantages and disadvantages.4. Social and ethical and legal issues relating to the design and implementation of

computer systems.

5. The structure of organizations and role of data and information within them.

This knowledge and understanding will be acquired through lectures, tutorials, laboratorysessions and directed research and reading.

A. Assessment methods:

The students will be assessed in tutorial exercises and log books of laboratory sessions. Inaddition there will be coursework assignments and examinations where appropriate.

B. Intellectual skills: B. Teaching and learning methods:

1. Studying concurrently in more than one subject discipline.2. Applying appropriate techniques tools and technologies to situations.3. Applying a variety of problem solving approaches to software development.4. Developing a capacity for critical analysis and evaluation.5. Planning and undertake academic research.

These skills will be developed on an individual basis in response to the stimulation of teachingmaterial received through lectures, tutorials, laboratory sessions and directed research andreading.Students will be encouraged at all times to develop their critical faculties and exercise creative

problem solving. The final year proj ect gives the opportunity for stude nts to further enhancethese skills

B. Assessment methods:

Intellectual skills will be assessed throughout the programme and in examinations andcoursework. The final outcomes of the project will also demonstrate the students development ofall of these skills


18/38

18

C. Subject practical skills: C. Teaching and learning methods:

1. Applying skills techniques and knowledge to design and implement non- complexcomputer applications to meet user requirements.

2. Being familiar with the basic hardware and software components of a computer.3. Using the Internet and basic Internet tools4. Creating web pages and database applications using a variety of programming

techniques and packages.

These skills are taught through lectures, tutorials, laboratory sessions and directed research andreading. In particular students will be encouraged to explore other information sources and on-line resources to make sure they are using current technology and skills

C. Assessment methods:

The skills will be assessed in tutorial exercises and log books of laboratory sessions. In additionthere will be coursework assignments and examinations where appropriate.

D. Transferable/key skills: D. Teaching and learning methods:

1. An understanding of the individual and group aspects of project management.2. A facility with communication both verbal and written.3. Presentation skills.4. Understanding of professional and ethical standards.5. The ability to research, analyze and formulate solutions for a variety of problem

domains.

Whilst many of these skills will be acquired throughout the taught courses, a week is set aside in both years 1 and 2 to develop person al professional and business skills. In addition the studentwill learn many aspects of research, project management and problem solving through the finalyear project

D. Assessment methods:

Students will be assessed by tutors in classroom and laboratory sessions. They will have groupand individual presentations to make during both their skills weeks and produce reports. Theywill work under individual supervision for their final project and be assessed throughout againstdeliverables.


19/38

19

E. Graduate Attributes: E. Teaching and learning methods:

This section will be completed when the home programme is reviewed.

E. Assessment methods:

12. Programme Structure: Levels, Courses and Credits Awards, Credits and Progression of Learning OutcomesLevel

5

Compulsory Courses

Application Development for Mobile Devices (15 credits)Software Engineering (30 credits)Systems Programming (15 credits)

Level

6

Compulsory Courses

Database Design & Implementation (15 credits)Information Systems Engineering (15 credits)IT Project & Quality Management (15 credits) Distributed Information Systems (15 credits)

Ordinary Degree (120 credits)


20/38

20

22 Appendix B - Course Specifications


21/38

21

COURSE SPECIFICATION

Code: COMP 1158 School: CMS 22.1 Course Title: Software EngineeringCourse Co-ordinator: Avgousta Kyriakidou Level: 5 Credit: 30 Department: Computing and Information Systems Pre-requisites: None

Pre-requisites: System Building 1

Aims: Following on from System Building 1 and Computer Programming 1, this course adopts anobject-oriented approach to systems building and covers in detail, the design andimplementation of computer systems. The course concentrates on a standardised object-oriented modelling language (currently the UML), and the use of an appropriate CASE toolthat supports object-oriented analysis and design, specification using the UML and somedegree of automatic code generation. The course also introduces the student to thecomplexities and risks of project management while trying to balance the diverse constraintsof the economical, social and technical environments within which they are built.

Learning Outcomes: By the end of the course, students will be able to:A. Use appropriate analysis, design, testing and implementation techniques, tools and

patterns to develop a design and partial implementation for a large software system using amethodical approach.

B. Appreciate the effects that; constraints, risks, quality assurance, complexity, laws, ethics prerequisites, change, contingencies and competencies have on project management and thetechniques that may be used ameliorate risks.C. Work in a team on a (case study based) well documented incremental systemsdevelopment.

Indicative Content: Systems Development:The Unified software development process. Risk, quality, reliability (formal methods),testing, version, project and integration management. Incremental, user centric development.

RAD. Extreme.Relationship between analysis, data, patterns, design and code:In depth OO analysis, design and implementation. Algorithms and their depiction. Use CaseModelling and requirements capture, CRC, Dynamic Modelling, Sequence Diagrams, ClassDiagrams, State Transition Diagrams and interfaces all designed down to code level.Programmatic database development. Scripting for productivity.Systems in context:Multinational, business, social, environmental, legal, ethical and human aspects.HCI factors:Internationalisation, Ergonomics, Usability, Input/Output Devices, Overview ofPsychological issues, User Interface Design, Design approaches, Evaluation.Case studies:Team work, planning, meetings, minutes and presentations, requirements and production oftechnical documentation, Iterative OOADI.Implementation:


22/38

22

Real time OO threaded control interface with concurrent programmatic database

manipulation for records and/or persistence.

Learning and Teaching Activities: The course will be taught by a mixture of lecture, tutorial, and laboratory work. Students willtake a focused view on specific aspects of the systems development process. The emphasis inall practical work will be on coping with complexity and engineering quality into the product.Major concepts will be introduced by lecture, with practical skills being developed intutorials and hands-on systems design and implementation taking place in scheduledlaboratory sessions. It is expected that students will spend an amount of time equal to thetimetabled hours in further group based and individual practical work. The course will be

supported by a logbook containing both examples of set work and reflective reviews.

Student time will be: Lecture 1/3, Tutorial 1/3, Laboratory 1/3.

Assessment Details:

Methods ofAssessment

GradingMode

Weighting%

MinimumPass Mark

WordsLength

Outline Details

GroupCoursework

50 40 6000 Learning outcomes: A, BCase Study - A substantialobject oriented design andimplementation and

presentation. IncludingHCI, teamwork and projectmanagement issues.

IndividualCoursework

50 40 3000 Learning outcomes: A, B, CCase Study - Case Study -focusing on one iteration ofan Analysis and Design ofan OO system, and

documentation.Logbook 10 40 N/A Learning outcomes: A, B, C

Ongoing, reflective, log ofexperiences anddeliverables.

Exam 40 40 N/A Learning outcomes: A, B3 Hours. Theory and

practical.


23/38

23

Text Books The following is a list of books that may be used in this course. This list is subject to change.Please wait for advice from the lecturer when the course begins before spending money on

books.Author Title Publisher Date Of

PublicationISBN Comment

Avgerou, C.and T.Cornford

DevelopingInformationSystems:Concepts,Issues andPractice (2ndedition)

Macmillan,Basingstoke,UK

1998 Worth a read!Some of itschapters will

be used in ourlectures

Bennet St,

Farmer R,McRobb S

Object-

OrientedSystemsAnalysis andDesign UsingUML

McGraw-

Hill

2010 0077125363 Important to

read forOOAD

Checkland, P Systemsthinking,systems

practice

John Wiley& Sons,Chichester

1999 Used in ourSoft systemsmethodologylecture.

Larman, C ApplyingUML and

Patterns: AnApproach toObject-orientedAnalysis andDesign

Prentice Hall 2005

Pressman, R.S. SoftwareEngineering:A

practitioner'sapproach

Mc-GrawHill

2000 Worth a read!Some of itschapters will

be used in ourlectures

Sommerville, I SoftwareEngineering,8th edition

AddisonWesley

2006 Important!Most of itschapters will

be used in ourlectures.

Whitten L.Jeffrey,Bentley D.Lonnie, andDittman C.Kevin

SystemsAnalysis andDesignMethods

McGraw-Hill Irwin

2001 0-07-231539-3

Important toread for OOAand SSA


24/38

24


Code: COMP 1302 School: CMS 22.2 Course Title: Database Design & ImplementationCourse Coordinator: Dr. Ala Al-Zobaidie Level: 6 Credit: 15 Department: Computing and Information Systems Pre-requisites: N one

Aims: 1. To explain the need for a database system and its role in a business and other types oforganisation.2. To provide a detailed understanding of the principles of database processing.3. To enable students to acquire and apply skills and techniques for the design and implementationof a database using a suitable relational database package.4. To discuss current and future trend in DB applications and their requirements.

Learning Outcomes:

By the end of the course, students will:Id Learning OutcomeA Develop a sound understanding and knowledge of database technology, its

importance, its architectures, user's roles, and the central role that databasetechnology plays in information systems.

B Critically evaluate various database design options at conceptual, logicaland implementation levels.

C Evaluate various file organisation methods, distribution strategies,concurrency mechanisms, query optimisation techniques, and database

recovery and security procedures.D Critically examine and reflect on the theoretical aspect of the process of

normalisation and its practical implementation.E Evaluate and use various modern database management systems tools in

building a small but realistic database system.F Describe advances in trends and emerging standards in database technology;

understand the comparative features and crucial aspects of data andknowledge management technology and the impact of the Internet ondatabase technology.

Content:

1. Database Architecture and environment Three-level schema architecture; Data Independence; Database languages and interfaces; Thedifferences between Conceptual, Logical and Physical data models; Functions of a DBMS;Data and Database Administration.

2. Conceptual Database Modelling Entity-Relationship Model concepts; Problems with ER Models; The Enhanced Entity-Relationship Model and various notations.

3. Relational Database Design Representing Data Model; Mapping EERD into a Relational Schema; Functional Dependencyand Normalisation


25/38

25

4. The Relational Database Languages Relational Algebra; Relational calculus; Structured Query Language; Relational DBApplication Development tools.

5. Database Administration Physical DB organisation; Transaction Management and Concurrency Control; DatabaseRecovery; Database Security; Query Evaluation, Processing and Optimisation.

6. Distributed Databases Client/ Database Server Architecture; Homogeneous, Heterogeneous and FederatedDistributed Database Management Systems; Schema Architecture for Distributed DBMS;Design Issues: Data Fragmentation, Allocation and Replication;

7. Object-Oriented Databases Object Modelling Concepts and Object-Oriented DBMSs: Weaknesses of Relational DBMSs;Architecture of OODBMS; The OODBS manifesto; Object-Relational Database managementsystem; Comparison of ORDBMS and OODBMS; The ODMG Standards.

8. Advances in Databases Data Warehousing; OLAP vs. OLTP; Multidimensional Modelling; Database and the InternetTechnology; Web enabled Databases and XML technology.

Prior Knowledge and/or Skills Required

It would be highly recommended to have knowledge of data & file structures and theirorganisation.

Learning and Teaching Activities Students are expected to have formal lectures on theoretical aspects followed by classroomtutorials or discussions to consolidate the covered issues. Instructors may refer to some of thereview and exercise questions which can be found at the end of related chapters in therecomme nded textbooks or use his/her owns material. Instructors may also find some relatedmaterial on the course website. Laboratory exercises usually follow these classroomexercises. The aim of most laboratory work is to enable students to acquire necessary skillsthat are essentials to carry out their coursework assignments. The coursework usually coverssome data analysis, design and an implementation of a small prototype for an appropriate

business application based on the Relational model. Therefore the coursework requirementsshould be reflected in these laboratory exercises, and laboratory work should focus on

building the relational tables and business rules using Structure Query Language (DDL &

DML) plus familiarisation exercises with the DBMS tools available.

Assessment Details:


GradingMode

Weighting%

MinimumPass Mark

WordsLength

Outline Details

Examination

Coursework

50%

50%

40

40

Assessing learning outcomesA, B, C, D, E & F.

Assessing learning outcomesB, D & E.


26/38

26

Core Texts

ISBN Author Date Title Publisher

0321523067 ThomasConnolly &Carolyn Begg

2009 Database Systems 5 th ed.http://vig.pearsoned.co.uk/catalog/academic/product/0,1144,0321523067,00.html

Addison-Wesley


27/38

27


Code: COMP 1303 School: CMS 22.3 Course Title: Distributed Information SystemsCourse Coordinator: Stylianos Kapetanakis Level: 6 Credit: 15 Department: Computing and Information Systems Pre-requisites: None

Aims:

In order to be able to function effectively as a software engineer, students need to acquireknowledge in designing and developing distributed information systems with associated toolsand techniques combined with the ability to apply appropriate modelling and designtechniques, and an awareness of leading-edge technologies. This course will both deepen and

broaden the students' existing knowledge of software engineering, focusing on the analysis of

enterprise distributed systems requirements and feasibilities.Learning Outcomes

By the end of the course, students will:Id Learning OutcomeA Analyse the business context and application domain of DIS.

B Differentiate between the various architectures of distributed systems andapplications and be able to determine their relative merits for a givenscenario.

C Appraise alternative designs and select suitable DIS developmentmethodologies including the object-oriented paradigm and WWWtechnology.

D Assess the role of middleware and its services in the design of DIS.

E Understand the need for standards and protocols in distributed computing,and be aware of the major standards and responsible bodies.

F Evaluate and select popular network technologies and protocols.

G Understand distributed transactions and issues that arise therefrom.

H Appreciate the security requirements of DIS.

I Apply knowledge and practical skills acquired in laboratory sessions andduring the completion of coursework assignments.


28/38

28

Content:

Content at level 5 (6 hours)

1. Networking and Internetworking: LANs, WANs, MANs, Switching, Protocols, Layeredarchitectures (OSI, TCP/IP), IP, IP Addressing, TCP and UDP, Point to Pointcommunication, Broadcast communication, Firewalls.

2. Characterisation of a DIS. Design goals: Openness, Security, Scalability, Concurrency,Reliability, Availability. Transparency: Access, Location, Concurrency, Replication, Failure,Mobility, Performance, Scale. Development methodologies.

3. System models: Client-Server, Middleware, Two-Tier vs Three-Tier models, Peer processes Mobile code: Applets, Mobile agents.

4. Networking and Internetworking: LANs, WANs, MANs, Switching, Protocols, Layeredarchitectures (OSI, TCP/IP), IP, IP Addressing, TCP and UDP, Point to Pointcommunication, Broadcast communication, Firewalls.

Content at level 6 (24 hours)

5. Inter-process Communication: OSI, UDP, Synchronisation, TCP-IP, Marshalling,CORBA, Java serialisation, Client / Server Communication, Group communication

6. Distributed Objects and Remote Invocation: Distributed data / distributed processing, IDL,Remote Interfaces, RMI, Events and Notification, .NET, SOAP, overview of COM / DCOM /OLE / ActiveX, Java RMI; Object Request Brokers: ORB, CORBA, CORBA IDL, CORBAServices, Applets with CORBA, Legacy Applications.

7. Building a DIS application using a choice of appropriate technologies including forexample .NET, Java, and MS SQL Server.

8. Operating System support: O/S Architectures, Kernels, Microkernels, Protection, Processesand Threads, Thread synchronisation and thread scheduling.

9. Security: Threats and Attacks, Cryptography, Digital signatures, Certificates, Accesscontrol, Credentials, Kerberos.

10. Distributed File Systems: File Service architecture, NFS, AFS.

11. Name Services: Directory and Discovery services, DNS.

12. Time and global states: Clocks, Clock synchronisation, Events, Logical time and Logicalclocks.

13. Coordination and agreement: Distributed Mutual Exclusion, Election Algorithms.

14. Transactions and Concurrency control: Transactions, Nested Transactions, Locks,Concurrency control, Distributed Transactions, Distributed Deadlocks. Distributedtransactional applications: Internet / Web Information Systems models and technology, J2EE,

Enterprise Java Beans. Distributed System design: Web Services Description Language(WSDL), XML and XML web services, JINI technology.

15. Replication: Group Communication, Fault-Tolerant Services, Primary-backup replication,


29/38

29

Active replication.

16. Java EE Application Architectures.

17. Service Oriented Architectures.

18. .NET Architecture.

19. Grid computing.

Prior Knowledge and/or Skills RequiredStudents should ideally have gained level-2 understanding of networking; operating systemstheory; and programming (in an object oriented language such as Java), before undertaking thiscourse.

Learning and Teaching Activities: This course is to be delivered via several complementary activities: lectures, tutorials, practicalwork and directed unsupervised learning. The rationale for this mix of activities is to give thestudents an interesting and varied learning experience combining theory and analysis backed up

by practical experimentation where appropriate.

Assessment Details:


GradingMode

Weighting%

MinimumPass Mark

Outline Details

Exam 50 40 A three hour closed-book examinationwith a choice of any three questions outof five.Learning outcomes A, D, E, F, G, Hwill be assessed.

Coursework 50 40 A case-based exercise in whichstudents have to carry out someanalysis, design, limitedimplementation, and devise test plans.A detailed critical evaluation is alsorequired.Learning outcomes B, C, D, F, I will beassessed.

Core Texts :


0321263545 G.Coulouris,J.Dollimore,T.Kindberg

2005 Distributed Systems:Concepts and Design, 4 thed.http://www.booksites.net/coulouris

Addison-Wesley


30/38

30


Code: COMP 1304 School: CMS 22.4 Course Title: Information Systems EngineeringCourse Coordinator: Phil Clipsham Level: 6 Credit: 15 Department: Computing and Information Systems Pre-requisites: N one

Aims: To give an understanding of how information systems methodologies can support thedevelopment of quality applications.To allow the student to examine the role of methods in a modern software developmentenvironment.To consider the importance of requirements analysis in the development life cycle.To look at some of the techniques used to understand human activity systems.

Learning Outcomes:

By the end of the course, students will:Id Learning OutcomeA Examine the role of information, data and knowledge in the development of

information systemsB Understand the role of a methodology and critically assess the benefits and

limitations of the traditional systems development frameworks.C Critically evaluate a range of approaches to aid the analyst to carry out

requirements analysis.

D Understand future trends in the use of methods in developing informationsystems.

Content:

1. Information and meaning: Introduce the concept of methodologies, Examine the traditionalSDLC in perceptive, Understand the need for methodologies, Explore issues of quality whenusing a methodology.

2. The role of a methodology: The concept of a methodology, traditional SystemsDevelopment ,Life Cycle (SDLC) in perspective, benefits/problems associated ,with SDLC,the human dimension, organisational aspects, the need for a methodology, requirements of anInformation, Systems methodology, criteria for selection of a methodology.

3. Object Modelling as a requirements analysis tool: developing the Use Case , developing primary scenarios, developing secondary scenarios. Using case tools to capture requirements.Translation into an object model.

4. Soft Approaches to systems development: Introduction to Human Activity Systems. SoftSystems Method. Role of the Rich Picture in requirements analysis. CATWOE. ParticipativeDesign. ETHICS.

5. Interpretive analysis.


31/38

31

6. The future of methods.

Learning and Teaching Activities: This course is to be delivered via several complementary activities: lectures, tutorials, practicalwork and directed unsupervised learning. The rationale for this mix of activities is to give thestudents an interesting and varied learning experience combining theory and analysis backed up

by practical development where appropriate.

Assessment Details:


GradingMode

Weighting%

MinimumPass Mark

WordsLength

Outline Details

Coursework 50% 40 A case study based essay(2000) examining theRequirements Analysistechniques in the systems

development process.Assessing learningoutcomes B, C.

Exam 50% 40 A two hour exam coveringlearning outcomes A to D

Core Texts :


978-0077114176

Avison &Fitzgerald

2006 Information Systems Development Methodologies,Techniques and tools, 4 th ed.http://www.mcgraw-hill.co.uk/html/0077114175.html

McGraw-Hill

Recommended reading:

ISBN Number Author Date Title Publisher0077096266 Avison and

Fitzgerald2002 Information Systems

Development 3rd edition

McGraw-Hill

0201178893 Stapleton 2002 DSDM Business focused Devt 2 nd ed.

Addison-Wesley

0333639081 Mumford 1995 Effective Systems Design andRequirements AnalysisThe ETHICS Approach

Macillan

0201360675 Pooley andStevens

1999 Using UML. Software withobjects and components

0077898366 Fitzgerald,Russo andStolterman

2002 Information systemsDevelopment Methods-in-action

Mcgraw-Hill


32/38

32

047120287 Ambler 2002 eXtreme programming and theunified process

Addison-Wesley

0471958204 Checklandand Holwell

1999 Information, Systems andInformation Systems - makingsense of the field

Wiley

014018810X Toole 1980 A Confederacy of Dunces Penguin

0099450259Haddon 2004 The Curious Incident of the Dogin the Night-time

Vintage

0099466031 Eco 2004 The Name of the Rose Vintage


33/38

33


Code: COMP 1305 School: CMS 22.5 Course Title: IT Project and Quality ManagementCourse Coordinator: Andrew Stanley Level: 6 Credit: 15 Department: Computing and Information Systems Pre-requisites: N one

Aims:

In order to be able to function effectively as a Project Leader or Quality Assurance Managerstudents need advanced skills in using a project management software and spreadsheetscombined with the ability to apply appropriate modelling and design techniques. This coursewill both deepen and broaden the students' existing business and management skills. It willfocus on project management (e.g. using MS Project), modelling (using MS Excel) and qualityassurance.

Learning Outcomes:

By the end of the course, students will be able to:

Id Learning OutcomeA Demonstrate an in-depth knowledge of project management and

quality management techniques and practicesB Develop a complex project plan for a business solutionC Model a complex business application using a spreadsheetD Evaluate different project management methodologies

E Evaluate different quality management methodologies

Content:

Level 5 Content

1. Project Management concepts and practice (Work Breakdown Structure, GanttCharts, Network diagrams, Critical Path Analysis)

2. Professional report writing skills3. Advanced Spreadsheet concepts and techniques (data analysis using pivot tables,

complex formulae and functions, statistical analysis, effective charts)

Level 6 Content

4. Project Management and IT Context5. Project Management Process Groups6. Project Integration Management7. Project Scope Management8. Project Time Management9. Project Cost Management10. Project Quality Management11. Project Human Resource Management12. Project Communication Management13. Project Risk Management14. Project Procurement Management15. Case Studies


34/38

34

Prior Knowledge and/or Skills Required

Students should have a good knowledge of modern business processes and an understanding of basic project management concepts. They should have a high level of IT skills, particularly inthe use of spreadsheets.

Learning and Teaching Activities:

Theoretical aspects of topics will be introduced though lectures and reinforced throughclassroom-based tutorials. Practical skills will be taught and reinforced through supervisedlaboratory-based tutorials. Students will also need to work unsupervised in order to strengthentheir practical spreadsheet modelling and project management skills.

Assessment Details:


Weighting%

MinimumPass Mark

WordsLength

Outline Details

Coursework1

70% 40 N/A Development of a complex spreadsheetmodel and presentation for a proposedchange in a business and thedevelopment of a complex project plan.

Covers learning outcomes A to E

Coursework2

30% 40 N/A A series of questions assessing learning oand E

Core Texts:


0619159847 K. Schwalbe 2004 IT Project Management, 3 rd edition

Thomson Learning

Recommended Reading:


0077096770 R. Pressman 2000 Software Engineering, APractitioners Approach,Fifth Edition

McGraw Hill


35/38

35


Code: COMP 1550 School: CMS22.6 Course Title: Application Development for Mobile DevicesCourse Coordinator: Sylianos Kapetanakis Level: 5 Credit: 15 Department: Computing and Information Systems Pre-requisites: N one

Pre-requisites: Level 1 Programming

Aims: Use of mobile devices has been experiencing a very significant increase in recent years. Thisis driven by the lowering cost of hardware components, service infrastructures as well assoftware architectures. With the fast expansion of mobile devices, the development ofapplications for these devices is fast entering the mainstream of software development.

Software developers entering this field need to understand how the characteristics of mobiledevices and applications affect decisions about software design and be able to select and useappropriate technologies, standards, APIs and toolkits to build mobile applications.This course aims to prepare students to work in the area of mobile software development byintroducing them to the relevant technologies and equip them with skills in the design anddevelopment of mobile applications using up-to-date software development tools and APIs.

Learning Outcomes: On successful completion of this unit, students will be able to:A. Understand the technical challenges posed by current mobile devices and wireless

communications; be able to evaluate and select appropriate solutions.B. Appreciate the need to keep up with rapid changes and new developments; be able toidentify current trends in mobile communications technologies and systems.C. Select and evaluate suitable software tools and APIs for the development of a particularmobile application and understand their strengths, scope and limitations.D. Use an appropriate application development to design, write and test small interactive

programs for mobile devices.

Indicative Content: Characteristics of wireless, mobile applications - examples, service requirement, technicalchallenges.Programming mobile applications (e.g. using J2ME CLDC and MIDP).APIs for mobile devices (e.g. Java ME, .NET CF).HCI issues for software design on mobile devices and user interface development.Security and maintenance of mobile computing systems.Data persistence on mobile devices.

Networking (e.g. HTTP, Wireless Messaging, Bluetooth).Multimedia on mobile devices (graphics, sound, music, video, games).

Learning and Teaching Activities:

This course will be taught by a mixture of formal lectures and laboratory sessions. Lectureswill cover theoretical background and relating to application development for mobile devices.


36/38

36

Extensive examples will be shown to demonstrated taught principles and students will beexpected to take notes and apply the skills in the following lab sessions.The material introduced in lectures will be supported by practical laboratory sessions, whichform a framework for the implementation of the coursework assignment.The course will be supported by a number of directed unsupervised learning activities and alogbook.Student time (Excluding self-directed work) will be:

Lecture - 66% Laboratory - 33%

Assessment Details:


Weighting%

MinimumPass Mark

WordsLength

Outline Details

Coursework 80% 40 N/A Create a mobile application.

Test 20% 40 N/A

Core Texts:

T

ISBN Number Author Date Title Publisher

1 59059 479 7 Li, Sing&Knudsen, J

2005 Beginning J2ME: From Novice toProfessional

Apress


37/38

37


Code: COMP 1564 School: CMS 22.7 Course Title: Systems ProgrammingCourse Coordinator: Richard Anthony Level: 5 Credit: 15 Department: Computing and Information Systems Pre-requisites: N one

Pre-requisites: Level 1 Programming, Computer and Communication Systems or Computer Systems andInternet Technologies

Aims: This course introduces students to the concepts and techniques for designing and developingsoftware applications that communicate across a network. It aims:

To provide an introduction to the use of application programming interfaces in a variety of programming contexts to exploit the services offered by networks.To provide a theoretical background to the provision and control of distributed resources, andof the operation of networked operating systems.To give the student practical experience of engineering application software for networks.To introduce an understanding of the concepts of distributed system performance, appropriatemetrics and relevant factors affecting performance.

Learning Outcomes: A. Demonstrate a working knowledge of networking technology - hardware components,

protocols, standards, performance issues; the Internet - services and protocols.B. Understand how distributed systems name, distribute and control resources.C. Understand the need for, and operation of, core services in distributed systems.D. Be aware of performance issues in networks and distributed systems and be able to applythe knowledge in practical situations.E. Show competence in the use of the sockets application programming interface.F. Design, implement and test networked applications.

Indicative Content: TCP/IP and the Internet; discussion of the main protocols - TCP, IP, UDP, ARP, DNS etc.;addresses and ports; application protocols.Design development and debugging of network applications.Introduction to distributed application architectures and design (peer-peer, client server anddistributed objects) - performance and efficiency.Distributed Systems - transactions, atomicity and related concepts.Distributed Operating Systems - transparency, core services, distributed file systems.Introduction to middleware, web services and java beansDistributed algorithms - election algorithms, clock synchronization algorithms.Distributed applications - name servers, networked games, client-server software.The sockets API, blocking and non-blocking sockets, message buffering, point-to-point and

broadcast applications.

Learning and Teaching Activities: Concepts will be introduced in lectures and problem solving will be done through tutorials.Practical work will be through supervised laboratory sessions. Unsupervised, guided self-


38/38

study will extend the amount of time students spend doing practical laboratory activities.

Student time will be:Lecture 50%Tutorial 10%Laboratory 40%

Assessment Details:


GradingMode

Weighting%

MinimumPass Mark

WordsLength

Outline Details

Coursework 50 40 N/A Programming task

Exam 50 40 N/A Traditional closed bookexamination which is usedto assess understanding ofthe theory and concepts

aspects of the course.