• No results found

CSC 306 System Analysis and design COURSE PARTICULARS COURSE INSTRUCTORS COURSE DESCRIPTION

N/A
N/A
Protected

Academic year: 2021

Share "CSC 306 System Analysis and design COURSE PARTICULARS COURSE INSTRUCTORS COURSE DESCRIPTION"

Copied!
5
0
0

Loading.... (view fulltext now)

Full text

(1)

1

CSC 306 – System Analysis and design

COURSE PARTICULARS

Course Code: CSC 306

Course Title: System analysis and Design No. of Units: 3

Course Duration: Two hours of theory per week for 15 weeks. Status: Compulsory

Course Email Address: Course Webpage: Prerequisite: NIL

COURSE INSTRUCTORS

Dr B.M Kuboye

Room 8, Adamu Abdullahi Academic Office complex Building, Dept. of Computer science,

Federal University of Technology, Akure, Nigeria.

Phone: +2348033865251 Email: [email protected] and

Mrs. O. D. Alowolodu

Room 6 Digital Resource center Building, Dept. of computer Science,

Federal University of Technology, Akure, Nigeria.

Phone: +2347035131650

Email: [email protected]

COURSE DESCRIPTION

This course is designed primarily for students in computer science. However, it also meets the need of students in other fields, as a course that provides adequate knowledge in the analysis, design, and development of an information system. Importance is placed on system characteristics, project management, prototyping, and systems development life cycle phases. At the end of this course, students should be able to analyze problems and design appropriately the solution required using a combination of tools and techniques.

(2)

2

COURSE OBJECTIVES

The objectives of this course are to let students:

 have understanding of the five phases of the system development life cycle;

 describe how systems analysts interact with stakeholders and information system;

 know how to analyze and design systems;

 know how to evaluate systems development alternatives;

 work together as a team on assigned projects.

COURSE LEARNING OUTCOMES / COMPETENCIES

Upon successful completion of this course, the student will be able to:

(Knowledge based)

 explain how the five phases of the system development relate together  analyse the problem of a system and design a new system;

 understand the use of computer system development tools;

(Skills)

 use the system development tools to:

o evaluate an existing system;

o analyse new system;

o design new system;

 determine methods for evaluating the effectiveness and efficiency of a system;  develop a good documentation for the developed system.

GRADING SYSTEM FOR THE COURSE

This course will be graded as follows:

Class Attendance 5%

Assignments 15%

Test(s) 20%

Final Examination 60%

(3)

3

GENERAL INSTRUCTIONS

Attendance: It is expected that every student will be in class for lectures and also participate in all practical exercises. Attendance records will be kept and used to determine each person’s qualification to sit for the final examination. In case of illness or other unavoidable cause of absence, the student must communicate as soon as possible with any of the instructors, indicating the reason for the absence.

Academic Integrity: Violations of academic integrity, including dishonesty in assignments, examinations, or other academic performances are prohibited. You are not allowed to make copies of another person’s work and submit it as your own; that is plagiarism. All cases of academic dishonesty will be reported to the University Management for appropriate sanctions in accordance with the guidelines for handling students’ misconduct as spelt out in the Students’ Handbook.

Assignments and Group Work: Students are expected to submit assignments as scheduled. Failure to submit an assignment as at when due will earn you zero for that assignment. Only under extenuating circumstances, for which a student has notified any of the instructors in advance, will late submission of assignments be permitted.

Code of Conduct in Lecture Rooms and Laboratories: Students should turn off their cell phones during lectures. Students are prohibited from engaging in other activities (such as texting, watching videos, etc.) during lectures. Food and drinks are not permitted in the laboratories.

READING LIST

1Jeffrey L. Whitten, Lonnie D. Bentley, Kevin C. Dittman (2001). Systems Analysis and Design

Methods 5th Edition. McGraw-Hill.

1Bolanle Ojokho. Lecture notes on Introduction to Systems Analysis and Design. 1 Unknown Author. Introduction to Systems and Systems Development Life cycle.

Legend

.

(4)

4

COURSE OUTLINE

Week

Topic

Remarks

WEEK 1 Introduction

A. Information system components B. Types on information systems C. System development life cycles D. The systems analyst

At the end of this class, the students would have gotten the general overview of system development.

WEEK 2 Systems planning

A. Systems requests B. Objectives

C. Preliminary investigation

Students would have acquired the knowledge needed to plan a system

WEEK 3 Determining requirements

A. Interviews B. Other fact-finding techniques

C. Recording facts D. JAD and RAD

E. Object-oriented systems development

The required models and tools for determining requirements must have been learnt.

WEEK 4 Analyzing requirements

A. Data flow diagrams B. Data dictionary C. Process description

Analysis requirement tools must have been exposed to the students.

WEEK 5 Evaluating alternatives

A. Software alternatives B. Evaluating software packages

C. Hardware alternatives D. CASE tools

System modeling tools must have been made known to the students.

WEEK 6 Continuous Assessment

WEEK 7 Systems design

A. Output design B. Input design

C. File and database design D. System architecture

The students should have been able to design a System.

WEEK 8 Systems implementation

A. Quality assurance B. Application development C. Documentation D. Management approval E. Installation F. Evaluation G. System operation

The group projects will be given out

WEEK 9 Describing process

specifications and structured decisions; The system

(5)

5 proposal.

WEEK 10 Designing the file or database

Designing the user interface

Database design would have exposed to the students.

WEEK 11 Designing data

WEEK 12 Documenting the design

phase

Group projects sub mission

WEEK 13 Software engineering and

implementation

Quality assurance through software engineering;

Implementing the information system

WEEK 14 Defense of Class Project.

References

Related documents

• You can create a Requisition via Catalog, Template, Favorites, Punch Out, or Special Request. Out, or

Dengan melakukan pembobotan menggunakan AHP dan perhitungan scoring system menggunakan OMAX, dapat diketahui 4 indikator kinerja supply chain yang perlu segera mendapatkan

• During the rest of this fall semester and winter break, the math faculty will work to switch College Algebra, Trigonometry, and Statistics over to OpenStax and WebAssign..

Importantly for this thesis, he underscored a tension (which, however, he did not investigate) between the international understanding of self-determination, embedded in

Course Description This  course  provides  a  comprehensive  overview  of  the  user experience  design  process,  and  is  intended  to  familiarize students  with

This equation shows that the greater the turning circle of the rover (i.e. the larger the rover's chassis is), the lower its mean free path.. This demonstrates one of

Fur- thermore, for one event, #5, the combined EUV and X-ray emission could be fit using only a multi-thermal plasma, sug- gesting a very weak or non-existent non-thermal component

AMBSB Bearings Sliding Surface AOPFC Pumps / Fundamentals of Centrifugal Types AMCAC Compressors Reciprocating AORBC Refrigeration Systems/ Basic Concepts AMCCC Compressors