In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:

Slides:



Advertisements
Similar presentations
Debugging ACL Scripts.
Advertisements

Testing Relational Database
P3, P4, P5, P6.
P5, M1, D1.
Advanced Database Projects In Access © Hodder Education 2008 Access Projects – Problem Specification.
CS0004: Introduction to Programming Visual Studio 2010 and Controls.
UNIT 12 LO4 BE ABLE TO CREATE WEBSITES Cambridge Technicals.
GCSE PROJECT GUIDELINES Use this presentation to make sure you have the correct content for you project - click on.
Validation and Verification Today will look at: The difference between accuracy and validity Explaining sources of errors and how they could be overcome.
Software Development, Programming, Testing & Implementation.
Documentation 1. User Documentation 2. Technical Documentation 3. Program Documentation.
Systems Analysis Chapter 8 P 94 to P 101
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Systems Life Cycle A summary of what needs to be done.
1 AQA ICT AS Level © Nelson Thornes 2008 Testing a solution.
Testing. Terms 1 Test Data: The data you will enter to test your system Test Plan: A plan of the tests you are going to complete to ensure your system.
1 Shawlands Academy Higher Computing Software Development Unit.
Unit 1 – Improving Productivity Instructions ~ 100 words per box.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Chapter 8: Systems analysis and design
Unit B065 – Coding a solution PREP WORK 1)Make sure you keep a work log / diary. Use the table on page 16 of the hand book as a template 2)Keep a bibliography.
What is Sure BDCs? BDC stands for Batch Data Communication and is also known as Batch Input. It is a technique for mass input of data into SAP by simulating.
Moodle (Course Management Systems). Assignments 1 Assignments are a refreshingly simple method for collecting student work. They are a simple and flexible.
Enrolment Services – Class Scheduling Fall 2014 Course Combinations.
Making a database Karyl Slim 11IOTA. In today’s lesson, we started to create a database that would contain details of endangered species. To create the.
* DIDA gave a brief of designing a database that would be able to store details of endangered species. The purpose of the database was so that members.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
STEPS IN THE WEB DESIGN PROCESS A 5 minute presentation on the latest Ideas and methods.
Making a great Project 2 OCR 1994/2360. Design Some candidates dive in, make a database or spreadsheet, then try and make a design afterwards. This won’t.
Software Development Process.  You should already know that any computer system is made up of hardware and software.  The term hardware is fairly easy.
C++ Programming Language Lecture 2 Problem Analysis and Solution Representation By Ghada Al-Mashaqbeh The Hashemite University Computer Engineering Department.
PROJECT LOG MOLLY ATKINSON. 10/09 Today, I got to grips with the course outline, which included creating the relevant folders for all my future publications,
Systems Life Cycle. Know the elements of the system that are created Understand the need for thorough testing Be able to describe the different tests.
From Lucent, Inc. This is the Sablime® home page. It has access to all the functionality of the Sablime® Configuration Management System.
Level 2 IT Users Qualification – Unit 1 Improving Productivity JACK GOODING.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
Microsoft ® Office Excel 2003 Training Using XML in Excel SynAppSys Educational Services presents:
Software. A web site is a collection of web pages on a particular topic. A web page is a document written in HTML code. Web pages are linked together.
The Software Development Process
 Network  A _____ of computers that can _________ w/ each other  Examples of hardware  ______________ & communication lines  Internet  Hardware.
