Computer-aided software engineering (CASE) is the scientific application of a set of tools and methods to a software system which is meant

to result in highquality, defect-free, and maintainable software products.[1] It also refers to methods for the development of information systems together with automated tools that can be used in the software development process.[2]
Contents
[hide]
o o o

1 History 2 Supporting software 2.1 Tools 2.2 Workbenches 2.3 Environments 3 Applications 4 Risks and associated controls 5 See also 6 References 7 External links

[edit]History The ISDOS project at the University of Michigan initiated a great deal of interest in the whole concept of using computer systems to help analysts in the very difficult process of analysing requirements and developing systems. Several papers by Daniel Teichroew fired a whole generation of enthusiasts with the potential of automated systems development. His PSL/PSA tool was a CASE tool although it predated the term. His insights into the power of meta-meta-models was inspiring, particularly to a former student, Dr. Hasan Sayani, currently Professor, Program Director at University of Maryland University College. Another major thread emerged as a logical extension to the DBMS directory. By extending the range of meta-data held, the attributes of an application could be held within a dictionary and used at runtime. This "active dictionary" became the precursor to the more modern "model driven execution" (MDE) capability. However, the active dictionary did not provide a graphical representation of any

of the meta-data. It was the linking of the concept of a dictionary holding analysts' meta-data, as derived from the use of an integrated set of techniques, together with the graphical representation of such data that gave rise to the earlier versions of I-CASE. The term CASE was originally coined by software company Nastec Corporation of Southfield, Michigan in 1982 with their original integrated graphics and text editor GraphiText, which also was the first microcomputer-based system to use hyperlinks to cross-reference text strings in documentsan early forerunner of today's web page link. GraphiText's successor product, DesignAid, was the first microprocessor-based tool to logically and semantically evaluate software and system design diagrams and build a data dictionary. Under the direction of Albert F. Case, Jr. vice president for product management and consulting, and Vaughn Frick, director of product management, the DesignAid product suite was expanded to support analysis of a wide range of structured analysis and design methodologies, notably Ed Yourdon and Tom DeMarco, Chris Gane & Trish Sarson, Ward-Mellor (real-time) SA/SD and Warnier-Orr (data driven). The next entrant into the market was Excelerator from Index Technology in Cambridge, Mass. While DesignAid ran on Convergent Technologies and later Burroughs Ngen networked microcomputers, Index launched Excelerator on the IBM PC/AT platform. While, at the time of launch, and for several years, the IBM platform did not support networking or a centralized database as did the Convergent Technologies or Burroughs machines, the allure of IBM was strong, and Excelerator came to prominence. Hot on the heels of Excelerator were a rash of offerings from companies such as Knowledgeware (James Martin, Fran Tarkenton and Don Addington), Texas Instrument's IEFand Accenture's FOUNDATION toolset (METHOD/1, DESIGN/1, INSTALL/1, FCP). CASE tools were at their peak in the early 1990s. At the time IBM had proposed AD/Cycle, which was an alliance of software vendors centered around IBM's Software repository using IBM DB2 in mainframe and OS/2: The application development tools can be from several sources: from IBM, from vendors, and from the customers themselves. IBM has entered into relationships with Bachman Information Systems, Index Technology Corporation, and Knowledgeware, Inc. wherein selected products from

these vendors will be marketed through an IBM complementary marketing program to provide offerings that will help to achieve complete life-cycle coverage.[3] With the decline of the mainframe, AD/Cycle and the Big CASE tools died off, opening the market for the mainstream CASE tools of today. Nearly all of the leaders of the CASE market of the early 1990s ended up being purchased by Computer Associates, including IEW, IEF, ADW, Cayenne, and Learmonth & Burchett Management Systems (LBMS). [edit]Supporting

software

Alfonso Fuggetta classified CASE into 3 categories:[4] 1. Tools support only specific tasks in the software process. 2. Workbenches support only one or a few activities. 3. Environments support (a large part of) the software process. Workbenches and environments are generally built as collections of tools. Tools can therefore be either stand alone products or components of workbenches and environments. [edit]Tools CASE tools are a class of software that automate many of the activities involved in various life cycle phases. For example, when establishing the functional requirements of a proposed application, prototyping tools can be used to develop graphic models of application screens to assist end users to visualize how an application will look after development. Subsequently, system designers can use automated design tools to transform the prototyped functional requirements into detailed design documents. Programmers can then use automated code generators to convert the design documents into code. Automated tools can be used collectively, as mentioned, or individually. For example, prototyping tools could be used to define application requirements that get passed to design technicians who convert the requirements into detailed designs in a traditional manner using flowcharts and narrative documents, without the assistance of automated design software.[5] Existing CASE tools can be classified along 4 different dimensions:

