Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
chapter 11 implement
| Question | Answer |
|---|---|
| Another term sometimes used for system tests | acceptance tests |
| Process of constructing the programs and core modules that serve as the building blocks of the information system | application development |
| Describe the characteristics of objects in the class | attributes |
| Another term for defect tracking software | bug tracking software |
| SEI's new model that integrates software and systems development into a much larger framework | Capability Maturity Model Integration (CMMI |
| Another term for structured walkthrough | code review |
| Process of turning program logic into specific instructions that the computer system can execute | coding |
| Measures a module's scope and processing characteristics | cohesion |
| Shows a status flag that one module sends to another | control couple |
| Existing data is loaded into the new system | data conversion |
| Used by system developers to document and track program defects, code changes, and replacement code | defect tracking software |
| Reviews interface with a cross-section of people who will work with the new system and ensures that all necessary features have been included | design walkthrough |
| Process of reviewing the program code to spot logic errors | desk checking |
| Approach that causes the changeover from the old system to the new system to occur immediately when the new system becomes operational | direct cutover |
| Describes an information system and helps users, managers, and IT staff who must interact with it | documentation |
| Sending data in an acceptable format from the old system to the new system | exporting |
| Makes it easier to program interactive software products by providing built-in tools and advanced features | integrated development environment (IDE) |
| Testing two or more programs that depend on each other | integration testing |
| Held at the beginning of each iteration cycle to break down the user stories into specific tasks that are assigned to team members | iteration planning meeting |
| Reusable code; Can be invoked from more than one point in a structure chart | library module |
| Another term for integration testing | link testing |
| Parts of the program code that produce incorrect results | logic errors |
| Indicates one or more modules are repeated | loop |
| Modules that are independent | loosely coupled |
| Represent program logic | methods |
| Consists of related program code organized into small units that are easy to understand and maintain | module |
| Provides immediate Help when users have questions or encounter problems | online documentation |
| Environment for the actual system operation | operational environment |
| Contains all the information needed for processing and distributing online and printed output | operations documentation |
| Two programmers work on the same task on the same computer | parallel programming |
| Changeover method that allows you to implement the new system in stages, or modules | phased operationphased operation |
| Changeover method that involves implementing the complete new system at a selected location of the company | pilot operation |
| Web-based broadcast that allows a user to download multimedia files to a PC or portable device | podcast |
| Large framework into which CMMI integrates software and systems development | process improvement |
| Technique for representing program logic that is Similar to structured English, but not language-specific | pseudocode |
| Specifies when user stories will be implemented and the timing of the releases | release plan |
| Software development process that stresses solid design, accurate documentation, and careful testing | software engineering |
| Message one module sends to another | status flag |
| Shows the program modules and the relationships among them using rectangles, arrows, and other symbols | structure chart |
| The programmer simulates each program outcome or result and displays a message to indicate whether or not the program executed successfully | stub testing |
| Lower-level modules that are directed by a higher-level control module | subordinate modules |
| Process of putting the new information system online and retiring the old system | system changeover |
| Describes the system's functions and how they are implemented | system documentation |
| Should contain both correct data and erroneous data and should test all possible situations that could occur | test data |
| One module is linked to internal logic contained in another module | tightly coupled |
| Proceeds from a general design to a detailed structure | top-down approach |
| Training strategy in which you can select knowledgeable users who then conduct sessions for others | train-the-trainer |
| How to use the documentation material in future training sessions | training plan |
| Series of online interactive lessons that present material and provide a dialog with users | tutorial |
| One-way transmission of a pre-recorded Webinar session, delivered whenever a user wants or needs training support | Webcast |
| shows data that one module passes to another. | data couple |
| class diagram includes the class attributes, which describe the characteristics of objects in a class and methods which represent program logic. | program logic |
| a condition line indicates the control module determine which subordinate modules will be invoked depending on a specific condition. | subordinate |
| can be used to model business logic for an information system. | decision table and decision tree |
| defect tracking software documents and tracks replacement code called | patches |
| the purpose of the cmm is to do | improve software quality, reduce development time, cut costs. |
| during implementation. serves as a blue print for constructing a new system | system design specification. |
| describes the inputs and outputs and processing logic for all program modules. | program documentation. |
| compiling the program using a case tool or language. compiler detects syntax errors. which are called | language grammar |
Created by:
gcharl3