Кіріспе
Бағдарламалық құралдар саласы. Компьютерлік көмекпен бағдарламалық жасақтама жасау (CASE) – қолданбаларды жобалау және іске асыру үшін қолданылатын бағдарламалық құралдар саласы. CASE құралдары аппараттық өнімдерді жобалау үшін пайдаланылатын компьютерлік көмекпен жобалау (CAD) құралдарымен ұқсас және ішінара шабыттанған. CASE құралдары жоғары сапалы, ақаусыз және қолдауға оңай бағдарламалық жасақтаманы жасауға көмектеседі. CASE бағдарламалық жасақтамасы жиі ақпараттық жүйелерді әзірлеу әдістерімен және бағдарламалық жасақтаманы әзірлеу процесінде қолданылатын автоматтандырылған құралдармен байланысты болды.
Computer aided software engineering (CASE) is a domain of software tools used to design and implement applications. CASE tools are similar to and are partly inspired by computer aided design (CAD) tools used for designing hardware products. CASE tools are intended to help develop high quality, defect free, and maintainable software. CASE software was often associated with methods for the development of information systems together with automated tools that could be used in the software development process.
Тарих
1968 жылы Мичиган университетінде басталған Ақпараттық жүйелерді жобалау және оңтайландыру жүйесі (ISDOS) жобасы, талдаушыларға талаптарды талдау және жүйелерді әзірлеудің өте қиын процесінде көмектесу үшін компьютерлік жүйелерді пайдалану тұжырымдамасына зор қызығушылық тудырды. Дэниел Тейхроудың бірнеше мақаласы автоматтандырылған жүйелерді дамыту мүмкіндігімен бірнеше буын энтузиасттарды шабыттандырды. Оның Проблемалық мәлімдеме тілі / Проблемалық мәлімдеме талдағышы (PSL/PSA) құралы CASE құралы болды, бірақ бұл термин пайда болғанға дейін жасалған. Тағы бір маңызды бағыт – деректер базасының дерек сөздігіне логикалық кеңейтім ретінде пайда болды. Метадеректердің ауқымын кеңейту арқылы қосымшаның атрибуттары сөздікке енгізіліп, орындалу кезінде қолданылуы мүмкін болды. Бұл «белсенді сөздік» қазіргі заманғы модельге негізделген инженерия мүмкіндіктерінің алға басушысы болды. Дегенмен, белсенді сөздік метадеректердің графикалық бейнеленуін қамтамады. Деректерді интеграцияланған әдістер жиынтығын қолдану арқылы алынған талдаушылардың метадеректерін сақтайтын сөздік тұжырымдамасымен, сондай-ақ мұндай деректердің графикалық бейнеленуінің үйлесімділігі CASE-тің алғашқы нұсқаларын тудырды. Нарыққа келесі кірген компания – Кембридждегі Index Technology компаниясының Excelerator құралы. DesignAid Convergent Technologies және кейіннен Burroughs Ngen желілік микрокомпьютерлерінде жұмыс істесе, Index IBM PC/AT платформасында Excelerator-ды іске қосты. Іске қосылған кезде және бірнеше жыл бойы IBM платформасы Convergent Technologies немесе Burroughs машиналары сияқты желілік қосылымдарды немесе орталықтандырылған деректер базасын қолдамаса да, IBM-нің тартымдылығы зор болды және Excelerator танымал болды. Excelerator-дың ізінен Knowledgeware (Джеймс Мартин, Фран Таркентон және Дон Аддингтон), Texas Instrument-тің CA Gen және Andersen Consulting-тің FOUNDATION құрал жиынтығы (DESIGN/1, INSTALL/1, FCP) сияқты компаниялардың ұсыныстары келді. CASE құралдары 1990 жылдардың басындағы ең жоғары деңгейіне жетті. 1990 жылғы қаңтардағы PC Magazine журналының мәліметтері бойынша 100-ден астам компания 200-ге жуық түрлі CASE құралдарын ұсынды. Мейнфреймнің құлдырауымен AD/Cycle және ірі CASE құралдары жойылды, бұл бүгінгі күнгі негізгі CASE құралдарының нарығын ашты. 1990 жылдардың басындағы CASE нарығының көптеген көшбасшылары Computer Associates компаниясымен сатып алынды, олар IEW, IEF, ADW, Cayenne және Learmonth & Burchett Management Systems (LBMS) компанияларын қамтыды. CASE құралдарының эволюциясына әкелген тағы бір тенденция – нысанға бағдарланған әдістер мен құралдардың пайда болуы болды. Көптеген құрал-саймандар өндірушілері нысанға бағдарланған әдістер мен құралдарды қолдауды қосты. Сонымен қатар, нысанға бағдарланған тәсілді қолдау үшін төменнен жоғарыға қарай жасалған жаңа өнімдер пайда болды. Andersen өзінің Foundation-ға балама ретінде Eagle жобасын жасады. Нысанға бағдарланған дамудағы бірнеше ой-пікір көшбасшылары әрқайсысы өз әдістемелерін және CASE құралдарын жасады: Джейкобсон, Румбо, Буч және т.б. Ақырында, бұл әртүрлі құралдар мен әдістер Object Management Group (OMG) бастаған стандарттар арқылы біріктірілді. OMG-нің Бірыңғай модельдеу тілі (UML) қазіргі уақытта нысанға бағдарланған модельдеудің өнеркәсіп стандарты ретінде кеңінен қабылданды.
Құралдар
CASE құралдары бағдарламалық жасақтаманы әзірлеу өмірлік циклындағы нақты міндеттерді қолдайды. Оларды келесі категорияларға бөлуге болады:
Бізнес және талдау модельдеуі: Графикалық модельдеу құралдары. Мысалы, Э/Р модельдеу, объектілік модельдеу және т.б.
Даму: Өмір циклінің жобалау және құрылыс кезеңдері. Ақауларды жою орталары. Мысалы, IISE LKO.
Тексеру және растау: Код пен ерекшеліктерді дұрыстығына, өнімділігіне және т.б. талдау.
Конфигурацияны басқару: Репозиторий нысандары мен файлдарды тексеру және шығаруды басқару. Мысалы, SCCS, IISE.
Метрикалар мен өлшеу: Кодты күрделілік, модулділік (мысалы, "goto" операторларының болмауы), өнімділік және т.б. бойынша талдау.
Жобаларды басқару: Жоба жоспарларын, тапсырмаларды, кестелеуді басқару.
CASE құралдарын ажыратудың тағы бір кең таралған тәсілі – Upper CASE және Lower CASE арасындағы айырмашылық. Upper CASE құралдары бизнес және талдау модельдеуін қолдайды. Олар ER диаграммалары, деректер ағыны диаграммалары, құрылымдық диаграммалар, шешім ағаштары, шешім кестелері және т.б. сияқты дәстүрлі диаграммалық тілдерді қолдайды. Lower CASE құралдары физикалық жобалау, жөндеу, құрылыс, сынау, компоненттерді интеграциялау, техникалық қызмет көрсету және кері инженерия сияқты даму шараларын қолдайды. Қалған барлық шаралар өмірлік цикл бойына созылады және Upper CASE және Lower CASE екеуіне де бірдей қолданылады.
Business and analysis modeling: Graphical modeling tools. E. g., E/R modeling, object modeling, etc. Development: Design and construction phases of the life cycle. Debugging environments. E. g., IISE LKO. Verification and validation: Analyze code and specifications for correctness, performance, etc. Configuration management: Control the check in and check out of repository objects and files. E. g., SCCS, IISE. Metrics and measurement: Analyze code for complexity, modularity (e. g., no "go to's"), performance, etc. Project management: Manage project plans, task assignments, scheduling. Another common way to distinguish CASE tools is the distinction between Upper CASE and Lower CASE. Upper CASE Tools support business and analysis modeling. They support traditional diagrammatic languages such as ER diagrams, Data flow diagram, Structure charts, Decision Trees, Decision tables, etc. Lower CASE Tools support development activities, such as physical design, debugging, construction, testing, component integration, maintenance, and reverse engineering. All other activities span the entire life cycle and apply equally to upper and lower CASE.
Қоршаған орта
Қоршаған орта — толық бағдарламалық жасақтама процесін қолдауға тырысатын CASE құралдары немесе жұмыс орталары жиынтығы. Бұл бір нақты тапсырмаға немесе өмірлік циклдің белгілі бір бөлігіне бағытталған құралдардан өзгеше. CASE орталары Fuggetta бойынша келесідей жіктеледі:
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Құрал жиынтығы: Бос байланысқан құралдар жиынтығы. Бұл жүйелер әдетте операциялық жүйе жұмыс орталарына, мысалы Unix Programmer's Workbench немесе VMS VAX жиынтығына негізделген. Олар әдетте деректерді алмасу және басқаруды жүзеге асыру үшін құбырлар немесе басқа қарапайым механизмдерді пайдаланады. Оңай интеграцияның артықшылығы бар болғанымен, ол кемшілік те болуы мүмкін. Shell скрипті сияқты технологиялар арқылы параметрлерді қарапайым түрде беру, жалпы репозиторий деректер базасының қамтамасыз ете алатын күрделі интеграцияны ұсына алмайды.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Төртінші буын: Бұл орталар 4GL деп те аталады, себебі алғашқы орталар Visual Basic сияқты нақты тілдерге негізделген. Олар бірнеше құралды терең интеграциялауды қамтамасыз еткен алғашқы орталар болды. Әдетте, бұл орталар нақты қосымша түрлеріне бағытталған. Мысалы, реляциялық деректер базасына стандартты атомдық операцияларды орындайтын пайдаланушы интерфейсімен басқарылатын қосымшалар. Мысалдар: Informix 4GL және Focus.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Тілге бағытталған: Символиктер Лисп Genera ортасы немесе Parcplace-тен VisualWorks Smalltalk сияқты бір, көбінесе объектіге бағытталған тілге негізделген орталар. Мұндай орталарда операциялық жүйенің барлық ресурстары объектіге бағытталған тілдегі объектілер болып табылады. Бұл қуатты түзету және графикалық мүмкіндіктерді ұсынады, бірақ әзірленген код көбінесе нақты тілмен шектеледі. Осы себепті бұл орталар CASE ішіндегі арнайы орынды иеленді. Олар көбінесе прототиптерді жасау және ғылыми-зерттеу жобалары үшін қолданылды. Бұл орталардың ортақ идеясы — модель-көрініс-бақылаушы пайдаланушы интерфейсі, ол бір дизайнның бірнеше нұсқаларын негізгі модельмен үйлесімді ұстауға мүмкіндік береді. MVC архитектурасы CASE орталарының басқа түрлерімен және олармен жасалған көптеген қосымшалармен қабылданып алынды.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Интеграцияланған: Бұл орталар — көптеген ИТ мамандары CASE туралы ойлағанда есімізге келетін нәрсе. IBM-нің AD/Cycle, Andersen Consulting-тің FOUNDATION, ICL CADES жүйесі және DEC Cohesion сияқты орталар. Бұл орталар талдаудан бастап техникалық қызмет көрсетуге дейінгі өмірлік циклды толық қамтуға тырысады және бағдарламалық жасақтама процесінің барлық артефакттарын сақтау үшін интеграцияланған деректер базасын ұсынады. Интеграцияланған бағдарламалық жасақтама репозиторийі — осы құралдардың ерекшелігі. Олар әртүрлі дизайн модельдерін, сондай-ақ гетерогенді тілдердегі кодты қолдайды. Бұл орталардың маңызды мақсаттарының бірі — «қайтару инженериясы»: дизайн деңгейінде өзгерістер енгізіп, оларды кодқа автоматты түрде көшіру және керісінше. Бұл орталар, әдетте, бағдарламалық жасақтаманы әзірлеудің нақты әдістемесімен байланысты болды. Мысалы, Andersen-дің FOUNDATION CASE жиынтығы Andersen Method/1 әдістемесімен тығыз байланысты болды.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Процесске бағытталған: Бұл интеграцияның ең жоғары деңгейі. Бұл орталар бағдарламалық жасақтама процесінің талдау және жобалау объектілерін ғана емес, сонымен қатар нақты процестің өзін ресми түрде сипаттауға және бағдарламалық жасақтама жобаларын басқару және бағыттау үшін осы ресми процесті пайдалануға тырысады. Мысалдар: East, Enterprise II, Process Wise, Process Weaver және Arcadia. Бұл орталар, өзіндік бағдарламалық жасақтама процесі ортаның бір бөлігі болғандықтан және құралдарды шақырудың көптеген аспектілерін басқара алатындықтан, әдістемемен байланысты.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.
Іс жүзінде, жұмыс орталары мен орталарды ажырату икемді болды. Мысалы, Visual Basic — бағдарламалау жұмыс ортасы, бірақ көптеген адамдар оны 4GL ортасы деп санайды. Жұмыс орталарын орталардан ерекшелейтін ерекшеліктер — ортақ репозиторий немесе ортақ тіл арқылы терең интеграция және қандай да бір әдістеме (интеграцияланған және процесске бағытталған орталар) немесе домен (4GL) ерекшелігі.
Toolkits: Loosely coupled collections of tools. These typically build on operating system workbenches such as the Unix Programmer's Workbench or the VMS VAX set. They typically perform integration via piping or some other basic mechanism to share data and pass control. The strength of easy integration is also one of the drawbacks. Simple passing of parameters via technologies such as shell scripting can't provide the kind of sophisticated integration that a common repository database can. Fourth generation: These environments are also known as 4GL standing for fourth generation language environments due to the fact that the early environments were designed around specific languages such as Visual Basic. They were the first environments to provide deep integration of multiple tools. Typically these environments were focused on specific types of applications. For example, user interface driven applications that did standard atomic transactions to a relational database. Examples are Informix 4GL, and Focus. Language centered: Environments based on a single often object oriented language such as the Symbolics Lisp Genera environment or VisualWorks Smalltalk from Parcplace. In these environments all the operating system resources were objects in the object oriented language. This provides powerful debugging and graphical opportunities but the code developed is mostly limited to the specific language. For this reason, these environments were mostly a niche within CASE. Their use was mostly for prototyping and R&D projects. A common core idea for these environments was the model–view–controller user interface that facilitated keeping multiple presentations of the same design consistent with the underlying model. The MVC architecture was adopted by the other types of CASE environments as well as many of the applications that were built with them. Integrated: These environments are an example of what most IT people tend to think of first when they think of CASE. Environments such as IBM's AD/Cycle, Andersen Consulting's FOUNDATION, the ICL CADES system, and DEC Cohesion. These environments attempt to cover the complete life cycle from analysis to maintenance and provide an integrated database repository for storing all artifacts of the software process. The integrated software repository was the defining feature for these kinds of tools. They provided multiple different design models as well as support for code in heterogenous languages. One of the main goals for these types of environments was "round trip engineering": being able to make changes at the design level and have those automatically be reflected in the code and vice versa. These environments were also typically associated with a particular methodology for software development. For example, the FOUNDATION CASE suite from Andersen was closely tied to the Andersen Method/1 methodology. Process centered: This is the most ambitious type of integration. These environments attempt to not just formally specify the analysis and design objects of the software process but the actual process itself and to use that formal process to control and guide software projects. Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia. These environments were by definition tied to some methodology since the software process itself is part of the environment and can control many aspects of tool invocation. In practice, the distinction between workbenches and environments was flexible. Visual Basic for example was a programming workbench but was also considered a 4GL environment by many. The features that distinguished workbenches from environments were deep integration via a shared repository or common language and some kind of methodology (integrated and process centered environments) or domain (4GL) specificity.