“Architecture is [insert favorite technology here].”
“The network is the architecture. The database is the architecture. The transaction server is the architecture. The GUI is the architecture. CORBA is the architecture. This standard is the architecture…” This is a special case of the previous point. Yes, many of these aspects are part of the architecture, but the architecture cannot be restricted to one aspect only.
Architecture is more than just a “technology watch,” but I see many organizations in which the major role of the software architect seems to be experimenting with interesting new technologies. Often this is also the consequence of having architects who all come from one single specialty: for example, an architecture team comprised solely of data engineers. I was told recently: “We do not need anybody to work on architecture; our company has standardized on three-tier client-server architecture.”

Philippe Kruchten

گزیده:

The three most useless things to a project manager are: unnecessary product features, yesterday’s calendar, and “90% done” work.
John M. Nevison, 13 Risk Rules for New Project Managers

“Architecture is design.”
Yes, architecture is design. It is about making the difficult choices on how the system will be implemented. It is not just the “what.” But not all design is architecture.
Architecture is one aspect of the design, focusing on the major elements — the elements that are structurally important, but also those that have a more lasting impact on the performance, reliability, cost, and adaptability of the system. Architecting is choosing the small set of mechanisms, patterns, and styles that are going to permeate the rest of the design and give it its integrity. Architecture is the tool that allows us to master complexity. It cannot be the whole design. It has to limit itself to a certain level of abstraction but still be concrete enough to draw definite conclusions. It is not just “high-level design.”

What shall the architect focus on, then? There is no universal answer. For any given project, a decision needs to be made about what is architecturally significant so that we can draw that thin and elusive line between architecture and the rest of the design activities.

“Architecture is infrastructure.”
Yes, the infrastructure is an integral and important part of the architecture: It is the foundation. Choices of platform, operating systems, middleware, database, and so on, are major architectural choices.
But there is far more to architecture than just the infrastructure. The architects have to consider the whole system, including all applications; otherwise an overly narrow view of what architecture is may lead to a very nice infrastructure, but the wrong infrastructure for the problem at hand.
Time and time again, I run into this in organizations in which an architecture team is working solely on infrastructure, largely ignorant of the problem domain and the application software — which they consider to be outside of the architecture. “Oh, you mean the application. That’s what the people in the other building do.”

Philippe Kruchten

گزیده:

Projects aren’t dangerous. Risks are dangerous.
John M. Nevison, 13 Risk Rules for New Project Managers

Responsibility-Driven Design و به خصوص تکنیک CRC-Class Responsiblity Collaboration- یکی از ساده‏ترین تکنیکها و روشهای طراحی شیءگرای نرم‏افزار است.

مبدع آن، خانم Wirfs-Brock است. کتاب ایشان با نام Designing Object-Oriented Software منتشر شده به سال 1990، یکی از تأثیرگذارترین کتابهای حوزه طراحی شیءگرا بوده است.

در سایت شرکتشان در مورد ایشان آمده است:

Rebecca Wirfs-Brock, who founded Wirfs-Brock Associates in 1997, is an object technology innovator and pioneer. Having invented Responsibility-Driven Design while at Tektronix in 1990, she has pushed on “object thinking” for the past 15 years.

توصیه می‏کنم کتاب جدیدتر ایشان با نام Object Design: Roles, Responsibilities, and Collaborations را مطالعه کنید. همچنین بد نیست مصاحبه ایشان را در OOPSLA2007 را که بهانه نوشته این مطلب بود، در اینجا ببینید و بشنوید.

گزیده:

Never let a project go somewhere your plan didn’t go a month earlier.
John M. Nevison, 13 Risk Rules for New Project Managers

Over the last decade or two, a philosophy has developed as an undercurrent in the object community. The premise of domain-driven design is two-fold:

• For most software projects, the primary focus should be on the domain and domain logic; and
• Complex domain designs should be based on a model.

Domain-driven design is not a technology or a methodology. It is a way of thinking and a set of priorities, aimed at accelerating software projects that have to deal with complicated domains.

مرجع: http://www.domaindrivendesign.org/
گزیده:

Every project needs an ending, but not every project needs to be started.
John M. Nevison, 13 Risk Rules for New Project Managers

امروز نامه‏ای از دوست خوب و همکلاسی قدیمی‏ام، فرهاد داشتم راجع به جایزه سالانه “افشین جعفری مژدهی” برای بهترین مقاله دانشجویی در موضوع اقتصاد. آدرس ارسال شده را دنبال کردم و ….
روحش شاد. همکلاسی با معرفت، بمب خنده، باهوش و فعال در امور درسی و دانشجویی. با بیماری سختی دست به گریبان بود. آخرین باری که زنده بود، قرار بود در گردهمایی همکلاسی‏ها شرکت کند، که در آخرین لحظات نتوانست. چقدر حسرت خوردیم که ای کاش برای آخرین بار می‏آمد و ….

