text:
User:Eas4200c.f08.aero.lee/HW4

= The Multicell Airfoil = First we will look at a specific example of how to analyze a multicell airfoil; the generalization will be provided later. Below is a schematic of a simple approximation of a two-celled airfoil.

For this example, $$t_1 = 0.3$$ cm, $$t_2 = 0.5$$ cm, $$t_{12} = 0.4$$ cm, $$a = 30$$ cm, $$b = 60$$ cm, and $$c = 40$$ cm.

To solve for the total effect of torsion on such an airfoil, contributions from each cell must be taken into account. Each cell will undergo its own shear flow and torque, and the overall torque can be equated as the sum of the torque in each cell.

 * $$T = T_1 + T_2 \qquad \qquad (1)$$

where $$T_1$$ and $$T_2$$ are the torque in cells 1 and 2, respectively. Using the equation $$T = 2q\bar A$$, where $$q$$ is shear flow and $$\bar A$$ are shear flow and average area. Applying this and equation 1 above becomes:

 * $$T = 2q_1\bar {A_1}+2q_2\bar {A_2}$$

where

 * $$\bar {A_1} = ac$$
 * and
 * $$\bar {A_2} = bc$$

It should be noted that both cells have the same rate of twists, $$\theta_1$$ and $$\theta_2$$, respectively.

 * $$\theta_1 = \theta_2 \qquad \qquad (2)$$

Also, an expression for $$\theta$$ has been previously derived and for each cell it is as follows

 * $$\theta_1 = \frac {1}{2G\bar {A_1}}\oint \frac {q_1}{t_1(s)}\, ds$$

 * and

 * $$\theta_2 = \frac {1}{2G\bar {A_2}}\oint \frac {q_2}{t_2(s)}\, ds$$

For this simplified model these equations become:

 * $$ \theta_1 = \frac{1}{2G\bar{A_1}}\oint_{}^{}{\frac{q_1}{t_1}ds} = \frac{1}{2G\bar{A_1}}\left(2\frac{q_1}{t_1}a + \frac{q_1}{t_1}c + (q_1 - q_2)\frac{c}{t_{12}} \right) $$

 * $$ \theta_2 = \frac{1}{2G\bar{A_2}}\oint_{}^{}{\frac{q_2}{t_2}ds} = \frac{1}{2G\bar{A_2}}\left(2\frac{q_2}{t_2}b+ \frac{q_2}{t_2}c + (q_2 - q_1)\frac{c}{t_{12}} \right) $$

= Different Methods for Determining Ā =

Two methods that were discussed in class was approximating area by using the triangular quadrature method shown in figure 2, and the trapezoidal approximation shown in figure 3. It has been deemed that using the triangular quadrature method is more elegant.

= Ad Hoc Engineering Method =

The equation $$ \theta = \frac{1}{2G\bar{A}}\oint_{}^{}{\frac{q}{t}ds} $$ can be developed in an ad hoc manner. Consider a uniform bar of non-circular cross-section subject to twist.

The displacement of point P to P' can be given as $$ \frac{PP'}{OP} = tan(\alpha) \approx \alpha $$ using a small angle approximation. Projecting the displacement onto a path perpendicular to OP' provides $$ PP'' = PP'cos(\alpha) $$. It is also seen that $$ OPcos\alpha = OP'' $$ via a project of OP across angle $$ \alpha $$ Thus,

 * $$ PP = (OPtan\alpha)cos\alpha = (OPcos\alpha)tan\alpha = (OP)tan\alpha $$

Recall from a previous lecture that $$ OP = r $$ and $$ OP'' = \rho $$. Then, the displacement of P in the direction perpendicular to the surface of the bar, using a small angle approximation, is given as

 * $$ PP'' = (rcos\alpha)tan\alpha = \rho tan\alpha \approx \rho \alpha $$

Also recall the definition of the rate of twist, $$ \theta $$, along a section of length dx is defined as $$ \theta = \frac{\alpha}{dx} $$. Examining the shear strain that results along an incremental section of the bar, substituting the above equations, it is seen that

 * $$ \gamma = \frac{PP''}{dx} = \frac{\rho \alpha}{dx} = \rho \left(\frac{\alpha}{dx}\right) = \rho \theta $$

Remembering that stress is calculated in the curvilinear coordinate system

 * $$\tau=G\,\gamma=G\rho\,\theta$$

 * $$\tau(s)=G\rho(s)\,\theta(x)$$

We can Integrate along the contour to arrive at our targeted equation

 * $$\oint{\tau(s)ds}=\oint{G\rho(s)\,\theta(x)ds}=G\,\theta(x)\oint{\rho(s)ds}$$

 * $$\oint{\frac{q(s)}{t(s)}ds}=G\,\theta(x)\,2\,\bar{A}$$

 * $$\theta = \frac{1}{2G\bar{A}}\oint_{}^{}{\frac{q}{t}ds}$$

= Normal Strains as Defined by the Theory of Elasticity =

The Theory of Elasticity gives us the equations of displacement within a bar subjected to a twist rate, $$ \theta $$, as:

 * $$ u_x = \theta\psi (y,z) $$

 * $$ u_y = -\theta xz $$

 * $$ u_z = \theta xy $$

where $$ \psi (y,z) $$ is a function of only y and z.

= Shear Strains as Defined by the Theory of Elasticity =

From above, remember that the Theory of Elasticity gives us the following kinematic assumptions:

 * $$ u_x = \theta\psi (y,z) $$

 * $$ u_y = -\theta xz $$

 * $$ u_z = \theta xy $$

Looking at the following figure, Figure 5:

Looking at the equations they vary slightly from those used in "Aircraft Structures" by C.T. Sun primarily due to the fact that different coordinate systems are used. Looking at the figure, the simple transformation in notation can be made between each of the axes that are shown.

Using the Kinematic Assumptions and that the relationship between normal strains and shear strains the following results are obtained:

 * $$\displaystyle \epsilon_{xx} = \displaystyle \epsilon_{yy} = \displaystyle \epsilon_{zz} = \displaystyle \gamma_{yz} = 0$$

=Looking at Strain Compenents in 3D=

When looking at the strain coefficients in 3D, we know that there are 9 coefficients, arranged in a 3X3 matrix, given by the matrix :

$$\mathbf{\displaystyle \epsilon} =  \begin{bmatrix}

\epsilon_{xx} & \epsilon_{xy} & \epsilon_{xz} \\ \epsilon_{yx} & \epsilon_{yy} & \epsilon_{yz} \\ \epsilon_{zx} & \epsilon_{zy} & \epsilon_{zz} \end{bmatrix} $$

Using this matrix, we now need to convert this matrix into indicial notation. Indicial Notation is used here and allows us to substitute the following values:

 * $$ x \Leftrightarrow 1, y \Leftrightarrow 2 , z \Leftrightarrow 3 $$

Using indicial notation, the previous matrix, $$\mathbf{\displaystyle \epsilon}$$ can be rewritten as:

 * $$\mathbf{\displaystyle \epsilon} = \begin{bmatrix}

\epsilon_{11} & \epsilon_{12} & \epsilon_{13} \\ \epsilon_{21} & \epsilon_{22} & \epsilon_{23} \\ \epsilon_{31} & \epsilon_{32} & \epsilon_{33} \end{bmatrix}$$

This matrix may also be rewritten once again by using the Tensor Calculus Theory of Relativity, and be written in Tensorial Notation. Using this notation, the matrix is rewritten as follows:

 * $$\mathbf{\displaystyle \epsilon} = \begin{bmatrix}

\epsilon_{ij}\end{bmatrix}$$ $$$$

where, ij range from 1 to 3 and the following hold true:

 * i represents the row index
 * j represents the column index

Using the calculated matrix of $$\displaystyle \epsilon_{[ij]}$$ is formed in tensorial notation, the symmetry of the strain tensor can be given as follows:

 * $$\displaystyle \epsilon_{ij} = \frac{1}{2} (\frac{\partial u_i}{\partial x_j} + \frac{\partial u_j}{\partial x_i})$$

By using this symmetrical formula, there are many advantages that include the need to only remember one formula and not have to constantly keep track of the x, y, and z variables.

Taking the coordinates of x,y,z to be $$ x_1, x_2 ,  x_3 $$ respectively the symmetrical strain tensor can now be rewritten making the following substitutions: $$ x \Leftrightarrow x_1 , y \Leftrightarrow x_2 , z \Leftrightarrow x_3 $$

and written as:

 * $$\epsilon_{11} = \displaystyle \epsilon_{xx} = \frac{1}{2} (\frac{\partial u_1}{\partial x_1} + \frac{\partial u_1}{\partial x_1})=  \frac{\partial u_1}{\partial x_1} \Rightarrow \frac{\partial u_x}{\partial x}$$

=Stress Component in 3D= Similarly from the proof of $$\displaystyle \epsilon$$ we know that for the stress tensor $$\displaystyle \sigma$$ there will only be 6 independent solutions to solve for the 9 coefficients of the matrix. This 3x3 tensor $$\displaystyle \sigma$$ can be described much like the other tensor $$\displaystyle \epsilon$$ was.

 * $$\mathbf{\displaystyle \sigma} = \begin{bmatrix}

\sigma_{ij}\end{bmatrix}$$ $$$$

where similarly, here, ij range from 1 to 3 and the following conditions hold true:

 * i represents the row index
 * j represents the column index

 Q:  Does the symmetry of $$\displaystyle \epsilon$$ related to the isotropy of the material?

Referring to the following equation (1) from the notes dealing with the shear strains defined by the theory of elasticity, we obtain the following equation:

$$\displaystyle \epsilon _{xx}=\epsilon _{yy}=\epsilon _{zz}=\gamma _{yz}=0$$

Due to $$\displaystyle \epsilon$$ - $$\displaystyle \sigma$$ relationship this equation can also be rewritten as following:

$$\displaystyle \sigma _{xx}=\sigma _{yy}=\sigma _{zz}=\tau _{yz}=0$$

=Relation of Strain to Elastic Modulus and Poisson's Ratio= We wish to relate normal strain, εxx, to elastic modulus, E, and Poisson's Ratio, ν. Poisson's ratio, named after Simeon Denis Poisson, is defined as:
 * $$\nu =-\frac{lateral strain}{axial strain} =-\frac{\epsilon_{y}}{\epsilon_{x}}=-\frac{\epsilon_{z}}{\epsilon_{x}}$$

(for an axial load in the x direction, for example.)

When taking a simple rigid object and compressing it in one direction of the material will tend to deform in the opposite direction, a direction that is perpendicular to the force. As shown in the illustration above in Figure 7, the compression in the x direction causes the rigid structure to deform (positively) in the y direction.

Some common values for Poisson's Ratio are given as:

For Rubber,$$\nu_{rubber} = 0.5 $$

For steel,$$\nu_{steel} = 0.3 $$

For a simple cork,$$\nu_{cork} = 0 $$

Using Hooke's Law:
 * $$\epsilon _{xx}=\frac{\sigma _{xx}}{E}-\nu \frac{\sigma _{yy}}{E}-\nu \frac{\sigma _{zz}}{E}$$

