Handle om å gjøre kunnskap tilgjengelig på internett, samt bruke de mulilghetene som samrabeid og åpenhet gir til å vinne ny kunnskap. Fishbowlkonseptet har derfor to dimensjoner. En etisk og en teknisk.

Ettersom internett er tilgjengelig for "alle", så kan det som ligger på internett sammenlignes med noe som befinner seg i en gullfiskbolle. Det er synlig for alle kanter.

The science of naval architecture

Modern low-cost digital computers and dedicated software, combined with extensive research to correlate full-scale, towing tank and computational data, have enabled naval architects to more accurately predict the performance of a marine vehicle. These tools are used for static stability (intact and damaged), dynamic stability, resistance, powering, hull development, structural analysis, green water modelling, and slamming analysis. Data is regularly shared in international conferences sponsored by RINA, Society of Naval Architects and Marine Engineers (SNAME) and others. Computational Fluid Dynamics is being applied to predict the response of a floating body in a random sea.

http://en.wikipedia.org/wiki/Naval_architecture

Free software foundation:

http://www.gnu.org/philosophy/why-free.html:

to be able to cooperate openly and freely with other people who use software.

to be able to learn how the software works

to teach your students with it.

to be able to hire your favorite programmer to fix it when it breaks.

society needs to encourage the spirit of voluntary cooperation in its citizens. When software owners tell us that helping our neighbors in a natural way is “piracy”, they pollute our society's civic spirit

http://en.wikipedia.org/wiki/Open_source_movement#Strengths

Strengths

• The collaborative nature of the open source community creates software that can offer customizability and, as a result, promotes the adoption of its products.^[9]
• The open source community promotes the creation of software that is not proprietary, thus resulting in lower costs.^[9]
• The development of open source software within the community is motivated by the individual who has expressed interest in the code and software creation. This differs from proprietary software that is often motivated via monetary means.^[9].
• An open source tool puts the system administrator in control of the level of risk assumed in deploying the tool.^[10]
• Open source provides a flexibility not available in closed products. The hope is that If you make improvements to an open tool you'll offer them back to the original developer and community at large. The give-and-take of the gift economy benefits everyone.^[10]

http://www.zope.org/DevHome/Fishbowl/index.html/Introduction.html

Fishbowl Motivations

The Fishbowl Process is the way the community, including Digital Creations, will design and develop Zope. The name "fishbowl" comes from the idea brought to prominence by Mozilla.org that there are no internal conversations; rather, all communication, decisions, arguments, and progress is visible as if everyone were working "in a fishbowl".

These are the goals and motivations of this process:

1) Lightweight. The process should be as simple as possible and should not require a great deal of learning or ceremony to use. A process that is too heavy will eventually be ignored.

1) Consistency. When approaching projects, potential Zope developers should be able to quickly come up to speed on requirements and other project information. Likewise, people running new projects should have a consistent body of existing projects to emulate when running their own.

1) Thinking about thinking. If code is the only artifact, we're in trouble. The requirements, design and decision-making that lead to code are as important as the code. Equally important, it means that non-developers can participate in the process by commenting on (and contributing to) non-code artifacts.

1) Formalizing arguments. It is hard to engage a proposal when it isn't clear what is proposed, or to debate an architecture when you don't know what the architecture actually is. At the same time, it is frustrating for would-be developers to be told things such as, "You didn't write the requirements right" when there are no examples of good requirements.

1) Ensuring progress. Projects that are mushy and poorly defined are easily sidetracked and difficult to keep moving forward. Ensuring that projects are well defined and using milestone-based "hill-to-hill" planning as a part of the process can ensure that projects make steady progress.

Sustainable design of ships for the future

Three leading Norwegian based maritime companies, STX Europe, Rolls Royce Marine and DNV, join forces with NTNU in Trondheim to build an international competence centre for research and education on the topic "Sustainable design of ships for the future". This research program is funded by the Norwegian Research Council and the industry partners.

• Innovative ship design - the capability to turn end user needs and wants into designs which exceed the end customer's expectations to performance, specifically related to areas such as environmental performance and onboard work environment.
• Production friendliness - deployment of state of the art production technologies and methods to enhance quality and cost-effectiveness in an increasingly distributed, collaborative ship production process
• Design effectiveness - the deployment of state of the art design technology and processes to enhance the design process itself
• Enhanced risk and opportunity management in conceptual design decision making

The research will be directed towards both theoretical and applied methods within the thematic areas, and comprise research subjects such as:

• New and improved methods for analysis and optimization in conceptual design, with emphasis on the early assessment of sustainability, producibility, cost, operability and risk.
• Methods and models for ship conceptual design optimization within the context of a fleet and/or transport system, with emphasis on utilization, robustness and lifecycle environmental impact
• Product platforms, work processes and best engineering practices in design, engineering and production, focusing on parametric and configuration-based design methods and modularization.
• Methods to identify key design drivers and simplified design representations from large, complex design models, with focus on assessing performance differentials (what-if) rather than absolute performance levels.
• Methods for the efficient exploitation of data embedded in existing databases and other knowledge sources to support design decisions and verification

Det beste man har I dag:

http://www.ivt.ntnu.no/imt/systemer/svartebok/

ballast-2.jpg

bildestian.jpg

lines.jpg

naval_architecture.jpg

roughseas.jpg

shipimages.jpeg

splan.gif