welcome to cap 312

Welcome to CAP 312Software Engineering

Tutorial

Latifa AlAbdlkarim [email protected] 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


Why?


Tutorial objectives Direct application for the SW

engineering activities. Discuss real software development

case studies.


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.


What?


Software Requirements

MS Project 2007. MS Office Visio 2007.


How?


Tutorial sessions

Explain

project phase

Phase discussion and

problems’

solutions

Phase Presentatio

n

Session Session

General topicsProject


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.


Project Organization

Coordinator

Analysts

Designers

Programmers

Testers


Roles and Responsibilities (1/3)

Roles Responsibilities

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.




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.




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.


How the project works

CoordinatorMonitor the work

Member Role(analyst/designer/

programmer/tester)

Document (v.1) SQA

Reviewed Document (v.2)

Corrected Document with comments TeacherSQA

Apply the comments from teacher

Document (v.3)


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:


Reviewer name

Comment type

Page number

Section Description

Grading Scheme


Document=7

Total=15

Presentation=3

Average of reviews=5

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.


Forming TeamsMy team is

Less about ME……..

…….More about WE


welcome to cap 312

Documents

project objectives

project documentation

graduation project

complete software system

project worksteam work

design document

team members

teamwork objectives