Send More Info
Apply Now
Classroom Login
Call Now
Call Now 855-300-1469

CIS 3512 Systems Analysis and Design

Course Description

Provides the opportunity to design, implement, and document the system development cycle. Course includes analysis of current systems, logical and physical systems design, program development, testing, implementation, maintenance, and documentation.

Course Objectives

Upon completion of this course, students should be able to

  • Analysis of current systems
  • Logical systems design
  • Physical systems design
  • Program development
  • Testing, implementation, maintenance, and documentation

Week 1

Lecture: Introduction to Systems Analysis and Design
Lecture: Preliminary Investigation


  • Discuss the impact of information technology on business strategy and success
  • Define an information system and describe its components
  • Explain how profiles and models can represent business functions and operations
  • Explain how the Internet has affected business strategies and relationships
  • Identify various types of business information systems and explain who uses them
  • Explain modeling, prototyping, and CASE tools
  • Distinguish between structured analysis and object-oriented analysis
  • Compare the systems development life cycle waterfall model to adaptive models
  • Discuss the role of the information technology department and the systems analysts who work there
  • Explain the concept of a business case and how a business case affects an IT project
  • Describe the strategic planning process and why it is important to the IT team
  • Explain the purpose of a mission statement
  • Describe the SDLC and explain how it serves as a framework for systems development and business modeling
  • Describe risks and risk management features
  • List the reasons for information systems projects and the factors that affect such projects
  • Explain the initial review of systems requests and the role of the systems review committee
  • Define operational feasibility, technical feasibility, economic feasibility, and schedule feasibility
  • Describe the steps in a preliminary investigation and the end product of an investigation

Week 2

Lecture: Systems Analysis Toolkit: Communication Tools
Lecture: Systems Analysis Toolkit: Case Tools


  • List the guidelines for successful communications
  • Explain the importance of effective letters, memos, and email communications
  • Explain how to measure the readability of written material
  • Describe the organization of written reports that are required during the SDLC and explain each report section
  • List the guidelines for effective oral communication
  • Organize and plan an oral presentation
  • Use speaking techniques to achieve your objectives
  • Define economic analysis
  • Classify costs and benefits into various categories including tangible or intangible, direct or indirect, fixed or variable, and developmental or operational
  • Explain chargeback methods and how they are used
  • Use payback analysis to calculate the length of time it takes for a project to pay for itself
  • Use return on investment analysis to measure a project’s profitability
  • Use present value analysis to determine the value of a future project measured in dollars

Week 3

Lecture: Requirements Modeling
Lecture: Data and Process Modeling


  • product of the systems analysis phase
  • Explain joint application development (JAD) and rapid application development (RAD)
  • Understand how systems analysts use a functional decomposition diagram (FDD)
  • Describe the Unified Modeling Language (UML) and explain use case diagrams and sequence diagrams
  • List and describe system requirements including outputs, inputs, processes, performance, and controls
  • Explain the concept of scalability
  • Use fact-finding techniques including interviews, documentation review, observation, questionnaires, sampling, and research
  • Define total cost of ownership (TCO)
  • Conduct a successful interview
  • Develop effective documentation methods to use during systems development
  • Describe data and process modeling concepts and tools including data flow diagrams, a data dictionary, and process descriptions
  • Describe the symbols used in data flow diagrams and explain the rules for their use
  • Draw data flow diagrams in a sequence, from general to specific
  • Explain how to level and balance a set of data flow diagrams
  • Describe how a data dictionary is used and what it contains
  • Use process description tools including structured English, decision tables, and decision trees
  • Describe the relationship between the logical and physical models
  • Describe the relationship between logical and physical models

Week 4

Lecture: Object Modeling
Lecture: Development Strategies


  • Explain how object-oriented analysis can be used to describe an information system
  • Define object modeling terms and concepts including objects, attributes, methods, messages, classes, and instances
  • Explain relationships among objects and the concept of inheritance
  • Draw an object relationship diagram
  • Describe Unified Modeling Language (UML) tools and techniques including use cases, use case diagrams, class diagrams, sequence diagrams, state transition diagrams, and activity diagrams
  • Explain the advantages of using CASE tools in developing the object model
  • Explain how to organize an object model
  • Describe the concept of software as a service
  • Explain software acquisition alternatives including traditional and web-based software development strategies
  • Describe software outsourcing options including offshore outsourcing and the role of service providers
  • Explain advantages and disadvantages of in-house software development
  • Explain cost-benefit analysis and financial analysis tools
  • Explain the differences between a request for proposal (RFP) and a request for quotation (RFQ)
  • Describe the systems requirements document
  • Explain the transition from systems analysis to systems design, and the importance of prototyping
  • Discuss guidelines for systems design
  • Describe future software development trends

