Software reengineering in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the sentence to define software reengineering.

Software Engineering

Software reengineering is the process of [1] and improving existing software systems.

Drag options to blanks, or click blank then click option'

Adiscarding

Breplacing

Cignoring

Danalyzing

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'discarding' because it sounds like removing software.

Choosing 'replacing' which is different from improving.

Software reengineering involves analyzing and improving existing software, not discarding or ignoring it.

2fill in blank

medium

Complete the sentence to identify a goal of software reengineering.

Software Engineering

One main goal of software reengineering is to [1] the software's maintainability.

Drag options to blanks, or click blank then click option'

Aignore

Breduce

Cincrease

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'reduce' which would make maintenance harder.

Choosing 'delete' which is unrelated to improving software.

The goal is to increase maintainability so the software is easier to update and fix.

3fill in blank

hard

Fix the error in the sentence about software reengineering.

Software Engineering

Software reengineering always involves [1] the software from scratch.

Drag options to blanks, or click blank then click option'

Arewriting

Brefactoring

Cdocumenting

Dtesting

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'rewriting' which implies starting over.

Choosing 'testing' which is part of development but not the main reengineering step.

Software reengineering does not mean rewriting from scratch but often involves refactoring existing code.

4fill in blank

hard

Fill both blanks to complete the description of software reengineering steps.

Software Engineering

The first step is [1] the existing system, followed by [2] the code to improve it.

Drag options to blanks, or click blank then click option'

Aanalyzing

Bignoring

Crefactoring

Ddeleting

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'ignoring' which skips understanding the system.

Choosing 'deleting' which removes code instead of improving it.

First, the system is analyzed to understand it, then the code is refactored to improve it.

5fill in blank

hard

Fill all three blanks to complete the software reengineering process example.

Software Engineering

During reengineering, developers [1] the code, [2] documentation, and [3] tests to ensure quality.

Drag options to blanks, or click blank then click option'

Arefactor

Bupdate

Crun

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'delete' which removes important parts.

Choosing 'run' for documentation which is incorrect.

Developers refactor code, update documentation, and run tests to maintain quality during reengineering.

Practice

1. What is the main goal of software reengineering?

easy

A. To create new software from scratch

B. To increase the number of software users

C. To delete outdated software permanently

D. To improve old software for easier maintenance and extension

Solution

1. Step 1: Understand the purpose of software reengineering

   Software reengineering focuses on improving existing software, not creating new software or deleting it.

2. Step 2: Identify the main benefit

   The main benefit is making old software easier to maintain and extend.

3. Final Answer:

   To improve old software for easier maintenance and extension -> Option D

4. Quick Check:

   Software reengineering = Improve old software [OK]

Hint: Focus on improving existing software, not creating new [OK]

Common Mistakes:

• Confusing reengineering with new software development
• Thinking it means deleting software
• Assuming it increases user base directly

2. Which of the following is a common step in software reengineering?

easy

A. Analyzing and restructuring existing code

B. Writing new software without reviewing old code

C. Deleting all old documentation

D. Ignoring software bugs

Solution

1. Step 1: Identify typical reengineering activities

   Reengineering involves analyzing and restructuring existing code to improve it.

2. Step 2: Eliminate incorrect options

   Writing new software without review, deleting documentation, or ignoring bugs are not part of reengineering.

3. Final Answer:

   Analyzing and restructuring existing code -> Option A

4. Quick Check:

   Reengineering step = Analyze and restructure code [OK]

Hint: Look for options about improving existing code [OK]

Common Mistakes:

• Choosing options about creating new software
• Ignoring the importance of analysis
• Confusing reengineering with software removal

3. Consider a software system that is outdated but still valuable. Which reengineering approach is most suitable?

medium

A. Software reverse engineering and restructuring

B. Complete rewrite from scratch

C. Ignoring the system and building a new one

D. Deleting the system immediately

Solution

1. Step 1: Understand the system condition

   The system is outdated but valuable, so it should be improved, not discarded.

2. Step 2: Choose the best reengineering approach

   Reverse engineering and restructuring help understand and improve the existing system without starting over.

3. Final Answer:

   Software reverse engineering and restructuring -> Option A

4. Quick Check:

   Outdated but valuable = Reverse engineering [OK]

Hint: Use reverse engineering for valuable outdated software [OK]

Common Mistakes:

• Choosing complete rewrite which is costly
• Ignoring the system instead of improving
• Deleting valuable software

4. A developer tries to reengineer software but skips analyzing the existing code. What is the likely problem?

medium

A. The software will be deleted

B. The reengineering will miss important design issues

C. The software will run faster without analysis

D. The software will automatically improve

Solution

1. Step 1: Understand the role of code analysis in reengineering

   Analyzing existing code helps find design problems and areas to improve.

2. Step 2: Predict consequences of skipping analysis

   Without analysis, important issues remain hidden, causing poor reengineering results.

3. Final Answer:

   The reengineering will miss important design issues -> Option B

4. Quick Check:

   Skip analysis = Miss design issues [OK]

Hint: Never skip code analysis in reengineering [OK]

Common Mistakes:

• Assuming software improves automatically
• Thinking skipping analysis speeds software
• Confusing deletion with reengineering

5. You have a legacy software with duplicated code and outdated modules. Which reengineering strategy best improves maintainability?

hard

A. Adding more duplicated code for backup

B. Deleting all old modules without replacement

C. Refactoring duplicated code and modularizing outdated parts

D. Ignoring the code quality and adding new features

Solution

1. Step 1: Identify problems in legacy software

   Duplicated code and outdated modules reduce maintainability and increase errors.

2. Step 2: Choose reengineering strategy to improve maintainability

   Refactoring removes duplication and modularizing updates old parts, making maintenance easier.

3. Final Answer:

   Refactoring duplicated code and modularizing outdated parts -> Option C

4. Quick Check:

   Fix duplication + modularize = better maintainability [OK]

Hint: Refactor duplicates and modularize outdated code [OK]

Common Mistakes:

• Deleting modules without replacement
• Adding more duplicated code
• Ignoring code quality issues