Or as its also called, The house of Quality, is a “method to transform user demands into design quality, to deploy the functions forming quality, and to deploy methods for achieving the design quality into subsystems and component parts, and ultimately to specific elements of the manufacturing process.
First described by Dr. Yoji Akao, who originally developed QFD in Japan in 1966.
One of the major problems in the engineering world out there is talking apples and apples. This simply applies to not only simple daily conversations, but cost acquisition programs, where you would have the sales team of a company work with a customer and try to break down the proposed cost. After the breakdown, and understanding of the different elements, and the inherent risk is where you realize that value of the service/product.
As UML 2.1 picks up in momentum, it would be a good time to look into utilizing this powerful tool to bridge this everlasting problem of misconception. I think if one can model a clear cost model for a product, then that creates a dialog medium, which will save lots of time/effort/resources and adds credibility/transparency/detail to the bidirectional conversation.
The only problem I see is that this methodology is easier said than done. Although I’m slowly preparing myself for all this model analysis and architecture analysis work, it is not very clear how I would go forward, even with all the software packages and modules out there. However, I do think that being in Stevens would prosper my chances of arriving at this delicious answer.
Many organisations today are establishing an Enterprise Architecture (EA) business function.
However the knowledge about enterprise architecture concepts, framework and processes within many organisations is still quite limited and at a low level of maturity.
Very often there is a good understanding of the technology and infrastructure architecture and the to a lesser extent of the application architecture but far less understanding of the enterprise architecture discipline.
The concept of enterprise architecture has evolved considerably from John Zachman’s original work in the 1980’s on his Framework for Information Systems Architecture.
The Zachman Framework has provided the basis for many more recent enterprise architecture frameworks and associated processes that are now available.
According to many surveys, the majority of organisations usually choose to create their own EA framework rather than adopt any existing one.
The reasons for this vary, from the requirement to support a service oriented architecture, object orientation and component based development viewpoints, to a simple desire to use a different terminology that is tailored to the language used within the organisation.
Systems engineering integrates two disciplines: Engineering, the technical knowledge domain, and Systems which is an interconnected composite of people with tools and process that create a capability to meet an objective.
Some people think of software when I tell them about system’s engineering. Well, here is something on the line of software architecture that I found interesting a couple of days ago.
http://www.codingthearchitecture.com/pages/book/software-architecture-document-guidelines.html
This information is retrieved from INCOSE’s website on Nov 7th,2009.
| This Code is concerned with how certain fundamental imperatives apply to one's conduct as an engineering professional. These imperatives are expressed in a general form to emphasize that principles which apply to engineering ethics are derived from more general ethical principles. It is understood that some words and phrases in a code of ethics are subject to varying interpretations, and that any ethical principle may conflict with other ethical principles in specific situations. Questions related to ethical conflicts can best be answered by thoughtful consideration of fundamental principles, rather than reliance on detailed regulations. |
| |
| Preamble |
| Engineering is a profession that requires its practitioners to be well educated and knowledgeable. Systems Engineering, in particular, is a unique discipline in that 1) it is highly integrative, spanning elements of many activities, 2) often provides representation of stakeholders' interests other than employer or client, and 3) operates in largely international arenas where value systems, beliefs and customs vary widely. The practice of Systems Engineering can result in significant social and environmental benefits, but only if unintended and undesired effects are considered and mitigated. |
| |
| Fundamental Principles |
| Systems Engineers uphold and advance the integrity, honor and dignity of the engineering profession by: |
|
| |
| Fundamental Duties to Society and Public Infrastructure |
|
| |
| Rules of Practice |
|
INCOSE will host the main guy who has been SysML. This lecture which is hostel by INCOSE will have a day seminar on SysML which is something that Stevens currently lacks. I am going to attend this seminar, and find out more detail about it. It should be around NOV 20th.
For the exact date, contact me: hellomatin@gmail.com
Read the Incose 2008 OMGSysML tutorial that is published in PDF format.
Not only does this explain SysML in the simplest terms, it is probably one of
The best sources to learn SysML thoroughly.
You can obtain a copy of this document at this website ( if it’s still hosted when you visit the site of course)
http://www.sysmlforum.com/training.htm
Enjoy.
Systomics is the foundational science of systems thinking. It asks and seeks to answer these two key questions: ‘What is a system (in the abstract)?’, and, ‘What is the meaning of this (particular) system?’ Systems thinking is itself an applied science asking ‘How can the notion of system be used to make sense of or to improve reality?’ Applied systems thinking benefits a wide range of domains and thereby provides testimony and future insights for systomics.
At Stevens Institute of Technology within the School of Systems and Enterprises (SSE), the Systomics Laboratory has been established to study the science of systems thinking so we may look at systems over space and time and may find the true systemic remedies to systemic failures.
