ITEC102 Flashcards

1
Q

An array of components designed to accomplish a particular objective according to plan.

A

System

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

It is a combination of inter-related elements to achieve a common objective.

A

System Integration

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

The architecture of a system defines in high-level structure, exposing its gross organization as a collection of interacting components.

A

System Architecture

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

It is a temporary endeavor undertaken to accomplish a unique product or service.

A

Project

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

These are undesirable situations that prevent the business from fully achieving its purpose, goals and objectives.

A

Problems

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

It is a chance to improve the business even in the absence of specific problems.

A

Opportunity

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

It is a new requirement that is imposed by the management, government, or some external influence.

A

Directive

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

These are the people involved in or affected by the project activities.

A

Stakeholders

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

What helps project succeed?

A
  • Executive support
  • User involvement
  • Experience project manager
  • Clear business objective
  • Minimize scope
  • Standard software infrastructure
  • Firm basic requirement
  • Formal methodology
  • Reliable sources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Focuses on roles and responsibilities, coordination and control.

A

Structural Frame

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

Focuses on providing harmony between needs of the organization and needs of people.

A

Human Resource Frames

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

Assumes organizations are coalitions composed of varied individuals and interest group.

A

Political Frame

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

Focuses on symbols and meanings related to events.

A

Symbolic Frame

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

3 basic organizational structure

A
  • Functional
  • Project
  • Matrix
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

People who do similar task, have similar skill and/ or jobs in an organization.

A

Functional Structure

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

The company will coordinate inter-group relationship to create a work team that can readily meet the need of certain customer or group of customers.

A

Divisional Structure

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

The team members are given more autonomy and expected to take more responsibility for their work.

A

Matrix Structure

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

The teams are put together based on the number of members needed to produce a product or complete the project.

A

Project Organization Structure

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

Project phases and project life cycle

A
  • Concept
  • Development
  • Implementation
  • Support
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Framework for describing the phases involved in developing and maintaining the systems.

A

System Development Life Cycle (SDLC)

21
Q

System development project can follow:

A
  • Predictive model
  • Adaptive model
22
Q

The scope of the project can be clearly articulated and the schedule and cost can be predicted.

A

Predictive model

23
Q

Projects are mission driven and component based, using time-based cycle to meet target dates.

A

Adaptive model

24
Q

It has well-defined, linear stages of systems development and support.

A

Waterfall Model

25
Q

It shows that software is develop using an iterative or spiral approach rather than the linear approach.

A

Spiral Model

26
Q

It provides the aggressive development of operational software.

A

Incremental Release Model

27
Q

It is used for developing prototype to clarify user requirements.

A

Prototyping Model

28
Q

It is used to produce system quickly without sacrificing quality.

A

RAD Model

29
Q

Developers program in pairs and must write the test for their own code.

A

Extreme Programming (XP)

30
Q

Repetitions of iterative development are referred to as sprints, which normally last 30 days.

A

Scrum

31
Q

System Development Life Cycle

A
  1. Identifying problems, opportunities and objectives
  2. Determining information requirements
  3. Analyzing system needs
  4. Designing the recommended system
  5. Developing and documenting software
  6. Testing and maintaining the system
  7. Implementing and evaluating the system
32
Q

These are statements that identity the essential needs of a system in order for it to have value and utility.

A

Requirements

33
Q

Requirements of life cycle

A

The user
1. Elicitation Phase
- Raw Req’ts
2. Organization Phase
- Organised Req’ts
3. Analysis Phase
- Analysed Req’ts
4. Prototype Phase
- Complete user Req’ts
5. Transform to spec
- SPECS

34
Q

The starting point of the requirements engineering proccess is an elicitation proccess that involves the number of people to ensure consideration of a broad scope of potential ideas and candidate problems.

A

Elicitation Phase

35
Q

In this step, there is no transformation of requirements, but simple classification and categorization.

A

Organisation Phase

36
Q

This represents a transformation.

A

Analysis Phase

37
Q

In this way poorly understood requirements may be tested and perhaps strengthened, corrected or refined.

A

Prototype Phase

38
Q

This represents the requirements as the finish product of the stakeholder requirements team.

A

Requirements Documentation and Specification

39
Q

Requirements determination question

A
  • Who does it?
  • What is done?
  • Where is it done?
  • When is it done?
  • How is it done?
  • Why is it done?
40
Q

System Requirements

A
  • Outputs
  • Inputs
  • Process
  • Timing
  • Control
  • Volume sizes and frequencies
41
Q

Fact-Finding Methods

A
  • Sampling
  • Reasearch and site visits
  • Observation of the work environment
  • Questionaires
  • Interviews
  • Prototyping
  • JAD/ joint requirements planning (JRP)
42
Q

These are statements in natural language plus diagrams of services the system provides, together with its operational constraints.

A

User Requirements

43
Q

Describe what the system should do.

A

Functional requirements

44
Q

Consist of constraints that must be adhered to during development.

A

Non-functional requirements

45
Q

Examples of NFR

A
  • Security
  • Operating requirements
  • Lifecycle requirements
  • Limits on development
  • Economic requirements
46
Q

Requirements Documentation

A
  • User Requirement Specification Document
  • System Requirement Specification Document
47
Q

The URD has following information:

A
  1. Functional requirement
  2. Non-functional requirement
48
Q

Tools that aid in developing and understanding system req’ts

A
  • Affinity diagrams
  • Force-field analysis
  • Ishikawa fishbone
  • Pareto diagrams
  • Pugh charts
  • Quality function development (QFD)