Software development Cycles
This is an excerpt from the paper...
Software development has a cycle which, if properly managed, can result in high quality products written in the least amount of time. However, improperly managed software development projects can result in cost overruns, poor quality programming, dissatisfied users, demoralized programmers, and put the viability of the software development at risk. There are many configuration management approaches and application development tools which have been developed to assist in the software development process, but the success of any of these is dependent on their implementation and the willingness of the supporting organization to embrace their use. One of the most widely touted tools available to software developers is Computer Aided Software Engineering (CASE), which includes system integration as well as software design and analysis of methodologies. This research examines CASE technology and how companies can benefit from its implementation.CASE software automates many of the functions that system designers and programmers must perform. Analysts can use CASE to generate flow chart symbols by using a mouse to designate symbol choices and screen positions, and create data dictionaries through the labeling of processes. In some products, data dictionary entries are automatically made with many of the fields filled in based on the development environment. Process description at a detailed level (such as structured English) can allow automatic gener
. . .
nd presentation. In a true ICASE environment, presentation should offer common user interface facilities regardless of the tool in use or the type of interface (GUI versus command line, for example).
Control integration is concerned with the formal, standard tool notification system that crosses tools and keeps the entire development process under control. In this way, announcements and details of modifications on one tool are sent to all other tools concerned with those changes. Such integration capabilities may include event notification when appropriate, a formal intertool communication mechanism, and formal application programming interfaces (APIs).
Process integration means that the tool is oriented toward the practice of formal software engineering techniques. This means that the additional processes required to complete the software engineering process (those that are required in addition to the software tools themselves) should be integrated into the overall procedures. These mean that the tools should be directed related to tasks in the software process, and that the processes themselves should form the basis for future CASE environments (Sullivan-Trainor, 1991, p. 72).
Finally, data integration is critical to the
. . .
Some common words found in the essay are:
Software Engineering, Integrated ICASE, Conclusion Overcoming, BMS BMS, APIs Process, Benefits Implemented, Introduction Software, Server BMS, Equipment Corporation, Sumner Ryan, software development, simon 1993, icase environment, control integration, software engineering, journal systems management, digital equipment, development environment, equipment corporation, client/server environment, platform integration, systems management pp, digital equipment corporation, sumner ryan 1994, sullivan-trainor 1991 72,
Approximate Word count = 2452
Approximate Pages = 10 (250 words per page)
More Essays on Software development Cycles
|