Lecture 1 - Business Process Modeling Flashcards

1
Q

The 4 paradigms of Object Oriented Programming

A
  • Abstraction: a process where you show only “relevant” data and “hide” unnecessary details of an object from the user.
  • Encapsulation: a practice that bind the data with the code that manipulates it and keeps the data and the code safe from external interference
  • Inheritance: the mechanism by which an object acquires the some (or all) properties of another object.
  • Polymorphism: a way to process objects differently based on their data type. In other words objects can have the same name for a method but the implementation may differ.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Business Function

A
  • Refers to an activity that a company performs, like order management, marketing, selling, finances, product design, and so on.
  • Business functions may be carried out by one or more departments and may be organized hierarchically.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Business Processes

A

The complete & coordinated set of collaborative activities that respond to a business requirement for action, that deliver value to customers (e.g., the purchasing of a certain product).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Business Process Integration

A

The techniques and mechanisms for managing the movement of data, and the invocation of processes in the correct and proper order to support the management and execution of common processes that exist in and between applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Functional Programming

A

Style of building the structure and elements of computer programs that treats computation as the evaluation of mathematical functional and avoids changing-state and mutable data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Object Oriented Programming

A

Based on the concept of objects, which may contain data, in the form of field, often known as attributes; and code, in the form of procedures, often known as methods

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Procedural Programming

A

Based upon the concept of the procedure call. A series of computational steps to be carried out.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Why do we model?

A
  • Modeling as a way of communication among all stakeholders
  • Model as a communication tool
    As we have to deal with people of different backgrounds and with different perceptions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Model

A

Abstract representation of the real world (which is messy and complex)

  • Reduces complexity
  • Represents only necessary details
  • Stille needs to be complex enough to cover all things
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Modeling methodology

A
  • specifies activities to be performed
  • roles of participants.
  • techniques to be used.
  • deliverables to be produced
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Modelling

A
  • Consider alternatives
  • Select best option
  • Work out details
  • Achieve agreement before they start building an application
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Business Process Modelling

A

Methodology for modelling

  • Business data (information)
  • Business processes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Collaborative Process

A

a process with implicit behavior and interaction between multiple business entities with different roles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Collaborative Activities

A

actions performed by the participating entities in response to the messages they receive from other participating entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Who models?

A

Business Analyst on behaf of all stakeholders (customers, service providers, business partners, system operators etc.)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Modelling method (consists of)

A

o Modelling language: is a collection of languages (usually graphical) that the method uses to express the design and concepts.
o Process: a set of guidelines/steps of how to do the design

17
Q

UML

A
  • Unified Modeling Language
  • Not a method
  • But a collection of languages
  • To specify the needs of the user in different views
18
Q

Use Case diagram

A
  • Functionality of the system in transactions (use cases) between actors and system(s)
19
Q

Generalization

A

A specialized case of achieving the same goal, for capturing alternative scenarios
Denotes a specialized case of achieving the same goal of the inherited Use Case. The inheriting use case would completely replace one or more of the courses of action of the inherited use case

A fixed account is a type of bank account
Update existing customer data is a type of provide customer data

Represented by a solid line with a white arrow pointing to the bank account

20
Q

Class diagram

A

Describes the types of objects in the system and the various kinds of static relationships that exist among them

21
Q

Data types

A
String: Text
Integer: Whole numbers
Double: Decimal numbers
Float: Number ending with f or F
Boolean: Yes or no, true or false etc.
Void: Return nothing
22
Q

Association

A
Objects of one class are connected to objects of a second (possibly the same) class
A passenger is part of an airplane
Represented by a solid line
23
Q

Directed association

A

There is an association, but only one way.
A passenger can not exist with the absence of an airplane, it can the other way round.
Represented by a solid line with the black arrow pointing to the passengers

24
Q

Reflexive association

A
A class has an assocation with itself, or other from the same class
Represented by a solid line from the class to itself
25
Q

Multiplicity

A

The numerical constraint of that particular class is defined

26
Q

Aggregation

A

A library is a collection of books, there has to be at least 1 book
Represented by a solid line with a white diamond pointing to the library

27
Q

Composition

A

When the composition (one piece) dies, all other components dies too (there is no car anymore)
A library exists only if there are books
Represented by a solid line with a black diamond pointing to the library

28
Q

Realization

A

A printer setup is an instance of a concept: the printer itself. It needs to be in place for the printer to work
Represented by a dashed line with a white arrow pointing to the printer

29
Q

Sequence diagram

A

To model the interactions among objects in use cases, in time sequence

30
Q

Activity diagram

A

Shows who does what under which condition and in which sequence

31
Q

Decomposition

A

An activity can be broken down into sub-activities

32
Q

Include

A

Dependency between a base use case and an included use case.
When the base is executed, the included is executed as well and a base use case needs a completed included use case in order to be completed (verify password and display login error for the log in use case, verify sufficient funds for make payment, choice of pay from checking or pay from savings for make payment).
Multiple use cases can point to the same included use case.
Represented by a dashed line with an arrow from the base to the included use case with the text: <> through the line

33
Q

Extend

A

A base use case and extend use case. When the base use case is executed, the extend use case will happen sometimes, it will only happen when certain criteria are met. Display log in error will only happen when a customer enters a wrong password.
Represented by a dashed line from the extend to the base use case with the text <> through the line

34
Q

-, +, # and ~

A
The minus signs (-) before all of the attributes and methods state that their visibility is private, it can’t be accessed by any other class or subclass. 
The plus sign (+) is the exact opposite (public). --> mainly used in methods. 
The hash sign (#) means that it is protected, it can only be accessed by its same class or its subclasses. 
The tilda sign (~) sets the visibility to package or default which means it can be used by any other class as long as it is in the same package.
35
Q

Inheritance

A
We make a class for a Tortoise, an Otter and a Slow Loris. Those become subclasses of the Animal class. We say that these subclasses (child class) inherit all of the attributes and methods of the superclass (parent class). We can add additional attributes or methods in the specific subclass. The Animal class in an abstract class so you can put it in italics or between <<>>. 
They are represented by a solid line with a white triangle pointing to the superclass/parent class