190 likes | 300 Views
Welcome to CAP 312. Software Engineering Tutorial. Overview. Who? Getting to know me Getting to know you Why ? Tutorial Objectives. Project Objectives. What? Software requirements. How ? Tutorial sessions Project work Teams. Why?. Tutorial objectives.
E N D
Welcome to CAP 312 Software Engineering Tutorial LatifaAlAbdlkarimlalabdulkarim@ksu.edu.sa King Saud University October,2009
Overview Who? Getting to know me Getting to know you Why? Tutorial Objectives. Project Objectives. What? Software requirements. How? Tutorial sessions Project work Teams LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Why? LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Tutorial objectives Direct application for the SW engineering activities. Discuss real software development case studies. LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
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. LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
What? LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Software Requirements • MS Project 2007. • MS Office Visio 2007. LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
How? LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Tutorial sessions General topics Session • Session Project LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
How the project works • Team work of (7) 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. LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Project Organization Analysts Designers Coordinator Testers Programmers LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Roles and Responsibilities (1/3) LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Roles and Responsibilities (2/3) LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Roles and Responsibilities (3/3) LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
How the project works Document (v.1) Member Role (analyst/designer/ programmer/tester) Document (v.3) Reviewed Document (v.2) Coordinator Monitor the work SQA SQA Apply the comments from teacher Corrected Document with comments Teacher LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Software Quality Assurance: • Review and evaluate the first version of the document. • Show the good and poor points in the document. As illustrated in the table below: LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Grading Scheme Document=7 Presentation=3 Average of reviews=5 Total=15 LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Next Session • Read about team work problems and suggested solutions. • Next week discussion: What does the team work mean to you ? • Answer using Mind Map. So don’t forget your coloring pens. LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009
Forming Teams My team is Less about ME…….. …….More about WE LatifaAlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009