WGU C173 Scripting and Programming

WGU C173 Scripting and Programming WGU - C173 Scripting and Programming Study Guide 1. behavioral diagram: visualizes dynamic behavior of software, such as the flow of an algorithm. Ex: A UML activity diagram is a flowchart, used to describe the flow of an activity or set of activities. 2. Analysis: Determines the goals for a program. The program should support mean, median, mode, max and min calculations. 3. Implementation: Builds the program according to the design and writes the code. A programmer writes each function using statements. 4. Design: Determines the specifics of how to build the program. Each calculation will be a function. User types a letter to invoke each calculation. 5. Testing: Checks that the program meets the goals and checks that ea function works. Class diagrams are used in this phase too and may help ensure that ea class from the diagram exists in the program's code. 6. object: a grouping of data (variables) and operations that can be performed on that data (functions). 7. Abstraction: means to have a user interact with an item at a high-level, with lower-level internal details hidden from the user (aka information hiding or encapsu- lation) 8. structural diagram: visualizes static elements of software, such as the types of variables and functions used in the program. 9. use case diagram: Behavioral diagram used to visually model user interaction w/ a software program, actions back/forth from the software & connections between diff. components of the software. Used to specify behavioral req's of programs. 10. class diagram: structural diagram that can be used to visually model the classes of a pc program, including data members and functions; a code blueprint for creating an object that is composed of data members and functions that operate on those data members. 11. sequence diagram: behavioral diagram that shows interaction bet software components; indicates the order of events; is commonly used to illustrate the order of events needed to handle a particular scenario in software. Commonly created in analysis or design phase. 12. In the Analysis phase: During this phase a use case diagram is created to define how user interacts w/ software 13. In the Design phase: the use case diagram is referenced to determine how the program is built. A class diagram is commonly created in this phase and used as guidance in the implementation phase. 14. In the testing phase: the use case diagram may also be referenced such as when creating usability tests. 15. In the implementation phase: The class diagram created in the design phase is used as guidance in this phase to help write the code. Ex: A spreadsheet app will need a class for a workbook, a worksheet, and a cell; identifies such classes and members of each class. 16. Sequence diagram commonly created in what phases?: Analysis or design phase. May be created in the analysis phase to detail how a user interacts with a software system. May be created in design phase to detail the logic of a particular function. 17. What does a structural diagram show: static items like variables and func- tions. 18. What does a behavioral diagram show: dynamic behavior like flow. A use case diagram is and shows how a user interacts w/ a program. 19. compiled language: is first converted by a tool into machine code, which can run on a particular machine; Ex's: C, C++, Java, and C#. 20. interpreted language (aka scripting language): is a language that is run one statement at a time by another program called an . Ex's include Python, Javascript, and MATLAB. Can run on any machine with an .