• Why do we make models?
• Course organization
• Seminar project information

Slides in English:

Recorded lecture in Czech:

Seminar briefing in English:

Seminar - Introducton:

• During the course of the semester, each team will deliver a seminar project
• Imagine that your team represent a small IT company 
• This team is going to deliver a solution to the client
• The client will (virtually) describe their business to be supported with an IS you should deliver
• Your task is to provide a document related to the analytic part of this project
• Each week, you will be assigned with specific task(s) – either multiple easier models, or model and its decomposition
• There is a total of 10 seminars for a maximum of 40 points – at each seminar, you will be informed about points to obtain for given tasks, 
• By the end of a semester, you will submit one pdf document with all mandatory tasks
• Accepted languages: CZ/SK/EN

Evaluation of the seminar project: 

We will evaluate your project based on these criteria:

1. Fulfillment of the mandatory tasks as assigned each week:
1. Quantity - were all tasks done in the requested scope?
2. Quality - how the tasks were carried out? Is given model notation applied correctly?
2. The overall impression of the document:
1. Readability - how convenient is for the reader to understand the document - e.g. consistent formatting (fonts for text/headers/(sub)sections, numbering...), pinpointing important information, etc. 
2. Understandability - how much do you adjust the content/meaning such that the reader will understand the document*
3. Consistency – are individual models interrelated/balanced against each other (and namely against the domain description = client’s expectations)?

*Try to imagine that you deliver a document that might be read by different stakeholders involved in the project. Not necessarily everyone is an IT professional, but they still should be able to understand the meaning

Seminar 1 tasks

1) Set up a document      [ 1pt]

• Create a unified nicely looking template for the whole project documentation
• Name your company
• Create a list of your team members + UČOs

2) Domain description      [ 1pt]

• verbal description of your client's business - unstructured or semi-structured (approx. 0.5-1 page)

3) Mind map      [ 1pt]

• mind map in any available tool to record the first brainstorming related to project kick-off (not only about the analysis of the IS, but about all the important things that are related to project execution) 
• Example topics to be addressed: How to communicate with the client? How to visit his business location? What pizza delivery service will we use for dinner? 

4) Work breakdown structure + pricing      [2 pts]

• use WBS to estimate the amount of work to be done on the project in order to present pricing to your client