Term
|
Definition
| Analysts determine what programs will be written and create instructions for the programmers. |
|
|
Term
| Physical data flow diagrams |
|
Definition
| The DFDs created during analysis are modified to show these implementation decisions |
|
|
Term
|
Definition
| The implementation phase consists of developing and testing the system’s software, documentation, and new operating procedures. |
|
|
Term
| Managing the programming process |
|
Definition
| Managing the programming process is the major task of the systems analyst in this phase |
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
| The Physical DFD and the Logical DFD contain the same components? T/F |
|
Definition
|
|
Term
| What's the difference between the physical and logical DFD? |
|
Definition
| The physical DFD contains additional details |
|
|
Term
| How many steps are required to make the transition for the physical DFD? |
|
Definition
|
|
Term
| step 1 logical to physical) Add implementation references |
|
Definition
| Using logical DFD, place the way in which the data stores, data flows, and processes will be implemented in parenthesis below each component. |
|
|
Term
| Step 2 logical to physical) Draw a human-machine boundary |
|
Definition
| Draw a line to separate the automated parts of the system from the manual parts. |
|
|
Term
| step 3 logical to physical)Add system-related data stores, data flows, and processes |
|
Definition
| Add system-related data stores, data flows, and processes to the model. (components have little to do with the business process) |
|
|
Term
| Step 4 logical to physical) Update the data elements in the data flows |
|
Definition
| Update the data flows to include system-related data elements |
|
|
Term
| Step 5 logical to physical) Update the metadata in the CASE repository |
|
Definition
| Update the metadata in the CASE repository to include physical characteristics |
|
|
Term
| What are two characteristics of a system that analysts create? |
|
Definition
|
|
Term
| top-down modular approach |
|
Definition
|
|
Term
|
Definition
| A high-level diagram used to illustrate the organization and interaction of the different pieces of code |
|
|
Term
|
Definition
|
|
Term
| structure chart shows all components of code what hierarchical format? |
|
Definition
| sequence, selection, and iteration. |
|
|
Term
|
Definition
|
|
Term
| what does a MODULE do in a structure chart? |
|
Definition
| Denotes a logical piece of the program |
|
|
Term
| what does a LOOP do in a structure chart? |
|
Definition
| Communicates that a module(s) is repeated. |
|
|
Term
| what does a CONDITIONAL LINE do in a structure chart? |
|
Definition
| Communicates that subordinate modules are invoked by the control module based on some condition. |
|
|
Term
| what does a Data COUPLE do in a structure chart? |
|
Definition
| Communicates that data are being passed from one module to another. |
|
|
Term
| what does a CONTROL COUPLE do in a structure chart? |
|
Definition
| Communicates that a message or a system flag is being passed from one module to another. |
|
|
Term
| what does a OFF-PAGE CONNECTOR do in a structure chart? |
|
Definition
| Identifies when parts of the diagram are continued on another page of the structure chart. |
|
|
Term
| what does a ON-PAGE CONNECTOR do in a structure chart? |
|
Definition
| Identifies when parts of the diagram are continued somewhere else in the same page of the structure chart. |
|
|
Term
| What are the three basic kinds of processes in structure charts? |
|
Definition
1) Afferent processes
2) Central processes
3) Efferent processes |
|
|
Term
| What do Afferent Processes do? |
|
Definition
|
|
Term
| What do Central processes do? |
|
Definition
| Perform critical functions in the operation |
|
|
Term
| What do efferent processes do? |
|
Definition
|
|
Term
| How many kinds of arrangements or structures are there for combining modules? |
|
Definition
|
|
Term
| What are the two kinds of arrangements or structures are there for combining modules? |
|
Definition
| Transaction structures and Transform structure |
|
|
Term
| What are some characteristics of a transaction structure? |
|
Definition
| 1) Few afferent processes, 2) Many efferent processes, 3) Higher levels of the structure chart, 4) Connected with coordinating the production of outputs |
|
|
Term
| What are some characteristics of a transaction structure? |
|
Definition
| 1) Many afferent processes,2) few efferent processes, 3) lower levels of the structure chart, 4) Connected with using inputs to create a new output. |
|
|
Term
| How many steps are involved in building the Structure Chart? |
|
Definition
|
|
Term
| What is step 1 in building a structure chart? |
|
Definition
| 1) Identify modules and levels |
|
|
Term
| What is step 2 in building a structure chart? |
|
Definition
| Identify special connections |
|
|
Term
| What is step 3 in building a structure chart? |
|
Definition
|
|
Term
| What is step 4 in building a structure chart? |
|
Definition
|
|
Term
| what are three measures of good structure chart design? |
|
Definition
| 1) cohesion, 2) coupling, 3) Appropriate levels of fan-in and fan-out |
|
|
Term
|
Definition
| Refers to how well the lines of code within each module relate to each other. |
|
|
Term
| What is SEQUENTIAL cohesion? |
|
Definition
| Output from one task is used by the next |
|
|
Term
| What is FUNCTIONAL cohesion? |
|
Definition
| when all elements of the modules contribute to performing a single task |
|
|
Term
| What is TEMPORAL cohesion? |
|
Definition
| Functions that are invoked at the same time |
|
|
Term
| What is COINCIDENTAL cohesion? |
|
Definition
| There is no apparent relationship among a module's function. |
|
|
Term
| What is LOGICAL cohesion? |
|
Definition
| List of activities; which are to perform is chosen outside of module |
|
|
Term
| What is PROCEDURAL cohesion? |
|
Definition
| elements are performed in sequence but do not share data |
|
|
Term
| What is COMMUNICATIONAL cohesion? |
|
Definition
| Elements contribute to activities that use the same inputs or outputs |
|
|
Term
|
Definition
| The process of separating out a function from one module into a module of its own. (can make modules have a better structure) |
|
|
Term
| Modules should be loosely couples? T/F |
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
| Describes the number of control modules that communicate with a subordinate. |
|
|
Term
|
Definition
|
|
Term
| How many subordinates should you limit a module to? |
|
Definition
| Seven to keep low fan-out |
|
|
Term
|
Definition
| Documents that include explicit instructions on how to program pieces of code. |
|
|
Term
| Is there formal syntax for program specifications? Y/N? |
|
Definition
|
|
