|
 |
Information and Communications Technology Qualifications
| Back to list of Prescriptions
Prescription: FG70n (FG30n)Fourth Generation Languages |
Aim of Module | To provide students with practical experience in applying a 4GL to develop a complete application.
|
Credits | 7
|
Knowledge Assumed From | DA600 (DA200) Data Analysis
DB600 (DB200) Database Management Systems
SI600 (SI200) Systems Implementation
FG600 (FG200) Fourth Generation Languages
|
Student Learning hours | 70
|
Content Revised | 2000
|
Prescription Expiry Date | Nov 2005
|
The Student Will
| | | C | 1.1 | Explain the syntax of advanced statements provided by the 4GL. These may include some or all of the following: | | | | | | -multiple table handling | | | | -views (logical tables) | | | | -array handling | | | | -multi-user access (table/row locking) | | | | -security and performance issues | | | | A | 1.2 | Demonstrate the use of advanced features such as help facilities, array handling and windowing (if supported by the 4GL). | |
| top
| | | C | 2.1 | Interpret the requirements of the application, identify the users. | | | | C | 2.2 | Identify with the user the overall scope of the model application system. | | | | C | 2.3 | Identify the deliverables such as successful handling of test data, and documentation.
| top
| | | P | 3.1 | Design an overview data model. | | | | P | 3.2 | Implement the data model in the 4GL. | | | | P | 3.3 | Resolve default settings and data checks. | | | | P | 3.4 | Outline test data to be entered to the model at a later stage. | |
| top
| | | C | | Identify the key criteria such as range of language, limitations to application areas, limitations to hardware size, portability to other environments, market penetration, reference customers, vendor support.
| top
| | | P | 5.1 | Establish the output requirements of the application and design with the user and the necessary layouts, by directly using the 4GL. | | | | P | 5.2 | Integrate the screen and report layouts with the data definition in the 4GL. | | | | P | 5.3 | Test both the data definition and the screen and report definitions by using the test data identified earlier. | |
| top
| | | P | 6.1 | Establish the changes to the 4GL defaults required by the application and implementation of these in the 4GL model. | | | | P | 6.2 | Define and implement the application-specific logic. | | | | P | 6.3 | Define and implement the menus necessary to invoke the application. | | | | P | 6.4 | Create test problems for the final test.
| top
| | | P | 7.1 | Use the 4GL documentation facilities (where these exist) to provide a graphic system overview, list the data model, screen and report layouts and program logic in readable form. | | | | P | 7.2 | Demonstrate how 4GL standard messages can be replaced by user-specific messages. | | | | P | 7.3 | Provide a simple Help function (if the 4GL supports the development of Help functions).
| top
| | | P | | Establish that the developed system meets the requirements as specified.
| top
|
|