Systems Development Tools and the Relationship to Project Design: Cost and Budget Implications (original) (raw)
Related papers
Current Practices in Information Systems Development Tools and Techniques
Malaysian Journal of …, 1997
The study examines the current practices in information systems development practices among Malaysian information systems managers and system analysts. Technical, organisational and intrinsic facets of information systems development process are assessed. Results indicated that most information systems departments are well-established within their organisations having a close link to top management and majority of the respondents have formal tertiary education in computer science or management information system. The study also indicates that 4GLs, data flow diagrams, data dictionaries and system flowcharts are the most familiar and widely used system development tools. CASE tools are used by all respondents especially for the analysis and design, implementation and project management activities. Majority of the respondents indicate that microcomputers are used extensively and most applications were developed using SQL and COBOL.
Software Development Tooling: Then and Now
While my criticisms of current tooling for development are often met with an attitude of " you're just remembering it differently, things are better now " , the ability to run up old environments and tools gives the lie to that interpretation, since rather than finding they weren't as good as I had remembered, in fact I've done so and found they were better. The slow degradation of capability, occurring over a long period, combined with my increase in experience and skill levels, makes them seem almost easy, even compared with my recollections. While some environments have improved they're largely niche environments, it's the mainstream environments that have in fact gotten worse. To give a bit of background, my first language as a child was Forth. Although I wrote one of the first sequencers on an Apple IIe in 8080 assembler, the lack of any conceptual structure enabled me to forget all of it within a few months of finishing it í ½í¸. At university I majored in 'anything and everything' that looked interesting, winding up with a double major in Philosophy and Mass Communications (the latter allowed me to include things like film production and classical electronic music composition as non-electives), and a B.S. in Mathematics, a title that seemed entirely apropos to the subject. The languages we studied in the programming courses I did take were Smalltalk and Objective-C, which were a little odd for the late 1980s, but then academic languages are often a little odd. Smalltalk felt quite natural having used Forth, but Objective-C was strange: it felt older and more primitive than either. Once done with university, I wasn't sure what I wanted to do, and my first full time job was at an ad agency. Without really intending it I migrated quickly to managing their AS/400 system, which was incredibly easy to use. As an advertising person though, I had some issues, the only ad I wrote in fact got banned, My next job was at a hydraulics and production automation firm, and as it happened they were running production lines using DOS software based on Forth. The problem, especially considering the price of even an 80386-based machine in 1992, was that hydraulic oil tends to float through the air and eventually settle, quite often on the motherboards of such machines, with the inevitable result that they fried. We had had problems, as well, with our accounting/inventory system (not quite an ERP, but close) which was a networked DOS program that used the old Netware DOS based networking (not Netware 3.x, which was its own OS). The system tended to crash, usually during backup, forcing the reentry of an entire week's work. Seemingly only the Xerox technician could even get it to come back up, since it needed to be reinstalled after every crash. Since my background, hardware and OS wise, was in Macintosh and NeXT, I didn't know much about Windows, which was becoming popular, or the current main alternative on PC's, OS/2 2.0. However, the presales attitude of Microsoft versus IBM (" just try it and see if it works " versus " if it doesn't, I'll fly out and make it work ") made the choice of OS/2 rather easy. We bought the requisite hardware and installed OS/2 with a Lan Server machine to run the network, and its flexibility allowed it to double as the owner's workstation. The machines in the shop etc. ran the DOS based program in a full screen DOS session, while the rest of us used the full OS/2 system. Since it stopped crashing, in fact ran the program remarkably well, that was one major issue solved.
System Development: What, Why, When And How CASE Tools Should Support Novice Software Engineers
2007
Novice software engineen particularly computer science students need to be ftained with theoretical knowledge and practical skills in system developments. The knowledge ani skills may encompass the activities involve in all phases of system development including analysis, design, coding, testing and maintenance. Computer Aided Software Engineering (CnSp) tools can be introduced to novices as a supporting .l"..rrt to understand software engineering aspects and principles, which are supposed to enhance the activities. Thus, this paper will discuss problems faced by novice software engineers mainly computer science students during the process of gaining the theoretical knowledge and practicing it while developing Joftware systems for their projects. The analysis of the study will be baseO on four types of elements, which are characteristics, behavior, belief and attitude. The findings will highlighr what, why, when and how CASE tools should support novice software enqineers from analysis to implementation phases of system levelopment compared to that ofexpert software engineers.
Towards a unified view of system development methods
International journal of information management, 1987
Currently a wide range of information system development methods exists, each method supporting different sets of concepts and being supported by different techniques and tools. For many large and complex systems a multi-method approach would be preferable but the fragmentation of contemporary methods does not cater at present for a unified representation of system specifications. The AMADEUS project attempts to redress this situation by enabling the integration of different contemporary development methods ...
Journal of Cases on Information Technology, 2000
The user has requested enhancement of the downloaded file. All in-text references underlined in blue are added to the original docum and are linked to publications on ResearchGate, letting you access and read them immediately.
Software Project Management: Tools assessment, Comparison and suggestions for future development
2016
Software engineering is concerned with the development and advancement of huge and multiple software intensive systems. It shelters theories, methods and tools for the specification, architecture, design, testing, and maintenance of software systems. Today’s development of software systems are significantly large, complex and critical, that only through the use of automated approaches can such systems be developed and evolve in an economic and timely manner. While using automated software tools which is vital for successful planning and managing of projects. There are many automated software tools which have been developed for different purposes in different situation. The literature on how to select the appropriate software project management tools is fairly narrow. The identification of quality project management software among the existing tools in literature is critical. In this paper we predict which project management tools have a great quality and how this quality can be stan...
Tool support for iterative system development activities: Issues and experiences
2000
In the past three years, seven system development projects involving industrial and academic partners have been carried out within Centre for Object Technology. Central to all projects has been an intensive use of a diversity of object-oriented tools and techniques. Based on the experiences from the projects, we discuss tool support for central activities in iterative development and point to directions for future research in development of usable objectoriented tools. Even though a variety of different (CASE) tools can collectively support an iterative, object-oriented system development process, we argue that there is a need for a deeper understanding of, and a better support for, concrete activities in system development practice. Furthermore, there is and cannot be a perfect tool for iterative object-oriented system development: tool developers also need to focus on the art-and skilful interplay and integration of separate tools.