WEEK 5 - SDLC AND WATERFALL Flashcards
Define information systems development (ISD)
- the activity of creating or modifying business systems
- involves project management and business analysis
Reasons for ISD
- problems with processes
- problems with existing systems
- increasing competition
etc.
how was ISD used to improve Angostura Limited?
- issues with outdated manual processes leading to inefficiencies
- redesigned sales processes using mobile technology integrated with Enterprise Resource Planning (ERP) systems
- benefits included faster order processing and reduced data entry errors
describe the AMR Corp example of how an ISD can fail?
- failure to “confirm” reservation system due to missed deadlines and lawsuits
what are some reasons why ISD projects fail
- projects never finish/overrun schedule
- over budget and over time
- do not accomplish principal goals
what are the 2 success factors for managing ISD?
- flow control: sequential vs iterative processes, parallel activities where applicable
- managerial controls: monitoring progress and allowing for changes, importance of project management and organizational change
what are the factors to consider in making the business case?
- IT as an investment
- rationale for investment
- alignment with strategic goals
etc
what is the systems portfolio analysis and scoring model
- evaluates alternative system projects
- assigns weights to various features and calculates weighted totals
describe the 4 types of project risk?
- cautiously examine: high potential benefits to firm and high project risk
- Identify and develop: high potential benefits to firm and low project risk
- avoid: low potential benefits to firm and high project risk
- routine projects: low potential benefits to firm and low project risk
what are the 3 options for building a system?
- In-house development
- pros: tailored to specific needs
- cons: high cost and time-intensive - tailored off-the-shelf software
- pros: configurable to business requirements
- cons: may require significant customization - standard off-the-shelf software
- pros: cost-effective and quick deployment
- cons: may not fully match business needs
contrast build vs buy for an information system
- building provides a better match but is expensive and time-consuming
- buying can be cost-effective but might not meet specific needs
explain the system development lifecycle for the waterfall methodology
- system definition
- define system goals and scope
- assess feasibility
- form a project team and plan the project - requirements analysis:
- identify detailed user requirements
- document requirements in a comprehensive report - design development and testing:
- create detailed design documents
- develop and test the system iteratively - implementation:
- deploy the system live
- ensure users and stakeholders start working with it - maintenance
- provide ongoing support and error fixes
- often the most expensive phase
what are the characteristics of the waterfall methodology?
- sequential project flow ‘
- control points or “gates” at each phase
- difficult to revisit earlier phases once completed
what are the challenges and issues with waterfall?
- cost and timetable blowouts
- requirements and documentation difficulty
- scheduling and budgeting difficulties
when should someone use Waterfall?
- suitable for projects where cost/speed is not the primary concern
- effective in environments with strict requirements like health and safety ratings