We now wish to find $$\epsilon _{yy}$$ and $$\epsilon _{zz}$$:
 * $$\epsilon _{yy}=-\nu\frac{\sigma _{xx}}{E}+\frac{\sigma _{yy}}{E}-\nu \frac{\sigma _{zz}}{E}$$
 * $$\epsilon _{zz}=-\nu\frac{\sigma _{xx}}{E}-\nu\frac{\sigma _{yy}}{E}+ \frac{\sigma _{zz}}{E}$$

For shear strain:
 * $$\gamma _{xy}=2\epsilon _{xy}=\frac{\tau _{xy}}{G}$$

We also wish to find $$\gamma _{yz}$$ and $$\gamma _{zx}$$. In the same manner,

 * $$\gamma _{yz}=2\epsilon _{yz}=\frac{\tau _{yz}}{G}$$

and

 * $$\gamma _{zx}=2\epsilon _{zx}=\frac{\tau _{zx}}{G}$$

=Hooke's Law for Isotropic Elasticity= Hooke's Law for Isotropic Elasticity can be defined in matrix form as:

\begin{Bmatrix} \epsilon _{xx}\\ \epsilon _{yy}\\ \epsilon _{zz}\\ \gamma _{yz}\\ \gamma _{zx}\\ \gamma _{xy}\\ \end{Bmatrix}=

\begin{bmatrix} \frac{1}{E}& \frac{-\nu }{E} & \frac{-\nu }{E} & 0 & 0 &0 \\ \frac{-\nu }{E}& \frac{1}{E} & \frac{-\nu }{E} & 0 &  0&0 \\ \frac{-\nu }{E}& \frac{-\nu }{E} &   \frac{1}{E}& 0 & 0 &0 \\ 0 & 0 & 0 & \frac{1}{G} & 0 & 0\\ 0 & 0 & 0 & 0 & \frac{1}{G}& 0\\ 0& 0 &0 &0 & 0 & \frac{1}{G} \end{bmatrix} \begin{Bmatrix} \sigma _{xx}\\ \sigma _{yy}\\ \sigma _{zz}\\ \sigma _{yz}\\ \sigma _{zx}\\ \sigma _{xy}\\ \end{Bmatrix} $$ and since, for example,
 * $$\gamma _{xy}=2\epsilon _{xy}=\frac{\sigma _{xy}}{G}

$$ then
 * $$\epsilon _{xy}=\frac{\sigma _{xy}}{2G}$$

the matrix becomes:
 * $$\begin{Bmatrix}

\epsilon _{xx}\\ \epsilon _{yy}\\ \epsilon _{zz}\\ \epsilon _{yz}\\ \epsilon _{zx}\\ \epsilon _{xy} \end{Bmatrix} = \begin{vmatrix} \frac{1}{E}& \frac{-\nu }{E} & \frac{-\nu }{E} & 0 & 0 &0 \\ \frac{-\nu }{E}& \frac{1}{E} & \frac{-\nu }{E} & 0 &  0&0 \\ \frac{-\nu }{E}& \frac{-\nu }{E} &   \frac{1}{E}& 0 & 0 &0 \\ 0& 0 & 0 & \frac{1}{2G} & 0 & 0\\ 0&0 & 0 & 0 & \frac{1}{2G} &0 \\ 0& 0 & 0 & 0 & 0 & \frac{1}{2G} \end{vmatrix}

\begin{Bmatrix} \sigma _{xx}\\ \sigma _{yy}\\ \sigma _{zz}\\ \sigma _{yz}\\ \sigma _{zx}\\ \sigma _{xy} \end{Bmatrix}$$

= A note on Poisson's ratio = For most materials, Poisson's ratio is positive, and is between 0 and 0.5. For example, steel has a ratio of 0.3, meaning an axial load in the x direction will result in some deformation in the y and z directions. It is interesting to note, however, that cork (used in wine bottles) has a ratio of zero. Also, some materials have a negative Poisson’s ratio. When subjected to strain in a longitudinal axis, the transverse strain in the material will actually be positive, and the material would therefore increase in that direction as well.

= Simplified Airfoil Example = A simplified airfoil is given in the figure below. It has a semicircular leading edge of diameter b = 2 m and a triangular trailing edge with one side of length a = 4 m. Thicknesses are $$ t_{1} = 0.008\ m,\ t_{2} = t_{3} = 0.01\ m $$. It is desired to determine the average area $$ \bar{A} $$, maximum torque, and the torsional constant J of the airfoil.

=NACA Airfoil Sample Roadmap= Using the following example we will outline the procedures to begin to setup the matlab project of this homework assignment by breaking up the multicell airfoil into 4 distinct areas, defined as: $$\bar {A_1}, \bar {A_{21}}, \bar {A_{22}},$$ and $$\bar {A_{3}}$$. The breakdown is shown below in Figure 9.

Similarly to what will be done in the HW 4 Matlab assignment, each of the areas will be calculated and added to develop the following sum:

 * $$\bar {A} = \bar {A_1}+\bar {A_{21}}+\bar {A_{22}}+\bar {A_3}$$

Here $$\bar {A_2}$$ represents the area of the 2nd airfoil section that is defined likewise as: $$\bar {A_2} =\bar {A_{21}}+\bar {A_{22}}$$. For simplicity this area section is divided into two sections ($$\bar {A_{21}}$$ and $$\bar {A_{22}}$$), by the dividing bisecting line, from E to F,($$\bar {EF}$$).

In Matlab, the total area will be taken by summing the individual sections. For these sections, the initial point will be set and the area calculated by sweeping areas for specific points from approximate semi circles and triangles. After the sum is taken from all of the components, careful consideration will need to be taken to compare and ensure that the results obtained in this homework 4 Matlab approximation are within 1% of the previous results obtained in the Matlab assignment in homework 3.

First to calculate area $$\bar {A_{1}}$$ we need to set the center point at $${P_{0}=D}$$ and sweep the area of the circle from the following points: $${B}\rightarrow{L}\rightarrow{E}$$

To first calculate the area of the subsection, $$\bar {A_{21}}$$, the center point will be set at $${P_{0}=E}$$ and sweep the area of the sectional triangle from points: $${F}\rightarrow{B}$$

To calculate the area of the second subsection, $$\bar {A_{22}}$$, the center point will be set at $${P_{0}=F}$$ and sweep the area of the sectional triangle from points: $${E}\rightarrow{H}$$

Finally, to calculate the area of $$\bar {A_{3}}$$ the center point will be set at $${P_{0}=G}$$ and sweep the area of the final triangle from the points: $${H}\rightarrow{T}\rightarrow{F}$$

= NACA Airfoil Matlab Code Continued =

This weeks matlab code involved adding functions to determine the torsional constant, J, for both single cell airfoils as well as multi-celled bodies.

= Matlab-code Certification =

I, the undersigned, certify that I can read, understand, and write matlab codes, and can thus contribute effectively to my team.

--Eas4200c.f08.aero.mcgilvray 16:16, 21 October 2008 (UTC)

--Eas4200c.f08.aero.lee 00:21, 21 October 2008 (UTC)

--Eas4200c.f08.aero.kurth 08:59, 21 October 2008 (UTC)

--Eas4200c.fo8.aero.oyama 16:30, 23 October 2008 (UTC)

--Eas4200c.f08.aero.strods 03:38, 24 October 2008 (UTC)

--Eas4200c.f08.aero.barcia 24:28, 24 October 2008 (UTC)

= Contributing team members =

--Eas4200c.f08.aero.mcgilvray 16:16, 21 October 2008 (UTC)

--Eas4200c.f08.aero.lee 00:21, 21 October 2008 (UTC)

--Eas4200c.f08.aero.kurth 08:59, 21 October 2008 (UTC)

--Eas4200c.fo8.aero.oyama 16:30, 23 October 2008 (UTC)

--Eas4200c.f08.aero.strods 03:38, 24 October 2008 (UTC)

--Eas4200c.f08.aero.barcia 14:29, 24 October 2008 (UTC)

title: User:Eas4200c.f08.aero.lee/HW4


text: File:Hw4 diag1.jpg

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

title: File:Hw4 diag1.jpg


text:
User:Eml4500.f08.lulz.abcd/HW4

Prove $$\mathbf{\tilde{f}^{(e)}}=\mathbf{\tilde{T}^{(e)}{f}^{(e)}}$$
$$\mathbf{\tilde{f}^{(e)}}=\mathbf{\tilde{T}^{(e)}{f}^{(e)}}$$

$$\mathbf{\tilde{T}^{(e)}}=\begin{bmatrix} l^{(e)} & -m^{(e)} & 0 & 0\\ m^{(e)} & l^{(e)} & 0 & 0\\ 0 & 0 & l^{(e)} & -m^{(e)}\\ 0 & 0 & m^{(e)} & l^{(e)} \end{bmatrix}$$

Since we know that $$l^{(e)} = cos(\theta)^{(e)}$$, $$m^{(e)} = sin(\theta)^{(e)}$$, and that the angle is 30 degrees, we can substitute values and compare the transformed matrix output to the values previously calculated. Confirmation will prove the relation.

$$\mathbf{\tilde{T}^{(1)}}=\begin{bmatrix} \sqrt{3}/2 & -0.5 & 0 & 0\\ 0.5 & \sqrt{3}/2 & 0 & 0\\ 0 & 0 & \sqrt{3}/2 & -0.5\\ 0 & 0 & 0.5 & \sqrt{3}/2 \end{bmatrix}$$

$$\mathbf{\tilde{T}^{(1)}f^{(1)}}=\begin{bmatrix} \sqrt{3}/2 & -0.5 & 0 & 0\\ 0.5 & \sqrt{3}/2 & 0 & 0\\ 0 & 0 & \sqrt{3}/2 & -0.5\\ 0 & 0 & 0.5 & \sqrt{3}/2 \end{bmatrix}\begin{bmatrix} -4.378\\ -2.5622\\ 4.4378\\ 2.5622 \end{bmatrix}=\mathbf{\tilde{f}^{(1)}}$$

$$\mathbf{\tilde{f}^{(1)}}=\begin{bmatrix} -5.1243\\ 0\\ 5.1243\\ 0 \end{bmatrix}$$

This confirms as expected and thus the proof is confirmed.

Prove that $$ \mathbf k^{(e)} = \tilde \mathbf T^{(e)^{T}}\tilde \mathbf k^{(e)}\tilde \mathbf T^{(e)}$$
$$ \mathbf k^{(e)} = \tilde \mathbf T^{(e)^{T}}\tilde \mathbf k^{(e)}\tilde \mathbf T^{(e)}$$

We already know the values from previous work for $$\mathbf{k^{(e)}}$$, $$\mathbf{\tilde{k}^{(e)}}$$, $$\mathbf{\tilde{T}^{(e)}}$$, and $$\mathbf{\tilde{T}^{(e)^T}}$$ is trivial to find:

