1. Roles and Responsibilities (1/3)
Analyst
Collects the requirements from the client
Structures the requirements into an SRS document
Develops any system models required (DFD, 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 King Saud University October,2009

2. Roles and Responsibilities (2/3)
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
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

3. Roles and Responsibilities (3/3)
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
Latifa AlAbdlkarim King Saud University October,2009

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

5. 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
Reviewer name
Comment type
Page number
Section
Description
Latifa AlAbdlkarim King Saud University October,2009

6. Discuss Projects topics