PROJECT TITLE

MEMBER 1 (000000)
MEMBER 2 (000000)

Software Engineering I
Islamic University of Gaza
First Semester 2019/2020
 Summary

On the this page, you should write a 150-word summary, summarizing the project
purpose, your effort and other highlights.

i
 Table of Contents

CHAPTER ONE PROJECT OVERVIEW ............................................................. 3

1.1 Project Overview .................................................................................................... 3
1.2 Problem Statement ................................................................................................. 3
1.3 Project Objectives .................................................................................................. 3
1.4 Software Process Model ......................................................................................... 3
1.5 Team Organization ................................................................................................. 3
1.6 Risk Analysis ......................................................................................................... 4
1.7 Hardware and Software Requirements................................................................... 4
1.8 Project Schedule ..................................................................................................... 5
1.9 Monitoring and Reporting Mechanisms................................................................. 5

SPECIFICATIONS .................................................................... 6
2.1 List of Requirements .............................................................................................. 6
2.2 Use Case Diagrams ................................................................................................ 6
2.3 System Scenarios ................................................................................................... 6
2.4 Sequence Diagrams ................................................................................................ 7
2.5 Class Diagram ...................................................... Error! Bookmark not defined.

ii
 CHAPTER ONE
PROJECT OVERVIEW

In this part you should write an overview of this chapter. You should use the sections

below. You have to follow the following format.

1.1 Project Overview

[Write here a summary of the project.]

1.2 Problem Statement

[Describe the current problems of the current system and why we need the new

system.]

1.3 Project Objectives

[State here the main objectives that should be achieved by completing the project.]

1.4 Software Process Model

[Describe the process model (e.g. Waterfall, Incremental, Scrum, etc.) you are going

to use. Show a figure for the model and justify your selection of the model]

1.5 Team Organization

[The name and the responsibilities of each team member working in this project. Use

table]

3
1.6 Risk Analysis

[Risk analysis goes here. You may use the following table]

Rank table

Impact
Probability H
L
L H

ID Risk Description Probability Impact Rank Risk Plan

1 Team turnover 10% Low Your action

2 HW Resources 50% High

3 Medium

1.7 Hardware and Software Requirements

[Describe all the hw and sw requirements needed in the project]

4
1.8 Project Schedule

[Define the work breakdown structure of the project. Draw Gantt Chart using suitable

tool (e.g. MS Project) ]

ID Task Title Expected Time Preceding Task(s)

1 Meeting the customer 3d -

1.9 Monitoring and Reporting Mechanisms

[State the reporting mechanisms you should use to provide project status,

communication and documentation]

You may add more sections as you see.

5
 SPECIFICATIONS

This chapter talks about specification activity.

2.1 List of Requirements

[You need to add a table of the system requirements based on the users of the system]

No. Requirement M/O

1 Customer sign in to the system M
2
3

2.2 Use Case Diagrams

[You need to draw the use case diagram for the whole system here]

2.3 System Scenarios

[You need to add the use case descriptions here for the key services in your system]

Requirement Sign in
Actor Customer
Description This requirement allows the user to access the system.
Pre-condition(s) The customer must get username and password
1. The customer open the main page of the system.
2. The customer inputs the username and password.
Basic Flow 3. The customer clicks sign in button.
4. The system checks the customer's inputs. [E1: Invalid inputs]
5. The system views the customer main page.

6
Alternative(s) -
E1: Invalid inputs
Exception(s) The system shall view an error message to the customer to
correct the inputs.
Post-condition(s) The customer can access the system.
Non-Functional
Requirement(s)
- The username must be the customer ID
Business Rules
- The password must be 8 characters.
Comment(s)

2.4 Sequence Diagrams

[You need to draw the sequence diagrams here for the key services in your system]