School of Information Systems & Technology. Course Syllabus: IS305, Information Systems Analysis and Design

Transcription

1 School of Information Systems & Technology Course Syllabus: IS305, Information Systems Analysis and Design Term: Fall 2010 Campus: Boeing Seal Beach Location: TBD Days & Times: Seal Beach sessions: Mondays 6:30-9:20 p.m. Online sessions: Asynchronous and synchronous (via Instructor: Bob MacLean Core Faculty Liaison: Terry Ryan Contact Information: Schedule of Office Hours: By Appointment Office Phone: Address: Cell Phone: Course Description: Covers the application development process from an object-oriented perspective. Various techniques for planning, analysis, design, and project management are discussed, with emphasis on UML and related methods. Prerequisites: IS303 and IS313, or permission of instructor

2 Objectives for Student Learning (Course and Program): Program Learning Outcomes Course Learning Outcomes: Graduates are prepared to be leaders in the IS field Graduates have core IS knowledge Graduates can integrate IS & business foundations Graduates have perspective on business and real world Graduates have communication, interpersonal, and team skills Graduates are able to think analytically and creatively Graduates have required career-specific skills Upon completion of IS305, students will know: how to write great software X X X X how to figure out what the customer really wants X X X X X X X how to respond to changes in what the customer wants X X X X X X X how to make sure that software will work in a real-world context X X X how to make software flexible X X X how to scale-up software as needed X X X how to minimize risk in software development X X X X how to apply design principles to reuse existing solutions X X X X how to prove to the customer that the software works X X X X X X what problems typically plague software development X X what life-cycle software development is X X X X X what agile software development is X X X X X

3 Grading: Graded components: Exercises 100 Tests 450 Project Grading scale 97% % A+ 93% % A 90% % A- 87% % B+ 83% % B 80% % B- 77% % C+ 73% % C 70% % C- Less than 70% U Books, Readings, and Materials: Required Textbook McLaughlin, B.D., Pollice, G., and West, D. Head First Object-Oriented Analysis & Design, O Reilly, ISBN (Shown in schedule below as OOAD.) Optional Textbook Sierra, K., and Bates, B. Head First Java, 2 nd Edition, O Reilly, ISBN (Shown in schedule below as Java.) Suggested Readings (All from IEEE Software, available from the Claremont Library web site) 1. Reusability: The Case for Object-Oriented Design, Bertrand Meyer, Mar./Apr Characterizing the Software Process: A Maturity Framework, Watts S. Humphrey, Mar./Apr Seven Myths of Formal Methods, Anthony Hall, Sep./Oct Prospects for an Engineering Discipline of Software, Mary Shaw, Nov./Dec Software Risk Management: Principles and Practices, Barry W. Boehm, Jan./Feb A Critical Look at Software Capability Evaluations, Terry B. Bollinger, Clement McGowan, Jul./Aug. 1991

4 7. Operational Profiles in Software-Reliability Engineering, John D. Musa, Mar./Apr The 4+1 View Model of Architecture, Phillipe B. Krutchen, Nov./Dec Architectural Mismatch: Why Reuse Is So Hard, David Garlan, Robert Allen, John Ockerbloom, Nov./Dec Anchoring the Software Process, Barry Boehm, Jul./Aug Course Requirements: the Exercises You must complete exercises as assigned by the instructor. These are due at beginning of class on the date specified in the assignment. Some assignments involve preparation of written deliverables; some require in-class presentation. Specifics will be explained by the instructor when the assignment is made. Exams There will be (2) midterms and a final exam. The exams will consist of a combination of multiple choice, true/false, and essay questions. Project Students will prepare and present an individual analysis and design project. Each student will partner up with 1 other student to form a team. Your team will then partner with another team that will serve as your customer and provide your project requirements. Your team will also serve as a customer team for another team. Each project must be approved by the instructor. Time will be allocated during each class session for you to meet with your partner, customer team, and contractor team. Deliverables for the project are due on the days specified in the schedule. All deliverables should be word-processed or CASE-tool-processed and stapled, with an appropriate cover sheet, which should include a title, the date, and the student s name with a sign off from your partner. All deliverable information will be compiled into a final report that will be submitted at the end of the class. E-Portfolio Requirement: In order to improve its courses, SISAT tries to assess student learning directly. As part of this, we require that every student in every course must document some aspect of his or her learning in the course using an e-portfolio. E-portfolios must be done with the Claremont Conversation Online. (For more details, see: To satisfy this requirement, an entry in the student s e-portfolio must be created, and it must address the learning objectives for the course and program. These are listed in the matrix above.

5 The instructor will determine whether the entry suitably reflects course- and program-related learning. She/he may ask the student to revise and resubmit the entry. There are many possible suitable entries. Possible examples include the deliverables for a class project, a paper written because of the course, or a series of blog entries. Any entry is acceptable that demonstrates that the student knows more about the course content than she/he did at the beginning of the course. It is important that the entry be non-trivial, but it need not be a major new undertaking either. Entries are intended to be a representation of what was learned. This is a special assignment. It is not used in calculation of your course grade; it is a requirement to get a grade. No final grade other than Incomplete (except Unsatisfactory ) will be assigned for the course until you have posted a suitable entry to your e-portfolio. Any e-portfolio entry intended to be used to satisfy the requirement for the course must remain in the student s CCO e-portfolio for at least one month following the course, to allow time for archival of pages to occur. Because entries to an e-portfolio provide you with an opportunity to reflect on your learning, we encourage you to create more than the one required entry, to share your entries with your classmates, and to collect entries across your classes in effect, creating a online collection of postings about what you have been learning. Such collections have value in expressing to yourself and others what you have learned in your degree program. Policy on plagiarism: Plagiarism will not be tolerated. The minimum penalty for plagiarism is a zero for the assignment; more severe penalties can include failure in the course and expulsion from the program. To avoid plagiarism, do not take credit for the work of others. Obtain permission from the holders of rights to any intellectual property you use, including text, code, images, etc. Provide a full reference for each work used. See for additional information.

6 Schedule for Course: SCHEDULE Date Reading Activity Aug 30 Appendix 2 Introduction to Course Sep 6 Labor Day No Classes Sep 13 Ch. 1 Sep 20 Ch. 2 Statement of Work Sep 27 Ch. 3 Oct 4 Midterm 1 Requirements/Feature List Oct 11 Ch. 4 Assignment 1 Oct 18 Ch. 5 Oct 25 Ch. 6 Use Case Diagrams Nov 1 Ch. 7 Nov 8 Midterm 2 Use Cases Nov 15 Ch. 8 Assignment 2 Nov 22 Ch. 9 Nov 29 Dec 6 Dec 13 Ch. 10 Class Diagrams Student Presentations Final Exam/Projects Date of Last Revision: June 27, 2010