In Week 3 you examined the analysis phase of the SDLC and the ways in which each development methodology addresses it. Week 3 focused on approaches for gathering requirements and communicating with various stakeholders to obtain those requirements and addresses methods for modeling the requirements, using techniques such as data flow diagrams (DFD) and the unified modeling language (UML).
In defining and documenting systems requirements, the vague term “process modeling” refers to various levels of abstraction and types of modeling of the process or logic that represent 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.
Review the approaches to gathering, defining, and documenting requirements. The completeness, order, and depth of the requirements represented at any point in the SDLC depends upon the development methodology chosen.
Address the following in your assignment:
Compare two process/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.
Your paper should be approximately 1,000 words, demonstrate critical thinking, and adhere to APA style and format.
