Simply Java Programming: An Application Driven, Tutorial

Similar documents
Computer Programming AAS Spring 2019 Outcomes

Subject : Computer Science. Paper : Software Quality Management. Module : CASE Tools

S/W Programming & Languages

Java Programming Unit 3: Variables and Arithmetic Operations

Job Ready Assessment Blueprint. Computer Programming. Test Code: 3023 / Version: 01

Introduction to Programming

1) What is the first step of the system development life cycle (SDLC)? A) Design B) Analysis C) Problem and Opportunity Identification D) Development

ITC213: STRUCTURED PROGRAMMING. Bhaskar Shrestha National College of Computer Studies Tribhuvan University

ANZSCO Descriptions The following list contains example descriptions of ICT units and employment duties for each nominated occupation ANZSCO code. And

Chapter Twelve. Systems Design and Development

Unit II. (i) Computer Programming Languages

OHIO ASSESSMENTS FOR EDUCATORS (OAE) FIELD 010: COMPUTER INFORMATION SCIENCE

C++ Programming Language Lecture 2 Problem Analysis and Solution Representation

Outline. Program development cycle. Algorithms development and representation. Examples.

SOFTWARE ENGINEERING. Curriculum in Software Engineering. Program Educational Objectives

Programming Languages and Program Development

Programming Languages and Program Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102

ICT 1. June Advanced level

Procedural Programming

Chapter 1: Introduction to Computers and Java

8/23/2014. Chapter Topics. Introduction. Java History. Why Program? Java Applications and Applets. Chapter 1: Introduction to Computers and Java

Job Ready Assessment Blueprint. Computer Programming. Test Code: 4023 / Version: 01

Low-Level Languages. Computer Programs and Programming Languages

Unit Assessment Guide

Contents. Tutorials Section 1. About SAS Enterprise Guide ix About This Book xi Acknowledgments xiii

Chapter 9. Introduction to High-Level Language Programming. INVITATION TO Computer Science

CT41 (ALCCS) SOFTWARE ENGINEERING JUN 2015

NGINEERING ANUFACTURE

Object-Oriented and Classical Software Engineering DESIGN 11/12/2017. CET/CSC490 Software Engineering Design CHAPTER 14. Stephen R. Schach.

Standard. Number of Correlations

PPSC Competitive Exam for the Post of System Analyst

Chapter 1: An Overview of Computers and Logic

Personalised Learning Checklist ( ) SOUND

Programming Principles and Techniques

4. The is a diagram that graphically depicts the steps that take place in a program. a. Program b. Flowchart c. Algorithm d. Code e.

Computer, Software and Technology Skills

FLOW CHART AND PSEUDO CODE

Oklahoma City Community College

GE PROBLEM SOVING AND PYTHON PROGRAMMING. Question Bank UNIT 1 - ALGORITHMIC PROBLEM SOLVING

Introduction to Computer Programming/Handout 01 Page 1 of 13

Chapter 1 Introduction to Computers and C++ Programming

Chapter 4: Writing and Designing a Complete Program. Programming Logic and Design, Third Edition Introductory

G COURSE PLAN ASSISTANT PROFESSOR Regulation: R13 FACULTY DETAILS: Department::

TASKS IN THE SYSTEMS DEVELOPMENT LIFE CYCLE

Detailed Design. Java Problem Repository & Education Platform JPREP

TOPICS AND SCOPE LEARNING OUTCOME SUGGESTED ACTIVITIES

Meltem Özturan

Software: Systems and Applications Software

Kadi Sarva Vishwavidyalaya, Gandhinagar

What Is SAS? CHAPTER 1 Essential Concepts of Base SAS Software

DEPARTMENT OF COMPUTER AND MATHEMATICAL SCIENCES UNIVERSITI TEKNOLOGI MARA CAWANGAN PULAU PINANG

350 Index 2005 GOAL/QPC

Computer Information Systems

Diploma in Software Testing (DST)

ADMINISTRATIVE MANAGEMENT COLLEGE

Rube Goldberg Final Report Format

(Team Name) (Project Title) Software Design Document. Student Name (s):

ENT 189: COMPUTER PROGRAMMING. H/P: Home page:

STUDY GUIDE. Illinois Licensure Testing System. Computer Science (038) This test is now delivered as a computer-based test.

