BUS 362 - Week 3

Ways to Classify Projects

Size, Cost, Purpose, Length, Risk, Scope, Economic Value

Methodology

Approach to implement the SDLC → steps to perform & deliverables to produce

Characteristics that affect methodology selection

Clarity of user requirements, familiarity with technology, system complexity & reliability, Time/Schedule, Schedule visibility (for managers)

Structured Systems Development - methodologies

Doing each phase thoroughly

• Waterfall, Parallel, V-model

Waterfall

One phase must be completed before the next begins → sequential

• Stable fixed requirements identified early

• Takes a long time to see the new system & finish

Parallel

SDLC phases are executed simultaneously to reduce project time

• Integration is complex & difficult

V-model

Each development phase has a corresponding testing phase

• Testing is planned early for high quality & reliability

• Rigid, takes lots of time & money

Rapid Application Development (RAD) - methodologies

Getting something working into users' hands quickly

• Iterative, System Prototyping, Throwaway Prototyping

Iterative

Developing the system in multiple versions (pieces) to gradually improve

• Users identify needs/feedback

• Delivers quickly → Users face an incomplete system for a time

System Prototyping

Prototype evolves/is refined into the final system through user feedback & re-implementation

Throwaway Prototyping

Develops prototype → learn insights → discard → build real system

• Reduced Issues/uncertainty but takes longer

• Good when unfamiliar with technology

Agile Development

Flexible, iterative development that emphasizes collaboration, adaptability & customer feedback

• Good for Changing requirements → has short development cycles, get feedback often, and adapt (flexible)

• Heavy user involvement → learning curve & better for small projects