ASAP
MITS5501 Assignment 2 MITS5501 Software Quality, Change Management and Testing Case Study Assignment MITS5501 Assignment 2 Copyright © 2015-2018 VIT, All Rights Reserved. 2 NOTE: This Document is used in conjunction with MITS5501 Case Study document [MITS5501- CaseStudy.doc] Objective(s) This assessment item relates to the unit learning outcomes as in the unit descriptor. This assessment is designed to improve student collaborative skills in a team environment and to give students experience in developing Quality Assurance documents including the Quality Plan, Test Plans and Test Cases using a simulated industry case study INSTRUCTIONS Case Study Assignment - 25% (week 12) In this assignment students will work in small groups to develop components of the Quality Assurance documents discussed in lectures. Student groups should be formed by Session four. Each group needs to complete the group participation form attached to the end of this document. Carefully read the associated CASE STUDY for this assignment contained in the document MITS5501-CaseStudy.doc From this Case Study you are to prepare the following documents: 1. Quality Assurance Plan 2. Test Plan 3. Test Cases (9 per group) 4. Project Scope Statement 5. Perform a Test Effort Estimation (include Tables and calculations used) 6. Test Strategy Document 7. Project Completion Checklist The above list of documents is not necessarily in any order. The chronological order we cover these topics in lectures is not meant to dictate the order in which you collate these into one coherent document for your assignment. MITS5501 Assignment 2 Copyright © 2015-2018 VIT, All Rights Reserved. 3 What to Submit. Your Assignment document containing the above documents is to be compiled into one word document Your report should use 1.5 spacing with a 12 point Times New Roman font. Include references where appropriate. Citation of sources is mandatory and must be in the Harvard style. Your report must include a Title Page with the title of the Assignment and the name and ID numbers of all group members. A contents page showing page numbers and titles of all major sections of the report. All Figures included must have captions and Figure numbers and be referenced within the document. Captions for figures placed below the figure, captions for tables placed above the table. Include a footer with the page number. Submit your document in a file named MIST5501CaseStudy.doc by the due date and time. MITS5501 Assignment 2 Group Participation Form This form is to be completed by the group and returned to your tutor/lecturer as soon as possible. We, the undersigned, agree to contribute individually and as a team to complete the Group Assignment for MITS5501 Software Quality, Change Management and Testing in the time specified. (It should be noted that failure to participate in a group may result in a fail for the assignment component of the subject.) Group membership: Surname First name Student ID Date Signature 1. ______________________ ___________________ __________ ___/___/___ _______________________ 2. ______________________ ___________________ __________ ___/___/___ _______________________ 3. ______________________ ___________________ __________ ___/___/____ _______________________ * All members in the team will receive the same mark for an assignment, unless there are extenuating circumstances whereby an individual’s mark has to be altered by the tutor/lecturer, or if the peer group assessment warrants it. ** Team members should contact their tutor/lecturer immediately if problems arise within the team that may cause completion of an assignment to be severely delayed, or the quality of the submission to be substantially lowered. MITS5501 Software Quality, Change Management and Testing CASE STUDY MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 2 Software Requirement Specification (SRS) Investment Management System 1. Introduction 1.1 Purpose The Investment Management System (IMS) is intended to help the user keep account of their money invested in institutions such as Banks and Share Market. This document is meant to delineate the features of IMS, so as to serve as a guide to the developers on one hand and a software validation document for the prospective client on the other. 1.2 Scope: We describe what features are in the scope of the software and what are not in the scope of the software to be developed. In Scope: a. Managing investment of a single user, which would include maintaining bookkeeping information about entities like Portfolio, Security, and Transaction. b. Computation of Net-Worth and Rate of Investment (ROI) of the Investor. c. Giving alerts to the user, if he requests for one. d. Downloading the current prices of shares from the web. e. User authentication. Out of Scope: a. Features for actual purchasing and selling of securities. That is, actually buying and selling of shares/securities is done outside IMS. b. Tax computations for gains/losses. c. Any market related prediction. MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 3 1.3 Definitions, Acronyms, and Abbreviations: Acronyms and Abbreviations: a. IMS: Personal Investment Management System. b. SRS: Software Requirements Specification. c. WWW: World Wide Web. d. GUI: Graphical User Interface. e. ROI: Rate of Investment. Definitions: a. Transaction: A real event that involves flow of personal money. In the context of shares, it is buying/selling a group of shares of the same company, and in context of Bank it is deposit/withdrawal of money to/from one’s account. b. Security: A set of all transactions pertaining to a company share or a bank account. c. Portfolio: A set of Securities. d. Net-Worth: The sum total of all the money of the investor in form of shares and bank balances. e. ROI: The interest that user gets on a particular investment. In the context of a bank account it is the annual interest and in case of a company share it is defined as given in appendix A: 1.4 References: Appendix A: Formula for ROI calculation for shares. Appendix B: Formula for Net-Worth calculation. Appendix C: User Screens. 1.5 Overview: The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed. Section 3 gives specific requirements which the software is expected to deliver. Functional requirements are given by various use cases. Some performance requirements and design constraints are also given. Section 4 gives some possible future extensions of the system. Finally, the appendices in Section 5 describe respectively the formula for ROI calculation for shares and user screen. MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 4 2. Overall Description: 2.1 Product Perspective: IMS is aimed toward a person who has considerable number of investments in stock market and banks, and so needs software assistance for book keeping and computations regarding the investments. IMS should be user-friendly, ‘quick to learn’ and reliable software for the above purpose. IMS is intended to be a stand-alone product and should not depend on the availability of other software. It should run on both UNIX and Windows based platform. 2.2 Product Functions: IMS should support the following use cases: Class of Use Case Use Case Use Case Description Use case related to Installation Installation Creates and initializes working files Uses cases related to system authorization Login Login to IMS Change Password Change IMS password Use cases related to portfolios Create Portfolio Creates a new portfolio Rename Portfolio Rename an existing portfolio Delete Portfolio Delete an existing portfolio Use cases related to securities Create security Create a new security in a given portfolio Rename Security Renames an existing security Delete Security Deletes an existing security Use cases related to transactions Add Transaction Add a transaction to a security Edit Transaction Edit an existing transaction Delete Transaction Delete an existing transaction Use cases related to information display Display Investment Display information of the entire investment Display Portfolio Display information about a given portfolio Display Security Display information about a given security Use cases related to computation Compute net-worth Compute net-worth of investment/ portfolio/ security Compute ROI Compute ROI of a given security Use cases related to share prices Get current share Price Download the current share price from the net Edit Share price Edit the price of a share already present in the list Use cases related to alerts Set alerts Set alert giving date and details Show alerts Show all the pending alerts Delete alerts Delete an already set alert MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 5 2.3 User Characteristics: a. The user should be familiar with the Investment Management related terminology like Portfolio/Security/Transaction. b. The user should know the details of a transaction. 2.4 Principal Actors The two principal actors in IMS are “user” and “system”. 2.5 General Constraints: a. For full working IMS requires Internet connection. b. IMS is single-user software. 2.6 Assumptions and Dependencies: a. Full working of IMS is dependent on the availability of Internet connection. b. The downloading of share prices in IMS is customized to www.asx.com.au. IMS would not work for any other website. c. The company shares registered in the Australian Stock Exchange (ASX) are only considered by IMS. 3. Specific Requirements: 3.1 Functional Requirements: We describe the functional requirements by giving various use cases. Use case related to installation: Use Case 1: Installation Primary Actor: User Pre Condition: Internet connection available. Main Scenario : 1. User initiates IMS installation program. MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 6 2. System asks the user for the home directory in which all the working files will be created. User is also asked for the initial login and password. 3. User specifies the home directory and login/password. 4. System creates the working files