I suggest you read this article in JOT.
The objectives of this paper are to clarify the terminology of software requirement models by suggesting a more consistent usage, to describe the different versions of requirement models, and to illustrate how to effectively address requirements analysis for large scale systems.

Quote:
Requirements are the things that you should discover before starting to build your product. Discovering the requirements during construction, or worse, when you client starts using your product, is so expensive and so inefficient, that we will assume that no right-thinking person would do it, and will not mention it again.
–Suzanne and James Robertson

In the wake of the recent PDC and TechEd developer events, Microsoft has decided to put some of its key executives out on the road to explain the innovations that Visual Studio 2010 and .NET 4.0 have in store.
Show related articles

Microsoft is promoting the next version of its Visual Studio toolset, code-named Rosario, as offering new levels of analysis of the application development process.
Reference: zdnet.co.uk

Quote:
A designer is an emerging synthesis of artist, inventor, mechanic, objective economist and evolutionary strategist. —R. Buckminster Fuller

خانم Rebecca Wirfs-brock نظرش را در مورد بازنگري معماري در مصاحبه‌اي با راديوي مهندسي نرم‌افزار ارائه كرده است. مصاحبه را مي‌توانيد در اينجا بشنويد.
جملات زير از ايشان نقل شده است كه نگراني‌اش را در مورد طراحي و كيفيت آن بيان نموده‌اند.

These days, complex IT systems are rarely understood by a single engineer or architect. Teams come together to create complex software systems. Technical challenges can be enormous and the “tricky bits” involve the subtle interplay of business and technical design decisions. The focus is on achieving overall business objectives, not the optimal design of a single component. Yet poorly designed interfaces, sluggishly performing services, or crappily constructed components can cause enormous grief. Design still matters.

Quote:
Software development has been, is, and will remain fundamentally hard.
Grady Booch

• Big systems are hard to get right. Thinking about “architecture stuff” up front is necessary for success.
• Architecture is the bearer of quality, but reasoning about architecture is actually reasoning about the potential of a system.
• Performance and flexibility really do trade off against each other.
• Reprioritizing architectural qualities is extremely risky.
• Don’t forget “saleability” and “marketecture.” They can help you sell a system to upper management before it is built, even if they offend a “pure” architecture sensibility.
• Autonomy of organizations and systems is paramount, and this autonomy happens to be the foundational principle of service-oriented architecture.
• If you don’t know where you’re going, you’re not going to get there—regardless of how good your map is.
• Technology doesn’t matter. What does matter are people, the process, and the consistency of practice.
• Architecture validation is critical but hard to institutionalize—even in a process-oriented organization.
• The deepest problems in IT are still communication and understanding.
• Don’t let “pragmatism” become a disguise for shortsightedness.

Reference:Lessons Learned about Software Architecture @ SEI
Quote:
“Architecture is not a set of PowerPoint slides, It’s the bridge between the business goals and the way a system operates.” Michael Gagliardi

مجله Reader’s Digest در شماره اخير خود، تحقيقي آماري انجام داده است با عنوان “آخرين باري كه به مادرتان زنگ زديد، كي بود؟”

با مراجعه به صفحه اصلي،مي‌توانيد جزئيات نتايج را مشاهده نماييد.

گزيده:
شعر مادر از ايرج ميرزا.

آدرس زیر شامل جدولی است برای مقایسه ابزارهای کمک مهندسی در حوزه مدیریت نیازمندی‌ها. در كنار ارائه‌ي داده‌هاي بسيار جالب،‌معيارهاي انتخاب شده براي مقايسه بسيار جالب و آموزنده است.

INCOSE Requirements Management Tools Survey

خوانندگاني كه با ابزار IBM Rational RequistePro كار مي‌كنند، مطلب زير مي‌تواند براي آنها مفيد باشد.

Evaluation of Rational RequisitePro as a General Artifact Manager

گزيده:
پسر به گورخر: تو سفیدی راه راه سیاه داری یا سیاهی راه راه سفید داری؟
گورخر به پسر: تو خوبی گاهی وقتا بدی، یا بدی گاهی خوب می‌شی؟…
نوشته شل سیلوراستاین
از دوست خوبم علي بابت اين يادداشت، سپاسگزارم.

You think it is a frog and I think it is a horse!

Wait for a while

Moral: We have to respect each other’s opinion; you can see it clearly in the above picture. We just need to wait and listen actively to others’ point of view!

مأخذ: از میان نامه‏های دوست خوبم، نوید.

گزیده:
ندارد.