Information Systems Analysis

General Course Information

Course Lecturer Name(s):  Dr. Thompson Cummings

Course Director Name: Dr. Thompson Cummings

Course Lecturer(s) Contact Information:  473-444-4175Ext.3178;

Course Director Contact Information:             

Course Lecturer(s) Office Hours:  Mondays: 9.30–11.45 AM; 1.00 – 4.00 PM. Tuesdays and   Thursdays:1.00 – 3.30 PM  

 Course Director Office Hours: 

Course Lecturer(s) Office Location:  Building D (Leeward Hall) 1st. Floor Course Director Office Location:         

Course Support: Mary Celestine, Ext. 37266

Course Management tool: To learn to use Sakai, the Course management tool, access the link

Course Curriculum Information

Course Description: 

This course provides students with the tools and techniques for analyzing information systems requirements. The course covers three units – systems analysis fundamentals, information requirements analysis, and the analysis process. The systems analysis fundamentals unit stresses the basics that students need to know about what an analyst does; how information systems fit into organizations; how to determine whether a systems project is worthy of commitment; and how to manage a systems project. The information requirements analysis unit emphasizes the use of systematic and structured methodologies for conducting such requirements analysis.  The analysis process builds on the other previous two units and move students into analysis of data flow as well as structured and semi-structured decisions.  It includes details on how to use structured techniques to draw data flow diagrams.

Course Objectives: 

1. The course is designed to provide students with the tools and techniques for analyzing information systems requirements and writing systems proposal.

Student Learning Outcomes:

Once students have mastered the course material, they will be able to:

  1. Describe and discuss the different types of information systems and at what level within an organization they are appropriately implemented.
  2. Realize what are the many roles of a systems analyst are.
  3. Know and understand the various development methodologies and how they help the systems analyst.
  4. Describe and discuss the main features to be examined in determining whether a system project is worthy of commitment.
  5. Describe how to manage a system project using Gantt Charts and PERT Diagrams.
  6. Describe and discuss the various analysis techniques that can be employed to determine user’s needs.
  7. Use structured techniques to construct data flow diagrams.
  8. Diagram structured decisions using Structured English, Decision tables, and Decision trees.
  9. Prepare and write a systems proposal.

Program Outcomes Met By This Course:

CTPO1 Analyse a problem, identify and define the computing requirements appropriate to its solution

SAS Grading Scale: Grades will be assigned as follows:

A  = 89.5% or better

B+ = 84.5 - 89.4%

B  = 79.5 - 84.4%

C+ = 74.5 - 79.4%

C = 69.5 - 74.4%

D = 64.5 - 69.4%

F = 65% or less

Course Materials:

Text: • Prescribed Text(s): Open Textbook on Systems analysis/Software engineering/Software development.

Supplementary Readings/Resources:  Systems Analysis and Design. 9th. Edition. Kendall and Kendall. Prentice Hall.

Course Grading Requirement:

Course Work










Course Requirements:

Course Schedule

This course covers the following topics:

Unit I Systems Analysis Fundamentals

  • Information systems – Types of information systems
  • The Systems Analyst - Systems analysis and design concepts, Role of the Systems Analyst  
  • Organizational style and its impact on information systems – Organizational fundamentals,  Levels of management, etc.
  • Development methodologies - Systems development life cycle, Case tools
  • Entity-Relationship modeling •      Project Management o      System selection – Problem identification and selection o       The Feasibility study – Types of feasibility o   Activity Planning and Control – Gantt Charts and PERT diagrams o      The Systems Proposal - Preparing, Writing, and Presenting the proposal

Unit II Information Requirements Analysis

  • Analysis Techniques – Interviews, Questionnaire, Observations, etc.
  • Prototyping – Approaches to prototyping, Developing a prototype, Users role in prototyping
  • Rapid Application Development
  • Agile modeling – principles and practices, development process and tools
  • DevOps

Unit III The Analysis Process & System proposal

  • 3.1 Data Flow Diagram – Developing data flow diagrams, logical and physical Data Flow Diagrams, Partitioning Data Flow Diagrams, Creating a physical Data Flow Diagram, Using Data Flow

