Conference management system Jordanian Renewable Energy Society (JRES) Team members.

Post on 28-Dec-2015

215 views 0 download

transcript

conference management systemJordanian Renewable Energy Society (JRES)

Team members

Outline

• Introduction • Requirements Collection

– Interviews– Questionnaires

• Requirements Analysis• Entity Relationship Diagram (ERD)• Data Flow Diagram (DFD)• Process Specification• Data Dictionary • Summary

Introduction

• what is systems analysis ?• How we collect the requirement in our

project?

• What we learned in this phase ?

Requirements Collection

• Interviews:Dr. Waheeb Eissa Al-Nasser , Professor of Applied Physics at the University of Bahrain

http://www.ecssr.com/ECSSR/print/prf.jsp?lang=en&prfId=/Profile/Profiles_0334.xml

Requirements Collection

• Questionnaires

•It is easy and safe to register and pay online ? •I was have a speakers (CV) ?

Requirements Analysis

• functional requirementsF4 Create schedule

Description: This function to manage the time table of the sessions , also it show start and end time for the session .

Activities: It shell allow Manager to organize the session time table

Date: Every conference .

Source of requirement : Interview

Priority : This function should be the main function in the system, it create the conferences.

Requirements Analysis

• Non-Functional RequirementNon-functional requirement type ExplanationBrowser based The user can access the system from any ware , just

he/she need a good internet connection .

XHTML compatible The interface will be same for all internet browsers, so the user can access the system by any browser.

Email interaction between system users The system user will receive notification by email or SMS.

Ability to support customized reports The system has the ability to generate deferent type of reports.

Able to run different Server Operating System: Windows / Linux based

The system can be run in Linux / Windows system because it creates using PHP and only need an apache and MySql database which can be run in different OS.

Privacy The system shall protect the privacy of user, by using groups.

Entity Relationship Diagram (ERD)

•What is ERD ?

Entity Relationship Diagram (ERD)

Data Flow Diagram (DFD)

•What is DFD?

http://en.wikipedia.org/wiki/File:DataFlowDiagram_Example.png

Data Flow Diagram (DFD)

Context Diagram

Data Flow Diagram (DFD)

Level Zero

Data Flow Diagram (DFD)

Level one - Manager

Data Flow Diagram (DFD)

Level One – Director

Data Flow Diagram (DFD)

Level One – Author

Data Flow Diagram (DFD)

Level One - Attendee

Data Flow Diagram (DFD)

Level One – Reviewer

Data Flow Diagram (DFD)

Level One – Sponsor

Process Specification

• Defining Process

– Process ID : 5.1– Process Name : add new user – Process Description: add new user to user list .– Input: user info.– Logic :

IF all user information correct add new user to databaseElse Re-enter user information EndIf

Process Specification

• Decision Table1 2 3 4 5 6 7 8 9 10 11 12

Country I O I O I O I O I O I O

Visa - Y - N - Y - N - Y - N

Registration due

E E E L L L O O O E E E

Early Registration

price

X X X X X

Late Registration

price

X X X

On-Site Registration

price

X X X

Data Dictionary

• DataflowID: F2

Name : Presenter name

Description Contain Presenter name

Source : external entity (Director)

Destination: Process 6.10

Type: Form

Volume/Time 4/Day

Comments: Contain Presenter name that will be added to the schedule .

Data Dictionary

• Defining ElementsName Num_page

Alias Page_num , number_of_pages,

Description Number of pages in the paper

Length 6

Input Format 9(6)

Output Format 9(6)

Default Value

Continuous/Discrete Discrete

Type Numeric

Base or Derived Derived

Upper Limit <6000

Lower Limit 1>

Comments This element for the number of pages.

Data Dictionary

• Defining Data StoresID D1

Name Users

Alias -

Description Store user information

File type ComputeFile format Database

Record size 150

Maximum record

40000

Average record 35000

Percent growth/years

10%

Data set/table name User

Data structure User record

Primary key uid

Secondary keys -

Comments This data store will used to store the users information

Summary

• We are talk about the requirement analysis, and provide the system according that results.

QUESTIONS

Finally, I'll be happy to answer your questions

Thank You