A7Hiphoppipotimi

A7Hiphoppipotimi

To-Do

• describe the most important themes from the lectures for your project
• describe important themes for your project that are not discussed in any of the course lectures

describe the most important themes from the lectures for your project

The lecture on Design Methodologies sparked our interest in the various levels of community involvement. Specifically, Meta Deign introduced us to the idea of the seed evolution reseed (SER) concept. This is a good framework for model democratic design. The idea of free expansion is very important. When it comes to model authoritative design, the lecture on SmartGrids exemplified how a company monitor energy flow. On the other hand, the companies are open to receiving feedback from users. When introduced to Cultures of Participation, we were first exposed to the funnel effect and the distinction between consumer cultures and cultures of participation. During the Distributed Cognition lecture, it was shown how model democratic design can benefit from role distribution and communities of shared knowledge (including the symmetry of ignorance!). In the Less is More lecture, the discussion of a SER model vs. high functionality applications seemed to parallel our discussion of model democratic vs. model authoritative.  Finally, the introduction of Richer Ecologies of Participation in class sparked our interest in researching when boundaries are not clear cut between consumers, active consumers, and lead users. Building from our existing knowledge from class, we are eager to discover more on the distinction between model authoritative and model democratic design.

describe important themes for your project that are not discussed in any of the course lectures

Some of the important themes that aren't discussed in the course lectures are real world applications and the continuing adaptation of the technology. Obviously there are examples, but the main focus of this project is to take the theoretical and apply it to a real world framework, thus creating new theories that can be put into practice. This is one of the most important themes, and really an extension of the course, in that we have to go out into the real world and apply our theoretical knowledge. But isn't that what college is all about?

Several different software engineering processes could have different strengths and weaknesses when applied to model authoritative or model democratic development. While the principles of extreme programming, Agile, and SCRUM may be better suited to a model democratic goal, Crystla, Lean, Kanban, and Waterfall have aspects that are better suited to model authoritative. The idea of software quality ties into all of these development methodologies, and especially in a setting where one is aiming for a SER model, building in quality to one's software is a must. One must also favor prevention over inspection in testing and one must utilize continuous integration with a stop-the-line mentality. This will make one's users more apt to contribute to a model democratic view, but may be slightly less important in developing high functionality applications. The possibilities of a model democratic project only became possible after the internet expanded its functionality from document management to applications. The parallel development of CGI, CSS, and database websites that utilize higher level languages like Ruby on Rails, Perl, Python, or Java mimics the possibilities for developing model democratic software on the web.