Week 5 Homework Problems
docx
keyboard_arrow_up
School
Ashford University *
*We aren’t endorsed by this school
Course
301
Subject
Information Systems
Date
Feb 20, 2024
Type
docx
Pages
4
Uploaded by LionDetroyer22
Week 5 Homework Problems
Week 5 Homework Problems
By Thomas Pedersen
University of Arizona Global Campus
CST301: Software Technology & Design
Professor: Pete Limon
February 18, 2024 1
Week 5 Homework Problems
9.1 Explain why a software system that is used in a real word environment must change or become progressively less useful.
A software system must change over time, or it risks becoming less useful due to several factors:
1.
Changing Requirements: User needs and business processes evolve, necessitating updates
to the software to meet new requirements.
2.
Technological Advancements: As technology progresses, new capabilities and improvements become available. Software must adapt to leverage these advancements.
3.
Security Vulnerabilities: New security threats emerge constantly. Software must be updated to patch vulnerabilities and protect against attacks.
4.
Compliance and Regulations: Laws and regulations change over time. Software must be updated to ensure compliance with current legal requirements.
5.
Interoperability: Software needs to work with other systems which are also updating and changing, requiring compatibility updates.
6.
Performance: Over time, inefficiencies may be identified in a system, or user load may increase, necessitating performance enhancements.
7.
Hardware Changes: As new hardware is released; software may need updates to ensure compatibility or to take advantage of improved hardware capabilities.
8.
User Experience: To remain competitive and relevant, the user interface and experience may need to be updated to align with current standards and expectations.
9.
Market Dynamics: Competitors may introduce new features, prompting a need for innovation and updates to maintain market position.
2
Week 5 Homework Problems
10. Bug Fixes: Software inevitably has bugs that need to be fixed through updates to ensure it
functions correctly.
Without adapting to these changes, software becomes outdated, less secure, less efficient, and less aligned with user needs, leading to reduced usefulness.
9.4 Under what circumstances might an organization decide to scrap a system when the system assessment suggests it is of high quality and high business value?
An organization might decide to scrap a high-quality, high-value system under certain circumstances, such as:
1.
Strategic Shift: The organization may undergo a strategic realignment that renders the current system misaligned with new business goals.
2.
Mergers and Acquisitions: After a merger or acquisition, the combined entity may opt for a different system to unify operations or to leverage existing licenses and infrastructure.
3.
Vendor Lock-In: The organization might want to avoid vendor lock-in and move to a more open or flexible solution, even if the current system is performing well.
4.
Cost of Ownership: If the total cost of ownership, including maintenance, support, and upgrades, becomes prohibitively expensive, it may be more cost-effective to replace the system.
5.
Technological Obsolescence: The underlying technology of the system may be at risk of becoming obsolete, prompting a proactive transition to newer technology.
6.
Scalability Issues: The system, while currently of high quality, may not be scalable to meet anticipated growth, leading to the decision to invest in a more scalable solution.
3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Week 5 Homework Problems
7.
Integration Challenges: If the system faces significant challenges in integrating with other
necessary tools or systems, it may be more beneficial to switch to a more compatible platform.
8.
Market Innovations: The emergence of innovative solutions offering significant advantages may prompt a switch, even if the current system is still valuable.
9.
Regulatory Compliance: New regulations or legal requirements might necessitate a system that can more easily adapt to these changes.
10. Risk Management: The system might pose a potential risk in terms of security, data privacy, or compliance that is deemed too high to continue its use.
In such cases, the decision to scrap the system is strategic, considering long-term benefits
and alignment with the organization's future direction, rather than the system's current operational performance.
4