Information System - ANS-interrelated components working together to collect, process,
and store info the support decision making
Why do we need a formal process of analyzing/designing a system? - ANS-1. minimize
failure
2. avoid creating an intuition-based system
3. avoid late, over-budgeted projects
4. deliver values as promised
Top 2 reasons for IT project failures (50-70%) - ANS-1. Lack of complete requirements
2. Lack of user involvement
SDLC stands for - ANS-Systems Development Life Cycle
Planning - ANS-WHY: identifying opportunities, analyzing feasibility, developing a work
plan
Analysis - ANS-WHO: develop analysis strategies, determine business requirements,
create use cases, model data
Design - ANS-HOW: How to accomplish the system's objective: design the physical
system...architecture/interfaces/program
Implementation - ANS-construct, install, support plan
What drives the business requirement? - ANS-the business need
, Systems Analyst - ANS-IT consultant who analyzes the SDLC/IS issues
System analyst skills - ANS-interpersonal, business, technical, analytical, management,
ethical
Similar positions to system analyst - ANS-business, infrastructure, requirement, change
management analysts
Methodology - ANS-formalized approach to implementing the SDLC
Categories of methodologies - ANS-1. Waterfall
2. Rapid App Development
3. Agile
Waterfall methodology - ANS-strictly sequential
Waterfall strengths - ANS-1. requirements are defined long before programming begins
2. requirement changes are limited as the project progresses
waterfall weaknesses - ANS-1. must wait a while before you see visible changes
2. long time start to finish
3. requirements overlooked at the beginning, tough to change
variants of waterfall - ANS-1. parallel
2. v-model
parallel - ANS-reduces project time and need for rework (split stages), but creates
subproject that may be difficult to integrate at the end
V-model - ANS-quality improves and there's an emphasis on testing, but it is rigid (for
zero errors) and testing is done all the time
Rapid App Development - ANS-Different versions are made:
1. planning
2. Analysis > Design >implementation
3. system prototype
4. implementation
3 variants of RAD - ANS-1. iterative development
2. system prototyping
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller Hkane. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $7.99. You're not tied to anything after your purchase.