1. Life-cycle support 2. Integration dimension 3. Construction dimension 4. Knowledge-based CASE dimension[6] Let us take the meaning of these dimensions along with their examples one by one: Life-Cycle Based CASE Tools This dimension classifies CASE Tools on the basis of the activities they support in the information systems life cycle. They can be classified as Upper or Lower CASE tools. Upper CASE Tools support strategic planning and construction of concept-level products and ignore the design aspect. They support traditional diagrammatic languages such as ER diagrams, Data flow diagram, Structure charts, Decision Trees, Decision tables, etc.

Lower CASE Tools concentrate on the back end activities of the software life cycle, such as physical design, debugging, construction, testing, component integration, maintenance, reengineering and reverse engineering.

Integration dimension Three main CASE Integration dimensions have been proposed:[7] 1. CASE Framework 2. ICASE Tools 3. Integrated Project Support Environment(IPSE) [edit]Workbenches Workbenches integrate several CASE tools into one application to support specific software-process activities. Hence they achieve:

a homogeneous and consistent interface (presentation integration). easy invocation of tools and tool chains (control integration).

CASE workbenches can be further classified into following 8 classes:[4]

1. Business planning and modeling 2. Analysis and design 3. User-interface development 4. Programming 5. Verification and validation 6. Maintenance and reverse engineering 7. Configuration management 8. Project management [edit]Environments An environment is a collection of CASE tools and workbenches that supports the software process. CASE environments are classified based on the focus/basis of integration[4] 1. Toolkits 2. Language-centered 3. Integrated 4. Fourth generation 5. Process-centered Toolkits Toolkits are loosely integrated collections of products easily extended by aggregating different tools and workbenches. Typically, the support provided by a toolkit is limited to programming, configuration management and project management. And the toolkit itself is environments extended from basic sets of operating system tools, for example, the Unix Programmer's Work Bench and the VMS VAX Set. In addition, toolkits' loose integration requires user to activate tools by explicit invocation or simple control mechanisms. The resulting files are unstructured and could be in different format, therefore the access of file from different tools may require explicit file format conversion. However, since the only constraint for adding a new component is the formats of the files, toolkits can be easily and incrementally extended.[4] Language-centered The environment itself is written in the programming language for which it was developed, thus enabling users to reuse, customize and extend the

environment. Integration of code in different languages is a major issue for language-centered environments. Lack of process and data integration is also a problem. The strengths of these environments include good level of presentation and control integration. Interlisp,Smalltalk, Rational, and KEE are examples of language-centered environments.[4] Integrated These environments achieve presentation integration by providing uniform, consistent, and coherent tool and workbench interfaces. Data integration is achieved through the repository concept: they have a specialized database managing all information produced and accessed in the environment. Examples of integrated environment are IBM AD/Cycle and DEC Cohesion.[4] Fourth-generation Fourth-generation environments were the first integrated environments. They are sets of tools and workbenches supporting the development of a specific class of program: electronic data processing and business-oriented applications. In general, they include programming tools, simple configuration management tools, document handling facilities and, sometimes, a code generator to produce code in lower level languages. Informix 4GL, and Focus fall into this category.[4] Process-centered Environments in this category focus on process integration with other integration dimensions as starting points. A process-centered environment operates by interpreting a process model created by specialized tools. They usually consist of tools handling two functions:

Process-model execution Process-model production

Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia.[4] [edit]Applications All aspects of the software development life cycle can be supported by software tools, and so the use of tools from across the spectrum can,

arguably, be described as CASE; from project management software through tools for business and functional analysis, system design, code storage, compilers, translation tools, test software, and so on. However, tools that are concerned with analysis and design, and with using design information to create parts (or all) of the software product, are most frequently thought of as CASE tools. CASE applied, for instance, to a database software product, might normally involve:

Modeling business / real-world processes and data flow

Development of data models in the form of entity-relationship diagrams

Development of process and function descriptions

[edit]Risks

and associated controls

Common CASE risks and associated controls include: Inadequate standardization: Linking CASE tools from different vendors (design tool from Company X, programming tool from Company Y) may be difficult if the products do not use standardized code structures and data classifications. File formats can be converted, but usually not economically. Controls include using tools from the same vendor, or using tools based on standard protocols and insisting on demonstrated compatibility. Additionally, if organizations obtain tools for only a portion of the development process, they should consider acquiring them from a vendor that has a full line of products to ensure future compatibility if they add more tools.[5]

