text:
User talk:Pratapkomaravolu

for distribution of "2007 DCS Asia Outlook thru 2010.pdf" ?
As it says on page 2 there: it may not be reproduced or published without prior written permission of ARC Advisory Group. Do you have the permission ? Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 18:55, 12 February 2008 (UTC)
 * File is deleted. If you can show the permission, it can easily be restored, Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 19:08, 12 February 2008 (UTC)

China and India-Contrasting Growth Markets for Automation.pdf
this doc is also from same company, so I assume, the same copyrights hold here ?

logo: Image:Invensys blue small.jpg
and I guess the logo is copyrighted as well ?

copy+paste
see Talk:PID Controller, Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 19:04, 12 February 2008 (UTC)

title: User talk:Pratapkomaravolu


text:
User talk:Robertlyn

Image copyright problems
Your currently affected images are listed below. For each, please provide a license template and source. Thanks .– Mike.lifeguard | @en.wb 23:57, 13 February 2008 (UTC)
 * 2007-08-22 09:41, Robertlyn: Robertlyn.jpg: untagged! ; 0 (0)
 * 2007-08-22 12:21, Robertlyn: Robert Lyn.jpg: untagged! ; 0 (0)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:Robertlyn


text:
User talk:Tapoo

Image copyright problems

 * The images are listed below. Please provide license information and a source for them.
 * Picture tania1.jpg
 * Pic tapoo.jpg
 * Thanks. – Mike.lifeguard | @en.wb 22:13, 13 February 2008 (UTC)

Czech content?
Hello, this seems to be Czech content: Problem. What do you say - on betawikiversity there is ongoing process to create content in Czech. Would you like to add it there ? Erkan Yilmaz Wikiversity:Chat  21:21, 7 March 2008 (UTC)

Ahoj, trochu nechápu co je na té stránce Problém vzdělávacího. Myslím si, že nálady do projektu Wikiverzita nepatří. Bude se to nějak vyvýjet nebo to zůstane takhle jako protest? Jinak českou verzi wikiverzity máme v inkubaci a to zde:. Mělo by se to tam přesunout, protože to sem nepatří - ale jak říkám, v této podobě to nepatří ani na českou ani na anglickou.--Juan 22:28, 8 March 2008 (UTC)

title: User talk:Tapoo


text:
User talk:Tnswettenham

Image copyright problems

 * This is the image in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 21:58, 13 February 2008 (UTC)

Files Missing Information
Thanks for uploading files to Wikiversity. All files must have source and license information to stay at Wikiversity. The following files are missing and/or License tags, and will be deleted if the missing information is not added. See Uploading files for more information.

 * File:BongiMosia-thumbnail.jpg
 * File:HolidaysofHope-thumbnail.png

MaintenanceBot (discuss • contribs) 15:33, 16 April 2016 (UTC)

title: User talk:Tnswettenham


text:
User talk:Satanist Lock

Image copyright problems

 * This is the image in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 21:59, 13 February 2008 (UTC)

title: User talk:Satanist Lock


text:
User talk:DELASTING

Image copyright problems

 * This is the media in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:35, 13 February 2008 (UTC)

title: User talk:DELASTING


text:
User talk:QKRAM

Image copyright problems

 * This is the image in question. Please provide a source and a license template for it. Thanks. – Mike.lifeguard | @en.wb 22:39, 13 February 2008 (UTC)

title: User talk:QKRAM


text:
User talk:Aa210789

Image copyright problems

 * This is the image in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:03, 13 February 2008 (UTC)

title: User talk:Aa210789


text:
User talk:Gheorghe

Image copyright problems

 * this is the image in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:31, 13 February 2008 (UTC)

title: User talk:Gheorghe


text:
User talk:Silver Tonto

Image copyright problems

 * This is the image in question; please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:23, 13 February 2008 (UTC)

title: User talk:Silver Tonto


text:
User talk:Adam Vance

Image copyright problems

 * This is the media in question; please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:37, 13 February 2008 (UTC)

title: User talk:Adam Vance


text:
User talk:Grahamlash

Image copyright problems

 * This is the image in question; please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:20, 13 February 2008 (UTC)

title: User talk:Grahamlash


text:
User talk:Jtor

Image copyright problems

 * This is the media in question. Please provide license information and a source for it. Thanks. – Mike.lifeguard | @en.wb 22:15, 13 February 2008 (UTC)

title: User talk:Jtor


text:
User talk:AgentOO

Image copyright problems

 * This is the image in question. Please provide a source and appropriate license template for it. Thanks. – Mike.lifeguard | @en.wb 22:32, 13 February 2008 (UTC)

title: User talk:AgentOO


text:
User talk:Gramsoft~enwikiversity

Image copyright problems

 * This is the media in question. Please provide a license template and source for it. Thanks. – Mike.lifeguard | @en.wb 22:16, 13 February 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Gramsoft. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Gramsoft~enwikiversity that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:37, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 06:09, 19 April 2015 (UTC)

title: User talk:Gramsoft~enwikiversity


text:
Talk:History of Indonesia and Timor-Leste

Hello,

this seems to be (partly) a copy from here and Wikipedia's article Indonesia Why don't we make a learning experiment now with this and try to rephrase this in our own words or use Wikipedia's article to generate information or a better learning experience on another level ?

Please also see: What Wikiversity is not

 * "A duplication of other Wikimedia projects. While Wikiversity complements other Wikimedia projects, it will not simply duplicate their content. So, if you want to read about a topic, you may be better off visiting, say, Wikipedia or Wikibooks, but if you want to learn about this topic, you can do so at Wikiversity. Learning materials will be created and used on Wikiversity, but materials on other projects may also be used as learning materials themselves or even places to consolidate this learning, i.e. writing an article, manual etc based on what you've learned. There may be some overlapping, but each project will maintain its own focus."

Also worthwile reading: What is Wikiversity? How to Cite from Wikipedia. Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 18:44, 12 February 2008 (UTC)


text:
Talk:History of China/The Three Kingdoms

copy + paste
Hello,

this seems to be a copy from Wikipedia's article Three Kingdoms Why don't we make a learning experiment now with this and try to rephrase this in our own words or use Wikipedia's article to generate information or a better learning experience on another level ?

Please also see: What Wikiversity is not

 * "A duplication of other Wikimedia projects. While Wikiversity complements other Wikimedia projects, it will not simply duplicate their content. So, if you want to read about a topic, you may be better off visiting, say, Wikipedia or Wikibooks, but if you want to learn about this topic, you can do so at Wikiversity. Learning materials will be created and used on Wikiversity, but materials on other projects may also be used as learning materials themselves or even places to consolidate this learning, i.e. writing an article, manual etc based on what you've learned. There may be some overlapping, but each project will maintain its own focus."

Also worthwile reading: What is Wikiversity? How to Cite from Wikipedia. Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 18:48, 12 February 2008 (UTC)

reading group
please also see Romance of the Three Kingdoms (by Luo Guanzhong), Erkan Yilmaz uses the Wikiversity:Chat (try) 07:49, 7 June 2008 (UTC)


text:
User talk:Annika~enwikiversity

Welcome
Hello Annika, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 21:59, 12 February 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Annika. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Annika~enwikiversity that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:28, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 06:03, 19 April 2015 (UTC)

title: User talk:Annika~enwikiversity


text:
User talk:Jenndel

Welcome
Hello Jenndel, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 21:59, 12 February 2008 (UTC)

title: User talk:Jenndel


text:
User talk:Alton

Welcome
Hello Alton, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Countrymike 22:03, 12 February 2008 (UTC)

Alton, special welcome from one UCLA grad to another. Countrymike 22:03, 12 February 2008 (UTC)

title: User talk:Alton


text:
Facts and figures

Miscellaneous

 * August 2008 The number of suicides in England has reached a record low, figures show.

Technology

 * MLC-flash SATA II drive has speeds of 200MBps read and 160MBps sequential write
 * June 2008 - The whole laptop market makes around 5 million laptops per month - According to the video, in about a year, OLPC will be making around 1 million a month...

Medicine

 * '22,146 American doctors in residency programs in the United States specializing in primary care' in 2006
 * Clinician visits in 2005:
 * Mental health 156m
 * Back issues 139m

Scale

 * 1.3-micron speck about 100th the diameter of a human hair. A human hair is about 100 microns wide.

Statistics

 * '200 million chickens raised in South Carolina'
 * (May 2008) 'In the U.S., there are approximately 2,000 landfill sites. The country generates about 230 million tons of solid waste a year.'
 * The United States Department of Energy estimates that if algae fuel replaced all the petroleum fuel in the United States, it would require 15,000 square miles (40,000 square kilometers), which is a few thousand square miles larger than Maryland, or 1.3 Belgiums.  This is less than 1/7th the area of corn harvested in the United States in 2000.
 * June 2008 - 2007 giving - US - 306 million dollars - 38 billion in foundation grants...
 * June 2008 "There are nearly 20 million state and local government employees in the country." [USA]

Economics

 * Estimated that US will pay $440 billion to import 10+ million barrels of crude/day

Engineering

 * Intel's 6 core chip - 'Dunnington is composed of... 1.9 billion transistors'
 * (May 2008) 'Intel says it expects more than 50 million of these netbooks to be sold by 2011. It's introduced a tiny, low-power processor to run them called Atom, which puts 47 million transistors on a chip about the size of a penny.'

title: Facts and figures


text: File:Xboxarcadesku.jpg

title: File:Xboxarcadesku.jpg


title: File:OA1.jpg


text: File:Digital Recording.gif

title: File:Digital Recording.gif


