New Module Form

burgerraraSoftware and s/w Development

Nov 18, 2013 (3 years and 8 months ago)

70 views

Draft Created by Syllabus Team as part of Academic Simplification

2012/2013

Page
1



New Module Form


Essential Information Required for
Module Manager


ACADEMIC YEAR
___________

Module Detail


Title

Object Oriented Software Design and Development

(maximum
50 characters)

Description

Principles of object oriented software design. Boundary, Control and Entity objects.
Use Case Diagrams, Subsystems and Architecture Design patterns
for software
design: Singleton, Observer, Adapter and Proxxy. Multi
-
threading and
concurrency. Static code analysis

and
automated unit testing
.

(brief description
of the
content of the module

between 75


150 words)

*Note Field to indicate

taught through Irish/English/Erasmus







Course Instances (s)


1SD3




















Module version number and date approved

*

xx/xx/2012


xx/xx/2012


xx/xx/2012

Date Retired


Module Owner / Lecturer

Dr Jim Duggan

E:mail: james.duggan@nuigalway.ie

Ext: 3336

Module Administrator Details

Mary Hardiman

E:mail: info@it.nuigalway.ie

Ext: 3836/3143


Please specify main contact person
(s)

for exam related queries and contact number /email


Module Code




(
Office use only)

Module Type

Core= Student must take the

module


Optiona
l = Choice for Student



Optional for









Core for

1SD3

ECTS

Multiple of 5 ects

5 ects

Course Requirement





































(i.e. where a module has to be passe
d at 40%)

Semester Taught


Semester 2

Semester Examined

Semester 2


Requisite(s)

Co
-
Req.

If they take module X they must
take module Y

Modules 




















Pre
-
Req


The student must have taken and
passed a module in previous year


Modules 













Excl.Req.

If they take module X they
CANNOT
take module Y


Modules 

























Module Assessment

1
st

Sitting


2
nd

Sitting

Assessment Type

Written Paper



Written Paper



Exam Session

Semester 2



Autumn



Duration

2 Hours



2 Hours





Bonded Modules

(modules which are to be
examined at the same date and
time)









































Draft Created by Syllabus Team as part of Academic Simplification

2012/2013

Page
2


PART B











Module Schedule

No. of Lectures

Hours

24

Lecture Duration

1 hour

No. of Tutorials

Hours







Tutorial Duration







No. of Labs

Hours

24

Lab Duration







Recommended No. of self study
hours







Placement(s)

hours







Other educational
activities
(Describe)

and hours allocated







*
Total range
of hours to be automatically totalled (min amount to be hit)



Module Learning Outcomes


(CAN BE EXPANDED)

On successful completion of this

module the learner should

be able to:

1
Understand the core principles of object oriented software design

2
For a given problem, identify and specify bound
ary, control and entity objects

3
Construct UML diagrams, including class diagrams, collaboration diagrams and
sequence diagrams

4
Understand the structure of key design patt
erns: Singleton, Proxy, Adapter and
Oberver.

5
Create a multi
-
threaded programming with concurrency features.

6
Understand static code analysis, automated unit testing and continuous intergration.

7






8







Module Learning, Coursework and Assessment

Learning Outcomes at module level should be capable of being assessed. Please indicate assessment methods and the outcomes th
ey will assess

Assessment
type
,
eg. End of year exam, group project

Outcomes
assessed

% weighting

Written Paper





1,2,3,4,5


4,5,6









70


30









Indicative Content

(Marketing Description and content)

This course provides students with an inisght into how they might successfully
navigate the terrain for designing, building and maintaining software systems. Case
studies are used to show how real world softwa
re development is conducted, and its
bottom
-
up approach help students to learn the material incrementally.




Module Resources


Suggested Reading Lists

Bruegge and Dutoit: "Object
-
Oriented Software
Workload:

ECTS credits represent the student workload for the programme of study, i.e. the total time
the student spends engaged in learning activities. This includes formal teaching, homework,
self
-
directed study and assessment.


Modules are assigned credits that are whole number multiples of 5.

One credit is equivalent to 20
-
25 hours of work. An undergra
duate year’s work of 60 credits is
equivalent to 1200 to 1500 hours or 40 to 50 hours of work per week for two 15 week
semesters (12 weeks of teaching, 3 weeks study and formal examinations).


Draft Created by Syllabus Team as part of Academic Simplification

2012/2013

Page
3



Engineering: Using UML, Patterns and Java"

Library







Journal







Physical

(e.g. AV’s)







IT

(e.g. software + version)







Admin










FOR COLLEGE USE ONLY

Student Quota

(where applicable only)

Quota

(identify number per module where applicable only)

Module:






Number:






Discipline involved in Teaching

*
(drop down for disciplines within school)

Discipline of Information Technology

Share of FTE

*
(% out of 1)

100%

RGAM



NB:

Notes on some fields are for the technical side when considering which
software

company to use.