Case Studies for introduction to system analysis The case where you name is listed as the analyst is your case for both the first and second assessment submissions. Owners, are the business and system owners for the purposes of assessment one. Owners are to provide the major input and feedback to the case where they are listed as owner. Due to time constraints it is not expected that users for a case will have major input or need to give major feedback to the analyst. Of course, you may like to join in the discussions and this is not precluded. It is good peer support. Group members are to inform their tutor about non-responsive students and the tutor will discuss actions that can then occur. Please note while the length of the case studies varies they all have around the same level of complexity. Do not underestimate the levels of complexity. Please note that “real” systems may not behave this way, some simplifications have been made to ensure that none of the case studies are too complex. While you are asked to list your assumptions, you may not make assumptions that over simplify the case study. It is expected that all cases and the resulting systems will have variations. This will be due to your owner and user input. Case A: Magazine Analyst Name (your case study to analyse): Deepak Owner Name (business owner responsible for major feedback to the analyst): Dipesh Other users’ names for minor feedback: Dipesh The magazine wants to develop an information system for supporting a set of business activities: subscriptions, advertising, editorial (managing contributions), distribution, payables, receivables, etc. This is the subscription side of the business. The owner will determine the name and type of magazine. Note: these must be appropriate in line with University expectations. The owner will provide the main details for the system based on the following with users providing additional peer input. The magazine is published ______ (e.g. quarterly, monthly, weekly). Target audience (demographics of the audience) Content (e.g. type of articles; authors’ and contributors’ demographics; advertiser demographics’ and input) This is mainly a subscription magazine. Up until now it has been a print magazine with one year subscriptions. However, the magazine wishes to diversify with online and/or print subscriptions with various lengths of subscriptions with varied discounts and offers. The magazine is also sold by select newsagencies. Renewals need to be handled by the system. Two months before the expiry of the subscription, a notice needs to be send to the subscriber. Subscribers are reminded up to three times. Payment can be made by credit card or bank deposit. The owner would like to know if other methods like PayPal should also be used. It is envisioned that the new systems will allow subscribers to renew via a website that is easy to use and secure. Contributors receive may receive up to a one-year complimentary subscription to the magazine. For example, people who are interviewed that are not paid for their interview receive a copy of the magazine containing their interview. Writers may receive a one-year subscription for two articles. Details to be stored about contributors: • maintain name, address and contact details; • maintain type of contribution, the dates, the payments and complimentary subscription type; • record which staff are working with which contributor; • track the status of each contribution. The owners expect to be able to run reports such as subscriber demographics, contribution status, and subscribers that have not renewed. ISYS215 Introduction to Systems Analysis Assignment One Due Date Monday 2 April 2017 at 9:00 (am) Individual work with a peer component 15% of the total marks for the semester Marking Rubric attached to Unit Outline An important part of being a good systems analyst is the ability to communicate and to define the correct requirements. For this assignment you are going to collect and model the requirements for a small information system. You will also act as a user for your peers in a small group. We will set up small groups, each student will be allocated a different scenario and for that scenario you will be the systems analyst. You will be a user for the other students in the group for their scenarios. Students can meet face to face, but must also enter their discussions on the group discussion forum. This way there will be a record of the advice given to the users and what the users give the analyst. These discussions will be marked and are worth 6 percent of the marks for the semester. See the rubric. So as you can see, you will be assessed on your practical work, but also for your explanations and assistance to your peers. Postings must be timely to allow fellow group members the chance to respond. Should your colleagues not be cooperative in your group, tutors will mark your participation on the other class forums. This should not be necessary, but this means no student should have reason to state that they lost marks due to others’ non-responsiveness. This also means that all forums for this unit are important. Groups will be three students with some groups of four if required. You may nominate a group in the first two weeks. However, if you have not sent you nomination as a group to your tutor by the end of week 2, you will be placed in a group. A discussion forum will be set up for your group to use. Starting case studies will be randomly assigned to group members by the tutor. Because you have a different case study from your fellow group members, you will be able ask for assistance from your colleagues just as you would ask a user and you will be able to explain your diagrams to them, just as would occur in a workplace. Please note: there should be no assignments that are submitted that are very similar and if there are these will be treated as plagiarism. As the systems analyst, for the first assignment you will need to start the requirements modelling process for your case study. In Assignment Two, you will complete it. Before you start you will need to be familiar with the UML case tool and in particular how to draw a Use Case Diagram. Files to be submitted by each person for their allocated system (note a to e will be a Word file): a. A list of stakeholders for your system b. A list of the system requirements (functional and non-functional requirements see page 45 of your text) that you have identified so far c. Use Case Stories d. Use Cases with brief descriptions (table) e. List of any assumptions made regarding the case study and why f. Use Case diagrams (UML modelling tool file). Assessment task 1: Assignment Submission 1 Weighting: 15 % Length and/or format: For submission of tasks such as a System Vision document use MS Word or equivalent; for modelling diagrams a file produced using the specified UML modelling software will be required. Purpose: Develop professional skills through the application of theoretical knowledge and understanding. Assessment criteria: Quality of work in meeting the unit’s learning objectives as further defined in the attached rubric. REFERENCING PFBS: This Unit requires you to use the Harvard referencing system Rubric – Assessment Tasks 1 Assignment Submission ILOs Criteria Standards Below Expectations Meets Expectations Exceeds Expectations Level 1 (e.g. NN) Level 2 (e.g. PA) Level 3 (e.g. CR) Level 4 (e.g. DI) Level 5 (e.g. HD) 3 and 5 Task 1 – 3 marks Completeness of the requirements with justifications Minimal proposed system requirements or the majority of the system requirements would not meet the users’ needs. No referencing. Analysed and discussed proposed system requirements, with respect to the majority of the user needs. Justifications were included for requirements. Documentation is adequate and referenced, with most arguments linked to the case. Clearly analysed and discussed proposed system requirements, with respect to user needs (only one or two missing). Clear justifications were included for requirements. Documentation is adequate and referenced, with arguments linked to the case. Critically analysed and discussed proposed system requirements, with respect to user needs. Clear justifications were included for requirements. Documentation is substantive and well referenced, with arguments linked to the case. Critically analysed and discussed proposed system requirements, with respect to user needs. Insightfully articulated the justifications. Documentation is substantive and well-referenced, with arguments clearly grounded in the case. 1 Task 1 – 6 marks Demonstrated ability to help users evaluate requirements. Little or no assistance to peers as outlined in the assignment requirements Demonstrated timely relevant and constructive assistance to peers for most attempts as outlined in the assignment requirements Demonstrated timely, relevant and constructive assistance to peers as outlined in the assignment requirements Demonstrated active, timely, relevant and constructive assistance to peers as outlined in the assignment requirements A very high level of demonstrated active, timely, relevant and constructive assistance to peers as outlined in the assignment requirements 4 Task 1 – 3 marks Demonstrated understanding of the use of the software Demonstrated little understanding of the use of the software/ did not use the nominated software Demonstrated use of the majority of the required features with some errors. Demonstrated use of the majority of the required features with only minor errors. Demonstrated use of all of required features with only minor errors. Demonstrated use of all of required features with no errors. 3 and 5 Task 1 – 3 marks Correctness of the diagramming/modelling Demonstrated little of understanding of using the required diagramming techniques which resulted in many errors. Demonstrated a good understanding of the required diagramming techniques with a few major errors. Demonstrated a good understanding of the required diagramming techniques with a few minor errors. Demonstrated an excellent understanding of the required diagramming techniques with a major error or a few minor errors. Demonstrated an excellent understanding of the required diagramming techniques