This is the home page for the course Software Engineering (TNM090). It contains current schedule and information about the course. All material distributed during the course will be linked to from this page (or there will be a description on where to find it).
Organization
The teaching in the course is based on lectures, with optional complementary reading, laboratory exercises and a relatively large group development project. The examination is based on hand-ins on some topics, project deliverables, reports, meetings and seminars, and the completion and demonstration of the laboratory exercises.
Teaching
- Lectures — attending is not compulsory but recommended since the lectures are bringing up and discussing all contents of the course.
- Course Literature — the course literature can be used as a complement or partial substitute for the lectures.
- Scientific articles — for some of the topics of this course there are articles listed that provide complementary information and deeper discussions.
- Laboratory exercises — provide hands-on experience of some more advanced development techniques, tools and principles.
- Development project — a development project will be conducted in groups of 5–10 students to provide hands-on experience of development in larger groups with limited time.
Course Literature
The primary course literature is Pfleeger & Atlee,
Software Engineering Theory and Practice, fourth edition.
Other literature that is useful for this course includes Design Patterns, Elements of Reusable Object-Oriented Software, by Gamma et al., Pattern-oriented Software Architecture, volume 2: Patterns for Concurrent and Networked Objects, by Schmidt et al., and Using UML, Software Engineering with Objects and Components, by Stevens & Pooley
Examination
- Hand-in assignments (2 hp) — the basic understanding of some important topics must be demonstrated through a written discussion with individual reflections.
- Laboratory work (3 hp) — in the laboratory exercises you show that you can learn to use advanced tools and techniques.
- Project (7 hp) — this element of the course is both hands-on experience and a way for you to show that you can apply theories on practice. Individual grades U or 3–5 are given for the project work.
Teachers
| Karljohan Lundin Palmerius | Giving lectures, and supervising and examinating project work | Web |
| Alexander Bock | Supervising laboratory work |
Schedule
Tentative schedule: this is the approximate distribution of teaching sessions. Always check the Timeedit database for the latest updates.
| Week | M | T | W | T | F | |
| 36 | Lec | Lec | ||||
| 37 | Lec | Lec | ||||
| 38 | Lec | Lec | ||||
| 39 | Lab | Lec | Lec | |||
| 40 | Lab | Lec | Lec | |||
| 41 | Lab | Project plan | ||||
| 42 | Lab | Lec | ||||
| 43 | ||||||
| 44 | ||||||
| 45 | Sem | Sem | Sem | Status sem. | ||
| 46 | Lab | |||||
| 47 | ||||||
| 48 | ||||||
| 49 | ||||||
| 50 | Lab | |||||
| 51 | Sem | Sem | ||||
| 52 | Christmas | |||||
| 1 | New Year | |||||
| 2 | ||||||
| 3 | Presentation | |||||
Lecture Topics
The lectures are divided into topics and one topic may span part of a lecture or more than one lecture. The topics that must be covered by the three hand-in assignments are marked as H1, H2 and H3.
| 00 | Course Information | ||
| 01 | Software Engineering | H1 | |
| 02 | Development Methodologies | H1 | |
| The Scrum Guide | |||
| Scrum of scrums | Web | ||
| 03 | Project Management | H1 | |
| 04 | Requirements | H2 | |
| 05 | System Architecture | H2 | |
| Patterns For Large-Scale JavaScript Application Architecture | Web | ||
| 06 | Program Design | H2 | |
| 07 | Modelling Notations | H3 | |
| Agile Modeling | Web | ||
| Five-step UML (incomplete) | Web | ||
| UML 2.0 Quick Reference | Web | ||
| UML Cheat sheet | |||
| Asta Five-step example | asta PDF | ||
| 08 | Implementation | H3 | |
| Google Style Guide | Web | ||
| 09 | Design Patterns | H3 | |
| 10 | Refactoring | H3 | |
| Refactoring, Improving the Design of Existing Code | |||
| 11 | Testing | H2 | |
| 12 | Maintenance | H2 | |
Extra topics | |||
| x2 | Multi Threaded Programming | ||
Laboratory Exercises
| Lab 1 | Laboratory Platform (optional) | instructions | ||
| Lab 2 | Software Configuration Management | instructions | ||
| Lab 3 | Developing a Particle System | instructions | files | |
| Lab 4 | Code Quality Analysis Tools | instructions | files |
Hand-in Assignments
Three reflection documents must be handed in for 2 hp, each covering a set of lectures as marked in the lecture list. The report should be brief, just a few pages.
| Deadline | |
| H1 — Project Management | 2013-10-18 |
| H2 — Software Engineering Principles | 2013-11-15 |
| H3 — Standards and Best Practices | 2013-11-15 |
The documents should show that you have an understanding of the underlying essence of the course and should therefore express your personal understanding of the topics. Review your notes, hand-outs and related literature, and reflect on what these topics mean to you. You may include observations, relate to earlier projects, associations with software you use, reflect on how you may use the new knowledge in the future, etc.
The reports should be written in Swedish or English in plain text, simply formatted, e g A4 paper with 12 pt Times New Roman.
It is recommended that the documents are written continuously during the period. All documents are handed in as PDF through URKUND by attaching them to an e-mail with "[TNM090]" as subject sent to karljohan.palmerius.liu@analys.urkund.se.
Development Project
The development project will be conducted in groups of tuned sizes. To ensure the quality of the project and the experience of the members, each group and each member has to perform certain steps. If one of these steps are not applicable to your project, you must consult the examiner.
To pass the development project, each group has to
- hand in a project plan to the examiner
- attend a status seminar with the examiner
- use at least one project management tool to manage workload
- perform at least one sprint meeting with architectural modelling and review
- write a common project report
To pass the development project, each individual member has to
- contribute to the project. Observe, however, that contribution is not measured in lines of code
- do code review on some part of the system
- implement automated unit tests
- write an individual project report
There will be four scheduled milestones with deliverables for the purpose of controlling the progress and examination of the project work
- the project plan, which is sent to the examiner,
- a status seminar, where the project group presents the progress of the project,
- the final presentation of the project and the results, and
- the final individual report.
The dates for these milestones are marked in the schedule.
Project Plan
The project plan should be based on the theories discussed in the lectures. There is, however, a minimum requirement for the project plan, as listed below. If a point below is not applicable to the project it may be omitted.
- Time-plan with calendar dates
- Time for planning
- Iterations and their dates
- Milestones and deliverables
- List of technologies to use
- Development infrastructure
- Development platform
- Requirements handling and tracking
- Story/Task management
- Version handling system and procedures
- Testing standards and procedures
- Modelling standards and procedures
- People and organization
- Technical description
- Target hardware, required software, standards and APIs, and development tools
- Restrictions, execution time, response time
- Standards, methods and third party APIs
- System environment, input and output
Group Report
The group report, to be handed in by the time of the presentation, will be the basis for pass or fail of the project, and help indicating the distribution of effort between the members.
This should contain:
- A general discussion on the original goals and how these have been accomplished and what has been omitted and why
- Description of technical solutions and the development process, with references to relevant literature
- At least one protocol from a sprint meeting including an architecture modelling and review process, and a comparison with the final architecture.
- List of the people involved together with a description of each individual's contribution to the project. This should not be line-by-line or file-by-file lists, but can be statistics from the version handling or backlog tool, description of documents written by whom, percentage of involvment per module, or any other means that you as a group think reflects the work distribution in a fair manner.
If the group cannot agree on the contents of a part of the report, the smallest of the disagreeing sub groups may produce a complementary document with an alternative text of the section concerned.
Individual Report
The individual report, to be handed in before tenta-P, will be the basis for the individual assessment and be used together with the group report to determine each student's grade. Observe, however, that it is not the number of lines of codes produced that determines the grade.
This report should contain:
- A general personal assessment of the involvment and contribution to the project
- An individual discussion and reflection over the project with references to relevant software engineering theories and principles.
- At least one protocol from an individual story modelling process, for example describing a Five Step UML design of a software unit implementing a certain functionality or the refactoring of a software unit.
Project Expectations
- All projects should make use of the following aspects of Software Engineering
- Project management and development methodology
- Requirements elicitation, analysis and documentation
- System architecture, module design and program design
- Unit testing and system testing
- The project should follow basic Scrum principles
- Everyone should be involved in all steps in the development
- Document authors of reports and involvement in reviews and meetings
Available Resources
- Any student can book facilities for meetings (here)
- Online digital task board may be used
- SeeNowDo — a digital task board
- Pivotal Tracker — free for public projects
- etc.
- Local course resources
- WebDAV via Owncloud providing an online shared folder for project files
- a GIT repository can be shared via WebDAV
- Agilefant (you don't sign up at agilefant.org)
- Software in K4504
- UML modelling tools: Astah, ArgoUML, Dia, Inkscape, etc.
- Development environments: Emacs, Eclipse, Kate, etc.
- Project managment tools: Calligra Plan and Planner
- Repository statistics: gitstats and statsvn
Observe that an Agile development tool will not provide all features required for this course. You will have to use a combination of tools, e.g. Agilefant for task tracking, Inkscape for architectural modelling, Astah for module and program design, Doxygen for documentation and GIT for source code handling and versioning.