Homework answers / question archive / Online Univ Reg System Q

Online Univ Reg System Q

Computer Science

Share With

Online Univ Reg System Q. H Chap 5 Course Info : Course Info Allow Staff to Examine course offerings Course Offerings : Course Offerings Allow Staff to manage course offerings Add Course Update Course Remove Course Student Info : Student Info Check for unpaid fees Student fees : Student fees Allow students to manage enrollment Schedule Course info : Student Enroll schedule : Student enroll schedule Add Course Examine Available Courses Drop Course Examine enrolled courses unacceptable Check Max # of Reg courses # of courses : Max Limit Status : acceptable Selected Courses : Selected Reports : Register For Courses Print reports Registered Courses : Registered Courses Printed Reports : On-line Univ Reg Sys Overview Use case Diag * Allow satff to Examine Course Offerings * * Top Package::Staff * * Allow staff to Manage course Offerings * * * Check for Unpaid fees * * Top Package::Student * * * Allow Students to manage enroll schedule Register for Courses * Top Package::Reg System * * * Print Reports * Check max # of Reg Courses On-line Univ Reg Sys Q. H Chap 5 Top Package::Course Offerings -Course# -CourseName -Credits -Day -Time -Location +Add() +Update() +Delete() Top Package::Student fees -Bal -DaysOverdue +Add() +Remove() +Update() +Calculate() 1 * * * -Pays -enables 1 Top Package::Registered Courses -CourseName -Course# -Credits -Time -Date +Add() +Delete() +Update() -checks 1 * * Grade -Grade -Date +Add() +Change() Top Package::Student Info -FName -LName -Street -City -Tele -Zip +Add() +Delete() +Update() 1 1 -print * Top Package::Printed reports -ReportName -DatedPrinted -#ofPages +Print() -has 1 Top Package::Student enroll schedule -className -Class# -Day -Time +Add() +Delete() +Update() +Examine() C:\Users\cloudconvert\server\files\121\127\0\eb5506bc-9cbe-412a-9561474eaea555a4\20210506221424hw_assignments_undergrad.doc MIS 360 HW Assignments See syllabus for assignment due date You are a systems analyst whose job is to analyze and design business and functional requirements for a DVD store. It is an online store with its own inventory warehouse. The HW should focus on two primary perspectives, 1. The customer activities on the website and 2. The procurement activities for purchasing inventory. Chapter 12 PDF explains the procurement process. HW Assignments: 1. Activity Modeling Use an activity diagram to design the business activities and their relationship. That is, you need to consider how the DVD store will operate. Factors to consider include but not limited to: 1. How will customers shipments be handled; 2. How is the receipt of company inventory handled and managed; 3. How is returned merchandise handled (i.e., inventory, customer credit, etc); 4. How is billing handled; 5. What forms of payment do you accept (cash, check, credit/debit cards etc.) and how are they handled; 6. How do customers know what products are available; 7. Other operations and activities not listed here. Note: the first draft is due a week before the assignment is handed in (see syllabus). The draft is to ensure 1. Assignment is done in Visio and 2. Answer any questions you may have before the due date. 3. To get the HW started early. 2. Use-Case Modeling 1. Develop a single overview use-case diagram. The diagram must have a minimum of 16 used cases (i.e. 16 functions of the DVD store from HW 1). On real projects you do not get to pick 16 activities. This decision is to reduce the size and complexity of the HW. I believe you can demonstrate your knowledge by using 16. I recommend picking the best 8 from the font end and best 8 from the back end that will provide as much detail as possible. The detail diagrams have includes and extends and the overview has none (see discussion in text book). This explains why the overview UC diagrams have less detail than the detail UC diagrams. It is the includes and extends that provide the details. When necessary, it is wise to improve/update the AD before creating the UC diagram. The book states that a system cannot have more than 9 use cases but you may violate the rule providing the diagram does not become cluttered and difficult to read. If that is the case, use two overview diagrams. 2. Develop one overview and two detail diagrams: 1. One detail for handling all back end related activities of the Store (backend) 2. One for handling all customer (front end) related activities of the Store Note: if the back end and customer functions were not part of the original 16, you have to add them. You may also identify additional back end and customer functions. C:\Users\cloudconvert\server\files\121\127\0\eb5506bc-9cbe-412a-9561474eaea555a4\20210506221424hw_assignments_undergrad.doc How to Prepare for the HW 1. Study the rules for each diagram. 2. Think about the various activities that the store must carry out for it to be functional. These activities are required for the activity diagram. The in-class skit will help to identify some of the activities you will need. You may also talk to people who have worked in retail stores. 3. Make a comprehensive list of the activities; it will take several days or weeks to compile a comprehensive list. 4. For each activity, identify and decisions associated with it. For example, making a payment is an activity; the decisions are the various ways a customer is allowed by the business to make payments. There is no limit to the number of decisions an activity could have. 5. Connect the activities as you see fit. 6. Connect the inputs and outputs to each activity and complete the diagram. 7. Completing the diagram will require several iterations. If you complete it in one iteration, you should be very concerned. 8. Let it sit between iterations and continue to improve and perfect it. 9. Pay strict attention to the syntax and semantics of the diagram The activity diagram plays a role in constructing the other diagrams. If it is incomplete and of poorly quality, it will have a negative impact on the rest of the assignments. If a diagram is too large you may decompose it into smaller diagrams, even though in principle it is one diagram. For example, the HW could be completed as a single diagram or decomposed into two smaller diagrams, 1. Customer related activities and 2. Procurement related activities. This makes it more manageable for some students. 05/09/21 Document1 This syllabus is subject to change at the discretion of the instructor. Students will be notified and are responsible for any changes that are announced in class or via the class web site. Changes to the syllabus are posted in red! MIS 360 Systems Analysis and Design Instructor: Dr. Grant Online Asynchronous: Office Hours: We have weekly “Ask Me Anything” Zoom session every Mon 6 pm CT Office: DPC 6023 email: dgrant2@depaul.edu Student Responsibilities Students are expected to be prepared for class. Students are expected to be on time for class. Students are expected to attend all class sessions and stay for the duration of class. Students are responsible for delivering assignments on time. Students are responsible for doing their fair share of work on group projects. Students are responsible for familiarizing themselves with the syllabus. Students are responsible for and staying abreast with any subsequent changes to the syllabus. Students are responsible for printing and carrying a copy of the syllabus. Students are responsible for providing pencil and eraser on exams or quizzes. Students are responsible for coming to class prepared. Students are responsible for signing the attendance sheet. Students should read the notes pertaining to the HW before attempting it. Students should do practice problems before attempting the HW. Students are responsible for knowing how to use Microsoft Visio 2003. See file on how to use it Students are responsible for any announcements made in class. Course and Behavioral Objectives: 1. Students should be proficient in the use of techniques, methods, and tools for analyzing and designing information systems. 2. Students should understanding the fundamental concepts of Systems Analysis and Design 2. Students should be able to analyze and design information systems using UML. 3. Students should be familiar with issues and problems encountered by systems analysts. Required Text: Systems Analysis and Design: An Object Oriented approach with UML Version 2.0, 5th Ed, by Dennis, Wixom, and Tegarden, Publ. Wiley, ISBN 978-1-118-80467-4 Supplemental Readings: Business Processes and Information Technology by Galinas, Sutton and Fedorowicz, Publ. Thompson Learning. The three chapters from this textbook each describes a business processes Chapter 10 Order to Cash, Part I; Chapter 11 Order to Cash, Part II; and Chapter 12 Purchase to Pay. The objective of the readings is to 1 05/09/21 Document1 enlighten you about important business processes that should find their way into your AD and UCD home work. Pay close attention to the horizontal flow activities, their inputs and outputs that make up each business process. The activities, inputs, and outputs are emphasized in the online quiz, so take notes when you read. You have about 4 days to complete it. Missing the due date earn you zero points. Chapter 12 Purchase to Pay (PtoP) Questions to focus on: Know the definitions of terms like, requisition, purchase order, accts receivables, accts payables, vendor packing slip, vendor invoice, and so on. What are the primary functions of the PtoP Process? What is the primary responsibility of the following depts. (accts payable, receiving dept, purchasing dept, inventory and so on) and the role that each manager of the dept plays? What are the horizontal info flows that make the process function properly (p. 425-425) and why are they needed? What are some of the sources of data used in the process and what is the importance of each data source. Try to identify as many data sources (data files). Also read p 438-439. Browse p 431-437. Chapter 10 read P. 328-331; Chapter 11 Billing Process read p. 387-388; read p. 375- 377 Know the definitions of terms like, bill of lading, packing slip, picking ticket, and so on. What are the primary functions of the Order to Cash process Visio is used to create diagrams. To learn it, go to LinkedIn Learning. All DePaul students have access to the site (DePaul login info is required). Employers expect MIS professional to be familiar with it, because it is the most widely used CASE tool. Grading Policy: Grades will be rounded two one decimal place. Therefore, 92.95 will become 93. 0 = A while 92.94 will become 92.9 = A-. Final course grade will be determined by: 1. Exam 30% 2. Assignments 35% (Proc 5%, AD 10%, UCD 10%, S&B Mod 5%, HCI-Phy 5%) 3. Project 35% To calculate your grade use this: .30*(exam grade/100) + .05*(proc grade/20) +.10*(AD grade/100) + .10*(UCD grade/100) + .05*(S&B grade/20) + .05*(HCI-Phy grade/20) + .35*(Proj grade/100) Score Grade Score Grade Score Grade 93 A 80 B66 D+ 90 A77 C+ 60 D 87 B+ 73 C < 60 F 83 B 70 C- 2 05/09/21 Document1 Quality of work: Getting an excellent grade requires high quality work. This includes, but is not limited to the following: • The use of paragraphs to express each main idea • The use of a spellchecker • No typos • Clear expression and organization of ideas • Supporting detail for main ideas • Thoroughness and completeness of the assignment Grading Expectations: This course is challenging for several reasons. First, the course requires the modeling of several business processes and in order to model a process one must understand it. Therefore, it is extremely important that you read up on business process and talk to people who perform them. If you do not have a thorough understanding of a business process, you will do a poor job modeling it. It is not recommended trying to model a process if you do not understand how it works. Second, UML is a language used to model business processes and like any language it has rules of syntax and semantics. Syntax is related to the symbols and how they are used to construct diagrams. Semantics have to do with the meaning that is conveyed to the user through the diagram. Therefore, for each assignment your grade will depend heavily on several factors including syntax, semantics, thoroughness of the process, completeness of the process, aesthetics, and the extent to which good business policy is reflected. Third, most undergraduate students lack business process knowledge and so for the first time they are forced to think in business terms and model the business process at the same time. This is not an easy task for most students; hence research and an understanding of the business are required to do well. Syntax: Points will be deducted for every syntax error. Semantics: Points will be deducted for every instance where the meaning is ambiguous. Thoroughness and completeness: points will be deducted if part of the business process is missing or incomplete. Aesthetics: This is related to how the diagram looks to the user. If the diagram is not appealing and turns off the user thus causing him to lose interest, then points will be lost. Therefore, avoid crisscross lines. Good business Policy: Good Business Policy should be reflected in the process if not points will be deducted. Good business policies involve business rules that would cause a business to thrive for a very long time and lend itself to high levels of customer satisfaction. How I Grade HW and other Assignments (grading philosophy): This section is intended to shed light on what to expect when I grade your work by incorporating more objectives measures in the grading process. It is clearly an attempt to remove as much subjectivity from the process. Grading often involves a measure of subjectivity, and the level of subjectivity varies with the topic and/or subject matter. In analysis and design it is impossible to remove subjectivity entirely because there is no single right or wrong answer to a given business problem. Some parts of a solution are naturally subjective; evaluating the aesthetic beauty or the semantic meaning of a diagram will always be subjective. Any business problem always has a range of possible solutions, some of which are clearly superior. My job is to determine the correctness of your solution and that is where my subject opinion and expertise play an important and inevitable role in the grading process. There are some parts of the grading process that lend themselves to more objective measures. I recognize that trying to be more objective has some limitations but I also recognize that moving to more objective measures has some merits. My intention is to incorporate more objective measures into the grading process. However, no matter what approach I use there are inherent 3 05/09/21 Document1 limitations, hence the approach taken here is definitely a compromise yet somewhat imperfect. The upside to adopting more objective measures is that students know ahead of time how they will be evaluated. When they receive their graded assignments, it would be clearer how they were graded especially on specific aspects of their solution. For example, every diagramming error will cost you a 2-point deduction (see list below). The downside to this approach is that some errors are more severe than others and I would have liked to reflect that in my grading. With this new approach that level of subjectivity is now removed by treating all errors as though they are equal. In reality, some errors are catastrophic while others are just insignificant. In my attempt to objectify the grading process the best I can, here is how you will be evaluated. On a 100 point scale, two points will be deducted for every syntax or semantic error identified. Therefore, if an error is repeated you will loose 2 points every time. Here is an incomplete list of errors: • • • • • • • • • • • • Crisscross lines that could be avoided Confusing situation Missing process, activity, use case, class, object, etc. Inappropriate or poor labeling Part of the diagram is missing when printed Missing titles on diagrams Instances of poor business policy reflected in the diagram. Therefore, it is very important to provide a list of assumptions with explanations when necessary If the homework consists of two diagrams and you hand in only one, you will be graded out of 50% Missing boundary Missing actors Actors misplaced; actors should always be on the outside of the diagram Syntax or semantic violations not listed above NOTE: 50 points will be deducted for submitting the wrong diagram. For example, submitting an overview use case diagram when the HW called for a detailed use case diagram. Please note that all the rules outlined here will be strictly enforced. To do 1. 2. 3. 4. 5. well on HW assignments, pay attention to these things: Pay attention to the list of errors above Spend a considerable amount of time researching and understanding the process before you model it Pay strict attention to the syntax Make sure each symbol of the diagram is correctly used and applied Do not try to create the diagram in one attempt; allow time to reread and improve the diagram over several iterations 6. Check for completeness of the diagram 7. Follow directions 8. Avoid crisscross lines when possible because they detract from the beauty of the diagram and create confusion for the user. As the amount of confusion increases the amount of semantics decreases. It is also possible to have no crisscross lines yet the diagram is confusing (low on semantics). Exams Homework and online quizzes provide the primary means of keeping students informed of their progress. Students should use them to judge their preparedness. The exam is comprised of 60 multiple choice questions, and two problems similar to the HW. Preparing for the exam should start the first week of class by doing the HW, quizzes, doing extra problems from the book, going over the review questions, studying 4 05/09/21 Document1 regularly, and so on. The multiple choice questions will cover basic definitions and terms from the text and is worth 1 point each. Missing HW, Quizzes, and Exams Students missing the deadline on quizzes, HW, exams, etc., are out of luck without a doctor’s note. This policy will be strictly enforced. Workload Students are advised to do all assignments, quizzes, etc. They provide the necessary practice to master the material. It is inconceivable students do well without expending sufficient effort and time practicing and studying. Students should plan on spending about 9 hrs per week outside of class. I strongly recommend that students working full-time should not take more than two classes and full-time students should not work more than 20 hrs. Students working full-time and going to school full-time is a recipe for poor performance. Home-Work Assignments All assignments must be done with the aid of the computer. All diagrams MUST be done using Visio and/or Word. When uploading assignments to D2Lmake sure the document is properly formatted and legible. Those who violate this policy will lose points because I can’t grade what I can’t see clearly or is confusing. Make sure to check D2L to ensure that you file was uploaded. Make sure you have enough time to upload your file and check to make sure it was uploaded on time. Forgetting to attach your file will not be considered an excuse for uploads. You have several days to deliver HW so late assignments get zero. Microsoft Visio is installed in Lewis on the 14th floor (1420). You can download a free copy of Microsoft Visio from Https://software.depaul.edu. Then select personal computers. 5 05/09/21 Document1 Then select Microsoft Azure Dev Tools for Teaching Sign in with your DePaul email, after sign in, select the download software button and scroll down to Visio.There is a view key button to the right (not shown here). Write it down you will need it to complete the install. There is no Visio for Mac users. They should access Visio through the Virtual Lab website: https://vlab.depaul.edu For Mac Users: Exporting from the Virtual Lab to your Word document. This article explains how to export a Visio diagram to a Word document: https://support.microsoft.com/en- 6 05/09/21 Document1 us/office/document-visio-process-diagrams-in-word-48073f4f-c6d4-4cc0-b9ae-3cb65e2ee158?ui=enus&rs=en-us&ad=us If you are using Apporto on your Mac. This article explains how to download the file from Apporto: https://www.apporto.com/helpcenter-enduser/uploading-a-file If you have trouble, please contact the TSC help desk 312 362 8765 for direct assistance. There will be NO second chance on HW assignments so make sure to do your best on each assignment. All up loaded files must include the sender’s name. Group Term Project The team project would be based on the Cohesion Case which can be found at www.cohesioncase.com. It is divided into several areas (ERP, CRM, SCM, Sys Dev, Networks and Telecom, E-business, etc). Each team will select a project topic by informing the instructor, on a first come basis. Click on the Cohesion Case Diagram link. Each of the above areas must have an Internet component. Term Project Outline Draft Project outline and contract should be uploaded to D2L by the third week but not later than week four. The project should include a cover page, table of contents with team member names attached, a short description of the business, and section headings. If there is any other item you would like to add feel free to do so. Team members must decide how the work is to be divided equally and fairly among team members. It is unfair and unequal for a student to work on a system request, problem definition, and/or project scope while others are responsible for AD, GUI, UCD, and other major pieces of work. Who is responsible for the various parts of the project must be in the form of a written contract. The contract must address penalties for team members who do not pull their weight. It must also address expectations of team members and each member must sign the document. Projects that do not have a contract will not be graded. Team members will evaluate their team mates at the end of the quarter. Download and complete the peer evaluation form from D2L. It is due when the project is uploaded. The total points for all team members, including you, MUST equal 100. Project Requirements These are some things that should be included in the project. Depending on the type of project some things may not be necessary, hence this is a guideline. • • • • • • • • • • Functional and nonfunctional requirements Activity diagram(s) that shows how the business functions Overview use case diagram(s) Windows navigation diagram (WND) showing the GUI layout The design of each GUI GUIs should correspond to the WND Narrative describing the business process Work break down structure showing the activities of the project Make sure to clearly label each diagram and each part of the report NOTE: the report must be double spaced and well written; points will be deducted for poorly written 7 05/09/21 • • • • • • Document1 reports Project must have headings and subheadings Page numbers, table of contents identifying who worked on the various parts of the project Bibliography Deployment diagram Cover page Anything else that may be appropriate to your project The GUI’s should correspond with the WND starting from top to bottom and left to right so that it is straight forward and easy for the reader to make the connection between GUIs and WND. Use a numbering system to ensure a mapping between the two diagrams. The number on the WND item should be identical to the corresponding GUI. The report must be computer generated. Use any tool necessary (Visio, VB, HTML, Visual Studio, etc). To keep the project manageable, do not submit more than 20 GUIs. GUI’s should subscribe to the guidelines for good interface design and should include all the necessary information including buttons. Anything that takes away from the clarity, readability, layout, organization, structure, and completeness of the report will be penalized. Here is a list of things that may cause you to loose points: • • • • • • • • • • • • • not following instructions, poorly organized report, incomplete project, pages numbered incorrectly, missing table of contents or page numbers poor structure missing diagrams missing page numbers, diagrams and GUI’s missing labels, unrealistic and unreasonable business practices and assumptions criteria related to how HW will be graded, poor quality and so on. Late projects get zero. Therefore, if the project is incomplete submit before the deadline. However, students not pulling their weight can expect to receive a lower grade based on the peer evaluation forms. For example, if the work of a team member was below average of the team, their project grade will reflect that. This is an attempt to avoid free loaders. You are now warned! It is strongly suggested that one student take on the responsibility of the team leader. Plan the project schedule, start the project early, leave enough time for unforeseen circumstances and report review. Make sure to create backup copies of the report. All correspondence should be documented in email and keep a record of all email. Email records could be used to settle disputes between team members. If agreements are made by phone still send email to confirm the details of the conversation. 8 05/09/21 Document1 It is strongly suggested that you research the business to get a good understanding of what is required and that reasonable and realistic business practices and assumptions are followed. Research may include talking to people, using the web, reading and so on. Contract Agreement The agreement should include all team members and their responsibilities. All parties must sign the contract. All parties must keep a copy of the signed contract. Copy of contract must be uploaded to D2L. Contract criteria peer evaluation may include attending meetings, being on time, delivering items as planned, returning emails and phone calls in a timely manner, quality of work, and so on. Academic Misconduct The DePaul Student Handbook states: Violations of academic integrity include but are not limited to the following categories: cheating; plagiarism; fabrication; falsification or sabotage of research data; destruction or misuse of the university's academic resources-alteration or falsification of academic records; and academic misconduct. Conduct that is punishable under the Academic Integrity Policy could result in additional disciplinary actions by other university officials and possible civil or criminal prosecution. Full text located at http://condor.depaul.edu/~handbook/code17.html Attendance Students are expected to attend face-to-face, or online weekly Zoom sessions on time. If you are absent, you are responsible for the missing information and are encouraged to get it from fellow students. Missing a session is not an excuse for being uninformed about the class materials, assignments, due dates, and so on. Students are allowed to miss one session. Missing two or more session result in a 2% reduction per missed session, from your final grade unless you provide a doctor’s note. Example if you miss three classes and 4% will be deducted. Attendance sheet is circulated for every face-to-face class. It is the student’s responsibility to sign the sheet every class. I will keep an eye out for students who leave class early because additional penalties may apply. Virtual Lab for MAC students For the first time the University is experimenting with a virtual lab that provides access to software via the internet. No need to go to the lab to access Visio and project etc. You are one of three classes across the university to participate in the virtual lab experiment. To user the lab go to https://vlabs.is.depaul.edu. Before using the lab you need to download and install the Citrix Client called the Citrix Receiver from: http://www.citrix.com/English/ss/downloads/details.asp?downloadId=2319934&productId=1689163&ntref=cli entcenter Click on the grey download button on the right. Once the client is installed go to the lab, log in using your campus connect Id and password and use the software. Not all software available. http://www.citrix.com/English/ss/downloads/details.asp?downloadId=2319934&productId=1689163&ntref=cli entcenter For Mac users, an alternative to using Visio is to use creately.com UCD = Use Case Diagrams AD = Activity Diagram 9 05/09/21 Document1 See D2L for all due dates Date Topic Assignment Due 3/29 Intro to the Course Intro to Sys Analysis and Design Chap1 Project Management Chap 2 Requirements analysis Chap 3 Chap 2 (ignore pg 54 - end except for Timeboxing, and CASE Tools). 4/5 4/12 Readings on Business Processes (see three business process PDF chapters (10,11,12) in D2L) 4/19 Functional Modeling (AD, UCD) Chap 4 4/26 5/3 5/10 Structural Modeling Chap 5 Behavioral Modeling Chap 6 Human Computer Interaction Layer Chap 10 5/24 Physical Architecture Design Chap 11 Construction Chap 12 Installation Chap 13 Teams work on Project Teams work on Project 5/31 Teams work on Project 6/7 Exam covers (chap 1,2,3,4,5,6) activity and use case diags 5/17 Chap 3 (ignore pgs. 95 to the end except for JAD, Concept Maps & User Stories) Project Outline and Contract On-line Quiz (See D2L) on Business Processes HW: Activity Modeling HW: Use Case Modeling On-line Quiz Structural-behavioral (See D2L) On-line Quiz HCI-Phy Arch Design (see D2L) Project Due (see D2L) Exam (see D2L) THINGS YOU SHOULD KNOW AND REMEMBER NOTE: This page may be updated from time to time. The Text book is not perfect and so there are things in the book that I disagree with so I am letting you know what they are and what I expect of you in reference to all assignments and exams. When these things are missing from any assignment or exam (anything that is handed in or graded) you will lose points so it is important to have this list handy when doing assignments. 10 05/09/21 Document1 1. All activities must have input and output therefore all object nodes must be shown. The one exception is related to decision activities. The activity diagram book example has a mistake. We will discuss these issues and how to deal with them. If I happen to forget it is your responsibility to remind me. 2. Show all parts of a class (name, attributes, and methods). 3. Show return messages on sequence diagrams 4. Responsibilities of a class are the operations that the class can perform. It is not about the responsibilities of the actor. The book example is misleading so be aware of that. Remind me to discuss the book example. 11 05/09/21 Document1 This syllabus is subject to change at the discretion of the instructor. Students will be notified and are responsible for any changes that are announced in class or via the class web site. Changes to the syllabus are posted in red! MIS 360 Systems Analysis and Design Instructor: Dr. Grant Online Asynchronous: Office Hours: We have weekly “Ask Me Anything” Zoom session every Mon 6 pm CT Office: DPC 6023 email: dgrant2@depaul.edu Student Responsibilities Students are expected to be prepared for class. Students are expected to be on time for class. Students are expected to attend all class sessions and stay for the duration of class. Students are responsible for delivering assignments on time. Students are responsible for doing their fair share of work on group projects. Students are responsible for familiarizing themselves with the syllabus. Students are responsible for and staying abreast with any subsequent changes to the syllabus. Students are responsible for printing and carrying a copy of the syllabus. Students are responsible for providing pencil and eraser on exams or quizzes. Students are responsible for coming to class prepared. Students are responsible for signing the attendance sheet. Students should read the notes pertaining to the HW before attempting it. Students should do practice problems before attempting the HW. Students are responsible for knowing how to use Microsoft Visio 2003. See file on how to use it Students are responsible for any announcements made in class. Course and Behavioral Objectives: 1. Students should be proficient in the use of techniques, methods, and tools for analyzing and designing information systems. 2. Students should understanding the fundamental concepts of Systems Analysis and Design 2. Students should be able to analyze and design information systems using UML. 3. Students should be familiar with issues and problems encountered by systems analysts. Required Text: Systems Analysis and Design: An Object Oriented approach with UML Version 2.0, 5th Ed, by Dennis, Wixom, and Tegarden, Publ. Wiley, ISBN 978-1-118-80467-4 Supplemental Readings: Business Processes and Information Technology by Galinas, Sutton and Fedorowicz, Publ. Thompson Learning. The three chapters from this textbook each describes a business processes Chapter 10 Order to Cash, Part I; Chapter 11 Order to Cash, Part II; and Chapter 12 Purchase to Pay. The objective of the readings is to 1 05/09/21 Document1 enlighten you about important business processes that should find their way into your AD and UCD home work. Pay close attention to the horizontal flow activities, their inputs and outputs that make up each business process. The activities, inputs, and outputs are emphasized in the online quiz, so take notes when you read. You have about 4 days to complete it. Missing the due date earn you zero points. Chapter 12 Purchase to Pay (PtoP) Questions to focus on: Know the definitions of terms like, requisition, purchase order, accts receivables, accts payables, vendor packing slip, vendor invoice, and so on. What are the primary functions of the PtoP Process? What is the primary responsibility of the following depts. (accts payable, receiving dept, purchasing dept, inventory and so on) and the role that each manager of the dept plays? What are the horizontal info flows that make the process function properly (p. 425-425) and why are they needed? What are some of the sources of data used in the process and what is the importance of each data source. Try to identify as many data sources (data files). Also read p 438-439. Browse p 431-437. Chapter 10 read P. 328-331; Chapter 11 Billing Process read p. 387-388; read p. 375- 377 Know the definitions of terms like, bill of lading, packing slip, picking ticket, and so on. What are the primary functions of the Order to Cash process Visio is used to create diagrams. To learn it, go to LinkedIn Learning. All DePaul students have access to the site (DePaul login info is required). Employers expect MIS professional to be familiar with it, because it is the most widely used CASE tool. Grading Policy: Grades will be rounded two one decimal place. Therefore, 92.95 will become 93. 0 = A while 92.94 will become 92.9 = A-. Final course grade will be determined by: 1. Exam 30% 2. Assignments 35% (Proc 5%, AD 10%, UCD 10%, S&B Mod 5%, HCI-Phy 5%) 3. Project 35% To calculate your grade use this: .30*(exam grade/100) + .05*(proc grade/20) +.10*(AD grade/100) + .10*(UCD grade/100) + .05*(S&B grade/20) + .05*(HCI-Phy grade/20) + .35*(Proj grade/100) Score Grade Score Grade Score Grade 93 A 80 B66 D+ 90 A77 C+ 60 D 87 B+ 73 C < 60 F 83 B 70 C- 2 05/09/21 Document1 Quality of work: Getting an excellent grade requires high quality work. This includes, but is not limited to the following: • The use of paragraphs to express each main idea • The use of a spellchecker • No typos • Clear expression and organization of ideas • Supporting detail for main ideas • Thoroughness and completeness of the assignment Grading Expectations: This course is challenging for several reasons. First, the course requires the modeling of several business processes and in order to model a process one must understand it. Therefore, it is extremely important that you read up on business process and talk to people who perform them. If you do not have a thorough understanding of a business process, you will do a poor job modeling it. It is not recommended trying to model a process if you do not understand how it works. Second, UML is a language used to model business processes and like any language it has rules of syntax and semantics. Syntax is related to the symbols and how they are used to construct diagrams. Semantics have to do with the meaning that is conveyed to the user through the diagram. Therefore, for each assignment your grade will depend heavily on several factors including syntax, semantics, thoroughness of the process, completeness of the process, aesthetics, and the extent to which good business policy is reflected. Third, most undergraduate students lack business process knowledge and so for the first time they are forced to think in business terms and model the business process at the same time. This is not an easy task for most students; hence research and an understanding of the business are required to do well. Syntax: Points will be deducted for every syntax error. Semantics: Points will be deducted for every instance where the meaning is ambiguous. Thoroughness and completeness: points will be deducted if part of the business process is missing or incomplete. Aesthetics: This is related to how the diagram looks to the user. If the diagram is not appealing and turns off the user thus causing him to lose interest, then points will be lost. Therefore, avoid crisscross lines. Good business Policy: Good Business Policy should be reflected in the process if not points will be deducted. Good business policies involve business rules that would cause a business to thrive for a very long time and lend itself to high levels of customer satisfaction. How I Grade HW and other Assignments (grading philosophy): This section is intended to shed light on what to expect when I grade your work by incorporating more objectives measures in the grading process. It is clearly an attempt to remove as much subjectivity from the process. Grading often involves a measure of subjectivity, and the level of subjectivity varies with the topic and/or subject matter. In analysis and design it is impossible to remove subjectivity entirely because there is no single right or wrong answer to a given business problem. Some parts of a solution are naturally subjective; evaluating the aesthetic beauty or the semantic meaning of a diagram will always be subjective. Any business problem always has a range of possible solutions, some of which are clearly superior. My job is to determine the correctness of your solution and that is where my subject opinion and expertise play an important and inevitable role in the grading process. There are some parts of the grading process that lend themselves to more objective measures. I recognize that trying to be more objective has some limitations but I also recognize that moving to more objective measures has some merits. My intention is to incorporate more objective measures into the grading process. However, no matter what approach I use there are inherent 3 05/09/21 Document1 limitations, hence the approach taken here is definitely a compromise yet somewhat imperfect. The upside to adopting more objective measures is that students know ahead of time how they will be evaluated. When they receive their graded assignments, it would be clearer how they were graded especially on specific aspects of their solution. For example, every diagramming error will cost you a 2-point deduction (see list below). The downside to this approach is that some errors are more severe than others and I would have liked to reflect that in my grading. With this new approach that level of subjectivity is now removed by treating all errors as though they are equal. In reality, some errors are catastrophic while others are just insignificant. In my attempt to objectify the grading process the best I can, here is how you will be evaluated. On a 100 point scale, two points will be deducted for every syntax or semantic error identified. Therefore, if an error is repeated you will loose 2 points every time. Here is an incomplete list of errors: • • • • • • • • • • • • Crisscross lines that could be avoided Confusing situation Missing process, activity, use case, class, object, etc. Inappropriate or poor labeling Part of the diagram is missing when printed Missing titles on diagrams Instances of poor business policy reflected in the diagram. Therefore, it is very important to provide a list of assumptions with explanations when necessary If the homework consists of two diagrams and you hand in only one, you will be graded out of 50% Missing boundary Missing actors Actors misplaced; actors should always be on the outside of the diagram Syntax or semantic violations not listed above NOTE: 50 points will be deducted for submitting the wrong diagram. For example, submitting an overview use case diagram when the HW called for a detailed use case diagram. Please note that all the rules outlined here will be strictly enforced. To do 1. 2. 3. 4. 5. well on HW assignments, pay attention to these things: Pay attention to the list of errors above Spend a considerable amount of time researching and understanding the process before you model it Pay strict attention to the syntax Make sure each symbol of the diagram is correctly used and applied Do not try to create the diagram in one attempt; allow time to reread and improve the diagram over several iterations 6. Check for completeness of the diagram 7. Follow directions 8. Avoid crisscross lines when possible because they detract from the beauty of the diagram and create confusion for the user. As the amount of confusion increases the amount of semantics decreases. It is also possible to have no crisscross lines yet the diagram is confusing (low on semantics). Exams Homework and online quizzes provide the primary means of keeping students informed of their progress. Students should use them to judge their preparedness. The exam is comprised of 60 multiple choice questions, and two problems similar to the HW. Preparing for the exam should start the first week of class by doing the HW, quizzes, doing extra problems from the book, going over the review questions, studying 4 05/09/21 Document1 regularly, and so on. The multiple choice questions will cover basic definitions and terms from the text and is worth 1 point each. Missing HW, Quizzes, and Exams Students missing the deadline on quizzes, HW, exams, etc., are out of luck without a doctor’s note. This policy will be strictly enforced. Workload Students are advised to do all assignments, quizzes, etc. They provide the necessary practice to master the material. It is inconceivable students do well without expending sufficient effort and time practicing and studying. Students should plan on spending about 9 hrs per week outside of class. I strongly recommend that students working full-time should not take more than two classes and full-time students should not work more than 20 hrs. Students working full-time and going to school full-time is a recipe for poor performance. Home-Work Assignments All assignments must be done with the aid of the computer. All diagrams MUST be done using Visio and/or Word. When uploading assignments to D2Lmake sure the document is properly formatted and legible. Those who violate this policy will lose points because I can’t grade what I can’t see clearly or is confusing. Make sure to check D2L to ensure that you file was uploaded. Make sure you have enough time to upload your file and check to make sure it was uploaded on time. Forgetting to attach your file will not be considered an excuse for uploads. You have several days to deliver HW so late assignments get zero. Microsoft Visio is installed in Lewis on the 14th floor (1420). You can download a free copy of Microsoft Visio from Https://software.depaul.edu. Then select personal computers. 5 05/09/21 Document1 Then select Microsoft Azure Dev Tools for Teaching Sign in with your DePaul email, after sign in, select the download software button and scroll down to Visio.There is a view key button to the right (not shown here). Write it down you will need it to complete the install. There is no Visio for Mac users. They should access Visio through the Virtual Lab website: https://vlab.depaul.edu For Mac Users: Exporting from the Virtual Lab to your Word document. This article explains how to export a Visio diagram to a Word document: https://support.microsoft.com/en- 6 05/09/21 Document1 us/office/document-visio-process-diagrams-in-word-48073f4f-c6d4-4cc0-b9ae-3cb65e2ee158?ui=enus&rs=en-us&ad=us If you are using Apporto on your Mac. This article explains how to download the file from Apporto: https://www.apporto.com/helpcenter-enduser/uploading-a-file If you have trouble, please contact the TSC help desk 312 362 8765 for direct assistance. There will be NO second chance on HW assignments so make sure to do your best on each assignment. All up loaded files must include the sender’s name. Group Term Project The team project would be based on the Cohesion Case which can be found at www.cohesioncase.com. It is divided into several areas (ERP, CRM, SCM, Sys Dev, Networks and Telecom, E-business, etc). Each team will select a project topic by informing the instructor, on a first come basis. Click on the Cohesion Case Diagram link. Each of the above areas must have an Internet component. Term Project Outline Draft Project outline and contract should be uploaded to D2L by the third week but not later than week four. The project should include a cover page, table of contents with team member names attached, a short description of the business, and section headings. If there is any other item you would like to add feel free to do so. Team members must decide how the work is to be divided equally and fairly among team members. It is unfair and unequal for a student to work on a system request, problem definition, and/or project scope while others are responsible for AD, GUI, UCD, and other major pieces of work. Who is responsible for the various parts of the project must be in the form of a written contract. The contract must address penalties for team members who do not pull their weight. It must also address expectations of team members and each member must sign the document. Projects that do not have a contract will not be graded. Team members will evaluate their team mates at the end of the quarter. Download and complete the peer evaluation form from D2L. It is due when the project is uploaded. The total points for all team members, including you, MUST equal 100. Project Requirements These are some things that should be included in the project. Depending on the type of project some things may not be necessary, hence this is a guideline. • • • • • • • • • • Functional and nonfunctional requirements Activity diagram(s) that shows how the business functions Overview use case diagram(s) Windows navigation diagram (WND) showing the GUI layout The design of each GUI GUIs should correspond to the WND Narrative describing the business process Work break down structure showing the activities of the project Make sure to clearly label each diagram and each part of the report NOTE: the report must be double spaced and well written; points will be deducted for poorly written 7 05/09/21 • • • • • • Document1 reports Project must have headings and subheadings Page numbers, table of contents identifying who worked on the various parts of the project Bibliography Deployment diagram Cover page Anything else that may be appropriate to your project The GUI’s should correspond with the WND starting from top to bottom and left to right so that it is straight forward and easy for the reader to make the connection between GUIs and WND. Use a numbering system to ensure a mapping between the two diagrams. The number on the WND item should be identical to the corresponding GUI. The report must be computer generated. Use any tool necessary (Visio, VB, HTML, Visual Studio, etc). To keep the project manageable, do not submit more than 20 GUIs. GUI’s should subscribe to the guidelines for good interface design and should include all the necessary information including buttons. Anything that takes away from the clarity, readability, layout, organization, structure, and completeness of the report will be penalized. Here is a list of things that may cause you to loose points: • • • • • • • • • • • • • not following instructions, poorly organized report, incomplete project, pages numbered incorrectly, missing table of contents or page numbers poor structure missing diagrams missing page numbers, diagrams and GUI’s missing labels, unrealistic and unreasonable business practices and assumptions criteria related to how HW will be graded, poor quality and so on. Late projects get zero. Therefore, if the project is incomplete submit before the deadline. However, students not pulling their weight can expect to receive a lower grade based on the peer evaluation forms. For example, if the work of a team member was below average of the team, their project grade will reflect that. This is an attempt to avoid free loaders. You are now warned! It is strongly suggested that one student take on the responsibility of the team leader. Plan the project schedule, start the project early, leave enough time for unforeseen circumstances and report review. Make sure to create backup copies of the report. All correspondence should be documented in email and keep a record of all email. Email records could be used to settle disputes between team members. If agreements are made by phone still send email to confirm the details of the conversation. 8 05/09/21 Document1 It is strongly suggested that you research the business to get a good understanding of what is required and that reasonable and realistic business practices and assumptions are followed. Research may include talking to people, using the web, reading and so on. Contract Agreement The agreement should include all team members and their responsibilities. All parties must sign the contract. All parties must keep a copy of the signed contract. Copy of contract must be uploaded to D2L. Contract criteria peer evaluation may include attending meetings, being on time, delivering items as planned, returning emails and phone calls in a timely manner, quality of work, and so on. Academic Misconduct The DePaul Student Handbook states: Violations of academic integrity include but are not limited to the following categories: cheating; plagiarism; fabrication; falsification or sabotage of research data; destruction or misuse of the university's academic resources-alteration or falsification of academic records; and academic misconduct. Conduct that is punishable under the Academic Integrity Policy could result in additional disciplinary actions by other university officials and possible civil or criminal prosecution. Full text located at http://condor.depaul.edu/~handbook/code17.html Attendance Students are expected to attend face-to-face, or online weekly Zoom sessions on time. If you are absent, you are responsible for the missing information and are encouraged to get it from fellow students. Missing a session is not an excuse for being uninformed about the class materials, assignments, due dates, and so on. Students are allowed to miss one session. Missing two or more session result in a 2% reduction per missed session, from your final grade unless you provide a doctor’s note. Example if you miss three classes and 4% will be deducted. Attendance sheet is circulated for every face-to-face class. It is the student’s responsibility to sign the sheet every class. I will keep an eye out for students who leave class early because additional penalties may apply. Virtual Lab for MAC students For the first time the University is experimenting with a virtual lab that provides access to software via the internet. No need to go to the lab to access Visio and project etc. You are one of three classes across the university to participate in the virtual lab experiment. To user the lab go to https://vlabs.is.depaul.edu. Before using the lab you need to download and install the Citrix Client called the Citrix Receiver from: http://www.citrix.com/English/ss/downloads/details.asp?downloadId=2319934&productId=1689163&ntref=cli entcenter Click on the grey download button on the right. Once the client is installed go to the lab, log in using your campus connect Id and password and use the software. Not all software available. http://www.citrix.com/English/ss/downloads/details.asp?downloadId=2319934&productId=1689163&ntref=cli entcenter For Mac users, an alternative to using Visio is to use creately.com UCD = Use Case Diagrams AD = Activity Diagram 9 05/09/21 Document1 See D2L for all due dates Date Topic Assignment Due 3/29 Intro to the Course Intro to Sys Analysis and Design Chap1 Project Management Chap 2 Requirements analysis Chap 3 Chap 2 (ignore pg 54 - end except for Timeboxing, and CASE Tools). 4/5 4/12 Readings on Business Processes (see three business process PDF chapters (10,11,12) in D2L) 4/19 Functional Modeling (AD, UCD) Chap 4 4/26 5/3 5/10 Structural Modeling Chap 5 Behavioral Modeling Chap 6 Human Computer Interaction Layer Chap 10 5/24 Physical Architecture Design Chap 11 Construction Chap 12 Installation Chap 13 Teams work on Project Teams work on Project 5/31 Teams work on Project 6/7 Exam covers (chap 1,2,3,4,5,6) activity and use case diags 5/17 Chap 3 (ignore pgs. 95 to the end except for JAD, Concept Maps & User Stories) Project Outline and Contract On-line Quiz (See D2L) on Business Processes HW: Activity Modeling HW: Use Case Modeling On-line Quiz Structural-behavioral (See D2L) On-line Quiz HCI-Phy Arch Design (see D2L) Project Due (see D2L) Exam (see D2L) THINGS YOU SHOULD KNOW AND REMEMBER NOTE: This page may be updated from time to time. The Text book is not perfect and so there are things in the book that I disagree with so I am letting you know what they are and what I expect of you in reference to all assignments and exams. When these things are missing from any assignment or exam (anything that is handed in or graded) you will lose points so it is important to have this list handy when doing assignments. 10 05/09/21 Document1 1. All activities must have input and output therefore all object nodes must be shown. The one exception is related to decision activities. The activity diagram book example has a mistake. We will discuss these issues and how to deal with them. If I happen to forget it is your responsibility to remind me. 2. Show all parts of a class (name, attributes, and methods). 3. Show return messages on sequence diagrams 4. Responsibilities of a class are the operations that the class can perform. It is not about the responsibilities of the actor. The book example is misleading so be aware of that. Remind me to discuss the book example. 11 Use case overview ************************** 1.Generalized admin, customer and agent with system user. (System user is the parent actor which has all the common use cases) Specific use cases are connected to the relevant actors. 2. Connected admin to all the specific cases relevant. 3. for agent/retailer, it should be rent out not just rent. 4. Added reserve and renew cases to the customer. Backend ************************ 1. Generalized customer with the system user 2. Maintain customer use case should be added only to Management. Removed it from the customer. 3. Added register use case. 4. Rent/ return items use cases should only be given to Customer 5. Added Verify Transaction/ Credit Card Details use case to the credit card payment system. 6. No need to put include between file operations and maintain inventory. Frontend ************************ 1. Added register use case 2. Added delete account 3. For renew and reserve cases, added include case to update details. 4. Check out DVD - added enter payment details case Notenia delarmat View Help Usecase 1. Generalized admin, customer and agent with system user. (System user is the parent actor which has all the common use cases) Specific use cases are connected to the relevant actors. 2. Connected admin to all the specific cases relavent. 3. for agent/retailer, it should be rent out not just rent. 4. Added reserve and renew cases to the customer. Backend 1. Generalized customer with the system user 2. Maintain customer use case should be added only to Management. Removed it from the customer. 3. Added register use case. 4. Rent/ return items use cases should only be given to Customer 5. Added Verify Transaction/ Credit Card Details use case to the credit card payment system. 6. No need to put include between file operations and maintain inventory. Frontend ***** 1. Added register usecase 2. Added delete account 3. For renew and reserve cases, added include case to update details. 4. Check out DVD - added enter payment details case Notenia delarmat View Help Usecase 1. Generalized admin, customer and agent with system user. (System user is the parent actor which has all the common use cases) Specific use cases are connected to the relevant actors. 2. Connected admin to all the specific cases relavent. 3. for agent/retailer, it should be rent out not just rent. 4. Added reserve and renew cases to the customer. Backend 1. Generalized customer with the system user 2. Maintain customer use case should be added only to Management. Removed it from the customer. 3. Added register use case. 4. Rent/ return items use cases should only be given to Customer 5. Added Verify Transaction/ Credit Card Details use case to the credit card payment system. 6. No need to put include between file operations and maintain inventory. Frontend ***** 1. Added register usecase 2. Added delete account 3. For renew and reserve cases, added include case to update details. 4. Check out DVD - added enter payment details case