Master of Science in Management & Systems
Systems Development and Analysis
Software Development Process & Methods -
Systems Analysis & Design -
Object Oriented Analysis & Design
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:
- The importance of adopting a structured methodology for system development
- Project planning and management for an effective system development process
- Feasibility analysis, cost justification and risk management
- Requirement gathering
- Systems analysis and modeling
- Systems design and modeling
- Systems Implementation and support
2. Student Learning Outcomes:
- Ability to distinguish between various system development methodologies
- Ability to analyze the business case, and to select the most value-added project to implement
- Ability ro evaluate financial feasibilities including NPV, ROI and break-even analysis
- Ability to develop a Baseline Project Plan and a Statement of Work
- Ability to create a Work Breakdown Structure
- Understand and become aware of risk management and minigation
- Perform Requirement Gathering
- Understand logical and physical data modeling
- Understand Object Oriented concepts and terminologies
- Ability to create Use Case narratives and diagrams, as well as Class diagrams
- Understand data modeling and data Normalization rules
- Understand system architecture in terms of single vs. multi-tier with thick/thin client
- Become aware of all alternatives, issues and concerns of system implementation
- Realize and appreciate system operation and ongoing support issues/concerns
COURSE REQUIREMENTS AND POLICIES:
See [Requirements and Policies]
Required Reading & Materials -
Recommended Reading & Materials -
- Systems Analysis and Design - Tenth Edition (© 2013/2014)
- Authors - Harry Rosenblatt - Shelly Cashman Series
- Publisher - Course Technology, Cengage Learning
- Systems Analysis and Design - Ninth Edition (© 2011/2012)
- Authors - Gary Shelly, Harry Rosenblatt - Shelly Cashman Series
- Publisher - Course Technology, Cengage Learning
GRADE ASSIGNMENT AND EVALUATION
Contributing factors for determining your course grade include:
- Class Attendance and Participation - 15%
- Homework/Project Presentation - 35%
- Final Exam - 50%
Details of Assignment and Evaluation.
Grades are FINAL.
- Class Attendance and Participation: To receive full credit for the course, you must attend all classes since much of the learning occurs during class presentation and discussions.
Please contact the instructor if you anticipate missing any part of the class.
Grades will be based on:
- Involvement in class activities
- Participation which demonstrates integration of reading, class work, relevance and application.
- Willingness to learn by accepting feedback, trying new skills and approaches, etc.
- Quality/quantity of providing effective and balanced feedback.
- Homework: Homeworks must be submitted on time within 1 week after date assigned.
Late submission will severly impact your homework grade, or may not be accepted altogether at instructor discretion.
- All homework pages must be stapled together, no exception (paper clips not accepted)
- Print out your homework code and output and bring with you to class
- I will not accept homework via email unless you are not able to attend the class.
- Proper indentation is a must. If not properly indented I may return it without grading it.
- Class Project Presentation: There will be a group/team class presentation.
The presentation will be a culmination of verbal, visual and presentation skills. It will also be the culmination of topics, concepts and competencies learned in this class.
- Final Exam: There will be a final exam. The exam will be an open book, open notes style exam.
The exam will test the student's acquisition of topics, concepts and competencies learned in this class.
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 -
|Grade||Verbal Interpretation||Gardation, Conversion and Scale|
|A ||Exceptional work|
|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:
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 |
|| Chapter 1
Analyzing the Business Case
SWOT (Strength, Weakness, Opportunity, Threat) analysis
Factors affecting system projects
Identifying and Selecting Projects
The System Service Request
Project Initiation and Planning
Cost-Benefit, NPV, ROI, Break-Even Analysis
Developing a Baseline Project Plan
A Project Scope Statement
A Statement Of Work document
Presentation to Management
|| Chapter 2, Toolkit Part C
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)
Gantt charts, PERT/CPM charts
Project monitoring and controlling
Software change control
Key to project success
|| Chapter 3
Requirement Gathering and Modeling
What is a requirement?
Characteristics for successful requirement gathering
Deliverables and artifacts
The interview process
Questionnaires and surveys
JAD, RAD and Agile
Type of system requirements
|| Chapter 4
Data and Process Modeling
Data Flow Diagrams
Creating a Set of Data Flow Diagrams
Process Description Tools
Logical Versus Physical Models
|| Chapter 5
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
|| Chapter 6
Development Strategies Overview
The Impact of the Internet
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
|| Chapter 7
Data Structures and Data Design Concepts
Physical Database Design
Structured Query Language (SQL)
Elements of a Relational Database
Tables, Rows, Columns, Relationships, indexes, views
DDL - Data Definintion language
DML - Data Manipulation language
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
|| Chapter 9
Team 1 Presentation
Planning the Architecture
Systems Design Completion
|| Chapter 10
Team 2 Presentation
Managing Systems Implementation
Software Quality Assurance
Overview of Application Development
Structured Application Development
Object-Oriented Application Development
Agile Application Development
Testing the System
System Installation and Evaluation
Operational and Test Environments
|| Chapter 11
Team 3 Presentation
System Support, Security and Post Go-Live
User Support and Operation
System Performance Management
System Security Overview
Backup and Recovery
Future Challenges and Opportunities
|| Chapter 12
All contents ©
NYU SPS Master's Degree Program web site
For more information, send e-mail to: