Post to the Group Discussion area:A list and short description of the classes and attributes you selected to store the system information. A simple list is acceptable at this point. You do not need to diagram the classes and attributes.A discussion of any questions you may have regarding the inclusion or exclusion of specific classes or attributes.I need something like what I sent those are examples and the case study is what the answer for the UML Diagram.
Meet with your group members. Based on the information posted in the Week 2 Group Project 1 area where the group developed a cohesive set of requirements for a comprehensive use case diagram, consider how to develop a high-level use case diagram that includes all functional requirements and sub-systems needed to complete the case study project.Each group member must complete a minimum of one sub-system use case diagram based on the decisions in the Group Project 1 area.Each group member must research the various costs and cost categories associated with designing, implementing, and maintaining a computer system for a period of five to seven years, including the appropriate cost categories and sub-costs.By Day 5Each group member will create and post a document to the Group Discussion area that includes the following:Their individual sub-system use case diagram(s) in the proper format, using the appropriate notation.The projected cost of designing, implementing, and maintaining the system for the next five to seven years, including the appropriate cost categories and sub-costs. A rationale is included for the projected costs.Days 5 and 6After examining the group member postings of the sub-system use case diagram(s) and costs supported by a rationale, respond to your group members helping to develop:The group high-level use case diagram in the proper format, using the appropriate notationA listing of each sub-system, the functional requirements included in each sub-systemThe name of the group member that completed each sub-system diagram.