63IS2261d

FACULTY OF SCIENCE & ENGINEERING 63IS2261

UNIT TITLE Information Systems Development

UNIT CODE NUMBER 63IS2261

HOME PROGRAMME BSc Combined Honours (IS)

HOME DEPARTMENT Computing and Mathematics

SUBJECT AREA N213 Project Management G530 Systems Analysis and Design G520 Systems Design Methodologies

UNIT LEADER(S) Keith Miller/Martin Stanton

CREDIT VALUE 20 CREDITS AT LEVEL: 2

AMOUNT OF STUDENT EFFORT (HOURS)

200 CLASS CONTACT TIME (HOURS)

48

UNIT STATUS MANDATORY CORE BSc Combined Honours Information Systems

ELECTIVE: for students with the pre-requisite module

PRE-REQUISITES 63IS1264 Data Analysis and Database Design

CO-REQUISITES None

UNIT LEARNING OUTCOMES

On successful completion of this module a student will be able to: • Appraise alternative approaches to the development of information

systems. • Understand the principles of object-orientation in the context of

analysis and design. • Understand the principles of prototyping and apply a rapid

application development method. • Apply project management techniques in order to plan, monitor and

control an IS project. • Assess the importance of risk, cost and quality in an IS project.

CURRICULUM OUTLINE

Method criticism: (10%) • Appraisal of methods introduced.

Object-oriented analysis and design (40%) • Principles of object-orientation • Application of an OOA&D method; • Overview of alternative methods • Transition from design to implementation • OO project management issues.

Prototyping: (15%) • Rationale for and principles of prototyping; prototyping

approaches; techniques (e.g. JAD, storyboarding, JRP); • Overview of tool support (application generators, CASE, 4GLs); • Principles of Rapid Application Development and examination of a

RAD method (e.g. DSDM);

G:\Def Doc Units\BSc Eng + Tech\63IS2261.doc Issue 1 March 2004 Page 1 of 3 A A Verwer


• Prototype construction and evaluation • Managing prototype development.

Project Management: (35%) • Planning and control concepts • Project planning techniques (e.g. Gantt/PERT charts) • Monitoring and change control • Software support • Cost/Benefit analysis • Quality and quality assurance • Risk analysis • Behavioural aspects (e.g. team organisation and leadership)

TEACHING AND LEARNING STRATEGIES

Students will be taught through a mixture of formal lectures laboratory sessions and tutorials. Lectures will provide the core material for the module and will take about 50% o the module contact time. These will be supported by appropriate tutorials and lab sessions in which concepts will be further developed, and practical skills will be developed.

ASSESSMENT STRATEGIES

Summative Assessment

End of Module Examination 60% Coursework 40%

Formative Assessment

In addition to the aforementioned coursework, this will take the form of exercises which are carried out during lab sessions and which develop the students’ understanding of the concepts and their ability to use appropriate software tools.

ASSESSMENT CRITERIA FOR UNIT/ELEMENTS OF ASSESSMENT

The examination assessment will be based on all areas of the syllabus and will allow students to demonstrate their ability to apply the concepts to small problems and scenarios. The coursework will involve two components, typically.

i) A short test Examines the students’ ability to apply OO techniques correctly and consistently to a set of scenarios.

ii) A team IS development project Gives the students an opportunity to apply correctly and consistently project planning techniques and OO techniques to the development of an information system in a team environment.

INDICATIVE STUDENT LEARNING RESOURCES

Books • D E Avison and G Fitzgerald Information Systems Development:

(3rd edition) McGraw Hill, 2003 • J Cadle, and D. Yeates. Project management for information

systems 3rd edition. Financial Times/Pitman 2001 • P Stevens, R Pooley, Using UML: Software engineering with

objects and components 3rd edition. Addison Wesley 2000 • M fowler, K Scott, UML distilled 2nd Edition, Addison Wesley 2000 • R Pressman Software Engineering: A Practitioner’s Approach (5th

edition) McGraw Hill, 2000 • Booch, Rumbaugh, and Jacobsen Unified Modelling Language User

Guide Addison Wesley, 1998 • Graham and Llewellyn-Jones Requirements Engineering and Rapid



Development Addison Wesley, 1998 • J Stapleton DSDM Dynamic Systems Development Method

Addison Wesley, 1997 • K Lockyer, J Gordon Project Management and Project Network

Techniques, Financial Times/Pitman, 1996. • M Cotterell and R Hughes Software Project Management Int.

Thompson Computer Press, 1995 • I Graham Object Oriented Methods (2nd edition) Addison Wesley,

1994 • J Rumblaugh, J Blaha, M Premalani, F Eddy, and W Lorenson

Object Oriented Modelling and Design Prentice Hall, 1991 • M F Smith Software Prototyping; adoption, practice and

management McGraw Hill, 1991

Web Resources • UML Resource Center

http://www.rational.com/uml/index.shtml


http://www.rational.com/uml/index.shtml

Documents

63IS2261d