5 framework activities, dalam software engineering (Rekayasa Perangkat Lunak)
Sebuah model spiral dibagi menjadi beberapa jumlah framework activities, yang juga disebut sebagai task region. Secara umum terdapat antara 3 sampai 6 task region. Gambar pada buku pressman menunjukkan sebuah model spiral yang berisi mengenai 6 task region.
Komunikasi pelanggan, tugas ini dibutuhkan untuk menciptakan komunikasi yang efektif antara developer dengan pelanggan
Perencanaan, tugas ini dibutuhkan untuk mendefinisikan resources, jadwal (timelines) dan proyek lainnya yang berkaitan dengan informasi.
Analisis Resiko, tugas ini dibutuhkan untuk mengassess resiko tekni dan resiko manajemen
Teknisi, tugas dibutuhkan untuk membangun satu atau lebih representasi dari aplikasi
Konstruksi dan release, tugas ini dibutuhkan untuk mengkonstruksikan , menguji, menginstall dan memberi pendukung untuk pengguna (misal, dokumentasi dan pelatihan)
Evaluasi Pengguna, tugas ini dibutuhkan untuk memperoleh masukan pelanggan yang berdasarkan evaluasi dari representasi perangkat lunak yang dibuat selama tahap teknis dan diimplementasikan selama tahap instalasi.
[PRE05, hal 36] Jawaban versi lain 1.2 Framework ActivitiesAn effective process model should define a small set of framework activities that are always applicable, regardless of project type. The APM defines the following set of framework activities:
• project definition - tasks required to establish effective communication between developer and customer(s) and to define requirements for the work to be performed
• planning - tasks required to define resources, timelines and other project related information and assess both technical and management risks
• engineering and construction - tasks required to create one or more representations of the software (can include the development of executable models, i.e., prototypes or simulations) and to generate code and conduct thorough testing
• release - tasks required to install the software in its target environment, and provide customer support (e.g., documentation and training)
• customer use - tasks required to obtain customer feedback based on use and evaluation of the deliverables produced during the release activity
Each of the above framework activities will occur for every project. However, the set of tasks (we call this a task set) that is defined for each framework activity will vary depending upon the project type (e.g., Concept Development Projects will have a different task set than Application Enhancement Projects) and the degree of rigor selected for the project.
http://www.rspa.com/apm/apm01.html
6 tingkatan dari SEI Capability Maturity Model Integration (CMMI)
Enam tingkatan dari Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI):
Tingkat 1 : Awal . Proses perangkat lunak dikarakteristikkan sebagai ad hoc dan kadang tidak dapat diprediksi. Beberapa proses didefinisikan dan keberhasilannya tergantung dari masing-masing proses.
Tingkat 2 : Pengulangan (Repeatable ).Proses manajemen proyek dasar dibuat untuk mengantisipasi biaya, jadwal dan kegunaan. Ilmu proses yang dibutuhkan adalah untuk mengulang keberhasilan lebih awal pada proyek dengan aplikasi yang serupa.
Tingkat 3 : Terdefinisikan. Proses perangkat lunak untuk kedua kegiatan dari manajemen dan teknik didokumentasikan , distandarisasikan dan di integrasikan menjadi proses perangkat lunak yang terorganisir secara luas. Semua proyek menggunakan versi yang telah didokumentasikan dan disetujui dari organisasi pengembang dan pendukung perangkat lunak. Tingkat ini mencakup semua karakteristik yang didefinisikan pada tingkat 2.
Tingkat 4 : Terorganisir (Managed). Ukuran yang terperinci dari proses dan produk perangkat lunak dikumpulkan. Proses dan produk perangkat lunak secara kuantitatif dipahami dan dikendalikan menggunakan ukuran terperinci. Tingkat ini mencakup semua karakteristik yang didefinisikan untuk tingkat 3.
Tingkat 5: Optimisasi. Proses pengembangan yang berkelanjutan diperbolehkan oleh umpan balik yang kuantitatif dari proses dan dari pengujian usulan dan teknologi yang inovatif. Tingkat ini mencakup semua karakteristik yang didefinisikan untuk tingkat 4.
[PRE05, hal 24-25] Versi lain jawaban kedua:
Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI)
Level 0: Incomplete (process is not performed or does not achieve all goals defined for
Level 1: Performed (work tasks required to produce required work products are being conducted)
Level 2: Managed (people doing work have access to adequate resources to get job done, stakeholders are actively involved, work tasks and products are monitored, reviewed, and evaluated for conformance to process description)
Level 3: Defined (management and engineering processes documented, standardized, and integrated into organization-wide software process)
Level 4: Quantitatively Managed (software process and products are quantitatively understood and controlled using detailed measures)
Level 5: Optimizing (continuous process improvement is enabled by quantitative feedback from the process and testing innovative ideas)
http://highered.mcgraw-hill.com/sites/0072853182/student_view0/chapter3/chapter_summary.html
Versi lain dengan penjelasan yang lebih lengkapCapability Level 0: Incomplete
An “incomplete process” is a process that either is not performed or partially performed. One or more of the specific goals of the process area are not satisfied, and no generic goals exist for this level since there is no reason to institutionalize a partially performed process.
Capability Level 1: Performed
A capability level 1 process is characterized as a “performed process.” A performed process is a process that satisfies the specific goals of the process area. It supports and enables the work needed to produce work products. Although capability level 1 results in important improvements, those improvements can be lost over time if they are not institutionalized. The application of institutionalization (the CMMI generic practices at capability levels 2 through 5) helps to ensure that improvements are maintained.
Capability Level 2: Managed
A capability level 2 process is characterized as a “managed process.” A managed process is a performed (capability level 1) process that has the basic infrastructure in place to support the process. It is planned and executed in accordance with policy; employs skilled people who have adequate resources to produce controlled outputs; involves relevant stakeholders; is monitored, controlled, and reviewed; and is evaluated for adherence to its process description. The process discipline reflected by capability level 2 helps to ensure that existing practices are retained during times of stress.
Capability Level 3: Defined
A capability level 3 process is characterized as a “defined process.” A defined process is a managed (capability level 2) process that is tailored from the organization’s set of standard processes according to the organization’s tailoring guidelines, and contributes work products, measures, and other process improvement information to the organizational process assets. A critical distinction between capability levels 2 and 3 is the scope of standards, process descriptions, and procedures. At capability level 2, the standards, process descriptions, and procedures may be quite different in each specific instance of the process (e.g., on a particular project). At capability level 3, the standards, process descriptions, and procedures for a project are tailored from the organization’s set of standard processes to suit a particular project or organizational unit and therefore are more consistent, except for the differences allowed by the tailoring guidelines. Another critical distinction is that at capability level 3, processes are typically described more rigorously than at capability level 2. A defined process clearly states the purpose, inputs, entry criteria, activities, roles, measures, verification steps, outputs, and exit criteria. At capability level 3, processes are managed more proactively using an understanding of the interrelationships of the process activities and detailed measures of the process, its work products, and its services.
Capability Level 4: Quantitatively Managed
A capability level 4 process is characterized as a “quantitatively managed process.” A quantitatively managed process is a defined (capability level 3) process that is controlled using statistical and other quantitative techniques. Quantitative objectives for quality and process performance are established and used as criteria in managing the process. Quality and process performance is understood in statistical terms and is managed throughout the life of the process.
Capability Level 5: Optimizing
A capability level 5 process is characterized as an “optimizing process.” An optimizing process is a quantitatively managed (capability level 4) process that is improved based on an understanding of the common causes of variation inherent in the process. The focus of an optimizing process is on continually improving the range of process performance through both incremental and innovative improvements. Remember that capability levels 2 through 5 use the same terms as generic goals 2 through 5.
http://www.sei.cmu.edu/pub/documents/06.reports/pdf/06tr008.pdf
BY OGI GUMELAR