CmpE 232 – Component-Based andPart 1: Component-Based Software DevelopmentPart 2: Stable Pattern-Based Software DevelopmentPersonal Digital Assistants in the Modern BattlefieldBriefing of Dismounted Soldiers on Operations OrdersABSTRACTProblem DescriptionOriginalDescription of the ProgramRequirementsCmpE 232 – Component-Based and Reuse-Oriented SW EngineeringPractice Problem (5)___________________________________________________________This problem statement was developed byTeam: OPORDMember: Rollie Olson, Robert Durtschi, Buu Che, and James Leege___________________________________________________________Part 1: Component-Based Software DevelopmentAnswer the following questions:(1) Document all of the Use Cases in Your Problem:(a) Identify two of the use cases(b) Identify Actors and their roles(c) Identify corresponding classes(d) Describe the Use Case Repeat the process for at least two of the use cases. Use the following Use Case Template to document your Use CasesAll the fields must be filled for each use case.1. Use Case Id.2. Use Case Title1. Actors & Corresponding Roles2. Classes5. Corresponding Attributes6. Corresponding Interfaces (services or operations)7. Use Case Description – Feel free to use pre- and post-conditions where appropriate.8. Alternatives(2) Create CRC cards for the existing classes.(CRC stands for Class Responsibility and Collaborations)(3) Prepare traditional models for this problem showing at least 10 relationships among the object classes in this problem, including associations, aggregations, and generalizations. Show multiplicities in your diagrams. You must name attributes and operations for each class. Use association and role names when needed. (4) Create Sequence diagrams. Sequence diagrams will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagrams 1can describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment.(5) Create Components diagrams for as many components in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component diagrams. Address implementation issues that are related to these component diagrams if any.Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio formats Part 2: Stable Pattern-Based Software Development(1) Use Cases. Update #1. Document all use case templates with software stability in mind. Use the following template to document your use cases. 1. Use Case Id.2. Use Case Title3. Actors & Corresponding Roles4. Classes1. Corresponding Attributes2. Corresponding Interfaces3. Class Classification: EBTs, BOs, IOs 4. Use Case Description1. Alternatives(2) Create or/and update all the CRC cards for all the (EBTs, BOs, Roles) in your stability model of your team project (CRC stands for Class Responsibility and Collaborations). (3) Class diagram (Stability Model). Create a new Class diagram of your team problem based on the EBTs, BOs, and IOs – Describe your stability model. Class descriptions should include all attributes and methods for the class. All class relationships (associations, aggregations, dependencies, and specializations) should be included in the class diagram. association classes, interface classes, constraints, interfaces, tagged values and/or stereotypes, and notes must be included in the class diagram. (4) Sequence diagrams. Create Sequence diagrams with stability in mind that will be used to "realize" Use Cases. All Use cases should be described through sequence diagrams. The sequence diagrams can describe the same Use Cases that a flow of events was created for in the Use Case portion of the assignment. (5) Create Components (or Stable Patterns) diagrams based on Software Stability for as many components (Patterns) in your project as you wish, and show all the interfaces, usage dependencies, ports, and connectors. Document the component (stable pattern) diagrams. Address implementation issues that are related to these component diagrams if any. Please submit your answer electronically as MS word documents before the next lecture. – Feel free to submit all diagrams in Rational Rose or Visio formats ___________________________________________________________2Personal Digital Assistants in the Modern BattlefieldBriefing of Dismounted Soldiers on Operations OrdersABSTRACT“In an attempt to remove as much chance of misunderstanding as possible, this communications process of intent and orders has been refined over the years. Military terms are used, each with a specific meaning, and maps and other graphic symbols are also used, each with it’s own specific meaning. In spite of this, normal human dynamics, chance occurrences, and enemy actions lead to misinterpretations…”1“Since the entire process of battle command – problem solving, dissemination of the solution, and actual physical execution – tends to take a long time, commanders are always looking for ways to reduce that time”2 “The targets I have chosen are shown on my map. Make sure you mark them on your map before you leave.”3The situation described by General Franks has improved greatly since Desert Storm in 1991. Almost all vehicles in the modern United States Army contain an embedded computer system that can display warning orders, operation orders (OPORD), or fragmentary orders (FRAGO). These orders can be loaded directly to the computer using a special device, or received over the tactical internet, also a quite recent development. The soldier who is mounted on such a vehicle has access to the exact information as conveyed by his superior and almost instantaneous updates if the situation changes. However, as the above quote from a recent sample Platoon Operation Order illustrates, the last frontier of the 21st century electronic battlefield is the foot soldier. Ground troops, dismounted soldiers, still rely on handwritten orders and paper maps, the same methods available to General Franks in Desert Storm, to Patton and Bradley in World Ward II, or for that matter, to Washington in a much earlier war. 1 “Into The Storm – A Study in Command” by Tom Clancy with General Fred Franks Jr. page 1472 IBID.3 “Example Platoon OPORD”, Section 3.a - http://www.acs.ohio-state.edu/arotc/opord.html3Infantry tactics build on 5 principles