Making a CASE for Using the Students Choice of Software or Systems Development Tools

By Howell, Barbara | Issues in Informing Science & Information Technology, Annual 2004 | Go to article overview

Making a CASE for Using the Students Choice of Software or Systems Development Tools


Howell, Barbara, Issues in Informing Science & Information Technology


Introduction

This paper outlines the first stages of a major research project. The paper describes an evaluation of a method by which a software product such as a Computer-Aided Software or Systems Engineering (CASE) tool may be selected for adoption within an educational institution. Furthermore, the paper seeks to establish which tool is the easiest to use and which provokes interest. This research exercise was not intended to refute the fundamental purpose of CASE tools but in addition to ease and interest sought to examine if the use of Information Communication Technology (ICT) in the form of a CASE tool can facilitate a students' understanding of a specific systems analysis and design technique. Based on these evaluations establish if a particular CASE tool could be a useful components of teaching and learning in relation to usability (ease of use), level of interest and facilitation.

Rationale

The School of Information Management, Leeds Metropolitan University, United Kingdom, is in the process of adopting a new CASE tool to support the learning and teaching of various stages of the software development life cycle. To assist the selection process the user (students are the primary users), are to provide their views on desirable and undesirable characteristics of the tools. If users are involved in the selection process it is asserted that they are more likely to use the tool (Pressman, 1993). In addition, the academic teaching team have found that both undergraduate and postgraduate students have difficulty in grasping the syntax and semantics of systems analysis and design techniques. Peter Chalk (2000) states that CASE tools can enhance learning and support student centred learning. Both are desirable outcomes, which need to be explored and confirmed.

CASE Tools

CASE tools are automated software used by systems analysts on small and large scale information systems development projects (Chalk, 2000). CASE tools can provide support for a range of systems development tasks from project identification and selection to the implementation and maintenances phases (Hoffer, George & Valacich, 1999). CASE tools can support one specific systems development methodology or a variety of approaches (Sommerville, 2001). In association with the organisations 'chosen' methodology, they help the analyst create systems models (many of them graphical models) and then automatically check the models for completeness and compatibility (Satzinger, Jackson & Burd, 2002). CASE tools can also be categorised as upper, lower or integrated CASE tools (Satzinger et al., 2002). Upper CASE tools support the project identification, selection, planning, analysis and design phases of the systems development life cycle. Lower CASE tools provide support for the implementation, generating of code and maintenance stages of the systems development life cycle. The third category, integrated or ICASE tools combine the features of the upper and lower CASE tools to provide support for the full life cycle. For simplicity any future reference to CASE tools will be inclusive of the ICASE definition.

The rationale for using a CASE tool varies enormously between the various stakeholders. From the systems analysts perspective the reason for using a CASE tool are generally very practical and focus on making life easier (Parkinson, 1991). From an organisation perspective, the rationale is much broader and includes; improvement in the quality of the systems development, helps standardisation, improves the management of projects, simplifies maintenance, promotes reusability, improves the quality and maintenance of documentation and increases productivity (Hoffer et al., 1999). CASE tools must also be faster than using pencil and paper and be usable in developing a first draft diagram, which may not require consistency checking (Robinson, 1992). However, the selection of a CASE tool for many professional development environments is largely dependent upon the hardware platform, software system and skill base of the development engineers (Barn, 1992).

The rest of this article is only available to active members of Questia

Sign up now for a free, 1-day trial and receive full access to:

  • Questia's entire collection
  • Automatic bibliography creation
  • More helpful research tools like notes, citations, and highlights
  • Ad-free environment

Already a member? Log in now.

Notes for this article

Add a new note
If you are trying to select text to create highlights or citations, remember that you must now click or tap on the first word, and then click or tap on the last word.
One moment ...
Project items

Items saved from this article

This article has been saved
Highlights (0)
Some of your highlights are legacy items.

Highlights saved before July 30, 2012 will not be displayed on their respective source pages.

You can easily re-create the highlights by opening the book page or article, selecting the text, and clicking “Highlight.”

Citations (0)
Some of your citations are legacy items.

Any citation created before July 30, 2012 will labeled as a “Cited page.” New citations will be saved as cited passages, pages or articles.

We also added the ability to view new citations from your projects or the book or article where you created them.

Notes (0)
Bookmarks (0)

You have no saved items from this article

Project items include:
  • Saved book/article
  • Highlights
  • Quotes/citations
  • Notes
  • Bookmarks
Notes
Cite this article

Cited article

Style
Citations are available only to our active members.
Sign up now to cite pages or passages in MLA, APA and Chicago citation styles.

(Einhorn, 1992, p. 25)

(Einhorn 25)

1

1. Lois J. Einhorn, Abraham Lincoln, the Orator: Penetrating the Lincoln Legend (Westport, CT: Greenwood Press, 1992), 25, http://www.questia.com/read/27419298.

Cited article

Making a CASE for Using the Students Choice of Software or Systems Development Tools
Settings

Settings

Typeface
Text size Smaller Larger
Search within

Search within this article

Look up

Look up a word

  • Dictionary
  • Thesaurus
Please submit a word or phrase above.
Print this page

Print this page

Why can't I print more than one page at a time?

Full screen

matching results for page

Cited passage

Style
Citations are available only to our active members.
Sign up now to cite pages or passages in MLA, APA and Chicago citation styles.

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences." (Einhorn, 1992, p. 25).

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences." (Einhorn 25)

"Portraying himself as an honest, ordinary person helped Lincoln identify with his audiences."1

1. Lois J. Einhorn, Abraham Lincoln, the Orator: Penetrating the Lincoln Legend (Westport, CT: Greenwood Press, 1992), 25, http://www.questia.com/read/27419298.

Cited passage

Welcome to the new Questia Reader

The Questia Reader has been updated to provide you with an even better online reading experience.  It is now 100% Responsive, which means you can read our books and articles on any sized device you wish.  All of your favorite tools like notes, highlights, and citations are still here, but the way you select text has been updated to be easier to use, especially on touchscreen devices.  Here's how:

1. Click or tap the first word you want to select.
2. Click or tap the last word you want to select.

OK, got it!

Thanks for trying Questia!

Please continue trying out our research tools, but please note, full functionality is available only to our active members.

Your work will be lost once you leave this Web page.

For full access in an ad-free environment, sign up now for a FREE, 1-day trial.

Already a member? Log in now.