Skip to main content
nounstudy
CIT212

System Analysis and Design

  • Sciences
  • 200 level
  • 3 credit units
  • 257 pages
  • 12 units

This course introduces the concepts, tools, and techniques for analyzing and designing computer-based information systems. It covers the system development life cycle (SDLC), emphasizing the roles of stakeholders and the system analyst. Topics include feasibility studies, system requirement specifications, structured system design, input/output design, file and database design, system development, quality assurance, and system implementation. The course aims to equip students with the skills to study, analyze, and design workable systems.

About this course

Difficulty
Intermediate
Study hours
120 hours
Maths
Basic
Content
Theoretical, practical, case study
Practical work
Yes
Before you start
  • Basic Computer Hardware and Software Concepts
  • Programming Languages
How it is assessed
  • Assignments
  • Tutor Marked Assessments (TMAs)
  • Final Examination

One paragraph, so you can see how it reads

CIT212 · UNIT 1 SYSTEM ANALYSIS

The Presentation Schedule included in your course materials gives you the important dates for the completion of tutor marked assignments and attending tutorials. Remember, you are required to submit all your assignments by the due date. You should guard against lagging behind in your work.

What you should be able to do

  1. Describe the basic elements in system analysis and the role of a system analyst.
  2. Explain different reasons for developing new systems projects.
  3. Describe the various system analysis and design tools.
  4. Select a project out of a number of project requests.
  5. Enumerate the role of quality assurance in various stages of a system development life cycle.
  6. Explain the characteristics of good documentation and its various types and the tools needed for documentation.
  7. Explain the various types and stages of system implementation and conversion as well as system maintenance.

What it prepares you for

Careers
  • System Analyst
  • Database Designer
  • IT Consultant
  • Software Developer
  • Project Manager
Where it is applied
  • Banking
  • Healthcare
  • Retail
  • Government
  • Education
Tools
  • Data Flow Diagramming Tools
  • Database Management Systems (DBMS)
  • CASE Tools

Where it gets hard

The units students slow down on, and what makes each one heavy.

  • Module 1:

    Unit 4: System Requirement Specifications and Analysis

    Requires understanding of complex diagramming techniques and ability to translate user needs into technical specifications.

  • Module 2:

    Unit 4: File and Database Design

    Involves understanding of database normalization concepts and the ability to design efficient and scalable data models.

A suggested way through it

Suggested

