Outcome 2 Flashcards

(34 cards)

1
Q

Data Collection Methods

A
  • Survey
  • Report
  • Interview
  • Observation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Functional Requirements

A

What the solution will do

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

Non-Functional Requirements

A

other requirements the client would like the solution to have, that doesn’t effect what the solution will do

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

Non-Functional Requirements - Components

A

Usability
Portability
Reliability
Robustness
Maintainability

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

Scope

A

Describes what the solution will and wont do

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

Constraints

A

Anything that may limit the options for development or delivery

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

Types of Constraints

A

Economic - includes time and cost
Legal - when legislation restricts the solution from performing certain activates
Social - limitations of people to perform functions
Technical - related to hardware and software available to the project
Usability - things like screen size, complexity of the solution

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

SRS

A

Software Requirements Specification

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

SRS - Features

A

Constraints
Scope
Functional & Non Functional Requirements
Optional - appendix containing other information needed to interpret the requirements (OS, third party tools required)

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

SRS - Purpose

A
  • to ensure that the clients problem or opportunity is understood
  • to form the basis of the design
  • to be used as the basis of the evaluation criteria
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Organizational Goals

A

Defines an organizations purpose, assist its growth and help is achieve financial objectives

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

Organizational Objectives

A

Specific, measurable, achievable steps towards achieving a larger goal
quantifiable - can be proved to be achieved with stats, observations and logs

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

Organizational Goals - Official

A

goals an organization aims to achieve

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

Organizational Goals - Operative

A

goals that are necessary to achieve an outcome

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

Use Case Diagrams (+ Actor + Use Case Definitions)

A

Describes how a user will interact with a solution - Created using UML (unified modelling language)

Actor - entity that can interact with the solution
Use case - a function or transaction an actor can use

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

Use Case Diagrams - Extend

A

means the entirety of a different use case MAY be included in another

17
Q

Use Case Diagrams - Include

A

means the entirety of a different use case is USED in the running of another

18
Q

Use Case Diagrams - System Boundary

A

drawn with a rectangle that demonstrates whats included in the solution

19
Q

Context Diagrams

A

Visualization of a system that indicates data flow in and out of a solution

20
Q

Context Diagrams - Process

A

Abstract representation of the whole system
Represented as a circle

21
Q

Context Diagrams - Entity

A

Users or external systems that interact with the system
Represented as a rectangle

22
Q

Context Diagram - Data Flow

A

Represents a single piece of data or a logical connection of data as it moves in or out of a system
Represented as an arrow with a label on top

23
Q

Data Flow Diagrams

A

Graphical visualisation of the flow of information in and out of a solution

Contains the core processes in the solution

24
Q

Data Flow Diagrams - Processes

A

abstract representation of a function (e.g. validate PIN).

Must start with a verb

represented as a circle

25
Data Flow Diagrams - Entity
users or external systems that interact with the processes represented as a rectangle
26
Data Flow Diagrams - Data Flow
represents a single piece or logical collection of data as it moves between processes represented as a line
27
Data Flow Diagram - Data Store
represents a collection of data in a solution. Represented by two parallel lines, with the name of the data in store between them
28
Techniques for Generating Design Ideas
Brainstorming Consulting end users Mindmapping
29
Factors influencing the design of solutions x5
- Usability - Affordance - Security - Interoperability - Marketability
30
User Experience
Design that provides relevant and meaningful experiences for users. Includes things like hierarchy, navigation and functionality
31
User Interface
Focuses on appearance. Includes things like colour, shape, spacing and the look and feel of the solution
32
Gantt Chart - Milestones
The achievement of a significant stage in a project time length is 0 Represented with a diamond on the gantt chart
33
Gantt Chart - Dependencies
tasks that require another task to be finished before the task can be completed arrows used to indicate dependencies
34
Gantt Chart - Critical Path
Sequence of tasks from beginning to end. Contains no slack time, is the longest duration and is the minimum possible time the task can be completed