TITLE

Systems Development Methods for Enterprise Integration, Part 1

AUTHOR(S)
Finkelstein, Clive
PUB. DATE
February 2004
SOURCE
DM Review;Feb2004, Vol. 14 Issue 2, p66
SOURCE TYPE
Periodical
DOC. TYPE
Article
ABSTRACT
Discusses the changes in systems development methods necessary for the 21st century enterprise. List of personalities who were key originators of software engineering methodologies or structured methods; Result of changing programs that automated the different versions of the manual process; Information on information engineering which was developed in Australia.
ACCESSION #
12432144

 

Related Articles

  • E is for e-engineering. Wilson., Dave // Design Engineering;Oct99, p15 

    Focuses on the benefits of computer software engineering to systems designers. Cost effectiveness of using the Internet; Dependence of software engineering on information technology infrastructure.

  • QUESTIONING SOFTWARE'S USABILITY. Hambrose, Harold // Baseline;Nov2008, Issue 90, p14 

    The article focuses on the usability of computer software. It implies that information technology (IT) companies spend billions of dollars to create and market software designed to improve efficiency and increase effectiveness. It notes that many of the software applications are failing the end...

  • Teaching embedded microprocessor systems by enquiry-based group learning. Barnes, M.; Bailey, M.; Green, P. R.; Foster, D. A. // International Journal of Electrical Engineering Education;Jan2006, Vol. 43 Issue 1, p1 

    Engineers today are required both to have a mastery of 'traditional' technological skills and to be competent with a variety of 'soft skills' such as teamworking and the ability to present or sell their ideas. At the same time the technological skill requirements are broader. There is a gradual...

  • Wisdom: A Software Engineering Method for Small Software Development Companies. Nunes, Nuno J.; Cunha, Joao F. // IEEE Software;Sep/Oct2000, Vol. 17 Issue 5, p113 

    Describes Wisdom (Whitewater Interactive System Development with Object Models), a software engineering method developed to meet needs of small software developing companies. Components of Wisdom; Mechanics involved in the implementation of Wisdom; Discussion on the workflows of Wisdom.

  • Point taken. GAMBUZZA, MICHAEL // EDN Europe;Nov2013, Vol. 11, p38 

    The author discusses the importance for hardware and software engineers to watch for inductor saturation and to environmentally test their designs to avoid technical mistakes when the system is deployed.

  • THE RELATIONSHIP BETWEEN ORGANIZATIONAL CULTURE AND THE DEPLOYMENT OF SYSTEMS DEVELOPMENT METHODOLOGIES. Iivari, Juhani; Huisman, Magda // MIS Quarterly;Mar2007, Vol. 31 Issue 1, p35 

    This exploratory study analyzes the relationship between organizational culture and the deployment of systems development methodologies. Organizational culture is interpreted in terms of the competing values model and deployment as perceptions of the support, use, and impact of systems...

  • From StPowla processes to SRML models. Bocchi, Laura; Gorton, Stephen; Reiff-Marganiec, Stephan // Formal Aspects of Computing;May2010, Vol. 22 Issue 3/4, p243 

    Service Oriented Computing is a paradigm for developing software systems as the composition of a number of services. Services are loosely coupled entities, that can be dynamically published, discovered and invoked over a network. The engineering of such systems presents novel challenges, mostly...

  • CASE Center shifts strategy toward established firms. Rombel, Adam // Business Journal (Central New York);10/10/2003, Vol. 17 Issue 41, p7 

    Reports on Sycaruse University Computer Applications and Software Engineering's (CASE) enhancement of the amount of its applied Information Technology research for established area companies. Popularity of the CASE center for its information technology business incubator; Number of companies...

  • When Models Collide: Lessons from Software Systems Analysis. Boehm, Barry; Port, Dan // IT Professional;Jan/Feb1999, Vol. 1 Issue 1, p49N 

    Discusses the use of Model-Based System Architecturing and Software Engineering approach in preventing conflict of development models around the creation and use of a software architecture package. Four basic models; Failure profile for particular types of projects; Success model clashes; Role...

Share

Read the Article

Courtesy of THE LIBRARY OF VIRGINIA

Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics