Ch. 13 - Acquiring Information Systems and Applications Flashcards
IT planning process
- organizational strategic plan
- IT architecture
- IT strategic plan
- IT steering committee
- IT/IS operational plan
3 objectives of IT strategic plan
- must be aligned with organizations strategic plan
- must provide IT architecture that seamlessly networks users, applications and databases
- must efficiently allocate IT development resources among competing projects so that projects can be complete on time + within budget and still have the required functionality
typical IT operational plan includes
- mission statement of the IT function
- IT environment
- objectives of the IT function
- constraints on the IT function
- application portfolio
- resource allocation + project management
evaluating + justifying IT investment
- assessing costs
- assessing benefits
- conducting cost-benefit analysis
4 approaches of cost-benefit analysis
- net present value (NPV) method
- return on investment (ROI)
- break-even analysis
- business case approach
strategies for acquiring IT applications
- purchase prewritten application
- customize a prewritten application
- lease the application
- application service providers (ASP)
- software-as-a-service (SaaS) vendors
- use open source software
- outsourcing
- continuous development
- employ custom development
systems development life cycle (SDLC) stages
- systems investigation
- systems analysis
- systems design
- programming and testing
- implementation
- operation and maintenance
systems of development life cycle (SDLC) team
- users
- systems analysts
- programmers
- technical specialists
- stakeholders
solutions to SDLD system investigation
- do nothing and continue to use existing system
- modify/enhance existing system
- develop new system
SDLC systems investigation feasibility study
- technical feasibility
- economic feasibility
- behavioural feasibility
SDLC: systems analysis
process where systems analysts examine business problem that the organization plants to solve with an IS/IT
- deliverable
set of system requirements (ex. user requirements)
SDLC system deisng
describes how system will resolve the business problem
deliverable:
set of technical system specifications that specify
- system outputs, inputs, calculations or processing, + user interfaces
- hardware, software, databases, telecommunications, personnel, and procedures
- blueprint of how these components are integrated
SDLC programming and testing
- programming
- testing
- testing vs User Acceptance Testing (UAT)
programming
translating design specifications into computer code
testing
process that assesses whether computer code will produce expected and desired results
- intended to detect errors or bugs in computer code
SDLC implementation
process of converting fomr an old computer a new one
converting strategies
- direct conversion
- pilot conversion
- phased conversion
- parallel conversion (or historic parallel)
SDLC operations and maintenance
systems operate while they meet their objectives
- assessed using audits
systems require several types of maintenance
- debugging
- updating
- adding new functions
alternative methods and tools for system development
- joint application design (JAD)
- rapid application development (RAD)
- agile development
- end-user development
- DevOps
joint application design (JAD)
group based, group meetings
rapid application development (RAD)
include JAD, prototyping, iCASE tools
agile development
rapid iterations
end-user development
shadow IT
DevOps
combining development & operations
tools for systems development
- prototyping
- integrated computer-assisted software engineering tools (iCASE and CASE, upper CASE, lower CASE)
- component-based development
- object-oriented development
- containers
- low-code development platforms (LCDP)
component-based development
reusable components
object-oriented development
begin with the aspects of the real world that need to be modelled
containers
level of portability