title: File:O0A1.jpg


text: File:Digital radio.jpg

title: File:Digital radio.jpg


title: File:Tivo-series3-box.jpg


text:
User talk:Livinglaboratory

O.k. so I started a discussion visible online so think before you write, this is public.

Mission Statement:  Main Ideas: In order to add your suggestions below, click on the tab at the top which shows "+". A blank box will show up for you to write your suggestion. Once you click save, it should show below the previous suggestion. Please sign your name (?). You must type " " to enter breaks in the text and the tool bar at the top should help you if you do not know html. I hope this works. Do not click the 'edit this page' tab unless you know what you're doing! There should be no reason for anyone to click on this tab anyway.
 * sustainable
 * off-grid
 * outreach
 * students
 * educating
 * learning
 * "Learn by doing"
 * time
 * please include the ones I missed. I apologize, I forgot to copy them from the whiteboard.

-kt

Enter suggestions below:

 * An interactive interdisciplinary laboratory students and community intended for promoting and educating on the benefits of sustainable building techniques and environmental technology.-kt

 * To educate our community in contemporary sustainable practices in an interdisciplinary interactive laboratory.

Presentation Comments
We got some good feedback. I really think that we should focus on the positives which included our very interdisciplinary group, the true costs of this project, and making a statement that could shame people. I think we need to move in the direction of really designing the site conditions and BWWS; we also really need to start getting the word out to "stakeholders." -Cerisa

Great job everyone! It was all around a good presentation. We pushed the time more than anticipated but I think we pulled it off o.k. and recovered well. Thank you for everyone's hard work. I will post more later. - kt

I know it was a week ago now, but the feedback we got was very encouraging. I also got the feeling that our Living Laboratory idea was the one that they felt handled the multi-disciplinary and "change" aspects that are so important in the class. Let's keep on moving towards the "big shame" (actually getting our ideas implemented) over the rest of the quarter. I have done a little more research on foundations for the BWW/LM and would love to work with that group tonight to get some details figured out. Also, if we could develop the site layout and some renderings I think that would help sell our ideas to the "stakeholders". See y'all later. -Robbie

title: User talk:Livinglaboratory


text:
User:Reppuli

Home page: blog

Courses I am taking

 * Composing free and open online educational resources

title: User:Reppuli


text:
Portal:Life Sciences/Topics

España avanza hacia su destrucción? Hola a todos los wikis, soy Marta y os pido a todos: Ayudadme a salvar el mundo y mi pais,España, de su propia destrucción.

School of Biology
🇨🇴
 * Agriculture
 * Anatomy
 * Arachnology
 * Division of Human Biology
 * Animal Physiology
 * Biochemistry
 * Bioinformatics/Computational Biology
 * Biomechanics
 * Bionomics
 * Biophysics
 * Biotechnology
 * Botany
 * Cell Biology
 * Ecology
 * Entomology
 * Engineering biology
 * Ethology
 * Evolution
 * Evolutionary Biology
 * Evolutionary Ecology
 * Evolutionary Virology
 * Exobiology

 * Genome Analysis
 * General Biology
 * General Botany
 * Genetics
 * Gerontology
 * Herpetology
 * Histology
 * History of Biology
 * Horticulture
 * Human Anatomy
 * Human Physiology
 * Ichnology
 * Ichthyology
 * Immunology
 * Limnology
 * Marine Biology
 * Microbiology
 * Molecular Biology
 * Mycology
 * Myrmecology
 * Neurobiology
 * Neuroscience
 * Ornithology

 * Plant Physiology
 * Population Genetics
 * Proteomics
 * Tropical Biology
 * Department of Tropical Diseases
 * Division of Paleontology
 * Palynology
 * Parasitology
 * Physical Biochemistry
 * Photobiology
 * Phycology
 * Physiology
 * Plant physiology
 * Biological psychology
 * Radiobiology
 * Sociobiology
 * Synthetic biology
 * Structural biology
 * Taxonomy
 * Virology
 * Zoology

School of Biomechanics

 * No topics yet

School of Marine sciences

 * Marine biology
 * Marine chemistry
 * Marine physics
 * Naval architecture and ocean engineering
 * Oceanography

School of Medicine
🇨🇴
 * Anatomy
 * Physiology
 * Histology
 * Diseases and conditions
 * Haematology
 * Cardiology and Vascular Medicine
 * Respiratory Medicine
 * Gastroenterology
 * Endocrinology
 * Nephrology
 * Neurology

 * Orthopedics
 * Rheumatology
 * Dermatology
 * Opthalmology
 * Anaesthesiology
 * Emergency Medicine
 * Obstetrics and Gynecology
 * Pediatrics
 * Podiatry
 * Psychiatry
 * Oncology

 * Geriatric Medicine
 * Otorhinolaryngology
 * Urology
 * Military Medicine
 * Pathology
 * Palliative Care Medicine
 * Community Medicine
 * Clinical Pharmacology
 * Laboratory Techniques

School of Alternative medicine
🇨🇴
 * Herbalism
 * Homeopathic Medicine
 * Energy Medicine
 * Meridian Therapy
 * Hypnosis
 * Neurolinguistic Programming

 * Ayurveda
 * Naturopathic Medicine
 * Traditional Chinese Medicine
 * Osteopathy
 * Chiropractic
 * Acupuncture

School of Dentistry

 * Endodontics
 * Orthodontics
 * Periodontology
 * Prosthodontics

School of Nursing

 * Pre-Nursing:Prerequisite Knowledge
 * Basic Nursing Care, History, and Theory
 * Medical/Surgical Nursing
 * Psychiatric Nursing
 * Maternal/Newbon Nursing
 * Pediatric Nursing

School of Pharmacy
🇨🇴
 * Pharmaceutics
 * Industrial Pharmacy\Pharmaceutical Technology
 * Biotechnology
 * Pharmaceutical Sciences
 * Pharmacology
 * Pharmaceutical Chemistry
 * Drug Design

 * Pharmacognosy
 * Phytochemistry
 * Toxicology
 * Spectrometry
 * Topic:Bioinformatics
 * Pharmacogenomics
 * Clinical pharmacy/Pharmacy practice

School of Veterinary Medicine
🇨🇴
 * Avian Veterinary Medicine
 * Bovine Veterinary Medicine
 * Canine Veterinary Medicine
 * Equine Veterinary Medicine
 * Feline Veterinary Medicine
 * Theriogenology
 * Small Ruminant Medicine
 * Swine Veterinary Medicine
 * Wildlife Veterinary Medicine
 * Zoo Veterinary Medicine

 * Veterinary Anatomy
 * Veterinary Histology
 * Veterinary Ethics
 * Veterinary Nutrition
 * Veterinary Biochemistry
 * Veterinary Pathology
 * Animal Reproduction, Gynaecology and Obstetrics

School of Plant Sciences

 * Phytochemistry
 * Plantlore
 * Medicinal Plants
 * Paleontology

School of Zoology

 * Animal physiology

title: Portal:Life Sciences/Topics


text:
User talk:Cad058

Welcome
Hello Cad058, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Gbaor 13:15, 13 February 2008 (UTC)

title: User talk:Cad058


text:
User talk:Jerina123

Welcome
Hello Jerina123, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Gbaor 13:15, 13 February 2008 (UTC)

title: User talk:Jerina123


text:
User talk:Mupaily

Welcome
Hello Mupaily, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Gbaor 13:15, 13 February 2008 (UTC)

title: User talk:Mupaily


text:
User talk:Reppuli

Welcome
Hello Reppuli, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Gbaor 13:15, 13 February 2008 (UTC)

title: User talk:Reppuli


text:
User:Philipv

Welcome. Content is TBD.

title: User:Philipv


text:
Wikiversity:Building successful learning communities

This is a learning project to explore how to build successful learning communities on Wikiversity. It is a continuation of a discussion in the learning model discussion group. Please help out to make this page as useful as possible, reflecting the experiences and thoughts of the Wikiversity community in its full diversity as fully as possible.

This project should:
 * Build a conceptual apparatus for discussing and thinking about its object of analysis.
 * Identify and discuss what has worked (or is working), and what hasn't (or doesn't) - in building learning communities on Wikiversity
 * Identify, describe, and analyse successful and unsuccessful learning communities elsewhere, ie not on Wikiversity
 * Find literature on both successful and unsuccessful learning communities, and other relevant topics

Wild communities
Wild communities are formed by attracting random Wikiversity visitors into a project. Attracting this group is the dream of all community-building, and it is also the hardest group to attract.

Examples are rare; the only known successful examples are: the film-making projects (e.g. Learning the Basics of Filmmaking), Web design. NB: the level of contribution by wild editors may be an issue here - needs analysing. The latter of these projects is not very active.

Tame communities
Tame communities are typically the classes of project coordinators. They have no choice about their participation and participate within the context of a real-world learning institution. They are invariably short term contributors only, but invest a lot of time in intense editing during this short period. Initial abilities tend to be low.

Examples include: Technical writing, Media literacy, Instructional Design, Design for the Environment, Social psychology (psychology), Introduction to Computers. This is the most common successful kind of participatory project on Wikiversity.

Insider communities
Insider communities consist of people who are already such regular Wikiversity contributors that they could be described as "insiders". When these people form a community around a new project, Wikiversity as a whole does not grow in terms of people. On the other hand, this group has a high level of familiarity with online learning and tends to build successful communities, so far as time allows.

Examples include: Composing free and open online educational resources and many reading groups.

Passive communities
Cf. Open Courseware.

