Software Development Failures [Electronic resources] : Anatomy of Abandoned Projects نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Software Development Failures [Electronic resources] : Anatomy of Abandoned Projects - نسخه متنی

Kweku Ewusi-Mensah

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید







chapter 3, which is based on the impact the various factor categories have on the requirements, design, and implementation stages of the project development process. We limited the case analyses of the projects to determining how each stage of the development process was affected by the socioorganizational factors. The remaining two categories—technological and economic factors—will be analyzed in chapters 5 and 6, respectively.

In summary, we can affirm that the socioorganizational factors as a whole have a significant impact on the entire development life cycle because of the behavioral, political, and other organizational influences they exert on the systems development process. For example, the lack of clear project goals and objectives tends to frustrate efforts to develop the software. Requirements volatility contributes to abundant "redirections" of projects, adding inevitably to project costs and schedule delays and even threatening the overall quality of the software itself. However, realistically speaking, stable and unchanging requirements, though highly desirable, are unlikely in a typical systems development environment. Consequently, the strategy must strike a balance in controlling the extent of the changes to minimize the fluctuations in requirements and thus help to control the costs and other factors associated with the development process. Lack of senior management commitment and involvement also contributes to lack of focus and may adversely affect the morale and commitment of the project team. Finally, lack of user involvement may carry with it a number of deleterious effects, such as the failure of the team to understand and fully appreciate the users' problem domain, which may in the long run contribute to an erroneous set of requirements and other problems.

/ 92