MITS5501 Software Quality, Change Management and Testing CASE STUDY MITS5501 Case Study Copyright © XXXXXXXXXXVIT, All Rights Reserved. 2 Software Requirement Specification (SRS) Investment Management...

1 answer below »
complete my assignment in time and submit my deadline


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 in the specified home directory. Working files contain: a. Authorization information. b. List of company names. c. Current share prices. d. Investment structure. 5. System downloads the list of companies (registered in ASX, from www.asx.com.au) and the current share prices. It initializes the files containing the list of companies and the current share prices with the downloaded data. Alternate Scenario: 5(a). Network failure. 5(a)1. Installation aborted. Use cases related to system authorization: Use Case 2: Login Primary Actor: User Pre Condition: Nil Main Scenario : 1. Start the application. User prompted for login and password. 2. User gives the login and password. 3. System does authentication. 4. Main screen is displayed. Alternate Scenario : MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 7 4(a). Authorization fails 4(a)1. Prompt the user that he typed the wrong password 4(a)2. Allow him to re-enter the password. Give him 3 chances. Use Case 3: Change Password Primary Actor: User Pre Condition: User logged in Main Scenario : 1. User initiates the password change command. 2. User is prompted for old password, new password and confirm new password. 3. User gives the old password, new password and confirm new password. 4. System does authentication. 5. New password is registered with the system. Alternate Scenario : 4(a). Authorization fails 4(a)1. Prompt the user that he typed the wrong password 4(a)2. Allow him to re-enter the password. Give him 3 chances. 4(b). New password and confirm new password do not match. 4(b)1. Allow him to re-enter the attributes. Give 3 chances. MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 8 Use cases related to portfolios: Use Case 4: Create Portfolio Primary Actor: User Pre Condition: User logged in. Main Scenario: 1. User initiates the “create portfolio” functionality. 2. System asks the user for the portfolio name. 3. User enters the portfolio name. 4. An empty portfolio is created. Alternate Scenario: 4(a). Portfolio with the same name exists. 4(a)1. System asks the user for a different name. 4(a)2. User enters a different name. 4(a)3. Empty portfolio gets created. Use Case 5: Rename portfolio. Primary Actor: User Pre-Condition: User logged in. Main Scenario : 1. User initiates the “rename portfolio” functionality. 2. System asks for the portfolio to be renamed and the new name. 3. User enters the new name. 4. Portfolio is renamed. Alternate Scenario: MITS5501 Case Study Copyright © 2015-2018 VIT, All Rights Reserved. 9 4(a). The portfolio whose name is supposed to change does not exist. 4(a)1. Renaming fails, the error message is displayed. 4(b). Portfolio with the same new name exists. 4(b)1. Renaming fails, the error message is displayed. Use Case 6: Delete portfolio. Primary Actor: User Pre-Condition: User logged in. Main Scenario : 1. User initiates the ”delete portfolio” functionality. 2. System asks for the name of the portfolio. 3. The portfolio is deleted. Alternate Scenario: 3(a). Portfolio does not exist. 3(a)1. Deletion fails, error message is displayed. Use cases related to securities: Use Case 7: Create a security. Primary Actor: User Pre-Condition: User logged in.
Answered Same DayJun 03, 2021MITS5501

Answer To: MITS5501 Software Quality, Change Management and Testing CASE STUDY MITS5501 Case Study Copyright ©...

Amit answered on Jun 05 2021
162 Votes
Title of the assignment: Software quality, change management and testing
Student name:
Student ID:
Professor’s name:
Course title: MITS 5501(Assignment – 2)
Date: 6/5/2019
Table of Contents
1.    Quality assurance plan for IMS (Investment management system)    3
2.    Test plan for IMS    4
3.    Possible test cases for IMS    5
4.    Scope statement for IMS project    15
5.    Estimation of testing effort for IMS project    16
6.    Document defining testing strategy for IMS project    18
7.    Checklist of project completion    19
8.    References:    20
1. Quality assurance plan for IMS (Investment management system)
The assurance of quality for maintain the stocks and other investments is most important. The QAP define
s the scope, purposes, objectives behind maintining quality, responsibilities of different stakeholders, test plan and followed guidelines with implementation standards [1, 2]. The developed QAP for this IMS system is presented below:
    Objective
    Activity
    Indicator
    Used tool
    Responsible person
    Status
    Improve the processes of IMS.
    Research requirements and develop application based on them.
    Output: stakeholder involvement.
