The SDLC is the framework that allows the IT team to use various software development methodologies. Depending on the chosen methodology, the considerations and impacts on the organization will differ. Once the methodology is chosen, the planning stage of the SDLC begins. Planning is a critical part of every software project; this is the stage in which project goals, a detailed resourcing plan, the project team, methodology, and CASE tools are determined. Every project has the potential to succeed or fail in myriad ways, based on these choices. For the first part of this assignment, use the context of your current workplace or a familiar organization along with the readings from Units 1 and 2 to: Choose two software development methodologies (waterfall, spiral, different types of agile) and analyze their effects on the SDLC for software-intensive systems. Identify key characteristics and conduct a brief SWOT analysis, supported with academic literature. Refer to the SWOT Analysis media piece linked in Resources to help you complete this. Analyze the content of SDLCs based on each of the two software development methodologies. Identify critical differences among the methodologies that contribute criteria for the selection of the best-fit software development methodology for your organization’s needs. Assess the tools used and the decisions made in software system project planning to help ensure successful projects that align with organizational goals. Analyze the relationship between organizational strategic planning and system acquisition planning, including the key players and roles. Determine who should be involved in system planning and when they should be involved; support this with a rationale. Analyze the characteristics needed of team members for system development or acquisition and balance it with the available workforce resources. Evaluate criteria for choosing in-house implementation, hiring specialized consulting teams, and/or selecting complete outsourcing teams. Now, consider the analysis phase of the SDLC and the ways in which each development methodology addresses it. In Units 3 and 4, we addressed methods for modeling the requirements using process/logic models such as data flow diagrams (DFD) and data models such as E-R diagrams; these approaches are used to gather requirements and to communicate with various stakeholders to obtain these requirements. In defining and documenting systems requirements, the vague term process modeling refers to various levels of abstraction and types of modeling of the processor logic that represents the system problem. Depending on the application, algorithms may drive a process model. Data models represent the other half of requirements modeling. UML can be used in data modeling as well as design. For the second part of this assignment, review the approaches to gathering, defining, and documenting requirements. The completeness, order, and depth of the requirements represented at any point in the SDLC depend upon the development methodology chosen. Address the following in this part of your assignment: Compare two logic models for use on a software development project, including the strengths and weaknesses of each. Compare two data models for use on a software development project, including the strengths and weaknesses of each. Determine the criteria for choosing the appropriate process/logic and data models for systems development and who should determine those criteria. Written communication: Written communication is free of errors that detract from the overall message. APA formatting: Your paper should demonstrate proper APA formatting and style. You do not need to include a cover page or abstract, but be sure to include your name, assignment title, and page number in the running head of each page. Use meaningful section headings to clarify the organization and readability of your paper. The number of references: You may use the resources provided to help you with your research and writing; the sources should be appropriately cited throughout your paper and in your reference list. Suggested paper length: 3,000 words. Font and font-size: Times New Roman, 12 point
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.Read more
Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.Read more
Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.Read more
Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.Read more
By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.Read more