Diploma of Software Development –

Subject:

Systems Design 1

Developer:

Allan Tadich

Contact Details:

Phone: (W) 9215 7011

Email: atadich@swin.edu.au
Time Frame:

36 hours – 2 hours per week for 18 weeks

References:

1. Systems Analysis and Design: 4th Edition – Shelly, Cashman

and Rosenblatt – Course Technology: Thompson Learning

2. Essentials of IT: General or Software Applications – Hamilton,

Olekalns, Rogers, Sutton and Wilson – Eastern House (specifically
for ICAITS031B)

3. Business Information Processing – Kypridemos and Veliotos -

CITB404 – Eastern House

4. Systems Development Analysis, Feasibility and Implementation

- CITB408/9/10 - Eastern House

5. Modern Systems Analysis & Design: 2nd Edition – Hoofer,

George and Valacich – Addison-Wesley

6. Toolbox - Systems Analysis & Design

http://toolbox.vetonline.vic.edu.au/

7. Systems Analysis and Design: 4th Edition – Kendall and Kendall

– Prentice Hall

Competencies:

ICAITB059B Develop detailed technical design

ICAITT077C Develop detailed test plan

• Diploma of MM (Integration) – Systems Design Page 1 Version 1 Feb 05 AT

 Subject Overview:

Ensure the client business requirements are developed as a pre-requisite to

designing the new/additional system.

Pre-requisites:

Nil

Assessment:

1. Assignment – 40%
2. Class presentation – 20%
3. Exam – 40%

Students must be deemed competent in each assessment item to receive a

graded result.

Sequence of Topics:

Time Topic Reference Comments

6hrs Specify context of business need or Information from The aim
problem: lesson plans here is to
provided by Allan provide
1.3 The business need is fully understood Tadich and from students with
by project team and client. Chapter 1 of the a
Shelly & background
1.2 Methods for gathering and collecting Cashman to systems
information are ensured to be cost effective textbook (5th analysis by
and relevant, both to the project and client edition). initially
environment. considering
the
1.3 System boundaries, scope and organization
methodologies to be used are determined. and its
features,
Students should have the textbook by functions,
week 3 and we can therefore start looking etc.
at the textbook
6hrs Specify interested parties: Chapter 1 –
Systems Analysis
2.1 People (especially the owner, sponsor and Design :
and those that will contribute to defining the Shelly, Cashman
requirements and using the system), and and Rosenblatt
roles of client users are identified.

2.2 The physical requirements of the

system are identified taking into account
current system functionality, geography,
environment, client user and cost

• Diploma of MM (Integration) – Systems Design Page 2 Version 1 Feb 05 AT

 constraints. systems, user productivity
systems & information system integration

2.3 Case studies

These are a list of the relevant headings

from the textbook. Materials i.e.
worksheets, student notes etc. will be
developed in due course.
2hrs Strategic plans. SCR(5) 2, Strategic
Use as intro only. Analysing the plans.
business case. Use as intro
only.
SCR(4) 2.2.

<overlaps
material covered
in Client Needs
Analysis >
2hrs Problem and solution statements. [P] determine the Problem and
Practical activity to get students to focus on problem for: solution
identifying the problem. • Programmer's statements.
toolbox 1 Practical
key terms: problem scope, problem • Programmer's activity to get
domain. toolbox 5 students to
(start) focus on
• Programmer's identifying
toolbox 8 the problem.
(start)
key terms:
problem
scope,
problem
domain.

4hrs SDLC methodologies (overview): SCR(5) 1, Intro to SDLC

Systems methodologi
• traditional, waterfall analysis and es
• prototype design. (overview):
• RAD Brief intro to:
• JAD • modelling • traditional
• prototyping , waterfall
Focus on design and construction. • CASE • prototype
• structured • RAD
analysis • JAD
• OO analysis
• SDLC – Focus on
Waterfall and design and
interactive construction.
development
guidelines
• Diploma of MM (Integration) – Systems Design Page 3 Version 1 Feb 05 AT
 SCR(5) 3,
Requirements
modeling
• JAD and RAD

SCR(4) 1.14 – .21

Brief intro to:
modelling,
prototyping,
CASE, JAD and
RAD, structured
analysis, OO
analysis, SDLC –
Waterfall and
interactive
development
guidelines

[P] SCR(5) 3,
Personal Trainer
Inc case study.
Determine
requirements.

[P] Continue with

toolbox problems.
[P] Roach's
Restaurant
problem
statement and
solution. Students
can determine if
solution solves
the problem and
comment on the
interface.

2hrs SDLC methodologies (detailed): SCR(5) 5, SDLC

• traditional Development methodologi
• prototype strategies es (detailed):
• RAD • select relevant • traditional
• JAD sections • prototype
• RAD
Examine the methodologies described in [P] SCR(5) 5, • JAD
SCR. Personal Trainer
Inc case study. Examine the
There are many other methodologies methodologi
described in textbooks and on the web. SCR(4) es described
6.2 –.9 evaluating in SCR.
In many textbooks, the traditional SDLC alternatives, 6.16

