Prerequisite Modules
Description
This module develops in the student
a theoretical and practical understanding of the software development
lifecycle as an engineering discipline. It gives the student an
overview of the development of a project from its inception right
through to its realisation. Using a relatively simple case study, the
student will analyse and specify requirements and design a partial
solution. The breadth of the module is confined to a single
methodology, with basic project management and testing techniques.
Aims
This module aims to introduce
student to the basic principles of software engineering. Specifically,
it aims to provide the student with the skills and knowledge to
identify and employ appropriate practices for the specification,
design, testing and operation of a system that requires many program
units.
Learning Outcomes
On successful completion of this
module, the student will be able to:
-
Gather and specify system
requirements, from a description of the current system and problems
inherent in it.
-
Design a new system, with a CASE
tool, using appropriate diagrams showing a system's function, data
and change over time.
-
Specify modules of the new system.
-
Test a program using a properly
specified unit test.
-
Design appropriate screens that
could be used by a function of the new system.
-
Have a sound appreciation of
testing and maintenance procedures.
Learning and Teaching Methods
Lectures, self-study, labs,
tutorials, and any combination of discussion, case study,
problem-solving exercises, readings, seminars, and computer-based
learning.
Content
Software Development Processes:
The software lifecycle, its phases and support activities.
Analysis:
Requirements gathering. notations used, module specifications and
interactions.
Design:
Module specifications and interactions, user interface design and HCI
design guidelines.
Testing:
Test case design, white and black box testing, unit testing,
integration testing, validation and system testing, user acceptance
testing.
Assessment
The methods of assessment to be used
to measure the learning objectives stated above are written
examination and continuous assessment including one or more of
assignment, essay, problem-solving exercise, oral presentation, and
class or lab tests.
-
Continuous Assessment: 30%
-
Examination: 70%
Recommended
Reading
-
David Avison & Guy Fitzgerald,
2003, Information Systems Development Methodologies, Techniques and
Tools, 3rd Ed., McGraw Hill.
-
Pressman, R Software Engineering,
A practitioner's approach, (European edition adapted by D. Ince)
McGraw-Hill Book Company, London, Latest edition
-
Britton, Doake, Software Systems
Development - A gentle Introduction, 3rd Ed. McGraw Hill, 2003
|
|
For more information contact
Ciarán O'Leary
|
Home