the most effective learning situation is one where a small number of apprentices work alongside an even smaller number of journeyman, who are receiving guidance from a master craftsman
Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems. Simply put, Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner. As you see in Figure 1 AM is meant to be tailored into other, full-fledged development methodologies such as XP or RUP, enabling you to develop a software process which truly meets your needs. The techniques of AM, in particular Agile Model Driven Development (AMDD), the lifecycle for which is depicted in Figure 2, enable you to scale agile software development to very complex situations.
Agile Development is one of the big buzzwords of the software development industry. But what exactly is it? Agile Development is a different way of managing software development projects. The key principles, and how Agile Development fundamentally differs from a more traditional Waterfall approach to software development, are as follows:
From the most interesting company in the IT area... "Continuous Integration, Source Control, a Wiki and a Bug-Tracker are all cornerstones of a functioning Agile development project. But if you've not configured them all before, it can be a bit tricky - a
Very interesting article, seems to be an extract of the author's book on rapid sw development from 1996 (sic). Many points (especially #4 e.g.) look quite familiar to me.
The concepts
The CodeCount toolset is a collection of tools designed to automate the collection of source code sizing information. The CodeCount toolset spans multiple programming languages and utilizes one of two possible Source Lines of Code (SLOC) definitions, physical or logical.
The CodeCount toolset is provided in source code only, and may be used as is, modified or further distributed subject to certain limitations.
The tools in the collection are supplied in C source code only. You are responsible for compiling and building executable versions.
The Product
The CodeCount toolset is copyright USC Center for Software Engineering but is made available with a Limited Public License which permits the distribution of the modifications you make provided you return a copy to us so we can further enhance the toolset for the benefit of all.
Joel on Software is a webpage of a NY sw developer, Joel Spolsky, which also has partially published in print. This page is the archive page with all the articles.
Crap4j is a Java implementation of the CRAP (Change Risk Analysis and Predictions) software metric – a mildly offensive metric name to help protect you from truly offensive code.
The CRAP metric combines cyclomatic complexity and code coverage from automated tests (e.g. JUnit tests) to help you identify code that might be particularly difficult to understand, test, or maintain – the kind of code that makes developers say: “This is crap!” or, if they are stuck maintaining it, “Oh, crap!”.
The best way to learn more about CRAP and Crap4j is to check the various articles, newsgroups and blogs about them.
"Relying on CVS and Subversion [...] with access controls limited to the select few committers makes it very difficult for those on the fringes to get more involved."
Europäische Geschichte Online (EGO) is an online European transcultural history composed of multimedia knowledge items encompassing the period from 1450 to 1950. EGO is methodologically pragmatic, international and interdisciplinary. It combines a variety of approaches and perspectives from debates in multiple languages and thus interlinks international scholars working in the various disciplines of European history.
Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I've found is: "Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.".
Joel on SW article, one argument is quite useful regarding the ongoing outsourcing discussion. Anyway, the most funny thing is, that Mozart did NOT write the whole Requiem, only Inroitus and Kyrie, the rest is Eybler and Süßmayr.
Towards understanding the complex interplay of software tools, human behaviour and social structures in order to enhance the development and use of software tools.
IceScrum is an J2EE application for using Scrum while keeping the spirit of a collaborative workspace. It also offers virtual boards with post-its for sprint backlog, product backlog and others.
The tool offers everything that is in Scrum :
*
The role management: Product Owner, ScrumMaster, Team member and StakeHolder
*
The product backlog management with advanced features for prioritizing stories
*
Scrum lifecycle including a roadmap view
*
Release planning
*
Sprint backlog, as a task board facilitating the Scrum ceremonial
*
Management of impediments
*
Chart production such as burndown charts, velocity charts, cumulative flow diagram
Icescrum offers others agile practices like :
* Roadmap
* Vision
* Features
* User stories
* Acceptance tests associated to stories
* User roles
* Planning poker
I find it useful to draw a contrast between two different organizational development styles: "process-oriented" and "commitment-oriented" development...
They offer xProcess, quite an extensible project/process/task/issue management tool that allows to define processes for project management etc. which can be used in real time.
Build. Test. Release.
Maestro - the powerful, open source-based solution stack from Mergere, brings best practices to build automation, eliminating most tedious interaction at runtime.
Based on the Apache Software Foundation's Maven, the Mergere's build platform frees developers to focus on writing applications, instead of writing build scripts. Maestro gives development teams the tools to automate, track, audit and analyze their application life cycle, to ensure that builds run from start to finish without issues -- shortening release time-lines, enhancing code quality, and enabling organizations to capture, maintain and reuse project knowledge.
methodische Lehrveranstaltungen verschiedener sozial- und wirtschaftswissenschaftlicher Fachbereiche an der Johannes Kepler Universität Linz in Form von Hypervideos, multimedialen Vortragsaufzeichnungen mit begleitenden online Kursmaterialien