Unrealistic expectations: Organizations often implement CASE technologies to reduce development costs. Implementing CASE strategies usually involves high start-up costs. Generally, management must be willing to accept a long-term payback period. Controls include requiring senior managers to define their purpose and strategies for implementing CASE technologies.[5]

Slow implementation: Implementing CASE technologies can involve a significant change from traditional development environments. Typically,

organizations should not use CASE tools the first time on critical projects or projects with short deadlines because of the lengthy training process. Additionally, organizations should consider using the tools on smaller, less complex projects and gradually implementing the tools to allow more training time.[5] Weak repository controls: Failure to adequately control access to CASE repositories may result in security breaches or damage to the work documents, system designs, or code modules stored in the repository. Controls include protecting the repositories with appropriate access, version, and backup controls.[5]

omputer-Aided Design Computers are sophisticated tools that are used in every facet of society to provide accuracy, flexibility, cost-savings, efficiency, record-keeping, vast storage, decision-making tools, and modeling. The use of computers to design two-or three-dimensional models of physical objects is known as computer-aided design. Designers in architecture, electronics, and aerospace or automotive engineering, for example, use computer-aided design (CAD) systems and software to prepare drawings and specifications that once could only be drawn or written by hand. Before CAD, manufacturers and designers would have to build prototypes of automobiles, buildings, computer chips, and other products before the prototypes could be tested. CAD technology, however, allows users to rapidly produce a computer-generated prototype and then test and analyze the prototype under a variety of simulated conditions. Manufacturers and designers also use CAD technology to study optimization, performance, and reliability problems in prototypes and in already existing designs. Drawings can be modified and enhanced until the desired results are achieved. CAD is very useful for prototyping because it allows designers to see problems before time and money is invested in an actual product. A Short History of CAD System Development The aerospace industry and mechanical engineering problems figured prominently in the early development of CAD system applications. The earliest uses of this technology demonstrated the need for fast computers with the ability to process large quantities of data. In early CAD systems, computer programs

used numerical methods to simulate real events, evaluate and analyze structures, and calculate optimal performance levels. In the 1950s the first CAD systema graphic air defense systemwas developed for the U.S. Air Force. In the 1960s CAD systems incorporated twodimensional geometry to depict the height and width of calculated objects, and CAD became a tool for drafting applications. By the 1970s many automated design and drafting systems became available. The 1980s brought the first CAD system to be available on a personal computer rather than a mainframe computer. By the 1990s the use of CAD systems had expanded beyond engineering applications to the architecture industry. What once was a need for better database manipulation was now a need for three-dimensional geometry and algebraic manipulations. Basics of CAD Systems Architectural renderings and drawings can be modeled on computers as searching, selection, and computational tasks. Searching tasks are represented as sets of variables with acceptable values. The design software selects alternatives using a generate-and-test process. Design also takes the form of optimization. In these instances rigid structural limits are imposed within a narrow design space. Computations are performed to predict performance and redesign plausible solutions. Searching, selecting, and optimizing are iterative, but compilation is not. Compilation uses programmed algorithms to translate facets of a problem into machine language and arrive at a workable solution. Mathematical Models. Numerical functions that are the basis for mathematical models are at the heart of CAD tasks. Mathematical models define the basic building blocks of three-dimensional (3-D) models. Points, curves, and lines are just a few of the predefined elements that are manipulated geometrically in CAD Systems. Points are usually represented by either two or three values depending on whether a two-dimensional (2-D) or 3-D model is being used. Curves are onedimensional entities that smoothly connect moving points. Lines are entities that have uniform endpoints. Many other geometric models are used in CAD systems to represent circles, arcs, different types of curves, polygons, and other fundamental entities that are used to construct images. Many mathematical models exist to handle basic operations such as interpolation and root finding. Interpolation allows CAD programs to make "educated" guesses about a function's or object's location in a coordinate system

