Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials Waterfall, Scope, Project.

Slides:



Advertisements
Similar presentations
Internet Librarian 2007 Project management workshop 28 th October 2007 Mary Auckland Project management workshop 28 th October.
Advertisements

Test process essentials Riitta Viitamäki,
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Software Development Life Cycle
SWE 316: Software Design and Architecture Objectives Lecture # 01 Prologue: The Software Process SWE 316: Software Design & Architecture  To review software.
The “Lifecycle” of Software. Chapter 5. Alternatives to the Waterfall Model The “Waterfall” model can mislead: boundaries between phases are not always.
Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials Implementation and Testing.
Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials File Handling.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Lesson 1-Introducing Basic Network Concepts
CS 5150 Software Engineering
System Design and Analysis
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Copyright © 2003 Bolton Institute Dept. of Computing and Electronic Technology - Multimedia Integration and Applications Lecture 3 - Project Planning.
Fundamentals of Information Systems, Second Edition
Software lifecycle. CS351 - Software Engineering (AY2004)2 Software lifecycle “student view” Design & Specification Coding Testing (optional) Hand it.
Lecture 6 - Project Planning. Lecture 6: Project Planning Overview Creating an outline plan –Work Breakdown Structure –Identifying tasks Waterfall and.
Connecting with Computer Science, 2e
CS CS 5150 Software Engineering Lecture 20 Acceptance and Delivery.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Chapter 1 The Uniqueness of Software Quality Assurance
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.
Introduction to Systems Analysis and Design Trisha Cummings.
CSI315 Web Applications and Technology Overview of Systems Development (342)
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Prologue: The Software Process. Main Phases of Software Process 1. Requirements Analysis (answers “WHAT?”) Specifying what the application must do 2.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
GROUP 1 Advantages of electronic system over its corresponding traditional system.
Software Engineering Management Lecture 1 The Software Process.
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT three UNIT Four Project UNIT Five Preview Project Status Summary.
ISYS 562 Microcomputer Business Applications David Chao.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
Top Down View of Estimation Test Managers Forum 25 th April 2007.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Test and Review chapter State the differences between archive and back-up data. Answer: Archive data is a copy of data which is no longer in regular.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
An Introduction to Software Engineering
Systems Development Life Cycle
10 Aug 2010 ECE/BENG-493 SENIOR ADVANCED DESIGN PROJECT Meeting #2.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 26 Delivering the System.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lecture Notes - Richard Ssembatya1 Information System Project Management Lecture Five By Richard Ssembatya MSc. Cs, BSc CS, CCNA, IT Essentials, ICDL Institute.
Introduction to System Analysis and Design MADE BY: SIR NASEEM AHMED KHAN DOW VOCATIONAL & TECHNICAL TRAINING CENTRE.
1 Lesson 5 Computer-Related Issues Computer Literacy BASICS: A Comprehensive Guide to IC 3, 3 rd Edition Morrison / Wells.
Starter To complement our notes and learning from last lesson (Topic 10 Introducing Large ICT Systems: Features of Large ICT Systems), fold your piece.
Unit F451 Computer Fundamentals Components of a Computer System Software Data: Its representation, structure and management in information.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
ICS 3UI - Introduction to Computer Science
IL Marking Get out your CPU / Memory answers Swap with someone else
Software Engineering Management
Software Project Management
CS 5150 Software Engineering
Models of Software Development Life Cycle (SDLC)
Requirements and the Software Lifecycle
Software Project Management
Introduction to Systems Analysis and Design
Computer Science Life Cycle Models.
Software life cycle models
Project management Learning Unit 5.
CS310 Software Engineering Lecturer Dr.Doaa Sami
Implementation of ICT-related solutions
Software Development Life Cycle Models
Identifying the Work to Be Done
Presentation transcript:

Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials Waterfall, Scope, Project Proposal

Alford Academy Business Education and Computing2 Lesson Objectives Waterfall model (arguments for and against) Project Scope Project Proposal

Alford Academy Business Education and Computing 3 Waterfall Model Proceed from one phase to the next in a purely sequential manner. Complete the analysis producing a requirements specification, which are set in stone. Proceed to design. When design is completed a blueprint is drawn for implementers (coders) to follow — this design should be a plan for implementing the requirements given. Implementation is followed by testing, debugging and then maintenance.

Alford Academy Business Education and Computing 4 Waterfall Model Arguments ForArguments Against  Errors found in the early stages of the development process (such as requirements specification or design) is cheaper, in terms of money, effort and time, to fix than the same bug found later on. It has been estimated that a requirements defect that is left undetected until implementation or maintenance will cost 50 to 200 times as much to fix as it would have cost to fix at requirements time.  This approach places emphasis on documentation – each stage has its own form of documentation. Easier to manage in the event of eg programmers leaving a company, etc  A structured and disciplined approach that requires each stage to be 100% complete and perfect before moving onto the next stage. Many argue that it is impossible, for any non-trivial project, to get one phase of the software development process perfected before moving on to the next phases and learning from them. For example:  Clients may not be aware of exactly what requirements they want before they see a working prototype and can comment upon it;  Clients may change their requirements constantly, and program designers and implementers may have little control over this.

Alford Academy Business Education and Computing 5 Project Management Triangle Like any human undertaking, projects need to be developed and delivered under certain constraints. The amount of time available to complete a project The budgeted amount available for the project What must be done to produce the project's end result

Alford Academy Business Education and Computing 6 Example – Introducing A New Course Cost - £500 to cover: photcopying, laminating and binding course booklets Toner cartridge and laser printer paper for course notes and PPT slides Scope – develop 7 topic PPT introductions, write course notes, self-assessment questions, end of topic tests. Schedule – 1 month

Alford Academy Business Education and Computing 7 Scope of SD Projects Small scale projectMedium scale projectLarge scale project Student AH Computing Project Installing a home network Computerising a small GP practice Computerising small library with web access Updating office filing system from manual to electronic College extending its LAN to a WAN Multi-national company providing Internet Services Supermarket chain introducing new technologies in all branches Computer Systems: 1-10Computer Systems: Computer Systems: 10,000+

Alford Academy Business Education and Computing 8 Project Proposal Starts with perceived need of the client Can be an individual but generally a business or company that needs change Change can be to an existing system or the installation of a new system Proposal put together by management team

Alford Academy Business Education and Computing 9 Project Proposal 1. Scope and objectives to solve the problem 2. Outcomes 3. Major Risks 4. Resources and Time 5. Outputs Formal document which goes to tender

Alford Academy Business Education and Computing 10 Activities Look at the format of a typical project proposal on pages 8-9 of the Scholar booklet Answer Review questions 1-3 on page 10 of the Scholar booklet Homework – Read pages 2-9 of Scholar booklet and begin to prepare your own summary notes – you may wish to copy some of the text and tables from the Scholar website