ISOM3210: Information Systems Analysis and Design (Spring 2015)

Transcription

1 ISOM3210: Information Systems Analysis and Design (Spring 2015) Instructor: Dr. Jia Jia Contact: Office: LSK 5045 Office Hours: Wed. 1:00pm 4:00pm and by appointment Class Schedule: Wed. & Fri. 4:30pm-5:50pm (LSK1001) Lab Schedule: Fri. 3:00pm - 4:00pm (LSKG005) Course Website: Textbooks (for reference to topics): 1. "System Analysis and Design with UML: An Object-Oriented Approach", by David Tegarden, Alan Dennis and Barbara Haley Wixom; 4th ed., 2012; John Wiley & Sons; ISBN AUCM 1 : Advanced Use Case Modeling, 2 nd printing, by Frank Armor and Granville Miller, Pearson, April ISBN Introduction Nowadays, many firms attempt to develop new information systems (IS) to gain competitive advantages and deal with various challenges in an increasingly competitive business world. The primary objective of IS development is not to create a wonderful system. Instead, it is to facilitate and improve the work processes for a firm to achieve better performance. It is not uncommon that firms experience time and cost overruns in their system development projects because IS managers (or analysts) try to build a system without clearly understanding how a new system will fit with the firm s strategic goals, current business processes, and other existing systems. As firms continue to implement different systems that are not integrated with each other, their overall business efficiency may decline. Therefore, it is critical to identify the core issues, analyze the business processes, and formulate integrated solutions. This course will provide an overview of fundamental principles of IS development methodologies. The primary objective of this course is to provide business students 1 Relevant topics will be scanned and posted on Canvas. 1

2 with the key skills related to IS development: Understand the IS development process; Capture and analyze user requirements; and Document those requirements using proper methodologies and modeling tools, and be ready to move into the design and implementation phase of the systems development cycle. 2. Key Components of the Course The course includes the following three key components: Lectures: to explain and discuss the key topics on system analysis and design and provide students with in-class exercises relevant to the topics Labs: to strengthen the knowledge acquired in lectures by working on more advanced exercises Team project: to provide students with hands-on experience in applying knowledge and skills learned in class to real-life applications 3. Learning Outcomes (Adapted from Outcome Based Education (OBE): PILOs-BBA-IS) Course student learning outcomes: Analyze the core issues and identify critical factors for IS development-related decision-making Solve business problems using analytical IS development methodologies Understand how IS interact with other business areas Demonstrate substantial knowledge and understanding of system analysis and modeling paradigms Apply IS development frameworks and tools to resolve business problems in the IS sector of an organization and other business sectors relying on IS Understand key IS development management issues and make sound IS development decisions as business managers In addition, throughout the semester, students will have opportunities to develop ability to: Produce professional quality business documents in English Deliver a professional quality presentation in English Communicate ideas persuasively to inform and convince others Demonstrate an understanding of team dynamics and the various roles played within the team Contribute to the successful and timely completion of a group project in line with 2

3 their roles in teams Collaborate positively by actively seeking and engaging in discussion of the views of others while showing sensitivity to opposing views Demonstrate the ability to lead a team to success 4. Grading Individual efforts (60%) Mid-term exam (25%) Final exam (25%) Participation (10%) Lecture (5%) Lab (5%) Team project (40%) Proposal (5%) Report (25%) Presentation (10%) Class participation Students are expected to come to class prepared and to participate in discussion. We highly value your inputs, and so participation marks will be awarded to those who make an effort to attend regularly and actively engage in class discussions. Both quality and quantity of your contribution will determine the credit for participation. Labs For each lab, there is a task that you need to complete during the lab session. You must attend the lab session to which you are assigned. Your performance of the lab exercises will determine the credit for participation. Project Students have to complete a team project requiring them to perform systems analysis and design activities on a proposed system. The project team will comprise 5 to 6 students. Each team needs to submit a project proposal and a final report, and make a presentation by the end of the semester. More details about the project will be provided. Examination 3

4 One mid-term exam will be administered during the semester followed by a final exam in the official final exam period. The exams are expected to measure the degree to which students individually have understood the key concepts covered in class. To help you prepare for the examinations, review sessions will be offered. Makeup examinations will be allowed only in cases of documented health or family emergencies or for official, university-sanctioned activities. The instructor reserves the right to use a percentage score of the other examinations to make up for missed examinations. Advanced notification of missing an examination is required. Any uncoordinated absence from an exam will result in a score of 0 for the exam. 5. Academic Integrity Academic integrity entails absolute honesty in one s intellectual effort. In general, students who are found cheating or plagiarizing other people s work will immediately fail the course and be subject to further disciplinary actions. For more information, please refer to the following Website: 4

5 Class Schedule (Tentative, last updated on Feb. 2 nd 2015) Week Date Topic Readings Lab Due 1 Feb. 4 Course Introduction Introduction: Systems Development Life Cycle (SDLC) Ch. 1 Feb. 6: Lab Session, Project introduction and Feasibility Analysis Feb. 6 Planning: Project Identification and Selection Ch. 2 2 Feb. 11 Analysis: Requirement Ch. 3 Feb. 13: Course Analysis Identifying functional and Add/Drop Feb. 13 Introduction to Object-Oriented Modeling AUCM Ch. 7 non-functional requirements (Feb. 14) Using the UML 4 Feb. 25 Object-Oriented Modeling I - Base Use Case Description AUCM Ch. 7 AUCM Feb. 27: Initial and Base Use Case Description Exercise Project Team Formation (Feb. 25) Ch. 8 Feb. 27 Use case exercise 5 Mar. 4 Object-Oriented Modeling III AUCM Mar. 6: Project - Elaborated Use Case Description (Alternative and Conditional) Ch. 9 Elaborated Use Case Description Exercise Proposal Due (Mar. 6) Mar. 6 Object-Oriented Modeling IV Ch. 5 - Elaborated Use Case Description (Included and Extended Use Cases) 6 Mar. 11 Interim Report Meeting I No Lab Mar. 13 Mid-term Exam Review 7 Mar. 18 Mid-term Exam Mar. 20: Mar. 20 Class Diagram I Ch. 6 MS Visio Tutorial 8 Mar. 25 Class Diagram II Ch. 6 Mar. 27: Mar. 27 Exercise: Class Diagram Class Diagram I 10 Apr. 8 No Class Apr. 10: Apr. 10 Interim Report Meeting II Class Diagram II 11 Apr. 15 Sequence Diagram Ch. 6 Apr. 17: Apr. 17 Behavioral State Machine Diagram I Ch. 6 Sequence Diagram 5

6 Week Date Topic Readings Lab Due 12 Apr. 22 Behavioral State Machine Diagram II Apr. 24 Comprehensive Exercise Ch. 6 Apr. 24: Behavioral State Machine Diagram 13 Apr. 29 Presentation Sequence & Final Exam Review May 1 No Class No Lab 14 May 6 Project Presentation I No Lab Team Project May 8 Project Presentation II Final Report (May 9, 5:00 pm; by ) 6