Emerging Trends in Software Engineering

University of Oulu
Home Noppa 811600S >  Assignments

Assignments

 


We have four types of assigments.

1) Weekly essays (5 deadlines). DL every Tuesday at 12:00.

Submit via Moodle

2) Weekly essay reviews (5 deadlines) only for the weeks you have submitted an essay

Submit via Moodle

3) Group exercise (1 deadline). DL after course. 30.10.2018 23:59. Optional weekly deadlines for those that cannot attend exercises (Sundays 23:59). Source code

4) Peerwise a) Questions create and b) Answers 5 (deadlines). Every Tuesday at 23:59. No submission just add your question and answers to Peerwise as usual.
Course ID is 17825
Identfier is <your student ID>

 


Expand all | Collapse all
Deadline  
Title
16 Sep 18 at 23.59 (Optional) Exercise progress week 1
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
18 Sep 18 at 23.59 Peerwise Week 1 Questions
Peerwise Week 1 Questions
18 Sep 18 at 12.00 Essay 1 - Trends
Use Moodle to essay submission and peer reviewing.

Read
- See 1st video lecture https://vimeo.com/album/5406569


Write an essay of a single trend in Software engineering that you think is interesting.
- How will this trend make software development: Faster, Better or Cheaper?
- Is this trend part of People, Process or Technology
Consider
- why the chosen trend is likely to have high impact
- why the chosen trend might fail after all
Use of search engines is allowed
Use of Google Trend allowed https://trends.google.com/trends/
You must write in your own words. Own reflection, insight, comparison of opinions, and critical analysis is highly valued in grading.
23 Sep 18 at 23.59 (Optional) Exercise progress week 2
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
25 Sep 18 at 23.59 Peerwise Week 2 Questions & Week 1 Answers
Peerwise Week 2 Questions & Week 1 Answers
25 Sep 18 at 12.00 Essay 2 - Web services & Reviews Essay 1
Remember to submit your reviews as well as your essay using Moodle.

- Discuss - What are web-services and their origins?
- Discuss - What are their general benefits?
- Discuss - Either A) or B)
A) Design a web-application or web-service using several web-services that solves some problem that you have related to your studies or hobbies?
B) Composition of web-services and Quality of Service. Discuss the proposal in [1]
What information with respect QoS can you find from Twitter, Google Facebook

Discuss = benefits, drawbacks, realism, own reflections

[1] Zeng, L., Benatallah, B., Ngu, A. H., Dumas, M., Kalagnanam, J., &
Chang, H. (2004). Qos-aware middleware for web services composition.
Software Engineering, IEEE Transactions on, 30(5), 311-327
30 Sep 18 at 23.59 (Optional) Exercise progress week 3
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
02 Oct 18 at 23.59 Peerwise Week 3 Questions & Week 2 Answers
See previous
02 Oct 18 at 12.00 Essay 3 - Industrial case studies and Context & Reviews Essay 2
Read article [1]
- What contextual factors the authors present to explain their findings
(Section 4.5.)
- Are they missing some obvious explanations?
- How could further evidence alter the conclusion?

Consider the lecture slides / see article [2]
- Discuss the examples that are provided on the effect of context
- Can you find personal example of any kind. What works for you? What works for you? Do you have programming or study techniques that very suitable to you Have you experienced the role of context in work or in study projects.
- Measures and Expertise are two sources of empirical evidence. To which is context more relevant?
- “Case studies can only be generalized to a similar case” What is a similar case?
[3] says the same in External Validity: “for case studies, the intention is to enable analytical generalization where the results are extended to cases which have common characteristics”

See sources in below.
07 Oct 18 at 23.59 (Optional) Exercise progress week 4
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
09 Oct 18 at 23.59 Peerwise Week 4 Question & Week 3 Answers
-
09 Oct 18 at 12.00 Essay 4: Source code - Evolution and Probabilistic Reasoning - & Reviews Essay 3
Remember to submit your reviews as well as your essay using Moodle.

- What is software evolution?
- How and why big software systems exists?
- What is probabilistic reasoning and how does it relate to source code?
- How can code be data?
- What is "Big Code"?


14 Oct 18 at 23.59 (Optional) Exercise progress week 5
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
16 Oct 18 at 23.59 Peerwise Week 5 Questions - Answers Week 4
-
16 Oct 18 at 12.00 Essay 5 - Bitcoin, Blockchain, and Cryptocurrencies - & Reviews Essay 4
Remember to submit your reviews as well as your essay using Moodle.

Explain: a) Commodity money, b) Gold standard (money), c) Fiat Money, d) Cryptocurrencies
- Why people trust Fiat money? Are there any examples of Fiat money problems?
- Are cryptocurrencies a, b, or c?

