ISAT L3 - IT Computer Science 2011

Copyright reserved

NATIONAL CERTIFICATE (VOCATIONAL)

NQF LEVEL 3

PROGRAMME ISAT:

INFORMATION TECHNOLOGY AND COMPUTER SCIENCE

2011 – 2013

This document consists of 17 pages.

INTEGRATED SUMMATIVE ASSESSMENT TASK

ISAT -2- 2011 – 2013 PROGRAMME: Information Technology and Computer Science, Level 3

Copyright reserved

SECTION 1: INTRODUCTION

1. Practical purpose and value of the ISAT to the workplace

The purpose of the Information Technology and Computer Science ISAT is to test students’

ability in applying skills, knowledge, values and attitude in a combination of hardware and

software products and services that people use to manage, access, communicate and share

information (data).

2. Scope of the ISAT

The ISAT comprises Systems Analysis and Design and Programming modules, which the

student(s) must have gained knowledge from the class environment or studying environment that

is related to Information Communication and Technology.

The ISAT project is divided into stages to allow a well oriented process for information systems

development. The project is divided into stages to help students understand the fundamental

concepts and procedures to be followed when planning a project for IS development.

An estimated timeframe is provided to guide the students and the lecturers on how much time is

needed to start and finish the project.

3. ISAT overview

Task Duration for

the task

Total marks for

tasks

Task 1: Initial / Business study 2 days 28

Task 2: Preliminary investigation 5 days 39

Task 3: Systems Analysis and Requirements definition 5 days 37

Task 4: Systems Design and requirements specification 6 days 43

Task 5: Systems Coding and Implementation 10 days 67

Task 6: Compiling Documentation 2 days 36

Total number 30 days 250


Copyright reserved

4. Resources requirements

Access to a computer with the following programs:

1. Word processor such as MS Word.

2. Microsoft Project or Microsoft Visio or Smart Draw software.

3. Microsoft Visual Basic Express or Microsoft Visual Basic.NET.

5. Assessment

The lecturer will evaluate the following during the assessments:

4. Time management – did the student(s) meet all the deadlines?

5. Utility value – Is your solution appropriate in the context of the given scenario?

6. Do the different tasks of development correlate and lead to the final solution as a continuous process?

7. Does the system deliver the functionalities as required and specified by the users?


Copyright reserved

SECTION 2: INSTRUCTION TO LECTURES

Guidelines for the demonstration of the project (information system)

The lecturer will schedule dates and times for demonstrations. About 30 minutes per project

will be allowed for demonstration.

The lecturer must prepare and equip the computer lab with the required tools and software

programs that will ensure successful demonstration or presentation by students.

The lecturer can use a test strategy provided in the technical manual as a guideline and ask

the student(s) to perform parts of or all of the test strategy.

The lecturer may request the student(s) to execute other additional test procedures to make

sure that the entire program is working correctly.

The lecturer can use the mark sheet for Task 3 as a guideline and allocate marks accordingly

during the demonstration.

As part of the demonstration, the lecturer will identify random pieces of programming

code (excluding the 10% recycled code) in the project. The student must then explain

the purpose and working of the randomly selected code to the lecturer. This is done to

ensure that students did the coding themselves. A similar type of procedure will be followed

during the external moderation. If the student cannot explain the code used in the project, no

marks can be awarded to the student for the project.

The lecturer will evaluate the following:

Time management – did the student(s) meet all the deadlines?

Utility value – Is your solution appropriate in the context of the given scenario?

Do the different tasks of development correlate and lead to the final solution as a continuous

process?

Does the system deliver the functionalities as required and specified by the users?


Copyright reserved

SECTION 3: ASSESSMENT TOOLS

A Marking Guideline is provided in a separate document to assist with the marking of Task 4 and must not be provided to students. MARKING GRIDS FOR TASKS 1 – 6 NOTE:

The students must be provided with these marking grids when they start with the project to guide them of what is needed and how they will be assessed.

The students must clearly identify their evidence by entering their name on these marking guides in the space provided.

Consult and use the marking guideline provided for Task 4 in conjunction with the Marking Grid to assess student performance in this task.


Copyright reserved

Student Name ………………………………..

Task 1: Business Study / Initial Study

Po

ssib

le

mar

k

Mar

k o

bta

ined

The Business Case is articulated

Reason(s) for the organization’s embarking on this project. 4

The project description is well articulated. 3

The solution addresses key business issues. 3