$$ \mathbf{\tilde{T}^{(e)^T}} = \begin{bmatrix} l^{(e)} & m^{(e)} & 0 & 0\\ -m^{(e)} & l^{(e)} & 0 & 0\\ 0 & 0 & l^{(e)} & m^{(e)}\\ 0 & 0 & -m^{(e)} & l^{(e)} \end{bmatrix}$$

$$\mathbf k^{(e)} = \tilde \mathbf T^{(e)^{T}}\tilde \mathbf k^{(e)}\tilde \mathbf T^{(e)}$$

$$\mathbf k^{(e)} = k^{(e)}\begin{bmatrix} l^{(e)} & -m^{(e)} & 0 & 0\\ m^{(e)} & l^{(e)} & 0 & 0\\ 0 & 0 & l^{(e)} & -m^{(e)}\\ 0 & 0 & m^{(e)} & l^{(e)} \end{bmatrix}\begin{bmatrix} 1 & 0 & -1 & 0\\ 0 & 0 & 0 & 0\\ -1 & 0 & 1 & 0\\ 0 & 0 & 0 & 0\end{bmatrix}\begin{bmatrix} l^{(e)} & m^{(e)} & 0 & 0\\ -m^{(e)} & l^{(e)} & 0 & 0\\ 0 & 0 & l^{(e)} & m^{(e)}\\ 0 & 0 & -m^{(e)} & l^{(e)}\end{bmatrix} = \begin{bmatrix} (l^{(e)})^{2} & l^{(e)}m^{(e)}  &  -(l^{(e)})^{2}  &  -l^{(e)}m^{(e)}   \\ l^{(e)}m^{(e)} &  (m^{(e)})^{2}  &  -l^{(e)}m^{(e)}  &  -(m^{(e)})^{2}   \\ -(l^{(e)})^{2} & -l^{(e)}m^{(e)}  &  (l^{(e)})^{2}  &  l^{(e)}m^{(e)} \\ -l^{(e)}m^{(e)} &  -(m^{(e)})^{2}  &  l^{(e)}m^{(e)}  &  (m^{(e)})^{2} \\ \end{bmatrix} = \mathbf k^{(e)}$$

title: User:Eml4500.f08.lulz.abcd/HW4


text:
User:Eas4200c.f08.nine.F/Homework 4

[|Homework 1]

[|Homework 2]

[|Homework 3]

[|Homework 4]

Group nine - Homework 4

Ad-Hoc
"Ad hoc is a Latin phrase which means "for this [purpose]". It generally signifies a solution designed for a specific problem or task, non-generalizable, and which cannot be adapted to other purposes."

"Common examples are organizations, committees, and commissions created at the national or international level for a specific task; in other fields the term may refer, for example, to a tailor-made suit, a handcrafted network protocol, or a purpose-specific equation. Ad hoc can also have connotations of a makeshift solution, inadequate planning, or improvised events. Other derivates of the Latin include AdHoc, adhoc and ad-hoc."

Angle of Twist Derivation
Derive $\theta = \frac{1}{2G\bar{A}}\oint^{} \frac{q}{t} ds$|undefined

Consider we have a uniform non circular cross section subject to twist.

Going through the geometry we can see that,

$\frac{P\dot{P}}{OP} = tan\alpha$|undefined

$P\ddot{P} = P\dot{P}cos\alpha$

$\rightarrow = (OPtan\alpha )cos\alpha$ where   $OPcos\alpha = O\ddot{P}$

Now we define the following:

$OP = r$ and  $O\ddot{P} = \rho$

$P\ddot{P} = rcos\alpha tan\alpha = \rho \alpha$

And now we take a look at the strain.

$\gamma = \frac{P\ddot{P}}{ds} = \frac{\rho \alpha}{ds}  =  \rho \theta  =  \rho \frac{\alpha}{dx}$|undefined

Hooke's Law: $\tau = G\gamma = G\rho \theta$

$\rightarrow \tau(s) = G\rho(s) \theta(x)$

and now integrating along the contour C $\rightarrow$

$\oint_{C} \tau(s)ds = G\theta(x) \oint_{C}^{} \rho(s) ds$

where $\tau(s) = \frac{q(s)}{t(s)}$  and  $\oint_{C} \rho(s) ds = 2\bar{A}$

Integrating and rearranging terms yields the final result$rightarrow$

$\theta = \frac{1}{2G\bar{A}}\oint^{} \frac{q}{t} ds$|undefined

Question

What is ad hoc about the derivation of the angle of twist shown above?

Answer

1) The strain must be obtained using the displacement of $P$  in the direction that is tangent to the contour curve at $P\ddot{P}$

2) It was assumed that the shear force was uniform across the wall the thickness.

3) To get line $P\dot{P}$ assume  $\alpha$  is small; to get  $P\ddot{P}$  assume  $ \alpha $  is finite and  $\rho = rcos\alpha$  ; and then reintroduced small  $\alpha$  after that.

_____________________________________________________________________________________________________________________________________________

Hooke's law: (Ricardo Albuquerque)

$\tau = G \gamma$

Normal strains:

$$ \epsilon_{xx} = \frac{\sigma_{xx}}{E} - \frac{\nu \sigma_{yy}}{E} - \frac{\nu \sigma_{zz}}{E} $$

$$ \epsilon_{yy} = -\frac{\nu \sigma_{xx}}{E} + \frac{\sigma_{yy}}{E} - \frac{\nu \sigma_{zz}}{E} $$

$$ \epsilon_{zz} = -\frac{\nu \sigma_{xx}}{E} - \frac{\nu \sigma_{yy}}{E} + \frac{\sigma_{zz}}{E} $$

Shear strains:

$$ \gamma_{xy}= 2 \epsilon_{xy} = \frac{\tau_{xy}}{G} $$

$$ \gamma_{yz}= 2 \epsilon_{yz} = \frac{\tau_{yz}}{G} $$

$$ \gamma_{zx}= 2 \epsilon_{zx} = \frac{\tau_{zx}}{G} $$

Strain tensor:

$$ \epsilon = \begin{bmatrix} \epsilon_{11} & \epsilon_{12} & \epsilon_{13} \\ \epsilon_{21} & \epsilon_{22} & \epsilon_{23} \\ \epsilon_{31} & \epsilon_{32} & \epsilon_{33} \end{bmatrix} $$

Note: It is important to note here that the above yields six independent strain terms because $\epsilon_{ij} = \epsilon_{ji}$.

Hooke's law (isotropic material):

$$ \begin{bmatrix} \epsilon_{11}\\ \epsilon_{22}\\ \epsilon_{33}\\ \epsilon_{23}\\ \epsilon_{31}\\ \epsilon_{12}\\ \end{bmatrix}~= $$                       $$ \begin{bmatrix} \frac{1}{E}&\frac{-\nu}{E}&\frac{-\nu}{E}&0&0&0\\ \frac{-\nu}{E}&\frac{1}{E}&\frac{-\nu}{E}&0&0&0\\ \frac{-\nu}{E}&\frac{-\nu}{E}&\frac{1}{E}&0&0&0\\ 0&0&0&\frac{1}{2G}&0&0\\ 0&0&0&0&\frac{1}{2G}&0\\ 0&0&0&0&0&\frac{1}{2G}\\ \end{bmatrix}~ $$ $$ \begin{bmatrix} \sigma_{11}\\ \sigma_{22}\\ \sigma_{33}\\ \sigma_{23}\\ \sigma_{31}\\ \sigma_{12}\\ \end{bmatrix} $$

or equivaletly:

$$ \begin{bmatrix} \epsilon_{xx}\\ \epsilon_{yy}\\ \epsilon_{zz}\\ \gamma_{yz}\\ \gamma_{zx}\\ \gamma_{xy}\\ \end{bmatrix}~= $$                        $$ \begin{bmatrix} \frac{1}{E}&\frac{-\nu}{E}&\frac{-\nu}{E}&0&0&0\\ \frac{-\nu}{E}&\frac{1}{E}&\frac{-\nu}{E}&0&0&0\\ \frac{-\nu}{E}&\frac{-\nu}{E}&\frac{1}{E}&0&0&0\\ 0&0&0&\frac{1}{G}&0&0\\ 0&0&0&0&\frac{1}{G}&0\\ 0&0&0&0&0&\frac{1}{G}\\ \end{bmatrix} $$ $$ \begin{bmatrix} \sigma_{xx}\\ \sigma_{yy}\\ \sigma_{zz}\\ \tau_{yz}\\ \tau_{zx}\\ \tau_{xy}\\ \end{bmatrix} $$

Question

What material has a Poisson's ration of 0?

Answer

Cork

____________________________________________________________________________________________________________________________________________________

Sample Run of Code
NACA Airfoil calculation program Enter first digit of airfoil: 2 Enter second digit: 4 Enter the third and fourth digits: 15 Enter Py: 0 Enter Pz: 0 Enter number of segments: 60

The average area is: 0.103 The minumum number segments required to have the average area accurate within 1 percent is: 24.000

Figure 1 shows the cross-section of the NACA airfoil and Figure 2 shows the centroid line

Matlab Code Certification
I, the undersigned, certify that I can read, understand, and write matlab codes, and can thus contribute effectively to my team.

Ricardo Albuquerque Eas4200c.f08.nine.r 22:46, 21 October 2008 (UTC)

Felix Izquierdo Eas4200c.f08.nine.F 3:46, 22 October 2008 (UTC)

David Phillips Eas4200C.f08.nine.d (talk) 18:34, 23 October 2008 (UTC)

Oliver Watmough Eas4200c.f08.nine.o 10:07, 23 October 2008 (UTC)

Stephen Featherman Eas4200c.f08.nine.s 11:48, 23 October 2008 (UTC)

Contributing Team Members
The following students contributed to this report:

David Phillips Eas4200C.f08.nine.d (talk) 18:34, 23 October 2008 (UTC)

Oliver Watmough Eas4200c.f08.nine.o 10:07, 23 October 2008 (UTC)

Stephen Featherman Eas4200c.f08.nine.s 11:48, 23 October 2008 (UTC)

Ricardo Albuquerque Eas4200c.f08.nine.r 4:30, 23 October 2008 (UTC)

Felix Izquierdo Eas4200c.f08.nine.F 4:34, 23 October 2008 (UTC)

title: User:Eas4200c.f08.nine.F/Homework 4


text: File:Hw4 diag2.jpg

title: File:Hw4 diag2.jpg


text: File:Hw4 diag3.jpg

title: File:Hw4 diag3.jpg


text: File:NACA 2415 3-Cell Airfoil.jpg

title: File:NACA 2415 3-Cell Airfoil.jpg


text:
File:Hw4-2415airfoil.jpg

Eas4200c.f08.ZYX.O'Mahoney 21:04, 24 October 2008 (UTC)

title: File:Hw4-2415airfoil.jpg


text:
Talk:Wiki Campus Radio/Formerly active audio stream

Wikimania

 * Tango music - assuming 'free' recordings...
 * Streamed feed ?

There is a provisional Schedule here :
 * http://wikimania2009.wikimedia.org/wiki/Schedule

I'd appreciate some assistance as to what can be covered :)

Also it probably a local co-ordinator to do studio switching...

