Faculty of Informatics
BUSS211 – Requirements
Determination and Systems Analysis
Subject Outline
Autumn Session 2007
Head of
School –Associate Professor Peter Hyland, Student Resource Centre, Tel: (02)
4221 3606
|
Dr Leone
Dunn |
|
|
Telephone
Number: |
3821 |
|
Email: |
|
|
Location: |
40.250 |
Dr Dunn’s Consultation
Times During Session
|
Day |
Time |
|
Tuesday
Wednesday
|
1030-1230 1430-1630 |
Subject
Organisation
|
Session: |
Autumn
session, Wollongong Campus |
||||||
|
Credit
Points |
6 credit
points |
||||||
|
Contact
hours per week: |
2L,2T/CL |
||||||
|
Lecture
Times & Location: |
|
||||||
|
Tutorial
Day, Time and Location can be found at: |
|
||||||
|
Week |
Topics Covered |
|
|
1 |
Introduction
to the Subject |
Chapter
1 |
|
2 |
BSA
In Context |
Chapter
2 |
|
3 |
Investigation |
Chapter
4 |
|
4 |
Modelling
Techniques |
Chapter
5 |
|
5 |
“ |
Chapter
5 |
|
6 |
“ |
Chapter
6 |
|
7 |
“ |
Chapter
7 |
|
8 |
“ |
Chapter
7 |
|
RECESS |
|
|
|
9 |
Walkthroughs,
Critical Appraisals |
Chapter
8 |
|
10 |
Business
System Specification |
Chapter
8 |
|
11 |
BSA
as Project Manager |
Chapter
3 |
|
12 |
Other
Topics in BSA, Presentation of Results |
|
|
13 |
Review |
|
Students
should check the subject’s web site regularly as important information,
including details of unavoidable changes in assessment requirements will be
posted from time to time. Any
information posted to the web site is deemed to have been notified to all
students.
This subject aims to introduce the student to the techniques and
technologies of structured systems analysis. It examines the complementary
roles of systems analysts, clients and users in life cycle development methods.
Data flow analysis and process descriptions are introduced and the relation to
object orientation examined. The student will make use of a Computer Aided
Software Engineering (CASE) tool to document solutions to typical problems.
On successful completion of this subject, students should be
able to: demonstrate an understanding of the origin and development of formal
systems analysis methods; demonstrate an ability to analyse the key elements of
a narrative and interview; demonstrate an appreciation of the relationship
between information strategy and organisational structure; information systems
requirements and organisational objectives; complementary roles of clients,
users and analysts in the development of computer based information systems and
demonstrate an ability to analyse a system and present a system description,
demonstrate an appreciation of CASE tools as an aid to systems modelling.
Attendance
Requirements
It is the responsibility
of students to attend all lectures/tutorials/labs/seminars/practical work for
subjects for which you are enrolled.
Attendance
and participation in lectures, tutorials and web-mediated activities is a
requirement for the successful completion of this course. Failure to do so may result in a fail grade
being recorded. A good indicator of
satisfactory attendance is approximately 80% of the allocated contact
hours. Attendance per se is not an
assessable component of the course.
It should be noted that according to Course Rule 003{Interpretation Point 2 (t)} each credit point for a single session subject has the value of about two hours per week including class attendance. Therefore, the amount of time spent on each 6 credit point subject should be at least 12 hours per week, which includes lectures/tutorials/labs etc
Satisfactory
attendance is deemed to be attendance at approximately 80%* of the
allocated contact hours. Attendance rolls may be kept for lectures, TUTORIALS and laboratories. If you are
present for less than 80%* you need to apply for special consideration,
otherwise a fail grade may be recorded.
Students
MUST attend their allocated tutorial
unless they have the written permission of the subject coordinator.
This subject consists
of 2 hours of lectures and 2 hours of
tutorials/computer labs.
Subject
Materials
These readings/references are recommended only and are not intended to be an exhaustive list. Students are encouraged to use the library catalogue and databases to locate additional readings
This subject has the
following assessment components.
|
Assessment Items & Format |
Percentage
of Final Mark |
Due Date |
|
Assessment
1 Tutorial Worksheets |
5% |
Tba (Group work) |
|
Assessment
2 Major Assignment in 3 Parts |
25% |
Tba (Group work) |
|
Mid Session Test |
20% |
Week 7 During Lectures (Individual work) |
|
Final Examination |
50% |
Exam Period
(Individual work) |
Scaling
Final results in this subject may be scaled. The scaling method that will be used in this subject is as follows.
If
E is the student exam mark, and A is the student assignment mark, the student
final mark will be determined as follows:
if E >= 40% of the
maximum exam mark: then student final mark is E + A;
if 35% <= E < 40%
of the maximum exam mark: then student final mark is /min/{E+A, 47};
if E < 35% of the maximum exam mark: then
student: final mark is /min/{E+A,
42}.
Students must refer to the Faculty Handbook or online references which
contains a range of policies on educational issues and student matters.
Please note that if this is your last session and you are granted a supplementary exam, be aware that your results will not be processed in time to meet the graduation deadline.
Plagiarism
When you submit an assessment task, you are
declaring the following
1.
It
is your own work and you did not collaborate with or copy from others.
2.
You
have read and understand your responsibilities under the
3.
You
have not plagiarised from published work (including the internet). Where you
have used the work from others, you have referenced it in the text and provided
a reference list at the end ot the assignment.
4.
Plagiarism
will not be tolerated.
5.
Students
are responsible for submitting original work for assessment, without
plagiarising or cheating, abiding by the University’s policies on Plagiarism as
set out in the Calendar under University Policies, and in Faculty handbooks and
subject guides. Plagiarism has led to the expulsion from the University.
This outline should be read in conjunction with the following documents:
|
Code of
Practice - Teaching and Assessment http://www.uow.edu.au/handbook/codesofprac/teaching_code.html |
Key Dates |
|
Code of
Practice - Students http://www.uow.edu.au/handbook/codesofprac/cop_students.html |
Information
Literacies Introduction Program |
|
Acknowledgement
Practice Plagiarism will not be
tolerated |
Student
Academic Grievance Policy http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8 |
|
Special
Consideration Policy http://www.uow.edu.au/handbook/courserules/specialconsideration.html |
Code of
Practice-Honours |
|
Non-Discriminatory
Language Practice and Presentation |
Intellectual
Property Policy http://www.uow.edu.au/research/researchmanagement/1998IP.html |
|
Occupational Health and Safety http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf |
SISAT
Internet Access & Student Resource Centre http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml |
|
SISAT
Computer Usage Rules http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml |
SISAT Style
Guide for Footnotes, Documentation, Essay and Report Writing |
|
SISAT
Student Guide |
Informatics
Faculty Librarian, Ms
Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au |
|
SISAT
Subject Outlines |
|