R Y A N V A N C EDecember 07, 2016 7:00PM – 8:30PM
https://connect.johnshopkins.edu/sm4utara
O U T L I N E
• Biography• Introduction and Need• Requirements• CONOPS• Functional Concept• Physical Concept• Trade Study• Risk Management• Test Plan• System Specification• Summary of Final Concept and Further Work• Lessons Learned• Recommendations
B I O G R A P H Y
• Works for Raytheon• University of Florida - B.S. in Electrical Engineering • Johns Hopkins University – M.S.E in Systems Engineering
I N T R O D U C T I O N A N D N E E D
I N T R O D U C T I O N A N D N E E D
I N T R O D U C T I O N A N D N E E D –S Y S T E M S E N G I N E E R P R I N C I P L E S
A N D P R O C E S S
I N T R O D U C T I O N A N D N E E D – I R O N M A N D E S C R I P T I O N
R E Q U I R E M E N T S
User Needs
Operational Requirements
System Requirements
System / Subsystem Specifications
Component Specifications(Configuration Item Specs)
A-Spec
B-Spec
System Type
System Concept
FunctionalDescription
PhysicalDescription
InterfaceDescription
R E Q U I R E M E N T S – G E N E R AT I O N P R O C E S S
R E Q U I R E M E N T S – U S E R N E E D SNeed Number Need Description Requirement Type
N1 When the Iron Man System is operational, it provides real time physiological measurements. Qualitative (Subjective)
N2 When the Iron Man System is deployed, it operates for the duration of extended missions. Qualitative (Subjective)
N3 Iron Man maintains a constant datalink communication link to the Command and Control Unit. Qualitative (Subjective)
N4 Iron Man provides physiological data confidentiality. Qualitative (Subjective)
N5 Iron Man provides physiological data integrity. Qualitative (Subjective)
N6 Iron Man provides physiological data availability. Qualitative (Subjective)
N7 Iron Man provides processing capability for the physiological data. Qualitative (Subjective)
N8 Iron Man provides energy, fatigue, and injury assessments. Qualitative (Binary)
N9 Iron Man maintains current anti-tamper techniques. Qualitative (Binary)
N10 Iron Man provides software patches to prevent cyber attacks. Qualitative (Binary)
N11 Iron Man provides the ability to operate in any mission related environment. Qualitative (Subjective)
N12 Iron Man provides an affordable solution compared to other human performance devices. Qualitative (Subjective)
N13 Iron Man provides low latency and anti-jam capabilities. Qualitative (Subjective)
N14 Iron Man provides diagnostic and fault data. Qualitative (Subjective)
N15 Iron Man provides numerous communication paths. Qualitative (Subjective)
N16 Iron Man provides multiple configurations related to physiological data points. Qualitative (Binary)
R E Q U I R E M E N T S – R E Q U I R E M E N T S T R A C E A B I L I T Y M A T R I X ( R T M )
Requirement ID Number
Traceability Origination/Type Requirement Description KPPVerification
MethodRationale
OPER1.0 N5OriginatingQuantitative
The system shall acquire physiological data with no less than 95% accuracy as a threshold and no less than 97% as an objective.
X DNeed accurate physiological data picture
FUNC4.0 N1, N5, N7DerivedQuantitative
The system shall gather pathogen data with accuracy no less than 99%.
DCreates full physiological picture
PERF5.0 N6, N14DerivedQuantitative
The system shall initialize in 60 seconds or less. MEfficiency of operations
PERF45.0 N14Derived Quantitative
The Emergency Response subsystem shall provide health status information in no greater than 0.01 seconds.
DEmergency Response Time
INT4.0 N13, N15Derived Qualitative (Binary)
The system shall comply with DoD MIL-STD-188-181A for all SATCOM communication.
M Interoperability
CON27.0 N8, N12Derived Qualitative (Binary)
The system shall comply with the environmental, safety, and health (ESH) requirements in DoD Directive 5000.1.
I Safe Design
C O N C E P T O F O P E R AT I O N S
C O N C E P T O F O P E R AT I O N S –A M B U S H S N I P E R S C E N A R I O
F U N C T I O N A L C O N C E P T
• Functional analysis was conducted by– Translating the requirements into system functions– The high level functions were decomposed into lower level
functions– External interfaces (inputs and outputs to the system) were
established– All appropriate functional interfaces (input and outputs) were
defined
F U N C T I O N A L C O N C E P T – C O N T E X T D I A G R A M
F U N C T I O N A L C O N C E P T – T O P L E V E L F U N C T I O N A L B L O C K D I A G R A M
F U N C T I O N A L C O N C E P T – L O W E R L E V E L E N H A N C E D F U N C T I O N A L F L O W B L O C K
D I A G R A M ( E F F B D )
Function 5: Execute the SOF Mission Enhanced Functional Flow Block Diagram
F U N C T I O N A L C O N C E P T – L O W E R L E V E L
Function 5.2: Transmit GPS Coordinates Enhanced Functional Flow Block Diagram
Function 5.5: Deter Cyber Threats Enhanced Functional Flow Block Diagram
F U N C T I O N A L C O N C E P T – S Y S T E M L E V E L N 2 D I A G R A M
F U N C T I O N A L C O N C E P T – F U N C T I O N S T O R E Q U I R E M E N T S T R A C E A B I L I T Y
Function Number
Function DescriptionTraceability
Requirement Number Requirement DescriptionFUNC.0.0.0.LVL.0 Enhance SOCOM Missions OPER1.0,OPER2.0,
OPER3.0, OPER9.0, PERF2.0
OPER1.0 The system shall acquire physiological data with no less than 95% accuracy as a threshold and no less than 97% as an objective.
OPER2.0 The system shall deliver physiological data with a minimum range of 250 nautical miles.
OPER3.0 The system shall deliver physiological data with a maximum response time of 2ms.
OPER9.0 The system shall operate for no less than ninety days.
PERF2.0 The system shall maintain operation for at least ninety days.
FUNC.1.3.0.LVL.2 Load Encryption Key FUNC10.0, INT6.0
FUNC10.0 The system shall encrypt physiological data.
INT6.0 The system shall interface with DoDI 8420.01 for wireless data encryption.
FUNC.5.2.0.LVL.2 Transmit GPS Coordinates FUNC9.0, INT5.0 FUNC9.0 The system shall transmit data simultaneously on 2 or more communications pathways.
INT5.0 The system shall interface with the control unit using common data links or LOS communications.
P H Y S I C A L C O N C E P T
• Created a conceptual design for Iron Man– Visualizing how the functional architecture is realized by hardware
and software component– Interfaces were finalized– Physical concepts were constructed to define potential solutions– Informal and formal trade studies and analysis were utilized to
decide the best allocations and physical structure– Functions were allocated to physical elements
P H Y S I C A L C O N C E P T – T O P L E V E L P H Y S I C A L D I A G R A M
P H Y S I C A L C O N C E P T – T O P L E V E L N 2 P H Y S I C A L D I A G R A M
P H Y S I C A L C O N C E P T – S U B S Y S T E M P H Y S I C A L D I A G R A M
Subsystem 8: Emergency Response
P H Y S I C A L C O N C E P T – C O M P O N E N T T O F U N C T I O N A L T R A C E A B I L I T Y
Physical FunctionalPHYS.0.0.0.LVL.0 Iron Man System FUNC.0.0.0.LVL.0 Enhance SOCOM Missions
FUNC.3.2.0.LVL.2 Assess Iron Man Status FUNC.10.0.0.LVL.1 Support SOF Training
PHYS.1.0.0.LVL.1 Electrical Power Subsystem FUNC.1.0.0.LVL.1 Perform Pre-Mission Operations FUNC.8.0.0.LVL.1 Promote Maintenance Operations FUNC.8.1.0.LVL.2 Allow Pre-Mission Maintenance FUNC.8.2.0.LVL.2 Allow Post-Mission Maintenance
PHYS.2.1.4.LVL.3 GPS Antenna FUNC.1.3.2.LVL.3 Establish Secure Encryption Link FUNC.5.2.0.LVL.2 Transmit GPS Coordinates FUNC.5.2.1.LVL.3 Maintain GPS Satellite Downlink FUNC.5.2.2.LVL.3 Maintain GPS Satellite Uplink
PHYS.5.1.2.LVL.3 Nervous System Nano Transceiver
FUNC.1.2.4.LVL.3 Set Nervous System Measurement Points FUNC.2.0.0.LVL.1 Conduct Mission Operations FUNC.4.3.0.LVL.2 Receive Nervous System Status FUNC.4.3.1.LVL.3 Receive Cervical Nerves Status FUNC.4.3.2.LVL.3 Receive Lumbar Nerves Status FUNC.4.3.3.LVL.3 Receive Sacral Nerves Status FUNC.4.3.4.LVL.3 Receive Thoracic Nerves Status
PHYS.6.1.0.LVL.2 Encryption Nano Controller FUNC.1.3.0.LVL.2 Load Encryption Key FUNC.1.3.1.LVL.3 Download Encryption Key FUNC.5.5.0.LVL.2 Deter Cyber Attacks FUNC.5.5.1.LVL.3 Updates Current Anti-Tamper Techniques
PHYS.9.1.1.LVL.3 Gyroscope FUNC.4.0.0.LVL.1 Interact with the Human Body FUNC.4.6.0.LVL.2 Navigate Through Human Body
P H Y S I C A L C O N C E P T – E X T E R N A L I N T E R F A C E S
External System Subsystem Data Passed Interface Function
EXT. AOR EnvironmentPHYS.5.0 Data Acquisition Subsystem
EXT. Temperature, Pressure, Shock, Vibration
PHYS.5.0 Sensor Emissions
Atmosphere
Optical
Function 4.1 Emit Radio Frequency Energy
EXT. Cardiovascular-Pulmonary System
PHYS.5.0 Data Acquisition Subsystem
Raw Physiological Data RF SignalsFUNC.4.0 Interact with the Human Body
EXT. Control UnitPHYS.2.0 Communication Subsystem
Processed physiological data, physiological measurement point configuration, Bias Information
Wire (for pre-mission events)
RF Signals (via communication subsystem)
FUNC.1.0 Perform Pre-Mission Operations
FUNC.2.0 Conduct Mission Operations
EXT. Emergency Response Team
PHYS.2.0 Communication Subsystem
SOF Energy Level, SOF Fatigue Level, SOF Injury Level, GPS Location, Emergency Data
RF Signals (Data Link)
FUNC.7.0 Handle Emergencies
EXT. Endocrine SystemPHYS.5.0 Data Acquisition Subsystem
Raw Physiological Data RF SignalsFUNC.4.0 Interact with the Human Body
EXT. MaintenancePHYS.8.0 Emergency Response Subsystem
BIT Initialization, Status Reports, Measurement Points
Wire (Maintenance Connection)
FUNC.8.0 Promote Maintenance Operations
P H Y S I C A L C O N C E P T – I N T E R N A L I N T E R F A C E S
Physical Interface Component Description Data Passed Implementation Function
PHYS.1 – PHYS.2Electrical Power Subsystem –Communication Subsystem
Power PCB Power Trace
FUNC.1.0 Perform Pre-Mission Operations
FUNC.8.0 Promote Maintenance Operations
FUNC.8.1 Allow Pre-Mission Maintenance
FUNC.8.2 Allow Post-Mission Maintenance
PHYS.2 – PHYS.1Communication Subsystem – Electrical Power Subsystem
Power PCB Power Trace
FUNC.1.0 Perform Pre-Mission Operations
FUNC.8.0 Promote Maintenance Operations
FUNC.8.1 Allow Pre-Mission Maintenance
FUNC.8.2 Allow Post-Mission Maintenance
PHYS.3.1 – PHYS.3.2 Energy Dissipation – White Blood Cell Protective Case
HeatEnergy Absorption Wire
FUNC.2.2.1 Activate Processor Coolant
FUNC.4.1 Emit Radio Frequency Energy
FUNC.4.2 Release Heat
PHYS.6.1 – PHYS.6.3Encryption Nano Controller – Intrusion Detection Mechanism
Encryption Data, Timing Information
PCB TraceFUNC.1.3 Load Encryption Key
FUNC.5.5 Deter Cyber Attacks
T R A D E S T U D Y• During the Iron Man life cycle, there are risk areas or functionality that
required different exploration of the trade space. To assist in this decision process, multiple informal trade studies and one formal trade study was conducted.
• Informal Trade Studies included:– Navigation Subsystems– Communication Subsystems– Electrical Power
• Data acquisition of human physiological measurements is at the forefront for SOCOM’s human performance gap
– Formal Trade Study• Evaluate alternatives for Iron Man’s physiological data acquisition subsystem
– The objectives of the physiological data acquisition subsystem are:• Reliable physiological data collecting system• Accurate physiological data• Timely physiological data collection• Maximize physiological collection of information• Minimize impact to the human body
T R A D E S T U D Y - A LT E R N AT I V E SAlternative 1: MICROS Physiological Sensor Alternative 2: BioNomadix
Alternative 3: BioRadio Alternative 4: DSI In Vivo
T R A D E S T U D Y – C R I T E R I A , P A I R W I S E C O M P A R I S O N A N D W E I G H T I N G F A C T O R
C O M P U T A T I O N
A B C D ERow
Value Products
Nth Root of Row Value Products
Normalized Weighting
FactorA 1 0.200 7 3 0.250 1.05 1.0098 0.15B 5 1 8 6 0.200 48 2.1689 0.32C 0.143 0.125 1 1 0.111 0.0019 0.2855 0.04D 0.333 0.167 1 1 1 0.0556 0.5610 0.08E 4 5 9 1 1 180 2.8252 0.41
Total Sum 6.8504 1.00
Weight gBattery Life Days
Physiological Channel Bandwidth Mbps
Response Time msPhysiological
Measurement Accuracy %Cost $
1080
120
2.00
95
70140
160
1.80
99
Alternatives
4000 2500 5000 1000
DSI In VivoRaw Score
20100
105
1.60
95
6590
100
1.30
96
MICROS BIOPAC BioRadioUnitsCriteria
T R A D E S T U D Y – U T I L I T Y F U N C T I O N S
Weight (Grams) Scores<=35 1<=55 0.66<=75 0.33>75 0
Battery Life (Days) Scores>=150 1>=130 0.75>=110 0.50>=90 0.25<90 0
Physiological Channel Bandwidth (Mbps)
Scores
>=200 1>=150 0.66>=100 0.33<100 0
Response Time (ms) Scores<=1.00 1<=1.50 0.66<=1.95 0.33>1.95 0
Physiological Measurement Accuracy (%)
Scores
>=97 1>=96 0.66>=95 0.33<95 0
T R A D E S T U D Y – U T I L I T Y C U R V E S
T R A D E S T U D Y – U T I L I T Y C U R V E S ( C O N T )
T R A D E S T U D Y – W E I G H T E D U T I L I T Y S C O R E S
• Based on the readings, alternative 4 (DSI In Vivo) came as the most cost effective with weighted sum/unit cost of 0.2985.
• Sensitivity Analysis– Performed sensitivity analysis by assigning the weight to zero for each
criterion and analyzed how the values were affected– Alternative 4 was cost effective in 4 out of 5 sensitivity analysis readings
Raw Score
Utility Value
Weighted Utility Value
Raw Score
Utility Value
Weighted Utility Value
Raw Score
Utility Value
Weighted Utility Value
Raw Score
Utility Value
Weighted Utility Value
Weight 0.15 20 1 0.15 65 0.33 0.0495 70 0.33 0.0495 10 1 0.15Battery Life 0.32 100 0.25 0.08 90 0.25 0.08 140 0.75 0.24 80 0 0
Physiological Channel Bandwidth 0.04 105 0.33 0.0132 100 0.33 0.0132 160 0.66 0.0264 120 0.33 0.0132Response Time 0.08 1.6 0.33 0.0264 1.3 0.66 0.0528 1.8 0.33 0.0264 2 0 0
Physiological Measurement Accuracy 0.41 95 0.33 0.1353 96 0.66 0.2706 99 1 0.41 95 0.33 0.1353Weighted Sum
Cost ($)Weighted Sum / Unit Cost
(Weighted Sum *1000) / Unit Cost 0.000101225 0.00018644 0.00015046 0.0002985
DSI In Vivo
Criteria Weight
MICROS BIOPAC BioRadio
0.18644 0.15046 0.2985
0.4049 0.4661 0.7523 0.29854000 2500 5000 1000
0.101225
T R A D E S T U D Y - S U M M A R Y
• Compared and selected the technology based on the Iron Man mission– Cost was the main driver– Selection of alternatives were based on and compared
to a minimum requirements level• Alternative 4 is the cost effective solution however..
– Alternative 4’s current product is only used in animals and not humans
– Cost per unit will increase from $1,000• Alternative 2, BioNomadix’s BIOPAC device is the
overall selection
R I S K M A N A G E M E N T
• Continuous risk management process, to identify program risk, assess their possible impacts on schedule, cost, and technical performance throughout the lifecycle of the project
• 7 risks were identified, tracked, and mitigated during project life-cycle– 6 risks were identified in the
Project Proposal– 1 risk was identified in the
Conceptual Design
R I S K M A N A G E M E N T – R I S K S U M M A R Y
• Risk Summary– Risk Title identifying baseline level and the current Risk
Level– All risks are mitigated
Risk December Risk Level Baseline Risk LevelRisk 1: Nano-Networking Protocol
C2 L1 C5 L3
Risk 2: Nano-Antenna Material
C2 L1 C5 L3
Risk 3: Network Reliability C4 L3 C4 L4Risk 4: Bio-Cyber Terrorism C5 L2 C5 L4Risk 5: Unable to Finish SM4 Project
C5 L1 C5 L4*
Risk 6: Steep R&D Costs C3 L2 C3 L4Risk 7: Data Acquisition’s Human Impact
C3 L1 C3 L3
*Likelihood increased from the Project Proposal due to external circumstances
R I S K M A N A G E M E N T – R I S K 4 : B I O -C Y B E R T E R R O R I S M
Risk Title Bio-Cyber Terrorism
Description:
Bio-cyber terrorism causing Iron Man to become unreliable.
Initial Assessment:
Likelihood: 4
Consequences: 5
Description of Consequences if realized
The Iron Man system will be unreliable and cause damage to the SOF Operator.
R I S K M A N A G E M E N T – R I S K 4 : R I S K W A T E R F A L L , R I S K C U B E A N D R I S K
M I T I G A T I O N
Mitigation Plan L C Impact Description &
Rationale ID Associated Report Mitigation Action
A PROP -- 4 5 --
B RAR Establish NIST Risk Management Framework requirements 3 5
Creates an adaptable system against cyber threats.
C FAR -- 3 5 --
D CDR Special analysis on the Anti-Tamper Subsystem 2 5
Allows for penetration and patch testing in a closed environment.
E TS -- 2 5 -- F A-SPEC -- 2 5 --
T E S T P L A N
T E S T P L A NRequirement
NumberRequirement Description Relevant Subsystem Verification Method Integration Test Case Qualification Test Case
OPER2.0
The system shall deliver physiological data with a minimum range of 250 nautical miles.
Communication T TC.B01.002 QTD.003
OPER3.0
The system shall deliver physiological data with a maximum response time of 2ms.
Communication T TC.B01.002 QTD.003
FUNC11.0
The system shall prevent malicious hardware intrusion with no less than 98% accuracy.
Anti-Tamper D TC.B04.002 QTD.005
FUNC12.0
The system shall prevent malicious software intrusions with no less than 98% accuracy.
Anti-Tamper T TC.B04.002 QTD.005
INT35.0
The Anti-Tamper subsystem shall relay intrusion data to the Emergency Response subsystem with a lag time not to exceed 0.01 seconds.
Anti-Tamper A TC.B04.003 QA.008
S Y S T E M S P E C I F I C AT I O N
Total QuantitativeQualitative
Binary SubjectiveRequirements Analysis Report
88 36 (41%) 22 (25%) 30 (34%)
Functional Analysis
93 39 (43%) 24 (25%) 30 (32%)
Trade Study 94 40 (43%) 24 (25%) 30 (32%)Conceptual Design
96 42 (44%) 24 (25%) 30 (31%)
System Specification Report
176 155 (88%) 21 (12%) 0 (0%)
Test Plan - - - -
• Total number of requirements in the Requirements Analysis: 88• Total number of requirements in the System Specification Report: 176• Requirements growth: 100%
S Y S T E M S P E C I F I C A T I O N – K E Y P E R F O R M A N C E P A R A M E T E R S ( K P P S )
Number Requirement ID Number Capability KPP Threshold Objective
1 OPER1.0 AccuracyThe system shall acquire physiological data with no less than 95% accuracy as a threshold and no less than 97% as an objective.
Greater than 95% accuracy
Greater than 97% accuracy
2 OPER2.0 RangeThe system shall deliver physiological data with a minimum range of 250 nautical miles.
Greater than 250 nautical mile range
Greater than 300 nautical mile range
3 OPER3.0 Response TimeThe system shall deliver physiological data with a maximum response time of 2ms.
Response time less than 2ms
Response time less than 1ms
4 OPER9.0 DurationThe system shall operate for no less than ninety days.
System operates for greater than 90 days
System operates for greater than 120 days
5 FUNC10.0 ConfidentialityThe system shall encrypt physiological data within 2ms of receiving the physiological data.
NSA Type 1 Certification Quantum Encryption
6 CON1.0 AvailabilityThe system shall have an operational availability of 0.95 (95%) or greater as a threshold and > 97% as an objective.
Greater than 95% availability
Greater than 97% availability
7 CON22.0 Maintenance
The system shall have Mean Time Between Operational Mission Failures (MTBOF) be more than one thousand hours as a threshold and one thousand five hundred hours as an objective.
MTBOF greater than 1,000 hours
MTBOF greater than 1,500 hours
S U M M A R Y O F F I N A L C O N C E P T A N D F U R T H E R W O R K
• Iron Man system has demonstrated confidence through the series of reports– However, recommend series of reviews to include
Requirements Review, Functional Review, and Preliminary Design Review (PDR)
– Also, systems engineering buy-in is required by the customer and systems engineering company
• Iron Man preliminary concept design is promising to provide the Special Forces community with a significant human performance enhancer.– Iron Man depends heavily on the Internet of Bio-Nano
Things area of research in order to provide SOCOM with state-of-the-art capabilities
S U M M A R Y O F F I N A L C O N C E P T A N D F U R T H E R W O R K – N E X T S T E P S
Number Next Step
1 Updating all reports based on the A-Spec changes mentioned in the final report
2
Establishing technical reviews for the documentation created for Project Iron Man. The technical reviews need to assess:A. Iron Man’s Technology Readiness Level (TRL)B. Iron Man’s Entrance and Exit Criteria for the DoD MilestonesC. RequirementsD. FunctionsE. Preliminary Design
3Communicating with the Iron Man stakeholders in order to ensure “buy-in” for Iron Man. Assess the actual cost, schedule, and performance expectations. This can manage expectations for the deployment of Iron Man.
4After successful technical reviews, I recommend developing an Iron Man prototype in order to demonstrate the key technologies associated with the system. Also, the prototype can assist with mitigating future Iron Man risks before full rate production (FRP).
5 Collaborating with the DoD’s TALOS program in order to assess any possible integration or interface issues since the TALOS suit will be worn by SOF Operators in the 2018 timeframe.
L E S S O N S L E A R N E D
• Locate a mentor at least two semesters before starting the final project
• Learn how to research topics– Deep web searches using portal, gateway, or
resources• Personal Discipline• Watch Professor Olson’s Core Videos• Communicate/discuss with SME’s/Peers
R E C O M M E N D AT I O N S
• Add one lesson to each SE course related to the final project– Difficult to figure out how to apply past course topics to the
final project• Integrate Core into SE core courses
– Save 20+ hours during Final Project semester• Integrate past students to help future students with the
final project– Take advantage of a student’s recent project execution– The student can be a coach
• Create positive reinforcement– Award top projects each semester with a monetary prize.
• Establish alumni mentorship program– Shape future JHU SE Professors
C O N C L U S I O N• Achieved the objectives of the Master’s project by applying systems
engineering principles to the Iron Man system• Through proper application of essential SE skills and techniques,
demonstrated knowledge and understanding of a number of SE activities including the following:
– Definition of Needs and Objectives– Requirements Analysis and Concept of Operations (CONOPs)– Functional Analysis– Conceptual Design– Trade-Off Studies– Risk Management– Test and Evaluation– System Specification (A-Spec)
• My goal is to continue to learn and enhance my SE skills by: – Applying to the George Washington University Systems Engineering Ph.D. program – Achieving INCOSE Certified Systems Engineering Professional (CSEP) certification.
![Untitled-1 [cdn.cnetcontent.com] · 2012. 7. 18. · Title: Untitled-1 Author: 원주현/개발기획그룹\⠀䤀吀尩/사원/삼성전자 Created Date: 4/18/2012 9:58:47 AM](https://static.documents.pub/doc/80x56/5fe1ab4a67dfe6033c2100f2/untitled-1-cdn-2012-7-18-title-untitled-1-author-eoeeoeeeea.jpg)