Contents. Acknowledgments Introduction

Higher Computing Science Software Design and Development - Programming Summary Notes

Appendix A: Objectives and Courseware Locations

CHAPTER 1 Introduction to Computers and Java

COP 1220 Introduction to Programming in C++ Course Justification

Computer Science Technology Department

Programming 1. Lecture 1 COP 3014 Fall August 28, 2017

C++ Programming Language Lecture 1 Introduction

ITM DEVELOPMENT (ITMD)

Computer Fundamentals

1: Software Development and.net. An approach to building software

Ivy s Business Analytics Foundation Certification Details (Module I + II+ III + IV + V)

Chapter 9 Quality and Change Management

SRM ARTS AND SCIENCE COLLEGE SRM NAGAR, KATTANKULATHUR

Computer Information Systems

Pearson Education 2007 Chapter 9 (RASD 3/e)

CIS 1.5 Course Objectives. a. Understand the concept of a program (i.e., a computer following a series of instructions)

Unit 1 Lesson 4 Representing Data. Copyright Houghton Mifflin Harcourt Publishing Company

Copyright 2005 Department of Computer & Information Science

About the Authors. Preface

,

0 Introduction: Computer systems and program development

B.V. Patel Institute of Business Management, Computer & Information Technology, Uka Tarsadia University

Curriculum Mapping for National Curriculum Statement Grades R-12 and Oracle Academy.

Standards/ Strands Essential Questions Skills Assessment. What are the strengths and weaknesses of Processing as a programming language?

Multiple Choice Questions ( 1 mark)

HIGHER SCHOOL CERTIFICATE EXAMINATION COMPUTING STUDIES 3 UNIT (ADDITIONAL) Time allowed One hour and a half (Plus 5 minutes reading time)

Advanced Manufacturing. and Engineering. Machining (Foundation Knowledge) Level 2 Diploma in. Qualification Specification

NOCTI Study Guide Yesterday s Study Questions. Correct Answer are included.

Chapter 7: Software Engineering. Copyright 2015 Pearson Education, Inc.

Overview. Certificate of Achievement

Software design descriptions standard

Discovering Computers Chapter 13 Programming Languages and Program Development

Systems Analysis and Design in a Changing World, Fourth Edition

CIS 120. Introduction to Programming

Unit 6 - Software Design and Development LESSON 3 KEY FEATURES

Part (04) Introduction to Programming

Component-Level Design. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only

CS111: PROGRAMMING LANGUAGE1. Lecture 2: Algorithmic Problem Solving

1) Which of the following is an example of a programming language? 1) A) Microsoft Word B) English C) HTML D) Java

COMPUTING SUBJECT KNOWLEDGE AUDIT

Transcription:

Simply Java Programming: An Application Driven, Tutorial st Approach, 1 Edition 2004 Georgia Competency-Based Curriculum Frameworks, Career & Technical Education, Information Technology, Programming and Systems Management (Grades 9-12) Georgia Competency-Based Curriculum Frameworks, Career & Technical Education, Information Technology, Programming and Systems Management, Course 11.41800 PROGRAMMING CONCEPTS 1. Demonstrate knowledge of programming language concepts. Demonstrate knowledge of the concept of physical representation of digitized information (e.g., data, text, image, voice). Demonstrate knowledge of the hardware-software connection. Demonstrate knowledge of the concepts of data and procedural representation. SE: 750-773 SE: 88-113 Analyze programming languages. SE: 3-6 Demonstrate knowledge of the function and operation of compilers and interpreters. SE: 4, 22, 35 Demonstrate knowledge of the basic principles for analyzing a programming language. Demonstrate knowledge of the basics of structured, object-oriented, and event-driven programming. Demonstrate knowledge of how a programming language can support multitasking and exception handling. Demonstrate knowledge of current key programming languages and the environment they are used in (e.g., C, C++, Visual Basic, Java, RPG, COBOL, Assembler). SE: 88-113, 575-641 SE: 663, 666-668 SE: 3-6 1

