THIRD TERM: INFORMATION SYSTEMS DEVELOPMENT AND DATABASE SYSTEMS

TOPIC
1. Information Systems Development
(a) Purposes of systems analysis and design;
(b) Differences between manual systems and computerised systems;
(c) Duties and responsibilities of personnel : managers, systems analysts and programmers;
(d) Differences between types of information systems: TPS, MIS, DSS, ES
2. Systems Development Life Cycle (SDLC)
2.1 Introduction to SDLC

2013
Quest.no

2014
Mark

Quest.no

Mark

DSS-1(a)(b)(c)

Feasibility - 2(a)(b)

(a) Systems development methodologies: waterfall model, rapid application development model and spiral model;
(b) Phases in SDLC: planning, analysis, design, implementation and maintenance with reference to waterfall model.
2.2 Planning phase
(a) Purpose of the planning phase;
(b) Activities in the planning phase: initial evaluation and feasibility study;
(c) Planning phase output : feasibility report, problem statement, project objective, project scope and project schedule.
2.3 Analysis phase
(a) Purpose of the analysis phase;
(b) Activities in the analysis phase: determination of users requirements and structuring of system requirements;
(c) Methods of determining users requirements: interview, survey, observations and review of procedures and
documents;
(e) Structuring of system requirements: process modelling, logical modelling and conceptual data modelling;
(f) use data flow diagrams to model the processes;
(g) use logical model representations: decision tree and decision table;
(h) use entity-relationship (E-R) diagrams to model conceptual data;
(i) Analysis phase Output : users requirements specifications, process model, decision tree or decision table and data
model.
2.4 Design phase
(a) Purpose of the design phase;
(b) Activities in the design phase: logical data design, physical data design and program structure design;
(c) Design phase Output: logical data design, user interfaces, form design, report design and program structures using
structure charts.
2.5 Implementation phase
(a) Purpose of the implementation phase;

7(a)(b)(c)

15

(b) Activities in the implementation phase: coding, testing, installation, evaluation, documentation, training and support;
(c) Types of testing: manual (inspections, walkthroughs and desk checking) and automated (syntax checking, unit
testing, integration test and system test) and user acceptance testing (alpha and beta);
(d) Implementation phase: test report, installed system (direct, parallel, pilot and phased) and documentation (system
and user);
(e) User training and support: (design and content) and (method and delivery).
2.6 Maintenance phase
(a) Purpose of the maintenance phase;

3(a)

(b) Activities in the maintenance phase: obtaining maintenance requests, transforming requests into changes, designing
changes and implementing changes.

3(b)

5(a)

5(b)

5(c)

3. Fundamental of Relational Database Systems

(a) Importance of data as an asset to organisations such as schools and hospitals;
(b) Types of data operation: sorting, validation and abstraction;
(c) Characteristics of good data and information which can help users in making decisions;
(d) Data hierarchy;
(e) Define database, database systems and database management systems (DBMS);
(f) Importance of database systems in administration, business and daily life;
(g)Importance of software, hardware, data, people and procedure as integrated components of a database system;
(h) Functions of the DBMS components: data dictionary, data manipulation language (DML) and data description
language (DDL);
(i) Advantages of database systems as compared to file processing systems;
(j) Representations of a relational database: table, row and column;
(k) Concept of keys: primary key, foreign key and candidate key;
(l) Concept of data integrity.
4. Database Systems Planning, Design and Administration
(a) Data redundancy, data inconsistency, data independency and data abstraction in the context of a database design;
(b) identify the entity set, attribute, relational set and cardinality in data modelling;
(c) use E-R diagrams to model data;
(d) map the E-R diagram to a relational model: one-to-one, one-to-many and many-to-many binary relationships;
(e) Concepts of full functional dependency, partial functional dependency and transitive functional dependency;
(f) normalise the database scheme up to the third normal form (3NF);
(g) Importance of an effective database administration;
(h) Duties and responsibilities of database administrators.
5. Query Language
(a) use the structured query language (SQL) to implement basic data manipulation: adding, deleting, updating,
arranging and retrieving;
(b) use SQL to create tables and to define views.

15

2015
Quest.no

Sys. Analyst-1(a)(b)
4(a)(b)

2 methods - 2

5(a)(b)

Interface - 3

2016
Mark

6
11

10

Quest.no

Mark

6(a)

11

6(b)

7(b)
7(a)(c)(d)

4
11