Software Engineering Tutorial. Tutorial objectives  Direct application for the SW engineering activities.  Discuss real software development case studies.

Slides:



Advertisements
Similar presentations
System Construction and Implementation Objectives:
Advertisements

T /5115 Software Development Project I/II Project Planning Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Unit 191 Introduction to Software Engineering The objective of this section is to introduce the subject of software engineering. When you have read this.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
Tutorial Week 7 PPM feedback PSR and Project Review Report.
Planning. SDLC Planning Analysis Design Implementation.
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
SQA Work Procedures.
Release & Deployment ITIL Version 3
Even More SQA: Work Procedures
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
IT 499 Bachelor Capstone Week 9.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software Quality Assurance Activities
Multi-agent Research Tool (MART) A proposal for MSE project Madhukar Kumar.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Planning and Writing Your Documents Chapter 6. Start of the Project Start the project by knowing the software you will write about, but you should try.
1 Software Development Configuration management. \ 2 Software Configuration  Items that comprise all information produced as part of the software development.
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.
2/6/01D-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Using PARTS to Illustrate Requirements Concepts.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT three UNIT Four Project UNIT Five Preview Project Status Summary.
© Copyright 2011 John Wiley & Sons, Inc.
Georgia Institute of Technology CS 4320 Fall 2003.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Introduction to Making Multimedia
Latifa AlAbdlkarim King Saud University October,2009.
CSSE 371 – Software Requirements and Specification Sriram Mohan.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Software Engineering Lecture # 1.
K-12 Teaching Application Support and Software Ongo-08 Client Dr. John Lamont Prof. Ralph Patterson Advisor Dr. Gregory Smith Team Members Sean Boyle Tony.
Chapter 3-Multimedia Skills
Lesson 3-Multimedia Skills. Overview Members of a multimedia team. Roles and responsibilities in a multimedia team.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
Testing and Evaluating Software Solutions Introduction.
ISIS Project Status Report May 18, 2006 Prepared by MAXIMUS, Inc Education Systems Division for the ABT Committee.
CASE Tools and their Effect on Software Quality
Advanced Higher Computing Science The Project. Introduction Worth 60% of the total marks for the course Must include: An appropriate interface using input.
The Software Development Process. Contents  Product Components  Software project staff  Software development lifecycle models.
OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.
Advanced Higher Computing Science
Module 4: Structuring the District Implementation Team for Success
Supporting quality devices
Software Verification and Validation
Responsibilities & Tasks Week 2
Mastering the Fundamentals of RESTful API Design
9/18/2018 Department of Software Engineering and IT Engineering
Roberta Roth, Alan Dennis, and Barbara Haley Wixom
Chapter 10 Development of Multimedia Project
Roles and Responsibilities (1/3)
Tools of Software Development
Software Quality Engineering
Chapter 1 (pages 4-9); Overview of SDLC
“Would I have to do this all by myself …….?”
homework assignment due Feb 23
Welcome to CT1315 Project1 Latifa AlAbdlkarim King Saud University October,2009.
QA Reviews Lecture # 6.
CIS 4328 – Senior Project 2 And CEN Engineering of Software 2
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

Software Engineering Tutorial

Tutorial objectives  Direct application for the SW engineering activities.  Discuss real software development case studies.  Solve exercises if any.

Project Objectives  Prepare the students’ for their graduation project.  Improve the students’ skills in project documentation.  Enhance the teamwork objectives and skills between the students.

 MS Project  MS Office Visio 2010.

Explain project phase Phase discussion and problems’ solutions Phase Presentation Session General topics Project

 Team work of (5-6) members.  Each team should collaboratively work to produce a complete software system with the documentation.  Team members will be graded on their individual effort within their specific role (see below), as well as the efforts they put in reviewing their peers work.

 You will submit 4 documents, total of 5 phases: 1.Proposal 2.SRS 3.Design 4.Testing 5.Presentation

 You will be handed guidelines / template prior each phase.  It will be posted on blog prior to tutorial.  Feel free to discuss it during tutorial time.

 In shared phases :  Proposal, testing, final document All the team’s members work. o Non- shared phases: software requirements specification, Design, implementation. Up to 2 member as main participant and rest of the team as reviewer

RolesResponsibilities Analyst Collects the requirements from the client Structures the requirements into an SRS document Develops any system models required (STD, SEQ, ER diagrams, Data Dictionary, etc) Submits the SRS document for review by the SQA (Software Quality Assurance) team. Designer Develops the design of the system which includes Architectural design Data design (Schema and data structures) Component design (flowcharts or pseudo code) Interface design (screens + error messages) Submits the design document for review by other the SQA (Software Quality Assurance) team. individual

RolesResponsibilities Programmer individual Using the documentation developed from the previous phases, the programmer should: Write the program code Perform unit testing Perform integration testing (this is usually performed by the testing team, but because our system is small it is better to have the programmer do it) Submit the implementation (source code) for review by the SQA (Software Quality Assurance) team. Tester ALL THE TEAM Using the SRS, the tester should develop A Test plan (can be done once the SRS is ready) Test cases They should perform system testing and produce Test Report Submit the Test Report for review by the SQA (Software Quality Assurance) team.

Latifa AlAbdlkarim King Saud University October,2009 RolesResponsibilities Coordinator Make sure that all members perform their tasks and submit on time. Negotiate any differences and report immediately to the Teacher any team problems, so that they can be solved as early as possible and not left to the end of the term. Collect and submit the report produced by each phase to the Teacher. Ensure that updates are made to the report after review by the Teacher. Collects and combines all the parts of the project Writes the introduction and the conclusion for the report. Submits the final project documentation for review by the SQA (Software Quality Assurance) team.

Latifa AlAbdlkarim King Saud University October,2009 Coordinator Monitor the work Member Role (analyst/designer/ programmer/tester) Document (v.1) SQA Reviewed Document (v.2) Corrected Document with comments Teacher SQA Apply the comments from teacher Document (v.3)

 Review and evaluate the first version of the document.  Show the good and poor points in the document. As illustrated in the table below:  In shared phases you should write who did what Reviewer name Comment type Page number SectionDescription

 Project1: Handling Sub Franchisee information for Edible Arrangements (Web based Project)  Building web based application to support Master Franchisee to record potential sub franchisee information around kingdom. Master Franchisee should be able to:  Change status of each sub franchisee as deal progress.  Track sub franchisee.  Search

 Project2: Warehouse control for Dunkin Donuts (Web based Project)  Building web based application to allow each store manager to order from warehouse. There is one central warehouse that supports all stores in single city. The items in warehouse should be decreased automatically when ever order is complete.