A passive community might be understood as a paradox, if "community" is originally understood as presupposing active participation or actual editing. We can also understand the word "community" in a wider sense, embracing the majority of Wikiversity users who never create an account and passively consume learning materials. Catering for passive communities should not be considered a betrayal of the Wikiversity spirit - on the contrary, it may be that active communities are easier to build around a core of materials built for a passive audience, and that vice versa, the success of materials left behind by an active community should be judged by their attractiveness to passive audiences. This is the concept of the symbiosis of active and passive communities.

Projects for passive communities are created as stand-alone educational resources, usually by a coordinator who is also the sole major editor.

Examples include: many language learning courses (Breton, Swedish, Spanish), Trade Finance, Nonlinear finite elements.

Coordinators
A crucial part in the success of a community is the role of the "community leader" or coordinator.
 * The project coordinator forms and guides the community and project through its various stages of development. The coordinator usually has some kind of goal in mind. They shape the project and see it through to to an advanced state of completion or achievement of its aims.
 * A project coordinator may not necessarily be a major editor - much of their activity may be offline in the role of motivating their tame audience (class). Examples of low-editing coordinators include User:SRego and User:ReneeHobbs2007. Examples of high-editing coordinators include User:Phonebein and User:Robert Elliott.
 * There are examples of projects which have lost a coordinator, and where new coordinators have stepped in (e.g. Breton - change of coordinator from 2007 to 2008).
 * Some projects have multiple coordinators functioning as a team (e.g. Economic Classroom Experiments - with 3 coordinators).
 * Featured lists many of the most successful projects at Wikiversity. All of them have one thing in common: coordinators.

Projects with no coordinator
There have been many attempts at Wikiversity to create community without coordinators. Many of them are listed as stub pages ( members). These pages largely become forgotten.

The most likely examples for projects succeeding without a coordinator are to be found in the area of computer science and information technology. This is because information technology skills are the most common skills to be found among "wild audiences".

Coordinator terminology

 * Teacher: the term "teacher" might be considered an alternative word for coordinator. However Wikiversity experience does not bear this out. Coordinators often don't teach at all - at least not at Wikiversity. They are usually educators, but not always. Their real role lies in managerial skills such as establishing a framework for project, building the team and seeing the project through to fulfillment.
 * Leader/manager: these terms possibly don't give the right message. "Coordinator" is a more neutral word in an educational context.
 * Facilitator: perhaps.
 * Lead editor: counter-factual. Coordinators are not always the lead editor.

Discussion: the coordinator-hypothesis
The "coordinator hypothesis" is this: although projects for tame and passive communities are more successful than projects for wild and insider communities, it is not the type of community which makes the difference between success and failure; instead the crucial factor for the success of a community is whether or not it has a coordinator.

What has worked, or is working
''Please give an account of a learning community which has been (or is) successful. Explain why you think it's successful, and perhaps what aspects of it that you think make it a success..''

Bloom Clock

 * Why: well, in fact is more research community, but it is succesful. I think, people study the plats they dont know. It si technically catched, even this can caused problems for new users, who havent been on wiki for a long time.
 * The Bloom Clock project has succeeded in building a small community. The most frequent community appears to be an "insider" community, but "wild" editors also seem to have been involved. The success of the project revolves around the coordinator and lead editor User:SB_Johnny.

What hasn't worked, or doesn't
As above, give an account of a learning community that hasn't worked (or doesn't work), giving your reasons for saying so, and why you think it is so..

Identifying communities outside Wikiversity
It would be good to describe in as much detail what the community is, what it aims to do, and why it has or hasn't been a success. We can then analyse this to see what we can take from it for our own context.

Successful communities
Primary schools are successful due to a core of experienced staff, student-continuity, strong public/parental support, multiple learning models, historical development, the ability for teachers to quietly fail ... and fulfilment of the need to earn the money; WV has the first of these. Schools start to fail when they start to not make the grade on one or two of these and with luck plus time and not too many noticing they can get back on track. Early days for WV and internet time is such a tricky metric Paulmartin42 19:38, 13 August 2008 (UTC)

Unsuccessful communities

 * User:Roadrunner's thoughts about the rise and fall of MOO universities should be read!

Increase support for tame communities
The first two years of life of Wikiversity (2006-2008) show that the "tame community" is the most successful participatory model for Wikiversity projects. However to date, Wikiversity has been wrongly focussed on "wild communities". In conjunction with this error, Wikiversity has also tended to overestimate the ability of new users: the target user was "an ex-Wikipedia editor", which is what many of the founders of Wikiversity were themselves.

As a correction to this view, Wikiversity needs to build a new concept of the most likely kind of editor/learner.

Tame communities have unusual characteristics which other Wikimedia projects have never catered for.
 * Short timeframe of activity; deadline often set by external class schedule.
 * Unusually low level of editing experience.
 * High level of motivation.
 * Strong focus on a set task, usually provided by a real-world educator.
 * More time available.

In response to this, Wikiversity will need to:
 * Provide better tutorials and other forms of passive help to orientate this kind of user faster.
 * Train its own people to recognize this kind of editor and distinguish them from vandals (see Learning to edit a wiki/Lesson plan A for the reason why vandalism is mentioned here).
 * Worry less about editor-retention (see bowing before the inevitable).

Embolden coordinators
The "old" Wikiversity concept of participation exuded an attitude of deference towards the superior, almost mythical, wild community. Editors who created new projects were encouraged not to take up dominant leadership roles, and instead merge or submerge their identity as elearning pioneers into a community of equals. This attitude derives in part from the culture of Wikipedia, in which the concept of "page ownership" is the antithesis of political correctness. Another origin for the attitude was an occasional anti-educationalism, which rejected the traditionally hierarchical teacher-student model of learning and looked for greater equality.

Despite this "old" Wikiversity concept of project non-leadership, the successes of the past show that this concept was often rejected. Where strong coordinators emerged, so did success.

Learning from these experiences, Wikiversity needs a new model of project leadership.

 * Page ownership: although there will still be no such thing as page ownership, the coordinator's special role in a project needs to become something recognized and respected as a matter of Wikiversity culture. To some extent, this is already the case for established users. New coordinators need to be made more aware of this role. The role of coordinator is one of the things which distinguishes Wikiversity from Wikipedia. In this context, coordinators need to quickly become aware of forking and its implications for project leadership.
 * Hierarchies: the role of coordinator is not intended as a reintroduction of the traditional (or autocratic) teacher-student model. As was noted above, the experience of coordinators at Wikiversity is that their Wikiversity activities lie more in the managerial than the pedagogical area. Management science offers alternative models to that of autocracy.
 * The guiding hand: help pages need to be developed which flesh out the role of coordinator. For example, as coordinators are often the real-world teachers of the classes that are Wikiversity's "tame communities", coordinators need guidance as to what they should and should not tell other users what to do. The current tendency is for coordinators to do too little ("laissez faire") because they are not aware of the trouble their students' inexperience can get them into (e.g. copyright violations).
 * Staying the full course: a very simple idea. Coordinators simply need to be advised that they both are allowed to and are advised to stay with the project until it has reached its goals.

Dynamic community concepts
This idea is that in the lifecycle of a project, the type of community involved with it naturally changes. The concept of a permanently evolving learning project with a community drawn from the wild is static. The dynamic concept of community accepts a model (for example) where a project begins with a tame community, draws in an additional and smaller wild community in its later stages of development, before finally reaching a maturity where its associated community is primarily passive.

Symbiotic community concept
This idea holds that the active community concepts (wild, tame, insider) are symbiotic with passive community concepts: active communities are easier to build around a core of materials built for a passive audience, and vice versa, the success of materials left behind by an active community should be judged by their attractiveness to passive audiences.

