:جديد المواضيع
صفحة 14 من 57 الأولىالأولى ... 410111213141516171824 ... الأخيرةالأخيرة
النتائج 131 إلى 140 من 568

......دورة هندسة البرمجيات......

  1. #131
    عضو فعال

    User Info Menu

    حسبى الله ونعم الوكيل bito


    0 Not allowed!

  2. #132
    عضو فعال

    User Info Menu

    I Tha
    Nk U For This Subject


    0 Not allowed!

  3. #133
    عضو فعال

    User Info Menu

    موضوع مميز ومفيد وفق الله الجميع ...أرجو من الله ان يوفق القائمين على هذا العمل الرائع لخدمة المسلمين فأرجو من القائمين على هذا العمل العظيم الاستمرار بدعمه بكل ما هو جديد ومفيد


    0 Not allowed!

  4. #134
    عضو فعال

    User Info Menu

    جزاكم الله خيرا وجعله في ميزان حسناتك أرجو من الله ان يوفق القائمين على هذا العمل العظيم الاستمرار بدعمه بكل ما هو جدي


    0 Not allowed!

  5. #135
    عضو فعال

    User Info Menu

    This Subect Is Too Intersting For Peaple And I Invite God To Help U For Helping Us


    0 Not allowed!

  6. #136
    عضو

    User Info Menu

    افيدونا بهذه الدروس جزاكم الله خيرا
    agaaaas***********


    0 Not allowed!

  7. #137
    مشرف سابق

    User Info Menu

    Lightbulb

    S/W ORGANIZATION PROCESSES

    Definition:-

    The purpose of Organization Process Definition is to develop and maintain a usable set of software process assets that improve process performance across the projects and provide a basis for cumulative, long-term benefits to the organization.
    Organization Process Definition involves developing and maintaining the organization's standard software process, along with related process assets, such as descriptions of software life cycles, process tailoring guidelines and criteria, the organization's software process database, and a library of software process-related documentation.

    These assets may be collected in many ways, depending on the organization's implementation of Organization Process Definition. For example, the descriptions of the software life cycles may be an integral part of the organization's standard software process or parts of the library of software process-related documentation may be stored in the organization's software process database.

    The organization's software process assets are available for use in developing, implementing, and maintaining the projects' defined software processes. (The practices related to the development and maintenance of the project's defined software process are described in the Integrated Software Management key process area.)

    Goals:-

    1-A standard software process for the organization is developed and maintained.

    2-Information related to the use of the organization's standard software process by the software projects is collected, reviewed, and made available.

    $$ The organization follows a written policy for developing and maintaining a standard software process and related process assets. $$

    The organization's software process assets include:-

    1-the organization's standard software process.
    2-guidelines and criteria for the projects' tailoring of the organization's standard software process.
    3-descriptions of software life cycles approved for use.
    4- the organization's software process database, and
    a library of software process-related documentation previously developed and available for reuse.

    This policy typically specifies that:-

    1-A standard software process is defined for the organization.

    The primary purposes of a standard software process are to maximize the sharing of process assets and experiences across the projects and to provide the ability to define and aggregate a standard set of process measurements from the projects at the organization level.

    The organization's standard software process may contain multiple software processes. Multiple software processes may be needed to address the needs of different applications, life cycles, methodologies, and tools, which the software projects may compose in multiple ways.

    2-A project's defined software process is a tailored version of the organization's standard software process.

    Refer to Activity 1 of the Integrated Software Management key process area for practices covering tailoring of the organization's standard software process.

    3-The organization's software process assets are maintained.
    4-Information collected from the projects is organized and used to improve the organization's standard software process.

    Examples of collected information include:-

    1-process and product measurements.
    2-lessons learned.
    3-other process-related documentation.



    0 Not allowed!
    التعديل الأخير تم بواسطة المهندس المسلم. ; 2006-06-20 الساعة 09:55 PM

  8. #138
    مشرف سابق

    User Info Menu

    Lightbulb

    $$ The organization's standard software process is developed and maintained according to a documented procedure. $$

    This procedure typically specifies that:-

    1-The organization's standard software process satisfies the software policies, process standards, and product standards imposed on the organization, as appropriate.

    2-The organization's standard software process satisfies the software process and product standards that are commonly imposed on the organization's projects by their customers, as appropriate.

    3-State-of-the-practice software engineering tools and methods are incorporated into the organization's standard software process, as appropriate.

    4-The internal process interfaces between the software disciplines are described.

    Examples of software engineering disciplines include:-

    1-software requirements analysis.
    2-software design.
    3-coding.
    4-software testing.
    5-software configuration management.
    6-software quality assurance.

    5-The external process interfaces between the software process and the processes of other affected groups are described.

    Examples of other affected groups include:-

    1-system engineering.
    2-system test.
    3-contract management.
    4-documentation support.

    6-Changes proposed for the organization's standard software process are documented, reviewed, and approved by the group responsible for the organization's software process activities (e.g., software engineering process group) before they are incorporated.

    Examples of sources for change include:-

    1-the findings and recommendations of software process assessments.
    2-results of the project's tailoring of the organization's standard software process.
    3-lessons learned from monitoring the organization's and projects' software process activities.
    4-changes proposed by the organization's staff and managers.
    5-process and product measurement data that are analyzed and interpreted.

    7-Plans for introducing changes to the software process of ongoing projects are defined as appropriate.

    8-The description of the organization's standard software process undergoes peer review when initially developed and whenever significant changes or additions are made.

    Refer to the Peer Reviews key process area.

    9-The description of the organization's standard software process is placed under configuration management.

    Refer to the Software Configuration Management key process area.



    0 Not allowed!
    التعديل الأخير تم بواسطة المهندس المسلم. ; 2006-06-20 الساعة 10:04 PM

  9. #139
    مشرف سابق

    User Info Menu

    Lightbulb

    $$ The organization's standard software process is documented according to established organization standards. $$

    These standards typically specify that:-

    1-The process is decomposed into constituent process elements to the granularity needed to understand and describe the process.

    Each process element covers a well-defined, bounded, closely related set of activities.

    Examples of process elements include:-

    1-software estimating element.
    2-software design element.
    3-coding element.
    4-peer review element.

    The descriptions of the process elements may be templates to be filled in, fragments to be completed, abstractions to be refined, or complete descriptions to be modified or used unmodified.

    Each process element is described and addresses:-

    1-the required procedures, practices, methods, and technologies.
    2-the applicable process and product standards.
    3-the responsibilities for implementing the process.
    4-the required tools and resources.
    5-inputs.
    6-the software work products produced.
    7-the software work products that should undergo peer review.
    8-the readiness and completion criteria.
    9-the product and process data to be collected.

    The relationships of the process elements are described and address:-

    1-the ordering.
    2-the interfaces.
    3-the interdependencies.



    0 Not allowed!

  10. #140

الكلمات الدلالية لهذا الموضوع

ضوابط المشاركة

  • لا تستطيع إضافة مواضيع جديدة
  • لا تستطيع الرد على المواضيع
  • لا تستطيع إرفاق ملفات
  • لا تستطيع تعديل مشاركاتك
  •