COURSE OUTLINE AND TIMEFRAME

UNIT TITLE : DESIGN PROGRAM LOGIC
UNIT CODE : ICT 313328
UNIT DESCRIPTOR : This unit defines the competency required to describe the various processes in a program to ensure that there is understanding of user and design requirements.

ELEMENT PERFORMANCE CRITERIA
Italicized terms are elaborated in the Range of Variables
1. Select the program logic design approach 1.1. Design documentation is obtained and the requirements for the programs are reviewed and clarified.
1.2. The design approach to be taken in coding and the modules and links required is determined
2. Document the program logic or design 2.1. Diagrams of program flow and modules are structured according to project standards
2.2. Program scope and limits are documented according to project standards
2.3. Special routines or procedures are documented or referenced according to project standards
2.4. References for tables, files, inputs, outputs, and other program functionalities are identified and revised according to program requirements
2.5. Templates are used as applicable
3. Validate the design 3.1. Program flow, states or conditions are checked for interfaces and compliance to design documentation requirements
3.2. Feedback/input is gained from appropriate person as needed



RANGE OF VARIABLES
VARIABLE RANGE
1. Design approach
The various program logic design approach may include, but not limited to the use of:
1.1 pseudo codes
1.2 flowcharts
1.3 diagrams
1.4 ERDs
1.5 HIPO Charts
1.6 data flow diagrams
1.7 data structures
1.8 RAD
1.9 case tools
1.10 prototyping
1.11 modular programming

2. Design documentation This may include:
2.1 Any form of written documentation of the system or program requirements received by a programmer from the systems analyst, project manager or supervisor.
3. Appropriate person This may be the:
3.1 systems analyst
3.2 supervisor
3.3 another programmer
3.4 teacher
3.5 user
4. Project standards This may include, but not limited to:
4.1 Client imposed systems development standards methodologies
4.2 Available commercial tools like: Visio, Smartdraw, or case tools


EVIDENCE GUIDE
1. Critical Aspects of Competency 1.1 Assessment must confirm sufficient knowledge of programming and program logic formulation or design skills.
1.2 Assessment must confirm the ability to meet technical requirements by successfully producing the required program design.
2. Underpinning Knowledge Knowledge includes:
2.1 Understanding of system specification and requirements
2.2 Knowledge of programming or coding
2.3 Knowledge of programming using constructs/ modules/ objects
2.4 Concepts of various program and system lifecycle options
2.5 Knowledge of program design and structure

3. Underpinning Skills Skills include:
3.1 Use and application of various design documentation tools
3.2 Coding programs
3.3 Designing and debugging program logic and flow

4. Resource Implications To demonstrate this unit of competence the following resources will be required:
4.1 Program or design specifications
4.2 Documentation tools
4.3 Personal computer or workstation

5. Methods of Assessment Competency may be assessed through:
5.1 Observation of real or simulated work processes
5.2 Third party reports
5.3 Portfolio assessment
5.4 Interviews

6. Context of Assessment 6.1 Competency may be assessed in the workplace or in a simulated work environment.

tesda