SYLLABUS CIS 3660: OBJECT-ORIENTED SYSTEM ANALYSIS AND DESIGN SPRING 2010

Transcription

1 SYLLABUS CIS 3660: OBJECT-ORIENTED SYSTEM ANALYSIS AND DESIGN SPRING 2010 Instructor: Dr. Silvana Faja Office: WDE 2400 Office Hours: 9:30 10:45 and 1:30 3:00, Tuesday and Thursday and by appointment Office Phone: Address: URL: Blackboard COURSE OBJECTIVES The purpose of this course is to introduce students to the fundamentals of analysis and design of computer information systems to meet business requirements. Students will learn and practice various methods, tools and techniques used by the systems analyst at each phase within the systems development cycle. The field of system analysis and design is continually evolving. Today, the most exciting change to system analysis and design is the move to object-oriented techniques. The course will cover object-oriented systems analysis and design techniques as well as managerial aspects of analysis and design such as project management and information gathering techniques. The course also introduces computer aided software development (CASE) technology. TEXTBOOK Alan Dennis, Barbara H. Wixom, and David Tegarden, Systems Analysis And Design with UML Version 2.0 An Object-Oriented Approach, 3 nd edition, John Wiley & Sons, Inc., 2009 (required) Additional materials: 3 Scantrons (Form 882-ES) Software: MS Project, IBM Rational RequisitePro, IBM Rational Software Modeler (available in the lab). 1

2 COURSE OUTCOMES 1. Technology - Become familiar with major systems development methodologies and the criteria for their selection. - Describe the key concepts, major objectives, task set, and tools used in each phase of the SDLC. - Understand fundamental concepts and object-oriented techniques of systems analysis and design. - Be able to gather and document system requirements. - Create functional models of the system with activity diagrams, use-case diagrams, and use-case descriptions. - Create structural models of the system with class diagrams. - Create behavioral models of the system with state charts and sequence diagrams. - Understand and employ the fundamental principles of user-interface design - Demonstrate the ability to use project management tools - Use of computer based tools to aid in system analysis and design. 2. Business Knowledge - Be able to analyze business processes and data of an organization to model its information processing needs. 3. People Skills - Communicate with potential systems users effectively and professionally, to elicit and define user requirements. - Demonstrate the ability to communicate effectively in both written and oral forms during systems development process. - Practice attitudes necessary for successful team behavior. COURSE ACTIVITIES: Exam points Exam points Exam points Assignments 150 points Group Project points Class participation.50 points Total 600 points 2

3 Calculation of final grades: A = points (90% and above) B = (80%-89.5%) C = (70% -79.5%) D = (60%-69.5%) F = 357 and below (59% and below) Exams There will be 3 exams as indicated in the class schedule. They examine the theoretical knowledge and practical skills that you have learned in this course in lectures, textbook, lab sessions and learning activities. No make-up examinations will be given except for university-approved absences. If you must miss an examination, you must let me know about this prior to the exam. Individual Assignments There will be several individual assignments re-enforcing some of the key knowledge acquired in class. Assignments are due at the beginning of the class on the date specified. Late submissions will be accepted, but they will be penalized 10% each day, beginning the day it is due. Assignments turned in more than three days late will be scored as a zero, unless prior arrangements have been made. Assignments due dates in the class schedule in this syllabus are only tentative. All due dates will be announced in class and posted on Blackboard. Please pay attention in class and review Blackboard regularly. Group Project Groups of 3-4 students will be formed at the beginning of the semester. The group project involves the analysis and design of an information system in a real life organization. Your group should find an organization, analyze its activity and develop a proposal for a new information system/product to meet the organizational needs or to improve the existing information system. The purpose of this project is to apply the theoretical concepts and technical skills we learn in class to a real life situation, develop analytical and critical skills in the context of information technology as well as the ability to work in a team. A separate document will provide details concerning the class project. After the completion of the project, each team member will complete a peer evaluation form. Your grade for this assignment will be weighted based on peer evaluations. 3

