Welcome to CAP 312

Software EngineeringTutorial

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.

Improve the students’ skills in project documentation.

Enhance the teamwork objectives and skills between the students.

MS Project 2010. MS Office Visio 2010.

Software Requirements

Tutorial sessions

Explain project phase

Phase discussion and

problems’ solutions

Phase Presentation

Session Session

General topicsProject

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.

How the project works

You will submit 4 documents, total of 5 phases:1. Proposal2. SRS3. Design4. Testing5. Presentation

Phases

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.

Method

Project organization

In shared phases : Proposal , testing , final document

All the team’s members work. o Non- shared phases:

• software requirements specification, Design , implementation.

• Up to 2 member as main participant and rest of the team as reviewer

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.

individual

individual

Roles and Responsibilities (2/3)

Roles Responsibilities

Programmerindividual

•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 produceTest 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

Roles and Responsibilities (3/3)

Roles Responsibilities

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

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)

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

Software Quality Assurance:

Reviewer name

Comment type

Page number

Section Description

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

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.

Discuss Project topics