from two known values. Curves and boundary points can be used to determine surface spacesa feature that is very useful in design and manufacturing applications. Numerical differentiationapproximates the derivative of an unknown function, and can be used in problems involving heat transfer, for example. Integration, a primary task in calculus, uses known and unknown values to solve equations that result in precise calculations for analytical approximations. Root finding techniques can be useful for computing changes in signs, determining convergence, and solving polynomial equations. Displaying 3-D Objects. After mathematical modeling develops a rendering of a computer image, it is stored and displayed. Two methods are used to display two-and three-dimensional objects: raster and vector graphics. Raster graphics save the image in a matrix as a series of dots or pixels. The pixels are stored as bits, and the compilation of bits is known as a bitmap . Bitmap images have a photographic type of quality with smooth lines, rich colors, and textures. Bitmap images can be manipulated at the pixel level, and their conversion to their binary representation requires a large amount of computer processing. Each pixel in a bitmap is highlighted and projected on a display screen. All pixels comprising an image appear as a continuous image. An electron beam traces the pixels of an image on the display screen. Vector graphics save images as collections of lines, circles, and intersecting angles. Usually the clipart found in most word processing packages serves as a good example of a vector graphic. In contrast to the photographic quality of bitmap images, vector graphics lack the realistic appeal and smooth surfaces of raster graphics. The lines that create the graphic image are stored as two points {x, y} in a matrix. An electron beam traces over the points several times and the pathway becomes illuminated, and this process produces the lines that make the images. Future Directions for CAD Virtual Reality (VR) is a 3-D visualization tool that is used to construct buildings, manipulate objects in real-time, and build prototypes. Certain features of virtual reality are likely to appear in future CAD packages once standards and protocols are developed. This scenario is desirable to reduce the duplicity involved in transferring geometric data between CAD and VR systems. In addition to the inclusion of VR technology, further advances in CAD technology could include Object-Oriented principles that allow data, data structures, and methods to be encapsulated and features that allow 3-D objects to gain access to the properties, member variables, and associated data through class designations. Another development for future CAD systems might include

the use of databases containing building modules that can be shared by both VR and CAD systems. Future developments in CAD systems might also yield more sophisticated systems for building complex, irregular forms. Such a development along with rapid prototyping, combinations of VR visualization techniques, and artificial intelligence (AI) might make CAD systems more responsive and more powerful development tools in manufacturing, design, and engineering environments. Other advances in CAD technology might involve sharable web-based design libraries and widespread use of agent-based design and problem-solving approaches. In agent-based approaches, the computer system would function like a knowledgeable partner that would work collaboratively to solve problem and address concerns. The agent would be a type of knowledge base that would store information and model planning and integration activities. Distributed AI applications may be the main focus of the next generation of CAD tools because of their ability to codify and represent knowledge structures. These complex systems have the ability to "learn" or change their rule sets based on inconsistencies, inaccuracies, and incomplete data. Applying learning to CAD applications may help reduce the problems of planning and system malfunctions due to the introduction of inaccurate and incorrect data. Other trends in CAD systems may include the application of formal optimization algorithms to manufacturing activities to improve design features of a product and reduce its costs. The application of heuristics or "rules of thumb" to scheduling and sequencing tasks may improve CAD systems in the near future.

Computer Aided Software Engineering (CASE Tools)

1.0 Abstract CASE (Computer Aided Software Engineering) technologies are tools that provide the assistance to the developer in the development of software. Main purpose of the CASE tools is to decrease the development time and increase the quality of software. Even the presence of these qualities CASE tools are not being used most often or freely. These tools are not used freely as they should be; there are some points that need improvement, so that the use of CASE tools can be increased. No a days most of the software houses dont bother to use the CASE tools in their development process. And finally the hurdles in the promotion of the CASE tools as a standard.

2.0 Introduction CASE tools reduce the time and cast of software development and ensure the quality of software. The objective of introducing Computer Aided Software Engineering (CASE) tools was the reduction of the time, cost of software development and for the enhancement of the quality of the systems developed (Diane Lending et al. 1998).
CASE technologies are tools that provide automated assistance for software development to the developers. The goal of introducing CASE tools is to reduce the time of development, reduce the cost of software, and the enhancement of the quality of the software. Upper CASE tools are used to capture, analyze and organize the models of system. These models help designers to focus on the systems linear behaviour. Lower CASE tools are used for development and software maintenance phases. Using these tools developers classify the scope and boundaries, describe current system, model requirements, prototyping, prepare design, etc. Integrated CASE tools provide support for Upper CASE and Lower CASE tool activities. Integrated CASE tools helps specifically in Analysis & Design, Maintenance and system planning. Integrated CASE tools provide the support throughout whole development lifecycle. This paper is almost about, what we already know about the use of CASE tools. First of all we see if get similar results to previous studies on the use of CASE tools. Then we will look in more depth and try to find more about the use of CASE tools and their developments. First of all we will look in the companies which are using CASE tools, what feature they are using of CASE tools? Secondly does CASE tools change or help the software developer in any way or not if yes then how and if not then why? Thirdly we look at the antecedents of intentions use a computer tool, and explore how motivated systems developers are to actually use CASE tools. This study will add depth to what already know about the usage of CASE tools, what are the factors that dont let CASE tools to penetrate in society, why CASE tools are not helpful for labour in saving time and try to discuss the other question like these? This report discuss the CASE tools introduction, history and growth of CASE tools and their use in past ten years, and especially the usage of CASE tools increase or decrease, if decrease what are the factor that can be improved and how these factor can be improved. Why the most of the big software houses dont bother to use the CASE tools in their development process. And finally the hurdles in the promotion of the CASE tools as a standard. 2.1 History of CASE Tools Right from the beginning of software development, software engineer have been in search of such tools that will prove helpful for them in the modeling of system, understanding of system in easy way and in many other ways to provide ease to the people related to computer science. From 1968 to 1971 they are a lot of improvement done in this regard like the top-down structure design, benefit of modularity and step by step code refinement