Literature
Please add literature here (it doesn't have to be from any particular source - it can come from blogs, newspapers, academic journals, books, etc.)
 * Heather James: "My brilliant failure: Wikis in classrooms" - and her notes on why she thinks it didn't work.


text:
Talk:Astrophysics Source Code Library

What about CosmoMC? http://cosmologist.info/cosmomc/ Or CAMB? http://camb.info/ Or any starlink software? http://www.starlink.rl.ac.uk/

Dead link
During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!

 * http://www-theorie.physik.unizh.ch/astrosim/code/doku.php
 * In Astrophysics Source Code Library on 2012-08-12 07:37:41, 404 Not Found
 * In Astrophysics Source Code Library on 2012-08-19 07:37:41, 404 Not Found
 * In Astrophysics Source Code Library on 2012-08-26 07:37:40, 404 Not Found

--Mu301Bot (talk) 07:37, 26 August 2012 (UTC)

title: Talk:Astrophysics Source Code Library


text:
Draft:Respiratory system

Without the Respiratory system in our body, we wouldn't be able to breathe, and live.

Anatomy of the Respiratory System
In the order in which the air typical passes through the respiratory system:

Nasal Passage (Nose)
When we breathe in, the air can be dry and cold, and may have particles in it. The nasal passage helps to warm up air, and increases the amount of moisture in the air.

Filter system of the nasal passage
The nose-hairs catch large particles, helping to stop them from going further into the body.

The mucus (snot, or the "green-slime" in your throat) lines the walls of the nasal passage. As mucus is sticky, most small particles that don't get caught by the nose-hairs get stuck to this.

Picking your nose essentially clears these filters! If someone doesn't breathe in through their nose (and instead breathes in through their mouth), the air skips this filter system.

Oral Passage (Mouth)
When air is breathed in through the mouth, instead of the nose, the air is typically drier, colder, and more dirty.

Pharynx
The pharynx connects/merges the path for the nasal (nose) and oral (mouth) passages.

Epiglottis
The larynx is a flap of skin, just above the larynx, which can open and close in order to stop food and drink from going into the larynx (voice-box), towards the lungs. When it is closed, it instead forces the food or drink into the esophagus (towards the stomach).

Larynx (Voice-box)
Inhaled air goes through the larynx (voice-box). This voice-box contains muscles which can control how the air leaves the body, in order to help form words.

Trachea (windpipe)
The trachea (windpipe) is a long tube which the air passes through to get to the lungs. It connects the larynx to the lungs.

Carina
The carina is where the trachea (windpipe) splits into the left and right main-bronchus.

Bronchi
The bronchi are the tubes which connect the trachea to the alveoli.

Main bronchus: when you are talking about the main section of the bronchus, before it has split up into the bronchi, you call it the 'Main bronchus', or 'Main bronchi' if you are talking about more than 1 of them.

Lobar bronchus: when you are talking about the divided section of the bronchus, after the main bronchus has split up, you call it the 'lobar bronchus', or 'lobar bronchi' if you are talking about more than 1 of them.

Due to the way the bronchus is formed, if an object managed to get into the bronchi, it is more likely to fall into the right main bronchus due to gravity, as it has more of a slope than the left main bronchus;

Alveoli + alveolar ducts
The alveoli mark the end of the bronchi path.

The alveolar ducts are tiny, and they connect the respiratory bronchioles to the alveolar sacs, which contain a collection of alveoli.

The alveoli have a very thin wall, which allows oxygen to pass through it into the blood, and for carbon dioxide to leave through the wall, into the lungs.

When you breathe in, and the lungs expand to do this, the alveloi inflate (and become much larger in size) as they are being stretched open.

The alveoli are covered in the protein elastin, which allows them to stretch out. When the intercostal muscles and diaphragm relax, this elastin naturally recoils; this means the alveoli won't remain puffed up, which would mean that air would not be replaced properly; this is also the main reason for the lungs shrinking in size.

title: Draft:Respiratory system


text:
User:Mike's bot account/Modified message

Thanks for uploading image(s) to Wikiversity. The Wikimedia Foundation is very careful about what Wikiversity includes because of copyright law, and requires that we maintain a strict copyright policy. Some or all of your uploaded files may soon be deleted unless we can determine the copyright holder and status. The copyright holder is usually the creator, the creator's employer, or the last person who was transferred ownership rights. Please take the time to read Copyright to learn more about what copyright information is required to satisfy our requirements and remember to include this important information for every file that you upload in the future as well. The images currently affected will be listed below shortly. Please edit each image description page to add a license template and source. If you have any questions, feel free to contact this bot's owner, Mike.lifeguard, or ask another editor at Colloquium.


text:
User talk:Cubez

Image:Wiki circuit diagram.jpeg
Please provide a license template and source for this image. Thanks. – Mike.lifeguard | @en.wb 22:02, 13 February 2008 (UTC)

title: User talk:Cubez


text:
User talk:Alcoholi

Image:Drunk.jpg
Please provide a source and license template for this image. Thanks. – Mike.lifeguard | @en.wb 22:27, 13 February 2008 (UTC)

title: User talk:Alcoholi


text:
User talk:Cameroncb1

Image:VoltageFollower.png
Please provide a license template and source for this image. Thanks. – Mike.lifeguard | @en.wb 22:55, 13 February 2008 (UTC)

title: User talk:Cameroncb1


text:
User talk:Rhys Andrew Cook

Image:Pootsyfrustrated.png
Please provide a license template and source for this image. Thanks. – Mike.lifeguard | @en.wb 22:57, 13 February 2008 (UTC)

File:Wonderland Adventures Pootsy.png
Hello Rhys Andrew Cook. I'm here to inform you that one of your files, File:Wonderland Adventures Pootsy.png, is up for deletion as having been copyrighted from http://wonder.3pointstudio.com/wiki/Pootsy from http://www.midnightsynergy.com/; please bear in mind Wikiversity does not accept copyrighted materials unless they have a fair use tag attached to them and are legitimately in use in an educational context. If you manage to obtain permission from the copyright holder agreeing to release it under a free license, or you want to use the file in a manner consistent with Wikiversity's fair use policy, please notify me and I will change the tag accordingly. Thanks, TeleComNasSprVen (discuss • contribs) 05:26, 15 March 2014 (UTC)

title: User talk:Rhys Andrew Cook


text:
User talk:Pianoman55

Image:Musdirectwikiversitysmaller.GIF
Please provide a license template and source on the image description page. Thanks. – Mike.lifeguard | @en.wb 23:06, 13 February 2008 (UTC)

title: User talk:Pianoman55


text:
User talk:Chris Rojas

Image:L 43ffb3e7ce63a2f33da94f51a8ca65ed.jpg
Please provide a license template and source on the image description page. Thanks. – Mike.lifeguard | @en.wb 23:07, 13 February 2008 (UTC)

title: User talk:Chris Rojas


text:
User:Cookiemonster~enwikiversity

Behold the power of cheese

title: User:Cookiemonster~enwikiversity


text:
Advanced energy engineering research

Part of the Energy Engineering Department

Nuclear Energy:

Reviews:
 * Jasmina Vujic, Nuclear Eng., UC Berkeley, "Heat pipe encapsulated nuclear heat source". Forefront, Fall 2007.
 * W. Hannum, G.E. Marsh, G.S. Stanford, Argonne Nat'l Lab, "Advanced Liquid Metal Reactors." 1983-2003. (Fast Neutron Reactors and pyro-metallurgical processing) (SciAm article)
 * J.A. Lake. "The Renaissance of Nuclear Energy" (website)
 * C. Schmidt. "The next generation of nuclear power?" (website)
 * http://web.mit.edu/nuclearpower/
 * Making the World Safe for Nuclear Energy
 * Generation IV Nuclear Energy Systems
 * Pebble Bed Modular Reactor
 * Onkalo Waste Management Project (Posiva)

Thermoelectricity:

 * Arun Majumdar, Mechanical Eng., UC Berkeley, "Thermoelectrics". Forefront, Fall 2007. (benzendithiol, silicon, ceramics as dielectrics) (Tech Review article)

Photovoltaic:

 * Ilan Gur, UC Berkeley. Inorganic nanocrystals. 2005. (dirt cheap inorganic solar panels) (Nanotech-Now article)

title: Advanced energy engineering research


text:
Talk:Conservation of money calculations and status reporting

better in main namespace? --Remi 05:09, 14 February 2008 (UTC)


text:
User talk:Stevesilsbee

Welcome
Hello Stevesilsbee, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Gbaor 09:14, 14 February 2008 (UTC)

TEFL-TESOL
Please see also the Naming conventions (i.e. no abbreviations if possible), and add relevant category to your page --Gbaor 09:14, 14 February 2008 (UTC)

title: User talk:Stevesilsbee


text:
User talk:Gbaor/Sandbox

ha, neat! --Remi 09:48, 14 February 2008 (UTC)
 * thx! :) --Gbaor 13:17, 18 February 2008 (UTC)

title: User talk:Gbaor/Sandbox


text:
User:Remi/Topics

Template:Medicine topics Template:Engineering-list

Topics by school for Portal:Life Sciences

School of Biology
🇨🇴
 * Agriculture
 * Anatomy
 * Arachnology
 * Division of Human Biology
 * Animal Physiology
 * Biochemistry
 * Bioinformatics/Computational Biology
 * Biomechanics
 * Bionomics
 * Biophysics
 * Biotechnology
 * Botany
 * Cell Biology
 * Ecology
 * Entomology
 * Engineering biology
 * Ethology
 * Evolution
 * Evolutionary Biology
 * Evolutionary Ecology
 * Evolutionary Virology
 * Exobiology

 * Genome Analysis
 * General Biology
 * General Botany
 * Genetics
 * Gerontology
 * Herpetology
 * Histology
 * History of Biology
 * Horticulture
 * Human Anatomy
 * Human Physiology
 * Ichnology
 * Ichthyology
 * Immunology
 * Limnology
 * Marine Biology
 * Microbiology
 * Molecular Biology
 * Mycology
 * Myrmecology
 * Neurobiology
 * Neuroscience
 * Ornithology

 * Plant Physiology
 * Population Genetics
 * Proteomics
 * Tropical Biology
 * Department of Tropical Diseases
 * Division of Paleontology
 * Palynology
 * Parasitology
 * Physical Biochemistry
 * Photobiology
 * Phycology
 * Physiology
 * Plant physiology
 * Biological psychology
 * Radiobiology
 * Sociobiology
 * Synthetic biology
 * Structural biology
 * Taxonomy
 * Virology
 * Zoology

School of Biomechanics

 * No topics yet

School of Marine sciences

 * Marine biology
 * Marine chemistry
 * Marine physics
 * Naval architecture and ocean engineering
 * Oceanography

School of Medicine
🇨🇴
 * Anatomy
 * Physiology
 * Histology
 * Diseases and conditions
 * Haematology
 * Cardiology and Vascular Medicine
 * Respiratory Medicine
 * Gastroenterology
 * Endocrinology
 * Nephrology
 * Neurology

 * Orthopedics
 * Rheumatology
 * Dermatology
 * Opthalmology
 * Anaesthesiology
 * Emergency Medicine
 * Obstetrics and Gynecology
 * Pediatrics
 * Podiatry
 * Psychiatry
 * Oncology

 * Geriatric Medicine
 * Otorhinolaryngology
 * Urology
 * Military Medicine
 * Pathology
 * Palliative Care Medicine
 * Community Medicine
 * Clinical Pharmacology
 * Laboratory Techniques

