TIFKK7Ch06 - Chapter 6 Systems Analysis and Design 6-1...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 6 Systems Analysis and Design 6-1 Chapter 6 True-False 1 . Prototyping is best applied late in the systems development life cycle. F (p. 171) 2 . Prototyping is very useful for eliciting user suggestions about changing the prototyped system. T (p. 171) 3 . User reactions to prototyping can be gathered through observation, interviews, and questionnaires. T (p. 172) 4 . A disadvantage of prototyping is the relatively large expense associated with redirecting system plans. F (p. 172) 5 . A prototype that works but is inefficient is referred to as a "first of a series prototype." F (p. 173) 6 . Some prototypes are nonworking models. T (p. 173) 7 . Prototypes that are full-scaled and installed at one location with the intention of later implementation at other locations are referred to as "selected features prototypes." F (p. 173) 8 . Models that include some of the features of the final system are thought of as "mock-ups." F (p. 173) 9 . Prototyping may be used as a replacement for the systems development life cycle. T (p. 174) 1 0 . One reason that prototyping is useful is that user requirements are likely to change over time. T (p. 174) 1 1 . An advantage of prototyping is that systems will be more thoroughly understood before the system is shaped. F (p. 175) 1 2 . Some experts suggest that prototyping be integrated with the system development life cycle. T (p. 175) 1 3 . Generally speaking, prototypes should be built rapidly. T (p. 175) 1 4 . Prototyping can help protect against over committing resources to a project that proves to be unworkable. T (p. 176)
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 6 Agile Modeling and Prototyping 6-2 1 5 . Prototyping modules should be highly interdependent. F (p. 177) 1 6 . One disadvantage of prototypes is that an inadequate prototype may be adopted as a completed system. T (p. 177) 1 7 . User feedback on the prototype should be obtained only one time. F (p. 178) 1 8 . A disadvantage of prototyping is the difficulty in changing the system early in its development. F (p. 178) 1 9 . An advantage of prototyping is the possibility of abandoning systems that prove unworkable. T (p. 178) 2 0 . Most COTS software is too limited to be used for prototyping. F (p. 178) 2 1 . One role of the analyst is to encourage criticism of the prototype. T (p. 179) 2 2 . RAD can be thought of as a specific implementation of prototyping. T (p. 181) 2 3 . Users and analysts meet to identify objectives of the application or system in the RAD design workshop phase. F (p. 182) 2 4 . During the requirements planning phase, users respond to actual working prototypes and analysts refine designed modules based on user responses. F (p. 182) 2 5 . One way that RAD tools differ from one another is in their capabilities to support client/server applications. T (p. 183) 2 6 . The implementation phase of RAD is in many ways less stressful than other phases.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/13/2011 for the course ACCOUNTING 6000 taught by Professor None during the Spring '11 term at Birmingham-Southern College.

Page1 / 12

TIFKK7Ch06 - Chapter 6 Systems Analysis and Design 6-1...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online