INFORMATION SYSTEMS 622, Assignments of Information Systems

Higher quality. Just as architects consider blueprints before constructing a building, you should consider data before building an app. On average, about 70 percent of software development efforts fail, and a major source of failure is premature coding. A data model helps define the problem, enabling you to consider different approaches and choose the best one.

Typology: Assignments

2016/2017

Uploaded on 12/26/2025

tetteh-1
tetteh-1 🇿🇦

3 documents

1 / 12

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
RICHFIELD GRADUATE INSTITUTE OF TECHNOLOGY (PTY) LTD
FACULTY OF INFORMATION TECHNOLOGY
INFORMATION SYSTEMS 622
2ND SEMESTER ASSIGNMENT
Name & Surname: ICAS No:
Qualification: BSC IT Semester: 2 Module Name: INFORMATION SYSTEMS 622
Date Submitted: 4/5/2018
ASSESSMENT CRITERIA
MARKS
ALLOCATION
EXAMINER
MARKS
MODERATED
MARKS
MARKS FOR CONTENTS
QUESTION 1
20
QUESTION 2
15
QUESTION 3
25
QUESTION 4
10
QUESTION 5
20
TOTAL MARKS
90
MARKS FOR TECHNICAL ASPECTS
1. TABLE OF CONTENTS
Accurate numbering according to the
numbering in text and page numbers.
2
2. LAYOUT AND SPELLING
Font Calibri 12
Line spacing - 1.0
Margin should be justified.
3
3. REFERENCE
According to the Harvard Method
5
TOTAL MARKS
10
TOTAL MARKS FOR THE ASSIGMENT
100
Examiner’s Comments:
Moderator’s Comments:
Signature of Examiner: Signature of Moderator:
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download INFORMATION SYSTEMS 622 and more Assignments Information Systems in PDF only on Docsity!

RICHFIELD GRADUATE INSTITUTE OF TECHNOLOGY (PTY) LTD

FACULTY OF INFORMATION TECHNOLOGY

INFORMATION SYSTEMS 622

2ND SEMESTER ASSIGNMENT

Name & Surname: ICAS No: Qualification: BSC IT Semester: 2 Module Name: INFORMATION SYSTEMS 622 Date Submitted: 4 /5/ ASSESSMENT CRITERIA MARKS ALLOCATION

EXAMINER

MARKS

MODERATED

MARKS

MARKS FOR CONTENTS

QUESTION 1 20

QUESTION 2 15

QUESTION 3 25

QUESTION 4 10

QUESTION 5 20

TOTAL MARKS 90

MARKS FOR TECHNICAL ASPECTS

1. TABLE OF CONTENTS

Accurate numbering according to the numbering in text and page numbers.

2. LAYOUT AND SPELLING

Font – Calibri 12 Line spacing - 1. Margin should be justified.

3. REFERENCE

According to the Harvard Method

TOTAL MARKS 10

TOTAL MARKS FOR THE ASSIGMENT 100

Examiner’s Comments: Moderator’s Comments: Signature of Examiner: Signature of Moderator:

TABLE OF CONTENT

make detailed errors as they write application code, but they are less likely to make deep errors that are difficult to resolve.

Master files They are used for the storage of permanent , or semi-permanent , data, which is used in applications such as stock, sales or payroll. Some of the fields tend to contain data which is fairly static, for example, customer name and address, whilst data in some fields is continually changing, for example, customer balance, as transactions are applied to the file. Such updating is carried out, either through the direct entry (on line) of individual transactions, or from an accumulated set of entries stored on a transaction file. Transaction File These are transient and only exist to allow the updating of master files. Each transaction record contains the key field value of the master record it’s to update (to allow correct matching with its relevant master record), together with data gathered from source documents, for example, invoice amounts which update the balance field in customer accounts

  1. transaction file is sorted into the same order as the master file
  2. each transaction record is read and used to update the corresponding record in the master file
  3. new master record is written to the new master file
  4. after the last transaction record is processed, remaining old master records are written to the new master file

QUESTION 2

Entity-Relationship Diagram with Cardinality Is shown below: In the above diagram, entities are Customer, Employee, Equipment and Project. All these entities are represented with the help of rectangle and relationship between these entities are represented with the help of diamond box. Three types of relation are represented between the entities.

3.4 Flow Chart.

Question 4 Question 5 5.1 Program documentation - describes the inputs, outputs, and processing logic for all program modules. The program documentation is a kind of documentation that gives a comprehensive procedural description of a program. It shows as to how software is written. Program documentation even has the capability to sustain any later maintenance or development of the program. The program documentation describes what exactly a program does by mentioning about the requirements of the input data and the effect of performing a programming task. Thus, if you want to know what a program is meant to do and how it has to be executed, you should refer to the program documentation. The most common examples would be the instruction manuals for a software product, which is given to the end-user. Thus the instruction manual for a programming language like Java or for understanding a word processor can come under the purview of program documentation. The description languages used are informal and are intended to make life easy for the end-user. http://kninn.blogspot.co.za/2010/03/what-is-program- documentation.html E-R diagram for the registrar’s of_ PC Training.