Business Modelling and Requirements Engineering

Vrije Universiteit Amsterdam

Course Description

  • Course Name

    Business Modelling and Requirements Engineering

  • Host University

    Vrije Universiteit Amsterdam

  • Location

    Amsterdam, The Netherlands

  • Area of Study

    Information Sciences

  • Language Level

    Taught In English

  • Course Level Recommendations

    Upper

    ISA offers course level recommendations in an effort to facilitate the determination of course levels by credential evaluators.We advice each institution to have their own credentials evaluator make the final decision regrading course levels.

    Hours & Credits

  • ECTS Credits

    6
  • Recommended U.S. Semester Credits
    3
  • Recommended U.S. Quarter Units
    4
  • Overview

    COURSE OBJECTIVE
    After taking this course, students will:
    • understand the key concepts of RE and its relevance for system and software engineering; (Knowledge and understanding)
    • know how to properly elicit and evaluate requirements; (Applying knowledge and understanding) (Making Judgements)
    • know how to properly specify and document requirements; (Applying knowledge and understanding)
    • know how to create goal models for the purpose of capturing functional and non-functional goals; (Applying knowledge and understanding)
    • know how to create UML class diagrams for the purpose of capturing the structure and the inter-relations between the conceptual objects
    manipulated in the system; (Applying knowledge and understanding)
    • know how to create operational models and behavioural models for the purpose of capturing the operational and behavioural aspects of the system. (Applying knowledge and understanding)

    COURSE CONTENT
    Requirements engineering (RE) is concerned with the identification of the goals that need to be achieved by an envisioned system, the
    operationalisation of these goals into services and constraints, and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. The processes involved in RE include domain analysis, elicitation, specification, assess- ment, negotiation, documentation, and evolution. Getting high-quality requirements is difficult and critical. Recent surveys have confirmed
    the growing recognition of RE as an area of utmost importance in software engineering research and practice. Within this course, we put an emphasis on requirements elicitation, specification, and modelling. The overall goal is to teach the key concepts related to RE and to create an awareness for the importance of this topic in practice. The various lectures and instructions will be devoted to the following topics:
    • Introduction to Requirements Engineering: In this lecture, you will learn what RE is all about, its aim and scope, its critical role in
    system and software engineering, and its relationship to other disciplines. You will also learn what requirements are, what they are not, and what good requirements are.
    • Requirements Elicitation and Evaluation: In this lecture (and the corresponding exercise session), you will learn a variety of techniques
    that we may use for understanding the domain in which a software project takes place and for eliciting the right requirements for a new system. What is more, you will learn how to evaluate the elicited requirements.
    • Requirements Specification and Documentation: In this lecture (and the corresponding exercise session), you will learn how to specify
    requirements in a proper way. Among others, we will discuss templates in natural language, diagrammatic notations, and formal specification methods for critical aspects of the to-be system.
    • Modelling System Objectives: In this lecture (and the corresponding exercise session), you will learn how to model the functional and
    non-functional goals of the to-be system. The models you will learn to create are referred to as goal models.
    • Modelling Conceptual Objects: In this lecture (and the corresponding exercise session), you will learn how to capture the structural perspective of the system. More specifically, you will learn how to use UML class diagrams to characterise, structure, and inter-relate the conceptual objects manipulated in the system.
    • Modelling System Operations and Behaviours: In this lecture (and the corresponding exercise session), you will learn how to model the
    functional and the behavioural perspectives of the system. To this end, you will learn how to create operational models and behavioural models.

    TEACHING METHODS
    Lectures and practical tutorials.

    TYPE OF ASSESSMENT
    Exam (50%) and practical assignment (50%)

Course Disclaimer

Courses and course hours of instruction are subject to change.

Some courses may require additional fees.

X

This site uses cookies to store information on your computer. Some are essential to make our site work; others help us improve the user experience. By using the site, you consent to the placement of these cookies.

Read our Privacy Policy to learn more.

Confirm