Approaches to Systems Development Flashcards

1
Q

What are some implications to the Waterfall method?

A
  • Linear
  • Predictive
  • Frozen requirements
  • No iteration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are some implications to the SDLC method?

A
  • Inflexible
  • Users still need to know what they want upfront (dissatisfaction)
  • Lots of documentation needed
  • Backlogs of work
  • Little participation of user
  • Missed targets
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the two Structured Approaches?

A
  • Process Oriented Approach
  • Data Oriented Approach
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is Structured Approach?

A

Applying structured programming approaches to development
- Breaking down processes into smaller processes
- Problem: Processes change frequently
- Solution: Look at the data, its attributes, and its relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Structured Systems Analysis and Design Method (SSADM)?

A
  • A very detailed and prescriptive method
  • System is made up of modules, which is made up of stages, which is made up of steps, which is made up of tasks
  • Too prescriptive
  • Developers are too focused on following the method slowing system creation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Spiral Model?

A
  • Iterative process
  • Risk analysis is key, is the project going in the right direction
  • Can use any sort of engineering that works for the project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is meant by Socio-Technical Approaches?

A
  • Effective Technical and Human Implementation of Computer Systems (ETHICS)
  • The aim is to develop ethically
  • Focuses on being ‘participative’
  • Design team made up of users and developers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is Soft Systems Method?

A
  • Consider real world situations to design effective solutions
  • ‘Soft problems’
  • Considers multiple viewpoints
  • Can be combined with other methods
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is prototyping?

A
  • Allows for active participation
  • Encourages testing ideas in the early stages
  • Gives the opportunity to improve
  • Reduces uncertainty and risk
  • At the time, not well accepted: Very hard to control/predict, reluctance to share unfinished work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is Object Oriented Approach?

A
  • A unified approach
  • Sees the world as interacting objects: Each phase is overlapping
  • Creation of sets of diagrams (UML) to design the systems, that are then used in construction
  • Encourages object reuse
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is Unified Process?

A
  • A framework of software development
  • Lots of different phases, each with overlap
  • No stage can be completed independently
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the four values of Agile Manifesto?

A
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are 3 Agile principles?

A
  • Satisfy customer through early and continuous delivery
  • Welcome changing requirements
  • Deliver working software frequently
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are 4 advantages of Agile?

A
  • Greater customer satisfaction
  • Greater chance of project success
  • System likely to be higher quality
  • Impact of changes and risks not as severe
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are 4 disadvantages of Agile?

A
  • Can be difficult to control scope (scope creep)
  • Lack of documentation
  • Harder to predict costs, time and resources
  • Demands on communication and collaboration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

When should Agile be used?

A
  • Small to medium sized projects
  • Building something new
  • Projects where requirements are likely to change
  • Deliverables that can be broken down into smaller parts
  • Customer that wants to be involved
  • Projects with strict/short deadlines
17
Q

When should Agile not be used?

A
  • Projects with strict requirements
  • Safety-critical systems
  • Customer not able to be involved
  • Inexperienced team
  • Projects with a fixed timeline or budget
18
Q

What are 3 popular Agile methods?

A
  • Extreme Programming (XP)
  • Kanban
  • SCRUM