Friday 14 th September 2012 In todays lesson we were introduced to our new coursework. We looked at the DIDA Wildcare project. I then made a new folder.
GCSE ICT Introduction. How is the GCSE course organised? The GCSE course has three parts: Assignment (Year 10 project) - this section is set by the examination.
Intermediate 2 Computing Unit 2 - Software Development.
Making a great Project 2 OCR 1994/2360. Implementation This is about how you make your system. It should have enough detail for a competent user to be.
The Hashemite University Computer Engineering Department
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Testing.
Validation & Verification Today will look at: The difference between accuracy and validity Explaining sources of errors and how they could be overcome.
Observing the Current System Benefits Can see how the system actually works in practice Can ask people to explain what they are doing – to gain a clear.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
1. Design: Plan in detail Look at the two images below. One is a design and one is the final product. The examiner needs to see your designs AND your final.
Easy Access with templates I: Create a database Lesson 16 By the end of this lesson you will be able to complete the following: Find the best database.
Learning Objectives Today we will Learn: The different types of test data.
Analysis. This involves investigating what is required from the new system and what facilities are available. It would probably include:
Advanced Higher Computing Science The Project. Introduction Worth 60% of the total marks for the course Must include: An appropriate interface using input.
REPORTING YOUR PROJECT OUTCOMES HELEN MCBURNEY. PROGRAM FOR TODAY: Report Reporting to local colleagues Reporting to the Organisation Tips for abstract.
Reporting your Project Outcomes Helen McBurney. Program for today: Report Reporting to local colleagues Reporting to the Organisation Tips for abstract.
Advanced Higher Computing Science
IL Marking Get out your CPU / Memory answers Swap with someone else
Training Guide for Faculty
Testing a Solution.
Training Guide for Faculty
Mary Torjussen A2 ICT Week 1.
Software Development Life Cycle
Computer Science Testing.
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
Learning Intention I will learn about testing programs.
The Systems Life Cycle: Development and testing
Presentation transcript:

In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing: what’s in the testing phase of a project why we test software how we can test software Software Development Lifecycle

Implementation Evaluation Testing Design Analysis Software Development Life-cycle

Analysis The analysis phase of a project involves looking at what the user wants. You might consider: features required, including hardware, operating system, user interface, etc. performance criteria data flow – including links to other systems skill level of the users different levels of user – e.g. administrators appearance – e.g. use of logos, corporate colours, etc.

Design The design phase of a project involves thinking about how you are going to create the software. You might consider: which programming language you are going to use data structures or database tables required the layout of the screen any addition files required, e.g. images, data files, cookies, etc. calculations required algorithms required as pseudo-code or flow-charts the test plan or testing procedure

Implementation The implementation stage is actually making the software. In a commercial setting, the end result will be the product that’s finished ready for testing. Comments should be included in the code to make it easy to maintain. In an educational setting – e.g. for GCSE coursework – you may need to “write up” what you’ve done; i.e. a commentary on how you created your program and how it works.

Testing Why would you need to test anything that you make? to make sure that it meets the requirements of the end-user to make sure that it works correctly, and there aren’t any bugs Ideally, who would do the testing?

Testing The requirements can either be: Quantitative – things you can measure and say for sure whether they’ve been done, e.g. there must be 10 slides Qualitative – things that are subjective, or a matter of taste, e.g. it must be easy to use, it must respond quickly Quantitative things are usually easier to test for using a test plan, e.g. validation…

Testing Validation If you created a system that performs calculations or includes validation, how would you test it? Create a test plan including sample values to try: –Normal data – the types of values you would normally expect –Extreme (or boundary) data – values that are right on the edge of what is acceptable –Erroneous – values that should be rejected

Testing Validation For example, in a system that processed marks from students’ exams there is a field for you to enter the percentage scored in the test. What values should you try in your test plan? –0–0 –100 –Something in the middle – e.g. 50 –101 –-1 Would they be accepted or rejected?

Testing Your Spreadsheet Why could you test in your software? Does it include all of the things you said you’d include? Do all of the calculations, etc., work properly? Is it suitable for your audience: –Do the colours make it easy to read? –Does the sorting, etc., happen quickly enough? –How would you decide what “quickly enough” is?

Writing a Test Plan A test plan usually takes the form of a table that includes tests to check whether: everything that the user requested has been included the boxes, buttons, etc., are the right size and behave as expected the system works with a set of typical data The usual method is to describe and action and then what you’d expect to see happen. There should be enough detail for someone else to follow.

Test Plan Template If you use my template, then... Initial Control States is the section where you check that With spreadsheets, changing the value in one cell (or clicking a button) can make something change elsewhere – you test that this happens correctly in the Dependent Control States section System Testing – does the software all work together once you use some typical data (you could use the files provided)