62.56.118.112 13:47, 14 August 2009 (UTC)

Regular Slots

 * On the day
 * Top news items
 * The Signpost
 * Audio Wikinews

(Oct 31st) Halloween playlist
See Halloween Now archived until next year.

Halloween

US elections (2009)
This section needs archiving !

Generic Lead in

 *
 * "This is Wiki Campus Radio"
 * Short music clip appriately patriotic

Obama Win
possibly even read live (Wikinews is CC-BY)
 * n:Wikinews_talk:Story_preparation/Barack_Obama_wins_U.S._Presidency - This might need to be recorded at short notice,

 * Possibly into live coverage? (Can this be arranged at 48 hours notice?)

McCain Win

 * "This is Wiki Campus Radio"
 * n:Wikinews:Story_preparation/John_Mcain_wins_U.S._Presidency
 * Into live coverage...

Around (Nov 11 th - Armistice/Vetrans Day)
 Important Owing to the complexities that have arisen in confirming the status of works in relation to this, it is unlikely that the planned play-list will air this year, development work can however continue.

See Armistice/Veterans Day

See Also: Wikisource:Wikisource:Scriptorium/WCR

Presidential Inauguration (2009)
This needs archiving...

*http://www.archive.org/download/nonfiction005_librivox/emancipationproclamation_lincoln_cs.ogg --> *I%27ll_overcome_some_day --> *Civil_Rights_Message -A Speech given by JFK. --> *User:ShakespeareFan00/Lord Creator From this day

Winter Festivals
See /Winter_Festivals

Burns Night
See /01-25

Spring Festivals
See /Spring Festivals


text: File:NACA Airfoil Basics.jpg

title: File:NACA Airfoil Basics.jpg


text:
MediaWiki:Globalblocking-blocked

Your IP address has been blocked on all wikis by $1 ($2). The reason given was "$3". The block $4.

You can request removal of the block by adding to your talk page. Replace "REASON" with the reason for requesting unblock. Please mention "global block" as part of the reason.

title: MediaWiki:Globalblocking-blocked


text:
Talk:Computer Architecture Lab/WS2008/Group2/ISA comparison

hello, ich möcht hiermit nochmal dafür plädieren die schriftstücke im wiki-format (statt als pdf downloads) zu hinterlegen, da es das "native" format für wikiversity ist, und unsere bisherigen beiträge ja ohnehin layouttechnisch nicht besonders anspruchsvoll sind ;) wenn ich mit der meinung alleine dastehe ordne ich mich aber auch gern unter. jedenfalls wär's nicht schlecht wenn wir die beiträge einigermaßen einheitlich halten (was jetzt auch meine schuld ist dass es nicht so ist), aber da dürften wir ja nach dem treffen heute eh übereinstimmen. Herr bayer 00:44, 25 October 2008 (UTC)


text:
User talk:Domokato~enwikiversity

Welcome
Hello Domokato, 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;
 * [ Ask] a question, discuss Wikiversity, etc. at the Colloquium;
 * Read and help develop our community policies, or
 * Chat with other Wikiversians on #wikiversity.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Emesee 03:27, 25 October 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 Domokato. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Domokato~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:31, 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:06, 19 April 2015 (UTC)

title: User talk:Domokato~enwikiversity


text:
Talk:United States currency/$5 bill

Does anyone believe or ever seen the "172" in the bushes in the Lincoln Memorial on the back of the $5 bill? If so, why is it there? I cannot find the answer anywhere on the Internet.

title: Talk:United States currency/$5 bill


text:
Introduction to coupled dancing/Introduction

With coupled dancing we mean dances where two persons dance together. Usually man and woman. The man has usually the role of the leader, while the woman has the role of the follower. Leaders and followers have different steps. The coupled dance can be either choreographed or free.


text:
User:Azamishaque

Biography
Azam Ishaque born on 5th February 1986 at Islamabad Pakistan

He is a Computer Engineer. He did his Computer Engineering from COMSATS, and currently doing MS leading to PhD in Engineering Management from CASE, Islamabad Pakistan

He is working with wikipedia since 2008 His Profile

He joined wikinews in July 2008 and got awards of such a good writer See His Profile.

He is contributing his work to Wikimedia Commons also.

He is woking as a System Analyst, in a reputable organization.

title: User:Azamishaque


text:
User talk:Azamishaque

 Hello Azamishaque, 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.
 * Visit a (kind of) random random project.
 * Browse everything on Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold to contribute and to experiment with the sandbox or your userpage, and see you around Wikiversity! Jtneill - Talk - c 09:33, 25 October 2008 (UTC)

 Hello , we are the Baah and Bahh twins and we'd both like to welcome you to Wikiversity. While you sit back and explore Wikiversity, enjoy some of our fresh goat milk. You can help us learn by creating new learning resources or help us by improving the guided tours and other exploration tools. We look forward to seeing you around. Baaaahbye for now.

Image Tagging Image:Azami.JPG
Thanks for uploading Image:Azami.JPG. I notice the image page currently doesn't specify who created the content, so the copyright status is unclear. If you have not created this media yourself then you need to argue that we have the right to use the media on Wikimedia Commons (see copyright tagging below). If you have not created the media yourself then you should also specify where you found it, i.e., in most cases link to the website where you got it, and the terms of use for content from that page. If the content is a derivative of a copyrighted work, you need to supply the names and a licence of the original authors as well.

If the media also doesn't have a copyright tag, then you must also add one. If you created/took the picture, audio, or video then you can use to release it under the multilicense GFDL plus Creative Commons Attribution-ShareAlike All-version license or PD-self to release it into the public domain. See commons:Commons:Copyright tags for the full list of copyright tags that you can use.

Note that any unsourced and untagged images will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have uploaded other media, please check that you have specified their source and copyright tagged them, too. You can find all your uploads using the Gallery tool. Thank you. TeleComNasSprVen (discuss • contribs) 06:24, 15 March 2014 (UTC)

title: User talk:Azamishaque


text: Friendship

title: Friendship


text:
Draft talk:Solids

Aren't molecules moving slightly even at 0 degrees kelvin? If they would not move at all one could measure the position and momentum and thus violate Heisenbergs Uncertainty principle. I remember seing a professor on youtube lecturing about this specific dilemma. --Ofey 15:00, 25 October 2008 (UTC)

title: Draft talk:Solids


text:
Consensus in a wiki environment/Establishing consensus

What happens on a wiki if 45 percent of people feel one way and 55 percent of people feel another way about some change or implementation on a wiki? What happens if there are only two or three people working on a project or an area of the wiki and those two or three people all disagree? Will the two "out vote" the one? Consensus is not a vote though, is it?

So communication must be key in establishing consensus.

Theoretically, once consensus is established, all stakeholders will agree, that the course of action to be taken is the right course of action to be taken. Everyone should be happy... in theory.

How are past users opinions taken into account? If inactive wiki contributors are not available to voice their opinion, or lack of one, should their investment in the direction of the wiki not be taken into account in deciding and agreeing what exactly is the consensus?

What happens if there are 1000 users, and 999 of those users feel one way, and the other one user feels a different way? Is that consensus? It seems like it might be a consensus among the 999 users, but is it truly then a consensus among all the participants within the wiki?

What about the location of consensus? If a few people create a consensus somewhere else about another project, does that consensus override local consensus?


text:
Topic talk:Wikiendeavor

What is the intention of this topic? Emesee 17:55, 25 October 2008 (UTC)

title: Topic talk:Wikiendeavor


text:
Plan-driven software development

Overview of Plan-driven software development
''Plan-driven software development is a more formal specific approach to creating an application. Plan-driven methodologies all incorporate: repeatability and predictability, a defined incremental process, extensive documentation, up-front system architecture, detailed plans, process monitoring, controlling and education, risk management, verification and validation.''

Plans are typically generated by the following: [Source: Coleman, Gerry. Software Process Management, Dundalk IT / IT Tralee(2008)]
 * Project broken down into stages/tasks
 * Each task broken into its composite activities
 * Each individual task estimated (perhaps using metrics)
 * Estimates aggregated to give total effort
 * Task list analysed for concurrencies and dependencies to provide schedule
 * Schedule and delivery date help provide team size and team composition
 * Team assembled and project commences
 * Monitoring and control throughout development
 * Delivery!

Overview of Plan-driven methodologies
The Plan-driven methodologies are known as "Heavy-weight" methodologies or "Traditional" methodologies.

Three of the most prominent plan-driven methodologies are the Personal Software Process (PSP), Team Software Process (TSP), and Rational Unified Process (RUP).

[Source: OpenSeminar]

''A software development process is the process by which user needs are translated into a software product. The process involves translating user needs into software requirements, transforming the software requirements into design, implementing the design in code, testing the code, and sometimes installing and checking out the software for operational use. Note: these activities might overlap or be performed iteratively.''

[Source: IEEE, 1990]

Personal Software Process (PSP), Team Software Process (TSP), and Rational Unified Process (RUP), all of which use the incremental model, are described below.

Incremental model
With the Incremental Model, the system is analysed, designed, developed, and tested in increments which are clearly defined. In other words the project is broken down into a series of builds. The core functionality is dealt with in the first increment and with the final increment the complete project is released. It emphasises a building block approach which means that an operational system is produced more quickly.

Complete requirements may be gathered up front or the project may begin with general objectives which are refined with each iteration. The requirements are prioritised, the higher a requirements 's priority the earlier it is to be included in an increment. Thus, new functionality added should not be more important than that which exists in the current build

The process can be illustrated as in figure 1.

..

Iteration

