Dines
Bjørner's
University of Saarland
Web Page
# 8216-17: From Domains via Requirements to Software
E-Mail: bjorner@gmail.com
Home Page
March 17, 2009
Dines Bjorner, September 2007
- Wed.4.March: Both "previously" schedule lectures 2 and 3 were given.
- We started Tue.3 March 2009. Schedule has thus been revised.
Lecture schedule reflects this.
- Days off:
-
Monday 23 March
: Mtg. @ FaM Airport w. W.J.P. + R.W. +
others (England, Frankreich, Österreich, Schweiz, ...)
Lecture schedule reflects this.
This Web page provides
information about the course given at the University of Saarland, March 2009.
-
Course Name:
#8216-17: From Domains via Requirements to Software
The Triptych of Software
Engineering
-
Informal and Formal Software Development
from Domain Models
-
Lecture Notes:
Draft:
The Full Set of
Lectures Notes
-
Beware: This
approximately 600 page document is
regularly updated.
-
Course Period:
1-31 March, 2009
-
Course Days:
Monday-Friday
, every day, normally,
but pls., for details, see below.
-
Exam:
Thursday 26 March @ 10:15 st-12:00
-
Course Hours:
- Morning `Methodology' lectures: 10:15 st-11:45
- Afternoon `Project' class: 14:00-15:30/16:00
-
Venue:
Seminar room 016, building E1.3
- For General Lecture
Plan
click this.
This plan details the contents and gives slide number references to
lectured material.
Similar lecture plan is given in the
lecture notes Pages XII-XV.
See also
Course Specific Lecture
Plan
below for URLs to individual
lecture note chapters and lecture slides.
-
Course Participants:
| No. |
Name |
E-mail Address |
Project: Yes |
No |
| 1 |
Artem Alekhin |
aalekhin...gmail.com
|
|
No |
| 2 |
Mikhail Kovalev |
mikhail.kovalev...gmail.com
|
|
No |
| 3 |
Guillaume de Chambrier |
s0672742...sms.ed.ac.uk
|
Yes |
|
| 4 |
Daniel Omyla |
daniel...math.uni-sb.de
|
Yes |
|
| 5 |
Robin Woll |
Robin_Woll...web.de
|
Yes |
|
| 6 |
Christian Müller |
cm...cs.uni-sb.de
|
|
No |
| 7 |
Zhe Zou |
zuozhexmu...yahoo.com.cn
|
Yes |
|
| 8 |
LianChao Li |
superemolee...googlemail.com
|
Yes |
|
| 9 |
Wenkai Dai |
Wenkai.Dai...gmail.com
|
Yes |
|
| 10 |
Mohammed Reza Yousefi |
myousefi...mpi-inf.mpg.de
|
Yes |
|
| 11 |
Alekh Jindal |
ajindal...mpi-inf.mpg.de
|
Yes |
|
| 12 |
Donjeta Ibrahimi |
donjeta.ibrahimi...gmail.com
|
Yes |
|
| 13 |
Christian Doczkal |
c.doczkal...stud.uni-saarland.de
|
|
No |
- The aim of the course is to cover a number of
"front-of-the-wave" software engineering topics:
- The Triptych of Software Engineering
- Domain Engineering, in depth;
- Requirements Engineering, a broad overview; and
- Software Design, a very brief summary.
It is the aim to whow how these three phases relate.
- To show the dual benefit of both
- precise national language Narratives couple with
- formal specification
- To show that the new element of software engineering, namely
domain engineering, has a number of precise methodological
stages:
- intrinsics,
- support technology.
- management &organisation,
- rules ®ulations,
- scripts, and
- human behaviour
facets.
- To show that the requirements engineering now has a rather
different methodology, including:
- domain requirements, with its
- projection,
- instantiation,
- determination,
- extension and
- fitting
domain-to-requirements operations.
- And to briefly show how the two phases of the triptych relate to
software design.
- The objectives of the course and the course project is to
- secure that course participants
- get a professional education and part-training as responsible
software engineers; and
- are exposed to a number of exciting research topics.
- The objectives are further that the course participants become
acutely aware of and familiar with
- ability to express themselves
- both in informal, yet precise natural language,
- and in some formal specification language.
- Finally it is an objective of the course that the course
participants
- discover the need for a serious attention,
- in software
engineering,
- as well as in computing science research
to
domain engineering.
- Bjørner is away (pls. note: lecture schedule has been resceduled)
- Especially this part of this Web page may be subject to
frequent updates.
- Notes on exam:
- Exam consist of two parts:
- a report, possibly worked out individually, or in subgroups, or
by full group of course participants;
- a two hour written test,
- Written test checks your understanding of the report !
- There are two parts to be evaluated:
- the student understanding of the course lectures and
- the course project report.
- The evaluation of the former
- is on the basis of a 2 hour 24
question test: each question requiring from 2-3 to 5-7 lines of answer.
-
Exam: Thursday 26 March, 2009, 10:00 st - 12:00am
- The evaluation of the latter
- is on the basis of the report work,
i.e., of progress across intermediate reports and on the basis of
the final report.
- There is going to be a course project.
- It is an indispensable part of the course.
- The topic of the course project,
- i.e., the kind of societal
infrastructure component domain that you, the course participants,
- are to model similarly to the model given in Appendices E-K of the
lecture notes
- was decided in the first Tutorial Class Session on the first
course day, Tuesday 3 March, 2009.
- This project was chosen:
- "The" Financial Service Industry:
- Team 1: "Main Street" Banking;
- Team 2: Securities Exchange (Stock, Petroleum, Metal, ...,
Exchanges; and
- Team 3: Govt. + Natl.Banks + Commercial Banks.
Brokers and Traders).
- I expect the class to be divided into one or more teams of 3
persons each, say N teams.
- Each team start out with an analysis of the domain with the
analysis leading to a decomposition of the domain into a number of
sub-domains - where that number equals the number of teams!
- The N teams progress, according to the method, illustrated by
Appendices E-K, by analysing, "terminologising", writing "information
documents" about, and modelling the domain.
- Twice a week each team is to deliver, initially a hand-written,
soon a preferably LATEX processed documents to the lecturer and to
all other teams (one per team and one for the lecturer), in paper
form.
- All reports, whether intermediate or final, must be dated, given
a report (running project) title, full names and e-mails of all team
members - and signed!
- The lecturer will not look at these reports outside tutorial
sessions - so deliver them at the very beginning of such a session,
say the Thursday and Monday. During that or a subsequent tutorial
session the lecturer will scan those N intermediate reports
and comment on them "before" the full class.
- The final report will be delivered at the end of the course, in paper form, either before I leave Saarbrücken or sent to me in
Denmark: Fredsvej 11, DK-2840 Holte, Dänemark.
- It is important that you excert a somewhat struct discipline in
this course:
- Make sure to come to all lectures (am) and all "tutorial"
sessions (pm), from first day.
- Make sure to become familiar with all aspects of this Web page.
- Make sure to be part of a project team, and form that team on
first day of course.
- Make sure to work for and in that team every day for 60-90 mins.
- Make sure to set up appropriate text files with appropriate
(e.g. LATEX) headers and footers of this kind:
- Header: Project No. / Page No. / Project Title
- Footer: Your name / Location, Date [and Time Stamp]
- It would be preferable if each page was also provided with a
time stamp: Here are LATEX macros etc. for that:
\usepackage{ifthen}%
\usepackage{calc}%
\newcounter{saarhours}%
\newcounter{saarmins}%
%% ctod: calculate time of day
\newcommand{\ctod}{\setcounter{saarhours}{\time/60}\setcounter{saarmins}{\time-\value{dbhours}*60}}%
- You may wish to redefine:
\let\@oddfoot\saaroddfoot%
\let\@evenfoot\saarevenfoot%
and define, in your main .tex file:
\newcommand{\saaroddfoot}{{"your-name"}\hfil{"loc."}\today: \ctod}
\newcommand{\evenoddfoot}{{"loc."}\today: \ctod\hfil{"your-name"}}
-
Get this to work now: in week: 2-6 March, 2009
- The lecture notes
and the
lectures slides will show formalisations in terms of
RSL
.
- Course participants are invited to choose any reasonable
formalisation approach.
- Some are listed below.
- Any team may choose their own approach, incl. a local, Univ. of
Saarland "favourite".
- The
R
AISE
S
pecification
L
anguage,
RSL
.
- Chris George: Formal Software Specification Using
RAISE
- Dines Bjørner. Software Engineering,
Texts in Theoretical Computer Science, the EATCS Series. Springer,
2006.
- Vol. 1: Abstraction and Modelling.
- Vol. 2: Specification of Systems and Languages.
Chapters 12-14 are primarily authored by Christian Krog Madsen.
- Vol. 3: Domains, Requirements and Software Design.
- There are many other formal development approaches:
-
Alloy
- Daniel Jackson.
Software Abstractions Logic, Language, and Analysis.
The MIT Press, Cambridge, Mass., USA, April 2006.
ISBN 0-262-10114-9.
- The Alloy Home Page
-
ASM
-
B
- Jean-Raymond Abrial.
The B Book: Assigning Programs to Meanings.
Tracts in Theoretical Computer Science. Cambridge University Press,
Cambridge, England, 1996.
- B4free
- Atelier B
-
Event B
-
VDM-SL
-
Z
- J. C. P. Woodcock and J. Davies.
Using Z: Specification, Proof and Refinement.
Prentice Hall International Series in Computer Science, 1996.
- The Z Notation
- Etcetera.
- Since all student questions are good
- all your fellow students need likewise hear
- the answers - which are, hopefully, also good.
- Therefore there will, in principle, not be granted individual
consultations with the lecturer.
- The lecturer may, however, at own discretion, contact students
- and give them some "private" tutoring.
For an unconventiomal CV click
this.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Dines
Bjørner's
University of Saarland
Web Page
# 8216-17: From Domains via Requirements to Software
This document was generated using the
LaTeX2HTML translator Version 2002-2-1 (1.71)
Copyright © 1993, 1994, 1995, 1996,
Nikos Drakos,
Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999,
Ross Moore,
Mathematics Department, Macquarie University, Sydney.
The command line arguments were:
latex2html -split 0 -toc_depth 6 home
The translation was initiated by Dines Bjorner on 2009-03-17
Dines Bjorner
2009-03-17