were admitted, up to 1975 quality, and reliability of software were the big issues and testing procedures were adopt for software reliance. The main start of CASE tools start in 1980s, when documentation, diagrams and design tools were introduce in this field. In same decade automated analysis design check, automated code generation and linking design utilities were introduce. In same decade importance of CASE tools was considered for the large scale system and CASE establish as an industry. Now a dyas there are lot of CASE tools even more than one CASE toils for same problem. Now tools are available that help developers to analyze, design and for the documentation of the software. Even CASE tools are available for deployment and maintenance of the software. Tools like Erwin, Rational Rose has create there importance in the market due to their qualities and reliability. In last ten years CASE tools has emerged as an interactive technology and has gained good position in the software development fields. They are still in the process of improvement like the other fields of the world, because every human created thing in this world has always room for improvement. 3.0 Need of CASE Software developers always looking for such CASE tools that help them in many different ways during the different development stages of software, so that they can understand the software and prepare a good end product that efficiently fulfill the user requirements. CASE tools provide the ways that can fulfill this requirement of software developers. These tools provide computerized setting to software developers to analyze a problem and then design its system model. 3.1 Good Points of CASE Tools 1. They provides better perceptive of system. 2. Facilitates communication among team members. 3. Tools are more effective for large scale systems and immense projects. 4. CASE tools provide visibility of processes and logic. 5. CASE tools improve quality and productivity of software. 6. CASE tools reduce the time for error correction and maintenance. 7. CASE tools provide clear readability and maintainability of the system. 3.2 FACTORS INFLUENCING THE SUCCESS OF CASE

CASE tools facing many troubles in creating a suitable place in market e.g. 1. Even after the completion of the design it is not necessary that it will fulfill the requirements. 2. Though CASE tools are helpful for the developer but do not assure that the design is according to the requirements. 3. Good quality CASE tools are very expensive and prove costly for the development. 4. CASE tools also required training for the user that increase the overall cast of development. 5. Almost every tool has its limitation that decreases its use and popularity. 6. Some tools may have very limited functionality and may not address all possible domain activities. 7. Every tool has a specific methodology for designing and modeling of the system. Due to this youre bound to follow them that decrease the flexibility which decrease the use of CASE tools. 8. Frequent users get used to it and afterward developers try to use the same approach and tool for other projects whether the tool addresses the target projects problems or not. 4.0 Use of CASE Tools The purpose of CASE is to reduce the cost and time required for the system development and the focus is on the quality of the end product. CASE is not being used as it was being expected. Most of the companies are reluctant to adopt the CASE tools. It is observed that CASE is being used but not in many companies. The reasons for abandonment included cost, lack of measurable returns, and unrealistic expectations. Organizations that used CASE tools and found that large numbers of their systems developers were not using CASE tools. He reported that in 57% of the organizations surveyed that were using CASE tools, less than 25% of the systems developers used the tools (Diane Lending 1998). And in those companies where CASE is adopted only few people are using CASE tools. In a survey of 67 companies it has been observed that 69% companies had never used CASE tools. And those people who are using CASE tools admitted that the use of CASE tools improved the standard of documentation and in result the system was easier to test and maintain. But people who used CASE tools also admitted that using CASE tools requires more time and effort and also adds in overall development time. Less then 30% of the potential users and developers use the CASE and those who use it,

