You are on page 1of 12

CSI341: Introduction to Software Engineering

The course aims to introduce you to: principles of software engineering why engineer software but not produce software artistically. Assumptions students MUST have taken at least two courses from: structured programming discrete mathematics data structures and abstraction

The course is comprised of lectures, exercise, group assignment, tests and an examination.

Any piece of work to be submitted should be formatted (and where necessary printed) neatly and submitted on time. No late submissions, unless with officially valid reasons will be accepted.

Mode of assessment Course assessment mark will comprise of :1.

one nine week long group assignment.


Two (one hour) tests

finally a two hour examination

Assessment 1. Attendance of scheduled classes 2. Printed (where required electronic) copy of assigned pieces of work. - any piece of work not printed (or not in electronic version) when required will score 0. - no pieces of work submitted late without valid reasons, will be considered. - duplicate pieces of work will score 0 CA : Exam ratio 1: 2

Piece of work Test 1 Assignment (group)

Likely due date first lecture week 7 1000hrs Monday of every second week starting in week 4 First lecture in week 10 ?/Nov- Dec/2011 Exam slot: 1ii

Test 2 examination

Group assignment


This week and before the last lecture in week 2, formation of groups (five students per group). Each group should register a system to work on before the 2nd lecture in week 3 Every Monday before 1000hrs (as from week 4) each group should submit a set of documents (milestone deliverables)

CSI341 Deliverables should include:

scheduled or planned event; venue; time and duration actual time (includes date if necessary) and duration Member participation and contribution actual (if any) lost time; risks and how they were alleviated

UML centered modelling tool 5 minutes group project demo and presentation at end of semester

Wk2 s/w systems; qualities; s/w development process; documentation of s/w development process & product Wk3 Project Management overview; Introdn to walkthroughs as validation tool; CASE tools overview Wk4 requirements engineering; system models overview (data-oriented & processoriented) requirements specn --- specn walkthrough; s/w requirements document Wk5 Introdn to formal specn
Wk6 software design (preliminary design); function-oriented design methodologies

Wk8 Wk9

object-oriented design methodologies

software design with reuse s/w reliability; programming for reliability

Wk10 implementation strategies testing process (verification, validation, debugging)

Wk11 legacy systems and software reengineering; elementary proof of correctness configuration management
Wk12, Revision ; Demo & presn of group projects 13 (5 minutes each)


Sommerville I, Software engineering, Pearson, 9 ed, 2010 Lethbridge T, and Laganiere R, Object-Oriented Software Engineering, McGraw-Hill, 2 ed, 2005 Rational Rose or Visual Paradigm (UML centered) modelling tools

Other useful materials (URLs have been provided as well) include:

The Capability Maturity Model Integration for Software processes Pressman R, Software engineering : a practitioner's approach, McGraw Hill, 2001 --- a must as well for a s/w engineer

ISO, IEEE and National standards as pertain to s/w


Other useful materials (URLs have been provided as well) include:

Park, Robert E., Wolfhart B. Goethert, and William A. Florac, Goal-Driven Software Measurement - A Guidebook. CMU/SEI-96-HB-002. Pittsburg, PA: Software Engineering Institute, Aug. 1996. from

Browse through this before the next lecture, especially chapter 2 foundations of software measurements

A number of journals which include:

Software engineering Software : practice & experience IEEE transactions on reliability IEEE transactions on software engineering IEEE software ACM Transactions on Software Engineering and Methodology Information and Software Technology