|
Index |
|
|
| Goal of the site | ||
| Why the name Processwave? | ||
| How to navigate the site | ||
| No Taking sides | ||
| Update hourly concept | ||
| Location | ||
| Goal of the site | ||
| The primary
goal is to offer a place for Software
Process Engineers (Architects of the development
process) to obtain and offer ideas about
the role of software Process
Engineering. What works and what doesn't. Its
also to share the software development process
and how to apply it to teams in general. UML and
modeling are a large part of this sites interest, but we try and cover all the
disciplines, wherever we find useful information. The site's aim is also to form a central collection point of relevant information about this emergent role of Process Engineering in teams doing software development. A place where useful material can be found by all people of all disciplines, both practical and theoretical, where newcomers to process can get help to get started or more experienced Process Engineers can benefit from others experience. A central junction to all things software process and software process related. |
||
| Why the name Process Wave? | ||
| Process Engineering as a role in the
software context is relatively new when compared to how long software
development and programming has been around. Its always been done but usually by
Architects, Project Managers and others as a background task to their primary
role. Software Development is still trying really hard to get out of the cottage
industry stage of its evolution! People have now realised that the process of
development is where many of the problems are being encountered and in some
cases solved. Hence a more formal approach to the role. Everything in life, and not least the software industry, happens in cycles. So "Process" is the context of the subject under discussion and its "Wave" is now gaining momentum. This wave will have its time, allow us to drastically enhance the way we work, and then give way to further realisations. ProcessWave.net is where you can find out information on these topics. |
||
| How to navigate the site | ||
There are four main sources of information on this site:
The Links section on the left will take you to a main page of link categories. The categories are roughly defined by the Unified Process disciplines as well as externally related or associated categories. This is simply a set of pointers to sites which contain a whole host of interesting content for you to browse.
The Articles section on the left has a similar structure to the links section, but the main difference here is that it takes you to individual articles we have found to be useful and relevant.
The Essays section is a collection of writings and publications generated by our own team of people.
Downloads is envisaged as a collection point for people willing to share their Artifacts such as Use Cases, Requirements Management plans, Configuration management plans, etc. This is so that people can get an idea how to do them by looking at real anonymous examples. This needs your help. Please donate artifacts to help others get up to speed and improve their development.
The rest is useful too:
The Glossary is mainly for definitions for our own publications, but can be used more generally too.
The Fun section is for a relaxing coffee break; to de-stress. Where you can laugh at the funny and silly parts of our industry.
Use the search facility to search for information and links on this site and the internet.
The feedback section is for just that. Send us stuff to publish, tell us to add your site offer comments on our publications. Help us improve the site.
We believe that there are good ideas and concepts in all the different software processes and methodologies. In lots of cases many of them can work together and complement each other. Each have their time and place for maximal benefit depending up on various factors. Software development is complex and dynamic. In time the individual concepts will all have their rightful place. This site will not take sides by process in the large, but explore the good in all concepts in the small.
The concept of this site is to use an iterative and incremental development paradigm. To all intents and purposes, all factors of this site both meta site content (design & structure) and site contents themselves are published on an hourly or daily basis, depending upon the level of activity and time available.
We are physically based in London UK, but the site tries to cater for all interested parties internationally.