Software Design Development - Analysis Flashcards

You may prefer our related Brainscape-certified flashcards:
1
Q

Term: Analysis

A

Definition:
Analysis is the initial phase of software development where a systems analyst meets with the client to gather crucial information.

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

Purpose of Analysis

A

Purpose:
Determine the primary purpose of the software.
Understand what the software will be used for.

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

Functional Requirements

A

Definition:
Functional requirements specify the inputs, processes, and outputs of the software.

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

Information Gathered in Analysis

A

Collected Information:
Purpose of the software (description of its intended use).
Functional requirements (inputs, processes, and outputs).

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

Role of Systems Analyst

A

Responsibility:
Systems analyst interacts with the client to collect and document requirements.
Ensures a clear understanding of the client’s needs and objectives.

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

Example 1: Purpose vs. Functional Requirements

A

Purpose

Description:
Create software to enable a user to perform specific tasks or achieve a particular goal.

Example:

Purpose: Develop software to facilitate number entry, validation, and calculation of a running total.
Functional Requirements

Description:
Specify the detailed functionalities and behaviors of the software.

Example:

Functional Requirements:
Allow the user to input ten numbers.
Validate each input to ensure it is between 0 and 100.
Keep a running total of the entered numbers.
Output the final total after all ten numbers have been entered.

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

Outlining Assumptions in Software Development

A

Importance:
Clear assumptions help ensure that everyone involved in the project has a shared understanding of critical factors.

Common Assumptions:
Hardware requirements, software compatibility, internet connectivity, user group IT competency.

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

Design Phase in Software Development

A

Purpose:
In the design phase, the software development team plans how to create the software based on the purpose, functional requirements, and assumptions gathered during analysis.

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

Considerations in the Design Phase

A

Factors Considered:
Purpose of the software.
Detailed functional requirements.
Any assumptions made during analysis.
How to translate these into a concrete plan for development.

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