13 weeks, about 38 hours in total. Yours will differ.

  1. Week 1Module 1:
    • Unit 1: Overview of System Analysis and Design · 2 hours

      Read the introduction to System Analysis and Design.. Define systems, systems study, systems analysis, and systems approach.. Identify the characteristics and types of systems.. Explain the role of a system analyst..

  2. Week 2Module 1:
    • Unit 2: Project Selection · 2 hours

      Understand the reasons for initiating system projects.. Identify the sources of project requests.. Discuss the management of project review and selection.. Explain the preliminary investigation process..

  3. Week 3Module 1:
    • Unit 3: Feasibility Study · 2 hours

      Define feasibility and feasibility study.. List and illustrate different types of feasibility.. Discuss the purposes of feasibility study.. Describe different steps in feasibility analysis.. Explain in detail cost/benefit analysis..

  4. Week 4Module 1:
    • Unit 4: System Requirement Specifications and Analysis · 4 hours

      Define Data Flow Diagrams (DFD).. Define Data Dictionary, its standard symbols and rules.. Explain HIPO, its two types of diagrams.. Draw decision tables and display decision trees.. Illustrate Warnier-Orr diagrams and Nassi-Shneidermann charts..

  5. Week 5Module 2:
    • Unit 1: Structured System Design · 2 hours

      Define system design considerations.. List out various design methodologies.. Know the brief outlines on structured design.. Explain modularization, computer system design process and system specifications.. Understand the importance of prototype design..

  6. Week 6Module 2:
    • Unit 2: Input Design and Control · 2 hours

      Understand the importance of input design for producing the correct report.. Determine criteria for selecting the most appropriate input method and medium for an application.. Develop a system for validating input to a computer application.. Prepare layout for terminal screens..

  7. Week 7Module 2:
    • Unit 3: Output Design · 2 hours

      Identify the devices used to output information from a computer.. Enumerate the design consideration.. Design a form and explain the design of screen output.. List role of graphics in output.. Enumerate record structure and report layout consideration..

  8. Week 8Module 2:
    • Unit 4: File and Database Design · 4 hours

      Explain file concepts and its different type.. Describe various methods of selecting data storage medium.. Explain file organization and file design.. Describe database design and coding system..

  9. Week 9Module 3:
    • Unit 1: System Development · 2 hours

      Understand different tasks of system development.. Know the importance of prototype.. Find out various factors to be considered prior to system selection.. Understand the term benchmark.. Define the various parameter responsible in considering the selection of a language..

  10. Week 10Module 3:
    • Unit 2: System Control and Quantity Assurance · 4 hours

      Highlight various issues involved in quality assurance, testing and system control.. Point out the role of quality assurance in various stages of a Software Development Life Cycle.. Illustrate the significance of various levels of tests and their different functions.. Explain the role played by system control in a computer system..

  11. Week 11Module 3:
    • Unit 3: Documentation · 2 hours

      Describe the characteristics of good documentation and its various types.. Identify the tool needed for documentation.. Explain the guideline/format to be followed for preparing good documentation package..

  12. Week 12Module 3:
    • Unit 4: System Implementation · 4 hours

      Appreciate the importance of training of personnel involved with system.. Get familiar with various training methods of conversion and operation plans.. Explain post implementation review.. Highlight various issues involved in system maintenance and designing of computer contract.. Get proper understanding about various factors for hardware/software acquisition and vendor's selection.. Understand the importance of service bureau and financing use of computer..

  13. Week 13All Modules
    • Final Revision · 6 hours

      Review all modules and units.. Work on all assignments and TMAs.. Prepare for final examinations..

Preparing for the exam

What to do
  • Create concept maps linking SDLC phases (Units 1-4 Module 1) to understand dependencies.
  • Practice drawing Data Flow Diagrams (DFDs) for sample business scenarios (Unit 4 Module 1).
  • Compare and contrast different database models (hierarchical, network, relational) in Unit 4 Module 2.
  • Review the different types of feasibility studies and their importance in project selection (Unit 3 Module 1).
  • Focus on understanding the trade-offs between different system conversion methods (parallel, direct, pilot, phased) in Unit 4 Module 3).
  • Practice creating decision tables and decision trees for different scenarios.
  • Study the different types of codes used in system design and their applications.

Questions students ask about this course

What is CIT212 about?

This course introduces the concepts, tools, and techniques for analyzing and designing computer-based information systems. It covers the system development life cycle (SDLC), emphasizing the roles of stakeholders and the system analyst. Topics include feasibility studies, system requirement specifications, structured system design, input/output design, file and database design, system development, quality assurance, and system implementation. The course aims to equip students with the skills to study, analyze, and design workable systems.

How many units does CIT212 have?

CIT212, System Analysis and Design, has 12 units across 3 modules, over 257 pages of course material. You can read it one unit at a time.

How many credit units is CIT212?

CIT212 carries 3 credit units, at 200 level in Sciences.

Is CIT212 hard?

CIT212 is rated intermediate level, with basic mathematical content. It is mostly theoretical, practical and case study work, and it has a practical component.

How long does CIT212 take to study?

About 120 hours of study, spread across its 12 units.

How is CIT212 assessed?

CIT212 is assessed by Assignments, Tutor Marked Assessments (TMAs) and Final Examination.

What do I need before starting CIT212?

Basic Computer Hardware and Software Concepts Programming Languages

What can I do with CIT212?

System Analyst, Database Designer, IT Consultant, Software Developer and Project Manager.

More courses in Sciences

EHS207

General Biochemistry For Environmental Health

3 credit units

Open EHS207
BIO206

Statistics For Agriculture and Biological Sceinces

2 credit units

Open BIO206
CIT204

Computer Appreciation And Application To Agriculture

2 credit units

Open CIT204