When developing a new system what does an organisation do first?
The context of new system planning is defined
What is done in the “context of new system planning” stage?
- Understanding of organisational needs
- Market research and trends
- Feasilibility study
How are the organisational needs understood?
- By defining the business goals/objectives(which could be to increase efficiency, improve service or expand market reach)
- Current system analysis: Examining the limitations and capabilities of exisiting systems and to identify areas of improvement/change
- User requirements: Gather input from users to understand their needs, challenges and expectations from the new system
How is market research done and how are trends identified?
- Benchmarking: Anylsis of similar systems in other organisations(with best practices and innovations)
- Technological trends:Staying updated with the new technology to see if tools or platforms could benefit with the new system
What types of feasibility are assesed?
- Technical feasibility(whether the existing infrastructure can support the new system)
- Economic feasibility(whether the new system is cost effective and a consideration of development operation and maintainence costs)
- Legal and compliance feasibility(whether the system complies with relevant laws regulations and standards)
What are the technical capabilities and constraints when developing a new system?
- Scalability
- Interoperability
- User experience
What is done during a cost-benefit analysis?
- Direct and indirect costs are considered(development, training and maintainence costs)
- Benefits are highlighted(increased efficiency, improved data accuracy, customer satisfaction and competitive advantage)
What are some organisational issues in the new system installation?
- User role implementation: End-users, admins, IT staff, decesion makers
- Underlying technologies: Selection of technologies, data management
- Installation challenges: Customising needs, training and support
- Security and data protection: Risk analysis, data encryption and backup
- Ethical and social considerations: Data privacy, employee well being
What are the parts of the “Change management” phase in developing a new system?
- Identifying the need for change management
- Factors for successful change
- Social and ethical effects of change management
How is the need for change management identified?
- Understanding drivers of change: Technological advancement, market dynamics, regulatory compliance, internal organisational strategy
- Goals for change management: Efficiency, agility, innovation
What are some of the factors that make change successful?
- Key Elements of Strategic Planning: Vision and goals, resource allocation
- Effective Communication: Engagement strategy (all levels),Message consistency
- Training and Empowerment: Capacity building (skills), Empowerment
- Methodical Implementation: Risk management, Monitoring and adjustment
What are some of the possible social and ethical impacts of change?
- Impacts on employers: Strategic challenges(change vs need), cultural shift
- Impacts on employees: psychological impact, change fatigue
- Managing expectations and perceptions: Fairness and transparency, active participation
- Promoting responsible decision making: Stakeholder analysis, ethical frameworks
- Addressing global and cultural differences: Respecting diversity, cross-cultural peace
What are some of the difficulties in changing software systems?
- Users don’t like change
- Omitted features
- Old systems may be faster
- Incompatibility
- Data loss
- High cost
What are the two types of compatibilities?
Software and hardware compatibility
What are some of the software compatibility issues?
- Integration of new and old Systems
- Software updates and versions
What are the solutions to the software compatibility issues?
- Middleware
- Version management
What are some of the hardware compatibility issues?
- Peripheral integration
- System performance
What are the solutions to the hardware compatibility issues?
- Standardisation
- Regular hardware review and upgrade
What is a legacy system?
An outdated system, programming language or application software which is used instead of upgraded versions
Why are legacy systems still used?
- Data can not be changed into newer or standard formats
- Application programs can not be upgraded
What are some of the legacy system compatibility issues?
- Integration issues
- Security vulnerability
- High maintenance cost
What are some of the legacy system compatibility solutions?
- Performing system audits: evaluate perfomance and risk
- Strategic replacement: Phased approach to replace legacy system
- Bridge solution: Using middleware to communicate between old and new systems
What are some of the business merger compatibility issues?
- Data compatibility
- Integration issues
- Transformation of data
- Different use of application software
- Different change management policies
Compare hosting locally to remotely.
Local(Saap):
* Need to buy and maintain servers and software
* Employees to support hardware and software
* Space to house servers
* Electricity cost
On cloud(Saas)
* No need to buy and maintain servers and software
* Fewer employees needed
* Pay for resources used
* Easy to deploy
* Incressed efficiency through use of virtual resources
* 24/7 support
* Remote access