Stakeholders are identified. 4

Cost estimation and estimated time-frame is discussed. 2

Measures to avert productivity loss during development and the transition are discussed. 3

A minimal number of risks are discussed. 4

The criteria to measure the success and failure of the project are articulated. 3

Other alternatives are discussed. 2

Total Mark 28


Copyright reserved

Student Name:……………………………….

Task 2: Preliminary Investigation – Criteria

Po

ssib

le

Mar

k

Mar

k o

bta

ined

Pro

ble

m s

tate

men

t

The student described the problem in his/her own words: (No task definition = 0)

4

4 3 1 0

Clearly described and unambiguous – clearly states where the student will go and what needs to be done. Identified all redundant information.

The description is clear but with minor shortcomings. Still evidence of redundant information.

The description is vague, leaving the reader unsure of what the purpose is Little evidence of identifying redundant information.

No description.

Res

earc

h a

nd

In

vest

igat

ion

Investigation clearly defines/explains key areas pertaining to the topic (No evidence of investigation = 0)

3

3 2 1 0

Comprehensive Shows good insight and understanding into all key areas of the topic.

Less comprehensive – minor shortcomings Shows some insight in most of the key areas of the topic.

Shows some insight in some of the key areas.

No description.

Pro

ject

sco

pin

g a

nd

co

nst

rain

ts id

enti

fica

tio

n

Project scoping was done in accordance with the problem statement

4

4 3 2 1

Comprehensive description of the project is articulated, and shows rigid researched information.

Less comprehensive description of the project is articulated, and shows not much rigidity of researched information.

The project is not well scoped as it lacks certain aspects of project scoping, however some descriptions is given.

The learner did not do much research and the project is not scoped.

The process to Staffing the project was undertaken

3

3 2 1 0

The learner showed clear understanding of staffing the project, and provided examples.

The learner showed partial understanding of project staffing, however no examples were provided.

The learner showed little knowledge of project staffing, and no examples have been provided.

No information was provided for project staffing.

Evaluation of systems development approaches

3

3 1

The learner investigated different systems development approaches, and made suitable choice for his/her project.

The learner did not do thorough research of systems development approaches, yet a choice was made.

Systems constraints and risks are identified

2

2 1

Systems constraints and risk are identified. The risks are practicable and well researched.

Systems constraints are not well articulated and the systems risks are not identified.

Fact-finding techniques are evaluated and chosen, suitable for the project

2

2 1

The learner investigated different data gathering techniques and made a choice on the ones suitable for the project, and provided reasons for the choice.

The learner showed little understanding of data gathering techniques, and did not provide any example or reasons for this task.


Copyright reserved

Task 2: Preliminary Investigation – Criteria (continued)

Po

ssib

le

Mar

k

Mar

k o

bta

ined

Fea

sib

ility

stu

dy

Feasibility study conducted (No feasibility study = 0 marks)

10

10 8 6 3 1

Feasibility study includes technical, operational, organizational, schedule, legal and economic aspects.

Feasibility study includes at least four aspects.

Feasibility study includes only two aspects.

Feasibility study includes only one aspect.

Feasibility is totally irrelevant.

Time frame for development and implementation recommended (No time frame = 0)

4

4 3 2 1

Most appropriate time frame for scenario and well-motivated.

Appropriate time frame recommended but not always well motivated.

Time frame inappropriate or not motivated.

Time frame totally inappropriate and not motivated.

Initial developmental costs are estimated and shown (No recommendation = 0)

4

4 3 2 1

An estimated budget is shown, articulating appropriate costs for development and maintenance.

Appropriate recommendation that includes at least few aspects of the budget is shown.

Appropriate recommendation that includes at least 2 aspects.

Recommendation inappropriate or only includes one aspect.

Total: 39


Copyright reserved

Student Name:…………………………………….

Task 3: Systems Analysis – Criteria Possible Mark

Mark Obtaine

d

Per

form

fac

t-fi

nd

ing

Fact-finding is conducted with recommended techniques

3

3 3 2 1

Fact-finding techniques are described appropriately and are suitable for the project.

Fact finding methods are described with less detail but shows good understanding.

The description of fact finding techniques is provided but with vague or incomplete.

Only listed – no description.

Sample of questions from participants

3

3 2 1 0

Short, clear and correct clear questions relating to the system are provided. More than 7 (seven) questions are provided.

A sample of appropriate questions is provided. The questions are less than 7.

