Methods and Evolution Trends of Applied Computer Science

The study course is dedicated to discussions on modern methods of applied computer science with an emphasis on research conducted at Riga Technical University. Students are encouraged to analyse online materials, periodical publications, and current information from scientific conferences and symposia, following trends in applied computer science and evaluating their development prospects. Independent work promotes the use and development of the latest trends in applied computer science in the master thesis.

grading

• There are multiple individual assignments in report and/or presentation format which are evaluated.
• Independent studies include performing research within the Master Thesis with the aim to synthesize it with the information considered within the course.
• The course final grade is calculated as a weighted average of individual assignments (see Tentative outline) and an examination.
• More than one-month late submission and/or violation of academic integrity* decreases the assignment grade potentially down to failed.
• During the semester, the progress will be reflected in the Grades section of the course.

class 1 - State of art in applied computer science

hot topics in IT:

• open-source
• cloud
• IoT
• AI
• ML
• VR
• cryptocurrencies
• cybersecurity

State of Software Development:

• v1.0 - 1969
• v2.0 - 2010 - "Software is eating the world, and also eating itself" <- the real problem is that a world running on bnuggy softwarre.
  • Can We Really Achieve Software Quality? - Ipek Ozkaya

what we learned from covid pandemic:

• Efficiency: Short-term optimization
• Resilience: Long-term optimization

What Software is Really About?

• People vs. Processes
• Science vs. Art (Engineering vs.Craftsmanship)
• Documenting vs. Understanding
• Metrics vs. Skills vs. Methods
• Good Enough vs. Right and Wrong

"Scientific thinking evolved as a means of understanding the world." Grady Booch

"There is nothing more practical as a good theory." - Boltzmann

class 4 -

class 5

Use the Functional features table template to:

• Refine problem domain description according to the discussion/lecturer feedback comments.
• Fill a functional features (FFs) table and design an initial TFM. (You can choose any appropriate tool for the TFM creation, e.g. Visio, draw.io, Word, etc.)
• Submit the refined description, FFs table and initial TFM before the next class.

class 6 - trends in model-driven software development - solution domain design and validation

• model driven enviroment (MDE)
  • model driven development (MDD)
    • model driven architecture (MDA)

Jon Whittle, John Hutchinson, and Mark Rouncefield. The State of Practice in Model-Driven Engineering

human factor is also a favour who benefits in MDE

Psyhology of MDE

• managers
• software archiects
• code gurus
• hobbyist dev

MDE adoption Issues

• organization factors
  • business domains
  • geenric software deveelopment
• MDE approaches Training issues
  • learning of abstraction
  • software modelling practice

MDE in research VS industry

In practice developers rarely use MDE to generate whole systems – they apply it to develop key parts of a system.

• MDE is necessary, but not sufficient!

Mapping Solution Domain Functional Requirements to Problem Domain Functional Features

Extended Tuple Functional Feature of a System

<Id, A , R, O, PreCond, PostCond, Pr, Ex, S, Cl, Op>,

• Cl is a class (type of object O) which will represent system in static model the object which will contain operation for functionality defined by this functional feature (can be fulfilled when the class diagram is synthesized)
• Op is an operation which will contain functionality defined by functional feature (this parameter can be fulfilled when the class diagram is synthesized)

importance of modelling

Additional reading:

1. Osis, J., Asņina, Ē. Is Modeling a Treatment for the Weakness of Software Engineering?, http://www.igi-global.com/gateway/chapter/49151
2. Nazaruka, Ē., Osis, J. Determination of Natural Language Processing Tasks and Tools for Topological Functioning Modelling. In: Proceedings of the ENASE 2018. Portugal: SCITEPRESS – Science and Technology Publications, Lda., 2018, pp.501-512. ISBN 978-989-758-300-1. DOI: 10.5220/0006817205010512 https://www.scitepress.org/papers/2018/68172/index.html
3. Osis, J., Asņina, Ē. Topological Modeling for Model-Driven Domain Analysis and Software Development: Functions and Architectures. http://www.igi-global.com/gateway/chapter/49152
4. Osis, J. Asņina, Ē. A Business Model to Make Software Development Less Intuitive, 2008. DOI: 10.1109/CIMCA.2008.52
5. Osis, J., Asņina, Ē., Grāve, A. Formal Computation Independent Model of the Problem Domain within the MDA. MARQ, 2007, pp. 47-54. http://ceur-ws.org/Vol-252/paper06.pdf
6. Doniņš, U. Software Development with the Emphasis on Topology. In: Advances in Databases and Information Systems, Vol.5968. Springer, 2010. pp. 220-228.
7. Osis, J. What is the Precise Relationship between Domain Modelling and Architectural Design and Modelling? Proc. Of ECOOP Workshop, 2001. pp. 9-12.
8. Jones, C. Positive and Negative Innovations in Software Engineering. International Journal of Software Science and Computational Intelligence, 1 (2), 2009, pp. 20-30.
9. Я. Я. Осис. Топологическая модель функционирования систем. Автоматика и вычислительная техника. АН Латв. CCР, № 6, 1969, с. 44-50. (in Russian)

literature:

• Janis Osis, Erika Asnina - Model-Driven Domain Analysis and Software Development: Architectures and Functions
• Nazaruka, Osis- The Formal Reference Model for Software Requirements