| 2.3.1. |
Identify and explain coding information and representation of characters (e.g., American Standard Code for Information Interchange [ASCII], Extended Binary Coded Decimal Interchange Code [EBCDIC], Unicode). |
Lessons
|
| 2.3.2. |
Convert between numbering systems (e.g., binary, hexadecimal, decimal). |
Lessons
|
| 2.9.1. |
Identify and incorporate branding strategies. |
Lessons
|
| 2.9.2. |
Determine the scope and purpose of the project. |
Lessons
|
| 2.9.3. |
Determine the target audience, client needs, expected outcomes, objectives, and budget. |
Lessons
|
| 2.9.4. |
Develop a conceptual model and design brief for the project. |
Lessons
|
| 2.9.5. |
Develop a timeline, a communication plan, a task breakdown, costs (e.g., equipment, labor), deliverables, and responsibilities for completion. |
Lessons
|
| 2.9.6. |
Develop and present a comprehensive proposal to stakeholders. |
Lessons
|
| 2.11.1. |
Identify the problem. |
Lessons
|
| 2.11.2. |
Select troubleshooting methodology (e.g., top down, bottom up, follow the path, spot the differences). |
Lessons
|
| 2.11.3. |
Investigate symptoms based on the selected methodology. |
Lessons
|
| 2.11.4. |
Gather and analyze data about the problem. |
Lessons
|
| 2.11.5. |
Design a solution. |
Lessons
|
| 2.11.6. |
Test a solution. |
Lessons
|
| 2.11.7. |
Implement a solution. |
Lessons
|
| 2.11.8. |
Document the problem and the verified solution. |
Lessons
|
| 2.12.1. |
Create a written procedure agreed by the stakeholders and project team for determining the acceptability of the project deliverables. |
Lessons
|
| 2.12.2. |
Develop a test system that accurately mimics external interfaces. |
Lessons
|
| 2.12.3. |
Develop test cases that are realistic, compare with expected performance, and include targeted platforms and device types. |
Lessons
|
| 2.12.4. |
Develop, perform, and document usability and testing integration. |
Lessons
|
| 2.12.5. |
Make corrections indicated by test results. |
Lessons
|
| 2.12.6. |
Seek stakeholder acceptance upon successful completion of the test plan. |
Lessons
|
| 2.13.1. |
Include overall project goals and timelines in the rollout plan. |
Lessons
|
| 2.13.2. |
Communicate rollout plans to key stakeholders in a timely manner. |
Lessons
|
| 2.13.3. |
Conduct final review and approvals according to company standards. |
Lessons
|
| 2.13.4. |
Identify support staff, training needs, and contingency plans in the rollout plan. |
Lessons
|
| 2.13.5. |
Test delivered application to assure that it is fully functional for the customer or user and meets all requirements. |
Lessons
|
| 2.13.6. |
Deliver support and training materials. |
Lessons
|
| 5.1.1. |
Describe how computer programs and scripts can be used to solve problems (e.g., desktop, mobile, enterprise). |
Lessons
|
| 5.1.2. |
Explain how algorithms and data structures are used in information processing. |
Lessons
|
| 5.1.3. |
Model the solution using both graphic tools (e.g., flowcharts) and pseudocode techniques. |
Lessons
|
| 5.1.4. |
Describe, compare, and contrast the basics of procedural, structured, object-oriented (OO), and event driven programming. |
Lessons
|
| 5.1.5. |
Describe the concepts of data management through programming languages. |
Lessons
|
| 5.1.6. |
Analyze the strengths and weaknesses of different languages for solving a specific problem. |
Lessons
|
| 5.1.7. |
Compare the functions and operations of compilers and interpreters. |
Lessons
|
| 5.1.8. |
Describe version control and the relevance of documentation. |
Lessons
|
| 5.2.1. |
Compare primitive types of numeric and nonnumeric data (e.g., integers, floats, Boolean, strings). |
Lessons
|
| 5.2.2. |
Identify the scope of data (e.g., global versus local, variables, constants, arrays). |
Lessons
|
| 5.2.3. |
Write code that uses arithmetic operations. |
Lessons
|
| 5.2.4. |
Write code that uses subtotals and final totals. |
Lessons
|
| 5.2.5. |
Write code that applies string operations (e.g., concatenation, pattern matching, substring). |
Lessons
|
| 5.3.1. |
Explain Boolean logic. |
Lessons
|
| 5.3.2. |
Solve a truth table. |
Lessons
|
| 5.3.3. |
Write code that uses logical operators (e.g., and, or, not). |
Lessons
|
| 5.3.4. |
Write code that uses relational operators and compound conditions. |
Lessons
|
| 5.3.5. |
Write code that uses conditional control structures (e.g., if, if-then-else). |
Lessons
|
| 5.3.6. |
Write code that uses repetition control structures (e.g., while, for). |
Lessons
|
| 5.3.7. |
Write code that uses selection control structures (e.g., case, switch). |
Lessons
|
| 5.3.8. |
Write code that uses nested structures and recursion. |
Lessons
|
| 5.3.9. |
Write code that creates and calls functions. |
Lessons
|
| 5.3.10. |
Code error handling techniques. |
Lessons
|
| 5.3.11. |
Write code to access data repositories. |
Lessons
|
| 5.3.12. |
Write code to create classes, objects, and methods. |
Lessons
|
| 5.4.1. |
Configure options, preferences, and tools. |
Lessons
|
| 5.4.2. |
Write and edit code in the integrated development environment (IDE). |
Lessons
|
| 5.4.3. |
Compile or interpret a working program. |
Lessons
|
| 5.4.4. |
Define test cases. |
Lessons
|
| 5.4.5. |
Test the program using defined test cases. |
Lessons
|
| 5.4.6. |
Correct syntax and runtime errors. |
Lessons
|
| 5.4.7. |
Debug logic errors. |
Lessons
|
| 5.5.1. |
Develop programs using data validation techniques. |
Lessons
|
| 5.5.2. |
Develop programs that use reuse libraries. |
Lessons
|
| 5.5.3. |
Develop programs using operating system calls. |
Lessons
|
| 5.5.4. |
Develop programs that call other programs. |
Lessons
|
| 5.5.5. |
Use appropriate naming conventions and apply comments. |
Lessons
|
| 5.5.6. |
Format output (e.g., desktop, mobile, enterprise, reports, data files). |
Lessons
|
| 5.6.1. |
Determine requirements specification documentation. |
Lessons
|
| 5.6.2. |
Identify constraints and system processing requirements. |
Lessons
|
| 5.6.3. |
Develop and adhere to timelines. |
Lessons
|
| 5.6.4. |
Identify a programming language, framework, and an integrated development environment (IDE). |
Lessons
|
| 5.6.5. |
Identify input and output (I/O) requirements. |
Lessons
|
| 5.6.6. |
Design system inputs, outputs, and processes. |
Lessons
|
| 5.6.7. |
Document a design using the appropriate tools (e.g., program flowchart, dataflow diagrams, Unified Modeling Language [UML]). |
Lessons
|
| 5.6.8. |
Create documentation (e.g., implementation plan, contingency plan, data dictionary, user help). |
Lessons
|
| 5.6.9. |
Review the design (e.g., peer walkthrough). |
Lessons
|
| 5.6.10. |
Present the system design to stakeholders. |
Lessons
|
| 5.6.11. |
Develop the application. |
Lessons
|
| 5.6.12. |
Compare software methodologies (e.g., agile, waterfall). |
Lessons
|
| 5.6.13. |
Perform code reviews (e.g., peer walkthrough, static analysis). |
Lessons
|
| 5.6.14. |
Ensure code quality by testing and debugging the application (e.g., system testing, user acceptance testing). |
Lessons
|
| 5.6.15. |
Train stakeholders. |
Lessons
|
| 5.6.16. |
Deploy the application. |
Lessons
|
| 5.6.17. |
Collect application feedback and maintain the application. |
Lessons
|
| 5.7.1. |
Explain version management and interface control. |
Lessons
|
| 5.7.2. |
Explain baseline and software lifecycle phases. |
Lessons
|
| 5.7.3. |
Analyze the impact of changes. |
Lessons
|
| 6.3.1. |
Select and apply scripting languages used in web development. |
Lessons
|
