Unit 3: Software development

AREA OF STUDY 1 - Systems analysis and design

SoD Unit 3 Outcome 1

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.

Key knowledge

1. KK3.1.01- types of information systems and settings in which they are used
2. KK3.1.02- information system goals and objectives
3. KK3.1.03- types of networks, and strengths and weaknesses of different network topologies
4. KK3.1.04- purpose and functions of operating systems and network operating systems
5. KK3.1.05- purpose, functions and capabilities of communications technology, including network interface cards, transmission media (cables and wireless), routing devices and protocols
6. KK3.1.06- economic, social and technical factors prompting organisations to change information systems
7. KK3.1.07- threats to data integrity and security of information, including deliberate actions, accidental actions and technical failures3.1.01- technical underpinnings of actions that threaten the security of information stored and transmitted, including viruses, trojans, spyware, hacking and denial of service
8. KK3.1.08- 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
9. KK3.1.09- the analysis phase of the SDLC, including identification of what systems currently do and what new or modified systems have to do
10. KK3.1.10- tools for representing the logical designs of networked information systems, including context diagrams, data flow diagrams, data dictionaries
11. KK3.1.11- methods for collecting data for analysis, including direct observation, surveys, interviews, reading system program documentation and logs
12. KK3.1.12- 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
13. KK3.1.13- tools for representing the physical designs of the new or modified systems, including system flow charts, structure charts
14. KK3.1.14- functions and characteristics of hardware and software components, including security devices available to protect data and information
15. KK3.1.15- physical design specifications for the input, processing and output requirements that will enable the new or modified information systems to achieve their goals.

AREA OF STUDY 2 - Software development

SoD Unit 3 Outcome 2

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.

Key knowledge

1. KK3.2.01- stages of software development, including design, development and testing
2. KK3.2.02- procedures and techniques for handling and managing files, including security, archiving, backing up and disposing of files
3. KK3.2.03- data types, data structures and data representation methods
4. KK3.2.04- data validation strategies
5. KK3.2.05- types and specifications of portable (mobile) computing devices, including personal digital assistants (PDAs), mobile phones, laptops, gaming consoles
6. KK3.2.06- 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
7. KK3.2.07- purpose and characteristics of internal documentation
8. KK3.2.08- naming conventions for program elements
9. KK3.2.09- legal obligations of programmers and ethical considerations regarding the development of programming solutions
10. KK3.2.10- characteristics of high-quality user interface
11. KK3.2.11- criteria for evaluating software, including effectiveness, efficiency, stability, reliability, usability, maintainability
12. KK3.2.12- a programming language as a method for developing software
13. KK3.2.13- techniques for checking that coded programs meet design specifications, including construction of test data
14. KK3.2.14- principles of hardware operation essential to the development of software modules.

SoD Unit 3 ASSESSMENT

Outcome 1

Analyse an existing networked information system used in an organisation, and propose physical design specifications for a new or modified networked information system.

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)

Outcome 2

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.

Task 1 - A software module, in response to a design specification. (40 marks)

And

Task 2 - One of the following: (10 marks)
* a written report
* a test.

Unit 4: Software development

For Outcome 1 of this unit students continue to study the programming language selected in Unit 3. They are required to engage in all stages of software development: analysis, design, development, testing, documentation, implementation and evaluation.

SoD Unit 4 - Area of Study 1 - Software engineering

Outcome 1

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.

Key knowledge

1. KK4.1.01- types of information system goals and objectives
2. KK4.1.02- stages of software development: analysis, design, development, testing, documentation, implementation and evaluation
3. KK4.1.03- methods of organising files to suit particular software needs, including serial, sequential and random access
4. KK4.1.04- factors affecting access of data, including file size, storage medium, organisation of files
5. KK4.1.05- naming conventions for program elements
6. KK4.1.06- the syntax of a programming language
7. KK4.1.07- factors affecting software design, including user interface, end-user needs, processing efficiency, development time
8. KK4.1.08- forms and uses of data structures to organise and manipulate data
9. KK4.1.09- methods and techniques of representing an algorithm
10. KK4.1.10- data validation and testing strategies
11. KK4.1.11- 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
12. KK4.1.12- applications and purposes of utilities in a programming environment
13. KK4.1.13- the relationship between the developers of purpose-designed software and end-users.

SoD Unit 4 - Area of Study 2 - Systems engineering: Development, implementation and evaluation

SoD Unit 4 Outcome 2

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.

Key knowledge

1. KK4.2.01- purposes for organisations using information systems in a global environment
2. KK4.2.02- advantages and disadvantages for organisations and society in using information systems in a global environment
3. KK4.2.03- 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
4. KK4.2.04- project management tools and techniques to schedule and monitor tasks, assign resources, identify milestones and determine contingency plans
5. KK4.2.05- technical, human, procedural, economic and management factors influencing the acquisition of specific hardware and software components to fulfil design specifications
6. KK4.2.06- testing techniques to ensure that the components operate as intended and to gain acceptance of the networked system
7. KK4.2.07- 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
8. KK4.2.08- types of system support documentation to assist end-users with the implementation of the proposed information systems
9. KK4.2.09- training requirements for the users of the proposed information system, including location of training and nature of training
10. KK4.2.10- methods for implementing the proposed information systems, including direct, phased, pilot and parallel conversions
11. KK4.2.11- 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
12. KK4.2.12- criteria and strategies for evaluating the performance of the proposed information systems.

SoD Unit 4 ASSESSMENT

Outcome 1

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.

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 test
• a written report.

Outcome 2

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.

One of the following:  (50 marks)
* a written report
* a test.