Abstract
We have designed a software development process that is suitable for small software projects, of the type typically performed by postgraduate students. The aim of the process is twofold, namely to put in place a quality management system which is manageable and appropriate for student projects and to provide templates and guidelines to assist students to design good software, in keeping with the current best practices for software design.
Get full access to this article
View all access options for this article.
References
1.
Hunter
R.
, Is ERP Delivery So Bad? Gartner Group Research Note, February 1999 , http://www.intranet.wits.ac.za…search/ras/76100/76199/76199.html
2.
Buhrer
K.
, From Craft to Science: Rules for Software Design Part II , http://www.therationaledge.com/content/jan_01/f_craft_sci_kb.html, 2001 .
3.
Jacobson
I.
Booch
G.
and
Rumbaugh
J.
, The Unified Software Development Process (Addison-Wesley , Boston , 1998 ).
4.Rational Software Corporation whitepaper , Rational Unified Process — Best Practices for Software Development Teams , 2001 .
5.
Rajakanthan
T.
Meyer
A. S.
and
Dwolatzky
B.
, ‘Smart maps streamline distribution design’ , IEEE Computer Applications in Power , 11 (1 ) (1998 ), 48 .
6.
7.
8.OMG Unified Modeling Language Specification , Version 1.3, First Edition , ftp://ftp.omg.org/pub/docs/formal/00-03-01.pdf, March 2000 .
9.
Quatrani
T.
, Visual Modelling with Rational Rose and UML (Addison-Wesley , Boston , 1998 ).
10.
Van Vliet
H.
, Software Engineering Principles and Practice , 2nd edn (John Wiley , New York , 2000 ).
11.
Gillies
D. F.
, Lecture 4: Use Cases — Design Implementation and Test , www.doc.ic.ac.uk/∼dfg/SoftwareEngineering/SengLecture4.htm, 2000 .