Scribd
Upload
22 views

CH06 PPT Modified

good

Uploaded by

bobomi7780
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
22 views

CH06 PPT Modified

good

Uploaded by

bobomi7780
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

Systems Analysis & Design

Tenth Edition

Chapter 6
Agile Modeling,
Prototyping, and Scrum

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Agile Modeling, but First Prototyping

• Agile modeling is a collection of innovative, user-centered


approaches to system development
• Prototyping is an information-gathering technique useful
in seeking
– User reactions
– Suggestions
– Innovations
– Revision plans

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Major Topics

• Prototyping
• Agile modeling
• Scrum
• DevOps (derived from Development and Operations)

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Prototyping

• Patched-up
• Nonoperational
• First-of-a-series
• Selected features

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Patched-Up Prototype

• A system that works but is patched up or patched


together
• A working model that has all the features but is inefficient
• Users can interact with the system
• Retrieval and storage of information may be inefficient

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Nonoperational Scale Models

• A nonworking scale mode that is set up to test certain


aspects of the design
• A nonworking scale model of an information system
might be produced when the coding required by the
application is too expensive to prototype but when a
useful idea of the system can be gained through
prototyping of the input and output only

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
First-Of-A-Series Prototype

• Creating a pilot
• Prototype is completely operational
• Useful when many installations of the same information
system are planned
• A full-scale prototype is installed in one or two locations
first, and if successful, duplicates are installed at all
locations based on customer usage patterns and other
key factors

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Selected Features Prototype

• Building an operational model that includes some, but not


all, of the features that the final system will have
• Some, but not all, essential features are included
• Built in modules
• Part of the actual system

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Figure 6.1 Four Kinds of Prototypes

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Users’ Role in Prototyping

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

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Agile Modeling

• Agile methods are a collection of innovative, user-


centered approaches to systems development

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Values and Principles of Agile Modeling

• Communication
• Simplicity
• Feedback
• Courage

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Figure 6.2 Values are Crucial to the Agile
Approach

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
The Basic Principles of Agile Modeling (1 of 3)

• Satisfy the customer through delivery of working software


• Embrace change, even if introduced late in development
• Continue to deliver functioning software incrementally
and frequently
• Encourage customers and analysts to work together daily
• Trust motivated individuals to get the job done

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
The Basic Principles of Agile Modeling (2 of 3)

• Promote face-to-face conversation


• Concentrate on getting software to work
• Encourage continuous, regular, and sustainable
development
• Adopt agility with attention to mindful design
• Support self-organizing teams

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
The Basic Principles of Agile Modeling (3 of 3)

• Provide rapid feedback


• Encourage quality
• Review and adjust behavior occasionally
• Adopt simplicity

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Four Basic Activities of Agile Modeling

• Coding
• Testing
• Listening
• Designing

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Coding

• Coding is the one activity that it is not possible to do


without
• The most valuable thing that we receive from code is
“learning”
• Code can also be used to communicate ideas that would
otherwise remain fuzzy or unshaped

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Testing (1 of 2)

• Automated testing is critical


• Write tests to check coding, functionality, performance,
and conformance
• Use automated tests
• Large libraries of tests exist for most programming
languages
• These are updated as necessary during the project

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Testing (2 of 2)

• Testing in the short term gives extreme confidence in


what you are building
• Testing in the long term keeps a system alive and allows
for changes longer than would be possible if no tests
were written or run

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Listening (1 of 2)

• Listening is done in the extreme


• Developers use active listening to hear their
programming partner
• Because there is less reliance on formal, written
communication, listening becomes a paramount skill

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Listening (2 of 2)

• A developer also uses active listening with the customer


• Developers assume that they know nothing about the
business so they must listen carefully to businesspeople

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Designing (1 of 2)

• Designing is a way of creating a structure to organize all


the logic in the system
• Designing is evolutionary, and so systems are
conceptualized as evolving, always being designed
• Good design is often simple

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Designing (2 of 2)

• Design should allow flexibility


• Effective design locates logic near the data on which it
will be operating
• Design should be useful to all those who will need it as
the development effort proceeds

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Four Resource Control Variables of Agile
Modeling

• Time
• Cost
• Quality
• Scope

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved
Four Core Agile Practices

• Short releases
• 40-hour work week
• Onsite customer
• Pair programming

Copyright © 2019, 2014, 2011 Pearson Education, Inc. All Rights Reserved

You might also like