IT 261 Study Guide Exam 1

Functional vs. Non-Functional Requirements

Functional: What the system does (happens when a computer jsnt reqhired eg: course registration. Non-Functional: How the system performs or constraints it must follow (piec3s that are added are things that are added because jt’s in acimluter

Three Types of System Events

Review lecture notes for the three types of events a system must respond to

Multiplicity

Specifies the minimum and maximum number of instances that can participate in an association

Multiplicity: 0..1

Zero or one (Optional)

Multiplicity: 1

One and only one (Mandatory)

Multiplicity: 0..*

Zero or more (Optional)

Multiplicity: 1..*

One or more (Mandatory)

Unary Association

An association where a class connects to itself (e.g., Student–Study)

Binary Association

An association between two classes

Ternary Association

An association among three classes

N-ary Association

An association involving any number of classes greater than 3

Association Class

Used in a many-to-many association when the association itself needs attributes to be recorded (e.g., grades)

Use Case

An activity the system performs, used to define functional requirements; typically named in verb-noun form

User Goal Technique

A technique for identifying use cases by identifying user categories, interviewing them, and probing for their specific goals

Domain Model Class Diagrams

Review purpose and components: super, inherente abstract, and concrete classes, and whole-part relationships

Activity, Use Case, and State Machine Diagrams

Review the purpose and UML standard components for each

Core Process 3

Review the specific activities and objectives

Application vs. Technology Architecture

Review the difference between these two architectural layers

Stakeholders

Review the definition and the different types of stakeholders gripping of purple who hefty intrest

User Interviews and Questionnaires

Review the process for conducting interviews and the two types of questionnaire questions