• Diploma of MM (Integration) – Systems Design Page 4 Version 1 Feb 05 AT

 has 7 phases: Problem Definition, completion of There are
Feasibility, Analysis, Design, Development, analysis, 6.17 many other
Implementation and Maintenance. transition to methodologi
design, 6.18 - .20 es described
Prototyping (incl in textbooks
advantages and and on the
disadvantages), web.
6.25 overview of
design, 3.3 - .4 In many
Joint Application textbooks,
Development the
traditional
[P] SCR(4) Look SDLC has 7
at Ridgeway phases:
Company case Problem
study 3.45 q1 Definition,
(determine Feasibility,
requirements) Analysis,
and q2 (scalability Design,
issues) only. This Developmen
case study t,
selected because Implementati
it is complete - on and
others are all in Maintenance
parts. .

SCR(4). Toolkit 4.
• 4.1 - .5 Rapid
Application
Development

• •
[P] Follow links to
OO Tips web site.
Investigate
"Extreme
Programming",
"Pair
programming"
and "To diagram
or not to
diagram".

[P] SCR(5) 3,4,5,

Personal Trainer
Inc case study.
Work in teams:
Try to sketch out
an initial (rough)
design. Which
development

• Diploma of MM (Integration) – Systems Design Page 5 Version 1 Feb 05 AT

 technique would
you use and why?

• [P] SCR(4)
Continue
Ridgeway
Company
case study
example.

2hrs Other methodologies • UML(R) 1.1, Other

Spiral Lifecycle methodologi
Iterative models. es
Waterfall, Spiral
Examine methodologies described in spiral, Iterative
UML(R). Compare with those in described incremental-
in SCR. iterative. Examine
• UML(R) 1.2, methodologi
Understand es described
the unified in UML(R).
modelling Compare
process. with those in
Rational described in
Unified SCR.
Process
phases:
inception,
elaboration,
construction
and transition.

• Larman –
timeboxing –
complete
development
cycle in 2 to 6
weeks.
• Selected
pages or
slides from
OOSAD

2hrs Comparison of life cycles Comparison

• B407 – text of life cycles
Look at advantages and disadvantages of has a
each life cycle. Determine the situations comparison of Look at
where a particular life cycle should be traditional advantages
used. SDLC and and
prototyping. disadvantag
Available on es of each
CIT server as life cycle.

• Diploma of MM (Integration) – Systems Design Page 6 Version 1 Feb 05 AT

 SDLC_Compa Determine
rison.doc. the
situations
[P] Discuss where a
advantages and particular life
disadvantages of cycle should
each approach in be used.
relation to a given
case study.
Possible case
studies:
• SCR(5)
Personal
Trainer Inc
• SCR(4)
Ridgeway
Country Club

4hrs Develop a detailed test plan Classroom based Feedback

activity session to
clients
2hrs Gather requirements: Chapter 3 –
Systems Analysis
4.1 Questionnaires are issued and and Design :
participation in workshops and interviews Shelly, Cashman
has occurred as per the requirements plan. and Rosenblatt

4.2 Collected data is evaluated and

collation of the requirements is started.

4.3 Any gaps in knowledge or other

requirements issues relevant to obtaining a
satisfactory resolution are followed up.

4.4 Views and requirements of key client

users are identified and documented.
Case studies

These are a list of the relevant headings

from the textbook. Materials i.e.
worksheets, student notes etc. will be
developed in due course.
4 Hours Student presentations:
1. Students will in-groups of two present
the findings of their group assignment.
3 Hours Exam:

• Diploma of MM (Integration) – Systems Design Page 7 Version 1 Feb 05 AT

 Elements:

Element Performance Criteria Comments

ICAITAD041A
1. Specify context 1. The business need is fully understood by project
of business team and client
need or 2. Methods for gathering and collecting information
problem are ensured to be cost effective and relevant, both
to the project and client environment
3. System boundaries, scope and methodologies to
be used are determined
2. Specify 1. People (especially the owner, sponsor and those
interested that will contribute to defining the requirements and
parties using the system), and roles of client users are
identified
2. The physical requirements of the system are
identified taking into account current system
functionality, geography, environment, client user
and cost constraints
3. Plan the 1. Most appropriate way to obtain requirements
requirements information is decided on
phase 2. Any questionnaires or material needed for
workshops and interviews are developed and trialed
3. A workable and extensible administration system to
cope with incoming data is prepared
4. An extensible Data Dictionary to be used
throughout the project is prepared.
5. Commitment and timing is agreed on by users and
managers impacted by the plan.
4. Gather 1. Questionnaires are issued and participation in
requirements workshops and interviews has occurred as per the
requirements plan.
2. Collected data is evaluated and collation of the
requirements is started
3. Any gaps in knowledge or other requirements
issues relevant to obtaining a satisfactory resolution
are followed up
4. Views and requirements of key client users are
identified and documented
5. Carry out 1. All functional areas included by the project brief are
preliminary covered in the analysis and meet the client’s stated
analysis of business expectations
information 2. All views and requirements are compared for
commonalties in line with project brief
6. Resolve 1. Conflicting information is investigated and a single
conflicts and position is developed
develop 2. The identified position is circulated for discussion
consensus with key client users according to agreed project
scope
3. Consensus is gained with key client users subject
to project brief and cost constraints