Each iteration can be seen as a mini project with its own lifecycle (this could be waterfall, for example). The end product of each iteration is an executable system which is integrated and tested. An iteration usually lasts for a predefined, relatively short period of time (generally a number of weeks.

Advantages Rapid return on investment
 * Operational portion ready early in project.
 * Allows for gradual introduction of new product to client.
 * Early and regular feedback from clients.
 * Early discovery of high risks
 * Accommodates changes

Disadvantages
 * Each new build has to be incorporated into the existing build without breaking it.
 * Clients have more opportunity to attempt to change requirements than with, for example, the waterfall method.
 * Has the potential to degenerate into a build and fix model.

Waterfall model
Successful software project rate has increased considerably since 70’s. This is explainable by standard and accepted methods of process management in companies. Lifecycle model development began in 70’s with suggested waterfall lifecycle model as a pioneer in software development. This model was proposed by Winston W. Royce and was successfully employed in the industry during these years.

Waterfall model has a linear structure characteristic. This linear structure defines the sequentially of tasks where task should be completed before the next task can be started, thus following non-iterative principle. Plan driven development mirrors the approach by waterfall model where steps in the development are planned out from the beginning until the project completion. Waterfall lifecycle model development is broken down into five steps:

 * Requirement analysis: development team meets project stakeholders to identify needs and establish requirements to satisfy project goals. Requirement analysis initially is a feasibility study that identifies functional and non-functional requirements with its constraints. Documentation is generated.

 * Design: development team converts requirements into representation of architectural model. Prototypes are created with functional algorithms and data structures. Creating accurate design in this stage is vital because after completing design stage, development team doesn’t go back to the design previous stage. Design is finalised and overall of the project outcome depends on it.

 * Coding and implementation: design is transformed into software.

 * Testing: software domain is tested for bugs. Different sets of tools are available for testers and developers to detect and fix defects in the software.

 * Maintenance: stage where product is updated (patched), to meet changing needs and environments. Fixing undetected bugs during testing stage and defects that might arise during updates.

Prior phases must be completed as accurate as possible. This model is structured the way that there is no return to previous phase. Any mistakes made in any of the phases would result in increased costs, time of the project and effort of the team.

The main disadvantage is the static lifecycle structure where this method can’t be employed in dynamic environment which requires an iterative approach. Waterfall lifecycle model is used in big government, military and other projects that utilise previous experience, estimation of time, costs and complexity is foreseen.

Spiral Model
Source: http://www.elanman.org/teaching/gmu/swe620-infs622/Graphics/spiral_model.gif

Spiral lifecycle model is a software development process associated with components design and prototyping. It inherits the concept of waterfall model, and involves risk analysis and iteration in each development phase.

Spiral lifecycle model follows the waterfall lifecycle model of software development, requirements analysis, design, coding, testing, and maintenance. The great distribution would be that it changed the phases of waterfall model into many pieces of iteration processes, to reduce the risk of project.

In each iteration, people should do:

 * 1) Determine objectives, alternatives and constrains.
 * 2) Evaluate alternatives.
 * 3) Identify and resolve risks.
 * 4) Develop product.
 * 5) Verify next-level product.
 * 6) Plan next phases (iteration).

People would be focusing on software management, establish the explicitly objective, and analyse the key risk.

V-Model
The V-Model (sometimes referred to as Vee Model) can be seen as a refinement of the waterfall method, with a focus on testing. It was developed for the  German Military in the 1980s, and is a  standard for all software development projects in the public sector in Germany.

The model derives its name from the fact that it can be represented as a v-shaped flow chart.

The V-Model as shown in the above diagram has the same sequence as the Waterfall Method. Each subsequent phase is begun upon the completion of the preceding one. The analytical and design phases precede coding and the testing phases follow but the relationship between each analytical/design phase and the corresponding testing phase is indicated by the horizontal arrows. So for example  unit test phase is concerned with the  implementation phase.

Phases in the V-Model
Requirements planning Determine system requirements and how the organisation's resources are to be used to meet those requirements. Create specification detailing the expected behavior of the software.

Design Includes both a high level and detailed design. High level design defines how the functions of the software will implement the specifications while detailed design is concerned with specific algorithms.

Implementation The coding phase where the algorithms from the design phase are turned into code.

Unit testing Each module is tested for errors.

Integration Testing Once each module is tested and known to be error free, they are integrated. This phase tests that the integrated modules maintain correct behaviour.

System testing The, now integrated, software system is tested in its intended hardware environment. At stage acceptance testing could also be included, here the user tests the system against the original requirements specification. Checks whether the entire software

Submodels
The V-Model is structured into submodels of which there are four; Project Management, System Development, Quality Assurance and Configuration Management.

Project Management (PM)
The PM submodel is concerned with the initiation, planning and monitoring of the project. It consists of fourteen activities.

Placement/Procurement Sending out request of proposal to possible sub-contractors. Determining best offer.

Contractor Management Ensuring that terms and conditions of contract are fulfilled. Both with customers and subcontractors.

Detailed Planning Establish a detailed plan for the project.

Cost Benefit analysis Evaluate the profitability of each of the planned solutions.

Phase Review The project status is checked at the end of each phase.

Risk Management Early prevention of risks

Project Control Ensure that the project is going according to plan. If not, take action to bring it back on course.

Information Service/Reporting Provide information to stakeholders.

Training/Instruction. Train project team members to ensure that each is aware of and able to perform their role.

Supplying resources The supply of the resources necessary for the completion of the project

Allocation of Work Orders The initiation of job sections as allocated by work orders

Staff Training The introduction of project members to their particular job section. Each member has his/her task explained to them.

Project completion Completion of the project including a final report.

System Development (SD)
The SD sub-model is concerned with the regulation of the actual development of the system. It consists of nine activities.

 * System Requirements Analysis
 * System Design
 * Software/Hardware Requirements analysis
 * Preliminary Software Design
 * Detailed Software Design
 * Software Implementation
 * Software Integration
 * System Integration
 * Transition to Utilisation

Quality Assurance (QA)
The QA sub-model specifies quality requirements for the activities and products of the other submodes. It consists of five activities.

 * QA Initialisation
 * Assessment Preparation
 * Process Assessment of Activities
 * Product Assessment
 * QA Reporting

The Configuration Management (CM)
The CM sub-model ensures that products can be identified unambiguously and that changes to products are made only in a controlled way. It consists of four main activities.

 * CM Planning
 * Product and Configuration Management
 * Change Management
 * CM Services.

Advantages/Disadvantages
Advantages
 * Strong emphasis on testing
 * Validation of internal and external deliverables not just the product.
 * Definition of requirements before designing the system.
 * Enable project management to track the progress very accurately. The completion of each phase is a milestone in the project plan.

Disadvantages
 * Does not handle concurrent events.
 * Does not handle iterations.
 * Can't handle the dynamic changing of requirements during the lifecycle.

Methodologies
Note that the methodologies below all use the incremental model.

Personal Software Process
Personal Software Process (PSP) was described by Watts Humphrey in 1994. PSP is based on Capability Maturity Model (CMM) operations. PSP has an iterative structure which defines tasks for improvement of personal development. Definition of processes in each iteration stage are measured and analysed.

Development of software begins from defining a pseudo code, following steps codes is written compiled, possible errors that might occur are reviewed. Reviewed code is tested. Personal techniques for progress measurement are developed; personal metrics allow measuring the success of the progress.

All collected information is assessed for strength and weaknesses; this allows producing personal improvements at the later stages. There are seven key models that software engineer has to pursue for PSP, these knowledge areas are:

 * 1) Foundational Knowledge – software engineers are practising defined processes which allow them to fulfil the scope with high-quality product on time.
 * 2) Basic PSP Concepts – are process fidelity, data collection, data analysis, and process improvement.
 * 3) Size Measuring and Estimating – definition of size measurement from previous, personal experience.
 * 4) Making and Tracking Project Plans – this involves the skill and tools to schedule and plan project duration for successful completion on time.
 * 5) Planning and Tracking Software Quality – creation of high-quality product that meets the scope that satisfies the customer.
 * 6) Software Design – capability for design integration into PSP.
 * 7) Process Extensions – flexibility moving from one environment to another.

Team Software Process
The Team Software Process (TSP) was developed in 1996 by Watts S. Humphrey and refined over a number of releases in the following years. There is an emphasis on advance planning and communication and an underlying goal of guiding team building and team working.

Goals
The goals of the TSP are to deliver high quality secure software and to build effective, highly motivated teams that can consistently deliver on time and within schedule and budget constraints.

Overview
Software projects often fail because teams fail to work together efficiently. TSP provides a framework that teams can follow to increase their success as well as improving the overall software development process.

TSP was devised by Watts S. Humphrey as a complementary process to Personal Software Process (PSP) and is based on practices expressed in the Capability and Maturity Model (CMM).

When Humphrey devised the PSP as an application of CMM to an individual developer, it became clear that a PSP developer could not function in a team that did not have the necessary structures in place to support PSP practices. The TSP was devised to address these problems. So where PSP is CMM for the individual, TSP is CMM for teams.

TSP is described as a CMM level 5 process, meaning that it is aimed at organisations that are at, or very close to the Optimising level in CMM and are focusing on continuous process improvement. However, TSP has been proven to be successful for organisations at CMM Level 2 (Repeatable) and has been shown to be a suitable vehicle for introducing process improvement within and organisation.

TSP teams relaunch periodically to accommodate changing requirements and issues that arise during the development process.

The Launch Meeting
The TSP Launch meeting is the key step in any TSP projects. It establishes the overall plan for the project and sets out key measurements and deadlines.

A TSP launch meeting lasts over four days and consists of nine separate meetings, the end result of which is a plan that all the team has committed to and agrees upon. It is important to note that team in this context refers to senior managers and marketing personnel as well as team leaders and developers. The TSP launch meeting should be chaired by a trained TSP launch coach.

In the first of the nine meetings, senior management and marketing establish the need for the product and the opportunity it represents. The seven interim meetings are with the team and team leader, where they break down the project into constituent parts and establish responsibilities and measures before finalising a plan (or alternative plan if the original senior management and marketing cannot be satisfied). In the last meeting, this plan is presented to senior management and either accepted or revised to meet any additional criteria. As well as having a trained coach to guide the launch process, TSP provides a launch script template to follow.

Benefits

 * Projects that do succeed in using TSP have a low risk of failure.

 * TSP projects have been proven to succeed in building highly effective motivated teams. The built-in process improvement aspect of TSP ensure that data gathered feeds back into team activities, helping to highlight issues and leading to resolutions.

 * TSP can be used as a vehicle for process improvement within an organisation. Teams can adopt TSP and use it to identify and implement process improvement.

 * TSP is scalable from single teams of between two and twenty people up to multiple teams totally 100 to 150 people.

Drawbacks

 * TSP inherits the many drawbacks of PSP, namely the bureaucratic nature of the process, a lack of tools that support the measurement aspect of the process and the difficulties associated with the significant training required.

 * TSP requires all team members to be trained in PSP. Given the problems associated with PSP training and dropout rates, TSP is almost automatically unsuitable in many cases.

 * TSP is highly customisable and while this can be of benefit in certain circumstances, the workload involved in trimming down the volume of documentation to suit the needs of a specific team and project can be daunting

 * There is disagreement as to whether TSP is an agile methodology or not. TSP advocates state that TSP is frequently accepted as being an agile methodology. This is because the process provides for periodic relaunch every three to four months. Postmortems are carried out on the current body of work and this data feeds into the next launch meeting. The principle is to discover integration and other issues early in the process and take corrective action where necessary. Critics argue that TSP is too process-heavy to be categorised as agile and the durations of iterations are too long to be truly effective.

 * A common criticism of TSP is that it is an academic process that has rarely been implemented outside of academia or a select few military and government projects. This would seem to be borne out in the types of projects cited by the Software Engineering Institute for TSP.

Additional Reading

 * The TSP Web Site

 * The Team Software Process

 * Why Big Software Projects Fail: The 12 Key Questions

 * CMMI Level 5 and the Team Software Process

Introduction
The Rational Unified Process (RUP) was developed in the late 90’s. Three prominent software experts known as the “Three Amigos” [Grady Booch, Ivar Jacobson and Jim Rumbaugh], each of whom had their own software companies and methodologies on software development and modelling, merged their ideas together to form the Unified Process, Unified Modelling Language (UML) and the Rational Software Corporation (Rational). The RUP came about when the Rational Software Corporation created its own version of the Unified Process, the Rational Unified Process.

Phases
A project that uses the RUP has iterations which are divided into four phases:

