1 / 16

Welcome to CAP 312

Welcome to CAP 312. 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.

zubin
Download Presentation

Welcome to CAP 312

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome to CAP 312 Software Engineering Tutorial

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

  3. 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.

  4. Software Requirements • MS Project 2010. • MS Office Visio 2010.

  5. Tutorial sessions General topics Session Session Project

  6. How the project works • 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.

  7. Phases • You will submit 4 documents, total of 5 phases: • Proposal • SRS • Design • Testing • Presentation

  8. Method • 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.

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

  10. Roles and Responsibilities (1/3) individual individual

  11. Roles and Responsibilities (2/3)

  12. Roles and Responsibilities (3/3) Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

  13. 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 Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

  14. 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: • In shared phases you should write who did what

  15. Discuss Project topics • 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

  16. Discuss Project topics • 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.

More Related