uses the simplest and basic functionality of the CASE tools. This shows that even after getting so much popular CASE tools are not adopted and used so much in the software development industry as they expected or as they should be used. Just after one year of introduction 70% of CASE tools are never used, 20 are used by one group and 5 % of CASE tools are used in general[Juhani Iivar,1996]. It has been observed that CASE Tools are not being used from the time CASE got recognition. CASE is being approached experimentarily and involves a very long learning curve. 5.0 Implications in CASE Tools Need for comprehensive CASE plan framework that considers estimated requirements for people, time, and money in the course of CASE adoption (awareness, commitment selection, and implementation) [ Ronald J. Norman,1991]. CASE is not being used as it was expected; there are many factors that affect the use of CASE tools. 5.1 Cost Many tools are costly and most companies are unwilling to implement these CASE tools by the fact that it increases the overall cost of the project. And second thing if a company does not get any extra by using CASE tools then why should they use CASE tools, which are expensive for it in the end. 5.2 Time Limitation There is always a time limit for every software project for development. Most of developers do not adopt CASE because it requires a lot of time to train developers and perform all CASE activities and there are always deadlines to complete the project. You have too meet deadlines of the company but if you use CASE tools you cannot finish your project on time, which is also a factor in less use of CASE tools. 5.3 Training Training is a big concern while any company going to use a new tool, which is quite costly procedure. They have to train there developer for the efficient use of that particular tool. Most of the companies avoid using CASE tools because of this fact that they would have to train a large number of staff and it is expensive and as well as time consuming.

5.4 Lack of Concern Most of the developers who use CASE tools are not fully satisfied from the CASE tools, which are why they are quite neutral about the usefulness of the CASE tools. The developer does not fully enjoy using CASE tools and if some of them do so, they use only limited functionality of the CASE tool. Many developers use CASE tools as a requirement of organization only. Developers do not seem motivated to use CASE tools and this lack of interest is on of the big factor in less use of CASE tools. 5.5 Technical Limitations Every CASE tool follows a methodology for the model the system. People who use any specific CASE tool for a longer period of time get used with the methodology of that tool and they try to apply the same methodology for other projects. Most of the tools have their hardware and software requirements. These requirements should meet to use that tool. This is another hurdle in CASE tool adoption for those companies who does not meet hardware or software requirements to use CASE tools. Tool should not be plate form dependent either of software or hardware. 5.6 Technology Transfer and Insertion One of the main challenges in CASE adoption is technology change. CASE depends on planning, managing and early experiences and it can not be guaranteed even by experienced people that CASE can easily be incorporated. 5.7 Environment Environment is another factor that plays important role in the failure of CASE tools. Is there any practice exists in the organization to adopt new technology and effectively learn it, opposition is always there for the new emerging technology and public dont like to change the existing technology, because they have to learn it before using it. Behavior of people towards change in organization is also very important, if developers and other related people in an organization are willing to implement and adopt new technology, then there are fewer problems. 5.8 Selection of CASE Tool It is also a big concern that an organization must choose a appropriate CASE tool that suite there organization, but unfortunality most of the time developer are not consulted and management use to select the CASE tool that is a big hurdle in the way of CASE tool penetration. Before selecting any new technology, people who uses them must be consulted because they can better argue that how they can effectively use the CASE tool.

As there are many tools for same problem in the market tool selection is a big concern as well. 6.0 Recommendations Tool must not be selected due to its advance features, because most of the advance feature may concern organization dont use in their project. And organizations pay more money for what they dont have to use in the end. There are a lot of tools available in market so you should be careful and try to choose an appropriate tool. Conclusion We have seen that CASE tools plays an important role in Software Development and getting its appreciation in software development industry slowly but surly. But CASE is still in growth and there are different perceptions about CASE.CASE tools are not being used as they are expected to. Though, there are many new CASE tools available in the market and integrated CASE tools provides significant help and support for developers and programmers throughout SDLC in design and development activities but CASE tools have never been first choice for the majority of developers. Research about CASE usage in different organizations has shown that CASE is not always welcomed by developers and programmers and has never been as a tool of choice in organizations. And where CASE is used, the developers are using only minimal required functionality.

Project Management
Printer-Friendly Format

Project Management uses a systematic and disciplined approach to develop software. Project Management activities include: determining the scope of the project, project planning, implementation of project components in a timely manner, review of project activities, and a listing of lessons learned during the project. These activities follow the typical life cycle of a software project. A Software Project Management Plan (SPMP) can be used to outline the structure of the project and how it will be managed. The SPMP will outline all

project management activities including configuration management and team management/roles.