1. Inception

Here the goals, broad scope, initial architecture, project planning, start-up activities and initial process configuration of the project are defined.

2. Elaboration

Here the scope is redefined to include more specific project details such as the features to be included in the project. The architecture is developed in a greater detail to ensure the new features will be functional and also that performance and security are taken into account. A prototype can be developed to practice any new technologies that will be used in the project.

3. Construction

In the construction phase, each iteration provides for new sections of the program/feature to be designed, constructed and tested. At the end of the construction phase the software element of the project should be just about complete.

4. Transition

In the transition phase the software is gradually taken by the customer/user. This is done after user acceptance testing, beta testing and a deployment stage. If issues/bugs are found at this stage they can be fixed in a new release during this stage. Once everything is satisfactory, the software gets handed over to the client, documentation is finalised and training and support is given to the users if necessary.

Iterations
There can be any number of iterations in each phase. RUP does not set the limit but does recommend that there should only be 3 to 9 iterations per project with a duration of 2 to 6 weeks for the iterations. Iterations can be up to 8 months for very large projects using RUP.

Roles
Roles define the responsibilities within each of the 9 workflows in RUP. There are over 40 roles defined by the RUP. Each role is specific which one of the team takes on. Examples of roles are Database Designer, Software Architect, Test Designer, Process Engineer, etc. Every person in the team takes on one or more roles. Each role can have more than one person assigned to it. It is the Project Manager’s responsibility to decide who takes on what roles.

Examples of roles and responsibilities [taken from Williams, L "A Survey of Plan-Driven Development Methodologies" (2004)]:
 * Analyst, who is responsible for eliciting the needs from the stakeholders, and communicating the needs to the development team.
 * Designer, who identifies and defines the design and makes sure it is consistent with the system architecture.
 * Implementer, who is responsible for developing and testing software components.
 * Reviewer, who reviews the software product or development activities.
 * Test Designer, who defines the test approach to make sure the test is successfully implemented.
 * Tester, who implements and runs the test suites.
 * Integrator, who is responsible for planning and performing integration tasks.
 * Project manager, who manages the resource and activities of the project to ensure the success of the outcome.
 * Technical writer, who composes the communications from the developer for the product stakeholder.
 * Software architect, who is responsible for the system architecture.
 * User interface designer, who works with the developers to produce desired user interface.

RUP Artefacts [Artifacts in American-English]
These are mostly either documents or else collection of documents. The people assigned to certain roles created and update the artefacts for that role. Examples are Vision, Use Case Model, Software Architecture Document, etc. There are more than 100 different artefacts defined by the RUP.

Disciplines and Workflows
Activities link the roles and the artefacts together by having the person in a role create or update the artefacts during a specific activity. There are over 60 workflow details defined in the RUP between the 9 disciplines, each of which are broken down into more steps.

Use Case Driven Development
The idea of a “use case” comes from the RUP. It conveys the steps required in order for a task to be completed and does so in a non-technical manner so that anybody would be able to understand it. This makes is much easer for the system developers to work with the customers and helps in finding out what the actual requirements of the customer are.

Benefits/Disadvantages of Plan-driven software development
Comparing of the agile software development, the Plan-driven development is a traditional development method, it does more emphasise particularly on plan and architecture. Plan-driven development methods’ attention is quality of software and predictability of process. The first rank paradigm of Plan-driven methods is related with capability maturity model (CMM).

Plan-driven software development is come from system engineering and the criterion of quality, builds up the principle of system engineering, coordinates lots of components which need work together accurately.

In order to push the process of software development, the Plan-driven development precisely depends on clear procedures.

Typically, the waterfall lifecycle model starts with some requirements analysis, moves into design, then coding, then implementation, testing, and finally maintenance. Every phase all need its former correct specific requirements, then can continue.

Note however that the example plan-driven methodologies above all use the incremental model, none use the waterfall model

So the key point of plan-driven software development is definition of the process and management. The advantage is its comparability and repeatability in association with the improvement of the procedure.

The main flaws of some plan-driven software development are that requirements change over time, as businesses and the environment in which they operate change rapidly. So it could not suitable for rapid development. Furthermore, the Plan-driven software development advocates predicting change using the framework. The framework will affect some waste of the resource in this rapid development environment. At last, from the culture aspect, plan-driven development could not let people feel comfortable, authorised, and more freedom under development.

Incremental model, such as the example methodologies above, and spiral model plan-driven software development better accommodate change through the use of iterations than the waterfall model.

Introduction
With the hype surrounding Agile methods, there is a temptation to believe that plan driven development is effectively defunct and is only used in very specific circumstances on very specialised projects.

While it is difficult to get exact data on the popularity of various software development methodologies there are a few surveys which provide some level of information. All of these suggest that Waterfall development is still widely used, even though that is declining as agile methods like XP become better understood.

Another indicator of the persisting use of waterfall style development is the body of work being produced that addresses ways of transitioning from waterfall and other non-iterative plan-driven processes to iterative development processes (such as the three example methdologies above), and also techniques for mixing both types of processes.

These factors suggest that waterfall style development is alive and well in many organisations.

Use in Open Source Projects
Open source projects are effectively incompatible with most forms of plan driven development. In most cases it is impractical to apply the level of process and documentation to open source projects.

The team membership grows and shrinks through the lifetime of an open source project. Contributors often only engage in the parts of the project in which they have an interest or even appropriate expertise. Participation is often voluntary. It would be impossible to ensure that contributors were trained in or complied with a process-heavy development process.

Also, the consensus based philosophy of the open source development process is effectively incompatible with the bureaucratic, top-down organisational structures that are characteristic of most plan driven development processes.

Use in Industry
Within the software industry, plan driven development is still widely used on military and government projects, particularly many that mandate the incremental model. It also prevails in many large financial institutions. There is plenty of evidence to suggest that even these organisations are transitioning to other iterative and especially agile processes and methodologies. Whether these organisations will eventually transition completely away from the 'old-style' processes remains to be seen but for now it is likely that the two approaches to software development must co-exist.

For example, an "early and striking example of a major IID success is the very heart of NASA’s space shuttle software—the primary avionics software system, which FSD built from 1977 to 1980. The team applied IID in a series of 17 iterations over 31 months, averaging around eight weeks per iteration. Their motivation for avoiding the waterfall life cycle was that the shuttle program’s requirements changed during the software development process". ["Iterative and Incremental Development: A Brief History", Craig Larman and Victor Basili, IEEE Computer, June 2003]

Why does Plan Driven Development persist
There are many reasons why organisations persist with plan driven development processes like the incremental methodologies above and Waterfall.

Standards
Requirements of suppliers to meet standards set by customers may dictate the development process that is used in a given organisation. Aspects of iterative development may be incompatible with the standards set by customers.

For example the US Department of Defense standard 5000.2 (like Mil-Std-498 before it) has planning requirements with a strong preference for evolutionary (incremental and iterative, such as the example methodologies above) over single step (waterfall):

"There are two approaches, evolutionary and single step, to full capability. An evolutionary approach is preferred. … [In this] approach, the ultimate capability delivered to the user is divided into two or more blocks, with increasing increments of capability...software development shall follow an iterative spiral development process in which continually expanding software versions are based on learning from earlier development."

Expertise
May organisations have teams that are well versed in existing plan driven development processes. Many of these will be highly skilled professionals with a track record of delivering software using a plan driven process. Abandoning these proven processes and embarking on retraining is often difficult to justify

Dependencies
In many cases the software development process is part of a larger process within the business. Changing the development process without disrupting other processes and keeping to required standards is not an easy thing to do and may be obstacle to adoption of different (e.g. one of the iterative methodologies above, if currently waterfall) development processes.

Documentation
There are issues around documentation that arise when using iterative development. In it's first form, more bureaucratic organisations that value project documentation will have difficulties adapting to certain aspects of the iterative process where standard design, architecture and other planning documents are not as prevalent. This is also another area where iterative development processes can come into conflict with meeting required standards.

Planning
For a project manager versed in waterfall plan driven development, iterative development projects (such as the incremental plan-driven methdologies above) are initially daunting. There is a lesser degree of predictability with iterative development which is a natural consequence of increased flexibility.

Culture
Cross all of the issues above is the culture within a company. Iterative development can be a huge upheaval both personal and professional within an organisation. Often iterative development can pose such a radical change in work practices as to appear unworkable in organisations well versed in Waterfall style development.

Future
The transition to iterative development, such as the three methodologies above, is ongoing, and the benefits that waterfall style development bring to many organisations will ensure it remains in use until iterative and/or agile methods can address the concerns of these organisations in the same way that plan driven has done in the past.

Additional Reading and References
Requirements Engineering: The state of the practice