How does bitcoin solve double spending problem in a network without central authority [1]?

What is bitcoin mining? How are nonce and hash functions related to bitcoin mining?

Electricity consumption of bitcoin mining. What are the consequences?

Is mining bitcoin mining profitable?

What are smart contracts?

How do you see the future cryptocurrencies and smart contracts?

[1] Nakamoto, Satoshi. "Bitcoin: A peer-to-peer electronic cash system." (2008): 28
https://bitcoin.org/bitcoin.pdf
21 Oct 18 at 23.59 (Optional) Exercise progress week 6
Exercise points. 3 ways of getting the points
1) Attend: exercises fully and work on the exercise,
2) Report and Demonstrate: your progress on Friday in exercises (may leave when done)
3) Send email <rebvar@oulu.fi> explaining the progress and with modified source code (Deadline Sunday 23:59)
Title: “811600S – Exercise Report Week N” Replace N with the week number of this course. Weeks are from 1-6
23 Oct 18 at 12.00 Reviews Essay 5
Moodle
23 Oct 18 at 23.59 Peerwise Answers Week 5 and Trendmining questions
-
30 Oct 18 at 23.59 Trend mining report (Group work)
-

 Sources for week 3 essays

Links here due to space limitation


[1] Mika Mäntylä, Juha Itkonen: How are software defects found? The role of implicit defect detection, individual responsibility, documents, and knowledge. Information & Software Technology 56(12): 1597-1612 (2014) http://mikamantyla.eu/Mantyla_How%20Are%20Software%20Defects%20Found_IST_pre_print.pdf

[2] Tore Dybå, Dag I. K. Sjøberg, Daniela S. Cruzes: What works for whom, where, when,  and why?: on the role of context in empirical software engineering. ESEM 2012: 19-28 https://www.researchgate.net/profile/Tore_Dyba/publication/261075445_What_works_for_whom_where_when_and_why_On_the_role_of_context_in_empirical_software_engineering/links/0deec533b0c9a25eb9000000.pdf

[3] Per Runeson, Martin Höst: Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 14(2): 131-164 (2009) https://link.springer.com/article/10.1007/s10664-008-9102-8

 

 

 

Examples of good essaysfrom 2015 (highly recommended)

Link

 

 

Submitting your essay assignments

Moodle

 

General instructions for writing an essay

Essays in this course are analytical and coherent writings with a clear viewpoint or statement that is logically reasoned and critically analyzed.

You must write in your own words. Own insight, comparison of opinions, and critical analysis based on the given sources is highly valued in grading. You should include, e.g., analysis and synthesis of the source materials, your personal experiences and reflections.

Think how is this information useful. I can use it “in my Master’s thesis” / “when I start my own company developing” / “when I work as a programmer in Nokia”  

An essay is NOT just a summary of the source material (referaatti). An essay is not just a list of direct answers to the questions in the assignment. The purpose of the questions is to give you viewpoints to consider, not to dictate the structure of your writing.

Structure your essay as a coherent article, not directly by the given assignment questions. E.g., introduction, question or statement, body / discussion, conclusion. Use headings that reflect the content of your essay. You may even modify the main title of your essay to better reflect your specific focus.

Do not copy-paste text to your essays. You must cite clearly all the sources you use. The lectures and lecture slides of this course count as sources and if you use them, you must list them. Use a citation style as demonstrated in the essay template. If you are unsure about the rules or what is counted as plagiarism, refer to the Aalto University Code of Academic Integrity and Handling Violations, or contact the teacher.

Diagrams, drawings, etc. are not required, but are allowed and encouraged to clarify your analysis. Note: You are allowed to copy diagrams from other sources (provided that the copy right allows it). This is a practical relaxation of the no plagiarism rule.

The essay formatting and returning rules in a nutshell are:

  • You may write in English,
  • The length of an essay is 1200-2000 words in English
  • The allowed file formats are PDF (recommended), RTF and DOC (or docx)
  • You must follow the formatting instructions (DO NOT put your name and student number at the top of the essay)
  • State your sources.

-1 point from your essay grade if your essay

  is too long
    or if you do not follow the details of the submission instructions
    or your essay document does not have your name and student number in the top of the essay text

If we find out that you have used a source without citing, you will get failed essay. Be specific when you list your sources: If you used Wikipedia as a source, mention which Wikipedia pages you used and when did you read the page, and if you used a lecture or lecture slides as source, state which lectures or which lecture slides you used.

Printable version
Updated 23 Sep 18 at 20:48

University of Oulu oulun.yliopisto(at)oulu.fi
Tel. +358 294 48 0000
Fax +358 8 553 4112
PL 8000
FI-90014 Oulun yliopisto
FacebookFacebook
YouTubeYouTube