Graduate Programs in Business -- Master of Science in Management & Systems
Systems Development and Analysis


Course Number - MASY1-GC3210
Tuesday and Thursday - 6:00-9:00pm

Announcement(s):

Professor: Sam Sultan [sam.sultan@nyu.edu]
Class website: [samsultan.com/sad] (or) [oit.scps.nyu.edu/~sultans/sad]
Office hours: By Appointment

+ syllabus
+ books
+ grades
+ final project
+ policies & procedures
+ student listing
+ examples & demos
+ other classes
+ student feedback
+ student evaluation & comments

Session - 1   2   3   4   5   6   7   8   9   10   11   12  

ITS - SDLC - Software Development Process & Methods - Systems Analysis & Design - Object Oriented Analysis & Design

COURSE DESCRIPTION:

This course investigates the concepts and techniques used in the analysis and design of business information systems. Topics include assessing business requirements; interviewing /testing techniques; determining the feasibility of software products; and estimating system costs. Students analyze data flow diagrams, data models, file design, interface design, and software design. Upon completion of this course, students will understand the key system development lifecycle approaches to system analysis and design, and how to select, plan, analyze, design, implement, and maintain modern application systems. Through collaborative learning approaches, lectures, peer-learning activities, and real-world projects, students receive a dynamic experience in developing business systems analysis documents, as well as in analyzing and designing systems.


COURSE LEARNING GOALS:

1. Course Objectives:

The course covers fundamentals of systems analysis and design. Topics include requirement gathering, system analysis, design and modeling of software specifications. As part of the course, students will learn skills, methodologies, techniques, tools and perspectives essential for system's analysts and designers to successfully develop information systems.

The course explains various methodologies for systems analysis and design, including the traditional SDLC method, object oriented approaches, and various agile methodologies.

Upon completion of this course, students are expected to be able to use a structured SDLC (System Development Lice Cycle) methodology to analyze IT system structures, model information processes, and design/redesign IT systems.

       The focus of the course will be on the following topics:

2. Student Learning Outcomes:


COURSE REQUIREMENTS AND POLICIES:

See [Requirements and Policies]


BOOKS:

Required Reading & Materials -

Recommended Reading & Materials -

GRADES

Grades are FINAL.

Please do not negotiate for a better grade. If you are expecting to receive a grade of an "A" at the end of the semester, then I expect you to attend all sessions, to participate and contribute in class, and to keep up with the class reading material. If you see yourself falling behind do not hesitate to ask for help. This will ensure that you stay current with the class, and will ensure that you get a good grade on your work.

NYU/SPS Grading Scale -

GradeVerbal InterpretationGardation, Conversion and Scale
A Exceptional work
Superior effort
A = 93-100 = 4.0
A- = 90-92 = 3.7
(there is no A+)
B Very good work B+ = 87-89 = 3.3
B = 83-86 = 3.0
B- = 80-82 = 2.7
C Satisfactory work C+ = 77-79 = 2.3
C = 73-76 = 2.0
C- = 70-72 = 1.7
(mininum passing grade)
F Fail. Unsatisfactory work F = below 70 = 0.0
IP Incomplete -
Failure to complete assigned work
(see note below)
IF Incomplete Fail -
Failure to complete assigned work
(see note below)

Notes for IP and IF -

Grade IP - Work to date was passing. Incomplete Pass (IP) may be granted only in extraordinary extenuating circumstances. It is not given automatically but only when it is deemed to have met the criteria and when a contract is signed by both the student and faculty prior to the end of the course. Pre-approval by the Academic Department is required before an Incomplete Grade can be awarded. Students must have completed at least 50% of the course to be considered for an IP. If the terms of the IP are not met within the time frame stated on the contract, the grade will convert to an F and cannot be changed or further appealed. Students will have to retake the course.

NOTE: A student who receives an IP grade may not simply retake a test or exam already taken. The student must do additional new work to remove the IP as outlined in the contract. There is a grade point deduction from the overall grade for late submission of work.

Grade IF - Work to date was failing. Students must have completed at least 50% of the course to receive an Incomplete. An IF that is not removed by the established time in the Contract becomes an F and cannot be changed or further appealed. Students will have to retake the course.

Please Note: The Office of the University Registrar maintains individual records of students enrolled in NYU and is the only department authorized to record an official grade. Final grades are reported on NYU-Albert.
For more information: http://www.scps.nyu.edu/academics/academic-policies-and-procedures/graduate-academic-policies-and-procedures.html


COURSE OUTLINE:

DATE SESSION TOPIC[s] COVERED
 