School of Alternative medicine
🇨🇴
 * Herbalism
 * Homeopathic Medicine
 * Energy Medicine
 * Meridian Therapy
 * Hypnosis
 * Neurolinguistic Programming

 * Ayurveda
 * Naturopathic Medicine
 * Traditional Chinese Medicine
 * Osteopathy
 * Chiropractic
 * Acupuncture

School of Dentistry

 * Endodontics
 * Orthodontics
 * Periodontology
 * Prosthodontics

School of Nursing

 * Pre-Nursing:Prerequisite Knowledge
 * Basic Nursing Care, History, and Theory
 * Medical/Surgical Nursing
 * Psychiatric Nursing
 * Maternal/Newbon Nursing
 * Pediatric Nursing

School of Pharmacy
🇨🇴
 * Pharmaceutics
 * Industrial Pharmacy\Pharmaceutical Technology
 * Biotechnology
 * Pharmaceutical Sciences
 * Pharmacology
 * Pharmaceutical Chemistry
 * Drug Design

 * Pharmacognosy
 * Phytochemistry
 * Toxicology
 * Spectrometry
 * Topic:Bioinformatics
 * Pharmacogenomics
 * Clinical pharmacy/Pharmacy practice

School of Veterinary Medicine
🇨🇴
 * Avian Veterinary Medicine
 * Bovine Veterinary Medicine
 * Canine Veterinary Medicine
 * Equine Veterinary Medicine
 * Feline Veterinary Medicine
 * Theriogenology
 * Small Ruminant Medicine
 * Swine Veterinary Medicine
 * Wildlife Veterinary Medicine
 * Zoo Veterinary Medicine

 * Veterinary Anatomy
 * Veterinary Histology
 * Veterinary Ethics
 * Veterinary Nutrition
 * Veterinary Biochemistry
 * Veterinary Pathology
 * Animal Reproduction, Gynaecology and Obstetrics

School of Plant Sciences

 * Phytochemistry
 * Plantlore
 * Medicinal Plants
 * Paleontology

School of Zoology

 * Animal physiology

title: User:Remi/Topics


text:
Template:Marine sciences

 * Marine biology
 * Marine chemistry
 * Marine physics
 * Ocean engineering and Naval architecture
 * Oceanography

title: Template:Marine sciences


text:
Software process management

Resources

 * Agile software development
 * Software Process Improvement Models
 * Configuration Management (SPM)
 * Software Metrics and Measurement
 * Process and People

title: Software process management


text:
User:Phantom~enwikiversity

Hi, This is Phantom's page. An International Law insider. Hope to find some quality time to provide useful information for anyone, particularly students, particularly in the field of International Humanitarian Law. Hope you like it. Phantom 13:37, 14 February 2008 (UTC)

title: User:Phantom~enwikiversity


text:
Talk:Writing a simple greeting bot for MediaWiki/Introduction to MediaWiki scripting access

This is a very good script. Can somebody please write the same for VB?

Thanks.


text:
User talk:Phantom~enwikiversity

Welcome
Hello Phantom, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 16:24, 14 February 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Phantom. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Phantom~enwikiversity that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:41, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 06:17, 19 April 2015 (UTC)

title: User talk:Phantom~enwikiversity


text:
User talk:MScCompTralee0708

Welcome
Hello MScCompTralee0708, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 16:27, 14 February 2008 (UTC)

title: User talk:MScCompTralee0708


text:
Pakistan and Bangladesh

Pakistan and Bangladesh are the two Islamic countries located in the South Asia region.

This area is for learning and research related to both Pakistan and Bangladesh.

 * Pakistan has a prevailing Islamic culture with its official name as Islamic Republic of Pakistan .Majority of the population is Muslim however the minorities are free to practise their customs and traditions.Most of the traditions of the muslims living in Pakistan are those which were common at the time of united sub-continent (before Pakistan's independence).However these are such that they may not clash with the religion.This state has no ethnic extremism policy.

 * Bangladesh

Discussion questions

 * How can peace be promoted inside both Pakistan and Bangladesh?
 * How can peace be promoted between both Pakistan and Bangladesh?
 * How can economic prosperity be promoted in both Pakistan and Bangladesh?

title: Pakistan and Bangladesh


text:
User:Ted Houk

Theodore Carl Houk, M.D. http://www.healingtheworld.com/ Diplomate, American Board of Internal Medicine Maryland State Council on Physical Fitness and Cardiovascular Disease and Stroke, Member Emeritus Suite 301, 7402 York Rd Towson, MD 21204-7522 USA

My paternal grandfather Theodore W. Houk, M.D. has a page, he passed in 1977 or so. My website describes my practice and approach to my 2000 patients. I've cared for 10,000 since beginning clinical work in in 1987.

title: User:Ted Houk


text:
User talk:Ted Houk

Welcome
Hello Ted Houk, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 22:01, 14 February 2008 (UTC)

title: User talk:Ted Houk


text:
User:Ethan D

My name is Ethan D. I am a 24 year old DJ from South Jersey. My interests are in music theory and composition, ear training, and other relevent courses. Feel free to contact me with any questions thoughts. -E-

title: User:Ethan D


text:
Agile software development

The Need for Agile methods
@todo

The Agile Manifesto
On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground and of course, to eat. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened. Now, a bigger gathering of organizational anarchists would be hard to find, so what emerged from this meeting was symbolic a Manifesto for Agile Software Development signed by all participants. Taken from: "History: The Agile Manifesto"

So why bother with agile methodologies? Alistair Cockburn did research about how a process influences project teams. He concludes that the larger a project team the more a process can influence the effectiveness of the project development. However it is the people in the project teams that repeatedly argue the process that is proposed to use. Alistair Cockburn summarizes this behaviour in his quote: “People trump process”. It is true that good enough people in a team can deliver a solution where no process can improve the quality of the outcome. The most interesting part that contributed to the manifestation of agile methodologies is the fact that people working together with good communication and interaction have the ability to perform at significant higher levels than operated on an individual basis. According to Cockburn this becomes apparent time and again in brainstorming and joint problem-solving sessions. This the reason agile methodologies can contribute to project teams by focusing on increasing both the individual competencies and the collaboration levels.

For further reading visit: URL:http://agilemanifesto.org

Authors of the Agile Manifesto
On February 11-13, 2001, seventeen people met at the Lodge in the Wasatch mountains of Utah, they initiated an agile manifesto.

They were :
 * Kent Beck
 * Mike Beedle
 * Arie van Bennekum
 * Alistair Cockburn
 * Ward Cunningham
 * Martin Fowler
 * James Grenning
 * Jim Highsmith
 * Andrew Hunt
 * Ron Jeffries
 * Jon Kern
 * Brian Marick
 * Robert C. Martin
 * Steve Mellor
 * Ken Schwaber
 * Jeff Sutherland
 * Dave Thomas

The Agile manifesto encompassed the idea of several pre-existing methodologies including:
 * Extreme Programming
 * SCRUM
 * DSDM
 * Adaptive Software Development
 * Crystal,
 * Feature-Driven Development,
 * Pragmatic Programming
 * Lean Development

These authors all work for the software industry, and did a great distribution on agile software development. That’s the reason why they became participates for the Agile manifesto.

Defining traits of Agile Methodologies
Agility is the ability to both create and respond to change in order to profit in a turbulent business environment - Jim Highsmith, Agile Software Development Ecosystems

Such a general description allows a lot of room for debate as to whether a particular methodology is Agile or not. Where there is debate, it is fair to say that a methodology which doesn't have the following principles cannot consider itself Agile.

 * Least Design Up Front
 * Accommodates changing requirements, even late in the development cycle
 * Iterations are measured in weeks, not months
 * Low bureaucracy and administration overhead
 * Continuous customer feedback and involvement
 * Complete buy-in from all stakeholders

It's also fair to say that an Agile team that fails to realize any of these principles will struggle and probably fail.

Adaptive Software Development
Adaptive software development is a management to control software project for changeable requirement and short period project.

The three key point of adaptive software development are:
 * speculation
 * collaboration
 * learning

“The overriding, powerful, indivisible, predominant benefit of the Adaptive Development Life Cycle is that it forces us to confront the mental models that are at the root of our self-delusion. It forces us to more realistically estimate our ability.” - Jim Highsmith

Crystal Methods
To view the Crystal Methods section, please click the following link:

Crystal Methods

Dynamic Systems Development Method (DSDM)
What is DSDM?

DSDM is an example of an iterative (Agile) development model. DSDM approaches every step in the process to be completed only enough to be able to move to the next step. Since agile development is applied in situations where business requirements are likely to change, any further work would not benefit the overall process of delivery. The DSDM Consortium defines DSDM as a framework based on best practises that can be used to deliver new systems, which combines the most effective use of people's knowledge, tools and techniques to achieve tight project delivery timescales. The DSDM framework serves as a basis for a development and implementation process whether it is an IT project or a business change. The framework includes people (staff and skills), the technology that supports them (IT) and the processes that bind them all together (the business strategy).

Why DSDM?

The goal of DSDM is to target a demand for organizations to deliver working systems in shorter timescales. A typical DSDM project delivers an operational system within six months. The main emphasis however is that, according to the DSDM organization, most projects fail because of people issues rather than technology. Therefore the focus is providing people with guidelines to work together in a way that business goals are achieved successfully.

Because of the agile approach, DSDM build systems focus on the current needs in contrast to the traditional approach of going through all the perceived possibilities. Therefore, the resulting system is expected to better fit the business needs, be easier to test and be more likely to be accepted into the users' working practices.

The DSDM Framework Principles

The framework is based on nine initial principles which are applied in the different phases of the methodology:

Source: DSDM Consortium, underlying principles
 * 1) Active user involvement is imperative
 * 2) DSDM teams must be empowered to make decisions
 * 3) The focus is on frequent delivery of products
 * 4) Fitness for business purpose is the essential criterion for acceptance of deliverables
 * 5) Iterative and incremental development is necessary to converge on an accurate business solution
 * 6) All changes during development are reversible
 * 7) Requirements are baselined at a high level
 * 8) Testing is integrated throughout the lifecycle
 * 9) A collaborative and co-operative approach between all stakeholders is essential

