NEW 261 exam material

Stakeholders

Anyone with an interest in the project, including users, managers, developers, and clients.

Functional Requirements

Descriptions of what the system must do (the specific behaviors and functions).

Non-Functional Requirements

Constraints on the system or descriptions of how it should perform (e.g., speed, security, reliability).

User Interviews

A direct gathering method used to elicit detailed requirements through conversation.

Questionnaires

A data collection tool using closed-ended (multiple choice) and open-ended (text) questions to gather info from a large group.

Use Case

A system activity described in verb-noun form that defines a functional requirement.

User Goal Technique

A method for identifying use cases by identifying user categories and probing for their specific goals.

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.

Binary Association

An association between two different classes.

Ternary Association

An association involving three different classes.

N-ary Association

An association involving any number of classes.

Association Class

A class used in many-to-many associations to store attributes that belong to the relationship itself.

Superclass

A general parent class that shares common attributes and behaviors with its subclasses.

Subclass

A specific child class that inherits from a superclass.

Abstract Class

A class that cannot be instantiated; it only serves as a blueprint for other classes.

Concrete Class

A standard class that can be used to create actual objects.

Application Architecture

The high-level design of the software components and their interactions.

Technology Architecture

The hardware and software platforms (OS, servers, databases) required to run the application.

Core Process 3

The process of analyzing the current environment and defining the desired future state of the system.

Activity Diagram

A UML diagram showing the flow of control or data from one activity to another.

State Machine Diagram

A UML diagram showing the different states an object goes through during its lifetime.