Ezgi UĞUR - 030060195 3rd Week

Computer-Aided Sorfware Engineering (CASE)

Computer-aided sorfware engineering (CASE) encompasses computer-based procedures, techniques, and tools which can be used to develop, maintain, and reengineer software. CASE is to the sorfware engineer as computer-aided design/computer aided manufacturing (CAD/CAM) (4. v.) is to the mechanical engineer and computer-aided electrical engineering (CAEE) is to the electrical engineer. Although the variety of technological alternatives can be bewildering, the concepts of CASE provide a commonsense approach to engineering quality software more productively.

The application of CASE is intended to allow teams of software engineers to produce softwarethat:

* meets business and system requirements

* is completed within a predictable Schedule

* is available within budget guidelines

* allows for easy maintenance and enhancement

(David Sharon, Computer Aided Software Engineering, p. 278)

Parameter Data Section (PD)

An IGES file consist of five sections which must appear in the following order: start section, global section, directory entry (DE) section, parameter data (PD) section, and terminate section.

The PD section contains the actual data defining each entity listed in the DE section. For example, a straight line entity is defined by the six coordinates of its two endpoints. While each entity is always two records in the DE section, the number of records required for each entity in the PD section varies from one entity to another (the minimum is one record) and depends on the amount of data. Parameter data are placed in free format in columns 1 through 64. The parameter delimiter (usually a comma) is used to separate the list of parameters. Both delimiters are specified in the global section of the IGES file. Column 65 is left blank. Columns 66 through 72 on all PD records contain the entity pointer specified in the first record of the entity in the DE section.

(Emad Abouel Nasr, Ali K. Kamrani, Computer-Based Design and Manufacturing, pp. 127-129)

Shortest Processing Time (SPT)

In single-machine scheduling problem, sequencing the jobs in increasing order of processing time is known as shortest processing time (SPT) sequencing. In single-machine scheduling, sometimes we may be interested in minimizing the time spent by jobs in the system. This in turn will minimize in process inventory. Also, we may be interested in rapid turnaround/throughput times of the jobs. The time spent by job in the system is nothing but its flow time and the “rapid turnaround time” is the mean flow time of the jobs in the system. Shortest processing time (SPT) rule minimizes the mean flow time.

(R. Panneerselvam, Operations Research, Second Edition, p. 496)

Jikoda

Jikoda is the ability to stop production due to a problem. Production may be stopped automatically by a machine or by on operator (Levinson, 2002). The idea here is that a quality issues should be fixed right away, at the source of the problem. Traditional manufacturing systems, which emphasize production over quality, allow the defect to work its way down the system. This allows the defect to "grow" and end up being a more expensive tix. At the same time because the defect is caught so far down stream, often the root cause is not identified and corrected. Jikoda utilizes the machine operator to identify quality concerns and correct them right away. It is critical that the operator has the authority and responsibility to stop the process and fix the error.

(Christian Gausman, Implementing Lean Manufacturing and Design for Manufacturing Concepts in a Job Shop Manufacturing Environment, pp. 17-18)