The DSDM Framework Phases

The framework defines phases that apply to the process in the case of a new system development or the change of business processes. The core project process is preceded by the Pre-Project phase and end with the Post-Project phase:

 * Pre-Project
 * Feasibility Study
 * Business Study
 * Functional Model Iteration
 * Design and Build Iteration
 * Implementation
 * Post-Project

Within DSDM the phases “Feasibility Study” and “Business Study” are firstly done in sequence. Because these phases set the foundation rules for the rest of the iterative and incremental development in the remaining phases, they must be before any other work is done in a project. With these first two core phases done, the other three phases can overlap and be merged in any other order appropriate to the project. When the project solution is delivered the project team will hand over the solution to the Post-Project phase. This final phase includes the process of maintaining the solutions operations and monitoring the performance to make sure that the business requirements have been met.

Within each phase the goal is to produce a minimum set of products. These products are often specific documentation with a defined criteria and purpose. As a result the achievement of every purpose can be assessed. The way these products are produced and what the content will be, is left open for the concerning organization or project to determine. Table 1 provides an overview of the activity and products that apply to the DSDM phases.

''Table 1. DSDM activity and products''

For further reading visit: URL:http://www.dsdm.org/version4/2/public/default.asp

Overview
Feature Driven Development(FDD) is a model driven process of short iterations (two weeks). An overall model is established at the beginning of a project after which the project continues with a series of design by feature/build by feature iterations. A feature is a small and “useful in the eyes of the client” result.

Processes
FDD consists of five processes, three of which are per project, the other two being per feature.

Develop an Overall Model
This process involves the domain experts, chief architect and chief programmers. The main goal here is to establish the overall shape of the system. Classes and their inter relationships are defined.

Build Feature List
This process involves the domain experts, chief architect and chief programmers. Its goal is to produce fine grained feature list. Essentially the model developed in process 1 is functionally decomposed into subject areas. Each subject area contains business activities and each business activity can be broken into a number of business steps. The categorisation of these steps forms the feature list.

Plan By Feature
The feature sets are sequenced into a high level plan and assigned to chief programmers.

Design by Feature
A small set of features are designed by a feature team. Each feature is represented by a sequence diagram in UML. This diagram is the design deliverable and is peer reviewed by the feature team against the requirements.

Build By Feature
The code for each feature is written by the members of the team who own the business classes affected by the functionality of that feature. The completed code is peer reviewed. Once the code has passed the review and been unit tested it is marked for inclusion in the system build.

Best Practices
FDD is built around a set of eight best practices each of which complements the other. The practices are not exclusive to FDD, but are used in a unique combination in FDD.

Domain Object Modeling
@todo

Developing by Feature
@todo

Individual Class (Code) Ownership
@todo

Feature Teams
@todo

Inspections
@todo

Regular Builds
@todo

Configuration Management
@todo

Reporting/Visibility of Results
@todo

Milestones
For each feature of the feature list there are six discrete milestones. Three of which belong to the Design by Feature process; Domain Walkthrough, Design, Design Inspection; and three which belong to the Build by Feature process; Code, Code Inspection, Promote to Build.

Domain Walkthrough
@todo

Design
@todo

Design Inspection
@todo

Code
@todo

Code Inspection
@todo

Lean Development
Although Robert Charette originally defined the principles of Lean Development, he has not been it's primary proponent nor has he contributed much to the body of work relating to Lean Software Development. Instead, Lean Software Development has mainly been popularized through the work of Mary and Tom Poppendieck. They describe in detail how to apply the principles of lean production to the software development process. They specify a set of seven principles and 22 tools to help realise those principles. (Charette lists twelve principles )

Lean Production
Since Lean Development derives it's principles and practices from Lean Production it is important to have an understanding of Lean Production (sometimes referred to as Lean Manufacturing).

The concepts and tools of Lean Production were laid out in Womack, Jones and Roos book "The machine that changed the World: The Story of Lean Production". Lean Production draws on several production processes including Toyota Production System (TPS), just-in-time manufacturing and inventory management as well as adding it's own ideas to the mix. One of the key ideas in Lean Production - eliminate waste - is drawn from TPS. TPS has an extensive definition for waste, breaking it down into seven categories and suggesting how to deal with each one. Lean Software development then is the application of the principles of Lean Production to the software process.

Benefits of Lean Development
Lean Development allows companies to manage their risk and turn that risk into an opportunity. Robert Charette refers to this as "risk entrepreneurship" [Agile Software Development Ecosystems, Highsmith, 2002]. By proactively dealing with risk and adapting to changes in the market place brought about by circumstances and competitors a company can gain a competitive advantage. Lean Development enables software systems to adapt to this change rapidly, something that software systems are generally known for.

Principles of Lean Development
There are seven principles of lean development (though sometimes twelve are listed). Also, the naming of some of the principles has changed with time.

In Lean Software Development : An Agile Toolkit the following principles are listed
 * Eliminate Waste
 * Amplify Learning (Create Knowledge)
 * Decide as Late as Possible (Defer Commitment)
 * Deliver as Fast as Possible (Deliver Fast)
 * Empower Teams (Respect People)
 * Build Integrity In (Build Quality In)
 * See the Whole (Optimise the Whole)

(Titles in brackets are apparently newer names used in Implementing Lean Software Development )

Eliminate Waste - The Core Principle
In TPS, Taiichi Ohno analysed the concept of waste in great detail and categorised different types of waste, and ways of addressing them. In explaining Ohnos concept of waste, Poppendieck uses the phrase "anything which does not create value for a customer is waste" [ASDE, Highsmith] and when applied to software development this translates to implementation of features that are not core requirements, poor or missing requirements, administrative overhead and bureaucracy. Poppendieck maps Ohnos concepts of waste to software as follows:

Tools: Seeing Waste, Value Stream Mapping

Amplify Learning
Take advantage of the short iterations and feedback from customers to learn how to improve the product and the process. Present a choice of solutions as working prototypes rather than explore possible solutions. This way you limit choice as well as get a head start on the final solution.

Tools: Feedback, Iteration, Synchronization, Set-Based Development

Decide as Late as Possible (Defer Commitment)
In traditional software development processes, important decisions are made far in advance of implementation. Any mistakes made at the distant planning stage are amplified in implementation and their effect on the whole process. By deferring decisions to as late as possible the implications of mistakes are limited and you also can deal with change more easily.

Tools: Options Thinking, The Last Responsible Moment Making Decisions

Deliver as Fast as Possible (Deliver Fast)
Business success is often achieved by responding rapidly to change. A customer who needs a system for commercial applications wants that system as fast as possible. The faster you can deliver that system the greater the value to the customer and the greater the long term benefit to you. The concepts of this principle are related to the theory of Just-In-Time delivery.

Tools: Pull Systems, Cost of Delay, Queuing Theory

Empower Teams (Respect People)
"An organization that respects software developers as professionals will expect them to design their own jobs with proper training, coaching, and assistance. It will expect them to improve continually the way they do their work as part of a learning process. Finally, it will give them the time and equipment necessary to do their jobs well. In a lean organization, the people who add value are the centre of organizational energy. Frontline workers have process design authority and decision-making responsibility; they are the focus of resources, information and training." [Chapter 5]

Instead of treating software developers as cogs in a wheel, respecting their needs and abilities will give them a sense of responsibility and increase their motivation, and ultimately benefits everyone. Tools: Self-Determination, Motivation, Leadership, Expertise

Build Integrity In (Build Quality In)
Perceived Integrity - the ability of the software to "delight" the customer by functioning well, and Conceptual Integrity - a sense of cohesiveness and integrity between different parts of the system are key demand of customers. Refactoring and Testing ensure that these goals are achieved.

Tools: Perceived Integrity, Conceptual Integrity, Refactoring, Testing

See the Whole (Optimize the Whole)
By choosing the right measures and interpreting the measures correctly we can find the root cause and source of defects in systems. The assumptions are that defects are caused by individuals when in fact they are the caused by the processes and procedures in the system. Also, most projects are made up of many sub-teams, vendors and contractors. A shared agreement and understanding of goals is of huge benefit for the project and company in the long term.

Tools: Measurements, Contracts

Extreme Programming
Extreme Programming (XP) was developed by Kent Beck in mid 90’s. As projects reduced in size and became more dynamic with rapidly changing requirements, there was a need for quick project development life-cycle. Since 70’s widely used approach had linear structure characteristic known as “Waterfall Model”, project scope was planned out at the beginning of the project life-cycle, in which changing requirements in the middle of the development, made it very costly. Frequently changing requirements by customers required for more agile approach.