Output: processed all requirements.
    Requirement evalution form.
    Requirement analyst.
    Completed.
    Maintain budget for required efficiency.
    
    Actual costing,
Capital
    Tracking tools for budget.
    Project manager
    In process.
    Maintaining planning time frame.
    
    Timely delivery
    Work plan and activity diary
    Project manager
    In process
    Maintaining scope and staying with it.
    
    Meeting the objectives.
    Project partners.
    PM
    In process.
    Following the set guidelines for IMS.
    
    Working as per feedback.
    Evaluation guidelines.
    Project manager.
    Completed.
Table 1: QAP for IMS application
2. Test plan for IMS
The test plan is mostly developed for defining the test cases for maintaining the quality and accuracy of application [2]. The developed test plan for this IMS application is provided below:
    Sr. No.
    Tested features of IMS
    Not tested features of IMS
    Testing environment
    1.
    The authentication for all users to IMS system must be tested.
    Different many users can use the IMS application to update stock prices at same time, so, load testing can be ignored.
    The testing environment with different involved users is set.
    2.
    The updating and deletion of user portfolio is tested.
    The behavior of IMS for updating and deletion of user portfolio is ignored.
    The testing environment with different involved users is set.
    3.
    Security of user portfolio in IMS is must be tested.
    The testing of security tools in different environment of UNIX and windows can be ignored.
    Security of portfolio is tested with different created attacks.
    4.
    The occurrences of financial transactions of investments done by users are properly tested.
    The repeated transactions for same portfolio can be ignored.
    This testing is performed in client environment.
    5.
    The testing for allowing users to display and print required portfolio information is tested.
    The testing of background printing can be ignored.
    This testing is performed in client environment.
    6.
    The testing of computation of net-worth and ROI is done properly with set formulas is tested.
    The testing of remaining calculations for user portfolio is not done.
    This testing is performed in client environment.
    7.
    The testing of updating of share prices from internet resources is also done.
    The testing of shares outside IMS is not done.
    This testing is performed in developer environment.
    8.
    The testing of possible alerts provided to user using IMS is also done.
    This testing only test alerts not the reason behind them.
    This testing is performed in developer environment.
    9.
    The testing of installation of IMS is also done.
    This testing is done only for UNIX and WINDOWS operating system, not for other open operating systems.
    This testing is performed in developer environment.
Table 2: test plan for IMS application
3. Possible test cases for IMS
The test cases plays the most important and critical role in execution of any test plan. As IMS is involving financial transactions based on the market values, so, all possible test cases must b developed and defined [3]. The test cases for IMS application involves following points:
1. Is authentication is maintained for all users?
2. Is user is able to update or delete any created portfolio in IMS?
3. Is security is considered as primary requirement for all portfolios in IMS?
4. Is financial transactions of investments by users are properly maintained?
5. Is user is able to display and print required portfolio information?
6. Is the computation of net worth and ROI is done properly with set formulas?
7. Is updating of share prices from internet resources are maintained in IMS?
8. Is possible alerts are provided to user for using IMS?
9. Is the installation is providing easy setup for IMS application?
Based on these test cases, the required quality and accuracy can be maintained in the IMS application for different portfolios. The detailed explanation of these test cases is provided below:
Test case 1 description:
    Test case name:
    The authentication is maintained for all users.
    Description:
    The user provides login details to use services for IMS application. User can change set password for his / her portfolio. IMS system allows authorized users to access their portfolio. Users can perform all required transaction in their portfolio.
    Trigger events:
    The user authentication maintaining events are executed with this test case.
    Test Description:
    1. The user provides login details to use services for IMS application.
2. User can change set password for his / her portfolio.
3. IMS system allows authorized users to access their portfolio.
4. Users can perform all required transaction in their portfolio.
    Actors:
    1. Client
2. IMS system.
    Pre condition:
    Each user must have to make login to IMS application for managing the investments and their portfolios.
    Activity Flow: client
    1. The user provides login details to use services for IMS application.
2. User can change set password for his / her portfolio.
    Activity flow: Administrator
    The administrator of IMS application can reject login for unauthorized users.
    Exception Condition:
    The user authentication is essential for using the services of IMS application.
Test case 2 description:
    Test case name:
    The user is able to update or delete any created portfolio in IMS.
    Description:
    The user provides login details to use services for IMS application. The authorized users for IMS system can change their portfolio. User can create, delete and update their portfolio. System saves the updates in its database.
    Trigger events:
    The portfolio change events are executed in this test case.
    Test Description:
    1. The user provides...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here