However I don't think this is the key point about agile
methods. Lack of documentation is a symptom of two much deeper
differences:
Agile methods are adaptive rather than predictive.
Engineering methods tend to try to plan out a large part of the software
process in great detail for a long span of time, this works well until
things change. So their nature is to resist change. The agile methods,
however, welcome change. They try to be processes that adapt and
thrive on change, even to the point of changing themselves.
Agile methods are people-oriented rather than
process-oriented. The goal of engineering methods is to define a
process that will work well whoever happens to be using it. Agile
methods assert that no process will ever make up the skill of the
development team, so the role of a process is to support the
development team in their work.In the following sections I'll explore these differences in
more detail, so that you can understand what an adaptive and
people-centered process is like, its benefits and drawbacks, and
whether it's something you should use: either as a developer or
customer of software.
The "International Journal of Critical Computer-Based Systems" (IJCCBS) is a quarterly research journal by Inderscience Publishers. It focuses on engineering and verification of complex computer-based systems (where complex means large, distributed and heterogeneous) in critical applications, with special emphasis on model-based approaches and industrial case-studies. Critical computer-based systems include real-time control, fly/brake-by-wire, on-line transactional and web servers, biomedical apparels, networked devices for telecommunications, environmental monitoring, infrastructure protection, etc.
A cogent analysis of the underlying complexity of software engineering. Each problem is new; software is the most complex thing humans have ever built; it is impossible to measure complexity of something given that product. Software is fractal in complexity (really?)
Open CASCADE Technology is software development platform freely available in open source. It includes components for 3D surface and solid modeling, visualization, data exchange and rapid application development.
The aim of the cooperative research project SoftWiki is to support the collaboration of all stakeholders in software development processes in particular with respect to software requirements.
S. Vahidnia, Ö. Tanrıöver, and I. Askerzade3. International Journal of Computer Science & Information Technology (IJCSIT), 8 (6):
01 - 13(December 2016)