Transcript 1 DEV 4 LEARNER GUIDE 2016

WALTER SISULU UNIVERSITY
LEARNER GUIDE
FACULTY
: SCIENCE, ENGINEERING AND TECHNOLOGY
DEPARTMENT
: INFORMATION TECHNOLOGY
QUALIFICATION
: BACHELOR OF TECHNOLOGY IN INFORMATION TECHNOLOGY (SD)
QUALIFICATION CODE : Bachelor of Technology in Information Technology
SUBJECT
: DEVELOPMENT SOFTWARE IV
SUBJECT CODE
: DEV41P0/ DEV41B0
COMPILED BY
: Mr. P A TAMBA TAMBA
………………………………………………………………
1 of 10 Development Software 4 (2016)
TABLE OF CONTENTS
PAGE
1. GENERAL INFORMATION
1.1 Welcome and introduction
1.2 Department information
1.3 Lecturer information
1.4 General course information
1.5 Roles, responsibilities and attendance requirements
1.6 Class representatives and complaint procedures
1.6 Learning
Learning and
and teaching
teaching strategies
1.7
strategies
1.8 Assessment
1.9 Learning materials and stationery requirements
3
3
4
4
4
5
5
5
6
1.10 Plagiarism
7
2. TECHNICAL COMPONENT
2.1 Course Information
2.2 Learning assumed to be in place and recognition of prior learning
2.3 Admission requirements and pre-requisites
2.4 Course exit level outcomes
2.5 Critical cross-field outcomes
2.6 Assessment criteria
2.7 Moderation
7
7
7
8
8
8
9
3. LEARNING COMPONENT
3.1 Modules and specific outcomes
…………………………………………………………………………………………………
2 of 10 Development Software 4 (2016)
9
1. GENERAL INFORMATION
1.1 Welcome and Introduction
On behalf of Walter Sisulu University, the Faculty of Science, Engineering and Technology and the
School of Computing, we would like to welcome you to the Information Technology programme and
especially to Development Software 4. Computing skills play an increasingly vital role in almost all
occupations, and contribute to productivity gains, innovation and employment growth across all South
African and international industries. The academic focus of the School is to offer programmes specifically
aimed at preparing students for the workplace by offering training that will enable diplomates and
graduates to demonstrate competence, knowledge and judgment in addressing discipline related
problems.
Please consult the School of Computing Prospectus for a description of the different specialisations and
information about all of the courses offered in the B.Tech program in the Information Technology
Department.
Development Software 4 is one of the required courses on the first semester to complete the B.Tech
program. It aims at giving the IT post graduate student an advanced on data structure and Object
Orientation methodologies and features. It enables the students to handle industrial system development
using the Object Oriented techniques.
The purpose of this Learner Guide is to provide you with written guidelines as to what to expect of the
University and what the University in turn expects of you, with regard to this course. In Section 1 you are
given administrative details of the Department as well as the contact details of the lecturer teaching this
course. The general course information shows you the number of lecture, practical and tutorial periods a
week and provides information about additional time you will be expected to spend on course-related
work. The responsibilities of the students with regard to participation and attendance are stated and an
overview is provided of the learning and teaching approach. Comprehensive assessment details for the
course are given in this section as well as details of the materials that will be used, e.g. text books. In
Section 2 full technical details of the purpose of the qualification, course entry requirements and NQF
level, assessment criteria and moderation are provided, as well as the exit level and critical cross-field
outcomes for the course. In Section 3, the modules and specific outcomes are shown.
1.2 Department Information
Delivery
Site
Head of Department
Mr J Lukose
Chiselhurst
Head of Department
Mr M Jaza
Ibika
Department Secretary
Ms A Ndaliso-Roji
Ibika
Secretary
Ms U Mtshizana
Chiselhurst
Office
No.
3 of 10 Development Software 4 (2016)
Telephone
Email / Fax
043 709 4047
[email protected]
047 401 6347
[email protected]
047 401 6232
[email protected]
Fax:
043 708 5207
[email protected]
1.3 Lecturer Information
Mr. PA Tamba Tamba
047 401 6270
[email protected]
Ibika
1.4 General Course Information
Duration of the course
Module
Semester
Part-time OR
Full-time
Year
Formal Contact Time – attendance at all classes is compulsory
Theory
50 x 45 minute periods
Practical
20 x 45 minute periods
Non Contact Time
Students are expected to spend at least 5 hours a week completing work outside of the formal contact
time. This includes the self study times in the library and any other consultations with lecturers, group
discussion, etc
Experiential Training/Service Learning/Work Integrated Learning
There is no WIL component in this course.
1.5 Roles, Responsibilities and Attendance Requirements
According to University Policy all lectures must be attended punctually and regularly. Registers will be
taken at all classes and filed for future reference. Participation is an important part of the class sessions.
Participation means both attendance and engagement. Students are expected to attend and fully
participate in all the scheduled classes, group learning opportunities, discussion sessions and practical
sessions. In addition, punctuality is important. Learners are expected to be on time and ready to begin at
the stated time on the timetable.
Learners who are not able to attend a formal contact session must provide the lecturer with a written note
explaining their non-attendance. These notes will be kept in the course file in case queries regarding a
student’s poor performance are raised.
See 1.8 below for details regarding the submission of medical certificates for missed tests, late
assignments, etc.
As stated in 1.4 above, learners are also expected to spend an additional minimum of 5 hours a week
completing homework exercises, revising work completed and preparing for classes and tests.
Misunderstandings about course content or failure to understand a topic can often be cleared up in oneon-one sessions with the lecturer and learners are urged to consult their lecturers if they have any
queries, etc. It is also important for a lecturer to be aware of any personal problems which may affect a
learner’s performance.
Learners are requested to make appointments to meet with lecturers during the available consultation
times. As this will not always be possible, however, lecturers are also expected to make time to meet with
learners in ‘emergency’ situations.
4 of 10 Development Software 4 (2016)
Lecturers are expected to attend all scheduled contact classes. If possible, notice will be given if a
lecturer cannot attend a class and arrangements will be made by the lecturer to cover the work missed.
1.6 Class Representatives and Complaint Procedures
It is university policy that each class should elect two class representatives at the beginning of each year.
One of the roles of the class representatives is to convey information from the lecturer/department to
other students. The class representatives might also be called upon to represent the learners in meetings
with Department/School staff and/or management.
The correct procedure for any learner who has a complaint about a lecturer or course is for the learner
a. Firstly to approach the lecturer and attempt to resolve the issue.
b. If this is unsuccessful, the learner should complete a student complaint form (available from the
secretary) and take the issue to the Site Head of Department.
c. If the matter is still not resolved it may be escalated to the Head of Department.
d. If many learners in a class have a problem with a lecturer or course, the problem must be detailed
on a student complaint form and the form should be passed to the class representatives who
should act on behalf of the learners by first approaching the lecturer and then, if necessary,
escalating the problem to the Site HOD and then the HOD.
1.7 Learning and Teaching Strategies
The University has adopted an OBE approach to teaching and learning. Consequently, teaching and
assessment strategies endeavour to be learner-centred, interactive and applicable to the future career
towards which this programme of study is directed.
Due to the adoption by the university of the e-learning component in teaching and learning, this course
content is also available on the WiSeUp e-learning platform to complement the formal contact time in
class. More information will be given in class by the lecturer.
1.8 Assessment
Formative Assessment
This type of assessment will be used to inform both the learner and the lecturer and will not be allocated a
mark. It will be used to allow the learner and lecturer to monitor his/her progress in achieving the course
goals and specific module outcomes. It will take the form of self-review, peer review and lecturer review
and should be seen by the learner as a valuable learning aid. It will also be used to provide valuable
feedback to the lecturer regarding his/her instruction techniques, topics that require revision or additional
attention, etc. This feedback will be mostly given during the project presentation stages.
Summative Assessment
This type of assessment is used to formally measure the learning of particular skills, knowledge and
understanding and is associated with a recorded mark.
Development Software 4 is a semester course which is exam-based.
All summative assessments will count towards the Duly Performed (DP) mark).
All summative assessments for this subject will be common across all delivery sites at which the course is
offered – unless this is prevented by unforeseen circumstances.
Medical certificates regarding missed tests and/or assignments, etc. must be submitted to the lecturer or
site department secretary within 7 working days of the test date or due date. Medical certificates not
received within 7 days will not be considered – unless the learner was hospitalised.
5 of 10 Development Software 4 (2016)
Complaints or queries about assessment marks must be raised with the lecturer concerned within 7 days
of the assessment being returned to the students.
Composition of the DP mark
The DP mark for Development Software 4 will be calculated from summative tests (2 are proposed) and
from assignments or projects, and presentations as weightings below.
Examination
Assessment Area
Presentations
Projects/Assignments
Tests
Weighting
20%
30%
50%
There will be a 3 hours written examination at the end of semester.
According to University policy, entrance into the examination is subject to a minimum DP mark of 40%.
The minimum mark required to pass an examination is 40%. If a learner scores below 40% in the
examination, he/she does not qualify for a final mark and does not pass the course.
Final Mark (before supplementary examination)
The Final Mark is calculated as follows:
DP
40%
Examination
60%
Total:
100%
A learner must score at least 50% for the final mark (calculated as shown above) in order to pass the
course.
Supplementary Examination
There will be a NO supplementary examination.
Re-mark requests, absence from examination due to illness, special examinations, etc.
See General Prospectus for rules pertaining to these.
1.9 Learning Materials and Stationery Requirements
Prescribed Textbook:
Brocks R W, Wilkerson B and Wiener L (2003) Designing Object-Oriented Software, Prentice-Hall, ISBN
0 136298257
Carrano F M, Savitch W (2003) Data Structures and Abstractions with Java, Pearson Education, ISBN 013-017489-0.
6 of 10 Development Software 4 (2016)
1.10 Plagiarism
The standard Harvard Referencing system is used at Walter Sisulu University – details are available on
the University Intranet and from the Resource centre.
Students who submit work which has not been adequately referenced but who have clearly used
information from textbooks, research articles, newspapers, magazines and internet pages will be held to
be in breach of the plagiarism and copyright act which is a criminal offence. Plagiarised work will not be
accepted for marking and students may be subjected to disciplinary action.
2. TECHNICAL COMPONENT
2.1 Course Information
2.1
COURSE
Development Software 4
2.1.1
CREDIT VALUE
12 credits
2.1.2
NQF LEVEL
7
2.1.3
FIELD
10 - Physical, Mathematical, Computer and Life Sciences
2.1.4
SUB-FIELD
Information Technology and Computer Sciences
2.1.5
PURPOSE OF THE COURSE
The course is designed to equip learners with a solid understanding and application of Object
Oriented (OO) Programming methodologies and features including OO analysis and design
using UML, design Pattern, components, and subject and aspect oriented programming.
2.1.6
PURPOSE STATEMENT OF THE QUALIFICATION
Bachelor of Technology: Information Technology
A qualified learner at this level is competent in applying Object Oriented design principals in
solving a program, development, implementation and/or maintenance strategies and
techniques in the development of Information Technology solutions
2.2 Learning Assumed To Be In Place and Recognition Of Prior Learning
A student may apply for Recognition of Prior learning in accordance with the WSU RPL Policy. Contact
the Head of Department for details.
2.3 Pre-Requisites
INTERNATIONAL STUDENTS
Applications from international students are considered in terms of the institutional equivalence
reference document and (where required) submission qualification to SAQA for benchmarking in terms
of HEQF.
MATURE AGE ENDORSEMENT
see General Prospectus.
RECOGNITION OF CREDITS FROM OTHER INSTITUTIONS
Not more than 50% of subjects in the Diploma may be exempted in this way
All exit level subjects should be done in the department. One exit level subject may be recognized
provided prior permission to register for that subject at another institution is sought by the student from
Senate. Also See General Prospectus.
7 of 10 Development Software 4 (2016)
ACADEMIC EXCLUSION
See General Prospectus, Faculty Prospectus and School Prospectus for details.
PRE-REQUISITES
It is required that the learner has passed all courses of the National Diploma IT in major in Software
Development or equivalent.
2.4 Course Exit Level Outcomes
Exit Level Outcome 1 (ELO 1)
The learner will be able to have the Knowledge to analyze and design software systems using Object
Oriented techniques
Exit Level Outcome 2 (ELO 2)
The learner will be able to develop the necessary skills to implement object oriented techniques using an
object oriented language of choice
2.5 Critical Cross-Field Outcomes (CCFO)
a) The learner should be able to solve problems, which involves:
i. Making the problem clear
ii. Completing the problem solving process
iii. Anticipating the problems that might arise
iv. Evaluating the problem solving process and solutions
v. Learning from experience
b) The learner should work with others, which involves:
i. Understanding the purpose of group work
ii. Taking notes, listening to others, debating points of view, being culturally sensitive
iii. Reaching a conclusion
c) The learner should successfully manage themselves and their activities, which involves:
i. Deciding on what is most important (prioritising)
ii. Checking the quality of work presented for evaluation
iii. Being responsive to changing circumstances
d) The learner should collect, analyse and organise information, which involves:
i. Getting information from different sources
ii. Piecing the information together into some sense-making
iii. Evaluating the goodness of the information
iv. Categorising information
v. Develop reading skills and practise using manuals, the Internet and online help text for research
and investigation and to increase their knowledge
e) The learner should communicate effectively, which involves:
i. Develop oral and written communication skills to make effective presentations and write reports
f) The learner should use technology effectively and critically, which involves:
i. Knowing the uses of technology
ii. Knowing the science behind the technology
iii. Knowing the broader impacts of using the technology
2.6 Assessment Criteria
Each summative assessment during the semester will assess how well the learner has achieved the
outcomes of specific modules (see below). The final examination will assess how well the learner has
achieved the exit level outcomes of the course and the specific outcomes of all of the modules.
8 of 10 Development Software 4 (2016)
2.7 Moderation
All summative assessment question papers and memoranda for are internally moderated during the year.
The final examination question papers and memoranda are externally moderated in accordance with
university rules.
3. LEARNING COMPONENT
3.1 Modules and Specific Outcomes
MODULE 1:
Object oriented programming and methodologies
Specific
outcomes:
On completion of this module, learners should be able to
a. Know the concepts of Object Oriented Programming.
b. Understand the terms used in Object Oriented Programming.
c. Appreciate the needs of an Object Oriented Programming
approach.
d. Familiarize with the different Object Oriented Languages.
e. Appreciate the advantages of Object Oriented technology.
Estimated
Duration:
References:
2 weeks
MODULE 2:
Specific
outcomes:
Object Oriented Analysis and Design
On completion of this module, learners should be able to
a. Learn the rules for effective Object Oriented Source Structure
and Packaging.
b. Analyse and design solution bzn principles using packages as
the granule to reduce complexity.
c. Appreciate the effective use of packages and their
interdependencies as one of the most powerful tools of Object
Oriented Programming to manage complex projects.
d. Open-closed principle to yield the greatest benefits of Object
Oriented Technology – reusability and maintainability.
e. Understand the Use Case, Object Modelling and sequence
diagramming notations of UML, how object modelling maps to
Object Oriented Programming languages, and how these and
notations hang together to complement each other.
Estimated
Duration:
References:
3 weeks (with continued exercises)
MODULE 3:
Specific
outcomes:
Analysis and design patterns
On completion of this module, learners should be able to
a. Learn the fundamentals of Design Patterns, Creational Patterns,
Partitioning Patterns, Structural Patterns, Behavioral Patterns
and Concurrency Patterns and their uses.
Study Aid (handout)
Study Aid (handout)
9 of 10 Development Software 4 (2016)
b. Create patterns in Java.
Estimated
Duration:
References:
3 weeks (with continued exercises)
MODULE 4:
Specific
outcomes:
Components
On completion of this module, learners should be able to
a. Know the similarities and differences of objects and components.
b. Understand the Basic Beam Concepts.
c. Create Java Beans.
d. Understand the similarities and differences between Bean and
applets
3 weeks (with continued exercises)
Estimated
Duration:
References:
MODULE 5:
Specific
outcomes:
Estimated
Duration:
References:
Study Aid (handout)
Study Aid (handout)
Subject and Aspect oriented programming.
On completion of this module, learners should be able to
a. Understand the subject oriented and aspect oriented
programming concepts from Object Oriented Programming
1 weeks (with continued exercises)
Study Aid (handout)
10 of 10 Development Software 4 (2016)