| | |
| > | Describe the fundamentals of the systems development life cycle. |
|
|
|
| 2.1 | Overview |
|
|
|
| > | Describe the processes of systems development for the waterfall and prototype models. |
|
|
|
| > | Identify the documentation produced at each phase of the life cycle |
|
|
|
| 2.2 | Requirements Analysis |
|
|
|
| > | Describe the problem definition process. |
|
|
|
| > | Describe the purpose of requirements analysis. |
|
|
|
| > | Describe the components of the feasibility report (project scope, general system objectives, technical, operational and economical feasibility, anticipated costs and benefits, project plan. |
|
|
|
| > | Describe information gathering techniques (interview, questionnaire, observation, participation, record searching). |
|
|
|
| > | Describe some modelling techniques (e.g. Data flow diagrams, Entity Relationship Diagrams, Data dictionaries, Function hierarchy chart). |
|
|
|
| > | Describe the components of the requirements definition. |
|
|
|
| 2.3 | Systems Analysis |
|
|
|
| > | Describe the reasons for amendments to the logical model |
|
|
|
| > | Describe alternative designs for the system (eg. computerised or, manual, centralised or distributed, file based or data based, input methods, package or specially designed system, hardware) |
|
|
|
| > | Describe a design process. (eg. hardware specification, modular design, structure charts, cohesion, coupling, development of program specifications) |
|
|
|
| > | Describe typical information processing steps (data entry, validation, sort, selection, update, and report) |
|
|
|
| > | Describe factors involved in interface design |
|
|
|
| > | Describe the importance of security of business systems (integrity, accessibility, confidentiality, information privacy, employee fraud, theft, physical threats, system controls) |
|
|
|
| > | Describe the components of system specification (overview, objectives, models, input & output documents, program specifications and diagrams, data storage, procedure controls, hardware specifications, clerical procedures, implementation schedule, cost estimates. |
|
|
|
| 2.4 | Systems Implementation |
|
|
|
| > | Describe the various approaches to systems implementation. |
|
|
|
| > | Describe the steps required to implement a system using one of these approaches |
|
|
|
| 2.5 | Systems Review |
|
|
|
| > | Describe the purpose of systems review |
|
|
|
| > | Describe the steps required for systems review |
|
|
|
|
|
|
|
| | |
| 3.1 | Depict diagrammatically the ways in which an information system department fits into the overall business organisation. |
|
|
|
| R | 3.2 | List typical jobs and the tasks required for each (e.g. IS Manager, analyst, programmer, operator, database administrator, network supervisor, user support staff). |
|
|
|
| R | 3.3 | Show diagrammatically at least two different ways in which information systems sections may be organised. |
|
|
|
| R | 3.4 | Outline the standard operating procedures for the systems and operations areas. |
|
|
|
| R | 3.5 | Explain the ways in which the systems and operations sections interact. |
|
|
|