Diagrams, Modeling Hierarchy

  • 3.2 Data Dictionary – The Data dictionary, the Data repository, Creating the Data dictionary, using the data dictionary.
  • 3.3 Process Specifications – Decision tables, Decision trees, Structured English
  • 3.4 Object-oriented analysis – Concepts, Unified Modeling Language (UML) concepts and diagrams

Tentative Course Schedule



Assignment/ Project

Assignment/ Project due date



 Information systems 




 Organization and Information systems

 The Systems Analyst

#1 Given



 Development methodologies


 CASE Tools


#1 due: end of week 3


 Entity Relationship Diagram





 Project Management  System selection

 Feasibility study

 Activity planning and control

#2 Given



 Activity planning and control (cont)

 Analysis Techniques  Interviews



#2 due: end of week 6


 Analysis Techniques (cont.)


 Document Review

 Analysis Methods  Prototyping





Midterm & Project Given



 System proposal

 Analysis Methods (cont.)


 Agile modeling





 Dataflow diagrams

#3 Given



 Dataflow diagrams (cont.)  Data dictionary


#3 due: end of week 11


 Process specifications  Structured English

 Decision tables

#4 Given



 Process Specifications  Decision tables (cont.)  Decision trees


#4 due: end of week 13


 Object-oriented systems analysis


Project end of Week 14


Course Wrap-up

Course Wrap-up

Course Wrap-up





School of Arts and Sciences Master Syllabi — Info for All Sections

Plagiarism Policy

Academic Integrity

The St. George’s University Student Manual (2019/2020) states as follows:

Plagiarism is regarded as a cardinal offense in academia because it constitutes theft of the work of someone else, which is then purported as the original work of the plagiarist. Plagiarism draws into disrepute the credibility of the Institution, its faculty, and students; therefore, it is not tolerated” (p. 48).

Plagiarism also includes the unintentional copying or false accreditation of work, so double check your assignments BEFORE you hand them in.

Be sure to do good, honest work, credit your sources and reference accordingly and adhere to the University’s Honor Code. Plagiarism and cheating will be dealt with very seriously following the university’s policies on Plagiarism as outlined in the Student Manual.

Your work may be subject to submission to plagiarism detection software, submission to this system means that your work automatically becomes part of that database and can be compared with the work of your classmates.

Attendance Requirement

The St. George’s University Student Manual (2019/2020) states as follows:

Students are expected to attend all classes and or clinical rotations for which they have registered. Although attendance may not be recorded at every academic activity, attendance may be taken randomly. Students’ absence may adversely affect their academic status as specified in the grading policy. If absence from individual classes, examinations, and activities, or from the University itself is anticipated, or occurs spontaneously due to illness or other extenuating circumstances, proper notification procedures must be followed. A particular course may define additional policies regarding specific attendance or participation” (p. 9).

Examination Attendance

The St. George’s University Student Manual (2019/2020) states as follows:

All matriculated students are expected to attend all assigned academic activities for each course currently registered. Medical excuses will be based on self-reporting by students. Students who feel they are too sick to take an examination or other required activity on a specific day must submit the online SAS medical excuse, which is available on Carenage. Students are only allowed two such excuses a year. Upon consultation with the Director of University Health Service, the third excuse will result in a mandatory medical leave of absence. The policies regarding make-up examinations are at the option of the Course Director” (p.46).

For additional specific examination policies and procedures, refer to the St. George’s University Student Manual (2019/2020), pages 31 through 37.

Student Accessibility and Accommodation Services Policy

The St. George’s University Student Manual (2019/2020) states as follows:

A student with a disability or disabling condition that affects one or more major life activities, who would like to request an accommodation, must submit a completed application form and supporting documentation to the Student Accessibility and Accommodation Services (SAAS) located in the Dean of Students Office. It is highly recommended that students applying for accommodations do so at least one month before classes begin to allow for a more efficient and timely consideration of the request. If a fully completed application is not submitted in a timely fashion, an eligibility determination may not be made, and accommodations, where applicable, may not be granted prior to the commencement of classes and/or examinations” (p. 8).


It is the responsibility of the student to read and understand the policies, laws, rules and procedures that while they could affect your grade for a course, have not been specifically outlined in the course syllabus. These are contained in the St. George’s University Student Manual.