Instructor: Dr. Liping Liu, CBA360, X5947
Credits: 3 hours
Applicable Term: Spring 2025 (January 15-May 15)
Textbook:
- Main Text: Liping Liu, Requirements Modeling and Coding, World Scientific Publishing, 2020 (ISBN: 978-1-78634-882-1)
Reference Resources:
- Book: Matt Weisfeld, The Object-Oriented Thought Process, 4th/2013, ISBN: 9780321861276, Addison-Wesley Professional
- Book: Frederick P. Brooks Jr., Mythical Man Moon: Essays on Software Engineering, Addison Wesley, 1995. ISBN-13: 858-0001065793. (Note: the methodology is outdated, but the book is a timeless piece on experience of managing complex projects.)
- Book: Rebecca Wirfs-Brock, Alan McKean, Object Design: Roles, Responsibilities, and Collaborations, Addison-Wesley Professional (November 18, 2002), ISBN-13: 978-0201379433. (Note: Written by a OO pioneer, the book offers many practical strategies and techniques such as CRC)
Learning C# for Prerequisite:
- Short Free Videos on Basic Visual C# Programming at eduonix.com: https://www.eduonix.com/courses/Software-Development/Learn-C-Sharp-Programming-From-Scratch (Recommended Use: watch the videos and follow the hands-on exercises along the videos)
- Short Tutorials on Visual C# Programming with Quiz Questions at TutorialsTeacher.com: https://www.tutorialsteacher.com/csharp (Recommended Use: take quizzes and tests to check your skills and understandings)
Office Hours:
- 1:30-3:30 PM on Tuesdays and Thursdays (Instructor)
- 12:30-3:30 PM on Mondays (Prachi Ghawade)
- 10-12AM, Wednesdays (Prachi Ghawade)
Course Description: Systems Analysis and Design is about modeling business rules and processes and designing database-centric applications to satisfy business data and process requirements. This course follows the whole systems development life cycle and introduces the fundamental concepts and techniques of use case modeling, object modeling, procedure modeling, and requirements validation. Prerequisite: 6500:602 or 6200:603
Objectives: Students are expected to understand the role of systems analysts in business, understand the process of systems development, and acquire the basic skills of modeling business functions and procedural logic, software architectures, and use behaviors. Students are encouraged to learn the comprehensive techniques of UML modeling, use case documentation, and object-oriented development methodology to embrace abundant career opportunities as systems analysts, data analysts, software engineers, and business process architects.
Weekly Schedule:
- Week 1: Introduction: information systems, systems analysis, and systems development life cycle (Chapter 1)
- Week 2: Programming Principles (Chapter 2)
- Experiential Learning Project: Developing Data Analytics System
- Week 3: Modeling and Programming Business Processes: Data Flow Diagrams <=> Operations and Activity Diagrams <=> Methods (Chapter 3)
- Week 4: Advanced Procedure Modeling and Programming: Nested Loops in Activity Diagrams, Advanced Functions and Function Invocations (Chapter 4)
- Week 5: Modeling and Programming Business Objects I: Concepts of Object-Orientation. (Chapter 5)
- Week 6: Modeling and Programming Business Objects II: Class Diagramming (Chapter 6)
- Week 7: Modeling and Programming Business Objects III: Advanced Object Modeling (Chapter 7)
- Week 8: Midterm Exam
- Week 9: Use Case Modeling, Optimization, and Storyboarding (Chapter 9)
- Week 10 Use Case Storyboarding and Interface Design. (Chapter 10)
- Week 11: Human-Computer Interface: User Interface Design Principles (Chapter 11)
- Week 13: Collaboration Modeling (Chapter 15)
- Experiential Learning Project: (due before the class)
- Week 14: Collaboration Programming (Chapter 14)
- Week 15: Final Exam
Exam Schedule: This course will have two major exams scheduled (see the weekly schedule above). The exam includes both hands-on and written questions
Assignments: Homework is assigned once a week. Assignments are due at the beginning of each class. No late homework will be graded. Please show your work in a neat and orderly fashion. Write or type your work on one side and in every other line. Use standard size paper (8 1/2'' by 11''). Do not use spiral notebook paper. For electronic submissions, it is the student's responsibility to submit correct files in correct formats.
Attendance: Attendance is MUST and will be 10% of your final grade. Attendance will be managed by ecourse.org system. The formula for computing your attendance grade is non-linear. It will take 3 points off for the first absence and 7 points off for second absence. If you missed the equivalent of three-week classes, you fail the course automatically. Under special situations, you can take a class online with the following guidelines:
- You must obtain permission from the instructor at least one day ahead of the online session
- Follow the lecture or its recordings to perform all in-class hands-on exercises and take notes. Within one day of the class, submit your notes and the finished exercises to ecourse.org as Proof of Attendance for the online session.
- All weekly assignments are due at the same time as in-person classes. All exams must be onsite.
Quizzes: I will use quizzes regularly to check your completion or preparation of assignments.
Makeup: Each student with appropriate excuses may have at most one chance to makeup homework or quiz. Note that it is your privilege but not right to have this special favor. Also, all makeups must be completed within one week of due date and before answer key is released.
Grades: Your final grades will be calculated by the following formulas:
40% (HW) + 45% (Tests) + 5% (Project) + 10% (Attendance)
A = 93-100%; A– = 90-92%; B+ = 87-89%; B = 83-86%; B– = 80-82%; C+ = 77-79%; C = 73-76%; C– =70-72%; D = 60-69%; F = 59% and less
Misconduct: Academic misconduct by a student shall include, but not limited to: disruption of classes, giving and receiving unauthorized aid on exams or in the preparation of assignments, unauthorized removal of materials from the library, or knowingly misrepresenting the source of any academic work. Academic misconduct by an instructor shall include, but not limited to: grading student work by criteria other than academic performance or repeated and willful neglect in the discharge of duly assigned academic duties.
On Collaboration: All for-credit assignments, except for those designated as group projects, must be done independently, and collaboration in providing or asking for answers to those assignments constitutes cheating.
On AI Tools: In this class, I allow students to use AI tools to help their learning. However, submitting AI generated work for credits is a violation of academic code. If a submitted work is suspected to be AI generated, the student will be asked to reproduce the submitted work in front of the instructor.
School Rule Cited: For graduate students that have been caught cheating: First offense = either a zero on the exam or assignment, or an F in the course; Second offense = Either an F in the course or expulsion (depending upon the punishment of the first offense)
|