Week 5

Lecture: Output and User Interface Design
Lecture: Data Design


  • Discuss output design issues and various types of output
  • Design various types of reports and suggest output controls and security
  • Explain the concept of user interface design and human/computer interaction including the basic principles of user-centered design
  • List specific guidelines for user interface design
  • Describe user interface techniques including screen elements and controls
  • Explain input design concepts, techniques, and methods
  • Describe guidelines for data entry screen design
  • Use validation checks for reducing input errors
  • Design effective source documents and input controls
  • Explain data design concepts and structures
  • Describe file processing systems
  • Explain database systems and define the components of a database management system (DBMS)
  • Describe web-based data design
  • Explain data design terminology including entities, fields, common fields, records, files, tables, and key fields
  • Describe data relationships, draw an entity-relationship diagram, define cardinality, and use cardinality notation
  • Explain the concept of normalization
  • Explain the importance of codes and describe various coding schemes
  • Describe relational and object-oriented database models
  • Explain data warehousing and data mining
  • Differentiate between logical and physical storage and records
  • Explain data control measures

Week 6

Lecture: Systems Architecture
Lecture: Systems Implementation


  • Provide a checklist of issues to consider when selecting a system architecture
  • Describe servers, server-based processing, clients, and client-based processing
  • Explain client/server architecture including tiers, cost-benefit issues, and performance
  • Compare in-house e-commerce development to packaged solutions
  • Explain the difference between online and batch processing
  • Define network topology including hierarchical, star, bus, and ring models
  • Describe wireless network standards, advantages, and disadvantages
  • Explain network protocols and licensing issues
  • Explain performance measurement, fault management, backup, and disaster recovery
  • Describe the systems design specification
  • Explain the importance of software quality assurance and software engineering
  • Describe the application development process
  • Draw a structure chart showing top-down design, modular design, cohesion, and coupling
  • Explain the coding process
  • Explain unit, integration, and system testing
  • Differentiate between program, system, operations, and user documentation
  • List the main steps in system installation and evaluation
  • Develop an overall training plan with specific objectives for each group of participants, compare in-house and outside training providers, and describe effective training techniques
  • Describe data conversion and changeover methods
  • Explain the post-implementation evaluation and the final report to management

Week 7

Lecture: Systems Operation, Support, and Security
Lecture: System's Analysis Toolkit: Project Management Tools


  • Explain how the systems operation, support, and security phase relates to the overall systems development phase
  • Describe user support activities including user training and help desks
  • Discuss the four main types of system maintenance
  • Explain various techniques for managing systems operations and support
  • Describe techniques for measuring, managing, and planning system performance
  • Assess system security at five levels: physical security, network security, application security, file security, and user security
  • Describe backup and disaster recovery policies and methods
  • List factors indicating that a system has reached the end of its useful life
  • Assess future challenges for IT professionals as technology reshapes the workplace
  • Describe project management tools and how they are used
  • Describe the steps used in project planning, scheduling, monitoring and controlling, and reporting
  • Explain techniques for estimating task completion times and costs
  • Describe various scheduling tools including Gantt charts and PERT/CPM charts
  • Calculate completion times, start dates, and end dates for a project
  • Identify examples of project management software and explain how these programs can assist you in project planning, estimating, scheduling, monitoring, and reporting
  • Explain the steps involved in software change control
  • Explain the reasons why projects sometimes fail

Week 8

Lecture: Systems Analysis Toolkit: CASE Tools
Lecture: Systems Analysis Toolkit: Internet Resource Tools


  • Explain CASE tools and the concept of a CASE environment
  • Trace the history of CASE tools and their role in a fourth-generation environment
  • Define CASE terms and concepts including a repository, modeling tools, documentation tools, engineering tools, and construction tools
  • Explain an integrated development environment
  • Provide examples of CASE tools features
  • Describe future trends for CASE tools including new developments and the emerging role of object-oriented analysis and design
  • Describe the characteristics of the Internet and the World Wide Web
  • Plan an Internet search strategy, evaluate your information requirements, choose a proper tool, assess the quality of the results, and download virus-free results
  • Explain how to use search engines, subject directories, and the invisible web to locate the information you require
  • Demonstrate advanced search techniques including Boolean logic and Venn diagrams
  • Describe other Internet communication resource tools including newsgroups, blogs, podcasts, newsletters, mailing lists, web-based discussion groups, chat rooms, and instant messaging
  • Provide examples of IT community resources and their value to a systems analyst
  • Explain the benefits and disadvantages of online learning opportunities
  • Use speaking techniques to achieve your objectives

The course description, objectives and learning outcomes are subject to change without notice based on enhancements made to the course.