Software Development and Management

Extensive user involvement

Joint application design session

Prototyping

Code generators

None of the above

feasibility study

requirements elicitation and analysis

requirements specification

requirement validation

none of the above

More speed and lower cost may lead to lower overall system quality.

It may have inconsistent internal designs within and across the system.

Difficulty with module reuse for future systems.

All of the above

Only (1) and (2)

Horizontal prototyping

Exploratory prototyping

Vertical prototyping

Waterfall model

Increment development model

Size oriented metrics

Indicators

Planned value

Actual cost

Objective statement

Presentation prototype

Evolutionary prototyping

Horizontal prototyping

Vertical prototyping

Incremental and Iterative model

Planned value

Actual cost

Objective statement

Earned value analysis

Accomplishment

Presentation prototype

Horizontal prototyping

Vertical prototyping

Embedded prototyping

Low fidelity prototyping

Analysis phase

Design phase

Implementation phase

Development phase

None of the above

A system analyst is responsible to write technical requirements from a critical phase.

A system analyst interacts with designers to understand software limitations.

A system analyst documents the user requirements and the manuals.

A system analyst is the technical head of the team.

None of the above

Testing

Implementation

Maintenance

Design

Analysis

Analysis

Design

Coding

Both (1) and (2)

None of the above

Analysis phase

Design phase

Implementation phase

Maintenance phase

None of the above

cost effectiveness

budget of the project

business scope

All of the above

Only (1) and (2)

Operational Feasibility

Economic Feasibility

Schedule Feasibility

Legal Feasibility

None of the above