از بانیان این کار بزرگ، صمیمانه سپاسگذارم. حق یاورشان.

This webpage is dedicated to pay tribute to the memory of our dear friend, classmate and colleague, Afshin Jafari Mojdehi, who passed away on September, 10th 2003 after three years of courageous battle with Leukemia. He was 29 years old.

Afshin was a researcher and faculty member of IRPD (Institute for Research in Planning and Development) the pioneer center for research and graduate studies of economics in Iran. In IRPD he impressed senior faculty and graduate students with his passion and hard work. The students that attended Afshin’s classes enjoyed having an enthusiastic teacher willing to explore and discuss new horizons in economics theory and applications. In his short time as an economic researcher he participated in several research projects, which resulted in publishing a number of excellent reports and papers, his contribution to the quality of these articles was enormous. He was an extraordinary teacher and devoted researcher.

Afshin came from a small green city in north of Iran. He graduated from Sharif University in Tehran in class of 1997 (1376). He continued his graduate studies in IRPD, where he was invited to stay after graduation. He was a lovely young man, who in any occasion tried his best to make everybody around him happy, life was radiating from him. Decided not to share anything his illness with others, he didn’t mention it to anybody until his last weeks. So it became a shock for many to understand it later.

Now here we are, his friends and colleagues in Iran and abroad, making a pledge to prolong his devotion to the development of economic studies in Iran, in naming an annually award for the best graduate student paper in the field of economics. We know if he were here among us, he would be the most industrious one to pursue this contest, something he would have longed to do. And he is doing it right now, because he inspired many of us in many ways to like economics. To see the details about the prize visit Afshin Jafaris’s Prize Page.

گزیده:
ببار ای ابر بهار
ببار ای باران ببار
با دلم گریه کن خون ببار
دلم خون شد خون ببار
بر کوه و دشت و هامون ببار

به همگی دوستان عزیزم، سلام.

به قول مرحوم حاج قربان سلیمانی، استاد دو تار “گاهی دوتارم با من قهر می‏کند”. گاهی هر چه فکر می‏کنم، حرفی برای گفتم ندارم. انگار وبلاگم با من قهر می‏کند.

قالب جدید وبلاگ، هدیه دوست خوب و عزیزم، آقای علی اعرابی است. دستشان درد نکند. من که نمی‏توانم جبران زحمتشان را بنمایم، محبت و لطفشان که جای خود دارد.

اگر نظری دارید بفرمایید تا در نهایی‏کردن قالب وبلاگ در نظر گرفته شود.

گزیده:

دندون اسب پیش‏کش رو، در هنگام تحویل می‏شمارند.

خانم مهندس کراری در توضیحی برایم نوشته بودند:
“….ولی قکر میکنم اگر شرکتها و سازمانها به نیروی انسانی به اندازه کافی بها می دادند اوضاع سودآوری شون حتما بهتر از اینی که هست می شد و حداقل می دیدیم که آرزوی هر نیروی IT داشتن یک شرکت مستقل نبود! “

ضمن تشکر از ایشان، گفتم شاید بد نباشد که حکایت جالب زیر را در اینجا بیاورم. اعتقاد شخصی من این است که ما مثل دانه‏های زنجیر به هم متصل هستیم (به عبارت فنی یک سیستم هستیم) که نمی‏شود تنها بخشی از آن را بدون در نظر گرفتن سایر اجزایش مورد بررسی و تحلیل قرار داد.

اما حکایت:
شخصی تعریف می‏کرد که پروسه مصاحبه و ارزیابی برای استخدام در شرکتی (خارج از کشور)، مدت زیادی طول کشید و بعد از عبور از انواع و اقسام امتحانات و مصاحبه‏ها، اعلام کردند که نظر شرکت نسبت به جذب شما مثبت است و برای عقد قرارداد به شرکت مراجعه کنید.
آخرین شخصی که با من مصاحبه کرد، مدیر عامل شرکت بود. از وی پرسیدم که چرا پروسه استخدام به این سادگی، در اینجا این قدر طول کشیده است؟ وی در جواب گفت که ما افراد را برای یک عمر استخدام می‏کنیم و نه برای چند وقت. از این رو در استخدامشان بسیار دقت می‏کنیم و وسواس به خرج می‏دهیم.

گزیده:

There is always something for which to be thankful. —Charles Dickens