FDD is a software development process that is client-centric, architecture-centric, and pragmatic. It focuses on developing features, which are small client-valued functions. Key aspects of FDD include developing an overall model, building a prioritized feature list, planning by feature, designing by feature, and building by feature in an iterative process. FDD was created by Jeff DeLuca in 1997 for a banking project and combines techniques like modeling, domain-driven design, and agile practices like XP.
FDD is an agile software development methodology that employs a short iterative process. It consists of 5 steps: develop an overall model, build a features list, plan by feature, design by feature, and build by feature. FDD is designed for large projects and teams, and combines best practices from other agile methods. It focuses on developing features in 2 week increments with mandatory code reviews, and involves customers during modeling and design.
The document discusses strategies for working with legacy code, which is code inherited from previous developers or older versions that often lacks tests and good documentation. It defines legacy code and outlines challenges like poor structure, dependencies, and lack of tests. It then provides approaches for modifying legacy code like identifying what to change and test, breaking dependencies, writing tests, and refactoring code in small, tested increments. Specific tactics are presented like using seams, sprouting methods, and interfaces to break dependencies and allow testing legacy code. The importance of understanding the system and increasing test coverage before making changes is emphasized.
Requirement prioritization is used in Software product management for determining which candidate requirements of a software product should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first. Several methods for assessing a prioritization of software requirements exist.
The document discusses various software production process models, including traditional waterfall models, iterative models like the spiral model, and agile methodologies. Waterfall models involve sequential phases from requirements to maintenance but lack flexibility. Iterative models divide the process into increments with feedback between phases. Agile methods like Scrum, Extreme Programming, and Smart emphasize rapid, incremental delivery, automating processes, and customer involvement. The choice of model depends on factors like requirements volatility, team experience, and project priorities.
Feature Driven Development (FDD) is an agile software development process that divides projects into small incremental pieces of work called features. The FDD process involves 5 main steps: developing an overall model, building a features list, designing by feature, coding by feature, and testing by feature. Key roles in FDD include a project manager, chief architect, and development manager who work with chief programmers and class owners to plan and implement features in 2 week iterations. FDD aims to improve communication, reduce complexity, and increase quality through its iterative approach and emphasis on modeling, class ownership, and tracking progress at the feature level.
FDD is a software development process that is client-centric, architecture-centric, and pragmatic. It focuses on developing features, which are small client-valued functions. Key aspects of FDD include developing an overall model, building a prioritized feature list, planning by feature, designing by feature, and building by feature in an iterative process. FDD was created by Jeff DeLuca in 1997 for a banking project and combines techniques like modeling, domain-driven design, and agile practices like XP.
FDD is an agile software development methodology that employs a short iterative process. It consists of 5 steps: develop an overall model, build a features list, plan by feature, design by feature, and build by feature. FDD is designed for large projects and teams, and combines best practices from other agile methods. It focuses on developing features in 2 week increments with mandatory code reviews, and involves customers during modeling and design.
The document discusses strategies for working with legacy code, which is code inherited from previous developers or older versions that often lacks tests and good documentation. It defines legacy code and outlines challenges like poor structure, dependencies, and lack of tests. It then provides approaches for modifying legacy code like identifying what to change and test, breaking dependencies, writing tests, and refactoring code in small, tested increments. Specific tactics are presented like using seams, sprouting methods, and interfaces to break dependencies and allow testing legacy code. The importance of understanding the system and increasing test coverage before making changes is emphasized.
Requirement prioritization is used in Software product management for determining which candidate requirements of a software product should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first. Several methods for assessing a prioritization of software requirements exist.
The document discusses various software production process models, including traditional waterfall models, iterative models like the spiral model, and agile methodologies. Waterfall models involve sequential phases from requirements to maintenance but lack flexibility. Iterative models divide the process into increments with feedback between phases. Agile methods like Scrum, Extreme Programming, and Smart emphasize rapid, incremental delivery, automating processes, and customer involvement. The choice of model depends on factors like requirements volatility, team experience, and project priorities.
Feature Driven Development (FDD) is an agile software development process that divides projects into small incremental pieces of work called features. The FDD process involves 5 main steps: developing an overall model, building a features list, designing by feature, coding by feature, and testing by feature. Key roles in FDD include a project manager, chief architect, and development manager who work with chief programmers and class owners to plan and implement features in 2 week iterations. FDD aims to improve communication, reduce complexity, and increase quality through its iterative approach and emphasis on modeling, class ownership, and tracking progress at the feature level.
Pasaules lielākā mācību stunda: Saldus 1. vidusskolas prezentācijaliela_stunda
Plašāk par akciju "Pasaules lielākā mācību stunda" Latvijā un Saldus 1. vidusskolas dalību lasiet šeit: http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/saldus-medus-piliens-kurzeme-pasaules-lielaka-stunda-saldus-1vidusskola/
Lai veidotu izpratni par gaisa un ūdens piesārņojuma avotiem un to ietekmi uz vidi, Kuldīgas Centra vidusskolas 7., 8.,9., un10. klasēs notika Pasaues lielākā mācību stunda, kas veltīta gaisa un ūdens piesārņojuma tēmai. Plašāk par stundu un akciju lasiet šeit: http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/gaisa-un-udens-piesarnojums-pasaules-lielaka-macibu-stunda-kuldigas-centra-7-10klases/
Pasaules lielākā mācību stunda Liepājas 7. vidusskolas 2. klasēliela_stunda
Pasaules lielākā mācību stunda Liepājas 7. vidusskolas 2. klasē.Plašāk lasiet šeit:http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/veseliba-celojums-uz-veselibas-valstibu-pasaules-lielaka-macibu-stunda-liepajas-7-vidusskolas-2-klas/
Pasaules lielākā mācību stunda Kuldīgas tehnoloģiju un tūrisma tehnikumā. Lasi vairāk šeit:http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/globalas-vides-problemas-un-mana-personiga-atbildiba-liela-stunda-kuldigas-tehnologiju-un-turisma-te/
Materiāli sagatavoti starptautiskās akcijas Pasaules lielākā mācību stunda ietvaros.
Plašāk: http://worldslargestlesson.globalgoals.org/
Latvijā: www.skolas.unesco.lv
Pasaules lielākā mācību stunda: Saldus 1. vidusskolas prezentācijaliela_stunda
Plašāk par akciju "Pasaules lielākā mācību stunda" Latvijā un Saldus 1. vidusskolas dalību lasiet šeit: http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/saldus-medus-piliens-kurzeme-pasaules-lielaka-stunda-saldus-1vidusskola/
Lai veidotu izpratni par gaisa un ūdens piesārņojuma avotiem un to ietekmi uz vidi, Kuldīgas Centra vidusskolas 7., 8.,9., un10. klasēs notika Pasaues lielākā mācību stunda, kas veltīta gaisa un ūdens piesārņojuma tēmai. Plašāk par stundu un akciju lasiet šeit: http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/gaisa-un-udens-piesarnojums-pasaules-lielaka-macibu-stunda-kuldigas-centra-7-10klases/
Pasaules lielākā mācību stunda Liepājas 7. vidusskolas 2. klasēliela_stunda
Pasaules lielākā mācību stunda Liepājas 7. vidusskolas 2. klasē.Plašāk lasiet šeit:http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/veseliba-celojums-uz-veselibas-valstibu-pasaules-lielaka-macibu-stunda-liepajas-7-vidusskolas-2-klas/
Pasaules lielākā mācību stunda Kuldīgas tehnoloģiju un tūrisma tehnikumā. Lasi vairāk šeit:http://skolas.unesco.lv/lv/pasaules-lielaka-stunda/globalas-vides-problemas-un-mana-personiga-atbildiba-liela-stunda-kuldigas-tehnologiju-un-turisma-te/
Materiāli sagatavoti starptautiskās akcijas Pasaules lielākā mācību stunda ietvaros.
Plašāk: http://worldslargestlesson.globalgoals.org/
Latvijā: www.skolas.unesco.lv
Students went on a hiking trip along the Gauja River where they learned about water recycling from a visiting company and how water treatment equipment works. They conducted experiments with water and wrote advertisements about water before and after learning from an expert about the different types of water available for purchase. The goal was to teach the students about the importance of water and how to save the planet's water resources through different educational activities.
The document discusses the importance of living a healthy lifestyle through spending time in nature, eating honey and other natural foods, and engaging in sports and physical activity outdoors. It describes an outing by an environment committee where they learned nature can help with wellness, and how they later had a sports day competition where they won a running event. The overall message is that being close to nature and active can contribute to a healthy life.
The document summarizes educational activities that a class participated in to learn about forests. The class watched presentations about forest development and biotopes. They played a tree identification game and made sticker albums and herbariums of tree samples. Students observed tree buds, bark, and anthills under magnifying glasses. They identified birds by song and drew pictures of them. Boys made bird houses. The class read folk songs and riddles about forests and tasted birch and maple sap. They had a cross-country run in a nearby forest and do spring cleaning in their school yard. In May there is a creative competition about forests where students make posters, pictures, and tales or collages using forest materials. The overall goal is for the
4. Pazemes ūdeņi Pazemes ūdeņi ir Zemes garozas iežu porās, plaisās un tukšumos uzkrājies ūdens šķidrā vai gāzveida stāvoklī. Kopā ar virszemes ūdeņiem tie ir būtiska Zemes hidrosfēras daļa un piedalās ūdens aprites ciklā.
5. Iztvaikošana Iztvaikošana ir fāžu pāreja, kurā viela no šķidra vai cieta stāvokļa pāriet gāzveida stāvoklī. Ūdens iztvaiko gan n o ūdenstilpnēm, gan no augiem.
6. Kondensēšanās Ūdens tvaikiem atdziestot, tie no gāzveida stāvokļa pāriet šķidrā. Uz zemes ūdens kondensēšanos mēs varam novērot kā miglu , rasu , ziemā – sarmu . Ūdenim kondensējoties atmosfēras augšējos slāņos, rodas nokrišņi .
7.
8. Sniegs Sniegs ir cieto atmosfēras nokrišņu veids. Tas veidojas mikroskopiskiem ūdens pilieniem, zemā temperatūrā kristalizējoties un augot simetriskās, starainu zvaigznīšu formās. Parasti sniegs veidojas, kad gaisa temperatūra ir tuvu 0 °C vai zem tās.
9. Krusa Krusa ir nokrišņi, kas parasti ir novērojami siltajā gadalaikā no gubu lietus mākoņiem kopā ar lietus lāsēm. Krusa veidojas mākoņu iekšienē, kur ir ļoti daudz ūdens pilieniņu un kur valda zema temperatūra ūdens pilieni sasalst ledus kristāliņos. Vairākiem ledus kristāliem sasalstot kopā, veidojas dažādas formas un lieluma krusas graudi.
10. Lietus Lietu veido ūdens pilieni, kas rodas mākoņos un smaguma spēka ietekmē krīt lejup. Krītot pilieni savā starpā savienojas, veidojot lietus lāses. Vienlaikus notiek arī lielo lietus lāšu dalīšanās.
11. Liela loma ir arī pilienu elektriskajam lādiņam. Vienādi uzlādēti pilieni atgrūžas, bet dažādi uzlādēti vai dipolāri pilieni - pievelkas. Dipolāri pilieni var izraisīt elektrisku izlādi, jeb zibeni.
12. Lai uz māju jumtiem nekrātos ūdens, tie tiek aprīkoti ar noteknēm. Tas ir skaidrs ikvienam, arī cilvēkiem, kas nav būvniecības speciālisti. Taču par to, kur ūdens nokļūs tālāk, māju saimnieki aizdomājas samērā reti.
13. Lietus laikā, kā arī pavasaros, kūstot sniegam, rodas ūdens, kas ne tikai bojā ēku pamatus, ceļu segumus un augsnes kvalitāti, bet var kavēt vai pat uz laiku apturēt pilsētas ikdienas dzīves ritmu.
14. Dabīgā ceļā šiem ūdeņiem būtu jāiesūcas zemē, bet pilsētās tas nav iespējams.
15. Tieši tādēļ tiek izveidotas lietus ūdens kanalizācijas sistēmas.
21. Teritorijās, kur nokrišņu ūdens var saturēt industriāla rakstura piemaisījumus, pirms to novadīšanas lietus ūdens kanalizācijā, tiek uzstādīti eļļas/ūdens seperatori.
22. Eļļas/ūdens separatori ir speciālas tvertnes, kas konstruētas, lai atdalītu brīvās tauku, eļļas un nogulsnējošās cietās daļiņas no ūdens. Pēc separācijas tīrais ūdens tiek ievadīts lietus ūdeņu kanalizācijā, bet uztvertie tauki tiek aizturēti tvertnē un vēlāk droši utilizēti.
23. Nereti, redzot ūdenstilpnēs ieplūstam duļķainu ūdeni, cilvēki nodomā, ka tur tiek novadīts neattīrīts kanalizācijas ūdens. Bet patiesībā tas ir nokrišņu ūdens, kas atsevišķos gadījumos var saturēt smilšu daļas.
26. Lai cilvēks varētu apmierināt savas pamatvajadzības, ik dienas ir vajadzīgs vismaz 20 līdz 50 litri tīra ūdens. Bet mūsdienu prasības pēc komforta ikdienas patērējamā ūdens apjomu ievērojami palielina.
27.
28. Tātad: 4 personas mājsaimniecībā patērē līdz 600 l vērtīgā dzeramā ūdens (50 spaiņu), lielāko daļu – nelietderīgi...