The questions are vague, with less knowledge on the process of questioning or fact finding. Three or two questions are asked.

No sample of questions provided.

Demographical statistical data is conducted

2 2 1 0

Identified all the necessary demographical data according to project.

Identified most of the necessary demographical data according to project.

No description.

Cu

rren

t sy

stem

s an

alys

is a

gai

nst

pro

po

sed

sys

tem

an

alys

is

Analysis of current systems is undertaken

6

6 4 3 1

Entities and processes are identified for analysis on the current system, against the proposed system. More than 5 entities and processes are identified.

Entities and processes are identified for analysis on the current system, against the proposed system. Less than 5 entities and processes are identified, but not in great detail.

Few appropriate entities are defined and analysed on the current system, but with vague explanation.

Entities are analysed, yet not appropriate to the project.

User requirements specification – URS

4

4 3 2 1

Appropriate user requirements are defined. More than five are defined.

Appropriate user requirements are defined, however less than five.

Few vague user requirements are defined, only two are defined.

No user requirements are defined.

Systems requirements specifications – SRS

4 3 2 0

4

Appropriate system requirements are defined. More than five are defined.

Appropriate systems requirements are defined, however less than five.

Few vague system requirements are defined, only two are defined.

No description.


Copyright reserved

Task 3: Systems Analysis – Criteria (continued) Possible

Mark

Mark Obtained

Det

aile

d d

evel

op

men

t ti

me

and

CB

A

Detailed Project development time plan

8

8 6 4 2 0

A chart (Pert or Gantt) is provided showing all tasks and dates accordingly.

A chart is provided showing activities with respective dates.

A chart is provided showing activities with not so clear dates.

A chart is provided but not with all the activities of the project, and less dates.

No chart provided for the project.

Cost Benefit Analysis with NPV and ROI

7

7 5 3 1

The learner tabulated a correct and well calculated CBA of the project showing all the amounts used and those to be used for maintenance for the project. The CBA shows the profit or loss analysis of the project over the specified period of 6 years.

The learner tabulated the CBA table with all the amounts needed for NPV and ROI analysis. The amounts provided are appropriate though to the project.

The learner showed little knowledge in the CBA analysis And provided vague amounts that may be related t the project.

The CBA analysis is provided, though the amounts are inappropriate and profit/loss analysis is displayed.

Total: 37


Copyright reserved

Student Name:………………………………..

Task 4: Design and Specification – Criteria

Possible Mark

Mark Obtained

Des

ign

an

d r

equ

irem

ents

sp

ecif

icat

ion

NO diagrams = 0 for all of the diagrams section

The ERD diagram is created appropriately and effectively

8

8 5 3

The ERD diagram is created and all the appropriate entities are shown with the correct relationships and cardinalities.

The ER-diagram is created with some entities identified and correct relationships shown, yet few cardinalities.

The ER diagram is shown with not many entities and the inappropriate relationships and no cardinalities.

Description of Input (No description = 0)

5 5 3 1

All the inputs are clearly described in terms of user input and other sources of input

Most of the input described in terms of user input and other sources of input

The description of the input is vague or incomplete

Processing : The description of the processing must show clearly how and where processing and manipulation was done to get the desired output e.g. Calculations of data or decisions required (No description = 0)

5 5 3 1

Good, clear and correct description in all instances

Descriptions clear in most instances. Good effort but room for improvement. Not always correct

Descriptions not clear or incomplete/incorrect in most instances

Identification of Output (No identification = 0)

5 5 3 1

Identified all the required output

Identified most of the required output

Identified less than 50% of the required output

The Process Flow diagram is created appropriately and effectively

8

8 5 3

The process diagram shows the correct steps and stages to be followed when registering a student.

The process flow diagram is correct, yet with minor shortcomings and some inappropriate steps.

The diagram is inappropriate but has some processes that are correct.


Copyright reserved

Task 4: Design and Specification – Criteria (continued)

Possible Mark

Mark Obtained

Illustration of Graphical User Interface = GUI input

4

4 3 2 1

Appropriate components in all instances where required. Substantiated choices where required.

Appropriate components in most instances where required. Choices not always substantiated.

Appropriate components in less than 50% of instances where required. Choices not substantiated.

Not done/not appropriate components in all instances.

Illustration of Graphical User Interface = GUI Output

4 3 2 1 4

Appropriate output components identified in all instances where required.

Appropriate output components identified in most instances where required.

