Software Engineering

Prerequisities: students should be able to program in one of object oriented languages (e.g. C++, Java). Software engineering course starts with definition what software engineering is. The software process is described and models of software process are presented (waterfall, evolutionary development, formal transformations, system assembly from reusable components), agile methods. The difficulties of project management are pointed out. Requirements engineering and analysis are discussed. The unified modeling language (UML 2.x) is studied in more details. In the final part of this course verification, validation and reliability of software are addressed. Methods of software testing and inspection are introduced. Techniques of reliable software production are briefly described. Formal specifications of software is presented. Software metrics and cost estimation methods are also presented. Classes have been prepared and are conducted with the use of presentation and discussion techniques.

Lecture contents

• Introduction to software engineering, software quality.


• Models of software process: waterfall, exploratory, reuse, rapid
  prototyping, spiral, incremental, agile.


• Feasibility study, scheduling, project manegement, Prince2.


• Requirements analysis: functional and nonfunctional requirements
  specification.


• Advantages of object approach, UML 2.x - unified modeling language:


• Use case view of a system, use case diagrams.


• Logical model: class diagrams, interaction diagrams, state
  machine diagrams, complex states, activity diagrams.


• Implementation model - components and deployment diagrams.


• Testing: testing strategies, defect testing, interface testing.
  Code inspection.


• Formal specification techniques.


• Cost estimation: function points, COCOMO, COCOMO 2 models.


• Software reliability: measures, programming techniques for highly
  reliable software.


Tutorial contents
During tutorials some problems concerning the material presented on lectures are practiced.
Classes have been prepared and are conducted with the use of the innovative and creative teaching methods. The Design Thinking technique is used in requirement engineering (identification of problems, elicitation, evaluation and prototyping of requirements).


Laboratory contents



• The objective of laboratory is to make a small object design
  using a CASE tool.


• In laboratory a CASE tool is necessary eg. IBM Rational Software
  Architect.

1. I. Sommerville: "Software Engineering - tenth edition", Addison
   Wesley 2015, http://iansommerville.com/software-engineering-book/slides/


2. P. Stevens, R. Pooley: "Using UML: Software Engineering with Objects and Components, Addison-Wesley", http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.454.4511&rep=rep1&type=pdf


3. M. Fowler: "UML Distilled - third edition", Addison Wesley 2007.