San Francisco State University

College of Business

BACS Department

ISYS 463: Systems Analysis and Design

 

 

Spring 2004
Section Time Instructor Room
All TTh 1410 - 1525 Dr. Garfolo BUS 115

Text
Whitten, Bentley & Dittman; Systems Analysis and Design Methods --- ISBN 0-07-231539-3. McGraw-Hill.

Course Goals
The goal of ISYS 463 is to impart System Analysis and Design literacy to enhance a graduateís ability to succeed in the complex world of requirements analysis and system design.

Systems Analysis and Design is the art of problem solving. Systems analysis is the study of a current business system and its problems, the determination and definition of business needs and information requirements, and the evaluation of alternative solutions. Systems design is the general and detailed specification of a computer and human solution that meets the requirements determined during systems analysis. During the life of a system, a systems analyst may monitor or evaluate its ability to continue to meet business requirements, and will design and implement modifications and enhancements in response to end-user requests and environmental changes.

In programming courses, program specifications for programming assignments are typically supplied by the instructors.In actual practice, program specifications such as these are provided by a systems analyst, who prepares the specifications in response to business requirements. An appropriate job description for a systems analyst might be:

A systems analyst will analyze the business situation, identify opportunities for improvement, and design an information system to implement them. The system analyst's primary goal is to create systems that enable the organization to perform better and add value to the enterprise.

Systems planning, systems analysis, systems design, and systems implementation are the primary activities of the systems analyst. Systems planning is the identification and prioritization of those technologies and applications that will return the most value to the business. Systems analysis involves defining the scope and planning the project, study of a current business system and its problems, and defining business needs and requirements for the new system. Systems design is evaluating and selecting alternative technical problem solutions, acquiring needed hardware and software, and the general and detailed specification of the solution.Systems implementation is placing the system into production.

The primary theme of the course is the use of systems analysis and design techniques to develop and document effective computer based information systems. You will be exposed to the entire systems analysis and design process. You will learn how to use a wide variety of systems analysis and design tools and techniques. These tools and techniques are used to communicate business needs, document the information systems that are built by systems analysts and programmers, and allow us to create intelligent and friendly computer based solutions for business problems. 

The value of this course will include:

  • A much better understanding of the entire information system development process, from the identification of the business problems and needs to the design of an improved system to the writing of computer programs. Perhaps for the first time, you will truly understand the whole process and where you might fit in.

  • Improved technical communications skills. Your ability to communicate with both technical and non-technical people should be improved through the proper use of the tools. Your writing and speaking skills will also be enhanced as you present your documented ideas to your instructor and classmates.

  • A better understanding of information systems in general. You will learn many capabilities and characteristics of good information systems.This will help you design more effective systems during your career.

 
Learning objectives

At the conclusion of this course, students should be able to:

Knowledge:

  • Define the concepts of methodology, life cycle models and the difference between them
  • Explain the basic system modeling perspectives and the related modeling primitives
  • Describe the main features of structured system modeling perspectives, and the advantages that might expected from them
  • Identify advantages and limitations of the methodologies presented
  • Describe how the various system models (giving different perspectives on the same problem) can be cross-checked and related

Cognitive Skills:

  • Identify how particular assumptions concerning the system being analyzed influence the particular models reached
  • Identify and explore system modeling issues that need to be investigated further
  • Investigate the system-related implications of various modeling decisions and assumptions
  • Combine various systems models to uncover inconsistencies

Subject Specific Skills:

  • Apply data, process and data modeling tools
  • Use a CASE tool to build consistent system models.
  • Manage a systems analysis and design project, with reference to project life cycle issues

Transferable Skills:

  • Work in a group in the area of systems analysis and design
  • Plan group work and integrate work done by different members
  • Document group work and its results
  • Write-up and present systems models

 
Course Methods, Project and Requirements

It is assumed that you will read the assigned chaptersAlthough the material may be summarized, lectures will be used mainly to further demonstrate the tools and techniques, to review any assigned exercises, and to answer specific questions.
 

A semester-long project will integrate many of the topics included in this course.  You will work in teams of three or four students.  The project will be defined and formulated during the first half of the semester.  While the project is being defined, you will be learning some of the fundamentals of systems analysis and design. You will study information systems and learn the capabilities and characteristics of good ones. 
 

The project will be run much as an actual project would be conducted.  As your instructor, I will play the role of project manager and quality assurance manager.  As project manager, I will continually review your progress on the project (although you are ultimately responsible for keeping up).  As quality assurance manager, I will review your documentation for completeness and accuracy. 
 

 
Course Topics

CASE (Computer-Aided Software Engineering)        Object-Oriented A & D
Change Management Plans                                           Project Repository
Conversion Plans                                                            Project Standards
Data Flow Diagrams                                                       Program Specifications
Data Modeling                                                                Program Structure Charts
Entity Relationship Diagrams                                     Project Management
Information Gathering Techniques                            RAD
Feasibility Assessment                                                 Risk Assessment
File / Database Specifications                                    Security Plans
Infrastructure Design                                                   System Requests
Input / Output Specifications                                     System Use Cases
Interface Standards                                                         Systems Development Life Cycle
Joint Application Development (JAD)                       Test Plans
Network Modeling                                                          User Documentation
Process Modeling                                                           User Interface Design

 
Grading
Your grade is determined by the following factors: 
1 Major Exam 20% each
2 Design Documents 10% each
Final 30%
2 Quizes 5% each
Project (Project Prototype) 20%

  • Grade Determimination. Grade calculation is a complex task taking into account many factors. The method for your grade determination can be found here.
  • A course outline can be found here.
  • Attendance and Participation. Regular class attendance, conscientious daily study and preparation, and completion of assignments are essential for satisfying the course objectives. 
  • Exams. Exams can not be made up unless the absences result from extreme circumstance. 
  • Assignments. All Assignments, homework, forms and materials are to be turned in at the beginning of class on the day they are due, unless announced otherwise. There will be a late penalty assessed of 10% per class period that each assignment is late. Assignments that are late for more than 4 class periods will not be accepted. 
  • The instructor reserves the right to retain for pedagogical reasons either the original, or a copy, of any student's test, written assignment, paper, disk, video, or similar work submitted by the student, either individually or as a group project, for this class. Student's names will be deleted from any retained items. 
  • Academic Dishonesty. San Francisco State University requires that students be honest in their academic work. Academic dishonesty is viewed as an ethical issue and violation of the principles expressed in the university's academic regulations. Academic dishonesty, identification and reporting procedures, academic and administrative sanctions and appeal procedures are outlined in detail in the student handbook and are available from the Division of Student Affairs. 
  •  

    Comments and suggestions to Dr. Blaine Garfolo:  bgarfolo@sfsu.edu