XP is known as a methodology of Agile development. This is used in small, collocated project teams up to 10 members, more is probable. Development is flexible and lightweight. XP is based on twelve practices and four groups - collaboration, feedback, revision and respect. Code is the most important part of XP, complete documentation is considered as a waste of assets. Simple code and design form the basis; this is understandable to programmers who join the team at the later stages. Peer programming complements it – what is obvious for one, is not for another, following the decisions is easy to understand the thought of the colleague.
 * Collaboration – active participation of all stakeholders of the project in which customer is a part of the development team. Project starts with creating simple design and ‘hands on’ coding. Test Driven Development approach is applied by adding new functionality to the code. Focus is on today tasks and requirements rather than looking at long-term. Regular meetings are held and frequent verbal communication between programmer team is practiced. Feedback acquired immediately through iterative structure of the development.
 * Feedback – feedback is effective if it is instantaneous. System feedback is achieved through Unit Testing. Unit Tests are created for the software throughout development phase on which complete software is built. Any changes to the requirements is done through collaboration process with customers who give the feedback to the existing model, changes are taken into account and presented as new requirements. XP exercise ‘Use Case’ diagrams and ‘Story boards’ through which requirements are presented.
 * Revision – XP development focuses on current tasks and problems. This makes written code often unstructured as it should be. Since the structure of the code is not planned out at the beginning of the project, regular refactoring is recommended and even compulsory for further development and maintenance. This takes courage to redesign the system and even sometimes discard completely parts of the code to implement a new functionality.
 * Respect – XP practices programming in pairs. Programmers split tasks, one is typing code (person is known as a ‘driver’), while the other programmer is following the code and working on an algorithm to solve the problem. Roles change in time. This is a good practice because every decision of the team matters which leads to the team loyalty.

There are twelve core practices in XP stated as a standard:
 * 1) Coding Standards – mutually agreed standard by the team throughout the development on language used, vendors, rules and format.
 * 2) Collective Code Ownership – every programmer in the team has a right on the code. Suggested to use repositories to store the code, every programmer has access rights.
 * 3) Simple Design – problem should be tackled and the simplest outcome should be applied.
 * 4) System Metaphor – classes and functions should do what they say on the ‘label’, naming should be given in mutual understanding for the functionality.
 * 5) Pair Programming - two programmers work on one task, one is typing and following the lead of the other who focuses on the functionality and algorithms to solve the problems, also reviewing written code.
 * 6) Planning Game – regular project meetings are held and are divided into release planning in which customers request necessary changes and new functionality, and iteration planning which is done after completing the iteration by presenting functional software.
 * 7) Test Driven Development – creation of a test case following by writing a code that satisfies the desired test result.
 * 8) Whole Team – all project stakeholders are actively involved and work together.
 * 9) Continuous Integration - team members should work on the latest release of the software, some team members who work on the delayed parts should integrate the code into the main release repositories as soon as possible.
 * 10) Refactoring – refactoring should be performed on a regular basis.
 * 11) Small Releases – functional releases should be built iteratively that form the project. These visible modules encourage customers, also used for evaluation purposes.
 * 12) Sustainable Pace – also known as a 40 hour week. Well being of the team is important, burnt out programmers do not perform at their best. Productivity is achieved by these means.

Scrum
See also full article on Scrum

Basic concept of Scrum
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. It uses iterative and incremental practices on the software product. It is raised in 1995 by Advanced Development Methodologies,Inc, and has become popular after the Agile Alliance is created since 2001.

The hypothesis of Scrum is, at the beginning of the product development, we could not definite the product’s final requirements. During the development duration, we need creation, develop, and get experience from mistakes, so there is no fixed procedure we can warrant the success. It seems like the Rugby football team, they have highest priority goal, familiar with the development process, have high self-control authority, and cooperate tightly, to ensure the develop team is going ahead to achieve their goals on every phase, every day.

One iteration lasts 30 days, it starts from the beginning of the new product’s requirements. The develop team must implement all functional parts which they select from the beginning. They have daily meeting, spend 15 minutes, to check the progress of every team number, to know what difficulties they met and try to resolve them as soon as possible.

Scrum’s advantage/ disadvantage
The most advantage of Scrum would be its changeability. Scrum can take action when something changes, e.g. requirement change from marketing.

Because of the changeable requirements using Scrum development process, it makes a great challenge to feature testing team especially when they are under developing test case. Because of unfixed and often changed requirements in every unit Sprint, testers often need to re-work on develop test case in a short time.

Scrum’s framework
 Glossary of Scrum terms

(Material in this section is based on information available at Scrum Alliance)

Backlog: Backlog is the requirements for a system, expressed as a prioritized list of product backlog Items. These included both functional and non-functional customer requirements, as well as technical team-generated requirements.

Sprint: An iteration of work during which an increment of product functionality is implemented.

Sprint backlog: Defines the work for a sprint, represented by the set of tasks that must be completed to realize the sprint's goals, and selected set of product backlog items.

ScrumMaster: The ScrumMaster is a facilitator for the team and product owner.

Time-box: The duration time of daily meeting.

Sprint planning meeting: The Sprint planning meeting is a negotiation between the team and the product owner about what the team will do during the next sprint.

Daily Scrum meeting: A fifteen-minute daily meeting for each team member to answer three questions:

 * 1) "What have I done since the last Scrum meeting?"
 * 2) "What will I do before the next Scrum meeting?"
 * 3) "What prevents me from performing my work as efficiently as possible?"

The ScrumMaster ensures that participants call sidebar meetings for any discussions that go too far outside these constraints. The Scrum literature recommends that this meeting take place first thing in the morning, as soon as all team members arrive.

Sprint review meeting: The team shows their achievement to their product owner during this sprint. It lasts 4 hours.

Sprint retrospective meeting: The sprint retrospective meeting is held at the end of every sprint after the sprint review meeting. It lasts 3 hours.

Introduction of Scrum process

 * 1) Divide product backlog into Sprint backlogs, ensure Sprint backlogs can be fulfilled based on the current resource.
 * 2) Hold a Sprint planning meeting, to make sure the works should be finished in this Sprint. Assign work to every team number with priority.
 * 3) Start the Sprint development lifecycle, hold the daily Scrum meeting.
 * 4) After the whole Sprint lifecycle ends, show their achievement to their product owner in the Sprint review meeting.
 * 5) Hold the Sprint retrospective meeting at last, the team and ScrumMaster meet to discuss what went well and what to improve in the next sprint.
 * 6) The next Sprint starts.

Related Material
Ken Schwaber provides an informative and entertaining overview of SCRUM in this Google Tech Talk

Choosing an Agile Methodology
The methodology chosen needs to be on a level that the company is willing to work with. Different levels have different requirements such as:

 * Planning
 * Design
 * Programming practices

Extreme Programming (XP) is far more detailed than the other methodologies and defines programming practices, whereas the other methodologies are mainly involved with the project management and planning issues

The agile methodologies have different degrees of support for the different parts of the software development project's life-cycle.

The methodology to choose depends on:

 * The project size
 * The effort involved
 * Is the project mission or life critical
 * What is the company culture like
 * What build environments are in place(build everything before test allowed, etc)
 * How many senior developers in the team
 * What size is the development team
 * Are requirements going to change often (e.g. Nuclear Power Plant vs Company Website)
 * Order vs Chaos

All the above will determine firstly whether or not to take work with an Agile Methodology and secondly, which agile methodology to choose.

Tool Support for Agile Methodologies
While only a few tools are exclusively applicable to Agile, many tools have been developed to meet the needs of Agile teams and have gone on to find wider audiences. Many of the tools listed here are either specific to Java, or were developed for and with Java but now support other languages. This is mainly due to the popularity of Java during the time that Agile methods were widely adapted. Many tools exist for other languages also.

Scheduling and project management

 * OnTime Axosoft's OnTime is an award winning project management tool for software developers developing in the Agile Scrum methodology.
 * XPlanner - XPlanner is a web-based project management tool for XP projects. XPlanner is probably the most widely used open source project management tool and can be used on other Agile projects, not just XP.
 * AgileTrack - A commercial project management tool for Agile projects
 * TargetProcess TargetProcess is a commercial project management tool for agile projects

Version Control Systems
Version control is a central configuration management activity in any Agile project. Code is written frequently and checked in every day at least. A reliable version control system is central to any agile project. There are dozens of version controls systems to choose from, only the most widely used are listed below, but even that doesn't approach a complete list
 * cvs - A client server system, until recently the dominant VCS system in use. Still very popular.
 * subversion - Seen as a successor to CVS and addresses many of the shortcomings of CVS
 * mercurial - A nascent distributed version control system
 * clearcase - A commercial client server source control system owned by IBM. See here for details of how it can be used in Agile projects.
 * perforce - A popular commercial VCS, used by Google amongst others.
 * Visual SourceSafe A widely used version control system from Microsoft

Build and Continuous Integration

 * CruiseControl - CruiseControl is an open source continuous build and integration tool.
 * buildbot - Another open source automated build and test tool

Testing
Unit Testing

Unit Testing is one of the principles of XP and other Agile methodologies and a whole ecosystem of unit testing frameworks has sprung up around Unit tests test code functionality at the smallest possible level of granularity. In object oriented programming this is usually at the level of a single method. There are simply too many unit testing frameworks to list here however the most widely known is probably JUnit.

 Mock Objects  Mock Objects and unit testing are intrinsically linked. Mock object allow you to create simulations of dynamic complex objects so that dependent code can be reliably tested without having to manage the complex objects state and complexity. There are many mock objects libraries for each language, the list below is a brief selection of what's available:
 * pMock for Python
 * EasyMock for Java
 * NMockLib for C#
 * RSpec for Ruby

