Paris, There are of course many software engineering texts that deal with the general gist of the topics below, describing many philosophies on how to organize a software project end-to-end. This includes product design all the way through to release and how all key teams (often product management, engineering, QA, build/release) interact to develop the product.
That said, the interesting point you bring up is the issue of "how to organize a team based on the architecture". I have not seen this specifically addressed, and it certainly is relevant. Having worked on engineering teams for web-based and non-web-based applications, different roles were necessary to fit the different technical requirements. A simple example is a Network Operations Center whose duty is to make sure the web servers hosting web-based-app's is up 24/7. A non-web-based-application obviously need not require such a department. The other key point is the documentation based on "design patterns". While the "general gist" of the topics is addressed in standard texts, with potentially the exception of "how to organize a team", they do lack the benefits of writing them in the style of design patterns. They are worthy of design patterns as they are solutions that have evolved over time and to a large extent tried-and-true with plenty of organizations following them to a tee. However, they aren't written in a design pattern style; e.g. they lack a) the specific types of problems the solutions address (i.e. what architecture/software type is this software engineering lifecycle paradigm good for?), b) often lack instances of use, c) lack the explicit relationship to other lifecycle variants, etc. etc. --Chris. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Paris > Avgeriou > Sent: Wednesday, February 25, 2004 3:30 AM > To: [EMAIL PROTECTED] > Subject: [patterns-discussion] patterns for architecture-centric > software development > > > Dear all, > > are you aware of any patterns that deal with architecture-centric > software development? For example patterns that deal with documenting > the software architecture (e.g. by identifying stakeholders, by > selecting multiple viewpoints and views, by choosing notations and > languages, by reverse-engineering existing system). Or even > organizational patterns that deal with how to organize your team > according to the architecture. > Please do not confuse these with architectural patterns such > as the POSA > patterns! > Thank you in advance, > > Paris > > -- > -------------------------------------------------------------- > ---------------- > > Paris Avgeriou, Ph.D. > Software Engineering Competence Center (SE2C), University of > Luxembourg, > Faculty of Science, Technology and Communication, > 6, rue Richard Coudenhove-Kalergi L-1359 > Luxembourg-Kirchberg, LUXEMBOURG. > > Tel: +352 420101 278 [EMAIL PROTECTED] http://hera.ist.lu > Fax: +352 43 21 24 http://fidji.ist.lu/pages/avgeriou/ > -------------------------------------------------------------- > ---------------- > > > _______________________________________________ > patterns-discussion mailing list > [EMAIL PROTECTED] > http://mail.cs.uiuc.edu/mailman/listinfo/patterns-discussion > > _______________________________________________ patterns-discussion mailing list [EMAIL PROTECTED] http://mail.cs.uiuc.edu/mailman/listinfo/patterns-discussion
