Module 2

Question 1

Software Development –

Answer 1

The structured approach is needed due to dependence on software

Question 2

User-Designer Communication Gap

Answer 2

Caused by differences in background

Question 3

Benefits of User Involvement

Answer 3

Better alignment with needs

Question 4

Importance of Management Involvement

Answer 4

Ensures commitment

Question 5

Attributes of Well-Engineered Software

Answer 5

Maintainability dependability efficiency usability portability and documentation availability.

Question 6

Software Dependability

Answer 6

Includes reliability safety and security; software should not cause physical or economic damage.

Question 7

Five Software Manuals

Answer 7

Functional description installation document introductory manual reference manual administration manual.

Question 8

Four Fundamental Software Process Activities

Answer 8

Specification development validation evolution.

Question 9

Three Solutions to a System Problem

Answer 9

Leave system unchanged enhance existing system develop a new system.

Question 10

SDLC Stages

Answer 10

Project Identification & Selection → Initiation & Planning → Analysis → Logical Design → Physical Design → Implementation → Maintenance.

Question 11

Logical Design

Answer 11

Defines functional features independent of hardware or software platforms.

Question 12

Physical Design

Answer 12

Transforms logical specifications into technical implementation details.

Question 13

Main Process Models

Answer 13

Waterfall, evolutionary development, formal systems development, reuse-oriented model.

Question 14

Waterfall Model Weakness

Answer 14

Inflexible and difficult to handle requirement changes.

Question 15

Types of Evolutionary Development

Answer 15

Exploratory development and throw-away prototyping.

Question 16

Advantage of Evolutionary Development

Answer 16

Fast feedback and improved requirement understanding.

Question 17

Disadvantage of Evolutionary Development

Answer 17

Poor structure low visibility and specialized tool requirements.

Question 18

Formal Systems Development

Answer 18

Uses mathematical specifications and transformations to produce correct programs.

Question 19

Weakness of Reuse-Oriented Development

Answer 19

Requires requirement compromises and loses control over component evolution.

Question 20

Incremental Development

Answer 20

Builds system in prioritized functional increments.

Question 21

Advantages of Incremental Development

Answer 21

Early delivery reduced risk improved feedback and more testing of core services.

Question 22

Spiral Model Unique Feature

Answer 22

Explicit risk analysis at each loop.

Question 23

Types of Software Risks

Answer 23

Project risks product risks business risks.

Question 24

Risk Management Stages

Answer 24

Identification analysis planning monitoring.

Question 25

Risk Avoidance Strategy

Answer 25

Reduces probability of the risk (e.g. replacing faulty components).

Question 26

Risk Minimization Strategy

Answer 26

Reduces impact of the risk (e.g. cross-train staff).

Question 27

Contingency Plan

Answer 27

A prepared response when the risk occurs.

Question 28

Requirements Engineering

Answer 28

Process of defining required system services and constraints.

Question 29

Types of Requirements

Answer 29

User requirements system requirements software specification.

Question 30

Functional Requirements

Answer 30

Describe system services reactions to inputs and behavior in situations.

Question 31

Non-Functional Requirements

Answer 31

Constraints such as performance usability security and standards.

Question 32

Categories of Non-Functional Requirements

Answer 32

Product organizational and external requirements.

Question 33

Why NFRs Can Be Critical

Answer 33

If unmet the system may be unusable even if functionally correct.

Question 34

Domain Requirements

Answer 34

Requirements from the problem domain or environment.

Question 35

Problems with Domain Requirements

Answer 35

Understandability and implicitness.

Question 36

Goal vs Verifiable NFR

Answer 36

Goal = intention; Verifiable NFR = measurable requirement.

Question 37

CASE Definition

Answer 37

Computer-Aided Software Engineering tools supporting analysis design coding and testing.

Question 38

Types of CASE Tools

Answer 38

Upper-CASE (analysis/design) and Lower-CASE (implementation/testing).

Question 39

CASE Risks

Answer 39

Inadequate standardization unrealistic expectations rushed implementation and weak repository controls.

Question 40

What is a Data Flow Diagram (DFD)?

Answer 40

A graphical representation of how data moves between external entities processes and data stores in a system.

Question 41

Purpose of a DFD

Answer 41

To visualize systems identify inefficiencies map existing systems and plan improvements.

Question 42

External Entity (Source/Sink)

Answer 42

Represents something outside the system that sends data to or receives data from the system.

Question 43

How to label External Entities?

Answer 43

Using singular nouns.

Question 44

Definition of a Process in a DFD

Answer 44

Work or actions performed on data to transform store or distribute it.

Question 45

How to label Processes?

Answer 45

Using verb phrases.

Question 46

Definition of a Data Store

Answer 46

Data at rest representing information stored by the system.

Question 47

How to label Data Stores?

Answer 47

Using noun phrases with no verbs.

Question 48

Definition of a Data Flow

Answer 48

Shows data in motion using arrows that depict movement between system elements.

Question 49

What should NOT be in Data Flow labels?

Answer 49

Verbs.

Question 50

Purpose of DFD Symbols

Answer 50

To visually represent how data enters moves through and exits a system.

Question 51

What is a Context Diagram?

Answer 51

The highest-level DFD showing the entire system as a single process interacting with external entities.

Question 52

Detail level of a Context Diagram

Answer 52

Broad and simple with little system detail.

Question 53

What is a Level 1 DFD?

Answer 53

A breakdown of the context diagram’s single process into multiple subprocesses.

Question 54

What additional elements appear in Level 1 DFDs?

Answer 54

Subprocesses additional data flows and data stores.

Question 55

How many DFD levels can exist?

Answer 55

Multiple levels such as Context Level 1 Level 2 and Level 3.

Question 56

Advantages of DFDs (1)

Answer 56

Simple to understand and helpful for defining system boundaries.

Question 57

Advantages of DFDs (2)

Answer 57

Useful for communicating system knowledge and explaining data flow logic.

Question 58

Are DFDs used in documentation?

Answer 58

Yes they are often included in system documentation.