ELECTRICAL DEVICES MARKETING

Submitted by :

MAHMOUD A. GHANEM 120070793

Supervisor:

ENG. MOHAMMED EL-SER

The Islamic University – GazaComputer Engineering DepartmentSoftware Engineering

Proposal

Purpose and Objectives

give customer detailed idea about the laptop.

I t should be easy to use in order to save time.

Any producer can show his products. Not anyone can add information about his

products. provide a service for the customers

suggestions

External Audiences Reached

Customersproducers

Project Scope and Possible Execution

Start in 25, February 2010

End in (deadline) 10, June 2010

Budget/Resources:

Possible Complications/Challenges

The team will be using new tools. Time is short. we face the electricity .

Responsibilities and Coordination Group 1 : ( Ahmed K. Ayash and Ahmed AlGhamry):

This group will start collecting information about the project, and listing the requirements for the first two weeks of the timetable, and make it ready for the design process.

  Group 2 : (Mahmoud A. Ghanem):

While the first group preparing the requirements, this group will start training on the tools needed for the design process, this will take the first two weeks and may be expanded for more weeks if needed.

 

Software RequirementsSpecification

(SRS)

Purpose: provides a complete and clear view of the software.

Intended Audience and Reading Suggestions

Project Scope: few seconds not in many days.

I. Introduction

II. Overall Description

Product Perspective: The idea is great but it's not impossible.

System Interfaces:

System Webpage

Customers Producers

Administrator

Database

User Interface:

II. Overall Description (continue)

Operations: easy to user.

Software Interfaces: ASP. Net or Adobe Flex.

Communications Interfaces: web browser.

Product Features: producers store products in web database and customer reach to it.

User Classes and Characteristics: (Administrators, producers, Customers).

Operating Environment: internet connections and

flash player.

II. Overall Description (continue)

Design and Implementation Constraints: time and

experience.

User Documentation: manual.

Assumptions and Dependencies: training.

II. Overall Description (continue)

III. Specific Functional Requirements:

Database Administrator : (CRUD) System Webpage Producers Customers

System Webpage

Customers

Producers

Administrator

Database

IV. Other Nonfunctional Requirements

Performance Requirements Security Requirements Software Quality Attributes

UML

Classes

Classes (continue)

Class Diagram:

Use case diagram:

Sequence diagram: