Chapter 1 Flashcards

(44 cards)

1
Q

A collection of components (software, hardware, processes, people).

A

System

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

Designed to work together toward a specific goal.

A

System

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

Subsystems combine to form a complete system.

A

System

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

Definition: Combining different subsystems into one unified system.

Goal: Seamless operation and data sharing.

A

System Integration

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

The structured design and organization of a system.

Shows how modules are arranged and interact.

A

System Architecture

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

_)____ – connects systems at the same level using middleware (flexible & scalable).

A

Horizontal Integration

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

____ – connects across hierarchy levels (operational → management → executive).

A

Vertical Integration

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

____ – direct connections between all systems (messy if many).

A

Star / Spaghetti Integration

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

___ – uses standardized format (JSON, XML) via middleware; most scalable.

A

Common Data Format / Middleware

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

What are the types of System Integration

A
  • Horizontal Integration
  • Vertical Integration
  • Star Integration
  • Common data format / middleware
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the methods of integration

A
  • point to point
  • vertical
  • star
  • Common data format
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the project life cycle (phases)

A
  • initiation
  • planning
  • execution
  • monitoring & controlling
  • closure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the software process model

A
  • waterfal
  • incremental
  • RAd
  • Prototype
  • Spiral
  • Concurrent
  • Agile
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

It connects system that perform similar functions or operate at the same layer in an organization

A

Same Level Integration

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

Uses middleware, API, or integration platform as a central point

A

Centralized Communication

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

Share data seamlessly

A

Data Sharing

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

New subsystem can be added without redesinging the system

A

Flexibility and scalability

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

Integration happens between different functional layers

A

Layered approach

19
Q

information flows upward for decision-making and downward for commands or updates

20
Q

often focuses on one specific process or department

A

Domain-specific

21
Q

Each system has its own separate link to every other system

A

Direct Connection

22
Q

Communication is established without a cnetral hub or middleware

A

Point to Point network

23
Q

When draw, it resembles a star

A

Looks like a star

24
Q

Define purpose, scope, feasibility. Deliverable: Project Charter)

25
Develop projec tplan, schedules, and budgets (Project plan)
Planning
26
Perfom actual work (Product or service)
Execution
27
Track progress, handle changes (Status reports
Monitoring & Controlling
28
Finalize activies, handover, evaluate(Final Report)
CLosure
29
A structured approach to plannig, designing, developing, tessting, deploying, and maintaining software
Software Development Life Cycle
30
Sometimes called the classic life cycle, suggest a systematic, sequantial approach to software development
Waterfall
31
Combines elements of linear and parallel proces flow Applies linear sequences in a staggered fashion as calendar time progresses
Incremental Process
32
is a type of incremental model
RAD
33
can quickly give the customes something to see and use and to provide feedback regarding the delivery and their requirements
RAD (Rapid Application Development)
34
The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements.
Prototype
35
____ is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements.
Prototyping
36
The ___ are usually not complete systems and many of the details are not built in the prototype.
prototype
37
Who made Spiral Process Model
Barry Boehm
38
is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model.
Spiral Model
39
is a risk-driven process model generator that is used to guide multi- stakeholder concurrent engineering of software intensive systems.
Spiral Development
40
One is a ___ for incrementally growing a system’s degree of definition and implementation while decreasing its degree of risk.
cyclic approach
41
The other is a set of ____ for ensuring stakeholder commitment to feasible and mutually satisfactory system solutions.
anchor point milestones
42
sometimes called concurrent engineering, allows a software team to represent iterative and concurrent elements of any of the process models.
Concurrent model
43
is essentially a flexible, iterative, and customer-focused approach that values collaboration, working software, and adaptability over rigid planning and documentation.
Agile model
44