Cheat Sheet Exam 2 - System Analysis (SDLC, Prototyping,...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
System Analysis (SDLC, Prototyping, Spiral model) System Analysis : - Applies to ALL FIELDS of business, engineering, operations, management, and biology. What a system does + how it is organized. - Logical and conceptual examination of a set of particular business/information system and procedures. - Defines /reveals general/ conceptual properties of system which may well provide of solution to some existing/ ongoing problem. Kinds of System= Biological (desert, pond), Mechanical (automobile, power plants), Social (organizations, societies, clubs), Computer (PCs, mobiles phones, the web). Model of Genetic process = Input → Process → Output → Control → Input. 3 System Analysis Methodologies: I. Traditional SDLC(PADAIMA)/ Classical/ Waterfall model: - System development life cycle - Structured methodology to understand and develop business info systems. - “Turned Key” system Best Uses? = For recurring, repetitive, standardized processes (banks, utilities) Steps= P lanning, A nalysis, D esign, I mplementation, M aintenance, A udit. Planning - System problem identification. What is wrong w/ current system? What do users need? IT Infrastructure= to support user needs through technology. Analysis - Translating user/org. needs in to conceptual design. Specs of proposed system? Architectural model? What is the flow of the data information? Design- Translate general/conceptual design into Physical/ Technical Specs. (SW+HW+DB+DBMS) for marketing, accounting, and other departments. Implementation- Testing, acquisition of HW+SW+NW+DB interfaces. Make, buy, or offshore? Debugging + Verification. Types of Implementations ( Parallell - Backup, time consuming. Direct(cold turkey )- Forced to use new system, updated, time to learn. Pilot - Problem specific, dependent, takes longer. Phased- gives time to adapt to new system, back up) Maintenance- SW & HW updates, maintenance. Audit- Post implementation audit, does new system solve the problem? Is the info/date reliable, safe? II. Prototyping/ Incremental/ Interactive approach: - Look alike. Develop 1 Module/Version at a time. - Improve with successive modules/ versions - Each prototype= an improvement of previous prototype Reasons for prototyping : - User requirement only partially known for each new Module - Key user involvement w/ each prototype - Less costly than a FULL BLOWN SYSTEM - Relatively quick implementation - Heavy use of “CASE” tools ( need to document (each new Prototype) - Prior Successful Prototype / Version = BLUEPRINT for new Prototype
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
III. Spiral Model - “Evolutionary” Approach - uses BEST features of SDLC + Prototyping - “ECLECTIC” approach (best of the best) Major components of Model= Planning, Risk Analysis (go-no go), Engineering, Customer Evaluation.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 13

Cheat Sheet Exam 2 - System Analysis (SDLC, Prototyping,...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online