This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the Third unit in the syllabus are covered. I hope it will be helpful to the students.
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the FIFTH unit in the syllabus are covered. I hope it will be helpful to the students.
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the fourth unit in the syllabus are covered. I hope it will be helpful to the students.
This is the power point presentation for System Engineering UNIT-2 for the students who are studying in Fourth Semester of various engineering disciplines in the institutes affiliated to RGPV, Bhopal. I hope it will be helpful to them
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the first unit in the syllabus are covered. I hope it will be helpful to the students.
Systems Engineering is a very broad , overarching, and generally applicable engineering discipline. Many types of systems are developed using SE. These include biomedical systems, space vehicle systems, weapon systems, transportation systems, and so on.
Systems Engineering involves the coordination of work performed by engineers from all other engineering disciplines (electrical, mechanical, computer, software, etc.) as required to complete the engineering work on the project/program.
Interdisciplinary Science, Engineering, and Management,
Systems theory,
Systems thinking,
System development life cycles,
Synergy,
Project management,
Engineering Domains (Industry 4.0) , and
Communities (INCOSE and IEEE SMC Society).
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the FIFTH unit in the syllabus are covered. I hope it will be helpful to the students.
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the fourth unit in the syllabus are covered. I hope it will be helpful to the students.
This is the power point presentation for System Engineering UNIT-2 for the students who are studying in Fourth Semester of various engineering disciplines in the institutes affiliated to RGPV, Bhopal. I hope it will be helpful to them
This is a power-point presentation prepared for the students who are studying SYSTEM ENGINEERING in Fourth Semester (CBCS) of the branches of colleges affiliated to RGPV, Bhopal (M.P.). In this presentation, topics of the first unit in the syllabus are covered. I hope it will be helpful to the students.
Systems Engineering is a very broad , overarching, and generally applicable engineering discipline. Many types of systems are developed using SE. These include biomedical systems, space vehicle systems, weapon systems, transportation systems, and so on.
Systems Engineering involves the coordination of work performed by engineers from all other engineering disciplines (electrical, mechanical, computer, software, etc.) as required to complete the engineering work on the project/program.
Interdisciplinary Science, Engineering, and Management,
Systems theory,
Systems thinking,
System development life cycles,
Synergy,
Project management,
Engineering Domains (Industry 4.0) , and
Communities (INCOSE and IEEE SMC Society).
Model-Based Systems Engineering (MBSE) is an ambiguous concept that means many things to many different people. The purpose of this presentation is to “de-mystify” MBSE, with the intent of moving the sub-discipline forward. Model-Based Systems Engineering was envisioned to manage the increasing complexity within systems and System of Systems (SoS). This presentation defines MBSE as the formalized application of modeling (static and dynamic) to support system design and analysis, throughout all phases of the system lifecycle, and through the collection of modeling languages, structures, model-based processes, and presentation frameworks used to support the discipline of systems engineering in a model-based or model-driven context. Using this definition, the components of MBSE (modeling languages, processes, structures, and presentation frameworks) are defined. The current state of MBSE is then evaluated against a set of effective measures. Finally, this presents a vision for the future direction of MBSE.
Præsentationen blev holdt ved InfinIT-konferencen SummIT 2013, der blev afholdt den 22. maj 2013 på Axelborg i København. Læs mere om konferencen her: http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/summit_2013.htm
Competency is a measure of an individual’s ability in terms of knowledge, skills, and behaviour to perform a given role in the Systems Engineering processes. The competency planning and deployment of Systems Engineering competencies are considered as one key factor in the successful re-industrialisation and digital transformation of Europe.
ISECF can be applied in the context of any application, project, organisation or enterprise for both individual and/or organisational assessment and/or development.
Overview of Model Based Systems Engineering Using InnoslateElizabeth Steiner
Daniel Hettema, an expert systems engineer at SPEC Innovations share how to leverage the power of Model-Based Systems Engineering through Innoslate’s unique modeling and simulation features.
[ Capella Day 2019 ] Capella integration with TeamcenterObeo
The main reason we do product architecture is to communicate to downstream product development what they need to build, thus the need to integrate the Capella product architecture with the product lifecycle through PLM (Product Lifecycle Management). Siemens’ Teamcenter PLM is used by millions of developers around the world in thousands of organizations. Capella is being integrated with Teamcenter enabling it to actively participate in the product lifecycle to drive the entire product development process.
This session will provide an update on Siemens’ PLM integration progress and demonstrate the value of a Capella enabled product lifecycle.
Christoph Marhold, Siemens PLM Software
Mastering modes and states is key to analyze the expected behavior and performance of a system in different spectrums of situations.
However, as systems and missions become more complex,
the combination of modes and states across system, subsystem, and component levels becomes exponential and jeopardizes this good understanding.
In this webinar, we will:
Present the original Arcadia / Capella approach for integrating the study of the impacts of modes and states in architectural design, both from methodological and tooling perspectives.
Explain the introduction of the concepts of “configurations” and “situations” as means to specify and analyze the system in specific contexts.
In a project Systems Engineering ensures the overall integrity of the design considering the space segment, the ground segment and the launch vehicle. Systems Engineering is an accepted practice in the space industry with an unstoppable growth and evolution because it brings a multi-disciplinary perspective that is critical to system product innovation, defect reduction and customer satisfaction. A systems engineer is a person who designs space missions and their vehicles by working together with engineers in the necessary disciplines. The technical leadership role of the systems engineer on a project is critical to the success of space projects driven by high safety and performance requirements, that is why demand is soaring for systems engineers in the space industries and government agencies worldwide ( including Spain). The session will help you to understand what makes an Effective Systems Engineer in terms of the expected competencies and the meaning of a Systems Engineering career path to a professional practitioner according to the world's leading organisations in the Space sector.
Model-Based Systems Engineering (MBSE) is an ambiguous concept that means many things to many different people. The purpose of this presentation is to “de-mystify” MBSE, with the intent of moving the sub-discipline forward. Model-Based Systems Engineering was envisioned to manage the increasing complexity within systems and System of Systems (SoS). This presentation defines MBSE as the formalized application of modeling (static and dynamic) to support system design and analysis, throughout all phases of the system lifecycle, and through the collection of modeling languages, structures, model-based processes, and presentation frameworks used to support the discipline of systems engineering in a model-based or model-driven context. Using this definition, the components of MBSE (modeling languages, processes, structures, and presentation frameworks) are defined. The current state of MBSE is then evaluated against a set of effective measures. Finally, this presents a vision for the future direction of MBSE.
Præsentationen blev holdt ved InfinIT-konferencen SummIT 2013, der blev afholdt den 22. maj 2013 på Axelborg i København. Læs mere om konferencen her: http://www.infinit.dk/dk/arrangementer/tidligere_arrangementer/summit_2013.htm
Competency is a measure of an individual’s ability in terms of knowledge, skills, and behaviour to perform a given role in the Systems Engineering processes. The competency planning and deployment of Systems Engineering competencies are considered as one key factor in the successful re-industrialisation and digital transformation of Europe.
ISECF can be applied in the context of any application, project, organisation or enterprise for both individual and/or organisational assessment and/or development.
Overview of Model Based Systems Engineering Using InnoslateElizabeth Steiner
Daniel Hettema, an expert systems engineer at SPEC Innovations share how to leverage the power of Model-Based Systems Engineering through Innoslate’s unique modeling and simulation features.
[ Capella Day 2019 ] Capella integration with TeamcenterObeo
The main reason we do product architecture is to communicate to downstream product development what they need to build, thus the need to integrate the Capella product architecture with the product lifecycle through PLM (Product Lifecycle Management). Siemens’ Teamcenter PLM is used by millions of developers around the world in thousands of organizations. Capella is being integrated with Teamcenter enabling it to actively participate in the product lifecycle to drive the entire product development process.
This session will provide an update on Siemens’ PLM integration progress and demonstrate the value of a Capella enabled product lifecycle.
Christoph Marhold, Siemens PLM Software
Mastering modes and states is key to analyze the expected behavior and performance of a system in different spectrums of situations.
However, as systems and missions become more complex,
the combination of modes and states across system, subsystem, and component levels becomes exponential and jeopardizes this good understanding.
In this webinar, we will:
Present the original Arcadia / Capella approach for integrating the study of the impacts of modes and states in architectural design, both from methodological and tooling perspectives.
Explain the introduction of the concepts of “configurations” and “situations” as means to specify and analyze the system in specific contexts.
In a project Systems Engineering ensures the overall integrity of the design considering the space segment, the ground segment and the launch vehicle. Systems Engineering is an accepted practice in the space industry with an unstoppable growth and evolution because it brings a multi-disciplinary perspective that is critical to system product innovation, defect reduction and customer satisfaction. A systems engineer is a person who designs space missions and their vehicles by working together with engineers in the necessary disciplines. The technical leadership role of the systems engineer on a project is critical to the success of space projects driven by high safety and performance requirements, that is why demand is soaring for systems engineers in the space industries and government agencies worldwide ( including Spain). The session will help you to understand what makes an Effective Systems Engineer in terms of the expected competencies and the meaning of a Systems Engineering career path to a professional practitioner according to the world's leading organisations in the Space sector.
FROM PLM TO ERP : A SOFTWARE SYSTEMS ENGINEERING INTEGRATIONijseajournal
The present paper on three related issues and their integration Product lifecycle management , Enterprise Planning resources and Manufacturing execution systems. Our work is how to integrate all these in a unified systems engineering framework. As most company about two third claim to have integrate ERP to PLM, ; we still observe some related problems as also mentioned by Aberdeen group. In actual global data sharing, we have some options to also integrate systems best practices towards such objective. Such critical study come with solution by reverse engineering, revisiting requirement engineering steps and propose a validation and verification for the success factors of such integration.
CMGT 580Introduction to Systems Engineering ManagementClass .docxmary772
CMGT 580
Introduction to Systems Engineering Management
Class 5
Chapter 6 Needs Analysis
Reminder where Needs Analysis fits in process
“there is a feasible approach to fulfilling the need at an affordable cost and within an acceptable level of risk”
Concept Development Stage – Needs Analysis
Originating a new system
Needs-driven example: 1960's new laws for automobiles (fuel economy, safety, pollution control)
Technology-driven new systems (space, computers)
External events (new threats, shift in customer demand, economics)
Since there‘s no preceding phase the inputs come from other sources
Applying the Systems Engineering Method
The focus of attention in this phase is on the system operational objectives and goes no deeper than the subsystem level.”
More detail on next charts
Systems Engineering Method applied to the Needs Analysis Phase
Requirements analysis -- Operations analysis
Clarifying requirements
Functional definition -- Functional analysis
Translating requirements into functions
Allocating requirements
Define interfaces
Physical definition -- Feasibility definition
Develop alternative designs
Perform trade-offs to select a preferred approach
Develop detail for the selected design
Design validation -- Needs validation
Model system environment
Verification
Operations Analysis
Detailed identification of perceived deficiencies in current systems
Obsolescence is a prevalent driving force for new systems
The output of this activity is operational objectives for new system
Functional Analysis
This is an extension of operational studies
Establish if there's a possible technical approach to a system
It's not necessary to visualize a best configuration
Feasibility Definition
Feasibility addresses functional design, physical implementation, cost, external constraints and interactions
No attempt is made to optimize the design
Feasibility can be difficult in technology-driven systems
Needs Validation
Examine the validity of the results of the previous steps
Use an operational effectiveness analysis tool (model) based on a set of scenarios
These simulations are evaluated based on criteria called Measures of Effectiveness
This effectiveness analysis determines if a system concept is feasible and satisfies the operational objectives
MOE and MOP Metrics
Measures of Effectiveness (MOE) – indicates the degree to which the whole system achieves its objectives under specified conditions
Measures of Performance (MOP) – quantitative metric of the whole system’s characteristics or performance of a particular attribute, typically a level of physical performance
Development of Operational Requirements (CONOPS)
Operational distribution or deployment: Where will the system be utilized?
Mission profile or scenario: What must the system do to accomplish its objective?
Performance and related parameters: What are the critical system pa.
Systems Analysis,
Systems Design,
Systems Modelling,
Systems Architecture,
System Development and Testing,
System Maintenance and Evolution,
SDLC example (Cloud Service life cycle)
"Overview of DoDAF with Innoslate" answers the questions:
- Why is DoDAF Important to DoD?
- How Can We Do Good Systems Engineering and Meet DoDAF Requirements?
-How Can MBSE Tools Specifically Support DoDAF?
Your webinar host, Dr. Steve Dam provides you with an in-depth overview of the DoDAF 2.0 using the systems engineering software, Innoslate. Dr. Dam, the President and Founder of SPEC Innovations, participated in the development of DoDAF. He recently published "DoDAF 2.02 A Guide to Applying System Engineering to Develop Integrated, Executable Architectures." The presenter will provides a live tool demonstration of Innoslate with a questions and answer session to follow.
Overview of Performance Evaluation
Intro & Objective
The Art of Performance Evaluation
Professional Organizations, Journals, and conferences.
Performance Projects
Common Mistakes and How to Avoid Them
Selection of Techniques and Metrics
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
Normal Labour/ Stages of Labour/ Mechanism of LabourWasim Ak
Normal labor is also termed spontaneous labor, defined as the natural physiological process through which the fetus, placenta, and membranes are expelled from the uterus through the birth canal at term (37 to 42 weeks
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Introduction to AI for Nonprofits with Tapp NetworkTechSoup
Dive into the world of AI! Experts Jon Hill and Tareq Monaur will guide you through AI's role in enhancing nonprofit websites and basic marketing strategies, making it easy to understand and apply.
Francesca Gottschalk - How can education support child empowerment.pptxEduSkills OECD
Francesca Gottschalk from the OECD’s Centre for Educational Research and Innovation presents at the Ask an Expert Webinar: How can education support child empowerment?
3. Place of needs analysis in system
development life cycle
Refer to the figure 6.1
Inputs are operational deficiencies and/or technological
opportunities
The need for a new system arises because of following
reasons
Serious deficiency in the present system designed to meet a
specific need
Technological development which promises a better solution
than the present system
Outputs to the following phase of concept exploration
Estimated operational effectiveness
System capabilities
SYSTEM ENGINEERING --- DR. S. S. THAKUR 3
5. Examples of new system needs
The most common example is automobile industry
Government laws require manufacturers to make
substantial improvements in
Fuel economy
Safety
Pollution control
The above factors render many present designs obsolete
overnight
Examples of technology driven new systems are
applications of space technology to meet public and
military needs such as
Powerful propulsion systems
Lightweight materials
Compact electronics
GPS
SYSTEM ENGINEERING --- DR. S. S. THAKUR 5
6. Competitive issues
Regardless of the source of funding there may be a
competition for resources necessary to demonstrate a
bona fide need
One question considered in the military is
Should maritime superiority be primarily a domain of
the surface or the air navy or a combination of two?
One question considered in automobile industry is
Should cleaner air be achieved by more restrictions on
the automobile engine combustion process or on the
chemical composition of the fuel?
The answers to the above questions play an important
role in the development of a new system
SYSTEM ENGINEERING --- DR. S. S. THAKUR 6
7. Design Materialization status
The focus of attention in this phase is on the system
operational objectives
It goes no deeper than the subsystem level
The activity is listed as “visualize” rather than
definition or design
The term “Visualize” refers to “forming a mental
image or vision”
It implies conceptual rather than the material view
At this level, most designs first originate , drawing on
analogies from existing system elements
Refer to the table in next slide
SYSTEM ENGINEERING --- DR. S. S. THAKUR 7
9. Applying System Engineering method in needs
and requirement analysis
Operational Analysis (Requirement analysis)
Focus is on
Projected needs of the system
Understanding the value of fulfilling projected needs
Defining quantitative operational objectives and the
concept of operation
Products are
Operational objectives
System capabilities
SYSTEM ENGINEERING --- DR. S. S. THAKUR 9
10. Applying System Engineering method in needs
and requirement analysis
Functional Analysis
Focus is on
Translating operational objectives into functions that
must be performed
Allocating functions to subsystems by defining
functional interactions and organizing them into a
modular configuration
Product is
List of initial functional requirements
SYSTEM ENGINEERING --- DR. S. S. THAKUR 10
11. Applying System Engineering method in needs
and requirement analysis
Feasibility Definition (Physical definition)
Focus is on
Visualizing the physical nature of subsystems conceived
to perform the needed system functions
Defining a feasible concept in terms of capability and
estimated cost
Product is
Initial physical requirements
SYSTEM ENGINEERING --- DR. S. S. THAKUR 11
12. Applying System Engineering method in needs
and requirement analysis
Needs Validation (Design Validation)
Focus is on
Designing or adapting an effectiveness model
(analytical or simulated) with operational scenarios,
including economic (cost, market etc.) factors.
Defining validation criteria
Demonstrating cost effectiveness of the postulated
system concept after suitable iteration or adjustment
Formulating the case for investing in the development of
a new system to meet the projected need
Product is
List of operational validation criteria
SYSTEM ENGINEERING --- DR. S. S. THAKUR 12
14. Types of requirements
Operational Requirements
Refer largely to the mission and purpose of the system
Will describe the end state of the world after the system
is deployed and operated
Give a broad view of objectives
Functional Requirements
Focus on what a system should do?
Action oriented and should describe the tasks or
activities that the system performs during its operation
Largely quantitative
SYSTEM ENGINEERING --- DR. S. S. THAKUR 14
15. Types of requirements
Performance Requirements
How the system should perform and affect its
environment
Minimal numerical thresholds
Objective and quantitative
Physical requirements
Characteristics and attributes of the physical system
and physical constraints placed upon the system design
Concerns with appearance, general characteristics as
well as volume, weight, power and material
Relates with constraints or even system requirements
SYSTEM ENGINEERING --- DR. S. S. THAKUR 15
16. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-6(Page numbers 139-145).
SYSTEM ENGINEERING --- DR. S. S. THAKUR 16
17.
18. Analysis of projected needs
Market studies are continuously carried out
Reaction of customers is monitored
Reason for lagging sales are mathematically probed
Strength and weaknesses of competing systems and their
likely future growth are analyzed
Deficiencies in the current system
Is development needed or an upgrade?
Must focus on ten years in the future
Accumulated test data with analysis often using system
simulations
Benefits
Consistent and accurate evaluation of system’s operational
performance
Documented history of results
SYSTEM ENGINEERING --- DR. S. S. THAKUR 18
19. Operational Objectives
Are outcome of operational studies
Should address the end state of the operational
environment
Should address the purpose of the system
Answers “WHY” question
Start with “Provide”
Objective Analysis
Refining the set of objectives
Objective tree is used
Automobile as example (GREEN)
Clean means good mileage and comfortable
SYSTEM ENGINEERING --- DR. S. S. THAKUR 19
22. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-6(Page numbers 146-151).
SYSTEM ENGINEERING --- DR. S. S. THAKUR 22
23.
24. Translation of operational objectives into
system functions
Visualize the feasible type of system concept
Visualization is an abstract process
In needs driven systems operational objectives are
considered
In technology driven systems technological
developments are considered
A helpful approach is to consider the type of media
(data, signal, material and energy) involved
All the elements of the concept should be functionally
related to the elements of the real system
SYSTEM ENGINEERING --- DR. S. S. THAKUR 24
25. Allocation of functions to subsystems
Visualize- How they might be allocated, combined and
implemented in a new system
A top level system concept should be visualized which
implements all the prescribed functions to obtain a
plausible solution
All interactions and interfaces, both internal and
external, should be identified and associated with
system functions
Trade-off process should be employed to check that
the consideration of various system attributes is
thorough and properly balanced
SYSTEM ENGINEERING --- DR. S. S. THAKUR 25
26. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-6(Page numbers 151-152).
SYSTEM ENGINEERING --- DR. S. S. THAKUR 26
27.
28. Feasibility Definition
System cost is a dominant factor especially compared
to other alternatives
Visualization of subsystem implementation
At this stage it is only necessary to find examples of
similar functional units in existing systems
The identification of media involved in each major
function (signal, data, material and energy)
Relation to the current system
Existing models and simulations of current system are useful
tools
Analysis answers “What if” question
Effectiveness model can be used for effectiveness analysis
SYSTEM ENGINEERING --- DR. S. S. THAKUR 28
29. Application of advanced technology
Analysis done on the basis of theoretical and experimental
data available
Data available from the research done on the candidate system
in consideration
Sometimes a particular technology may offer a substantial
gain but may lack maturity
Cost
Cost assessment is very important
Task is particularly complicated when there is a mix of old,
new and modified subsystems, components and parts
Cost models and maintenance records of the current system
combined with inflation factors can be helpful
SYSTEM ENGINEERING --- DR. S. S. THAKUR 29
30. Definition of a feasible concept
The system description should include
Discussion of the development process
Anticipated risks
General development strategy
Design Approach
Evaluation methods
Production issues
Concept of operations
SYSTEM ENGINEERING --- DR. S. S. THAKUR 30
31. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-6(Page numbers 153-154).
SYSTEM ENGINEERING --- DR. S. S. THAKUR 31
32.
33. Operational Scenarios
Mission Objectives
The scenario should identify the overall objectives of the
mission represented
The purpose and role of the system(s) in focus in
accomplishing those objectives
Architecture
The scenario should identify the basic system
architecture involved
Includes a list of systems, organizations and basic
structural information
Includes basic information on system interfaces
SYSTEM ENGINEERING --- DR. S. S. THAKUR 33
34. Operational Scenarios
Physical Environment
The scenario should identify the environment in which
it takes place
Includes physical environment (eg. Terrain, weather,
transportation grid and energy grid)
Business environment (eg, recession and growth period)
Neutral entities (eg. Customers and their attributes,
neutral nations and their resources)
SYSTEM ENGINEERING --- DR. S. S. THAKUR 34
35. Operational Scenarios
Competition
The scenario identify competition to the efforts
Identify elements directly opposed to the mission’s
success (eg. Software hacker or other types of “enemy”)
Consider natural disasters such as tsunami or hurricane
Consider outside market forces that may influence the
target customers
General Sequence of the events
Sequence should be within the mission context
There should be freedom of action on the part of the
players
Should not “script” the system, they are analysis tools,
not shackles to restrain the system development.
SYSTEM ENGINEERING --- DR. S. S. THAKUR 35
36. Operational Requirements Statement
Described in terms of operational outcomes rather
than system performance
Should not be stated in terms of implementation
Should not be biased towards a particular conceptual
approach
All requirements must be mentioned in measurable
(testable) terms
Time factor should be considered
Not readily derived from operational factors but may be
critical in certain cases when obsolescence of current
system and schedule of platforms
SYSTEM ENGINEERING --- DR. S. S. THAKUR 36
37. Feasibility Validation
Build a convincing case by analogy with already
demonstrated applications of the projected technique
Comparison should be quantitative rather than only be
qualitative
Experimental investigations should be conducted
Experience of the engineering staff is an important
factor
The investigation should be extensive
This approach is often referred to as “critical
experiments”
SYSTEM ENGINEERING --- DR. S. S. THAKUR 37
38. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-6(Page numbers 158-162).
SYSTEM ENGINEERING --- DR. S. S. THAKUR 38
39.
40. Alternative implementation concepts
At one end predecessor system should be explored for
Operational deficiencies
Modifications (if required)
developmental risks
At the other end
Innovative technical approaches featuring advanced
technology
Generally more risky and difficult to implement
Brainstorming is one of the oldest technique
Mind Maps is a prominent technique which helps in
brainstorming (the figure in the next slide shows a
mind map for favorite pastime)
SYSTEM ENGINEERING --- DR. S. S. THAKUR 40
42. Concept exploration for a new aircraft
Automation has become more widespread, especially in
autopilots and navigation systems
Changes in safety requirements must be examined to
identify the performance characteristics
While exploring alternative implementations, the main
features of each candidate system must first be analyzed to
see if they are conceptually achievable
At this stage of development, a detailed design analysis is
usually not possible because the concept is not yet
sufficiently formulated
Based on previous experience and engineering judgment,
system engineer must decide whether or not the concept is
proposed is likely to be achievable within given bounds of
time, cost and risk
SYSTEM ENGINEERING --- DR. S. S. THAKUR 42
43. Technology Development
Many of the new systems have been brought into being
because of technological developments
It is important for system engineers to understand the
nature and sources of technological advances that concerns
with proposed system development
System oriented exploratory R & D can be distinguished
according to
Needs driven system which aims at gaining a firm
understanding of the operational environment and factors
responsible for the increasing need of a new system
Technology driven systems which is focused on extending
and quantifying the knowledge base for the new technology
and its knowledge base for the new system objectives
SYSTEM ENGINEERING --- DR. S. S. THAKUR 43
44. Preferred System
In most cases it is best to refrain from picking a superior
system concept prematurely
There are instances where it is permissible for the
requirements definition effort to identify a so-called
preferred system
Preference for a system or subsystem may be set forth when
significant advanced development work has taken place
and has produced very promising results
Such work is often conducted or sponsored by the
customer
Another factor is major technological breakthrough which
promises high gains in performance at an acceptable risk
The idea of this approach is that subsystem analysis can
start building on this concept, thereby saving time and cost
SYSTEM ENGINEERING --- DR. S. S. THAKUR 44
45. Performance Characteristics
Performance analysis
Used to derive a set of relevant performance
characteristics for each candidate system concept that
has been found to satisfy the effectiveness criteria
The issue of relevance arises because a full description of
any complex system will involve many parameters
Must extract from the identified system characteristics
only those that directly affect the system’s operational
effectiveness
The defined set of characteristics must be both
necessary and sufficient to facilitate a valid
determination for each candidate system concept
SYSTEM ENGINEERING --- DR. S. S. THAKUR 45
46. Constraints
Interfaces and interactions with other system or part of systems
cannot be overlooked, which will invariably place the constraints on
the new system
May affect the physical form and fit, weight and power,
schedules(eg. Launch date), mandatory software tools, operating
frequencies, operator training etc.
The immediate benefit of early attention to such problems is that
the conflicting concepts can be filtered out
More time can be given for the analysis of more promising
approaches
The whole system life cycle should be considered
Constraints like environmental conditions of temperature,
humidity, shock vibration etc. are often same for any candidate
system concept irrespective of their architecture
SYSTEM ENGINEERING --- DR. S. S. THAKUR 46
47. References
Alexander Kossiakoff, William N Sweet, “System
Engineering Principles and Practice”, Wiley India,
Chapter-7(Page numbers 185-189).
http://baibasvenca.blogspot.in/2013/01/using-mind-
maps-with-students.html
SYSTEM ENGINEERING --- DR. S. S. THAKUR 47