2. Demonstrate knowledge of the stages of program development. Identify the use of program design tools. SE: 117-122, 140, 183, 956 Demonstrate knowledge of structured/modular programming. Demonstrate knowledge of the information system (IS) life cycle. Demonstrate knowledge of the characteristics and uses of batch processing. Demonstrate knowledge of the characteristics and uses of interactive processing. Demonstrate knowledge of the characteristics and uses of event-driven, object-oriented processing. SE: 88-113, 575-641 3. Develop technical documentation associated with software development. Secure needed information using appropriate reference materials. Analyze specifications. Identify constraints. Identify input and output (I/O) requirements. SE: 116, 119, 182, 455 APPLIED PROGRAMMING LANGUAGES 1. Apply computational and logical operations. Develop programs that use arithmetic operations. SE: 73, 90, 92, 99, 120, 128-129 Develop programs that use relational operators and compound conditions. SE: 160-162, 184 Develop programs that use control breaks. SE: 101, 103 Develop programs that use subtotals and final totals. 2

2. Apply techniques for building applications. Demonstrate knowledge of the development environment. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Use editors. Compile or interpret applications into runable form. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Run an application. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 3

Run an application. SE: 3. Apply language-specific programming techniques. Develop programs using the desired language. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Incorporate the use of sort routines. SE: 407-408 Develop programs designed to create, update, and delete records. Develop programs using menus. SE: 21-47 Develop programs that require user input. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 4

Develop programs that require user input. Demonstrate knowledge of key constructs and commands specific to the language. SE: SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Compile a program. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 5

Test the program. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Correct errors. SE: 36, 86, 101-104, 134-136, 288, 318, 482-483 4. Debug programs. Test/run a program. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Correct syntax errors. SE: 36, 86, 101-104, 134-136, 288, 318, 482-483 Debug compiler errors. SE: 36, 86, 101-104, 134-136, 288, 318, 482-483 Correct common run-time errors. SE: 36, 86, 101-104, 134-136, 288, 318, 482-483 Debug complex logic errors. SE: 36, 86, 101-104, 134-136, 288, 318, 482-483 6

SOFTWARE DEVELOPMENT 1. Demonstrate knowledge of software development methodology. Identify the basic concepts of algorithm development and programming. Demonstrate knowledge of how to complete a project. Demonstrate knowledge of the principles of program design. SE: 115, 122, 206 SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Demonstrate knowledge of different data types. SE: 90-91, 98, 119, 126, 136, 265, 350, 942 Demonstrate knowledge of the software design process. SE: 117-122, 140, 183, 956 7

Demonstrate knowledge of how to resolve program implementation issues. Demonstrate knowledge of software development issues. Demonstrate knowledge of the system life-cycle approach. Demonstrate knowledge of the use, structure, and contents of a requirements specification document. Demonstrate knowledge of how to use a structured methodology to analyze a real-world problem. Demonstrate knowledge of how dataflow diagrams, process specifications, and a data dictionary are used to model functional requirements. Demonstrate knowledge of nonfunctional requirements (e.g., security, integrity, response time, and reliability). SE: 117-122, 140, 183, 956 SE: 117-122, 140, 183, 956 SE: 117-122, 140, 183, 956 SE: 261, 838 Demonstrate knowledge of how to use computeraided software engineering (CASE) tools. Demonstrate knowledge of different system design models (e.g., client server, centralized). Demonstrate knowledge of how to design and implement programs in a top-down manner. Demonstrate knowledge of how to use algorithmic and modular design to develop a problem solution. SE: 117-122, 140, 183, 956 SE: 117-122, 140, 183, 956 SE: 115, 206, 222 Demonstrate knowledge of how concepts of modular design are used to define cohesive modules. Demonstrate knowledge of how programming control structures are used to verify correctness. Demonstrate knowledge of data normalization. 8

2. Demonstrate knowledge of basic software systems design. Access needed information using company and the manufacturers references. Analyze documentation, forms, notes, and source data. Identify constraints. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Identify system processing requirements. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 9

Identify input and output. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Design system inputs, outputs, and processes. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Prepare logic using program flowchart. SE: 117-122, 140, 183, 956 Define variables. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 10

Define variables. SE: Select programming language. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Create design documentation. Prepare a printer spacing chart. Design an implementation plan. Design a project plan. Prepare a dataflow diagram. SE: 117-122, 140, 183, 956 Present the system design to management. Present the system design to users. Select computer-aided software engineering (CASE) tools. Review the design (e.g., peer and/or user walkthrough). 11