[http://www.ddj.com/architect/200001986 Survey says... Agile has crossed the chasm]

Converting a project from a waterfall to an iterative approach

Turning Waterfall Contracts into Scrum Contracts

MIL-STD-498

Iterative and Incremental Development: A Brief History, IEEE Computer June 2003

Software Development Methods
With every endeavour taken it is proven by experience that a methodological approach saves times and provide better quality results. This also applies to software development. All methodologies that are used by software developing organisations can be categorised into two main streams namely Plan-Driven Development and Agile Development. Both these methodologies include components such as defined processes, procedures and documentation. However it is the approach in utilising these components to successfully complete a software development project.

Plan-driven development may be broken up into waterfall development and plan-driven incremental development, as detailed above.

In order to understand the different approaches that define either Plan-Driven or Agile development in software engineering, it is important to identify the general phases that occurs in nearly any software project. The International Organisation for Standardisation (ISO) conducted research that led to the establishment of a standard (ISO 12207) that describes a set of processes and tasks that defines the lifecycle for software. While some methodologies might work with different phases in a particular project domain, the following phases are repeatedly apparent in software development cycles.

 * Requirements: In the requirements phase the project team needs to capture what the client needs are in relation to a software product. The requirements are always documented in some format and signing the document of makes the requirements official. Requirements can change during a project therefore it is important to state the boundaries of a product.

 * Design: The design phase allows the project team to reflect proposals for the implementation of the software product and highlight boundaries and needed interfaces in the existing environment. When stakeholders agree on these proposals a detailed design is established which encompasses coding specifications

 * Coding: This phase involves the actual development of the core product based on the designs agreed on. The project team uses coding standards and reviews. Also developers use comments in the code and test driven development can be applied to save debugging time afterwards.

 * Testing: When the application is coded test plans are executed to determine a working product in the client’s environment. This is followed by the actual system test to ensure that all features are working. It is important to include end users in the testing process in order to tackle any other problems prior to release of the system.

 * Integration and implementation: This involves the roll-out of the system in the client’s environment.

 * Documentation & Maintenance: The documentation produced at each phase of the project is categorised in two sections: Internal & External. Internal documentation is project plans, specifications, designs and test plans. These are useful should the client need additional features to the system in the future. External documentation include user, operational, technical and training guides. These are important documents to sustain the system

 * Upgrade & Retirement: Should the requirements of the business change, the current system could undergo certain upgrades to support the business. Or requirements could have changed in such a drastic manner that a new system is needed in this case it could be more cost effective to replace the system instead of upgrading it.

Foundation of Plan-Driven & Agile Development
There is one major fundamental difference between Plan-Driven and Agile development. Plan-Driven development tends to be successful in an environment where all properties of the end product are specified in detail and provides a clear model of a fixed end result. It assumes that a project is predictable and therefore it is possible to plan and design the whole from beginning to end form the start. An example of a Plan-Driven Development in practice can be the construction of a large building. In this an architect designs the building completely based on the requirements of the customer before the first brick is laid. A software example could be an application that allows remote workers to connect to the office and access company specific resources.

In contrast Agile development is a much better approach when the properties of the final product cannot be determined on beforehand. The projects requires a basic part of the project to be built in order to determine what is needed in order for the product to evolve. To give an example of Agile development in the same context as the remote workplace, a client could need a portal that includes intranet, extranet and online collaboration for internal and external workers that are based locally or remote. Since the requirements are somewhat unclear it impossible to design the whole system upfront prior to implementation. It requires exploration of requirements for certain deliverables in every separate component.

Plan-Driven vs. Agile Development
For making a fundamental comparison between Plan-Driven & Agile development, Michael Hirsh has clearly described how the general software development phases described above are approached in each development process. The following table provides examples and descriptions of each software development phase applied in either Plan-Drive or Agile software development.

title: Plan-driven software development


text:
User talk:Walkingdictionary1928

Welcome
Hello Walkingdictionary1928, 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;
 * [ Ask] a question, discuss Wikiversity, etc. at the Colloquium;
 * Read and help develop our community policies, or
 * Chat with other Wikiversians on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold, and see you around Wikiversity! --Emesee 18:04, 25 October 2008 (UTC)

title: User talk:Walkingdictionary1928


text:
User:Walkingdictionary1928

Hi! I am a walking dictionary and am known as that! i can write scary stories well, so please please, read some of mine! they will be scattered across this page! thank you!

title: User:Walkingdictionary1928


text:
User talk:Filiberto

 Hello Filiberto, 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.
 * Visit a (kind of) random random project.
 * Browse everything on Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold to contribute and to experiment with the sandbox or your userpage, and see you around Wikiversity! --mikeu talk 20:16, 25 October 2008 (UTC)

title: User talk:Filiberto


text:
User talk:Jestermeister

 Hello Jestermeister, 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.
 * Visit a (kind of) random random project.
 * Browse everything on Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold to contribute and to experiment with the sandbox or your userpage, and see you around Wikiversity! --mikeu talk 20:22, 25 October 2008 (UTC)

Seed section
Hi! I was having a look at your "Seed" articles, and they are very good - it is an area I don't know a lot about, and I picked up quite a bit reading through your work. However, I also noticed that you've used a lot of non-free images. They're all great, but there's a slight problem in that non-free images aren't technically permitted in userspace. So I figure we've got a couple of choices - ignore it, which I'm inclined to do, or move the work to mainspace. (Removing them doesn't seem like a good choice). So I wanted to ask- are you happy to move the content to mainspace yet? Or would you rather I just add rationales to the files as is. :) - Bilby 02:18, 26 October 2011 (UTC)

title: User talk:Jestermeister


text:
User talk:Stevenarntson/Online

To add your own links, copy the format below and paste it into the edit box after clicking the "edit this page" tab. Change the URL and then the title of the link to match the contribution you want to add.

==== Resource Name ====

a description of the resource here. a description of the resource here. a description of the resource here. a description of the resource here. a description of the resource here. a description of the resource here.

 * Example Link

~(this will leave your signature, if you are logged in)

Hydrogen
Hydrogen is an advanced drum machine for GNU/Linux. It's main goal is to bring professional yet simple and intuitive pattern-based drum programming. It is available for Windows, Mac OS X, and any Linux distribution such as Ubuntu Linux.

 * Hydrogen Drum Machine

Scottmccaffree 21:01, 25 October 2008 (UTC)

Wings 3D
Wings 3D is a subdivision modeler inspired by Nendo and Mirai from Izware. It is available for Windows, Mac OS X, and any Linux distribution such as Ubuntu Linux.

 * Wings 3D

Scottmccaffree 21:06, 25 October 2008 (UTC)

Mint.com
Mint.com is a great place to track your check balances, budgets, transactions, and investments. It's also free.

 * Mint.com

Aaron Reinke 05:42, 30 January 2009 (UTC)

Pandora Radio
Pandora is a free online streaming radio that plays music similar to whatever artist you have chosen. You can discover a lot of really good musicians and also have free radio at the same time. Just type in the name of an artist and get that artist plus other musicians in like-genres.

 * Pandora Radio

JohnCardoso 04:22, 5 February 2009 (UTC)

stock.xchng
This is another free stock photo website. Their material is all royalty free and usually available in very high resolutions. It can sometimes be difficult to find what you need because their search engine seems to completely disregard tags at times, but I've found it to be a valuable resource overall.

 * stock.xchng

Hjfrew 22:18, 31 July 2009 (UTC)

title: User talk:Stevenarntson/Online


text:
Wiki Campus Radio/PSA

This page is workspace for example PSA's based on those that might air on radio or podcast media.

1
A moment of absence..

...could become a life-time.

(with authority) Think! Driver Inattention Kills!'

2
A moment of absence..

... could became a life-time

(with authority) Think! Driving needs your attention.

Shock of his life.
Fred thought he knew better than the regulations,

He got the (pause)

Shock of his life.

(With authority) Don't mess with High Voltage!

Single Dollar (2011-10-29)
A single dollar?

Is that what a life is worth? A single measly dollar?

Life isn't cheap, A battery is.

Check your smoke alarm.

Wood Burning 1 (2011-10-29)
It's that time of year?

Thinking of clearing the garden?

Make sure it's only the rubbish you clear!

(with Authority) FIRE KILLS! Keep Bonfires under close supervision!

' I don't like to pry:'
Female Voice:

I don't like to pry, but .. this week...

Did you hear about Mr Smith at No 42? Well, it comes as a shock ... I mean we didn't know about the fall... and he'd only gone up to check the gutters..

or Mrs Jones in the close... You know heart murmer.. Nasty business really... Found her in the kitchen apparently... 3 Days.... and no-one heard a word...

Oh and then there's Dave.. Young loveable but bonkers dave... Forgets his pills ... You'd have thought someone would have noticed... But Dave's well Dave...

Fred over the road.. Fought in Korea ... fancy him trusting the man saying he'd won the lottery. .. Not all there these days they say...

I mean, I don't like to pry...

VO: Be a good neighbour! Don't be scared to ask vulnerable neighbours if they are OK.

"Mrs Smith doesn't get vistors..."
Mrs Smith is fine, she doesn't get vistors, Her husband's dead, the children away, and the gas meter read, last tues-day.

Except Mrs Smith isn't fine... because Mrs Smith could be dying..

Mrs Smith is fine, she doesn't get vistors, the bin-men keep to the path and don't pry, Papers none since years long gone by...

Except Mrs smith isn't fine... because Mrs Smith could be dying...

Mrs Smith is fine, She doesn't get visitors, The neighbours next door, keep themselves, Over the road doesn't delve..

Except Mrs Smith isn't fine... because Mrs Smith could be dying...

The small step down to get the mail. The dizzy spell that made her so pale.. The house is so quiet, The house is so still.

Mrs Smith isn't fine, Mrs Smith doesn't get visitors... anymore... VO: Be a good neighbour! Don't be afraid to check on vulnerable neighbours..

One puff (from IRC)
One puff, and your'e so adult. One puff and you are cool, Yet many puffs will take their toll, as the grasp expands with each one you roll. A lung pitch black, a wheezing pain, is this really such a gain? Discolored teeth in weary smiles, Could you walk those needed miles? And the firey imp is always there, the match, the lighter an evil pair! Step back, I say from this doom Cast out the smoke filled, toxic gloom. VO: Keep the Horrors for Halloween. - Smoking KILLS !

Last Cigarette
(Narration) Fred thought he was careful...

He'd locked up

Put the gas out

Turned off the heater...

In bed he smoked a last cigarette, before he drifted into a thoughtful slumber.

Fire KILLS. Put it out, Right Out!

Fog
(incomplete) Fog is out upon the roads.

Movement can seem like a dream, but there will be no wake-up scream.

Kill you speed, not someone's child beware of others not so mild.

Fog is out upon the roads.

VO 2: Think! Driving in fog needs extra care.

Heatwave
Issue : Some simple advice for heatwave weather...

Script
The sun is out to shine, It's going to be fine. The sun is out to shine, It's going to be fine.

Be sure you've got some shade, some spot where the shadows can be layed. Be sure you've got some shade, some spot where the shadows can be layed. And cover up that parked car, a sunshade will go far. And cover up that parked car, a sunshade will go far.

Keep the clothing loose and long, and you won't go far wrong. Keep the clothing loose and long, and you won't go far wrong. Wear a nice brimed hat, or perhaps that baseball cap Wear a nice brimed hat, or perhaps that baseball cap

The sun is out to shine, It's going to be fine. The sun is out to shine, It's going to be fine.

Be sure to watch the fluid flow, don't end up in a low Be sure to watch the fluid flow, don't end up in a low And if you overheat, re-consider that epic feat. And if you overheat, re-consider that epic feat.

The sun is out to shine, It's going to be fine. The sun is out to shine, It's going to be fine.

Use Water Responsibly
VO:'
 * Do you remember the Summer of '76?

VO:
 * Standpipes on the streets

VO:
 * Water on ration.

VO:
 * If a prolonged drought were to occur in Britain.

VO:
 * The nightmare could happen again..

VO:
 * Imagine,(pause)
 * Trains and Buses, dusty from their work.(pause)
 * The workforce idle because the factories can't be cleaned. (pause)
 * Swimming pools empty, and playing fields turning brown. (pause)
 * No fountains, cascades or water-falls. (pause)
 * No ice in the cocktail shaker. (pause)

VO:
 * This could all happen in a drought.

VO:
 * In extremis, ALL non-essential water use could be curtailed and public supplies rationed.

VO:
 * This nightmare can be avoided.

VO:
 * Use Water responsibly. Don't Waste it!

Water use (Leaks 1)
VO:
 * If you leaked blood, you'd seek assistance.
 * (enforcing ) So fix that dripping tap now !

VO:'
 * Water. Don't Waste it..

Water Use ( Leaks 2)
VO:
 * If your arteries burst, you'd call a Doctor.
 * Burst pipes waste water, and can cause serious damage.

 * (enforcing) - Check your pipes and get them fixed - TODAY!

VO:'
 * Water. Don't Waste it.

Stay Away from the Edge
Issue : Waterways Safety

(Note this is directly influenced by a famous PIF narrated by Donald Plesance.) VO(Narration): I am the spirit of waterways past. Yet I still see the fools, in foolish mis-venture cast

The revellers afloat, or even aside, If not with sense, with my embrace shall em-bide?

The misplaced footing, the balance that slipped. And into my chill, the inebriate dipped.

