Testing a Project

Anonymous
timer Asked: Sep 6th, 2018
account_balance_wallet $25

Question description

2 part separated

1) You will continue working on the development of the IT network system application project and contributing to the Key Assignment deliverable. You will finish your testing this week and document all of the results in the quality management report. You may have conducted testing in the previous weeks if you were using an iterative approach to development. The activities this week should result in a minimum of 10 major test cases completed, with results documented in your quality management report.

You will continue executing the project plan to develop the IT network system application. Each team member will continue working on the tasks that they were assigned to be completed this week. These tasks were designated in the work breakdown structure created earlier in the course.

  1. discuss the status of the quality assurance plan you developed during Week 2.
    1. Discuss the percentage of testing completed to-date, and discuss the current quality of the project deliverable. You are encouraged to update your testing strategy to ensure that you have adequate unit-testing coverage. All new components should be unit tested.
    2. You should also conduct integration and system testing to make sure that any new technology works with the rest of the system. Discuss the team’s testing strategy, and determine which team member is responsible for each testing activity.
    3. In addition to unit, integration, and system testing, testing may include network-readiness testing, volume testing, recovery testing, penetration testing, hardware-certification testing, migration testing, regression testing, and ready-for-use testing. The team should complete all planned testing during Week 4. Review each other’s results and ensure that all required testing is completed.
    4. Assess the status of the project and your feelings concerning whether or not the project will be ready for delivery as scheduled. Discuss any serious quality issues that were found during testing and the team’s plan to resolve them.
  2. You will continue to report the status of project development in your quality management report. A section of this report included the results of the quality assurance activities executed to-date, including all testing results. Discuss your current progress with your assigned tasks from the work breakdown structure (WBS), and offer assistance where possible.



2 )Individual Deliverables

Test Cases

At least 10 major test cases should have been executed, and the results should be ready to be documented. Document the results for each test case in your quality management report.

Testing should include—at a minimum—unit, integration, and system testing. Regression testing is highly encouraged. Include your results from additional types of testing, including network-readiness testing, volume testing, recovery testing, penetration testing, hardware-certification testing, migration testing, and ready-for-use testing.

Each test case should include (at a minimum) the following information:

  • Objective of test case I will do that
  • Setup procedure group member will do that
  • Expected results group member will do that
  • Procedure for executing test case group member will do that
  • Results group member will do that

