Module Code: ELEC2600
Title: Software Engineering
Number of Credits: 10
Semester: 1
Year Running: 2000/2001
Programmes: Compulsory for: BEng(Hons) / MEng programmes in the School of Electronic and Electrical Engineering. BEng / MEng Mechatronics
Prerequisites: Software Development ELEC1600 and Software Development Laboratory 1N2 ELEC1820 .
Corequisites: None.
Objectives: On completion of this module, students should be able to: Describe the basic models of the software life cycle, e.g. the waterfall model, the prototyping model, and the spiral model. Explain the importance of the different phases of the software life cycle, e.g. analysis, design, implementation, testing and maintenance. Interpret environment models for computer systems presented using standard methods, such as context diagrams and use case diagrams, and produce environment models for simple computer systems. Interpret behavioural models for process oriented computer systems based on data flow diagrams, process narratives and state transition diagrams and produce behavioural models for simple process oriented computer systems . Describe the basic concepts of object oriented software development, such as classes, objects, inheritance, operator overloading etc.. Interpret class diagrams which show the static relationship of classes both in the problem domain and as the description of an object oriented computer system. and use class diagrams to represent simple systems. Interpret activity diagrams used to describe a system activity, and draw activity diagrams for simple operations. Interpret interaction views drawn using sequence and collaboration diagrams, and draw interaction views for simple systems.
Syllabus: Introduction to Software Engineering: Reasons for using software engineering techniques. Different phases of software development and how they relate to each other in the software life cycle. Structured Software Engineering: Environment modelling using Context Diagrams and Use Cases. Behavioural modelling using Data Flow Diagrams, Process Narratives, State Transition Diagrams. Structure Charts for code organisation modelling. Object Oriented Software Engineering: Introduction to the concepts of class, object, inheritance and operator overloading. Object oriented analysis using UML based notation (class-, activity-, interaction- and sequence diagrams). Object Oriented Design. Using C++ for implementing object oriented systems.
Form of Teaching: Lectures: 22 x 1 hour.
Assessment: 2 x tests each 10%; 1 x 2 hour examination 80%.
| Module Search System | Geoff Richards <ctzgpr@comp.leeds.ac.uk> |