• Diploma of MM (Integration) – Systems Design Page 8 Version 1 Feb 05 AT

ICAITAD042A
1. Confirm client 1. Information is cross-checked and verified as
expectations relevant to project brief using appropriate
and needs techniques to confirm needs
2. Cost effective, relevant and reliable methods are
used to present requirements to client users in
order that they may confirm requirements
3. The identified needs are submitted to higher
authority for confirmation from key decision makers
in the company
2. Confirm that 1. Information is checked to cover functional, quality
information is and added-value requirements, fits within any
consistent and constraints and fully covers the project
complete proposal/brief
2. Latent assumptions are explored and detailed
according to project requirements
3. Consistency and coherence of the elicitation
process is confirmed through the internal
reviews/walk throughs
3. Verify that 1. All techniques used to elicit and to validate
overall process information are verified and found to be consistent
is integrated, and compatible
ensure remote 2. Relevant details only are contained in requirements
users and any model and the elicitation process is confirmed
distributed through requirements model
requirements 3. Details of function usage by business unit including
are covered entity, volumes and function frequency are obtained
4. Matrix/relationship of business units to geographic
locations is confirmed
4. Specify 1. Functions where complexity, function dependency
organisation or usage require special attention are identified
specific issues 2. Transition issues relating to user competence
levels, organisation structure and existing systems
are identified and recorded
3. Organisation specific issues are documented and
reported to higher authorities and/ or technical
specialists
4. The scope of the requirements are reported to
higher authorities for sign off
ICAITAD043A
1. Confirm that 1. Analysis of client requirements has occurred and is
proposed confirmed
solution is the 2. Solutions most useful to client needs are
best reasonable considered by each key client user
fit 3. Proposed solution are accepted by key decision
makers
4. Analysis and recommendations are reviewed with
management according to company requirements
2. Develop high 1. Future business process requirements are
level alternative compared and analysed with current requirements
scenarios 2. Alternative work scenarios are performed for each

• Diploma of MM (Integration) – Systems Design Page 9 Version 1 Feb 05 AT

 work to analyse the principal inputs/outputs;
expected improvements/impacts; revenue/cost
benefits; risks, negatives, down-sides; physical
requirements of each system
3. Alternatives are fully examined against budget
constraints and are dismissed after careful
consideration
4. Model of preferred scenario is prepared
3. Prepare and 1. Reasons for change are established and scope and
publish function of proposed system are detailed
feasibility report 2. Alternative scenarios are described, assumptions
are articulated and 1 (or 2) preferences are
presented
3. Project constraints and impact statement eg.
Personnel/budget are described
4. Cost benefit analysis is prepared in accordance
with organisation standards and project
requirements
5. Plan is produced that describes project schedule,
timeframe and cost constraints
6. Summary is presented to higher authorities / or
client for project approval
ICAIYS031B
1. Analyse client 1. Logged requests are answered in accordance with
support issues organisation guidelines
2. Client support issues are investigated and
documented in accordance with organisation
guidelines
3. Previous logs are checked for similar problem by
same or other client
2. Provide advice 1. Client requirements are confirmed
on software 2. Advice is determined and provided or client is
referred for further technical assistance
3. Advice is provided to client to overcome software
problem in line with organisation guidelines
4. Manuals and help documentation are provided to
client
5. Group or one to one instruction is provided, as
required
6. Upgrade requirements or new software
requirements are documented and
recommendations are referred to
supervisor/management
3. Provide advice 1. Client requirements are obtained from
on hardware documentation
2. Advice is provided to client to overcome hardware
problem in line with organisation guidelines
3. Manuals and help documentation are provided to
client
4. Group or one to one instruction are provided , as
required

• Diploma of MM (Integration) – Systems Design Page 10 Version 1 Feb 05 AT

 5. Further requirements are documented , such as
new equipment requirements, and refer
recommendations to supervisor/management
4. Provide advice 1. Client requirements are obtained from
on network documentation
2. Advice and support is provided to client to
overcome network problem in line with organisation
guidelines
3. Manuals and help documentation are provided to
client
4. Group or one to one instruction is provided , as
required
5. Further requirements are documented and
recommendations are referred to
supervisor/management
5. Obtain client 1. Client evaluation and feedback are obtained to
feedback ensure client requirements are met
2. Function is performed by client unassisted
according to instruction

• Diploma of MM (Integration) – Systems Design Page 11 Version 1 Feb 05 AT