Network System Application Project IT488-1803B-02 James Larkin, Andrew Raby, Anthony Harris, Christian Luna-Zaragoza 8-29-18 Table of Contents Overview of the Project .................................................................................................................. 3 Section 2: Requirements ................................................................................................................. 5 Section 3: Design ............................................................................................................................ 7 1. Technical Design Factors ........................................................................................................ 7 2. System Constraints.................................................................................................................. 8 Section 4: System development methodology ................................................................................ 9 Section 5: Work breakdown structure (WBS) .............................................................................. 10 Section 6: Communication plan: Week 1 (1 page) ....................................................................... 12 Section 7: Quality assurance plan ................................................................................................. 13 Unit Testing Plan ...................................................................................................................... 14 Integration, System, and Regression testing ............................................................................. 15 Metrics ...................................................................................................................................... 16 System Defects.......................................................................................................................... 17 Risk Management Strategies..................................................................................................... 18 Section 8: Documentation plan: Week 3 (1 page) ........................................................................ 20 Section 9: Quality Assurance and results of test-case execution: Week 4 ................................... 21 Project closure: Week 5 (2–3 pages) .......................................................................................... 22 Quality management report: Weeks 1–5....................................................................................... 23 Week 1 Assessment: ................................................................................................................. 23 Week 2 Assessment: ................................................................................................................. 23 Week 4 Assessment: ................................................................................................................. 23 Week 5 Assessment: ................................................................................................................. 23 3 user documents: Week 3 (3–9 pages) ...................................................................................... 24 References ..................................................................................................................................... 25 Overview of the Project For this project we aim to create a customer technical support system which will enable organizations to improve and ensure the satisfaction of their customers. The system application will provide the support required by organizations to explore and address the needs and concerns of their customers. The system will be designed to be a self-help application where customers can query the system and find out what they are looking for without necessary seeking the help of the technicians within the organization. This will be a full support application which provides solutions for solvable problems, helping to reduce delays for the customers and workloads for the technicians of the organization. The system will give customers access to simplified self-help which will be available through an electronic platform. Upon its completion, the system will have a number of features which allow it to effectively carry out its functions. These will range from allowing the customers of an organization to create their own accounts, providing them with the search function such that they can look for particular information they need, connecting them to helpful materials such as training videos. The system will also provide the option of live chats for customers and supervisors within an organization. The option will enable clients to deal with any matter that the available information did not address or seek clarification. The system will also provide direct communication between the customers and the support within an organization through the option to call back improving the satisfaction rate. The system will provide a schedule which will enable clients know when technicians will be available to assist them and their specific profile. The system will also enable the customers to give their own feedback of the help given by the technicians and service within the organization allowing them to detect areas of concern, changes that need to be made in order to improve the delivery of service and customer satisfaction. The system will provide information on the organization ranging from their full product range and their cost. It will also provide any additional information on the products such as special offers, discounts allowing customer to take advantage of this. It will also give third party recommendations to clients on other frequently requested products or services which the company does not provide. Section 2: Requirements There are going to be many requirements needed for our system to operate the way we want it to. While we are building the system, it is important to think about redundancy of critical systems, so we can continue to operate under any circumstances including disasters. That being said I would suggest that we use a service provider to host our datacenter. This will allow us to stay up to date on all current patches for our servers and maintain connectivity through redundant connections from the provider. They will guarantee us close to 100% up time, which is great and frees up some of our staff to work on other projects instead of maintaining servers 24/7. We can find a provider that will provide all the power we need I am suggesting the following equipment to run our system. Hardware to host or application and databases 2 ESXI servers to host the following • Application server • Database server to host all FAQ, support and training docs. • Web server • File share server • Print server These servers will house all of the databases, web and application data. This will allow us to stay connected from anywhere. This will benefit us when it comes to providing reliable service for our customers. We need to make sure the provider can guarantee us up time. Functions needed for database and applications. • database relationship to our work application that links o estimated times of availability o current availability calendar o estimated time of arrival o employee profiles (name, photo, type of vehicle) o call back requests from customers • database relationship with current job and product availability and descriptions and all specials / discounts • full security protocols to protect linked company databases • SaaS vendor for Olark live chat application. • virtual private cloud vendor / or PaaS vendor As far as office applications for our employees we can use a product such as Office365. It has all the applications we need as well as email functionality. I would like to keep most of the services hosted. This will allow us to scale much easier as the company expands and with most of our services being cloud based it will be easier to set up the new locations in the future. Section 3: Design The overall system design for this project build will include many features that will encompass all of our customer’s request. Functional design standards will include a relational database that houses our company Service Scheduler and customer data and will feed to our company’s website through AWS web applications (Amazon Aurora). The onsite servers will be 2 ESXI, using Microsoft Server 2012 with a stack schema. (Amazon Web Services, 2018) We will have both physical and virtual server alignment (adding secure protocols w/remote access capabilities). The physical server onsite will also house database server which will host all FAQ, support and training docs, file share server, and print server. The virtual server will house application and web servers and use Application Discovery Service (ADS). (Amazon Web Services, 2018) The web app layout will be developed with homepage, weekly specials and discounts landing page, customer review section, products and services library area, and service scheduler interactive calendar. It will include a special customer GUI screen for Account creation and include entry forms. We have also established other design factors that will correlate to customer satisfaction and employ overall system efficiency by the creation of minimal processing requirements. 1. Technical Design Factors • Cross platform for end-user access • Database will use Stack Overflow schema. • Website application must maintain a secured customer database and provide access to each user’s accounts. • Have an aesthetically pleasing GUI on web platform with minimal latency occurrences, while providing access to Home+ Networking’s website available data. • The application must be fully accessible to standard and disabled users and work smoothly across all device platforms with nearly no noticeable drop-off. 2. System Constraints • Latency < 5 seconds per user interval when accessing database server or sending data update • and timeout/retry message if user data entry delay over 10 minutes. Home+ Networking must be accessible and readily operable with an up-time of over 98%. • Built-in data entry checker and Auto-complete function • Require User password w/8-character minimum, non-alpha character, & special character • Secured transaction handler (partnering w/Stripe) • Event log tracker that sends application performance logs (Hourly), user activity logs (Hourly), access error (at Occurrence), and latency or service interruptions (at Occurrence) to internal dashboard application for local IT to monitor. • Run on all Java Platforms including 64-Bit versions. Section 4: System development methodology The system development methodology that will be used to develop this system application will be the spiral methodology. This methodology focuses on the identification and reduction of risks before they can cause any damage to the computer systems. The Spiral Model is a sophisticated model that focuses on early identification and reduction of project risks (TatvaSoft, 2015). As stated before, this model will allow us to focus on how to reduce any type of risks during the development of the project. This model will allow us to start the project on a small scale and as we develop we can project any type of risks and come out with solutions that will avoid those risks. The spiral methodology fits well with the development of the application because this methodology is designed for larger projects such as the application we will be developing. It also gives us the flexibility to add or change more features in the future. Since we can already project many modifications, the spiral methodology will be able to suit us when the changes do occur without having to deviate from the goal. Since the main purpose of the application is to provide a self-help application to those clients that do not seek help from other technicians, we will need to rely on databases services which will add up costs to the already costly application development. Even though this might be a costly project, we believed that it is necessary in order to provide our clients with the best support that will help them achieve their tasks. The outcome of the application will be determined by how attentive and our knowledge of the project while being developed. Section 5: Work breakdown structure (WBS) Week 1- Overview of the project August 15, 2018 – August 21, 2018 • • • Meeting with stakeholders Requirements Purchasing of servers Week 2 – Design August 22, 2018 – August 28, 2018 • • • Meeting with Developers Meeting with Third Party Apps Design a rough draft of the application Week 3 – Development August 29, 2018 – September 4, 2018 • Development of the project along with the third-party software o Amazon Web Services o Olark Week 4 – Testing of the application September 5, 2018 – September 11, 2018 • • • • Test 1 Test 2 Test 3 Report of the tests Week 5 – Installation and Completion September 12, 2018 – September 21, 2018 • • Training Project Closure Figure 1 Section 6: Communication plan: Week 1 (1 page) Communication is going to play a major in the success of this project. Our project team leaders will be meeting with management on a weekly basis to ensure that the project is on track and meeting all of the goals and milestones. These meetings will go over timelines, budgets and any other topics that may come up. The team leaders will present any findings or errors that they may have come across in the previous week so that they can work as a group to find a resolution that won’t impact the entire project. These meetings will be important because with any project changes may need to be addressed quickly. This will enable the project to get back on track. These weekly meetings will also make sure everyone is on the same page and working in the right direction. After the meetings the team leaders will go back to their teams and relay the messages and make any adjustments needed to get the tasks done. I believe this form of open communication will be a big benefit and deliver the results we are looking for. In a large project, things can get out of control and without communication things can begin to fall apart or key elements may be left out or overlooked. The image below will show the chain of command for the project. Team Leader Team Member Management Figure 2 Team Leader Section 7: Quality assurance plan In our project we do not only want to make sure that we meet the requirements and do them on time and the required budget and the like. We would like to ensure that we deliver quality that will be favorable to all the stakeholders involved. Since we have different phases in the project our quality assurance plan will involve each of the phases so that we can have an outcome that is favorable to all and of high quality. Since we have taken up the spiral model of the system development, we will incorporate of quality assurance planning in all the phases of the system development life cycle. The plan is to have checks at all the phases and a confirmation by the team leaders and project managers that all is of the required quality before moving on to the next phase. In the first phase which is the planning phase, we need to understand the requirements of the system and we will do this through the collection of information from the necessary parties. The outcome of the system will be determined by the level of understanding of the requirements and hence for quality assurance in this phase we will ensure that all the parties that will take part in the project have clearly understood what is required. They will be tested and asked questions by the team leaders who will gauge their level of understanding before the start of implementation. Risk analysis is the next phase and for this level, the team will test each of the mitigation plans against the risk itself and brainstorm over and over if it deals with the situation. They will run through different scenarios so that they can ensure that the mitigation plans are effective, and they deal with the risks effectively. This will ensure that the output has no flaws and is of high quality. The engineering phase is one of the most important phases and to ensure quality we will involve the use of customers in our quality assurance so that they can be able to help us test the workability of the system. Different random clients will be asked to participate in the testing of the system before launch and their feedback and criticism allowed so that the end product can be superb. There will also be some sort of audit team for the developers so that they ensure that the end product is of high quality (Amado et.al). In the end of the methodology we have the evaluation which will be done by the customers, since we will have already enlisted the help of several or different of them in the previous phase we hope the feedback will be very positive. Any feedback that needs us to fix a few issues will also be take in stride and necessary corrections made. Unit Testing Plan Home+ Networking will employ a sound and industry approved unit testing process to ensure that the web application code, server accessibility, database integrity, website features, GUI, and customer and employee access are compliant with the projects restraints and requirements. We will be creating the unit test and testing the code and server accessibility, and GUI through Visual Studio 2017. These test categories are listed below and will follow the attached format. (DIETRICH, 2017) Test Case ID Test Scenario Test Steps Test Data Figure 3 Expected Results Actual Results Pass/Fail We will employ 10 major test cases including: TC01 Verify Web app runs on Java Platform TC02 Verify Web app Home Page loads. TC03 Check Customer Login w/valid data TC04 Check Customer Login w/invalid data TC05 Verify Web app can access Database table TC06 Verify Customer form updates Database table TC07 Test code utilizes integrated libraries TC08 Verify Web app list valid Google links TC09 Confirm Event log tracker sends application performance logs TC10 Test Built-in data entry checker and Auto-complete functions correctly Integration, System, and Regression testing When you are working on a complex application and system you may have features added and subtracted throughout the process. These integrations will be addressed at our project management meetings to make sure that they don’t have any negative affect on existing functions and functions that will be added in the future. These features will need to be tested by our developers prior to being added into the current project. We will be using a sandbox environment to test the features. This will be a virtual environment that is an exact replica of our production environment. This will allow us to test without breaking our production system. Being able to run these test environments are a huge help to delivering quality products that run without issues. Metrics Quality is at the top of our list and we will do everything we can to ensure we deliver the quality the stakeholders expect within the time we promised. Our testing will use a variety of metrics to test for performance, reliability and cost. We will fine-tune the system to provide the highest performance with the budget given to use by the stakeholders. With any project there is a sweet spot that blends the perfect amount of cost and performance and that is what we will be looking for as we test the system. Figure 4 We will ensure that Latency < 5 seconds per user interval when accessing database server or sending data update and timeout/retry message if user data entry delay over 10 minutes. The Home+ Networking website must be accessible and readily operable with an up-time of over 98%. The addition of an event log tracker that sends application performance logs (Hourly), user activity logs (Hourly), access error (at Occurrence), and latency or service interruptions (at Occurrence) to internal dashboard application for local IT to monitor. System Defects During each phase of the QA, there’s always a possibility to have defects in the application especially during the testing phase. These defects have to be measure, documented, and reported so a change in the application can be performed. One way we will be measuring these defects is by using the Measurement System Analysis, or MSA for its initials. Our application that we’re developing will be used support technicians, which they will utilize it to provide support for their customers. If the defects are not found, then it will be crucial to a technical which could potentially give wrong information to their customers. MSA is defined as an experimental and mathematical method of determining the amount of variation that exists within a measurement process (Quality-One, n.d.). By using this tool, we will be able to find measure certain parameters that will be able to detect any type of defects during the production and development phase. MSA will also help us by assuring that all the data is accurate and the system that will be used to collect the data is the right system for our application. By obtaining reliable data, we will be able to predict any defects or any other issues that might delay our application production. MSA will also measure the following characteristics during the production phase: • Resolution - the incremental ability of a measurement system to discriminate between measurement values. • Accuracy - is a measure of the distance between the average value of the measurement of a part and the True, certified, or assigned value of a part. • Linearity - the consistency of accuracy over the range of measurement. • Repeatability - the consistency of a single appraiser to measure the same part multiple times with the same measurement system. • Reproducibility - is the consistency of different appraisers in measuring the same part with the same measurement system. • Stability - is the ability of a measurement system to produce the same values over time when measuring the same sample (Raytheon, 2007). Risk Management Strategies In order to provide an application that’s capable of assisting technicians, we will have to eliminate any risks that could interfere with the development of the application. A Project Risk Register will be created to analyze and treat any type of risks. A Project Risk Register is a handy tool to add structure and consistency to your project risk management process (Kloosterman, What are the 12 Key Elements of a Project Risk Register Template?, 2014). This can be achieved by utilizing the next following strategies. • Identify the risk – If a risk is found then we will have to predict how the risk will affect the development of the application • Analyze the risk – Once there’s a confirmation of a risk, then we can predict the consequences of the risk and how it should be treated • Evaluate and rank the risk – The risk can be evaluated from a low – medium – high level. By placing a value on the risk, developers can assist the seriousness of the risk and its consequences. • Treat the risk – If a high-level risk is found, then a plan is designing to eliminate the risk or bring the risk down to the lowest level possible. • Monitor the risk – The risk will be monitored and documented in the Project Risk Register (Kloosterman, What are the 5 Risk Management Steps in a Sound Risk Management Process?, 2014). A risk manangement matrix, such as the table below, can also help assess the level of seriousness of the risk, and the probability that it will happen in the future. Figure 5 All risks will be document and each risk will have its own Project Risk Register, which will be used as references in case any other type of risks appear throughout the process of the application development. Section 8: Documentation plan: Week 3 (1 page) Section 9: Quality Assurance and results of test-case execution: Week 4 Project closure: Week 5 (2–3 pages) Quality management report: Weeks 1–5 Week 1 Assessment: At this point we have established an overview of the project, confirmed project requirements, laid out system application designs, chosen a System Development Methodology, constructed a WBS to establish and allocate work duties as needed. Lastly, we set up a communication plan to ensure visibility and clarity remain top priorities throughout completion of the project. Week 2 Assessment: Now that the project is about to begin we have added a Quality Assurance Plan to include quality planning activities that will go along with our chosen System Development methodology. It includes a Unit Testing plan with 10 major test cases, a plan for integration, system, and regression testing. We have added quality metrics which will ensure our web application delivers on all features with minimal to no drop-off, and established measurements for any possible system defects found. If any other concerns were to arise we have added risk-management strategies that will be employed. Week 4 Assessment: Week 5 Assessment: 3 user documents: Week 3 (3–9 pages) References Amazon Web Services. (2018, July 24th). AWS Application Discovery Service. Retrieved from AWS.amazon.com: https://aws.amazon.com/application-discovery/ DIETRICH, E. (2017, February 22nd). You Still Don’t Know How to Do Unit Testing (and Your Secret is Safe with Me). Retrieved from Stackify.com: https://stackify.com/unit-testingbasics-best-practices/ Kloosterman, V. (2014). What are the 12 Key Elements of a Project Risk Register Template? Retrieved August 2018, from continuingprofessionaldevelopment: http://continuingprofessionaldevelopment.org/key-elements-project-risk-registertemplate/ Kloosterman, V. (2014). What are the 5 Risk Management Steps in a Sound Risk Management Process? Retrieved August 2018, from continuing professional development: http://continuingprofessionaldevelopment.org/risk-management-steps-in-riskmanagement-process/ Quality-One. (n.d.). MSA. Retrieved August 2018, from Quality-One: https://qualityone.com/msa/ Raytheon. (2007). Measurement Systems Analysis. Retrieved August 2018, from Raytheon: https://www.raytheon.com/sites/default/files/connections/rtnwcm/groups/public/documen ts/content/rtn_connect_msa_pdf.pdf TatvaSoft. (2015, April 15). Top 12 Software Development Methodologies & its Advantages / Disadvantages. Retrieved August 2018, from TatvaSoft: https://www.tatvasoft.com/blog/top-12-software-development-methodologies-and-itsadvantages-disadvantages/ Project Management for Instructional Designers by Amado, M., Ashton, K., Ashton, S., Bostwick, J., Clements, G., Drysdale, J., Francis, J., Harrison, B., Nan, V., Nisse, A., Randall, D., Rino, J., Robinson, J., Snyder, A., Wiley, D., & Anonymous. (DATE). Project Management for Instructional Designers. Retrieved from http://pm4id.org/ under Creative Commons Attribution 3.0 Unported.
Network System Application Project IT488-1803B-02 James Larkin, Andrew Raby, Anthony Harris, Christian Luna-Zaragoza 9-5-18 Table of Contents Overview of the Project .................................................................................................................. 4 Section 2: Requirements ................................................................................................................. 6 Section 3: Design ............................................................................................................................ 8 1. Technical Design Factors ........................................................................................................ 8 2. System Constraints.................................................................................................................. 9 Section 4: System development methodology .............................................................................. 10 Section 5: Work breakdown structure (WBS) .............................................................................. 11 Section 6: Communication plan: Week 1 (1 page) ....................................................................... 14 Section 7: Quality assurance plan ................................................................................................. 15 Unit Testing Plan ...................................................................................................................... 16 Integration, System, and Regression testing ............................................................................. 17 Metrics ...................................................................................................................................... 18 Section 8: Documentation plan: Week 3 (1 page) ........................................................................ 20 Section 9: Quality Assurance and results of test-case execution: Week 4 ................................... 22 Project closure: Week 5 (2–3 pages) .......................................................................................... 23 Quality management report: Weeks 1–5....................................................................................... 24 Week 1 Assessment: ................................................................................................................. 24 Week 2 Assessment: ................................................................................................................. 24 Week 3 Assessment: ................................................................................................................. 24 Week 4 Assessment: ................................................................................................................. 25 Week 5 Assessment: ................................................................................................................. 25 3 user documents: Week 3 (3–9 pages) ...................................................................................... 26 System Administrator’s Reference Guide ................................................................................ 26 Template for Reference Guide .............................................................................................. 26 User Manual and Release Description ...................................................................................... 28 Template for User Manual .................................................................................................... 28 Quick reference guide ............................................................................................................... 30 Template for Quick Reference Guide ................................................................................... 30 Conclusion .................................................................................................................................... 31 Unit 3 ........................................................................................................................................ 31 References ..................................................................................................................................... 32 Overview of the Project For this project we aim to create a customer technical support system which will enable organizations to improve and ensure the satisfaction of their customers. The system application will provide the support required by organizations to explore and address the needs and concerns of their customers. The system will be designed to be a self-help application where customers can query the system and find out what they are looking for without necessary seeking the help of the technicians within the organization. This will be a full support application which provides solutions for solvable problems, helping to reduce delays for the customers and workloads for the technicians of the organization. The system will give customers access to simplified self-help which will be available through an electronic platform. Upon its completion, the system will have a number of features which allow it to effectively carry out its functions. These will range from allowing the customers of an organization to create their own accounts, providing them with the search function such that they can look for particular information they need, connecting them to helpful materials such as training videos. The system will also provide the option of live chats for customers and supervisors within an organization. The option will enable clients to deal with any matter that the available information did not address or seek clarification. The system will also provide direct communication between the customers and the support within an organization through the option to call back improving the satisfaction rate. The system will provide a schedule which will enable clients know when technicians will be available to assist them and their specific profile. The system will also enable the customers to give their own feedback of the help given by the technicians and service within the organization allowing them to detect areas of concern, changes that need to be made in order to improve the delivery of service and customer satisfaction. The system will provide information on the organization ranging from their full product range and their cost. It will also provide any additional information on the products such as special offers, discounts allowing customer to take advantage of this. It will also give third party recommendations to clients on other frequently requested products or services which the company does not provide. Section 2: Requirements There are going to be many requirements needed for our system to operate the way we want it to. While we are building the system, it is important to think about redundancy of critical systems, so we can continue to operate under any circumstances including disasters. That being said I would suggest that we use a service provider to host our datacenter. This will allow us to stay up to date on all current patches for our servers and maintain connectivity through redundant connections from the provider. They will guarantee us close to 100% up time, which is great and frees up some of our staff to work on other projects instead of maintaining servers 24/7. We can find a provider that will provide all the power we need I am suggesting the following equipment to run our system. Hardware to host or application and databases 2 ESXI servers to host the following • Application server • Database server to host all FAQ, support and training docs. • Web server • File share server • Print server These servers will house all of the databases, web and application data. This will allow us to stay connected from anywhere. This will benefit us when it comes to providing reliable service for our customers. We need to make sure the provider can guarantee us up time. Functions needed for database and applications. • database relationship to our work application that links o estimated times of availability o current availability calendar o estimated time of arrival o employee profiles (name, photo, type of vehicle) o call back requests from customers • database relationship with current job and product availability and descriptions and all specials / discounts • full security protocols to protect linked company databases • SaaS vendor for Olark live chat application. • virtual private cloud vendor / or PaaS vendor As far as office applications for our employees we can use a product such as Office365. It has all the applications we need as well as email functionality. I would like to keep most of the services hosted. This will allow us to scale much easier as the company expands and with most of our services being cloud based it will be easier to set up the new locations in the future. Section 3: Design The overall system design for this project build will include many features that will encompass all of our customer’s request. Functional design standards will include a relational database that houses our company Service Scheduler and customer data and will feed to our company’s website through AWS web applications (Amazon Aurora). The onsite servers will be 2 ESXI, using Microsoft Server 2012 with a stack schema. (Amazon Web Services, 2018) We will have both physical and virtual server alignment (adding secure protocols w/remote access capabilities). The physical server onsite will also house database server which will host all FAQ, support and training docs, file share server, and print server. The virtual server will house application and web servers and use Application Discovery Service (ADS). (Amazon Web Services, 2018) The web app layout will be developed with homepage, weekly specials and discounts landing page, customer review section, products and services library area, and service scheduler interactive calendar. It will include a special customer GUI screen for Account creation and include entry forms. We have also established other design factors that will correlate to customer satisfaction and employ overall system efficiency by the creation of minimal processing requirements. 1. Technical Design Factors • Cross platform for end-user access • Database will use Stack Overflow schema. • Website application must maintain a secured customer database and provide access to each user’s accounts. • Have an aesthetically pleasing GUI on web platform with minimal latency occurrences, while providing access to Home+ Networking’s website available data. • The application must be fully accessible to standard and disabled users and work smoothly across all device platforms with nearly no noticeable drop-off. 2. System Constraints • Latency < 5 seconds per user interval when accessing database server or sending data update • and timeout/retry message if user data entry delay over 10 minutes. Home+ Networking must be accessible and readily operable with an up-time of over 98%. • Built-in data entry checker and Auto-complete function • Require User password w/8-character minimum, non-alpha character, & special character • Secured transaction handler (partnering w/Stripe) • Event log tracker that sends application performance logs (Hourly), user activity logs (Hourly), access error (at Occurrence), and latency or service interruptions (at Occurrence) to internal dashboard application for local IT to monitor. • Run on all Java Platforms including 64-Bit versions. Section 4: System development methodology The system development methodology that will be used to develop this system application will be the spiral methodology. This methodology focuses on the identification and reduction of risks before they can cause any damage to the computer systems. The Spiral Model is a sophisticated model that focuses on early identification and reduction of project risks (TatvaSoft, 2015). As stated before, this model will allow us to focus on how to reduce any type of risks during the development of the project. This model will allow us to start the project on a small scale and as we develop we can project any type of risks and come out with solutions that will avoid those risks. The spiral methodology fits well with the development of the application because this methodology is designed for larger projects such as the application we will be developing. It also gives us the flexibility to add or change more features in the future. Since we can already project many modifications, the spiral methodology will be able to suit us when the changes do occur without having to deviate from the goal. Since the main purpose of the application is to provide a self-help application to those clients that do not seek help from other technicians, we will need to rely on databases services which will add up costs to the already costly application development. Even though this might be a costly project, we believed that it is necessary in order to provide our clients with the best support that will help them achieve their tasks. The outcome of the application will be determined by how attentive and our knowledge of the project while being developed. Section 5: Work breakdown structure (WBS) Week 1- Overview of the project August 15, 2018 – August 21, 2018 • • • Meeting with stakeholders Requirements Purchasing of servers Week 2 – Design August 22, 2018 – August 28, 2018 • • • • • • Meeting with Developers Meeting with Third Party Apps Design a rough draft of the application Test Case 1 Test Case 2 Test Case 3 Week 3 – Development August 29, 2018 – September 4, 2018 • Development of the project along with the third-party software o Amazon Web Services o Olark • • • Test Case 4 Test Case 5 Test Case 6 Week 4 – Testing of the application September 5, 2018 – September 11, 2018 • • • • • Test Case 7 Test Case 8 Test Case 9 Test Case 10 Report of the tests Week 5 – Installation and Completion September 12, 2018 – September 21, 2018 • • Training Project Closure Section 6: Communication plan: Communication is going to play a major in the success of this project. Our project team leaders will be meeting with management on a weekly basis to ensure that the project is on track and meeting all of the goals and milestones. These meetings will go over timelines, budgets and any other topics that may come up. The team leaders will present any findings or errors that they may have come across in the previous week so that they can work as a group to find a resolution that wont impact the entire project. These meetings will be important because with any project changes may need to be addressed quickly. This will enable the project to get back on track. These weekly meetings will also make sure everyone is on the same page and working in the right direction. After the meetings the team leaders will go back to their teams and relay the messages and make any adjustments needed to get the tasks done. I believe this form of open communication will be a big benefit and deliver the results we are looking for. In a large project things can get out of control and without communication things can begin to fall apart or key elements may be left out or overlooked. The image below will show the chain of command for the project. Management Team Leader Team Member Team Leader Section 7: Quality assurance plan In our project we do not only want to make sure that we meet the requirements and do them on time and the required budget and the like. We would like to ensure that we deliver quality that will be favorable to all the stakeholders involved. Since we have different phases in the project our quality assurance plan will involve each of the phases so that we can have an outcome that is favorable to all and of high quality. Since we have taken up the spiral model of the system development, we will incorporate of quality assurance planning in all the phases of the system development life cycle. The plan is to have checks at all the phases and a confirmation by the team leaders and project managers that all is of the required quality before moving on to the next phase. In the first phase which is the planning phase, we need to understand the requirements of the system and we will do this through the collection of information from the necessary parties. The outcome of the system will be determined by the level of understanding of the requirements and hence for quality assurance in this phase we will ensure that all the parties that will take part in the project have clearly understood what is required. They will be tested and asked questions by the team leaders who will gauge their level of understanding before the start of implementation. Risk analysis is the next phase and for this level, the team will test each of the mitigation plans against the risk itself and brainstorm over and over if it deal with the situation. They will run through different scenarios so that they can ensure that the mitigation plans are effective and they deal with the risks effectively. This will ensure that the output has no flaws and is of high quality. The engineering phase is one of the most important phases and to ensure quality we will involve the use of customers in our quality assurance so that they can be able to help us test the workability of the system. Different random clients will be asked to participate in the testing of the system before launch and their feedback and criticism allowed so that the end product can be superb. There will also be some sort of audit team for the developers so that they ensure that the end product is of high quality (Amado et.al). In the end of the methodology we have the evaluation which will be done by the customers, since we will have already enlisted the help of several or different of them in the previous phase we hope the feedback will be very positive. Any feedback that needs us to fix a few issues will also be take in stride and necessary corrections made. Unit Testing Plan Home+ Networking will employ a sound and industry approved unit testing process to ensure that the web application code, server accessibility, database integrity, website features, GUI, and customer and employee access are compliant with the projects restraints and requirements. We will be creating the unit test and testing the code and server accessibility, and GUI through Visual Studio 2017. These test categories are listed below and will follow the attached format. (DIETRICH, 2017) Test Case ID Test Scenario Test Steps Test Data Expected Results Actual Results Pass/Fail We will employ 10 major test cases including: TC01 Verify Web app runs on Java Platform TC02 Verify Web app Home Page loads. TC03 Check Customer Login w/valid data TC04 Check Customer Login w/invalid data TC05 Verify Web app can access Database table TC06 Verify Customer form updates Database table TC07 Test code utilizes integrated libraries TC08 Verify Web app list valid Google links TC09 Confirm Event log tracker sends application performance logs TC10 Test Built-in data entry checker and Auto-complete functions correctly Integration, System, and Regression testing When you are working on a complex application and system you may have features added and subtracted throughout the process. These integrations will be addressed at our project management meetings to make sure that they don’t have any negative affect on existing functions and functions that will be added in the future. These features will need to be tested by our developers prior to being added into the current project. We will be using a sandbox environment to test the features. This will be a virtual environment that is an exact replica of our production environment. This will allow us to test without breaking our production system. Being able to run these test environments are a huge help to delivering quality products that run without issues. Metrics Quality is at the top of our list and we will do everything we can to ensure we deliver the quality the stakeholders expect within the time we promised. Our testing will use a variety of metrics to test for performance, reliability and cost. We will fine-tune the system to provide the highest performance with the budget given to use by the stakeholders. With any project there is a sweet spot that blends the perfect amount of cost and performance and that is what we will be looking for as we test the system. We will ensure that Latency < 5 seconds per user interval when accessing database server or sending data update and timeout/retry message if user data entry delay over 10 minutes. The Home+ Networking website must be accessible and readily operable with an up-time of over 98%. The addition of an event log tracker that sends application performance logs (Hourly), user activity logs (Hourly), access error (at Occurrence), and latency or service interruptions (at Occurrence) to internal dashboard application for local IT to monitor. Section 8: Documentation plan: Documentation plan Introduction In every business organization a skeleton template is essential for every audience since it offers the essential layout of documentation on the product or service to be used. These skeleton template documents determine the progress and achievement of the audiences in user documentation. User documentation offer details that give customers clear information needed for product usage. This document is written for end users since it clearly describes the information on ways to use a certain product. However, determining the different types of user documentation and the works they provide ensures effective progress. Three types of user documentation Documentation involves various ways in which a set of documents are provided either on paper or in digital form (Schell, 1986). However, the essential procedures needed vary in different forms. User documentation is a visual description on how an application system works and the various ways to use it. The types of user documentation that can be provided include the system administrator’s guide, release description and quick reference guide (Rosenbaum, 1987). The reference guide includes specific information about an operating system in a clear and concise format. Conclusion In conclusion, user documentation ensures detailed information is given to the customers on the products and services needed. However, the system administrator guide ensures new systems are installed and troubleshooting problems are avoided. Home+ Networking will push the development of the user manual and reference guide continually throughout the development of the web application and its Use Case testing cycles as changes may occur or need to be notated. Instead of having to write a full document before or after development is completed, it will be an ongoing process that is only completed once a final sign off is obtained. The user manual document will be distributed by email in links to customers once their account has been created and email has been confirmed in the form of a PDF. The reference guide will be saved on the company server and can be accessed by any requiring party that has proper user access credentials from the company portal. The maintenance requirements on both documents will occur with each iteration as that will be the only time updates are necessary depending on actual changes rolled out. All customers that have created accounts will be emailed a link giving access to the newest user manual if desired. The reference guide change notifications will only be emailed to personnel on the distribution list created by the project team and authorized by the project manager but will still reside on the company server if required. Section 9: Quality Assurance and results of test-case execution: Week 4 Project closure: Week 5 (2–3 pages) Quality management report: Weeks Week 1 Assessment: At this point we have established an overview of the project, confirmed project requirements, laid out system application designs, chosen a System Development Methodology, constructed a WBS to establish and allocate work duties as needed. Lastly, we set up a communication plan to ensure visibility and clarity remain top priorities throughout completion of the project. Week 2 Assessment: Now that the project is about to begin we have added a Quality Assurance Plan to include quality planning activities that will go along with our chosen System Development methodology. It includes a Unit Testing plan with 10 major test cases, a plan for integration, system, and regression testing. We have added quality metrics which will ensure our web application delivers on all features with minimal to no drop-off, and established measurements for any possible system defects found. If any other concerns were to arise we have added risk-management strategies that will be employed. We have now completed Test Cases 1-3 with a positive (PASS) output result from two of 3. Test Case 2 will require more time to correct as we were unable Verify Web app Home Page loads on all platforms (mobile IOS failed). Week 3 Assessment: At this juncture we have added our templates for user documents. Establishing separate criteria for both user manual and reference guides. This will assist us in ensuring that each user will have adequate knowledge at their given user level to operate and or maintain the web application. We have now completed Test Cases 4-6 with a positive (PASS) output result from all 3 and have corrected failure received on TC 02. Now all Test Cases 1-6 are resulting in PASS. Week 4 Assessment: Week 5 Assessment: 3 user documents: System Administrator’s Reference Guide This guide will be used for system administrators to access the web application and make changes. It will also give documentation on how to troubleshoot some common issues that may happen while using the application. Template for Reference Guide Introduction Chapter 1: Parts of the Home+ Networking Website (Section will lay out creation and boot sequence and explain how servers are integrated) Installing and Activating the Home+ Networking Theme Customer Database Link Web Integration Process Chapter 2: Editing Home+ Networking HTML Setup (Section will lay out Java HTML sequence of webpage) WordPress Top Bar Menu Ear Content Banner Search Box Auxiliary Menu FAQ Chapter 3: Theme Customization (Section will lay out remaining Java HTML web form) Content Panel and Sidebars Border Width Content Panel and Sidebars Border Radius Content Panel and Sidebars Border Color Content Panel and Sidebars Background Color Chapter 4: Home+ Networking App Features (Section will describe how features are integrated into web application) Company Video Links Customer Account Creation Section Customer Data Entry Form Section DIY Google Links Technician Scheduler Chapter 5: Troubleshooting topics (Simple Troubleshooting Tips) Starting services Make sure user is not locked out of the system Make sure servers are reachable User Manual and Release Description This document will be used to describe the application and all its features. It will list the version number and information about the company. The system is a self-help application where customers can query the system and find out what they are looking for without necessary seeking the help of the technicians within the organization Template for User Manual Chapter 1. Introduction to Home+ Networking Self-Help Web Application Purpose Scope System Organization Chapter 2. Describing the System Key Features Customer Interface Prompts Entry Forms System Operations Chapter 3. Installing, Starting and Stopping the System First-time Users Creating Login Creating Password Accessing the Self-Help Window Chapter 4. Step by Step Instructions for Scheduling a Technician Instructions Conventions Errors, Malfunctions, and Customer Contact Options Messages Quick-Reference Chapter 5. How to access the Self-Help Videos Instructions How to Request Videos Updating Video Content Accessing Samples Videos Chapter 6. Appendix Appendix A – Reference Documents Appendix B – Glossary of Terms (Klariti, 2018) Version 1.0 Release date 09/1/2018 Created by The Group Quick reference guide This section houses quick references to demonstrate step-by-step processes for some of the more common features. This will be a great document for our users and IT help desk staff to have. It will help answer some quick question for our customers allowing them to get back to work quickly without spending time researching how to do simple tasks. Template for Quick Reference Guide About This Guide This document is divided into the following chapters: Chapter 1 “Introducing Our Web App”. Chapter 2 “Key Features” gives an overview of the key features. (Introduction to Training Videos) Chapter 3 “Getting Started”, explains how to get started. (How to start Chat Session) Chapter 4 “System Administration”, describes general administration functions etc. Appendix A Appendix B Appendix C Glossary provides definitions of technical terms that appear in the guide. Conclusion Unit 3 This week the project was focused on creating a documentation guide for the application users and the system administrators. According to Alex Trica, “The presence of documentation helps keep track of all aspects of an application and it improves on the quality of a software product”. Documentation is a vital step that has throughout the development of the application, and one that transfer even after the completion of the project. In our case, three different documents were created to assist our users and managerial audience. (Trica, n.d.) A System Administrator’s Reference Guide was created to facilitate administrators on how to access web application and how to make any necessary changes. This guide also included how to install the Home+ Networking application, how to make changes to any type of setups, and also provided trouble shooting help. A User Manual and Release Description was also created which helps understand the Home+ Networking Application in more depth detail. This will help the users understand why the application was developed, a description of the application, installation of the system, step by step instruction and self-help videos. A Quick Reference Guide was also developed which it will be a great tool for both users and the IT helpdesk staff. This guide will provide quick reference answers of the most common questions and will also provide a quick overall look of the whole application. References Amazon Web Services. (2018, July 24th). AWS Application Discovery Service. Retrieved from AWS.amazon.com: https://aws.amazon.com/application-discovery/ DIETRICH, E. (2017, February 22nd). You Still Don’t Know How to Do Unit Testing (and Your Secret is Safe with Me). Retrieved from Stackify.com: https://stackify.com/unit-testingbasics-best-practices/ Klariti. (2018, September 4th). User Guide Templates. Retrieved from Klariti.com: https://klariti.com/user-guide/ Rosenbaum, S. (1987, October). Selecting the appropriate subjects: Subject selectionfor documentation usability testing. Proceedings of the 1987 IEEE International Professional Communication Conference, pp. 135-142. Schell, D. A. (1986, December). Testing online and print user documentation. IEEE Transactions on Professional Communication ( Volume: PC-29, Issue: 4, Dec. 1986 , pp. 87-92. TatvaSoft. (2015, April 15). Top 12 Software Development Methodologies & its Advantages / Disadvantages. Retrieved August 2018, from TatvaSoft: https://www.tatvasoft.com/blog/top-12-software-development-methodologies-and-itsadvantages-disadvantages/ Trica, A. (n.d.). Filtered. Retrieved September 2018, from The Importance of Documentation in Software Development: https://filtered.com/blog/post/project-management/the- importance-of-documentation-in-software-development Project Management for Instructional Designers by Amado, M., Ashton, K., Ashton, S., Bostwick, J., Clements, G., Drysdale, J., Francis, J., Harrison, B., Nan, V., Nisse, A., Randall, D., Rino, J., Robinson, J., Snyder, A., Wiley, D., & Anonymous. (DATE). Project Management for Instructional Designers. Retrieved from http://pm4id.org/ under Creative Commons Attribution 3.0 Unported. https://careered.libguides.com/wscb/format#s-lg-box-17269547)"

Tutor Answer

Drval
School: UT Austin

fin...

flag Report DMCA
Review

Anonymous
Excellent job

Similar Questions
Hot Questions
Related Tags

Brown University





1271 Tutors

California Institute of Technology




2131 Tutors

Carnegie Mellon University




982 Tutors

Columbia University





1256 Tutors

Dartmouth University





2113 Tutors

Emory University





2279 Tutors

Harvard University





599 Tutors

Massachusetts Institute of Technology



2319 Tutors

New York University





1645 Tutors

Notre Dam University





1911 Tutors

Oklahoma University





2122 Tutors

Pennsylvania State University





932 Tutors

Princeton University





1211 Tutors

Stanford University





983 Tutors

University of California





1282 Tutors

Oxford University





123 Tutors

Yale University





2325 Tutors