Appropriate output components identified in less than 50% of instances where required.

Not done/not appropriate output components identified in all instances.

Illustration of Graphical User Interface = GUI Design

2 1

2 Design appropriate to age level, computer literacy level, visual aesthetics.

Design inappropriate to age level, computer literacy level, visual aesthetics.

Context sensitive help available (+ appropriate tool tip text included = 2) otherwise 1 mark 2

TOTAL MARK 43


Copyright reserved

Student Name: ……………………………..

Task 5: Systems Coding & Implementation – Criteria

Possible Mark

Mark Obtained

Cre

ate

Dat

abas

e

NO Database = 0 for all of the database section

The Database is created appropriately and effectively

3 3 2 1

Table designs appropriate. Table designs speak of an efficient solution.

Table designs are incomplete. Not enough tables to store data as per intended solution.

The database consists of only one table / The tables contained are not appropriate to the intended solution.

Database relationships: (No relationships = 0)

3

3 2 1 0

Primary keys and foreign key in related tables effective and appropriate. Referential Integrity is enforced in all the relationships.

At least one effective and appropriate relationship. Referential Integrity is enforced

At least one effective relationship created / Referential integrity not enforced

Default database keys used / Database relationships inappropriate to intended solution.

Database Data Types ( Default Data Types used = 0)

2 2 1

Appropriate Data Types used. Data types used are inappropriate. Eg Currency used to store Text.

Database Forms Created ( No Forms = 0)

2 2 1

One Form for each database table / Form modified appropriately ( Header, Footer, Layout )

Only one form / Form not modified ( No Header or No Footer)

Database Queries Created ( No Queries = 0 )

2 2 1

Query makes use of one or more tables. Query makes use of one table only.

Database Reports Created ( No Reports = 0 )

3

3 2 1

Two or more reports created and report makes use of (SUM, MIN, MAX, AVERAGE, COUNT),

Two or more reports created / Report makes use of existing query.

Only one report created / Report does not make use of existing queries.

Pro

gra

mm

ing

So

luti

on

NB: Evaluate the source code if the program does not compile or execute.

All Variables named appropriately / according to Naming Conventions (No Naming Convention = 0)

2

