Social Arithmetic by Ogi Gumelar In market activity there are salesperson (merchant) and customer (buyer), in this situation salesperson give merchandise to customer as money replacement beside that customer provide money as merchandise replacement. Sales get all merchandise from wholesaler or factory buy with the price which determined by them, or called buying price. Selling price is a price determined by sales which sold out to customer. We can conclude that from the passage market activity always related with buying price or capital, this price will become basic calculation. There are two possibilities condition in market activity 1. Sales will get profit condition, or 2. Sales will get loss condition Basic rule condition equal selling price is subtracted by buying price, if condition result is positive then sales get profit in contrary if condition result negative then sales get loss. Profit A condition where sales will get profit if selling price higher than buying price. For example case There is a salesperson buy a racket with price Rp 160,000.00 and then he sell the racket with price Rp 200,000.00, from this transaction we can conclude sales do get profit for about Rp 40,000.00 due to selling price is higher than buying price. We can derive profit from the difference (deduction) between selling price and buying price: Rp 200,000.00 subtract with Rp 160,000.00 equal Rp 40,000.00. Loss A condition where sales will get loss if buying price higher than selling price. For example Mr. Mamat buy an old television with price Rp 250,000.00 after that he repair the television with cost Rp 65,000.00 but he sell the television with price Rp 300,000.00. Reparation cost and buying price will be accumulated and equal as Rp 315,000.00, where capital is Rp 250,000.00 and addition cost is Rp 65,000.00. From this case we can summarize that Mr Mamat get loss for about Rp 15,000.00. Determining loss or profit percentage In market activity loss or profit is always represented in percentage, following statement is casual condition which describe amount of percentage: 5% = 5 /100 = 1/20 = 0.05 10% = 10/100=1/10=0.01 Discount Discount is a price allowance (deduction from the price amount), discount usually use as a tool to attract customer. For example there is a sale in a store with discount from 10 % up to 50 % such that there will be a lot of customer who come to this store due to the price is cheaper than other store. Gross, Net and Tare Gross is whole or total not net Net is free from any deduction Tare is deduction Inside a box which contain sugar has total weigh for about 100 kg, if that box weigh itself for about 0.8 kg then sugar will have weigh 99.2 kg from 100 kg subtract 0.8 kg. In this case we can summarize that: Gross weigh is a total weigh 100 kg Net weigh is only sugar weigh 99.2 kg Tare weigh is a box weigh 0.8 kg Interest If we have some money then we usually will save our money in Bank account, Bank also will provide us money as a feed back. The money is called interest. Tax Tax is a routine charge that has to paid by community in one country according its’ policies without any feed back, and the tax itself usually provide public prosperity. For example PPh (Pajak Penghasilan) where collected from salary employee allowance PPn (Pajak Pertambahan Nilai) where collected from any transaction in store, wholesaler and dealer.
by ogi gumelar
Saturday, March 29, 2008
Software engineering in Indonesia language (BAHASA)
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
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
Multiresolution-Based Image Fusion
Abstract— The standard data fusion methods may not be
satisfactory to merge a high-resolution panchromatic image and
a low-resolution multispectral image because they can distort the
spectral characteristics of the multispectral data. In this paper,
we developed a technique, based on multiresolution wavelet
decomposition, for the merging and data fusion of such images.
The method presented here consists of adding the wavelet
coefficients of the high-resolution image to the multispectral (lowresolution)
data. We have studied several possibilities concluding
that the method which produces the best results consists in
adding the high order coefficients of the wavelet transform of
the panchromatic image to the intensity component of the multispectral image. The method is, thus, an
improvement on standard intensity-hue-saturation (IHS or LHS)
mergers. We used the “`a trous” algorithm which allows to use a
dyadic wavelet to merge nondyadic data in a simple and efficient
scheme. We used the method to merge SPOT and LANDSAT
(TM) images. The technique presented is clearly better than the
IHS and LHS mergers in preserving both spectral and spatial
information.
By:Jorge N´u˜nez, Xavier Otazu, Octavi Fors, Albert Prades, Vicen¸c Pal`a, and Rom´an Arbiol
satisfactory to merge a high-resolution panchromatic image and
a low-resolution multispectral image because they can distort the
spectral characteristics of the multispectral data. In this paper,
we developed a technique, based on multiresolution wavelet
decomposition, for the merging and data fusion of such images.
The method presented here consists of adding the wavelet
coefficients of the high-resolution image to the multispectral (lowresolution)
data. We have studied several possibilities concluding
that the method which produces the best results consists in
adding the high order coefficients of the wavelet transform of
the panchromatic image to the intensity component of the multispectral image. The method is, thus, an
improvement on standard intensity-hue-saturation (IHS or LHS)
mergers. We used the “`a trous” algorithm which allows to use a
dyadic wavelet to merge nondyadic data in a simple and efficient
scheme. We used the method to merge SPOT and LANDSAT
(TM) images. The technique presented is clearly better than the
IHS and LHS mergers in preserving both spectral and spatial
information.
By:Jorge N´u˜nez, Xavier Otazu, Octavi Fors, Albert Prades, Vicen¸c Pal`a, and Rom´an Arbiol
landsat example
This is the example of landsat (land satelite) image or you can download other images in landsat.org or you can see in indonesias' satelite in www.lapanrs.com
classification in image processing
I just want review about classification in image processing, in general classification divide into two types, unsupervised classification and supervised classification. The purpose of classification is to clusterize or groupping some image data into specified class. For unsupervised classification usually i use isoclass method rather than k means, you can use er mapper, envi or ilwis to do this procces. Also for supervised classification i used maximum likelihood.
Continue to other post
Continue to other post
Subscribe to:
Posts (Atom)