582104 Software Modelling

Principal theme Prerequisite knowledge Approaches the learning objectives Reaches the learning objectives Deepens the learning objectives
  • Introduction to the basics of software modelling
 
  • Can explain the basic objectives and demands of modelling (design, documentation, communication)
  • Can explain and give examples of different types of models: structural models (class array), functional or behaviour models (e.g. sequence array)
  • Can select a suitable modelling method according to problem area and assignment, and can justify their choice.
  • Can use simple modelling annotation repfresenting different modelling types.
  • Can formulate models of a system to describe the system on different levels of abstraction and from different viewpoints.
  • Can analyse whether a model represents the functionality of a system reliably.
  • Can describe the principles of model-based software development.
  • Can explain the connection between models and meta-models.
  • Software lifespan and the basics of software manufacturing
  • Know the basics of object-oriented programming (Introduction to programming)
  • Can explain the basic principles of good software design
  • Can describe the main stages of software lifespan and explain what happens at each stage.
  • Can explain the significance of requirements analysis when mapping interest groups and service needs.
  • Can describe the main principles of requirements analysis.
  • Functional and non-functional requirements
  • Priorisation of requirements
  • Compatibility of requirements
  • Can apply methods of requirements analysis in the requirements analysis of small information systems.
  • Can apply the basics of requirements documentation on the formulation of requirements specification.
  • Can describe the role of different models and model types, as well as their demands and uses, at different stages of the software's lifespan.
  • Can explain the equivalences of software artefacts (models, source code, implementation) throughout their lifespan: from requirements to design and on to implementation.

 

  • Modelling and description methods at different stages of the software process
  • Know the basics of object-oriented programming (Introduction to programming)
  • Can explain the most significant UML diagram techniques and their uses.
  • Can categorise the most significant UML diagram techniques according to model type.
  • Can interpret simple software models.
  • Can use a use-case diagram to support a requirements analysis.
  • Can use a class and sequence diagram to describe the design solutions for a piece of simple software.
  • Can apply the principles of object-oriented design to create detailed class and sequence diagrams.
  • Know complex design solutions, such as simple design models.
  • Use the methods and tools of requirements specification in programming projects. 

 

22.09.2011 - 15:48 Marina Kurtén
31.08.2011 - 10:43 Matti Luukkainen