ENGR 500
New Product Design:
Logical Structure Assignment Instructions
Overview
In this assignment, you will develop the logical structure viewpoint for your new product design. This viewpoint should describe the hierarchical organization of parts (software and/or hardware) needed to realize the behavior described in the system functions viewpoint. It is used to identify all the parts needed to realize the system functions, and the means by which these functions are achieved. The logical structure viewpoint should be traceable to the operations, requirements and behavioral, and physical domains. The logical structure viewpoint is intended to capture the internal structure of the system from the perspective of the system.
Instructions
1. Analyze logical structure.
· specify logical structure using SysML Block Definition Diagram
2. Create/Complete a document based on assignment template.
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. 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 ru
ic for further details.
New Product Design:
system architecture Assignment Instructions
Overview
In this assignment, you will develop the system architecture viewpoint for your new product design. This viewpoint should describe how parts described in the logical structure viewpoint are encapsulated and interconnected to realize the behavior described in the system functions viewpoint. It is used to identify interfaces needed to realize the system functions, and the means by which these functions are achieved. The system architecture viewpoint should be traceable to the operations, requirements, behavioral, and physical domains. The system architecture viewpoint is intended to capture the physical interfaces of the system from the perspective of the system.
Instructions
1. Analyze system architecture.
· specify system architecture using SysML Internal Block Definition Diagrams
2. Create/Complete a document based on assignment template.
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)
Impress
1
New Product Design: Final Report Template
Name: _Houstin Claiborne___________
1
2
New Product Design: Logical Structure Template
Name: _____________________
2
3
New Product: Need/Opportunity
To design and reinvent a flat iron for domestic use with inbuilt intelligent features to increase the quality of the iron clothes with reduced complexity and ease of use. The cu
ent generation of flat irons are designed to remove the crease from the clothing but don't consider the ergonomics, product, or efficiency. These limitations can be resolved through a considerate redesign and development of the flat iron. The improvement process for the design approach will serve as a roadmap and theoretical stage for commodity improvement that will involve
oad research, analysis, and visioning. The design process will consider the use of IoT in the product for an efficient heating profile for a particular fa
ic, moisture, and pressure for a specific operation. The economic front of the product will also be considered through the design process, considering the classification of the product as a household item for generals.
3
4
Benchmark Analysis
Product Customer Segment 1
Tech Savvy Customer Segment 2
Housewife Customer Segment 3
Minimalists
Smart Feature
Desirable Maybe Maybe
Connectivity with Mobile Desirable Maybe Not Desirable
Energy Efficiency Desirable Desirable Desirable
Lime Scale Desirable Desirable Desirable
Ergonomic Maybe Maybe Desirable
Low Price Ok with high price Desirable Maybe
4
5
Analysis/Summary of User Needs
The cu
ent generation of flat irons has many vital issues that are needed to be solved for ergonomic and organic use in the home. Consumers are looking for the flat iron design to be cohesive with the other household according to the environment. The water refilling tank to be more efficient and should provide moisture based on the fa
ic demand, which is solved through the IoT system. The system will take much less energy to operate as the efficiency of the heating element can be improved, and the inbuilt IoT design compared to the conventional flat irons. The ergonomic design of the iron will lead to ease of usage for the consumer with the iron profiles available within the system. The Lime scale will be improved with the introduction of the IoT system in the flat iron, which will enhance the crease removal from the clothing.
5
6
Problem Statement
To design and develop a smart flat iron for domestic clothing which can operate efficiently under various environmental conditions for various variety of fa
ics. The shape of the product has to be ergonomically considered for ease of use by the consumer. These combined with an IoT system inbuilt into the flat iron will provide the product a local database based on the consumer crease liking and will perform accordingly. These features will have to be added to the flat iron economically as possible for the products feasibility in the market.
6
7
Requirements Table
Requirement ID [Unique Identifier] Requirement Name Requirement Description Requirement Rationale Requirement Type
R.1.1 Cost System must cost less than $30
Must be affordable Stakeholde
R.1.2 Featured Marketing Constant Influence of product on consumer Product must be visible to customer Stakeholde
R.1.3 Functionality Provides better functionality compared to competition Must be viable in market with competitors Stakeholde
R.1.4 Quality Quality Control on product Providing quality product with end user in mind Stakeholde
R.1.5 Supply Constant supply of product Market availability Stakeholde
R.1.6 Efficient Higher efficiency of the product Power consumption can be reduced Stakeholde
7
8
Requirements Table
Requirement ID [Unique Identifier] Requirement Name Requirement Description Requirement Rationale Requirement Type
R.2.1 Variable Heating Profile Variable heating profile for different fa
ic configuration
To provide seamless crease System
R.2.2 IoT system Implementation of IoT system for smart features Smart feature to observe and learn from the end user to provide best heating and steaming profiles System
R.2.2.1 Inbuilt database for profiles Generate different heating profiles Initial profiles for different fa
ics System, Child
R.2.3.2 Learning through sensor Getting data based on the history of the equipment use The learning will provide the system to perform efficiently System, Child
8
9
Requirements Table
Requirement ID [Unique Identifier] Requirement Name Requirement Description Requirement Rationale Requirement Type
R.2.4 Material Selection Adequate material selection for proper heat discharge
To delay or extend the damage of the flat surface System
R.2.5 Steam Injection Proper container to ca
y the stem and proper heating and injecting mechanism For proper or uniform release of stem at a proper temperature based on the fa
ic System
R.2.6 Ergonomic Design for handle, flat surface and steam injection points Design of flat iron be such that the end user can use it for extended period of time Help the end user to perform task with no load on the wrist or experiencing heating or sweating in hands System, Child
9
10
System Operation
10
11
System Functions
[...use as many slides as needed]
11
12
Logical Structure
[...use as many slides as needed]
12
13
System Architecture
[...use as many slides as needed]
13
Biblical Integration
14
2 Thessalonians 3:6-8 Now we command you,
others, in the name of our Lord Jesus Christ, that you keep away from any
other who is walking in idleness and not in accord with the tradition that you received from us. For you yourselves know how you ought to imitate us, because we were not idle when we were with you, nor did we eat anyone's
ead without paying for it, but with toil and labor we worked night and day, that we might not be a burden to any of you. This scripture
ings me to the point of having accountability for ones own actions. Whether it is a stake holder building a product for the masses or your person self going day to day, Preparations and thoroughly sound ethical judgement is necessary.
14
Biblical Integration
15
James 4:13-14 Come now, you who say, “Today or tomo
ow we will go into such and such a town and spend a year there and trade and make a profit”— yet you do not know what tomo
ow will
ing. What is your life? For you are a mist that appears for a little time and then vanishes. This scripture
ings me to a place where planning and preparation is essential to accomplishing all goal. Having faith and wishing for the best for a future vision or goal is not enough you must set out visionary key factors and benchmarks to track one’s progress. The bible is telling us time is not to be wasted an to garner fruits of our labors we must be steadfast and organized in our strategy.
15
16
Source Documents/References
Walden, D., Roedler, G., Forsberg, K., Hamelin, R., Shortell, T. (Edition 2015), Systems Engineering Handbook, Wiley
Gue
ero, H. M. D. A., Costas, E., & García, P. M. A. Why do we iron clothes? Tracking its origins based on a sanitary hypothesis.
Ba
ón-Cedeño, A., Vila, M., Martí, M. A., & Rosso, P XXXXXXXXXXPlagiarism meets paraphrasing: Insights for the next generation in automatic plagiarism detection. Computational Linguistics, 39(4), XXXXXXXXXX.
English Standard Version Bible XXXXXXXXXXESV Online. https:
esv.literalword.com
16
17
Logical Checklist
[ ] Repeat analysis of stakeholder needs and requirements
[ ] specify stakeholder requirements
[ ] Repeat analysis of system requirements
[ ] specify system requirements
[ ] Repeat analysis of system operation
[ ] specify system operation using SysML Use Case Diagram
[ ] Repeat analysis of system functions
[ ] specify system functions using SysML Activity Diagrams
[ ] Analyze logical structure
[ ] specify logical structure using SysML Block Definition Diagram as needed
[ ] Create/Complete a document based on assignment template
[ ] Export/Upload completed document as a pdf file
17
18
Final Checklist
[ ] Repeat analysis of stakeholder needs and requirements
[ ] specify stakeholder requirements
[ ] Repeat analysis of system requirements
[ ] specify system requirements
[ ] Repeat analysis of system operation
[ ] specify system operation using SysML Use Case Diagram
[ ] Repeat analysis of system functions
[ ] specify system functions using SysML Activity Diagrams
[ ] Repeat analysis of logical structure
[ ] refine logical structure using SysML Block Definition Diagram as needed
[ ] Analyze system architecture
[ ] specify system architecture using SysML Internal Block Definition Diagrams
[ ] Create/Complete a document based on assignment template
[ ] Export/Upload completed document as a pdf file
18