1. Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

2.  Who? › Getting to know me › Getting to know you  Why? › Tutorial Objectives. › Project Objectives.  What? › Software requirements.  How? › Tutorial sessions › Project work  Teams Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

3. Why? Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

4.  Direct application for the SW engineering activities.  Discuss real software development case studies. Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

5.  Prepare the students’ for their graduation project.  Improve the students’ skills in project documentation.  Enhance the teamwork objectives and skills between the students. Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

6. What? Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

7.  MS Project 2007.  MS Office Visio 2007. Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

8. How? Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

9. Explain project phase Phase discussion and problems’ solutions Phase Presentation Session General topics Project Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

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

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

12. Coordinator Analysts Designers Programmers Testers Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009

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

14. RolesResponsibilities Programmer 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 lalabdulkarim@ksu.edu.sa King Saud University October,2009

15. RolesResponsibilities Coordinator Make sure that all members perform their tasks and submit on time. Negotiate any differences and report immediately to the TA 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 TA. Ensure that updates are made to the report after review by the TA. 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 lalabdulkarim@ksu.edu.sa King Saud University October,2009

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

17.  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 Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009 Reviewer name Comment type Page number SectionDescription

18. Latifa AlAbdlkarim lalabdulkarim@ksu.edu.sa King Saud University October,2009 Document 75 % Document 75 % reviews= 25 % reviews= 25 %