0% found this document useful (0 votes)
33 views4 pages

Assignment 2

The document outlines Assignment 2 for the SESE4183 Software Re-Engineering course, focusing on various case studies related to software evolution, COTS implementation, reuse-oriented models, maintenance processes, and legacy system re-engineering. Each case study presents specific scenarios and challenges faced by organizations in adapting and improving their software systems. The assignment includes a strict submission deadline, a late submission policy, and emphasizes the importance of academic integrity.

Uploaded by

bargainbay73
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views4 pages

Assignment 2

The document outlines Assignment 2 for the SESE4183 Software Re-Engineering course, focusing on various case studies related to software evolution, COTS implementation, reuse-oriented models, maintenance processes, and legacy system re-engineering. Each case study presents specific scenarios and challenges faced by organizations in adapting and improving their software systems. The assignment includes a strict submission deadline, a late submission policy, and emphasizes the importance of academic integrity.

Uploaded by

bargainbay73
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SESE4183: Software Re-Engineering

FALL 2023
Assignment - 2
Contents: Week 4-6 Instructor:
Marks: 50 (5*10) Date:
SECTION: Name 1:
ID1:
ID2: Name 2:
Questions Attempted
Question 1:
Question 2:
Question 3:
Question 4:
Question 5:

Submission:
Deadline: 6th December 2023
Late Submission Policy: 25% Deduction /24 Hours.
IMPORTANT
There is a strict policy against plagiarism and cheating. The penalty can be an F grade.
Attach this title page to your assignment with all required fill-ins.
Make the name of submission file as per your registration number, only one member will submit the
assignment

CLO applied: CLO 2: Apply re-engineering techniques to maintain and modify software systems using
software evolutionary processes, and component-based software engineering.
Attempt All Questions in order.

1. Case Study: Applying Lehman's Laws in a Real-World Scenario:


This case study delves into the practical application of Lehman's Laws of Software Evolution
within the context of a well-established, large-scale e-commerce platform. Operating for several
years, the platform encounters the complex task of aligning with evolving customer preferences
and technological advancements, all while ensuring the continued provision of a dependable and
user-friendly experience.
A. Scenario1: The e-commerce platform recognizes that remaining relevant in the market
necessitates continual adaptation to shifting customer preferences.
B. Scenario2: With the passage of time, the e-commerce platform experiences a natural
increase in complexity due to the addition of new features and functionalities.
C. Scenario3: Balancing the introduction of new features with the need to maintain and
enhance existing functionality is a continual challenge for the e-commerce platform.

2. Case Study: Implementing COTS in an Enterprise Resource Planning (ERP) System:


This in-depth case study explores the intricate process of incorporating Commercial Off-The-Shelf
(COTS) solutions into the framework of an Enterprise Resource Planning (ERP) system. The
organization under examination strategically embraces COTS-based solutions to enhance the
efficiency and coherence of its business processes.
The organization, recognizing the need for a comprehensive business process overhaul, opts for a
COTS-based ERP system. The objective is to seamlessly integrate a suite of commercially
available solutions, allowing for the harmonization and optimization of diverse business
functionalities.
A. Situation1: Faced with the task of selecting appropriate COTS components, the
organization navigates through various options to identify those aligning most closely with
its business requirements.
B. Situation2: The introduction of COTS solutions necessitates an adjustment in
organizational processes and workflows.
C. Situation3: Post-implementation, the organization faces the challenge of evaluating the
performance and effectiveness of the integrated COTS solutions.

3. Case Study: Implementing Reuse-Oriented Models in a Software Development


Company:
This case study delves into the strategic initiatives undertaken by a software development company
to elevate its productivity through the deliberate incorporation of reuse-oriented models. The
company, cognizant of the potential benefits of such models, endeavors to optimize its
development processes and outcomes.
With the overarching goal of boosting productivity, the software development company
conscientiously ventures into the realm of reuse-oriented models. The objective is to harness the
inherent efficiencies and advantages offered by these models to streamline development practices
and enhance overall project outcomes.
A. Situation1: Faced with the imperative of adopting reuse-oriented models, the software
development company embarks on the task of integrating these models into its established
development methodologies.
B. Situation2: The transition to reuse-oriented models necessitates a cultural shift within the
organization, requiring employees to adapt to new methodologies.
C. Situation3: Post-adoption, the company grapples with the challenge of ensuring sustained
improvements and identifying areas for further enhancement.

4. Case Study: Implementing IEEE/EIA 1219 Maintenance Process in a Software


Development Company:
This case study delves into the strategic initiatives undertaken by a software development company
committed to fortifying the reliability and longevity of its products. In pursuit of these objectives,
the company conscientiously embraces the IEEE/EIA 1219 Maintenance Process, recognizing its
potential to bring about sustained improvements in product performance and durability.
With a steadfast commitment to enhancing product reliability and longevity, the software
development company consciously adopts the IEEE/EIA 1219 Maintenance Process. The intent is
to systematically integrate and implement the principles outlined in this maintenance standard,
ensuring a structured and holistic approach to the upkeep of its software products.
A. Situation1: At the inception of the adoption process, the company is confronted with the
challenge of evaluating and enhancing the maintainability of its software products.
B. Situation2: Post-assessment, the company faces the challenge of identifying and
addressing problems within existing software and defining necessary modifications.
C. Situation3: The actual implementation of modifications poses challenges related to
ensuring the seamless integration of changes without compromising existing
functionalities.

5. Case Study: Legacy System Re-engineering in a Financial Institution:


This case study delves into the dynamic landscape of a venerable financial institution grappling
with the complexities of a longstanding legacy banking system. Faced with the ever-evolving
landscape of customer expectations and emerging technologies, the institution undertakes a
strategic re-engineering initiative to contemporize its core banking system.
Entrenched in a legacy banking system, the financial institution confronts challenges arising from
the rapid evolution of customer needs and the relentless pace of technological advancements. In
recognition of the imperative to remain agile and responsive to these shifts, the institution makes
a decisive choice to embark on a comprehensive re-engineering initiative aimed at modernizing its
core banking infrastructure.
A. Situation1: The financial institution initiates the re-engineering journey by
comprehensively evaluating and understanding the intricacies of its existing legacy
banking system.
B. Situation2: The institution grapples with the imperative to refactor and modernize the
legacy system in a phased and strategic manner.
C. Situation3: The legacy system's reliance on outdated technologies poses challenges that
necessitate strategic migration and adaptation.

You might also like