GCSE OCR 3 A451 Computing Professional standards

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

Database Planning, Design, and Administration
Configuration Management
Commenting and Naming Conventions
Programming Paradigms and languages
Unit 6 Assignment 2 Chris Boardley.
FUNDAMENTALS OF COMPUTER SYSTEMS OCR GCSE Computing.
System Analysis (Part 1)
Documentation 1 Comprehending the present – Investing in the future.
Project activities and experiences in an Albanian software company Luan Jubica Zagreb 2004.
Programming Creating programs that run on your PC
Coding Practices. What are Coding Practices ? Coding practices are a set of informal rules that the software development community has learned over time.
Computer Programming and Basic Software Engineering 4. Basic Software Engineering 1 Writing a Good Program 4. Basic Software Engineering 3 October 2007.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
Planning and Estimating
Ch7: Software Production Process. 1 Questions  What is the life cycle of a software product?  Why do we need software process models?  What are the.
Program Commenting CS-212 Dick Steflik. Commentary Commentary are pieces of information included in a program’s source files to provide additional information.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Maintenance = Software Evolution Any changes after the client has accepted the product is considered maintenance. n Any Changes? n What might these be?
HOMEWORK PAGE STAND ALONE PROGRAMS FUNCTION ON THEIR OWN AND SOMETIMES CANNOT SHARE DATA WITH OTHER PROGRAMS. INTEGRATED SOFTWARE COMBINES.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
4 types of implementing information systems
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Wizards, Templates, Styles & Macros Chapter 3. Contents This presentation covers the following: – Purpose, Characteristics, Advantages and Disadvantages.
Software Construction. Implementation System Specification Requirements Analysis Architectural Design Detailed Design Coding & Debugging Unit Testing.
Managing Software Quality
1 Shawlands Academy Higher Computing Software Development Unit.
1 Software Construction Software Construction Chapter 1.
Implementation Considerations Yonglei Tao. Components of Coding Standards 2  File header  file location, version number, author, project, update history.

Software Engineering CS3003 Lecture 3 Software maintenance and evolution.
Introduction to Algorithm Design and Documentation CSIS 1595: Fundamentals of Programming and Problem Solving 1.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
BTEC Unit 06 – Lesson 08 Principals of Software Design Mr C Johnston ICT Teacher
What Is Wiki ? Wiki is a piece of server software that allows users to freely create and edit Web page content using any Web browser. Wiki supports hyperlinks.
SE: CHAPTER 7 Writing The Program
I Power Higher Computing Software Development The Software Development Process.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
The Software Development Process
Nonbehavioral Specifications Non-behavioral Characteristics Portability Portability Reliability Reliability Efficiency Efficiency Human Engineering.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
Database Design Process For many businesses, the database is the most important set of computer files they have. For some, like EBay or Facebook, the database.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Getting Started With Scratch Brendan Routledge
Starter To complement our notes and learning from last lesson (Topic 10 Introducing Large ICT Systems: Features of Large ICT Systems), fold your piece.
Software Design and Development Development Methodoligies Computing Science.
FUNDAMENTALS OF COMPUTER SYSTEMS Lesson 1. Starter What is the difference between hardware and software?
Software Development Life Cycle Waterfall Model
Software Construction
ICS 3UI - Introduction to Computer Science
Computational Thinking, Problem-solving and Programming: General Principals IB Computer Science.
Configuration Management and Prince2
1. Welcome to Software Construction
Software Design and Development
Software Development Life Cycle
Software Documentation
Understand the Programming Process
TRANSLATORS AND IDEs Key Revision Points.
Software Development Initiation Planning Design Analysis Development
“Would I have to do this all by myself …….?”
Lecture 09:Software Testing
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Unit 6 Assignment 2 Chris Boardley.
Understand the Programming Process
Maintaining a Program In today’s lesson we will look at:
Software Construction
CMSC 345 Programming.
Software Re-engineering and Reverse Engineering
Presentation transcript:

GCSE OCR 3 A451 Computing Professional standards 2-1-1 Fundamentals of computer systems 3

Objectives Understand the need for standards in the development and maintenance of computer systems Give examples of standards in computer systems Understand how standards help to ensure that computer systems are free of errors, easy to maintain and easy to use

Who needs standards? In the UK, we drive on the left Some standards come about through constant usage In the UK, we drive on the left In many other countries, people drive on the right Does this ever cause a problem?

De facto standards De facto standards are ones which come about through common usage Americans write dates in the format MM-DD-YYYY How do we write them? Could this ever cause problems in software usage? Think of some other de facto standards in everyday life and in the context of computing. Are they the same all over the world?

Software development Many computer systems involve tens of thousands or even millions of lines of code Teams of programmers work on the project, each developing a small part of the system People leave, teams change, and new programmers must take over in the middle of a project Good organisation, “rules” and standards are essential!

Stages in creating a computer system Analysis Design Programming Testing Maintenance

Software development standards How to document what the system needs to do How to break the system up into small parts that can be developed by teams of programmers How to allocate staff to teams How to keep track of changes How to code programs How to test How to document the whole system

Standards in Analysis and Design Companies involved in the creation of complex computer systems don’t start from scratch in documenting their design There will be professional standards defining the structure of the document, ensuring that all essential areas are covered You probably know yourself that it is much easier to write a lengthy document explaining your ideas, when you are given a structure to work to

Worksheet 4 Coding standards Then look at Worksheet 5 Suggest how this program could be made easier to understand and amend Then look at Worksheet 5

Programming standards Even a small team of programmers working on a class project would find it difficult to come up with a maintainable system if they had no agreed standards

Developing standards What aspects of the programming and testing need to be agreed on? Suggest some standards that a team of prgrammers might agree before they start

Standards for coding programs Comments in the code Variable names and naming conventions Passing information from one module to another Formatting the code Version names and numbers Suggest some “rules” for certain comments that MUST be included in every module Suggest some “rules” for variable names

Example of standards for program comments Every source code file should begin with a comment block describing the content and its purpose The author and any revision authors should be identified The date of original code and all revisions should be given Comment blocks should be delineated as follows: /********************************/ /Comment Lines….

Benefits of software standards? Efficiency: any member of a software team can work on any part of the software code without having to adapt to a different programming style Fewer errors and easier debugging: standards result in more accurate coding Easy to maintain: any programmer will find it relatively easy to look through the code, understand its structure and find what they are looking for when a change needs to be made

What about the user? Users have certain expectations when they use hardware and software If standards are not followed throughout a piece of software, how does this affect the user? When a user buys a new computer system or a new piece of software, what documentation would they expect to find?

Recap Professional standards cover every phase of software development – analysis, design, development, implementation and maintenance Adherence to standards helps make the development process faster, more efficient, and less error-prone Standards make the end product easier to use Can you give examples to explain each of these points?