[Week 1] 1
  • Introduction to System Analysis and Design
  • The Impact of Information Technology
  • Information System Components
  • Understanding the Business
  • Impact of the Internet
  • Type of Information Systems
  • Information System Users and Their Needs
  • Systems Development Cycle
  • Overview of Systems Development Methods
  • the 4 steps of the SDLC methodology
  • The Role of a Systems Analyst
  • Reading: Chapter 1
     
    [Week 1] 2
  • Analyzing the Business Case
  • Project Planning
  • SWOT (Strength, Weakness, Opportunity, Threat) analysis
  • Factors affecting system projects
  • Identifying and Selecting Projects
  • The System Service Request
  • Project Initiation and Planning
  • Feasibility Studies
  • Cost-Benefit, NPV, ROI, Break-Even Analysis
  • Developing a Baseline Project Plan
  • A Project Scope Statement
  • A Statement Of Work document
  • Presentation to Management
  • Reading: Chapter 2, Toolkit Part C
     
    [Week 2] 3
  • Managing Systems Projects
  • The role of a Project Manager
  • Project Planning and project scope
  • Dividing the project into manageable tasks
  • Estimating task effort
  • Creating a WBS (Work Breakdown Structure)
  • Project Scheduling
  • Gantt charts, PERT/CPM charts
  • Risk management
  • Project monitoring and controlling
  • Project reporting
  • Software change control
  • Key to project success
  • Reading: Chapter 3
     
    [Week 2] 4
  • Requirement Gathering and Modeling
  • What is a requirement?
  • Characteristics for successful requirement gathering
  • Deliverables and artifacts
  • Collecting Requirements
  • The interview process
  • Questionnaires and surveys
  • Direct observations
  • Document review
  • JAD, RAD and Agile
  • Prototyping
  • Requirement Modeling
  • Type of system requirements
  • Reading: Chapter 4
     
    [Week 3] 5
  • Data and Process Modeling
  • Modeling Tools
  • Data Flow Diagrams
  • Creating a Set of Data Flow Diagrams
  • Data Dictionary
  • Process Description Tools
  • Logical Versus Physical Models
  • Reading: Chapter 5
     
    [Week 3] 6
  • Object Modeling
  • Overview of Object-Oriented Analysis and Modeling
  • Object-Oriented Concepts and Terminologies
  • Relationships among Objects and Classes
  • Object Modeling with the Unified Modeling Language
  • Use Cases, Use Case Diagrams, Use Case Narratives
  • Class Diagrams and Object Models
  • Sequence Diagrams
  • Reading: Chapter 6
     
    [Week 4] 7
  • Development Strategies Overview
  • The Impact of the Internet
  • Outsourcing/In-sourcing
  • In-House Software Development Options
  • Role of the Systems Analyst
  • Analyzing Cost and Benefits
  • The Software Acquisition Process
  • Completion of Systems Analysis Tasks
  • The Transition to Systems Design
  • Systems Design Guidelines
  • Prototyping
  • Reading: Chapter 7
     
    [Week 4] 8
  • Data Design
  • Data Structures and Data Design Concepts
  • Physical Database Design
  • Structured Query Language (SQL)
  • Why Relational?
  • Elements of a Relational Database
  • Tables, Rows, Columns, Relationships, indexes, views
  • DDL - Data Definintion language
  • DML - Data Manipulation language
  • Joining Tables
  • Designing Fields and Composite Attributes
  • Controlling Data Integrity and security
  • Data Normalization, 1NF, 2NF, 3NF
  • Normalization vs. Denormalization
  • Entity Relationships and Cardinality
  • File and Index Organization
  • Reading: Chapter 9
     
    [Week 5] 9
  • Team 1 Presentation

  • System Architecture
  • Planning the Architecture
  • Client/Server Architecture
  • Internet-Based Architecture
  • Processing Methods
  • Network Models
  • Wireless Networks
  • Systems Design Completion
  • Reading: Chapter 10
     
    [Week 5] 10
  • Team 2 Presentation

  • Managing Systems Implementation
  • Software Quality Assurance
  • Overview of Application Development
  • Structured Application Development
  • Object-Oriented Application Development
  • Agile Application Development
  • Coding
  • Testing the System
  • Documentation
  • Management Approval
  • System Installation and Evaluation
  • Operational and Test Environments
  • Training
  • Data Conversion
  • System Changeover
  • Post-Implementation Tasks
  • Reading: Chapter 11
     
    [Week 6] 11
  • Team 3 Presentation

  • System Support, Security and Post Go-Live
  • User Support and Operation
  • Maintenance Tasks
  • Maintenance Management
  • System Performance Management
  • System Security Overview
  • Security Levels
  • Backup and Recovery
  • System Obsolescence
  • Future Challenges and Opportunities
  • Reading: Chapter 12
     
    [Week 6] 12
  • Final Exam



  • NYU SCPS Master's Degree Program web site
    For more information, send e-mail to: sam.sultan@nyu.edu