Course Guide IS325 Systems Analysis & Design II Ms Fatima Khan Prince Sultan University, College for Women

Course Description The course helps newcomers to OOA/D learn how to “think in objects” by presenting three iterations of a single, cohesive case study, incrementally introducing the requirements and OOA/D activities, principles, and patterns that are most critical to success. The most frequently used UML diagramming notation will be introduced, while emphasizing that OOA/D is much more than knowing UML notation. All case study iterations and skills are presented in the context of an “agile” version of the Unified Process -- a popular, modern iterative approach to software development.

Course Objectives This course aims at presenting the essential topics of software engineering, i.e. what are the techniques, the theories, the tools, and the methodologies for developing large software systems. The emphasis of this course is OOAD (Object-Oriented Analysis and Design) of software systems using the UML and patterns. Students will become familiar with OO modeling techniques (using the Unified Modeling Language (UML)), agile ("lightweight") processes, software architectures, and design patterns.

Course Objectives 1.“Think in objects” 2.Analyze requirements with use cases 3.Create domain models 4.Apply an iterative & agile process 5.Relate analysis and design artifacts 6.Read and write UML 7.Assign responsibilities to objects 8.Design collaborations 9.Design with patterns 10.Design with architectural layers

Topics to be covered TopicsNo of Weeks Introduction1 Object Oriented Analysis and Design1 The Unified Process1 Inception & Understanding Requirements1 Case Tools1 Use Case Model2 Domain Model3 Design Model2 Modelling Behaviour More Patterns (if time permits) 2 Revision1

Course Resources This course is based on the book: zApplying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process by Craig Larman, Prentice Hall, Third Edition, ISBN

Course Location & Office Hours Course Location:  Saturday 8:00 – 9:50(W 351)  Tuesday 8:00 – 9:50(W 351) Office Hours:  Sunday 9:00 - 9:50 am.(W 351)  Tuesday 10:00-11:50 am.(Lab A)  Other hours strictly by appointment. Office : W Web Site:

Grading Policy AssessmentAssessment TaskWeek DueProportion of Final Assessment 1Attendance & ParticipationThroughout the Semester %5 2Quiz1Week 6%10 3Major ExamWeek 10%15 4Quiz2Week 14%10 5 Project WorkThroughout the Semester %10 6Research WorkThroughout the Semester %10 7Final ExamTBA%40 zNo Make-Up exams will be performed.

Assignment Policy Academic dishonesty in assignments includes (but is not limited to):  unacceptable collaboration What is unacceptable? There is a difference between discussing assignments and solutions with fellow students, and working together on the solutions to the point where the work submitted is clearly not individual work. If in doubt, ask your instructor.  copying of another student's assignment  allowing another student to copy  using code from an external source (text, instructor, course website) where a student's own code is expected (if in doubt, ask your instructor)  altering of assignment results. Assignments that are judged to be the result of academic dishonesty will, for the student's first offence, be given a mark of zero with an additional penalty equal to the weight of the assignment also being applied. The assignment (s) in question will be kept by the Department.

Attendance Policies Students that regularly come to class 10 minutes late will be marked absent. Students that are regularly absent will be given DN warnings. (See DN Warning Flyer). Students that are regularly late and/or absent will also receive lower class participation marks. Students that are not in class can’t participate!

Other Policies Website should be checked frequently. Students should read from the textbook. Late assignments, research work, or project work will be penalized.

Class Policies Be punctual. Your cell phone must be turned off or switched to the silent mode. No side talks or irrelative chat. No Abayas, pants, short skirts, or sleeveless blouses. You must bring a notebook with you to keep a record of all the important points I mention.

How to Study for this Course The primary source of material will be the book Applying UML and Patterns by Craig Larman. The book is excellent, and every computer scientist should own a copy. In general, the following is expected of you: ◦ You are expected to attend all classes. If, for some reason, you are unable to attend a class please send to the instructor. ◦ If you miss a class, you are expected to catch up with the material covered. ◦ You are expected to do all homework and turn it in on time. ◦ You are expected to do your own work, unless specifically told that you may collaborate. The main exception to this is the course project, where you must work in teams. ◦ You are expected to read all of the material and understand it. If you have questions about any readings, and the questions are not answered in the course of the class lectures, you are responsible for asking your instructor. ◦ Read the chapter before and after class. ◦ Make notes. Good Luck.