You are now ready to start the development effort for the financial management software. The CIO stopped by your office and stated that before the project could begin he wants you to prepare a risk assessment, human resource plan, and work breakdown schedule for the project for his review and approval. The CIO also wants to validate that you have the appropriate stakeholders identified for the project. Build upon the assignment deliverable from Unit 2 to help you prepare You prepared a risk assessment and human resources plan in the previous week. Based on your previous report and after reviewing the project plan, the CIO has identified several concerns. The CIO has asked you to conduct research on project budgeting and estimation tools. You have been asked to incorporate project estimates techniques using PERT, Analogous, and Delphi into the software development plan. Make sure you also could include a discussion on Metrics as part of the project deliverable.

Also you will be submitting the overall plan, known as the Key Assignment Draft in the upcoming Discussion Board for a peer review. Please make sure your overall plan includes the items mentioned above and these items:

  • a company name
  • identify a software application/software development project
  • determine which software development method you would use and justify your recommendation
  • provide an outline of the software development project plan based on the development method you selected
  • also include project oversight considerations such as risk management, scheduling, budget, and configuration management

Explanation & Answer length: 15 pages1 attachmentsSlide 1 of 1

  • attachment_1attachment_1


Running Head: WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY Waterfall Software Development Methodology Hollie Gates CTU SWE 440 Date4.09.21 Waterfall Software Development Methodology WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY 2 Introduction The waterfall methodology is a systematic software development process, where the processes flow steadily toward completion through the project phases, which involves analysis, design, development, and testing. The methodology involves documenting the project in advance, organizing the user stories, user interface and other features, and reviewing the outcomes (Balaji & Murugaiyan, 2017). Thus, the waterfall methodology involves a comprehensive process, raising significant concerns about quality management. However, ISO and IEEE standards can help the project team utilize the waterfall methodology effectively to achieve success. This report explains how I will incorporate the ISO and IEEE standards into developing the company’s financial management system. Analysis The product development team analyzes the requirements and understands the problem. Connor (2015) considers the analysis phase research; therefore, it doesn’t include building. During this phase, the team attempts to ask relevant questions and secure answers they need to build the product requirement. In this sense, I will help ISO standards to ensure the quality, consistency, and safety of the financial management system. For example, I will use ISO standards to analyze user needs and identify software features that meet the needs. Connor (2015) reveal that ISO standards allow an organization demonstrates their reliability to suppliers, purchasers, government, and business partners. Thus, I will use ISO standards to understand the company’s safety and quality issues and design a financial system to improve performance. System analysis is crucial because it provides an avenue for solutions in the system through various tasks involved in the analysis. Laporte & Cinoyt (2016) argue that the project team can easily modify the system’s quality through the analysis. The primary purpose of the WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY analysis phase is to design a high-quality system that meets the company’s expectations. In this regard, I will use IEEE standards to research current technological trends to formulate a highquality system. While IEEE standards emphasize innovation, education, and standardization, I will use them to research the appropriate system based on the company’s needs. For example, I will research a successful company that uses the financial system to determine how the client may benefit from the system or manage risks. Design The software developers design a technical solution to the problems revealed by the product requirements, including layouts, scenarios, and data models. Connor (2015) states that the design phase is accomplished by documentation for each requirement. The documentation will allow other team members to review the system for validation. While documentation requires detailed information on how the system will meet the company’s needs, I will use ISO standards to locate resources and ensure sustainability. According to Connor (2015), sustainability is increasingly becoming important, and ISO standards help an organization deal with environmental and social challenges. In essence, the financial field requires comprehensive standards to enhance trust and security. While comprehensive systems are usually expensive, ISO standards will help me develop a sustainable system that saves the company money and improve its image. One of the company’s expectations is to get a system that deploys highly focused products and services. Laporte & Cinoyt (2016) found that today’s system developers target the intersection between customer satisfaction and profitability by designing the most valuable systems. Automation and commoditization of high-margin processes are crucial for financial systems. While IEEE standards promote innovation, I will use them for innovative designs that 3 WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY 4 facilitate automation. Moreover, Laporte & Cinoyt (2016) argue that financial organizations must invest in innovative systems that provide personalized customer services. I will use IEEE standards to understand the ever-changing customer needs and design features that promote customer satisfaction. For example, I will design a system that sends personalized messages to customers or provides real-time communication to improve customer experience. Implementation After the team approves the design, technical implementation begins. According to Gonzales (2016), implementation is the shortest phase because the team has already conducted research and designed the system. However, implementation can be difficult because it involves different departments as the company strives to use proven methodologies. I will use ISO standards to ensure proven methodologies and minimize the implementation time. ISO standards are accepted in many countries. Therefore, they provide authentic guidelines to enhance implementation (Gonzales, 2016). In essence, Gonzales (2016) observed that many implementation processes fail due to a lack of accurate planning in the initial stages. Inadequate resources and unforeseen problems contribute to implementation failure. Thus, I will ensure ISO standards in the initial steps to enhance implementation. For example, identifying current issues in financial systems will help me plan adequate resources to overcome implementation challenges. IEEE standards will guide me to engage stakeholders in the implementation process and meet their needs. Stakeholder engagement is one of the goals of IEEE standards (Laporte & Cinoyt, 2016). Effective stakeholder engagement will help align the system to the company and consumer needs. IEEE standards emphasize that software implementation should recognize the end-user expectations and needs. In this sense, IEEE standards will help me prioritize end-user WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY 5 participation in the implementation to achieve their business objectives. End-use involvement will make the end-user more receptive to potential changes because they have firsthand experience of the system. Laporte & Cinoyt 2016 (2016) state that a company must overcome the user-design communication gap to implement a successful system. In this case, IEEE standards will help me engage end-user in implementing various efficiencies, restrictions, and database management principles. Testing After completing the implementation, the team should test the system before releasing it to the client. The software testing team will use the user case scenarios and design documents to create their test cases. Software testing is the process of verifying and validating the system to ensure that it meets the technical requirements. Connor (2015) argues that software testing aims at finding faults and finding measures to improve the system’s efficiency, accuracy, and usability. In this regard, I will use ISO standards to ensure effective testing, enhancing the system’s functionality and performance. ISO standards are essential for the two steps of testing: verification and implementation since they promote quality management. Technology trends raise significant concerns about system security as attackers change their techniques daily to access systems. Therefore, the testing team must use updated testing techniques to identify the system’s weaknesses and fix them accordingly. While IEEE standards promote updated knowledge regarding software development, I will use them to find effective testing techniques. For example, IEEE standards will help install security control that can identify, detect, and respond to attacks. Conclusion WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY ISO and IEEE standards enhance the waterfall methodology by improving the software development faces. Innovation and quality management are some of the aims of ISO and IEEE standards. Therefore, the standards help a team develop an effective system that meets organizational needs and improves user experience. Teams should use the standards to identify and fix the problems that might arise during the project and develop an innovative system. 6 WATERFALL SOFTWARE DEVELOPMENT METHODOLOGY References Balaji, S., & Murugaiyan, M. S. (2017). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30. Connor, R. V. (2015, June). Developing software and systems engineering standards. In Proceedings of the 16th International Conference on Computer Systems and Technologies (pp. 13-21). Gonzales, R. (2016). Developing the requirements discipline: Software vs. systems. IEEE software, 22(2), 59-61. Laporte, C. Y., & Cinoyty, R. V. (2016). Systems and software engineering standards for very small entities: accomplishments and overview. Computer, 49(8), 84-87. 7

Do you similar assignment and would want someone to complete it for you? Click on the ORDER NOW option to get instant services at

Do you have a similar assignment and would want someone to complete it for you? Click on the ORDER NOW option to get instant services at We assure you of a well written and plagiarism free papers delivered within your specified deadline.