Chapter 6

Question 1

Agile modelling

Answer 1

Collection of innovative, user-centered approaches to system development

Question 2

Prototyping

Answer 2

Information-gathering technique useful in seeking: 
o User reactions
o Suggestions
o Innovations
o Revision plans

Question 3

4 different types of prototyping:

Answer 3

1. Patched up
2. Non-operational scale models
3. First-of-a-series
4. Selected-features

Question 4

‘patched up’ prototype

Answer 4

• System that works but is patch up or patch together
• working model that has all the features but is inefficient
• users can interact with the system
• retrieval and storage of information may be inefficient

Question 5

‘non-operational scale models’ prototype

Answer 5

• set up to test certain aspects of design
• may be produced when coding required is too expensive to prototype but a useful idea of the system can be gained through prototyping of the input and output only

Question 6

‘first-of-a-series’ prototype

Answer 6

• creating a pilot
• completely operational
• useful when many installations of the same information system are planned
• installed in one or two locations and if successful, duplicates are created

Question 7

‘selected-features’ prototype

Answer 7

operational model that includes some feature that the final system will have

Question 8

users role in prototyping

Answer 8

• honest involvement
• Communicate the purpose of the prototype clearly
• Get suggestions for changing, expanding the prototype and innovation

Question 9

Basic principles of agile modeling

Answer 9

• Satisfy the customer through delivery of working software
• Embrace change
• Continue to deliver functioning software incrementally and frequently
• Encourage customers and analysts to work together
• Promote face to face convo
• Concentrate on getting software to work
• Provide rapid feedback
• Encourage quality

Question 10

Four basic activities of agile modelling

Answer 10

1. coding
2. testing
3. listening
4. designing

Question 11

4 resource control variables of agile modelling

Answer 11

1. time
2. cost
3. quality
4. scope
   - -> there will be a trade off

Question 12

Four core agile practices

Answer 12

1. short releases
2. 40-hour work week
3. onsite customer
4. pair programming

Question 13

6 vital lessons that can be drawn from agile approach to systems

Answer 13

1. Short releases allow system to evolve
2. Pair programming enhances overall quality
3. On-site customers are mutually beneficial
4. 40-hour workweek improves effectiveness
5. Balanced resources and activities support project goals 6. Agile values are crucial to success

Question 14

Scrum

Answer 14

• Begin the project with high level plan that can be changed on the fly
• Success of the project is most important
• Individual success is secondary
• Project leader has some influence on the detail
• System team works with a strict time frame

Question 15

Roles played in the scrum

Answer 15

1. product owner
2. scrum master
3. team member