Fluent Essays

Project rollout begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project rollout process comprises specific steps that must be scheduled carefully to enable the project to hit production deadlines and meet business expectations. For this assignment, you will create an implementation project plan, which outlines the steps involved in implementing your project. This document is sometimes called a work-back schedule because you begin with the date that your project needs to go live, and then work back from there to determine what needs to be done when. You will also conduct a post-mortem on the work you have submitted to date. Post-mortem (from the Latin for “after death,” but referring to it in the context of business) is the analysis of a project’s process and results conducted by key project stakeholders after the project has been moved into production, which means it’s functionally complete. The goal of a post-mortem is to identify what went right and what went wrong post-implementation so that project managers can apply these lessons learned to future projects. For this three-part assignment, you will: Construct a work-back schedule that presents the steps involved in implementing your project. Construct a post-mortem using the template on the work you have submitted to date in this course. Create updated project documents based on the results of your post-mortem. Review the Project Implementation Plan Example. Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software to create your project implementation plan. Complete the Post-Mortem template based on your experiences with completing the course project over the last five weeks. Update the project documents you have submitted thus far in the course based on your completed post-mortem. Submit your project implementation plan, post-mortem, and updated project documents. BSA/425 v1.3 Post-Mortem BSA/425 v1.3 Page 2 of 2 Post-Mortem Use the table to list the things that went well during the completion of this 5-week project and the things that didn’t go well. Date: Project Manager (your name): Project Name: 5 Things that Went Well During the Project 5 Things that Could Have Been Done Better Below, discuss all 10 things from the list above in detail. As a project manager, or participant, what processes might you put in place to ensure the same things go well on future projects you’re involved in? What processes can you put in place to improve the not-so-great things on future projects? Be specific. Copyright 2020 by University of Phoenix. All rights reserved. Copyright 2020 by University of Phoenix. All rights reserved. BSA/425 v1.3 Project Implementation Plan Example BSA/425 v1.3 Page 2 of 2 Project Implementation Plan Example Replace the italicized information with information relevant to your project. Project Name: Implementation Phase: Project Plan: Task Activity Name Resource Schedule Start Date Schedule Finish Date Schedule Comments Prepare for Implementation Identify the implementation team CIO/Project Sponsor 6/4/2018 6/8/2018 Order server hardware for production environment and test/QA environment IT Manager/CIO 6/4/2018 6/29/2018 Order client hardware for production environment and test/QA environment IT Manager/CIO 6/4/2018 6/29/2018 Order Cloud Computing Services and software subscriptions IT Manager/CIO 6/4/2018 6/29/2018 Obtain on premise software applications IT Manager/CIO 6/4/2018 6/29/2018 Create user IDs and groups for on premise technology System Admin 7/2/2018 7/13/2018 Create security infrastructure for production and test/QA environment System Admin 7/2/2018 7/13/2018 Prepare Test Environment Install test/QA servers and software System Admin 7/16/2018 7/20/2018 Install test/QA client machines and software System Admin 7/16/2018 7/20/2018 Configure test/QA environment System Admin 7/16/2018 7/20/2018 Prepare Production Environment Install production servers and software System Admin 7/23/2018 7/27/2018 Install production client machines and software System Admin 7/23/2018 7/27/2018 Configure production environment/ integrate with cloud service architecture System Admin 7/23/2018 7/27/2018 Data Conversions Perform data conversions and loading into the test/QA environment Data Specialists 7/13/2018 8/10/2018 Perform data conversions and loading into the production environment Data Specialists 7/13/2018 8/10/2018 Documentation Ensure all documentation applicable to implementation is available Documentation Specialists/Technical Writers 6/11/2018 8/17/2018 Training Provide administrator training Trainers 8/13/2018 8/17/2018 Provide support training Trainers 8/13/2018 8/17/2018 Provide end-user training Trainers 8/13/2018 8/17/2018 Go-Live Production Go-live CIO/Project Sponsor 8/27/2018 8/27/2018 Copyright 2020 by University of Phoenix. All rights reserved. Copyright 2020 by University of Phoenix. All rights reserved. BSA/425 v1.3 Project Plan Draft BSA/425 v1.3 Page 9 of 9 Project Plan Draft Fill out each of the sections below with information relevant to your project. Be sure to include the company name associated with your project. Company Name: XYZ Bank Network Technology Recommendations Network Technology Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points IN a Scale of 10) LAN It connects a number of computers or low-voltage devices across a short distance. 5 WAN Long distance computer connection 5 WLAN Does not require the physical devices as it operate like Wi-Fi 8 Network Technology Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Cisco Very fast, best customer service Expensive Heavy network in the organization 9 Alloys Cheap, better customer service Poor network Encryption of user data 5 Aruba Cheap, superb network Poor network Software for organizational services 4 Network Technology Deployment Challenges Deployment Challenge Deployment Challenge Description Physical vs logical deployment The appliances in physical networks are connected via protocols, but in logical networks, other traffics are used which are indifferent to physical networks and must be run. Scalability and automatic deployment Not only must the networks be automated, but they must also be scalable. Bringing separate own network When installing a network in a data center architecture, an automated and quicker deployment is preferable. Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed technology must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed technology Training of employees Organization employees’ needs be trained on the internet and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Increase the number of employees $3000 High productivity Construction of new block $50000 Installation of the proposed system and components Database System Recommendation Database System Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Terms of reference definition The purpose of the project 5 Products shortlisting Selecting the best database management system (DBMS) 8 Products evaluation Thorough analysis of the selected DBMS 4 Recommendation Findings and analysis of the right organization 9 Database System Recommendation Recommended Database System Description Benefits Aggregate Selection Criteria Score Desktop Entering and logical storage of user data High speed in data processing 4 Relational Tables arranged in schemas in a particular server Storage of multiple data 5 Normalization Processing and breaking up of data Ais in sorting of database documents based on defined criteria 7 Database System Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Cost Cost effectiveness must be considered 5 Security Data must be well protected from attacks 9 Convenience Data must be utilized without previous errors 7 Database System Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Oracle Support cloud services, very powerful N/A Cloud database management as well as employee training 8 Microsoft SQL Widely used globally N/A Easily integrated with Microsoft products such as Word, Excel etc 6 Database System Deployment Challenges Deployment Challenge Deployment Challenge Description Data and information security Currently there are numerous cyber security attacks Performance The performance of the system can face issues Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed database must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed database technology Training of employees Organization employees’ needs be trained on the database management and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Purchase of the new database system $5000 It will assist the firm in better storing and retrieving its expanding volumes of data. Software Application Recommendations Software Application Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Industry and business expertise This is the proportion of employees having IT expertise in the firm. 8 Program management The program and project must be complicated, and the organization must be competent to handle it. 5 Understanding the market Our program must be compatible with our businesss market. 7 Software Application Recommendation Recommended Software Application Description Benefits Aggregate Selection Criteria Score Browsers Such as Chrome Accessing the internet 7 Microsoft office suite Consist of Ms Word, Excel, PowerPoint, Access among others Management of organization documents 6 Mobile application Like Skype Communication 7 Software Application Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Broad needs definition Type of the required application is checked 5 Report capabilities checking The selected software has to define the company summary well 8 Software Application Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Amazon Web Services Includes all kind of software products revenue Other service revenue not included It supplies advanced software for the firm. 9 SUN GUARAD Revenues from FIS worldwide are supported Maintenance of the software is not included The transactions are computed using a derived value, that is the same as a direct software license. 8 Salesforce Includes all kind of sales service software Other service revenue not included It includes revenue-generating marketing apps and a cloud app. 7 Software Application Deployment Challenges Deployment Challenge Deployment Challenge Description Data security The software can be attacked by cyber criminals Performance The performance of the software can face issues Insufficient knowledge The users of the software may not have sufficient knowledge on their usage Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed software applications must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed software applications Training of employees Organization employees’ needs be trained on software control and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations New computers buying $2000 The new computers will be installed the new software applications Employing new staff $3000 The new employees will make sure that the software is properly utilized. Cloud Services Recommendations Cloud Services Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Cost Cost effectiveness must be considered 4 Security The software applications must be well protected from attacks 9 Convenience The software applications must be utilized without previous errors 8 Cloud Services Recommendation Recommended Cloud Services Description Benefits Aggregate Selection Criteria Score Google Drive 15GB capacity Best in team collaborations 10 Dropbox 2GB limit Best in small devices like smartphones 8 Box 10GB limit Best in enterprise solutions 7 Cloud Services Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Standard compliance The cloud service providers must comply with the government set standards 8 Data security The service providers must ensure the user data is protected 9 Service roadmap The organization objectives must be met through project implementation 7 Cloud Services Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Amazon Web Services Includes all additional computer and database storage N/A Business integration is made easier for users 9 Google cloud Famous worldwide N/A Best in google searches and YouTube services 8 Cloud Services Deployment Challenges Deployment Challenge Deployment Challenge Description Data security The cloud servers can be attacked by cyber criminals Performance The performance of the cloud servers can face issues Insufficient knowledge The users of the cloud services may not have sufficient knowledge on their usage Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed software applications must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed software applications Training of employees Organization employees’ needs be trained on software control and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Increase the number of employees $1000 The new employees will be responsible for controlling the cloud services. Copyright 2020 by University of Phoenix. All rights reserved. Copyright 2020 by University of Phoenix. All rights reserved. BSA/425 v1.3 Project Plan Draft BSA/425 v1.3 Page 9 of 9 LEWIN’S INTERNET BANKING COMPANY Project Plan Draft Fill out each of the sections below with information relevant to your project. Be sure to include the company name associated with your project. Company Name: XYZ Bank Network Technology Recommendations Network Technology Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points IN a Scale of 10) LAN It connects a number of computers or low-voltage devices across a short distance. 5 WAN Long distance computer connection 5 WLAN Does not require the physical devices as it operate like Wi-Fi 8 VWLAN Decreases network resources wasted by acting LAN segments and reduce collisions 9 Network Technology Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Cisco Very fast, best customer service Expensive Heavy network in the organization IOs optimization better experience and great mobile experience 9 Alloys Cheap, better customer service Poor network Encryption of user data 5 Aruba Cheap, superb network Poor network Software for organizational services 4 Network Technology Deployment Challenges Deployment Challenge Deployment Challenge Description Physical vs logical deployment The appliances in physical networks are connected via protocols, but in logical networks, other traffics are used which are indifferent to physical networks and must be run. Scalability and automatic deployment Not only must the networks be automated, but they must also be scalable. Bringing separate own network When installing a network in a data center architecture, an automated and quicker deployment is preferable. Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed technology must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed technology Training of employees Organization employees’ needs be trained on the internet and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Increase the number of employees $3000 High productivity Construction of new block $50000 Installation of the proposed system and components Database System Recommendation Database System Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Terms of reference definition The purpose of the project 5 Products shortlisting Selecting the best database management system (DBMS) 8 Products evaluation Thorough analysis of the selected DBMS 4 Recommendation Findings and analysis of the right organization 9 Database System Recommendation Recommended Database System Description Benefits Aggregate Selection Criteria Score Desktop Entering and logical storage of user data High speed in data processing 4 Relational Tables arranged in schemas in a particular server Storage of multiple data 5 Normalization Processing and breaking up of data Ais in sorting of database documents based on defined criteria 7 Database System Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Cost Cost effectiveness must be considered 5 Security Data must be well protected from attacks 9 Convenience Data must be utilized without previous errors 7 Database System Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Oracle Support cloud services, very powerful Oracle database may not be ideal because it is complexity and users need high technical ability to operate Cloud database management as well as employee training 8 Microsoft SQL Widely used globally Complicated licensing and expensive Easily integrated with Microsoft products such as Word, Excel etc 6 Database System Deployment Challenges Deployment Challenge Deployment Challenge Description Data and information security Currently there are numerous cyber security attacks Performance The performance of the system can face issues Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed database must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed database technology Training of employees Organization employees’ needs be trained on the database management and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Purchase of the new database system $5000 It will assist the firm in better storing and retrieving its expanding volumes of data. Software Application Recommendations Software Application Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Industry and business expertise This is the proportion of employees having IT expertise in the firm. 8 Program management The program and project must be complicated, and the organization must be competent to handle it. 5 Understanding the market Our program must be compatible with our businesss market. 7 Software Application Recommendation Recommended Software Application Description Benefits Aggregate Selection Criteria Score Browsers Such as Chrome Accessing the internet 7 Microsoft office suite Consist of Ms Word, Excel, PowerPoint, Access among others Management of organization documents 6 Mobile application Like Skype Communication 7 Software Application Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Broad needs definition Type of the required application is checked 5 Report capabilities checking The selected software has to define the company summary well 8 Software Application Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Amazon Web Services Includes all kind of software products revenue Other service revenue not included It supplies advanced software for the firm. 9 SUN GUARAD Revenues from FIS worldwide are supported Maintenance of the software is not included The transactions are computed using a derived value that is the same as a direct software license. 8 Salesforce Includes all kind of sales service software Other service revenue not included It includes revenue-generating marketing apps and a cloud app. 7 Software Application Deployment Challenges Deployment Challenge Deployment Challenge Description Data security The software can be attacked by cyber criminals Performance The performance of the software can face issues Insufficient knowledge The users of the software may not have sufficient knowledge on their usage Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed software applications must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed software applications Training of employees Organization employees’ needs be trained on software control and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations New computers buying $2000 The new computers will be installed the new software applications Employing new staff $3000 The new employees will make sure that the software is properly utilized. Cloud Services Recommendations Cloud Services Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Cost Cost effectiveness must be considered 4 Security The software applications must be well protected from attacks 9 Convenience The software applications must be utilized without previous errors 8 Cloud Services Recommendation Recommended Cloud Services Description Benefits Aggregate Selection Criteria Score Google Drive 15GB capacity Best in team collaborations 10 Dropbox 2GB limit Best in small devices like smartphones 8 Box 10GB limit Best in enterprise solutions 7 Cloud Services Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting in Points) Standard compliance The cloud service providers must comply with the government set standards 8 Data security The service providers must ensure the user data is protected 9 Service roadmap The organization objectives must be met through project implementation 7 Cloud Services Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products/Services Provided to Project Aggregate Selection Criteria Score Amazon Web Services Includes all additional computer and database storage N/A Business integration is made easier for users 9 Google cloud Famous worldwide N/A Best in google searches and YouTube services 8 Cloud Services Deployment Challenges Deployment Challenge Deployment Challenge Description Data security The cloud servers can be attacked by cyber criminals Performance The performance of the cloud servers can face issues Insufficient knowledge The users of the cloud services may not have sufficient knowledge on their usage Technology Adoption Methods Method Name Method Description Strategy and Technology Alignment The proposed software applications must meet the organizational needs Analysis of the present system This will help the management to determine the need of the proposed software applications Training of employees Organization employees’ needs be trained on software control and how to use it so that they can accept it more quickly. Cost/Benefit Considerations Benefits Costs Considerations Increase the number of employees $1000 The new employees will be responsible for controlling the cloud services. Copyright 2020 by University of Phoenix. All rights reserved. Copyright 2020 by University of Phoenix. All rights reserved. BSA/425 v1.3 Project Proposal Template BSA/425 v1.3 Page 2 of 7 Banking E-Services Project Proposal Fill out each of the sections below with information relevant to your project and add your company’s name. Company Name: XYZ Bank Project Proposal: Internet Banking System Project Scope Statement Project Title Banking e-Services Project Sponsor(s) XYZ Bank Business Context for the System The proposed internet bank project needs to implement accounts and deposits, credit, debit and travel cards, insurance, tax services, investment as well as insurance services. Project Scope Description IT infrastructure, Data and system security, network, applications among others. Date Prepared 13th July, 2021. Prepared By Student Name Problems/Issues/Opportunities the Proposed System Expected to Solve Problems Issues Opportunities Network problem Hacking Security Malicious activities It makes the system more secure and up to date with installation of antivirus, firewall and applying data encryption. Project Objectives Project Objective Name Project Objective Description (In terms of Issues and Opportunities) Transactions, Balances, Statements, Accounts Issues: Security, Technical difficulties, sometimes difficult to access, network glitches. Opportunities: Time saving, user-friendly, safe, time-saving, and password and id-based authentication Objective definition: Clients data is fed into the system, and it provides as much information and services as it can, such as maintaining accounts, balances, and records of deposits and withdrawals, all while maintaining a highly secure infrastructure and fewer network issues. The technical infrastructure should be robust and easy to use. Project Deliverables Project Deliverable Name Project Deliverable Description (In terms of Issues and Opportunities) ATM, servers, infrastructure, applications as well as other devices Issues: Occasionally they stop working, or there is an issue with accessibility, such as a slow internet connection or poorly designed applications that are not user friendly. Opportunities: It can give the people an opportunity to learn new technical ideas hence saving time and cost Project Acceptance Criteria Project Acceptance Criteria Name Project Acceptance Criteria Description (In terms of Issues and Opportunities) User name, mobile number, account number, address, additional codes Issues: A user can miss to fill some important information due to misunderstanding, or others just prefer manual work Opportunities: It gives the users an opportunity to enhance the computer knowledge by working using their smartphones and laptops. Project Exclusions Project Exclusion Name Project Exclusion Description Hardware requirements This project will not build the hardware needed for the implementation. However, it will focus on the integration and configuration of the hardware with the software. Project Constraints Project Constraint Name Project Constraint Description (In terms of Issues and Opportunities) Assistance, network, security, inflexibility Issues: People may want help while doing online transactions, for instance, when operating an ATM machine. Even though network brokerage is a regular occurrence, security measures might be poor sometimes, thus banks should employ antivirus and firewalls in their systems. Opportunities: It makes the system more transparent by making information more readily available, and it may be made more scalable by emphasizing the significance of online banking to the public. Project Assumptions Project Assumption Name Project Assumption Description (In terms of Issues and Opportunities) Service oriented, Customer driven Issues: While there are interruptions when providing services, it totally meets the demands of the population. As a result, meeting client needs should be a top priority. Opportunities: It can acquire a better understanding of what customers require in order to meet their needs, and it can install all of their services on their website, making work easier. Project Methodology i The website should be simple to use. Develop a vision and work on it, such as what all consumer demands you can meet with the website, and so on. ii Design as many templates as possible, and align the website creation and success methods. iii It should be adaptable as well as simple to use even remotely and at any time. iv It is highly scalable and can meet the demands of a large number of employees, as well as feed consumer data into the system. v Available 24 hours a day, 7 days a week. vi It should be customer-focused. High-Level Work Schedule: Project Scope Description of Work Assumptions and Constraints Build a system that allows one to make payments as well as other type of transactions online. Basic computer knowledge System requirements met Assistance Security Network Infrastructure Milestones Due Dates Project approval Requirements review Design approval Planning Requirement’s definition Designing Development and implementation Final approval Deployment Maintaining 20th July, 2021 31st July, 2021 5th August, 2021 11th August 2021 17th August 2021 20th August 2021 30th August 2021 21st September 2021 30th September 2021 15th October 2021 ID Activity Resource Labor Hours Labor Rate (USD) Labor Total Material Units Material Cost (USD) Material Total Total Cost 1 Deposit and withdraw money ATM, software, computer 80 400 32000 10 1000 10000 42000 2 Make online payments Mobile application, software 50 300 15000 5 500 2500 17500 3 Borrow loans Mobile application, software, computer, mobile phones 40 300 12000 5 600 3000 15000 4 Verify user transactions Software, computer 40 200 8000 6 300 1800 9800 5 Insurance activities Software, computer, mobile phones 80 400 32000 15 400 6000 38000 Quality Requirements Reliability, Availability, Usability, Customer service, Customer experience, Performance, Maintainability Acceptance Criteria Clear project mission, Client consultation, Clear communication, Adequate resources, Monitoring and feedback mechanisms, committed project personnel, Top management support. Technical Information Technical Issues: Performance, Reliability and Availability Software Requirements: Best programming language, Operating system Agreement Information The Recipient undertakes not to use the Confidential Information for any purpose except the Purpose, without first obtaining the written agreement of the Discloser. The Recipient undertakes to keep the Confidential Information secure and not to disclose it to any third party [except to its employees [and professional advisers] who need to know the same for the Purpose, who know they owe a duty of confidence to the Discloser and who are bound by obligations equivalent to those in clause 2 above and this clause 3. Signed and Delivered as a Deed by: [name of Recipient] in the presence of: ____________________ Signature ______________________________ Signature of witness _____________________ Name of Witness _________________________ Address of the witness _________________________ Copyright 2020 by University of Phoenix. All rights reserved. Copyright 2020 by University of Phoenix. All rights reserved. 8 XYZ Bank Software Test Plan Student Name: powede yingi Software Test Plan Project Name: XYZ Bank Software Test Plan Purpose of Project: To prepare an effective software test plan for testing the organization software components and functionalities. Features To Be Tested/Not To Be Tested The features to be tested in this project include; i. Software application units ii. Software system iii. Software integration iv. Software performance and stress v. Software user acceptance vi. Software automatic regression vii. Software beta requirements On the other hand, the following feature will not be tested i. Software batch. This feature will not be tested since it has low risk based on the previous risk assessment conducted. Testing Pass/Fail Criteria Feature Pass/Fail Criteria (Pass definition) Software application units All test cases completed All codes covered Software system All test cases completed All codes covered Software integration All test cases completed All codes covered Software performance and stress All test cases completed Software user acceptance level All test cases completed Software automatic regression All test cases completed Software beta requirements All test cases completed Testing Approach Execution of this project applied the box approach. This is a hybrid method combing the two traditional approaches. White-box and black-box testing are two types of software testing methods. These two methodologies are applied in the description of testers point of view when creating test cases. Grey-box testing is a hybrid approach to software testing methodology that can be used. The above arbitrary distinction among black- and white-box testing has faded somewhat as the concept of grey-box testing—which develops tests from specific design elements—has gained traction. White-box testing verifies a programs internal structures or workings rather than the functionality that is visible to the end user. In white-box testing, test cases are created using an internal perspective of the system (the source code) and programming skills. The tester selects inputs in order to exercise code paths and determine appropriate outputs. It includes API testing, code coverage, fault injection among others. On the other hand, black-box testing looks at the program as if it were a black box, assessing functionality without knowing how it works inside or viewing the source code. The testers only know what the program should do, not how it should do it. Use case testing, exploratory testing, equivalence partitioning, state transition tables, among others are all examples of black-box testing techniques. Testing Cases This project implementation requires implementation of the following use cases; Test Case Test Case Description Test Data Expected Result Actual Result Pass/Fail 1 Launch application www.google.com Google.com Google.com Pass 2 Enter valid email and password Email: [email protected] Password: ****** The password entered is incorrect, forgotten password? The password entered is incorrect, forgotten password? Pass 3 Login Email: [email protected] Password: ****** Login needs to be successful Login successful Pass 4 Verify user settings page N/A User preference page should be displayed User preference page is displayed Pass Testing Materials (Hardware/Software Requirements) Hardware requirements: i. Modems ii. Computers Software requirements: i. Workstation ii. Mainframe iii. Operating system Testing Schedule Testing Activity Duration Resource Comments Test Plan Creation 5 days Test Manager Planning entails preparation details to carry out the identified tests Test Specification Creation 10 days Test Leads This phase entail identification of specific tests to be carried out. Test Specification Team Review 5 days Project Team The team is selected and reviewed by defining specific roles of each member. Component Testing 20 days Component Testers Individual components are tested Integration Testing 20 days Component and System Testers The integration of different components is tested. System Testing 15 days System Testers The complete system is tested Performance Testing 5 days System Testers The performance of the system is tested. Use Case Validation 10 days System Testers All the use cases defined validated. Alpha Testing 5 days Product Managers/Analysts The product release details are tested Beta Testing/Pilot Program 20 days Pilot Program End-Users The end user’s capability to use the software is tested. Risks and Contingencies Matrix Risk Probability Risk Type Owner Contingencies/Mitigation Approach Do not have enough skilled workers to test components as they are ready for testing. 25\% Project Resources Testing Manager Testing schedule will be adjusted based on available resources. Testing team member turnover 10\% Project Resources Testing Manager Adjust testing schedules. Make sure testing team members are cross-trained on testing techniques in case a team member leaves the organization. Software hacking 50\% Project resources Security Manager Training of end users. Implementing data and information security techniques and procedures. Inaccurate estimations 30\% Project resources Project Manager Consider uncertainty while estimating Allocate duties to different team leaders. Effective communications. End user engagement 25\% Project resources Testing Manager Ensure end users are involved in all necessary phases of the project. Poor quality code 8\% Project resources Testing Manager Code reviews. Clear coding standards and policies Testing all the codes XYZ Bank Software Test Plan Student Name Student ID 2 Date Software Test Plan Project Name: XYZ Bank Software Test Plan Purpose of Project: To prepare an effective software test plan for testing the organization software components and functionalities. Features To Be Tested/Not To Be Tested The features to be tested in this project include; i. Software application units ii. Software system iii. Software integration iv. Software performance and stress v. Software user acceptance vi. Software automatic regression vii. Software beta requirements On the other hand, the following feature will not be tested i. Software batch. This feature will not be tested since it has low risk based on the previous risk assessment conducted. Testing Pass/Fail Criteria Feature Pass/Fail Criteria (Pass definition) Software application units All test cases completed All codes covered Software system All test cases completed All codes covered Software integration All test cases completed All codes covered Software performance and stress All test cases completed Software user acceptance level All test cases completed Software automatic regression All test cases completed Software beta requirements All test cases completed Testing Approach Execution of this project applied the box approach. This is a hybrid method combing the two traditional approaches. White-box and black-box testing are two types of software testing methods. These two methodologies are applied in the description of testers point of view when creating test cases. Grey-box testing is a hybrid approach to software testing methodology that can be used. The above arbitrary distinction among black- and white-box testing has faded somewhat as the concept of grey-box testing—which develops tests from specific design elements—has gained traction. White-box testing verifies a programs internal structures or workings rather than the functionality that is visible to the end user. In white-box testing, test cases are created using an internal perspective of the system (the source code) and programming skills. The tester selects inputs in order to exercise code paths and determine appropriate outputs. It includes API testing, code coverage, fault injection among others. On the other hand, black-box testing looks at the program as if it were a black box, assessing functionality without knowing how it works inside or viewing the source code. The testers only know what the program should do, not how it should do it. Use case testing, exploratory testing, equivalence partitioning, state transition tables, among others are all examples of black-box testing techniques. Testing Cases This project implementation requires implementation of the following use cases; Test Case Test Case Description Test Data Expected Result Actual Result Pass/Fail 1 Launch application www.google.com Google.com Google.com Pass 2 Enter valid email and password Email: [email protected] Password: ****** The password entered is incorrect, forgotten password? The password entered is incorrect, forgotten password? Pass 3 Login Email: [email protected] Password: ****** Login needs to be successful Login successful Pass 4 Verify user settings page N/A User preference page should be displayed User preference page is displayed Pass Testing Materials (Hardware/Software Requirements) Hardware requirements: i. Modems ii. Computers Software requirements: i. Workstation ii. Mainframe iii. Operating system Testing Schedule Testing Activity Duration Resource Comments Test Plan Creation 5 days Test Manager Planning entails preparation details to carry out the identified tests Test Specification Creation 10 days Test Leads This phase entail identification of specific tests to be carried out. Test Specification Team Review 5 days Project Team The team is selected and reviewed by defining specific roles of each member. Component Testing 20 days Component Testers Individual components are tested Integration Testing 20 days Component and System Testers The integration of different components is tested. System Testing 15 days System Testers The complete system is tested Performance Testing 5 days System Testers The performance of the system is tested. Use Case Validation 10 days System Testers All the use cases defined validated. Alpha Testing 5 days Product Managers/Analysts The product release details are tested Beta Testing/Pilot Program 20 days Pilot Program End-Users The end user’s capability to use the software is tested. Risks and Contingencies Matrix Risk Probability Risk Type Owner Contingencies/Mitigation Approach Do not have enough skilled workers to test components as they are ready for testing. 25\% Project Resources Testing Manager Testing schedule will be adjusted based on available resources. Testing team member turnover 10\% Project Resources Testing Manager Adjust testing schedules. Make sure testing team members are cross-trained on testing techniques in case a team member leaves the organization. Software hacking 50\% Project resources Security Manager Training of end users. Implementing data and information security techniques and procedures. Inaccurate estimations 30\% Project resources Project Manager Consider uncertainty while estimating Allocate duties to different team leaders. Effective communications. End user engagement 25\% Project resources Testing Manager Ensure end users are involved in all necessary phases of the project. Poor quality code 8\% Project resources Testing Manager Code reviews. Clear coding standards and policies Testing all the codes