Tips and Alternatives
The agile technique works well in collocation environments, for relatively small developer teams (four to ten people). Unlike the Waterfall model, which is more oriented at e.g. software contractors performing projects from conception to maintenance; Agile development uses iterations, which churns out new features and provides maintenance in a continuous cycle, with no set final plan and little documentation. This is not an approach suited for "reliable" software, such as security-critical projects.

Meeting weekly with the customers or other stakeholders will positively impact the success of Agile development. Collaboration is very important. Agile principles propose face-to-face meetings; this is easiest accomplished when team members are collocated in the same premises. There may be significant setbacks if all members work from remote, separate locations, which depends on the type of software, team dynamics, or other factors.

Part of Extreme Programming practice is to refactor regularly. Recoding existing code or changing the structure of the system, even discarding and writing brand new code. This is suitable for rapid prototyping, but may not be the most responsible usage of resources. Excess resource usage is preventable if the architecture of the system is planned from the very beginning.

Agile development works well with experienced developers who are comfortable in their position and skills.

Current Status and Future Directions
‘Agile’ development is a very dynamic and elastic technique that could be applied in a variety of ways to different kinds of projects. Radically evolving technology creates a need for flexible ways of dealing with a new set of environments and rules. There is much scepticism in ‘Agile’ development, however the technique works well for many and they don’t want to discard it or apply heavy-weight development style instead. The set of ‘Agile’ tools and processes provided may be improved. Saying that current ‘Agile’ method is not final and it will be most definitely enhanced.

title: Agile software development


text:
User:MScCompTralee0708

Masters in Computing (Software Development) A.Y. 2007/2008 Tralee, Co. Kerry. Ireland.

title: User:MScCompTralee0708


text:
Talk:Software process management

We should add in a breadcrumb trail for easier navigation.

title: Talk:Software process management


text:
Ivan Illich

Ivan Illich (pronounced [ɪˈvɑn ˈɪlɪtʃ][1]) (Vienna, September 4, 1926 - Bremen, December 2, 2002) was an Austrian philosopher and anarchist social critic. He authored a series of critiques of the institutions of contemporary western culture and their effects of the provenance and practice of education, medicine, work, energy use, and economic development.

Reading groups

 * Deschooling Society.

title: Ivan Illich


text:
Carbon capture and storage

Part of the Wikiversity Ecological Engineering Department, Environmental Engineering Department, School of Engineering and the Engineering and Technology Portal

Goals
To further knowledge of carbon dioxide capture and storage technologies from an engineering perspective and to enable the practitioner to effectively design within the parameters of such.

Recent Research

 * Carbon Sponges
 * Zeolitic imidazolate frameworks
 * Biosynthetic Carbon Uptake
 * Alkaline Earth Absorbtion
 * Nanotube CO2 --> CHx Electrocatalysis
 * Algae Biomass

Wikiversity Research

 * Oilgae

Other Resources

 * Wikipedia article:Climate change
 * Wikipedia article:Carbon dioxide
 * Wikipedia article:Carbon dioxide sink
 * Wikipedia article:Carbon capture and storage
 * Wikipedia article:CO2 sequestration
 * openCCS - wiki-style CCS knowledge base. Mature articles viewable by all, registration required to edit or to view "Draft", "Developing" or "Under review" articles.

title: Carbon capture and storage


text:
Category:Ivan Illich

Pages related to the study of Ivan Illich.

title: Category:Ivan Illich


text:
Template:User sv

de:Vorlage:User sv fr:Modèle:Utilisateur sv it:Template:Utente sv sv:Mall:Användare sv

title: Template:User sv


text:
Energy Conversion Physics

This page will cover the basic physics of energy conversion covering a fairly wide scale of phenomena and devices.

Electric Generation
=Electric Motor

Photoelectrical Effect
The photoelectric effect was actually discovered by Einstein and it is for which he won the Nobel Prize in physics in 1921.

Piezoelectric Effect
In the piezoelectric effect when stress is applied to a material it results in a build up of charge. The effect is reversible. This is the basis for the functioning of microphones as they convert the pressure waves of sound waves into pulse of charge which are detected by a receiver and amplified.

Thermoelectric Effect
The thermoelectric effect also known as the Seebeck or Peltier effect is the phonemena whereby when two different types of metals are joined together and one end is held at a higher temperature and the other at a lower, will result in a voltage differential and when linked up in a circuit will produce some current flow.

Oxidation or Burning
This covers all the known fuels such as oils and gases.

title: Energy Conversion Physics


text:
Mathematical Methods for Engineers II

Main Topics of Mathematical Methods of Engineers I

 * Applied Linear Algebra
 * Discrete equations
 * Matrices
 * Ordinary and Partial Differential Equations and Boundary Values
 * Fourier

Main Topics of Mathematical Methods of Engineers II

 * Differential equations with initial values
 * Heat Equation
 * Nonlinear Equations
 * Large Linear Systems
 * How to solve
 * Direct methods
 * Renumbering nodes
 * Elimination methods
 * Iterative methods
 * Modern computing
 * Optimization and Minimization
 * Linear program

Lectures
Lecture 1: Difference Methods for Ordinary Differential Equations

title: Mathematical Methods for Engineers II


text:
User:Retard robbie

Learning to score films

title: User:Retard robbie


text:
Mathematical Methods for Engineers II/Lecture 1

Ordinary Differential Equations
Given initial values
 * $$u(t=0)$$

What is the equation associated with evolution?
 * There can be a large number of equations

Linear equation:
 * $$u' = au\;$$

 * $$a\;$$ - scalar
 * $$a=\frac{\partial f}{\partial u}$$

N x N matrix
 * $$u' = Au$$
 * Know all the constants
 * Symmetric matrices associated with real eigenvalues
 * Negative eigenvalues mean the solution decays

The constant $$a$$ can be complex
 * Convection term may not be symmetric

Non-stiff Ordinary Differential Equations

 * $$u' = 4u$$
 * Equations relatively easy to solve
 * Use explicit methods
 * Compute $$u_{n+1}$$ directly from $$u_n$$ and $$f(u_n, t_n)$$
 * Calculate from formula
 * Fast methods of calculation
 * Types of methods
 * Euler
 * Minimum accuracy
 * First order
 * Families of methods
 * Adams-Bashforth
 * Multi-step method
 * Runga-Kutta
 * Half-steps to calculate $$u_{n+1}$$
 * ODE45 in Matlab
 * Fourth order Runga-Kutta
 * Varies $$\delta t$$ based on behavior
 * The code uses internal checks to estimate the error
 * Relative accuracy of $$10^{-3}$$
 * Absolute accuracy of $$10^{-6}$$

Stiff

 * $$u(t) = e^{-t} + e^{-99t}$$
 * $$e^{-t}$$ control $$u$$ but $$e^{-99t}$$ control $$\delta t$$
 * Stiff problems arise in process where there is a dynamic range in rates
 * Ill-conditioned
 * Implicit methods
 * Formula involves the previous value and slope
 * The equation can be non-linear
 * Methods are not as fast
 * Types of methods
 * Backward Euler
 * Families of Methods
 * Adams Moulton
 * Backward differences
 * ODE15s in Matlab
 * Varies $$\delta t$$

Trade-off of speed versus stability

Euler's method

 * Construction of method:

$$\frac{u_{n+1} - u_n}{\Delta t} = f(u_n, t_n) = a u_n$$

$$u_{n+1} = (1 + a \Delta t) u_n\;$$

$$u_n = (1 + a \Delta t)^n u_o\;$$

 * Test of stability

$$|1 + a \Delta t| \le 1$$

Limit when $$a \Delta t = 2\;$$

Too big a time step results in an estimated value with too great a difference

Backward Euler method

 * Construction of method:

$$\frac{u_{n+1} - u_n}{\Delta t} = f(u_n, t_{n+1}) = a u_{n+1}$$

$$(1 - a \Delta t) u_{n+1} = u_n\;$$

$$u_n = \left ( \frac{ 1}{1-a \Delta t} \right )^n u_o$$

 * Test of stability

Absolutely stable

Growth factor is always less than one


text: File:Robert Hall fear.ogg

title: File:Robert Hall fear.ogg


text: File:Robert Hall sad.ogg

title: File:Robert Hall sad.ogg


text: File:Robert Hall surprise.ogg

title: File:Robert Hall surprise.ogg


text: File:Robert Hall tired.ogg

title: File:Robert Hall tired.ogg


text: File:Robert Hall joy.ogg

title: File:Robert Hall joy.ogg


text:
File:Jbaggette Wikifilm project.pdf

Used with the WikiU Film School Lesson on how to format a movie script

title: File:Jbaggette Wikifilm project.pdf


text:
Portal talk:Orthopedics

Procedure developed at Yale creates new bone --Remi 05:56, 15 February 2008 (UTC)

title: Portal talk:Orthopedics


text:
Management

Management (or managing) is the administration of an organization, whether it is a business, a not-for-profit organization, or government body.

Management includes the activities of setting the strategy of an organization and coordinating the efforts of its employees (or of volunteers) to accomplish its objectives through the application of available resources, such as financial, natural, technological, and human resources. The term "management" may also refer to those people who manage an organization - managers.

Resources

 * /Brainstorming/

title: Management


text:
User talk:Retard robbie

Welcome
Hello Retard robbie, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. To get started, you may
 * Take a guided tour and learn to edit;
 * Explore our learning projects;
 * Browse our portals, schools, and research activities;
 * Read and help develop our community policies；or
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! Erkan Yilmaz ( Wikiversity:Chat, wiki blog ) 07:27, 15 February 2008 (UTC)

title: User talk:Retard robbie