Chp 13 - System Implementation Flashcards

(55 cards)

1
Q

Define System Construction

A

Building the system via programming after design approval.

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

When is system construction done?

A
  1. Design of system is approved
  2. Design specifications are available.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the deliverable of system construction?

A

Fully working software or system.

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

List out things to consider before coding ( 8 )

A
  1. Software Architecture to be used
  2. Choice Programming Languages
  3. Programming / Coding Standards
  4. Types of testing to be carried out
  5. User Involvement
  6. Code Repository
  7. Version Control
  8. Security and Copyright
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What to consider about software architecture?

A

Choose architecture and platform supporting application requirements.

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

How to select programming language?

A

Pick language flexible and compatible with requirements.

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

Why follow coding standards?

A

Ensure compliance and maintainability; e.g., IEEE or Open Source.

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

What testing planning is needed before coding?

A

Decide test types for pre and post deployment.

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

Why involve users before coding?

A

Assess user availability and expertise for validation.

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

Where to store code?

A

Use secure, shareable code repository.

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

Purpose of version control?

A

Track modifications, backup, and restore workable code.

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

What about security and copyright?

A

Implement security; identify artifacts needing patent or copyright.

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

List out 5 factors for Good Programming Practice

A
  1. Efficiency
  2. Portability
  3. Security
  4. Readable Codes
  5. Refactoring
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does ‘Efficiency’ mean in code?

A

Keep code short and simple.

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

Why avoid hard-coded values?

A

Use variables for portability and flexibility.

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

What improves code readability?

A

Meaningful names, comments, and consistent formatting.

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

What is refactoring?

A

Improving code structure without changing behavior.

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

What is software testing?

A

Executing software to find bugs and validate requirements.

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

Name a primary testing objective.

A

Finding defects and bugs.

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

Why prevent defects?

A

Avoid expensive recovery and failures.

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

How does testing improve quality?

A

Raises code and product quality.

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

What must testing ensure?

A

End result meets business and user requirements.

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

List out 2 testing approach

A
  1. Static Testing
  2. Dynamic Testing
24
Q

What is static testing?

A

Finding defects without executing code.

25
Techniques used in static testing?
Reviews, static analysis, walkthroughs, inspections.
26
What is dynamic testing?
Executing code to validate behaviour.
27
Which tests are dynamic?
1. Unit 2. Integration 3. System tests.
28
Recommended tools for testing?
Automated testing tools.
29
List out 3 common testing terms
1. White Box Testing 2. Black Box Testing 3. Stub Testing
30
What is white-box testing?
Tester sees input, process, and output; usually programmers test.
31
What is black-box testing?
Only input and output seen; internal process hidden.
32
What is stub testing?
Testing a single execution line, checking data presence.
33
What is unit testing?
Tests specific code sections, typically functions or classes.
34
What is integration testing?
Verifies interfaces between components and their interactions.
35
What is component interface testing?
Checks data handling between units or subsystems.
36
What is system testing?
Tests fully integrated system against requirements.
37
List out popular testing types
1. Installation Testing 2. Compatibility Testing 3. Smoke and Sanity Testing 4. Regression Testing 5. Acceptance Testing 6. Alpha Testing 7. Beta Testing 8. Destructive / Robust Testing 9. Security Testing
38
What is installation testing?
Ensures correct system installation.
39
What is compatibility testing?
Checks compatibility with other software and OS.
40
What is smoke/sanity testing?
Determines if further testing is reasonable.
41
What is regression testing?
Finds defects after major code changes.
42
What is acceptance testing?
Performed by customer for approval and feedback.
43
What is alpha testing?
Simulated operational testing by selected internal users.
44
What is beta testing?
External user acceptance testing after alpha testing.
45
What is destructive testing?
Tests software durability and tolerance.
46
What is security testing?
Tests for intrusion prevention for confidential data.
47
What are program monitors?
Tools for full or partial program monitoring.
48
Examples of program monitors?
Instruction set simulator, hypervisor, program animation.
49
What are debugging tools?
Allow inspection of program variables on error.
50
What are automated GUI testing tools?
Repeat system-level GUI tests automatically.
51
What do benchmark tools do?
Compare run-time performance with rivals.
52
What are profiling tools?
Highlight hot spots and resource usage.
53
What is a test plan?
Guide to test software using sample data.
54
When is a test plan prepared?
Usually before software is built.
55
Who prepares the test plan?
Software testers.