Software Design & Development
PRELIMINARY ASSESSMENT TASK 2
Case Studies
These
four assignments are to be handwritten on A4 paper. You may wish to use the
examples on the web sites listed or you can choose your own. You will need to
list where you found your case study in your report. Use the six(6) point
outline to write your report on the following four approaches. Limit each case
study to two(2) A4 pages.
1. The structured approach to software solutions (due 11th
May)
The structured approach has the characteristics
Ø
Long time periods
Ø
Large scale projects
Ø
Large budgets
Eg Flag Inn
2. The
prototyping approach to software solutions (due 25th May)
The prototyping approach has the characteristics
Ø
non-formal
Ø
shorter
time period
Ø
small
scale projects
Ø
small
budgets
Eg Demos of programs
3. The rapid applications
software development approach (due 8th Jun)
The rapid applications software development approach
has the characteristics
Ø
Lack
of formal stages
Ø
Coding
languages used
Ø
Relationship
of programmer to end user
Ø
Short
time period
Ø
Small-scale
projects
Ø
Low
budgets
Eg Rip Curl
4. End user approach to software development (due 22nd Jun)
The end user approach has the characteristics
Ø
use
of standard software packages
Ø
lack
of formal stages
Ø
short
time period
Ø
potential
long-term, small-scale project
Ø
low
budgets
Ø
end
user is the developer
Eg Sausage Software http://www.sausage.com.au/ and www.ebib.com.au/casestudies/index.asp
|
Assessment task 2 Time allowed 10 weeks Due date Week 10, Term 2, 2001 Marks 15 Weighting 15% |
Outcomes to be assessed: P1.2 describes and uses appropriate data
types P3.1 identifies the issues relating to the
use of software solutions P4.1 analyses
a given problem in order to generate a computer-based solution P4.2 investigates a structured approach in the design and implementation of a software solution P4.3 uses a variety of development
approaches to generate software solutions and
distinguishes between these approaches P5.1 uses
and justifies the need for appropriate project management techniques P5.2 uses and develops documentation to
communicate software solutions to others P6.2 communicates with appropriate personnel
throughout the software development process P6.3 designs and constructs software
solutions with appropriate interfaces |