CS605 Final Term Solved Subjective by Junaid

1. Legacy System Assessment

For each legacy system, there are four strategic options:

•  Scrap the system completely: This is the case when system is not making an effective contribution to business processes and business processes have changed significantly and the organization is no longer completely dependent upon the system.
•  Continue maintaining the system: This option is used when system is still required, it is stable, and requirements are not changing frequently
•  Transform the system in some way to improve its maintainability: this option is exercised when system quality has been degraded and regular changes to the system are required.
•  Replace the system with a new system: this path is taken when old system cannot continue in operation and off-the shelf alternative is available or system can be developed at a reasonable cost.

2. Software Reengineering Process Mode

1. Requirement attributes

Answer: We need to tag requirements with certain attributes in order to manage them in an orderly fashion. Attributes are used to establish a context and background for each requirement. They go beyond the description of intended functionality. They can be used to filter, sort, or query to view selected subset of the requirements. A list of possible attributes is enumerated as below:

•  Requirement ID
•  Creation date
•  Last modified on
•  Last modified by
•  Version number
•  Status
•  Origin
•  Subsystem
•  Product Release
•  Priority

3. Requirement Status

The requirement status attribute is one of the most useful ones. It can be used to keep track of different requirements going through different phases. The possible status values are proposed, approved, implemented, verified, and deleted. These are elaborated in the following paragraphs.

2. Proposed:

The requirement has been requested by a source who has the authority to provide requirements.

3. Approved:

The requirement has been analyzed, its impact on the rest of the project has been estimated, and it has been allocated to the baseline for a specific build number or product release. The software development group has committed to implement the requirement.

4. Implemented:

The code that implements the requirement has been designed, written, and unit tested.

5. Verified:

The implemented requirement has been verified through the selected approach, such as testing or inspection. The requirement has been traced to pertinent test cases. The requirement is now considered complete.

6. Deleted:

A planned requirement has been deleted from the baseline. Include an explanation of why and by whom the decision was made to delete the requirement

7. Tasks of Network

•  Concept scoping
•  Preliminary concept planning
•  Technology risk assessment
•  Proof of concept
•  Concept implementation
•  Customer reaction to concept

8. types of reviews

Answer: There are many types of reviews. In general, they can be categorized into two main categories namely

•  informal technical reviews.
•  formal technical reviews.

9. when a system called legacy system

Answer: A system is considered to be a legacy system if it has been in operation for many years. A legacy system has many components. These include business processes, business rules, application software, application data, support software, and system hardware. 10.

If SCM is not its proper place, then what are disadvantages?

Answer: Software configuration management (SCM) is one of the five KPA required for an organization to be at CMM level 2. That means, according to SEI, effective project management is not possible without having a proper SCM function in place. The basic idea behind SCM is to manage and control change. As mentioned by Bernstorff, no matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. It is therefore essential that we manage and control it in a fashion that this continuous change does not convert into chaos.