THE POWER POINT IS JUST A TEMPLATE FOR THEM TO UNDERSTAND THE ASSIGNMENT
ENGR 500 REVERSE ENGINEERING: SYSTEM ANALYSIS ASSIGNMENT INSTRUCTIONS OVERVIEW In this assignment, you will develop a Wasson MBSE model of your reverse engineered product (i.e., system of interest). These model viewpoints (stakeholder requirements, system requirements, system operation, system functions, logical structure, and system architecture) should collectively describe the system of interest using the SysML modeling language, Papyrus modeling tool, and the Wasson MBSE modeling method. I NSTRUCTIONS 1. Analyze stakeholder needs and requirements. specify stakeholder requirements 2. Analyze system requirements. specify system requirements 3. Analyze system operation. specify system operation using SysML Use Case Diagram 4. Analyze system functions. specify system functions using SysML Activity Diagrams 5. Analyze logical structure. specify logical structure using SysML Block Definition Diagram 6. Analyze system architecture. specify system architecture using SysML Internal Block Definition Diagrams 7. Create/Complete a document based on assignment template. 8. Export/Upload completed document as a pdf file. Recommendations 1. Refer to Chapter 4 section on writing good requirements. 2. Use Papyrus to create Use Case Diagram. 3. Use Papyrus to create Activity Diagrams. 4. Use Papyrus to create Block Definition Diagram. 5. Use Papyrus to create Internal Block Diagrams. 6. Verify traceability between model perspectives (i.e., Requirements, Operations, Behavioral, Physical). Note: These are minimal requirements. To achieve a higher grade on this assignment, you must exceed these requirements. See the grading rubric for further details. Impress 1 / Name: Houstin Claiborne Reverse Engineering: Problem Statement Template 2 / System of Interest (SOI) Product Name: Osters Blender Product/Model ID:Duralast Classic Manufacturer: Osters 3 / Osters Blender -SOI 4 / Osters Disassembly - [STEP 1 REMOVE BASE ] Center Mechanical / Electrical Device Analysis/Summary of User Needs The current generation of food blenders has many vital issues that are needed to be solved for ergonomic and organic use in the kitchen. These fundamental issues include high price, high noise, and limitations concerning the temperature of food to be blended. These limitations can be solved by redesigning the blender. The improvement process for the design approach will serve as a roadmap and theoretical stage for commodity improvement that will involve broad research, analysis, and visioning. The strategy will include to study the effect of the motor power and RPM used in the blender for the noise level including the cutting blade shape as these are the most important factor for an ergonomic and efficient food blender. Furthermore, when the strategy is developed, then the design will reinvigorate it by producing commodities in a better way delivering on the strategic promise. This reverse engineering project is introduced to create a commodity idea for a redesigned kitchen food blender. The redesigned blender is intended to provide the best blending experience with various blending modes for chunky, hot, and cold foods and vegetables taking economic and ergonomic constraints. Problem Statement To design and reinvent a domestic food blender to reduce noise pollution that is produced by the current generation of food blenders Source Documents/References Wells, Pete. ( June 25, 2008). “The Pulse of Summer: Blender Drinks Are Back” Retrieved from https://www.nytimes.com/2008/06/25/dining/25blender.html 12 / Requirements Table [...use as many slides as needed] Requirement ID [Unique Identifier]Requirement NameRequirement DescriptionRequirement RationaleRequirement Type R.1.1CostSystem must cost less than $30 Must be affordableStakeholder R.1.2Stakeholder R.1.3Stakeholder …. R.2.1System R.2.2System R.2.3System R.2.3.1System, Child R.2.3.2System, Child R.2.4System … 12 13 / System Operation 13 14 / System Functions [...use as many slides as needed] 14 15 / Logical Structure [...use as many slides as needed] 15 16 / System Architecture [...use as many slides as needed] 16 17 / Source Documents/References [Reference 1] [Reference 2] [Reference 3] [Reference 4] …. 17 18 / Checklist [ ] Refine user needs/Develop requirements [ ] specify stakeholder requirements [ ] specify system requirements [ ] Analyze system operation [ ] specify system operation [ ] specify system functions [ ] Analyze how parts interact [ ] specify logical structure [ ] specify system architecture [ ] Create/Complete a document based on assignment template [ ] Export/Upload completed document as a pdf file 18 Checklist [ x] Determine user needs [x ] Develop problem statement [ x] Create/Complete a document based on assignment template [ x] Upload completed document as a pdf file [ x] All sections of Assignment Template Completed