4 Class participation and activities You are expected to attend classes on a regular base. If a student misses class, he or she is responsible for any material covered during his or her absence. Attendance will be taken at the beginning of each class. Attendance and class participation are worth 8% of the final grade. During the semester there will be several class activities, where you will participate individually or in group. You are expected to read the assigned reading material and participate in class discussions and activities. Grade Availability Grades will be available on Blackboard as soon as possible. After availability has been announced (or after assignments already graded are handed back) it is your responsibility to check for correctness and/or omissions. The deadline to request any potential corrections to a grade is two weeks after the availability date. ACADEMIC HONESTY Students who violate the University policy on academic honesty will not be tolerated in class. It is acceptable to discuss conceptual aspects of the projects with other people; however, do not key your assignment from someone else s work, do not allow someone to key your assignment, do not allow anyone to dictate keystrokes to you, and do not copy another person s project files onto your disk. All written work is to be unique to you. Any student who turns in work that is not their own or who is observed copying off another during a testing situation will be immediately reported and recommended for disciplinary action in addition to receiving a 0 for that work. Below is the to link the HCBA code of conduct: Role of CIS 3660 in CIS Major Students successfully completing the CIS major will be able to: 1. Demonstrate knowledge of professional and ethical expectations in the work place. 2. Use productivity software (word processing, spreadsheet, and database) effectively and manage hardware and software resources by applying knowledge of operating systems and environments. 4

5 3. Develop application software using skills in appropriate business programming languages (e.g. COBOL, Visual Basic, Java) 4. Develop and maintain databases using theoretical and applied knowledge of relational database management systems (e.g. Oracle, DB2). 5. Develop and maintain telecommunications networks using theoretical and applied knowledge of telecommunications (e.g. Novell, Windows/NT). 6. Analyze business problems and develop solutions by applying critical thinking skills within the systems development process (e.g. The Systems Development Life Cycle [SDLC] and Information Engineering. 7. Be a team player by applying group process skills: participate fully in group discussion and activities, lead/follow when appropriate, provide support and collaboration when needed. 8. Access information resources and communicate effectively using a variety of methods: oral, written, and electronic. 9. Design and construct client/server applications by using appropriate tools and architectures and develop effective graphical user interfaces (GUIs). 5

6 TENTATIVE COURSE SCHEDULE Date Topics Chapter Assignment Due 1/12 Course Orientation 1/14 Introduction to Systems Analysis and Design Ch. 1 1/19 Project Initiation Ch. 2 1/21 Project Initiation 1/26 Project Management Ch. 3 HW 1 1/28 Project Management 2/2 Project Management 2/4 Requirements Determination Ch. 4 HW 2 2/9 Exam 1 (Chapters 1-3) 2/11 Requirements Determination Group project proposal 2/16 Functional Modeling (Activity diagrams) Ch. 5 HW 3 2/18 Functional Modeling 2/23 Functional Modeling 2/25 Functional Modeling (Use case diagrams) 3/2 Functional Modeling Group project report 1 3/4 Structural Modeling Ch. 6 HW 4 3/9 Structural Modeling 3/11 Behavioral Modeling Ch. 7 HW 5 3/16 Spring Break 3/18 Spring Break 3/23 Behavioral Modeling 3/25 Behavioral Modeling 3/30 Exam 2 (Chapter 4-7) 4/1 Moving on to design Ch. 8 4/6 Moving on to design HW 6 4/8 Class and Method Design Ch. 9 4/13 Class and Method Design 4/15 Human Interface Design Ch. 11 4/20 Human Interface Design 4/22 Physical Architecture Layer Design Ch. 12 HW 7 4/27 Physical Architecture Layer Design Group project final report 4/29 Physical Architecture Layer Design 5/4 Final exam (Chapters 8, 9, 11, 12) Note: The above schedule is subject to change if it is deemed appropriate at the instructor s discretion. 6