3. Develop software requirements/specifications. Access needed information using company references. Analyze requirements/specifications using current approaches (e.g., structured analysis, objectoriented analysis, prototyping, Jackson System Development). Divide design specifications into logical process blocks. SE: 117-122, 140, 183, 956 Identify parameters. Clarify specifications using questioning techniques. Follow specifications or drawings. SE: 117-122, 140, 183, 956 Record the process. Record data. Gather information using interviewing strategies. Identify system requirements. SE: 117-122, 140, 183, 956 Develop informal specifications. Develop formal specifications. Identify documentation needs. Identify computing standards and methodologies. SE: 117-122, 140, 183, 956 Identify security measures. SE: 261, 838 4. Code programs. Access needed information using company and the manufacturers references (e.g., procedural manuals, documentation, standards, work flowcharts). 12

Prepare a detailed flowchart for coding program. SE: 117-122, 140, 183, 956 Design program solution using pseudocode. SE: 120, 125, 150-157, 182-186, 210-211, 239-240, 266-268, 324-325, 347, 367-368, 397-398, 426-427, 455-457, 503-506, 553-554, 577-578, 606-607, 645-646, 666, 670, 693-694, 708-709, 743-745, 791, 824, 856-857 Generate source code using programming tools in accordance with established standards (e.g., BASIC, COBOL, RPG, C). SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Code error-handling techniques. SE: 668 Access data using various data storage methods. SE: 712 Apply logical operators (e.g., AND, OR, NOT). SE: 90, 92, 120, 128-129, 912 Perform program sorts. SE: 407, 408 Develop programs in higher-level languages (e.g., C++, Visual Basic). SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 13

Develop programs in higher-level languages (e.g., C++, Visual Basic). SE: Generate executable code. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Debug compilation errors. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Review code with peers or the design team. SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, 14

Review code with peers or the design team. SE: Apply security measures. SE: 261, 838 Apply computer-aided software engineering (CASE) tools and reverse engineering. Develop dataflow designs and translate them to pseudocode. Translate a logical system design into a physical design in a real environment. SE: 117-122, 125, 140, 150-157, 182-186, 210-211, 239-240, 266-268, 324-325, 347, 367-368, 397-398, 426-427, 455-457, 503-506, 553-554, 577-578, 606-607, 645-646, 666, 670, 693-694, 708-709, 743-745, 791, 824, 856-857, 956 SE: 1, 40, 42, 43, 44, 46, 47, 48, 82, 83, 84, 86, Report progress based on time line. 5. Execute software testing, validation, change control, defect tracking, and documentation. Access needed information. Develop a comprehensive test plan. 15

Develop a test system. Develop test procedures. Perform tests. Document errors. Perform regression tests. Update design documentation. Prepare program documentation. Prepare user documentation. Perform a user-acceptance test. Validate user documentation. Review results with the customer/user. Report progress based on time line. 6. Demonstrate knowledge of data structures. Demonstrate knowledge of techniques for data abstraction. Demonstrate knowledge of program design using abstraction. SE: 792 SE: 792 Demonstrate knowledge of data structures. SE: 407-408, 553-557, 587, 597-598, 793, 800 Analyze mathematically the efficiency of algorithms that manipulate and use data structures in searching, sorting, dictionary operations, and graphing. Estimate algorithm efficiency using basic database concepts. 16

DATABASE ADMINISTRATION 1. Apply databases to actual situations and business problems. Derive a database design from a workflow drawing or other requirement documents. Design a database to solve a business problem or other real-life problem situation. SE: 733-786 Identify the relationship between database components. Sort data on multiple fields. Add/remove filters. Create queries with multiple criteria. Create/apply different types of queries. Join tables in a query. Enhance the design of a form. Create needed subforms. Group data in reports. Make a calculation on a report. Imbed data and graphics. Import data and graphics. Link data and graphics. 2. Create conceptual data models. Analyze model requirements. Identify business entities and the relationships between them. 17

Define data in an integrated data dictionary. Ensure that the conceptual model includes tools to facilitate user access. 3. Create logical data models. Map a data model to a relational model. Identify attributes of model entities and relationships between them. Verify that the logical model is consistent with the conceptual model. Specify integrity constraints. 4. Normalize data models. Normalize a logical data model in accordance with established company policy. Verify that the data model matches specifications. Validate the logical data model with the client. 18