(SDLC, Prototyping, Spiral model)
- Applies to ALL FIELDS of business, engineering, operations, management, and biology.
a system does
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)
- System problem identification. What is wrong w/ current system? What do users need? IT
Infrastructure= to support user needs through technology.
- Translating user/org. needs in to conceptual design.
Specs of proposed system?
model? What is the flow of the data information?
Translate general/conceptual design into Physical/ Technical Specs. (SW+HW+DB+DBMS) for
marketing, accounting, and other departments.
Testing, acquisition of HW+SW+NW+DB interfaces. Make, buy, or offshore?
Types of Implementations
- Backup, time consuming.
)- Forced to
use new system, updated, time to learn.
- Problem specific, dependent, takes longer.
gives time to
adapt to new system, back up)
SW & HW updates,
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