Software
Development
Unit 3
Homework/Course Material -- 2007
Text Book : Fitzpatrick , Keane "Software Development"
Unit 3 focuses on the techniques and procedures for determining the ability of networked information systems to meet organisational needs and on how the development of purpose-designed software, using a programming language, helps fulfil these needs. Students explore the roles and functions of networked information systems, and the types of networks. They apply three phases of the waterfall model of the systems development life cycle (SDLC): analysis, design and development. They use this concept as the methodology for making changes to networked information systems.
On completion of this unit the student should be able to analyse an existing networked information system used in an organisation, and propose physical design specifications for a new or modified networked information system.
Assessment : Task 1 - In response
to a given design brief
- a written report (including documentation of analysis and design) (40
marks)
And
Task 2
- a labelled visual representation of a networked information system. (10
marks)
In achieving this outcome the student will draw on knowledge described in Area Of Study 1 ( Systems analysis and design ). To achieve this outcome the student should demonstrate knowledge of
types of information systems and settings in which they are used;
information system goals and objectives;
types of networks, and strengths and weaknesses of different network topologies;
purpose and functions of operating systems and network operating systems;
purpose, functions and capabilities of communications technology, including network interface cards, transmission media (cables and wireless), routing devices and protocols;
economic, social and technical factors prompting organisations to change information systems;
threats to data integrity and security of information, including deliberate actions, accidental actions and technical failures;
technical underpinnings of actions that threaten the security of information stored and transmitted, including viruses, trojans, spyware, hacking and denial of service;
security devices and procedures available to protect data and information; .
the systems development life cycle (SDLC) and techniques for managing this, including a detailed study of the waterfall model of the SDLC and an overview of rapid application development (RAD), prototyping, and Agile models;
the analysis phase of the SDLC, including identification of what systems currently do and what new or modified systems have to do;
tools for representing the logical designs of networked information systems, including context diagrams, data flow diagrams, data dictionaries;
methods for collecting data for analysis, including direct observation, surveys, interviews, reading system program documentation and logs;
the design phase of the SDLC, including identification of the components (people, procedures, data and equipment) that will enable the logical design specifications to be implemented;
tools for representing the physical designs of the new or modified systems, including system flow charts, structure charts;
functions and characteristics of hardware and software components, including security devices available to protect data and information;
physical design specifications for the input, processing and output requirements that will enable the new or modified information systems to achieve their goals.
explain the economic, social or technical factors causing organisations to change their networked information systems, including reference to security weaknesses; and/or inefficiencies of data processing;
propose a range of methods to collect data for analysis;
apply logical design tools and techniques to document existing systems
identify the processes, procedures or equipment that must be changed in order to fulfil an information system goal or objective;
describe the physical specifications of the new or modified system, including the input and output devices, format, size and use of fi les, software capabilities, control procedures, backup procedures, security procedures;
represent visually the components of proposed networked information systems and their relationships.
No | Homework/Course Description |
Area of Study/ Key Knowledge | Resource |
Due Date |
SAC 31 -- |
||||
1 |
Handout 1 --
Course Outline.
Handout 3
-- Due Dates. Text p 2 - 8 , Activities 1.1 - 1.6 , Q 1,2,4,6-8 p 22. Information System Types slide show |
SAC31 , Key Knowledge 1 | Text | |
2 | Handout 2 -- Information
Systems Types of Organisations CD Area of Study 3.3 Worksheet "Components of Information Systems". Worksheet CD AOS 43, Organisational Goals Worksheet CD SAC 33, Achieving Organisational Goals Worksheet CD SAC 33, Information System Goals and Objectives. Worksheet Organisational goals, system goals and objectives Case Study Goals and Objectives |
SAC31 , Key Knowledge 1,2 | Handout, CD |
|
3 | Text p 14 -18 , Activities 1.10 Q 3,12,14-16 p 22 | SAC31 , Key Knowledge 1 | CD | |
4 |
Computer Architecture Worksheet;
Computer architecture slide-show and questions . Slide Show ( complete missing parts of slide show using www.pcwebopaedia.com ) |
SAC31 , Key Knowledge 4 | Online | |
5 | SOHO network design ( 4 stations, printer/scanner, internet, wireless, security, performance, share files, login, share games etc ) | SAC Key Knowledge 3 - 5 | Class exercise | |
6 | Text p 24 - 41 ,
Activities 2.1 -2.6 Q 1 -27 p 52 CD SAC 42 Network and Data Communications worksheet; Network Topologies Worksheet. Handout 4 |
SAC31 , Key Knowledge 3 - 5 | Text, CD | |
7 | CD SAC 42, Network Operating Systems, Architecture and components worksheet. Slide show on Networks and concepts. | SAC31 Key Knowledge point 4 | CD | |
8 | Complete 10 quizzes on VITTA CD | SAC31 Key Knowledge 1 - 5 | ||
9 |
Handout 5, 6 ;
Slide show impetus for change CD Area of Study 42, Impetus for Change worksheet. |
SAC31 Key Knowledge point 6 | Handout, Online |
|
10 |
Information Security;
Slide Show information security . Text p 42 - 47 , Activities 2.7; Q 28 - 30 p 52. Backup Worksheet, Handout 7 CD Area of Study 32,"Data and information security" and "Security measures" worksheet |
SAC31 Key Knowledge point 7 - 9 | Text, Online |
|
11 | Text p 8 -13 , Activities 1.7
-1.9 Q 5, 9, 10, 11, 13 p 22. Slide show SDLC CD Area of Study 42, Systems Development Life Cycle worksheet. RAD and Agile Models Text p 100 - 102 Q 8 p 119 |
SAC31 Key Knowledge 10 | Text | |
12 |
Data
and information Text p 55 - 80, Activities 3.1 - 3.2; Q 1 - 32 p 81 -82 CD SAC 32 -Value and Suitability of Information Worksheet Case Study p 82 - 83 |
SAC31 Key Knowledge 11-13 | Text Handouts | |
13 |
Handout 8 (Context Diagrams) ; Handout
9 (Data Flow Diagrams) Hierarchy/Structure Charts and System Flow Charts Data Dictionary, System Flow Charts, Hierarchy/Structure Charts |
SAC31 Key Knowledge 12,17 | Handout | |
14 | Text p 83 -88 ; Q 1
- 11 p 89 ; Case Study p 89 -90 |
SAC31 Key Knowledge 14 -17 | Text | |
13 | Test your knowledge, What you
should know p 19 -22
Text Case Study p 23 Text What you should know; Test your knowledge p 47 -52 Text Case Study p 53 -54 Text |
SAC31 Key Knowledge 1 - 17 | Text |
On completion of this unit the student should be able to produce a software module suitable for implementation on a portable computing device, in response to a design specification, verify its performance against this specification and explain how the program has taken into account an ethical dilemma or a legal obligation.
Assessment : Task 1 - In response
to a given design brief
- A software module, in response to a design specification. (40 marks)
And
Task 2 One of the following: (10 marks)
- a written report or
- a test.
In achieving this outcome the student will draw on knowledge described in Area Of Study 2 ( Software Development ). To achieve this outcome the student should demonstrate knowledge of
stages of software development, including design, development and testing;
procedures and techniques for handling and managing files, including security, archiving, backing up and disposing of files;
data types, data structures and data representation methods;
data validation strategies;
types and specifications of portable (mobile) computing devices, including personal digital assistants (PDAs), mobile phones, laptops, gaming consoles;
methods of expressing software design using data tables and algorithms, including an overview of flow charts, pseudocode, Nassi-Shneiderman diagrams, object descriptions and a detailed understanding of one of them;
purpose and characteristics of internal documentation;
naming conventions for program elements;
legal obligations of programmers and ethical considerations regarding the development of programming solutions;
characteristics of high-quality user interface;
criteria for evaluating software, including effectiveness, efficiency, stability, reliability, usability, maintainability;
a programming language as a method for developing software;
techniques for checking that coded programs meet design specifications, including construction of test data;
principles of hardware operation essential to the development of software modules.
interpret the design specifications by representing processes in the form of algorithms and data structures in the form of a data table;
use a programming language from the list published annually by the Victorian Curriculum and Assessment Authority;
apply appropriate naming conventions and formatting;
apply data validation techniques;
document the code;
apply relevant constructs of the programming language to produce a working module within the constraints of the chosen portable computing device;
develop and apply a testing strategy to compare the intended with the actual module capabilities;
explain how the program has taken into account an ethical dilemma or a legal obligation.
No | Homework/Course Description |
Area of Study/ Key Knowledge | Resource |
Due Date |
SAC 32 -- |
||||
1 | Text p 11 - 14. p 122 -124, 192- 197. PHP/MySQL Text Learning Activity 1. Q 1-4 p 225 | SAC32 , Key Knowledge 1 | Text | |
2 | Text p 220 - 221, Backup Worksheet, Handout 7 | SAC32 , Key Knowledge 2 | Text Handout |
|
3 | Text p 156 - 162, p 166 - 171
Activities 6.1 - 6.5 [Q 1 - 49 p 188 - 190] Text p 125 -130, 153 - 155 |
SAC32 , Key Knowledge 3 | Text | |
4 | Text p 195 -196 PHP/MySQL Text
Learning Activity 2, 3, 4, 5 , 6 , 7 Q 5 p 225 |
SAC32 , Key Knowledge 4 | Text | |
5 | Text p 33, PHP/MySQL Text Learning Activity 13 | SAC32 , Key Knowledge 5 | Text | |
6 | Text p 196 - 204 , Q 6 - 14 p 225 | SAC32 , Key Knowledge 6 | Text | |
7 | Text p 214 Q 37 p 227 | SAC32 , Key Knowledge 7 | Text | |
8 | Text p 208 - 212 Q 30,31,47 p 227 | SAC32 , Key Knowledge 8 | Text | |
9 | Text p 137 - 142 , Q p 148 - 149 | SAC32 , Key Knowledge 9 | Text | |
10 | Text p 193 -195 Q 3, 4 p 225 | SAC32 , Key Knowledge 10 | Text | |
11 | Text p 218 - 219 Q 46 p 227. p 102 -103, 86 -88 | SAC32 , Key Knowledge 11 | Text | |
12 | Text p 171 - 184, p 84 - 87 Q 31 - 36 p 189, p 134 - 137 | SAC32 , Key Knowledge 12 | Text | |
13 | Text p 208 - 215, 218 Q 21 -29 p 226 | SAC32 , Key Knowledge 13 | Text | |
14 | Text p 25 , 84 -88, p 104 - 106 Q 1 - 11 Test your knowledge p 89 | SAC32 , Key Knowledge 14 | Text | |
15 | What you should know p 143 -
146, 147 - 148, 185 - 188 Test your knowledge p 188 - 190 Apply your knowledge p 149, 190 |
Text |
This unit focuses on techniques, procedures and strategies to develop, implement and evaluate proposed networked information systems. Students explore the technical, human, procedural, economic and management factors that need to be considered when undertaking these phases of the systems development life cycle (SDLC). The development phase is realised through the creation of software solutions using the programming language studied in Unit 3.
On completion of this unit the student should be able to apply the stages of software development to produce purpose-designed software that takes into account a networked information system objective and the needs of end-users.
Assessment :
Task 1 - Information technology solution (including internal
documentation) in response to a design brief. (35 marks)
And
Task 2
User documentation and an explanation of how purpose-designed software may
cause conflict between program developers and end-users in one of the
following modes: (15 marks)
- a written report or
- a test.
Key knowledge
types of information system goals and objectives;
stages of software development: analysis, design, development, testing, documentation,
implementation and evaluation;
methods of organising files to suit particular software needs, including serial, sequential and random access;
factors affecting access of data, including file size, storage medium, organisation of files;
naming conventions for program elements;
the syntax of a programming language;
factors affecting software design, including user interface, end-user needs, processing efficiency, development time;
forms and uses of data structures to organise and manipulate data;
methods and techniques of representing an algorithm;
data validation and testing strategies;
forms of user documentation, including printed, CD, online Internet site, and types of user documentation, including quick start guide, tutorial, content sensitive help and manual;
applications and purposes of utilities in a programming environment;
the relationship between the developers of purpose-designed software and end-users.
identify factors affecting the design and implementation of software solutions, taking into account the information system objectives;
define the requirements of the software solutions;
represent specifications in the form of algorithms and data tables;
develop and apply data validation techniques and security procedures;
develop and apply testing strategies;
write programs and internal documentation;
write appropriate user documentation;
run and debug programs so that they produce output that is well organised and readable and that meets user needs;
propose evaluation strategies to determine the extent to which the programs fulfil the information system objectives;
explain how purpose-designed software may cause possible conflict between the individuals or organisations responsible for developing it and end-users.
No | Homework/Course Description |
Area of Study/ Key Knowledge | Resource |
Due Date |
SAC 41 -- |
||||
1 | See SAC 31 , point 2 | SAC41 Key knowledge 1 | Text | |
2 | p 192 - 221 Activity 7.1 [ Q 1 - 48 p 225 ] | SAC41 Key knowledge 2 | Text | |
3 | Text p10 PHP/MySQL Text Learning Activity 8 - 12 , Exercises |
SAC41 Key knowledge 3 | Text/DVD | |
4 | Text p162 - 166 [Q 1 - 49 p 188 - 190 - covered in SAC32] | SAC41 Key knowledge 4, 5 | Text | |
5 | Text p 220 - 221 | SAC41 Key knowledge 6 | Text | |
6 | Text p 12, 172, 213 | SAC41 Key knowledge 7 | Text | |
7 | Text p 192 - 200 | SAC41 Key knowledge 8 | Text | |
8 | Text p 157 - 162 | SAC41 Key knowledge 9 | Text | |
9 | Text p 196 - 208 | SAC41 Key knowledge 10 | Text | |
10 | Text p 208 - 215 | SAC41 Key knowledge 11 | Text | |
11 | Text p 215 - 218 | SAC41 Key knowledge 12 | Text | |
12 | Text p 131 - 133 | SAC41 Key knowledge 13 | Text | |
13 | Text p 137 - 138 | SAC41 Key knowledge 14 | Text | |
14 | What you should know and
Test your knowledge p 222 - 225, 226 - 227 What you should know and Test your knowledge p 185 - 188, 190 |
Text |
On completion of this unit the student should be able to propose and justify strategies for managing, developing, implementing and evaluating the introduction to an organisation of a networked information system that will operate in a global environment.
Assessment : One of the following: (50 marks)
- a written report or
- a test
In achieving this outcome the student will draw on knowledge described in Area Of Study 2 ( Systems engineering: Development, implementation and evaluation ). To achieve this outcome the student should demonstrate knowledge of
purposes for organisations using information systems in a global environment;
advantages and disadvantages for organisations and society in using information systems in a global environment;
the development phase of the systems development life cycle (SDLC), including the realisation of the physical design specifications with respect to acquiring the identified hardware requirements, acquiring and/or developing software, identifying required personnel and their knowledge and skills, and assembling and testing the new information systems;
project management tools and techniques to schedule and monitor tasks, assign resources, identify milestones and determine contingency plans;
technical, human, procedural, economic and management factors influencing the acquisition of specific hardware and software components to fulfil design specifications;
testing techniques to ensure that the components operate as intended and to gain acceptance of the networked system;
the implementation phase of the SDLC, including preparation of user documentation, designing and conducting training programs, preparation of disaster recovery plans and the changeover to new systems;
types of system support documentation to assist end-users with the implementation of the proposed information systems;
training requirements for the users of the proposed information system, including location of training and nature of training;
methods for implementing the proposed information systems, including direct, phased, pilot and parallel conversions;
procedures to protect and secure stored and communicated data and information;
the evaluation phase of the SDLC, including determining if the information system is fulfilling its design specifications;
criteria and strategies for evaluating the performance of the proposed information systems.
prepare project management plans for coordinating the development, implementation and evaluation of the proposed systems;
explain what factors influenced the acquisition of specific hardware and software components and personnel to fulfil the specifications;
devise appropriate testing strategies;
propose implementation strategies that include a description of the changeover method, types of documentation, training and procedural requirements and key disaster recovery actions;
formulate strategies to evaluate the performance of the proposed information systems;
explain one way in which organisations and their end-users will be affected by the implementation of the proposed information systems.
No | Homework/Course Description |
Area of Study/ Key Knowledge | Resource |
Due Date |
SAC 41 -- |
||||
1 | Handout 10 | SAC42 Key knowledge 1 | Handout | |
2 | Handout 11 | SAC42 Key knowledge 2 | Handout | |
3 | Text p 99 - 105 | SAC42 Key knowledge 3 | Text | |
4 | Text p 92 - 99 | SAC42 Key knowledge 4 | Text | |
5 | Text p 102 - 106 | SAC42 Key knowledge 5 | Text | |
6 | Text p 106 - 108 | SAC42 Key knowledge 6 | Text | |
7 | Text p 108 - 111 | SAC42 Key knowledge 7 | Text | |
8 | Text p 112 - 114 | SAC42 Key knowledge 8 | Text | |
9 | Text p 110 - 112 | SAC42 Key knowledge 9 | Text | |
10 | Text p 108 - 110 | SAC42 Key knowledge 10 | Text | |
11 | Text p 113 - 115 | SAC42 Key knowledge 11 | Text | |
12 | Text p 115 - 118 | SAC42 Key knowledge 12,13 | Text | |
15 | Test your knowledge;
Apply your knowledge p 118 - 120 |
Text |