The child, so playful and without supervised care, Badly in my dark waters, will fair..

A swimmer I spy, yet in my embrace he could die. The rubbish below, a fever to-go?

As to my depth, could I have perhaps lied? And what of the currents, or even a tide?

This said there are those who don't need this re-told. Following as ever a long e-stablished code.

I am the spirit of waterways past. Yet I still see the fools, in misadventure cast VO: (authortative) 'Stay SAFE Near Waterways this summer!'

A cold Embrace?
(female voice) I am the spirit of an old lonely pond, and with reveller unwary I will be bond.

I'm moderately remote, but not out of the way, and seemingly solid, on a cold winter's day

But the fool and his arrogant pride into my depths, I shall be their bride!

The center crack'd up in cricle deepn'ng As uncatious fellow sinking and scream'ng!

But no gentle lady, can I claim to be for my embrace, the last they shall see.

And cold are my arms, around them env-elope And with that could any life cope?

I am the spirit of an old lonely pond, and with reveller unwary I will be bond.

I'm moderately remote, but not out of the way, and seemingly solid, on a ..cold .. winter's .. day VO: Frozen ponds can be thinner than you think!

Tractors mate, don't overtake
If you are stuck in a queue... wait, don't overtake.

Don't crash. Oncoming traffic can come faster than you think

is it worth risking your life to save a few minutes?

If you see farm vehicles, Think!

 Arthur Kerensa (discuss • contribs) 21:15, 10 December 2017 (UTC)

Go with the herd?
If you get caught by a herd ... wait, don't overtake.

That dumb animal is smarter than you think,

Is it worth risking your life to save a few minutes?

If you see livestock, Think! ShakespeareFan00 (discuss • contribs) 21:19, 10 December 2017 (UTC)

1.
Don't get to close to cliffs

Underwater rocks are further out than they look

Before you sink, Think !

Arthur Kerensa (discuss • contribs) 21:31, 10 December 2017 (UTC)

2.
Cliffs you can see.

Submerged rocks ,reefs, and wrecks you can't

Always check your charts, aids and sense.

Before you sink, Think! ShakespeareFan00 (discuss • contribs) 21:46, 10 December 2017 (UTC)

NB: Next one mostly aimed at recreational boaters, the professional mariners alreayd have stringent regulations and codes of practise.

3.
A "drunk in charge" is nobody's friend.

Don't let a simple drink ruin a trip!

Before you sink, Think. ShakespeareFan00 (discuss • contribs) 21:46, 10 December 2017 (UTC)

4.
A warning offshore, A fool to ignore.

Weather forecasts are not for someone else.

Before you sink, Think! 21:50, 10 December 2017 (UTC)

5. Old Shanty
(Shanty Sung Starts Jovially but shifts towards minor key as it progresses) What shall we do with a Drunken Sailor? What SHALL we do with a Drunken Sailor? What shall we do with a Drunken Sailor? Ear-ly in the morning!

Let him be merry, because they seem sober, Let him be merry, because they seems sober, Let him be merry, because they seems sober?

Keep him ashore, because he had too many, Keep him ashore, because he had too many, Keep him ashore, because he had too many! Ear-ly in the morning!

Keep'em in the lock-up for two months clear, Keep'em in the lock-up for two months clear, Keep'em in the lock-up for two months clear! Ear-ly in the morning.

(shift to minor key in music and melancholy/somber voice) Pull him out blue, by the har-bours wall Pull him out blue, by the har-bours wall Pull him out blue, by the har-bours wall Ear-ly in the morning!

VO (with authority): A "Drunken sailor" is always safest ashore. VO: Before you sink, Think!

Lonely Building
Issue : Condemned buildings - Keep Out!

Script
VO1 I am the building at the end of the street. I am the derelict, abandoned, asleep.

Yet I am the trap, that will catch the fool, waiting to ensnare those trying to be cool.

The old beams and thus floor that could give way, the stairs and landing to the ground violently sway.

So DO heed the signs so often ignored. and reject the stupidity into the mix poured.

Some think of such stark warnings in an ignorant jest, but they will come shortly   to an in-finite rest.

I am the building at the end of the street I am the derelict, abandoned asleep.

VO2:
 * Keep the Horrors at Home !
 * Stay OUT of Condemned buildings!

Dark night
Issue : Visibility at night.

Script
VO1:

I am the night, I am the dark.. I am a danger, The consequence Stark!

Drivers pass through me, maybe with care? . So be-wary stranger, if in-to me dare.

The cyclist I hide, if no brightness applied. And to how many travellers have faulty lamps lied?

The traveller on foot - easy to snare. Unless reflective and visible, yeah.

The motorist driver easier still, Unless sound judgement applied over thrill.

I am the night, I am the dark.. I am a danger, I can leave a mark.

Drivers pass through me, maybe with care? . So be-wary stranger, if into me you dare.

VO2:
 * Keep the Horrors at Home!
 * Think! Be seen in the Dark!

Silent Killer
Issue : Carbon Monoxide poisoning from faulty propane/gas appliances.

Script
I'm called the silent killer, a master of my art. and hopefully this poem, shall some sense impart.

No one has yet seen me, only the resultant fall, sleeping victims, as always in my deadly enthral.

No sound to wake them, to my pres-en-ting form and no odour to sense, my approach in-bound borne.

A mystic sleep I will cause, no dread upon the souls. Just like the poor canary, deep down in mined out holes.

I will tend to choke them slowly, A poison in their blood, As I shall continue, and into their lungs I flood.

The oldest and the youngest into my grasp if nothing done, and without some attention, my will, it shall become.

Some claim they'll know me, action will not impart. But then I'm the silent killer, a master of my art....

Carbon Monoxide KILLS! Get your appliances checked regularly!

Don't Walk!
Issue : Jaywalking

Script
Notes: This is intended to be a 'Jazz Singer' type singer, and could utilise call-response. Hey listen brother, Listen good Cause this song heed you should

When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk you can be on you way When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk you can be on you way

The city cars are mighty fast So stop until the danger past When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk on your way for sure

When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk you can be on you way

The signs they may seem tedious But still, they mean serious When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk cross you can at will

When the sign says Don't Walk - Don't Walk! When the sign says Don't Walk - Don't Walk! But when it says Walk you can be on you way

The Freeze
Status : Ready for test recording Issue: Cold Weather, really more to do with ice, than snow..

Script
Notes: This was not RP English, but Regional (Think Archers accent or simmilar)

I'm known by many a name. Jack frost be one the same. I'm also known as the freeze so respect me if you please.

Working outside in my time o'year my icy hand you need not fear Wrap-up warm, and my chill, you com-bat-ate with skill.

The hearth-en home warp as well for heat it does not dwell, Toward the cooler it will lead unless it's path, you should impede.

Now pipes, be a specialty of mine, in weather clear, and frost so fine, So lag them up if needs may must, as ice sha-tter metal and rust.

I am known by many a name Jack Frost be one the same. I'm also known as the freeze so respect me if you please.

Wikimedia
PSA's related to Wikimedia matters...

Ideas:

 * Minority outreach?

Resorces

 * AD Council - Official site, (Browse campaigns) Organisation that helps produce PSA's in the US, (The adverts it distributes are not necessarily licensing compatible with Wikimedia projects though).

 * http://www.uscgboating.org/
 * http://www.uscgboating.org/command/resource.htm

title: Wiki Campus Radio/PSA


text:
Talk:Educational Media Awareness Campaign/Music/POTD 2

Perhaps it would be a good idea to remind the readers, including some who haven't experienced it before, that the names of the notes on the diagram are rendered in the German system ("H" is the same note as B-natural. "B" is the same note as B-flat.  "-Es" and "-as" mean flat, "-is" means sharp).


text:
User:Foolestroupe

Boo! Foolestroupe 10:57, 26 October 2008 (UTC)

title: User:Foolestroupe


text:
User talk:Foolestroupe

Start! Foolestroupe 10:58, 26 October 2008 (UTC)

title: User talk:Foolestroupe


text:
Enterprise Resource Planning/Presales and Business Analysis/05

Users Want Functionality First
This is a lesson part of the module ERP Presales and Business Analysis out of the Open Source ERP/Executive Diploma course conducted by a private university.

Topics

 * A frightening number of IT projects "failed" - failed to meet budget, failed to meet deadlines and failed to meet user requirements.

Discussion

 * How many percent of IT projects fail and how many percent of ERP projects fail? Why the difference?
 * Why is it important for enterprise systems (and thus, the professionals who implement them for enterprises) to meet user requirements?
 * What is the difference between the "Client" and the "User"?
 * In what ways can Open Source ERP professionals mitigate the risk of not meeting client/user requirements?

Activities

 * Publish your works in an attractive manner in your user page, stating your own views and findings providing links to your sources. Use the talk page here to score marks.
 * Create or edit sub-pages of course materials within wikiversity.
 * Discuss in the forum (link shall be provided) by offering your ideas and answering or comment on others' postings.

Links to Student Notes
(Provided by Students - subject to edit ranking by tutor)

Notable Links to Resources
(Provided by Students - subject to edit ranking by tutor)

Sub-Pages
(Done in wikiversity as course material by the students under the guidance of the tutor)


text:
Talk:Consensus in a wiki environment/Establishing consensus

A key is to look for common ground. Hillgentleman | //\\ |Talk 11:54, 26 October 2008 (UTC)


text:
Enterprise Resource Planning/Accounting/1

Introduction to the accounting equation
This is a lesson part of the module ERP Accounting out of the Open Source ERP/Executive Masters course conducted by a private university.

Topics

 * The accounting equation is the basis for book keeping and all accounting. A strong fundamental understanding of this equation and its application is the difference between having a passing understanding of accounting versus being able to add value, and squeezing the maximum benefit from OSS ERP.

Discussion

 * Why is "book keeping" also called the "double entry system" ?
 * Can you name some of the benefits of adopting the "double entry system" ?

Activities

 * Publish your works in an attractive manner in your user page, stating your own views and findings providing links to your sources. Use the talk page here to score marks.
 * Create or edit sub-pages of course materials within wikiversity.
 * Discuss in the forum (link shall be provided) by offering your ideas and answering or comment on others' postings.
 * Work through all the drills from AccountingCoach.

Links to Student Notes
(Provided by Students - subject to edit ranking by tutor)

Notable Links to Resources
(Provided by Students - subject to edit ranking by tutor)

Sub-Pages
(Done in wikiversity as course material by the students under the guidance of the tutor)


text:
User talk:Izamryan

 Hello Izamryan, 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.
 * Visit a (kind of) random random project.
 * Browse everything on Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.

And don't forget to explore Wikiversity with the links to your left. Be bold to contribute and to experiment with the sandbox or your userpage, and see you around Wikiversity! --Cormaggio talk 16:35, 26 October 2008 (UTC)

title: User talk:Izamryan


text:
Template:Move

Instructions

 * Transclude, using:
 * 1st parameter: Target name for move
 * 2nd parameter (optional): reason

title: Template:Move


text:
Category:Requests for custodial action

__HIDDENCAT__

title: Category:Requests for custodial action