This week we covered the analysis of features and how it can be tricky to get th

This week we covered the analysis of features and how it can be tricky to get the correct analysis done. To better grasp, we will use one of the more common methods for showing stakeholders the “lay of the land,” so to speak, of a program.
In this week’s discussion, you will choose one program and build out a robust UML diagram of the features and methods (to the best of your ability) and a data flow diagram. This single diagram should show where the data enters the program, how it interacts with the methods/features of the program, and how the data exits the program. This diagram is helpful in that it will show how complex a program can be and allow you to build out a UML with an ETL (Extract, Transform, and Load) movement simultaneously.
What you should do:
Tell the class about the program you selected
What does it do
How does it do it
Draw a UML which shows
All the functions of the program
How the data move from function to function
Write a brief description (3-4 sentences) that describes the flow of the program
APA Note: Using citations in your discussion posts is important to avoid plagiarism and paraphrasing offenses (refer to the syllabus and Herzing’s catalog). It is also an important part of the academic discussion to provide a scholarly reference for your comments; this gives your audience the opportunity for further research on the topic discussed. There are different guidelines or formats used for citing references. Herzing University has chosen the APA format for reference citation. Please refer to the Library for information on how to cite a reference using the APA format.