Use of Data Structures ( Including Primitive Data Types (Integer, String etc), Abstract Data Types(Arrays, Lists, Queues )

3

4 3 2 1

Used appropriate and

most effective data

structures to solve the

problem in all instances

Used appropriate

and most effective

data structures in

most instances

Appropriate and most

effective use of data

structures in less than

50% of the instances

Inappropriate or ineffective use of data structures


Copyright reserved


(Continued)

Possible Mark

Mark Obtained

Pro

gra

mm

ing

So

luti

on

Use of Selection Structures (IF, ELSEIF, CASE)

4

4 3 2 1


most effective

selection structures to

solve the problem in

all instances


most effective selection

structures in most

instances


effective use of

selection structures in

less than 50% of the

instances

Inappropriate or

ineffective use of

selection structures

Use of iteration structures. (For, Do While, Do Until)

4

4 3 2 1


most effective

repetition structures to

solve the problem in

all instances


most effective repetition

structures in most

instances


effective use of

repetition structures in

less than 50% of the

instances

Inappropriate or

ineffective use of

repetition structures

Use of algorithms or other programming techniques for manipulating data. (Eg Bubble Sort, Binary Search, Multithreading)

4

4 3 2 1

It works correctly.

Appropriately used

and adds value to the

solution

It works correctly. Not

always appropriately

used or does not really

add value to the

solution

Effort made but it does

not work properly.

Inappropriately used.

Not relevant to the

solution

None used or exceeds

more that 10% of code

Use of Modular programming (parameter passing) (Functions, Sub/Procedures)

5

5 4 2 1

Excellent interaction/

communication

between

modules/classes.

Includes parameter

passing

Proficient/appropriate

use of

modules/functions or

other sub-procedures

with small flaws.

Includes parameter

passing between

modules/ functions or

other sub-procedures

but not always

appropriate or correct.

Limited use of


other sub-procedures.

Limited parameter

passing

No use of


other sub-procedures.

No parameters passed

Complexity of Algorithms/Code

4 4 3 2 1

Advanced Skilled Intermediate Basic


Copyright reserved


(Continued)

Possible Mark

Mark Obtained

Pro

gra

mm

ing

So

luti

on

Solution algorithms – (does the code work correctly?)

4

4 2 1

All solution algorithms used in solving problem are appropriate and effective. No logical errors. All the results of processing are correct.

Most of solution algorithms used in solving problems are appropriate and effective. Few logical errors.

Less than 50% of solution algorithms used in solving problem are appropriate and effective. Many logical errors.

Data Validation Techniques –Input (No Validation = 0) Input validated at Design Time or Run Time

5 5 3 2 1

Complete validation of all input.

Most input validated Less than 50 % of input validated / Controls only validated at Design Time (eg: Masks)

Little validation on Input Controls/Components

Error/Exception Handling (No Error Handling = 0)

3

3 2 1

Excellent exception handling by the use of selection structures and try, catch statements. Proper Feedback given to user.

Exceptions minimized by the use of selection structures and try, catch statements. No Feedback given to user.

Exception minimized by the use of selection structures only. No Feedback given to the user.

Program Compiles Successfully 2

Run Time Errors

3

3 2 1

No run time errors. All the options are executed successfully

Some of the options produce errors when executed

Only one of the options can be executed successfully

Output

3

3 2 1

Program gives correct as well as appropriate output in all cases.

Program gives correct and appropriate output in most cases.

Program gives correct and appropriate output in less than 50% of the cases. .

Logical Flow of Events

2

2 1

Easy to navigate between Screens, Appropriate menus to ease navigation.

Navigation between screens difficult/inappropriate. No menu’s to help navigate.

Coding commented to explain the purpose thereof 2

Coding indented and presented in format to enhance readability 2

67


Copyright reserved

Student Name: ……………………………

Task 6: Documentation and General Evaluation - Criteria Possible

Mark

Mark

Obtained

Use

r G

uid

e

Title sheet 1

Table of contents 1

Introduction to the project (genre) 1

Project scope and limitations are clearly described 1

User input requirements/formats 1

Output/reports produced (screen dumps included) 1

Detailed instructions and walk-through (0 = not done)

3

3 2 1

All the steps to be followed when using the program clearly indicated and supported by screen dumps where required. Well structured with a logical flow. Well formulated – easy to understand.

Most of the steps to be followed when using the program clearly indicated and some screen dumps where required. Not always well structured and not always a logical flow. Not always formulated well

Only a few of the steps to be followed when using the program is indicated. No screen dumps. Not well structured. Not formulated well.

Hardware required to run program (1 mark each up to max of 3 marks)

3

Hard drive space, memory, CPU, special devices – Give list List:

Software requirements listed 1

Installation instructions given 1

List of required files 1

User troubleshooting clearly described 1

Gen

eral

Eva

luat

ion

Time Management: (0 = always late, work was never done)

5

5 4-3 2-1

All deadlines met – all 4 tasks and all the required work were done.

Met 4 out of 3 deadlines or submitted on time but some of the work was not done.

Met only two deadlines or submitted on time but most of the work was not done.

Correlation of Tasks

5 5 4-3 2-1

All tasks correlate with each other.

Some tasks correlate with each other.

Tasks do not correlate with each other.

Utility Value

5

5 4-3 2-1

The solution is a working system that can be applied in a real situation

The solution is a system that can be applied in a real situation with some fine tuning

Some parts can be applied in the real situation

Project Deliverables

5 4-3 2-1 5

Systems able to deliver all functionalities as required/specified by users

Systems delivered limited functionalities as required/specified by users

Systems was unable to deliver all functionalities as required/specified by users

Total: 36

GRAND TOTAL: 250


Copyright reserved

SECTION 4: RECORD OF PERFORMANCE

College:

Campus:

Student’s Surname and First Name/s:

Student’s ID Number:

Lecturer’s Surname and Initials:

Date of conclusion of assessment:

ASSESSMENT GRID

TASKS MARK ALLOCATION STUDENT’S MARK

Task 1: Initial / Business study 28

Task 2: Preliminary investigation 39

Task 3: Systems Analysis and Requirements definition 37

Task 4: Systems Design and requirements specification 43

Task 5: Systems Coding & Implementation 67

Task 6: Documentation & Evaluation 36

Total 250

Percentage 100%

COMPETENCE LEVEL INDICATORS

5-Point Achievement Rating Scale

5 (80-100%)

4 (70-79%)

3 (50-69%)

2 (40-49%)

1 (0-39%)

Competency Level Indicators

Rating Code Rating Marks %

5 Outstanding 80 – 100 %

4 Highly Competent 70 –79 %

3 Competent 50 – 69 %

2 Not Yet Competent 40 –49 %

1 Not Achieved 0 – 39%

Student’s competence level:

Student’s signature:

Lecturer’s signature:

Date:

Copyright reserved

NATIONAL CERTIFICATE (VOCATIONAL)

NQF LEVEL 3

INTEGRATED SUMMATIVE ASSESSMENT TASK

PROGRAMME ISAT:

INFORMATION TECHNOLOGY AND COMPUTER SCIENCE

2011 – 2013

This document consists of 9 pages.

INSTRUCTIONS TO STUDENTS

ISAT – Instructions to Students -2- 2011 – 2013 PROGRAMME: Information Technology & Computer Science, Level 3

Copyright reserved

BACKGROUND

This ISAT tests students’ ability in applying skills, knowledge, values and attitude in a

combination of hardware and software products and services that people use to manage access,

communicate and share information (data).

The ISAT comprises Systems Analysis and Design and Principles of Computer Programming

modules, which the student(s) must have gained knowledge from the class environment or

studying environment that is related to Information Communication and Technology.

The table below gives a summary of the six tasks in this ISAT:

Task Duration for the

task

Total marks for

tasks

Task 1: Initial / Business study 2 day 28

Task 2: Preliminary investigation 5 days 39

Task 3: Systems Analysis and Requirements definition 5 days 37

Task 4: Systems Design and requirements specification 6 days 43

Task 5: Systems Coding and Implementation 10 days 67

Task 6: Compiling Documentation 2 days 36

Total number 30 days 250

INSTRUCTIONS:

The student should hand in all the documentation after the demonstration has taken place – at least 48 hours after, however ONLY when the lecturer has (re)assessed the project.

Students should adhere to timeframes

The demonstrations must be done electronically on the computer in the computer lab.

The student(s) must execute his/her computer program and show all the features of the program to the lecturer for evaluation.

The student(s) must hand in the electronic copy of the project that was demonstrated. The lecturer will use this copy to allocate any outstanding marks in order to finalise the mark.


Copyright reserved

Scenario 1 Background of the study Monument FET College has 5000 students at the five campuses across the country. Monument FET College would like to increase the intake of students at the current campuses and expand to two other provinces. The college management IT/IS strategic planning session has decided that it needs to design and develop a new information system that will be able to manage the expansion as well as the influx of students to the college. The college management and its functional department managers have instructed the IT/IS department to embark on the process of systems development and implementation of the state-of-the-art technology across all campuses with the use of the cloud computing technology. The college management has also approved an estimated budget of R2, 500 000 (R2, 5m) to develop and maintain the proposed systems for the next six years. Problem statement

Monument FET College has grown extensively in the last three years, and projections for the next three years indicate that student enrolment will increase by 33%. The College currently has five campuses with future plans to open two more campuses. The current IT network set up allows for the sharing of few resources between the campuses, thus hampering other extensively needed sharing and communication between campuses. The college currently uses a manual system for student registration, were all students (new and old) have to complete an application form for admission, which will later be captured by the admin staff and thereafter filed by the registrar. The current registration process is tedious and time consuming as it takes two months to process all the application forms to be captured and filed. Students must fill in their personal details, residential addresses and postal addresses, parents or guardian details, and also fill in the courses details. The subjects are filled in by the Head of Department of respective departments. Incomplete forms are not captured thus delaying the process of finalizing class registers and the registration process. The disintegration of the current systems at the college does not allow students to inquire or register at the other campuses, rather than were they are attending. The college management has decided to implement the concept of cloud computing to revamp the IT/IS infrastructure for all campuses. The college has contracted your organization to design, develop and implement a new technology infrastructure that would be able to meet the expansion and large enrolments expected at the college. You have been appointed as the Project Manager/Systems Analyst for this project. Use this information and your knowledge to plan, co-ordinate, manage, design and develop and include an analysis presentation that will resemble the optimum solution for the problem experienced at the Monument FET College.

Use a combination of methodologies of Rapid Application Development (RAD), Joint Application Development (JAD) and Structured Analysis, which is based on the concept of Systems Development Life Cycle (SDLC) to develop a new system for Monument FET College.


Copyright reserved

Task 1: Project initiation / Business study

Information: Business case refers to the reasons, justifications for a project. A business case should be comprehensive, yet easy to understand, and it should describe the project clearly, proving the justification to proceed and estimate the project’s financial impact.

NB: The summary report must not have less than 150 words.

1. Prepare a Business case for any of the scenario chosen, using the following

questions/points as your guideline.

a. Why is the organization doing or embarking-on this project?

b. What is the project about?

c. How does the solution address key business issues?

d. Who are the internal stakeholders and external stakeholders of the project?

e. How much will it cost and how long will it take?

f. Will the organization suffer productivity loss during the transition (manual to

computerized)?

g. What are the risks of doing the project? What are the risks of NOT doing the project?

h. How will we measure the success of the project? How will we measure the failure of

the project?

i. What alternatives do we have?

(2 days- 28 marks)


Copyright reserved

NOTE: For this stage, submit a business case documentation consisting of the contents based

on answers from the questions above.

Task 2: Preliminary Investigation

Use the following guidelines to prepare your preliminary investigation documentation. NB: Use the information from the business case to draft your project scope.

1. Understand the problem or opportunity associated with the scenario.

a. Summarise the problem statement in your own words, and provide a clear understanding of what the problem is with the current system.

b. Identify and discuss the critical objectives of the proposed project.

2. Define the project scope and constraints.

a. Summarise the scope of the entire project, beginning with the current situation leading to the proposed system. Give an ideal picture or logic view of what is to be done within the project, and what is NOT to be done within the project.

b. Identify the people who will be involved in the project, termed staffing the project

and assign tasks and responsibilities to each.

c. Evaluate and choose a suitable systems development approach for the project e.g.

Waterfall approach, Parallel approach or Prototyping approach, etc. d. Identify the constraints and risks that may be encountered within the project

development time. (E.g. budget, short time-frame, etc.) e. Investigate the different techniques or methods of gathering data and choose the

ones most suitable to your project. 3. Conduct feasibility study and evaluate different feasibility options.

a. Conduct FIVE feasibility options with regard to your project, to determine its value and significance.

b. Evaluate the following feasibility options against your project.

i. Economic feasibility ii. Technical feasibility iii. Organizational feasibility iv. Operational feasibility v. Schedule feasibility

4. Estimate an initial project development time and costs.

a. Provide an initial development plan and the estimated cost for the project. b. Provide an estimation of the timeframe that it will take to complete the project and

also the amount needed to finance this project. (5 days- 39 marks)


Copyright reserved

Task 3: Analysis and Design

The overall objective of system analysis stage is to understand the proposed project to ensure that it will support the business requirements, and build a solid foundation for the later stage and systems development.

Use the following guideline to plan the documentation required for this stage.

1. Perform fact-finding

a. From the methods or techniques of data gathering investigated in Stage 1 conduct fact-finding based on the JAD/RAD principles.

b. Provide a sample of questions presented to participants and their details as

reference to the fact-finding process. c. Investigate the demographical statistics of the participants (users and managers)

within the IS development project. (E.g. number of female/ male participants, race or ethnicity, level of knowledge on computer literacy).

2. Conduct an analysis of the current system against the analysis of the proposed

system.

a. Conduct a systems analysis of the current systems and the proposed systems focusing on the identification of Who, What, Where, When, How, and Why is involved in the system.

b. The analysis on the above must be based on people (users), processes, networking

& communication, data & information, use-interfaces and system architecture relating to the current/proposed system.

c. Identify and list all the users’ requirements with regard to the proposed system. (User

Requirements Specification - URS). d. Identify and list all the system requirements with regard to the proposed system.

(System Requirements Definition - SRD). 3. Provide a detailed project development time-frame and development cost.

a. Provide a detailed project development plan showing all the activities/tasks to be

undertaken within the project with their start date and end date, including slack time – if allowed.

i. (Use Microsoft Visio, MS Project or other software programs to illustrate the Gantt chart or Pert Chart)

b. Calculate and tabulate a Cost-Benefit Analysis (CBA) showing the Net Present Value

(NPV) of the project, against the possible Return on Investment (ROI) of the project. c. Use the budget amount approved by the management as the total money for the

project, and with the other amounts provided from your own discretion. The CBA/ROI must show the cost of development, operational, maintenance and benefits or losses (if any) through a period of 6 years.

(5 days- 37 marks)


Copyright reserved

Task 4: Design and Requirements Specification

The overall objective of system analysis stage is to understand the proposed project to ensure that it will support the business requirements, and build a solid foundation for the later stage and systems development.

Use the following guideline to plan the documentation required for this stage. NB: Use Microsoft Visio or other drawing programs to draw the diagrams below.

1. Illustrate the proposed system using structured analysis or Object-Oriented analysis

models.

a. Draw an Entity Relationship Diagram to illustrate a logic view of the database. b. Draw a I-P-O Chart showing the el`ements listed below :

Inputs – With descriptions in terms of user inputs and other sources of inputs

Processing – Indicate where and how the processing or the manipulation of

data will be done

Output – Identify all the required outputs

c. Draw a Process Flow Diagram/Flowchart for “Registering a new student”. 2. Draw or illustrate the system-interface for your application.

a. The user-interface forms/screens need not be coded. b. The forms or screens may be showed as a layout of drawings by hand or be plotted

using Microsoft Visual Studio.NET.

3. Prepare an updated project development plan.

a. Provide an updated project development plan, if there were any changes to the schedule.

(6 days- 43 marks)


Copyright reserved

Task 5: System Coding & Implementation

The overall objective of system coding stage is to write the programming code that will implement the solution. This includes coding the GUI that was planned in Task 4, creating

the appropriate algorithms and data structures, debugging and testing the solution.

Use the following guideline to plan the documentation required for this stage. NB: Use Microsoft Access to implement the database design.

Use Microsoft Visual Basic Express / Microsoft Visual Basic.NET 2005 for the coding.

1. Create the Database

a. Use MS Access and create the appropriate and necessary data structures to store and

organise the data. ( Use ERD and IPO created in TASK 4 as guides)

2. Code the Interface

a. Code the GUI (created in Task 4) using Visual Basic Express or Visual Basic.NET.

b. Code the solution using Visual Basic Express or Visual Basic.NET, according to the

requirements and specifications planned in the previous tasks. Marks will be awarded

according to the functionality (Algorithms and Calculations) of the code, together with

general readability of the code, use of comments, Good programming practices (Naming

Conventions, Code re-use, Implicit and Explicit Conversion/Data Types etc).

c. Error Handling – Ensure that the program is able to accommodate Error/Exception

handling. Input should be validated wherever deemed necessary and should an error

occur the program should be able to deal with the error in an acceptable manner without

abruptly terminating (crashing).

d. Ensure that the program is Tested and Debugged properly. Marks will be deducted if the

program does not compile. Apply a test strategy to ensure that the program is able to

perform without compromising integrity of the data, functionality of software. Compile a

list of some test data that was used to test the program.

3. Evaluate the program

a. Evaluate your program. Did you apply good programming practices? Are the

controls/components named correctly, is the code commented and easy to read. Did you

use naming conventions? Are the variables and data types used appropriate? Are the

functions and sub-procedures, which are used appropriate?

b. Compile an executable program for evaluation.

(10 days- 67 marks)


Copyright reserved

Task 6:Documentation & General Evaluation

The overall objective of this stage is to compile all the documentation that was generated throughout the development together with creating a user manual for the program/system.

Use the following guideline to plan the documentation required for this stage.

1. The following guidelines can be used to create a user manual for the

program/system.

a) Title sheet and table of contents.

b) Background to the project. Here the history of the development of the project should be

described.

c) How to use the software – detail depends on the complexity of the software and the

user-friendliness of the GUI. Screen Dumps can be included to show the user what

each form(s) can perform.

d) Scope and limitations of the program/system.

e) PC Requirements

f) Hardware requirements for the program. (Eg: hard drive space, memory space, CPU,

special input devices, etc.)

g) Software required in addition to the program itself. (Eg: Operating system version, etc.)

h) Installation instructions.

i) Detailed instructions for the user and a walk-through of the program.

j) Input required. The exact format of the input should be specified, particularly if

formatted input is being used, for example a date.

k) Output/reports produced.

l) Troubleshooting for potential problems

m) References and acknowledgements, especially where third party software or

algorithms/functions and coding is used.

2. Your lecturer will then conduct a general evaluation based on:

a. Time-management. Did you meet all deadlines as per the project plan?

b. Correlation of tasks. Do the tasks flow into each other?

c. Utility value. Does the proposed solution have a real value in terms of implementation

in a real world environment?

d. Overall Project Deliverables. Did the final end product (program/system) meet the

requirements as set out in Task 2?

(2 days- 36 marks)

ISAT L3 - IT Computer Science 2011

Documents

Transcript of ISAT L3 - IT Computer Science 2011