University of Bahrain
Information Technology College
Computer Science Department
System Analysis and Design ( ITCS 311)
JRES Conference Management System
Project Group ID: 311S2G12
Done by:
Supervised by:
Dr. Taher Hammed
Miss. Ejlal Al-khuzaie
Date: 03/01/2012
Work Sheet
Title : Final Report
Date of Submit : 03/01/2012
Deadline Date : 03/01/2012
Group : 311S2G12
Group member s:Project Manager : Mohamed Hasan Adel
1st Member : Ali Abbas Saleh
2ed Member : Ismail Khalil Ebrahim
Member Name
Tasks
Comment
Project manager: Mohamed Hasan
1. Write project objective
2. Search for other similar software
3. Write problem definition
4. Select process model
5. Interview
6. Write functional requirements
7. Write non-functional requirements
8. Write process Specifications
9. Write Defining Dataflow.
10. Write Defining Data structures
11. Write Defining Elements
II | P a g e
12. Write Defining Data Stores.
13. Database table
14. Member status
15. interface
1st member : Ali Abbas
1. References
2. Project Activities Plan
3. Interview
4. Create questioner
5. Edit DFD date store
6. Create presentation slide
7. Draw author maintenance
8. Draw notification process
9. Edit DFD
2ed Member : Ismail Khalil
1.
Write the introduction
2.
Create fusibility study
3. Collect information about JRES
4. Interview
5. Write process Specifications
6. Write Defining Dataflow.
7. Describe ERD
8. Write Defining Data structures
9. Check DFD Rules
10. Write Defining Data Stores.
11. Draw registration in conferences
12. Create table of content.
III | P a g e
Contents
CHAPTER 1: INTRODUCTION ............................................................................................................................ 1
1.1 OVERVIEW ........................................................................................................................ 1
CHAPTER 2: SYSTEM PLANNING ....................................................................................................................... 3
2.1 BACKGROUND ................................................................................................................... 3
2.1.1 Definition .................................................................................................................. 3
2.1.2 Jordanian Renewable Energy Society (JRES) .......................................................... 3
2.1.3 Global Green Techies Forum & Exhibition (GTECHs2011) ................................... 3
2.1.4 Problem lead into current system ............................................................................. 4
2.1.5 Information about project and Software environment .............................................. 4
2.1.6 Other solutions and software solve this problem ...................................................... 4
2.2 PROBLEM DEFINITION ....................................................................................................... 8
2.3 OBJECTIVE OF THE PROJECT .............................................................................................. 9
2.4 PROCESS MODEL ............................................................................................................. 10
2.4.1 Iterative and incremental development: ................................................................. 10
2.4.2 Phases: .................................................................................................................... 11
2.5 FEASIBILITY STUDY ......................................................................................................... 12
2.5.1 Economic feasibility: .............................................................................................. 12
2.5.2 Operational feasibility: ........................................................................................... 16
2.5.3 Technical feasibility: ............................................................................................... 16
2.5.4. Schedule feasibility: ............................................................................................... 16
2.6 PROJECT ACTIVITIES PLAN.............................................................................................. 17
2.6.1 Project Tasks: ......................................................................................................... 17
2.6.2. Gantt Chart: ........................................................................................................... 18
2.6.3. PERT (Network) Diagram: .................................................................................... 19
CHAPTER 3: SYSTEM ANALYSIS ...................................................................................................................... 20
3.1 OVERVIEW ...................................................................................................................... 20
3.2 REQUIREMENTS COLLECTION.......................................................................................... 20
3.2.1 Interview ................................................................................................................. 20
3.2.2 Questionnaires ........................................................................................................ 25
3.3 REQUIREMENTS ANALYSIS .............................................................................................. 29
3.3.1 Functional requirements ......................................................................................... 29
IV | P a g e
3.3.2 Non-Functional Requirement.................................................................................. 31
3.4 DATA FLOW DIAGRAM (DFD) ........................................................................................ 32
3.4.1 Context diagram...................................................................................................... 32
3.4.2 Level zero ................................................................................................................ 33
3.4.3 Level one ................................................................................................................. 39
3.5 PROCESS SPECIFICATION ................................................................................................. 44
3.5.1 Defining Process ..................................................................................................... 44
3.5.2 Decision Table ........................................................................................................ 49
3.6 ENTITY RELATIONSHIP DIAGRAM (ERD) ........................................................................ 49
3.6.1 Mapping .................................................................................................................. 51
3.7 DATA DICTIONARY ......................................................................................................... 52
3.7.1 Defining Dataflow................................................................................................... 52
3.7.2 Defining Data structures......................................................................................... 54
3.7.3 Defining Elements ................................................................................................... 54
3.7.4 Defining Data Stores............................................................................................... 57
CHAPTER 4: SYSTEM DESIGN .......................................................................................................................... 61
4.1 OVERVIEW ...................................................................................................................... 61
4.2 DESIGNING SYSTEM DATABASE ...................................................................................... 61
4.3 GRAPHICAL USER INTERFACE DESIGN ............................................................................ 70
4.3.1 Author maintaining ................................................................................................. 70
4.3.2 Notification ............................................................................................................. 81
4.3.3 Registration in the conference ................................................................................ 87
4.3.4 Member Status Report............................................................................................. 97
4.3.5 Attendee Status Report ............................................................................................ 99
4.4 DIALOG DIAGRAM ........................................................................................................ 101
CHAPTER 5: IMPLEMENTATION ................................................................................................................... 102
5.1 OVERVIEW .................................................................................................................... 102
5.2 CASE TOOLS .................................................................................................................. 102
5.2.1 Language used: ..................................................................................................... 102
5.2.2 Software & Suites: ................................................................................................ 102
5.2.3 Hardware: ............................................................................................................. 103
5.2 TESTING ........................................................................................................................ 103
V|Page
5.3 TESTING PURPOSE ......................................................................................................... 103
5.4 TESTING METHODS ........................................................................................................ 103
CHAPTER 6: CONCLUSIONS .......................................................................................................................... 104
6.1 LEARNED FROM THIS PROJECT ....................................................................................... 104
6.2 BENEFIT OF THE REPORT ................................................................................................ 104
6.3 FUTURE WORK ............................................................................................................... 104
REFERENCES:................................................................................................................................................ 105
VI | P a g e
Table of Table
TABLE 1: TEAM MEMBER ......................................................................................................................................... 2
TABLE 2: TABLE OF ONE-TIME-COST..................................................................................................................... 12
TABLE 3: TABLE OF RECURRING COST ................................................................................................................... 12
TABLE 4: TABLE OF TANGIBLE BENEFIT ................................................................................................................ 13
TABLE 5: INTERVIEWS 1 ........................................................................................................................................ 20
TABLE 6 : INTERVIEWS 2 ....................................................................................................................................... 22
TABLE 7:FUNCTIONAL REQUIREMENT 1 ................................................................................................................ 29
TABLE 8: FUNCTIONAL REQUIREMENT 2 ............................................................................................................... 29
TABLE 9: FUNCTIONAL REQUIREMENT 3 ............................................................................................................... 30
TABLE 10: FUNCTIONAL REQUIREMENT 4 ............................................................................................................. 30
TABLE 11 : FUNCTIONAL REQUIREMENT 5 ............................................................................................................ 30
TABLE 12: FUNCTIONAL REQUIREMENT 6 ............................................................................................................. 30
TABLE 13: FUNCTIONAL REQUIREMENT 7 ............................................................................................................. 31
TABLE 14: NON-FUNCTIONAL REQUIREMENT ........................................................................................................ 31
TABLE 15 : DECISION TABLE 1 .............................................................................................................................. 49
TABLE 16: DEFINING DATAFLOW 1 ....................................................................................................................... 52
TABLE 17: DEFINING DATAFLOW 2 ....................................................................................................................... 52
TABLE 18: DEFINING DATAFLOW 3 ....................................................................................................................... 53
TABLE 19: DEFINING DATAFLOW 4 ....................................................................................................................... 53
TABLE 20: DEFINING DATAFLOW 5 ....................................................................................................................... 53
TABLE 21: DEFINING ELEMENTS 1 ........................................................................................................................ 54
TABLE 22: DEFINING ELEMENTS 2 ........................................................................................................................ 55
TABLE 23: DEFINING ELEMENTS 3 ........................................................................................................................ 55
TABLE 24: DEFINING ELEMENTS 4 ........................................................................................................................ 56
TABLE 25:DEFINING ELEMENTS 5 ........................................................................................................................ 56
TABLE 26: DEFINING DATA STORES 1 ................................................................................................................... 57
TABLE 27: DEFINING DATA STORES 2 ................................................................................................................... 57
TABLE 28: DEFINING DATA STORES 3 ................................................................................................................... 58
TABLE 29: DEFINING DATA STORES 4 ................................................................................................................... 58
TABLE 30: DEFINING DATA STORES 5 ................................................................................................................... 59
TABLE 31: DEFINING DATA STORES 6 ................................................................................................................... 59
TABLE 32:ACTIVITY .............................................................................................................................................. 63
TABLE 33: CONFERENCES_SETTING ....................................................................................................................... 63
TABLE 34: CONTACT.............................................................................................................................................. 63
TABLE 35: EMAIL_TEMPLATE ................................................................................................................................ 64
TABLE 36: GROUPS ............................................................................................................................................... 64
VII | P a g e
TABLE 37: NEWS.................................................................................................................................................... 64
TABLE 38: NOTIFICATIONS .................................................................................................................................... 65
TABLE 39: PAPERS ................................................................................................................................................. 65
TABLE 40: PAPER_AUTHORS .................................................................................................................................. 65
TABLE 41: PRESENTERS ......................................................................................................................................... 66
TABLE 42: REGISTRATION ..................................................................................................................................... 66
TABLE 43: REGISTRATION_CONTENT ..................................................................................................................... 66
TABLE 44: REVIWER .............................................................................................................................................. 66
TABLE 45: SCHEDULE ............................................................................................................................................ 67
TABLE 46: SENT_EMAI........................................................................................................................................... 67
TABLE 47: SESSION ................................................................................................................................................ 67
TABLE 48: SPONSORS............................................................................................................................................. 68
TABLE 49: SPONSOR_SESSION ............................................................................................................................... 68
TABLE 50: SUBMIT_PAPER ..................................................................................................................................... 68
TABLE 51: USERS ................................................................................................................................................... 69
VIII | P a g e
Table of Figure
FIGURE 1: OTHER SOLUTIONS AND SOFTWARE 1 ................................................................................................................ 5
FIGURE 2: OTHER SOLUTIONS AND SOFTWARE 2 ................................................................................................................ 6
FIGURE 3 : OTHER SOLUTIONS AND SOFTWARE 3 ..................................................................................................... 7
FIGURE 4 ITERATIVE AND INCREMENTAL DEVELOPMENT 1 .................................................................................................. 10
FIGURE 5 : ECONOMIC FEASIBILITY 4 .................................................................................................................... 14
FIGURE 6 : ECONOMIC FEASIBILITY 5 .................................................................................................................... 15
FIGURE 7: TABLE OF TASKS ................................................................................................................................... 18
FIGURE 8 : GANTT CHART 1 ......................................................................................................................................... 18
FIGURE 9 : PERT (NETWORK) DIAGRAM 1..................................................................................................................... 19
FIGURE 10:QUESTION 1.............................................................................................................................................. 25
FIGURE 11: QUESTION 3 ......................................................................................................................................... 26
FIGURE 12: QUESTION4.......................................................................................................................................... 26
FIGURE 13: QUESTION 5 ......................................................................................................................................... 26
FIGURE 14: QUESTION 6 ......................................................................................................................................... 27
FIGURE 15: QUESTION 7 ......................................................................................................................................... 27
FIGURE 16: QUESTION 8 ......................................................................................................................................... 27
FIGURE 17: QUESTION 9 ......................................................................................................................................... 28
FIGURE 18: DATA FLOW DIAGRAM 1 .................................................................................................................... 33
FIGURE 19: DATA FLOW DIAGRAM 2 .................................................................................................................... 34
FIGURE 20: DATA FLOW DIAGRAM 3 .................................................................................................................... 34
FIGURE 21: DATA FLOW DIAGRAM 4 .................................................................................................................... 35
FIGURE 22: DATA FLOW DIAGRAM 5 .................................................................................................................... 35
FIGURE 23: DATA FLOW DIAGRAM 6 .................................................................................................................... 36
FIGURE 24: DATA FLOW DIAGRAM 7 .................................................................................................................... 36
FIGURE 25: DATA FLOW DIAGRAM 8 .................................................................................................................... 37
FIGURE 26: DATA FLOW DIAGRAM 9 .................................................................................................................... 38
FIGURE 27: DATA FLOW DIAGRAM 10 .................................................................................................................. 39
FIGURE 28: DATA FLOW DIAGRAM 11 .................................................................................................................. 40
FIGURE 29: DATA FLOW DIAGRAM 12 .................................................................................................................. 41
FIGURE 30: DATA FLOW DIAGRAM 13 .................................................................................................................. 42
FIGURE 31: DATA FLOW DIAGRAM 14 .................................................................................................................. 43
FIGURE 32: DATA FLOW DIAGRAM 15 .................................................................................................................. 43
FIGURE 33: ENTITY RELATIONSHIP DIAGRAM 1 .................................................................................................... 50
FIGURE 34: ENTITY RELATIONSHIP DIAGRAM 2- MAPPING ................................................................................................ 51
FIGURE 35: AUTHOR MAINTAINING 1 .................................................................................................................... 71
FIGURE 36: AUTHOR MAINTAINING 2 .................................................................................................................... 73
IX | P a g e
FIGURE 37:AUTHOR MAINTAINING 3 ..................................................................................................................... 75
FIGURE 38: AUTHOR MAINTAINING 4 .................................................................................................................... 77
FIGURE 39:AUTHOR MAINTAINING 5 ..................................................................................................................... 79
FIGURE 40: NOTIFICATION 1 .................................................................................................................................. 82
FIGURE 41: NOTIFICATION 2 .................................................................................................................................. 84
FIGURE 42: NOTIFICATION 3 .................................................................................................................................. 86
FIGURE 43: REGISTRATION IN THE CONFERENCE 1 ................................................................................................ 88
FIGURE 44: REGISTRATION IN THE CONFERENCE 2 ................................................................................................ 90
FIGURE 45: REGISTRATION IN THE CONFERENCE 3 ................................................................................................ 92
FIGURE 46: REGISTRATION IN THE CONFERENCE 4 ................................................................................................ 94
FIGURE 47: REGISTRATION IN THE CONFERENCE 5 ................................................................................................ 96
FIGURE 48: MEMBER STATUS REPORT 1 ............................................................................................................... 98
FIGURE 49: ATTENDEE STATUS REPORT 1 ............................................................................................................. 99
FIGURE 50: DIALOG DIAGRAM ............................................................................................................................ 101
X|Page
Chapter 1: Introduction
1.1 Overview
We are going to create a conference management system to Jordanian Renewable Energy
Society (JRES). Our system will help the JRES to organize the Global Green Techies Forum
& Exhibition (GTECHs2012) and the system will make the work easier and more efficiency.
In addition, the system will reduce organization time of the conference. Also it is will support
the communication between manger of conference and attendee, author and sponsor.
The purpose of this phase is to create relationship with JRES and create project plan. In
addition, discover the environment that the system will work on it, and organize the team on
how to work in this project in chapter 2 we will give brief description about the background
of the JRES and also we introduce some program that solve the problem in the current system
of JRES.
In this report we are going to talk about what we have done in our Conference management
system. In chapter 2 we have create a connection with JRES and we give some information
about them. In chapter 3, we show our collection of requirement and the function and nonfunction of the proposed system, also we drew an ERD and DFD for the system. In chapter 4
we show the design of the some function in system and the database table. In chapter 6 we
have talk about the tools and language that we care going to us it. In the last chapter, chapters
7 we talk about we have learn in this project and what we wish to do.
1|Page
Member of the team will work on this project:
Table 1: team member
ID:
20080055
Name:
Mohamed Hasan Adel
Role:
Manager
Skills :
C++, SQL, VB, Photoshop, Java, PHP, jQuery, C#, Assembly Language, WHM.
ID:
20082382
Name:
Ali Abbas Saleh
Role:
Member
Skills :
C++,Assembly Language ,Java ,Photoshop ,MS Office , Flash, VB
ID:
20071669
Name:
Ismail Khalil Ebrahim
Role:
Member
Skills :
C++,SQL, Assembly Language, Photoshop, Java, SPSS, MS Office
2|Page
Chapter 2: System planning
2.1 Background
2.1.1 Definition
A conference is kind of meeting the people to "confer" and discus about a topic. There are
many type of conference like academic conference in science and academia where some
author present researchers and show there results, and also some activities and workshops
done during the conference.
Conference management system is web-based software that supports the organization of
scientific conferences. It is used to help the organizers of conference to manage their work.
Furthermore, it shows to the authors and the reviewers their activities in the conference. Also,
it is use to schedule the time and program chair(s) of the conference.
2.1.2 Jordanian Renewable Energy Society (JRES)
Jordanian Renewable Energy Society (JRES) is a
society that Established in Jordon and its vision to
stimulate
the
exploitation
of
renewable
energy
resources in Jordan or anywhere, worldwide, and
use that energy efficiently and feasibly for the benefit
of Jordan and for all Arabic countries and invest in the now how of renewable energy
technology for the benefit of the Arabic world and concentrate on the future energy from the
sun. JRES has done some projects in the renewable energy like Jordan Solar Car, Hybrid
System, Hybrid Renewable Energy System and Small Home Application.
2.1.3 Global Green Techies Forum & Exhibition (GTECHs2011)
Global Green Techies Forum & Exhibition (GTECHs2011) hosted by University of Bahrain
(UOB) at kingdom of Bahrain in collaboration with Jordanian Renewable Energy Society
(JRES) aims at encouraging thoughtful evaluation and discussions, regarding the promotion
of renewable energy with the scientists, engineers, technologists, investors and industrialists
will present and exchange ideas, results and experiences in the area of green technologies and
applications.
3|Page
2.1.4 Problem lead into current system
The system of GTECHs2011 uses the manual method; means everyone wants to attend the
conference should take a paper and fill it. Then, submit the paper to society by hand. Also,
the society takes long time while they meet with the authors and organize the conference. In
addition, the society finds a lot of problem when they search about sponsor. Finally, this
system needs a lot of employee and more money.
2.1.5 Information about project and Software environment
We will use in our project a Database that contains all information related with conferences
of the society. Also, we use XHTML and PHP the use the information from database and to
create user friendly system.
The system will be run at online server “apache server” using PHP, HTML, JavaScript and
CSS.
2.1.6 Other solutions and software solve this problem
There are some solutions and software created to solve this problem which covers some part
or feature needed for the system, for example:
1. ConfTool: http://www.conftool.net
The first solution is the ConfTool which has several main features for this system:

Online submission of papers.

Download of the assigned papers by the reviewers.

Submission and administration of reviews.

Support of the PC-meeting, either locally or online by a forum.

Easy assignment of accepted contributions to conference sessions.

Administration of final uploads.

Bulk mailings to reviewers, authors, participants.

Conference participant registration with a flexible registration form generator.

Administration of participants, payments, events and products.

Registration of participants at the conference site.
4|Page
The next figure is a snapshot of ConfTool that displays the interface of the system and what
function that you can use:
Figure 1: other solutions and software 1
2. The Conference Nous: http://www.confious.com/
The second solution is the Conference Nous which has some powerful features like:
- Multi-conference support:
Confious system is provided as a web service. This means that there is no need for separate
installations for each conference served. Confious can support multiple conferences in
parallel, transparent between each other. Therefore, the submission site of your conference
can instantly be created. It takes no more than a single moment to have your conference ready
to accept submissions.
- Paper Assignment Management:
Program Committee Chairs (PCCs) has the option to assign papers either automatically or
manually. The most advantageous process includes an automatic assignment by the system
followed by manual adjustment of assignments by the chairs. The automatic assignment
algorithm takes into account the following constraints:

Matches between paper topics and reviewer's topics of interest.
5|Page

Bids of reviewers to specific papers ("High", "Neutral", "Low").

Conflicts that arise between reviewers that are co-authors of papers.

Load Balance (The number of papers assigned to reviewers usually requires a normal
distribution).
- Dynamic construction of the "Review Form":
The "Review Form" is the form that needs to be completed by reviewers during the reviewing
process. Confious System gives to program committee chair(s) the possibility of constructing
or/and customizing the review form on the fly. Chair(s) has the option to add, update or
delete questions and possible answers from the review form and to specify whether a specific
question will be included in the acceptance/ rejection notification sent to contact persons. The
question types that are supported include radio buttons, text areas, checkboxes and dropdown lists. This is one of the most advantageous features provided by Confious System as it
is not supported by almost any other known conference management system. If you are bored
of static review forms, having always the same format and you would like to have the
potential of providing additional questions to reviewers about a specific paper, then you will
really appreciate this feature.
The next figure is a snapshot of Conference Nous that displays the interface of the system and
what function that you can use:
Figure 2: other solutions and software 2
6|Page
3. X-CD: http://www.x-cd.com/
X-CD is the last solution that does some services to organize the conferences. X-CD used a
cycle steps as shown:
Figure 3 : other solutions and software 3
7|Page
2.2 Problem Definition
There are some problems in the system that the JRES use it to manage and organize their
conference that delays the work and make it so difficult, such as:
1. The attendee need to wait long time before they register, because the employees use
the manual way to register and accept the attendee by filling a register paper and
return to the employees and wait for response by sending an invitation.
2. The society finds a lot of problem while there searching for sponsor; they need to call
them phone and wait until they get response from the sponsor and this operation take
a lot of time to finish.
3. Need a large room to store the paper and archive the old information about pervious
conferences.
4. Hard to contact with attendee and organize the speaker.
5. The data is not accurate; some font of some people is not readable so when the
employee enters the information of this person he may make some mistake.
6. Hard to check back for any information, when the clients want to edit his information,
the employee should search in a lot of paper to cancel the old one and create new one.
7. Hard to collect the reviews, the Exhibitor should write the review in the paper than
submit it to the Box of the society address, than the reviewer should read all the
reviews and divide them in to category and collect group of them to show them to the
manger , a lot of step !
8. The society face difficult while they collect the payment from the attendees and
sponsor.
8|Page
2.3 Objective of the Project
Our project will do a powerful feature that increase the efficiency and support the success of
the conference management system. In addition, it is going to solve all problems faced by the
JRES in its conference by the following:
1. The system will reduce time, for organization, for collecting reviews, for contacting
with attendee and authors.
2. Provide the system with registration feature that make registration easier; the user
now can only use internet to register in the conference.
3. Speed communication with attendee, employee can use SMS or Email or even social
network.
4. Provide the system with online archiving system to the news and archive of the old
conferences, so no need to go to society and search for paper about certain
conference.
5. Allow the sponsor to register in the system online.
6. High security and performance.
7. Easy to check back for any information.
8. Provide system that help in collecting the reviews.
9. Easy assignment of accepted contributions to conference sessions.
10. Administration of participants, payments and events.
9|Page
2.4 Process model
2.4.1 Iterative and incremental development:
Iterative and Incremental development is at the heart of a cyclic software development
process developed in response to the weaknesses of the waterfall model. It starts with an
initial planning and ends with deployment with the cyclic interactions in between.
The basic idea behind the light method is to develop a system through repeated cycles
(iterative) and in smaller portions at a time (incremental), allowing software developers to
take advantage of what was learned during development of earlier parts or versions of the
system. Learning comes from both the development and use of the system, where possible
key steps in the process start with a simple implementation of a subset of the software
requirements and iteratively enhance the evolving versions until the full system is
implemented. At each iteration design modifications are made and new functional capabilities
are added.
Figure 4 Iterative and incremental development 1
10 | P a g e
2.4.2 Phases:
Incremental development slices the system functionality into increments (portions). In each
increment, a slice of functionality is delivered through cross-discipline work, from the
requirements to the deployment. The unified process groups increments/iterations into
phases: inception, elaboration, construction, and transition.

Inception identifies project scope, risks, and requirements (functional and nonfunctional) at a high level but in enough detail that work can be estimated.

Elaboration delivers a working architecture that mitigates the top risks and fulfills the
non-functional requirements.

Construction incrementally fills-in the architecture with production-ready code
produced from analysis, design, implementation, and testing of the functional
requirements.

Transition delivers the system into the production operating environment.
Each of the phases may be divided into 1 or more iterations, which are usually time-boxed
rather than feature-boxed. Architects and analysts work one iteration ahead of developers and
testers to keep their work-product backlog full.
11 | P a g e
2.5 Feasibility study
A feasibility study looks at the viability of an idea with an emphasis on identifying potential
problems and attempts to answer one main question: Will the idea work and should you
proceed with it? , to answer this question you need to study four feasibility categories in any
project:
-
Economic
- Operational
-
Technical
- Schedule
2.5.1 Economic feasibility:
Economic feasibility studies are designed to weigh a host of options, or simply determine if a
venture makes long-term economic sense.
One-Time cost:
Table 2: Table of One-time-cost
Requirement
Price
Hardware
BHD 2000
Software
BHD 550
Communication tools
BHD 100
Worksite
BHD 600
User training
BHD 250
TOTAL
BHD 3500
Recurring cost:
Table 3: Table of recurring cost
Type
Price
Application software upgrade
BHD 500
Hardware maintenance
BHD 500
Communication
BHD 200
Incremental data storage expense
BHD 600
TOTAL
BHD 1800
12 | P a g e
Tangible benefit: the amount of the new benefit that the system is making:
Table 4: Table of tangible benefit
Tangible benefit
Price
Reduce time
BHD 1200
Payment collection
BHD 1000
Electronic Registration
BHD 800
Online Archive
BHD 500
TOTAL
BD 3500
So the result/benefit of this system is:
13 | P a g e
0.12
Discounte rate
Benefits
Year#0
Net economic benefit
Discounte rate
Year#1
BHD 0.000
BHD 1.0000
BHD 0.8929
BHD 0.7972
Year#3
Year#4
Year#5
BHD 3,500.000
BHD 3,500.000
BHD 3,500.000
TOTAL
BHD 0.7118
BHD 0.6355
BHD 0.5674
PV of benefit
BHD 0.000
BHD 3,125.000 BHD 2,790.179
BHD 2,491.231
BHD 2,224.313
BHD 1,985.994
NPV for all benefits
BHD 0.000
BHD 3,125.000 BHD 5,915.179
BHD 8,406.409
BHD 10,630.723 BHD 12,616.717 BHD 12,616.717
BHD 3,500.000
One time cost
Year#0
Recurring Costs
Costs
Year#2
BHD 3,500.000 BHD 3,500.000
Year#1
Year#2
BHD 0.000 BHD 1,800.000 BHD 1,800.000
Discounte rate
BHD 1.0000
PV of Recurring Costs
NPV for all Costs
BHD 0.8929
Year#3
BHD 1,800.000
Year#4
BHD 1,800.000
Year#5
TOTAL
BHD 1,800.000
BHD 0.7972
BHD 0.7118
BHD 0.6355
BHD 0.5674
BHD 0.000 BHD 1,607.143 BHD 1,434.949
BHD 1,281.204
BHD 1,143.933
BHD 1,021.368
BHD 3,500.000 BHD 5,107.143 BHD 6,542.092
BHD 7,823.296
BHD 8,967.229
BHD 9,988.597
BHD 9,988.597
Overall NVP=Total benefits - Total costs
BHD 2,628.120
OVERALL ROI(Overall NVP/NPV for all Costs)
0.26
Break Even Analysis
Year#0
Year#1
Year#2
yearly NPV Cash flow
BHD 3,500.000- BHD 1,517.857 BHD 1,355.230
Overall NPV Cash flow
BHD 3,500.000- BHD 1,982.143-
BHD 626.913-
Year#3
Year#4
Year#5
BHD 1,210.026
BHD 1,080.381
BHD 964.626
BHD 583.113
BHD 1,663.494
BHD 2,628.120
project break-even occurs at year 3
Use first year of overall positive cash flow to calculate break-even fraction
1.463
Actual break-even occurred at 2.5 years
Figure 5 : Economic feasibility 4
14 | P a g e
NPV for all benefits
NPV for all Costs
BHD 14,000.000
BHD 12,000.000
BHD 10,000.000
BHD 8,000.000
BHD 6,000.000
BHD 4,000.000
BHD 2,000.000
BHD 0.000
Year#0
Year#1
Year#2
Year#3
Year#4
Year#5
Figure 6 : Economic feasibility 5
15 | P a g e
2.5.2 Operational feasibility:
Operational feasibility defines the urgency of the problem, the acceptability of any solution
and probability of using the system if it's developed. Our system will be easy and fast for the
employees and attendee, because of the new adding technical (software and hardware).
According to that, our system is feasible and successful to use. Also the system well installed
in online server, so the manger can access the system from everywhere.
2.5.3 Technical feasibility:
It is the capability of available technology that should be considered to pursing further
improvement.
Our system will have new software and hardware like computers and printers, it will also
need some experience and programmers to make an easy and efficient interface for the
system, it also have such functions that can help when system at risk. Also there will be a
database that contains all attendee information and previews conference events. By these
properties, the system will be so efficient and make it easy and fast to help the Society to
create a better conference, also the cost and the number of employee will be decreased.
The system will install in online server to give the users the ability to access from every ware.
2.5.4. Schedule feasibility:
It is the process that study how much time is available to build the new system and when it
can be build. There are several tasks involved in the project, and each task will have duration
time. Beginning of some tasks will depend on the finish the previous task. In our project we
used Gantt chart to determine and organization the specific time for each task, according to
that our system will be feasible in this stage also our development process will help us at any
risk may it happen.
16 | P a g e
2.6 Project Activities Plan
Project planning is part of project management, which relates to the use of schedules such as
Gantt charts to plan and subsequently report progress within the project environment.
Initially, the project scope is defined and the appropriate methods for completing the project
are determined. Following this step, the durations for the various tasks necessary to complete
the work are listed and grouped into a work breakdown structure. The logical dependencies
between tasks are defined using an activity network diagram that enables identification of the
critical path. Float or slack time in the schedule can be calculated using project management
software. Then the necessary resources can be estimated and costs for each activity can be
allocated to each resource, giving the total project cost. At this stage, the project plan may be
optimized to achieve the appropriate balance between resource usage and project duration to
comply with the project objectives. Once established and agreed, the plan becomes what is
known as the baseline. Progress will be measured against the baseline throughout the life of
the project. Analyzing progress compared to the baseline is known as earned value
management.
2.6.1 Project Tasks:
In project management a task is an activity that needs to be accomplished within a defined
period of time. An assignment is a task under the responsibility of an assignee which should
have a start and end date defined. One or more assignments on a task put the task under
execution. Completion of all assignments on a specific task should claim the task as
completed. Tasks can be linked together to create dependencies.
The tasks and duration of our project in each phase:-
17 | P a g e
Figure 7: Table of tasks
2.6.2. Gantt Chart:
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate
the start and finish dates of the terminal elements and summary elements of a project.
Terminal elements and summary elements comprise the work breakdown structure of the
project. Some Gantt charts also show the dependency relationships between activities. Gantt
charts can be used to show current schedule status.
This chart shows the task duration, time overlap and slack time in duration:
Figure 8 : Gantt chart 1
18 | P a g e
2.6.3. PERT (Network) Diagram:
The Program (or Project) Evaluation and Review Technique, commonly abbreviated PERT,
is a statistical tool, used in project management, that is designed to analyze and represent the
tasks involved in completing a given project.
PERT is a method to analyze the involved tasks in completing a given project, especially the
time needed to complete each task, and to identify the minimum time needed to complete the
total project.
This diagram showing the tasks dependencies and overlapping time:-
Figure 9 : PERT (Network) Diagram 1
19 | P a g e
Chapter 3: System analysis
3.1 Overview
Systems analysis is a process of collecting factual data, understand the processes involved,
identifying problems and recommending feasible suggestions for improving the system
functioning. This involves studying the business processes, gathering operational data,
understand the information flow, finding out bottlenecks and evolving solutions
for
overcoming the weaknesses of the system so as to achieve the organizational goals.
System Analysis also includes subdividing of complex process involving the entire system,
identification of data store and manual processes.
The major objectives of systems analysis are to find answers for each business process: What
is being done How is it being done, who is doing it, When is he doing it, Why is it being done
and How can it be improved? It is more of a thinking process and involves the creative skills
of the System Analyst. It attempts to give birth to a new efficient system that satisfies the
current needs of the user and has scope for future growth within the organizational
constraints. The result of this process is a logical system design. Systems analysis is an
iterative process that continues until a preferred and acceptable solution emerges.
3.2 Requirements Collection
3.2.1 Interview
An interview is a conversation between two people (the interviewer and the interviewee)
where questions are asked by the interviewer to obtain information from the interviewee and
to collect some requirement of the system.
In the following table there is some information about interviews that we have make.
Table 5: Interviews 1
Interviewer
Mohammed Hassan , Ali Abbas
and Ismail
Khalil
Location
S40
Objective
Conference management systems problems
Agenda
Date:19\10\2011
20 | P a g e
Time:15:00
Duration: 40 minutes
He was friendly and has a lot of
information about conferences.
Interviewee
Miss. Ejlal Al-khuzaie
Question
Note and answers
Q1. Did you attend conference before?
Yes
Q2. How do you register in the Although Google form they send
conference?
Q.3 Did you face any difficulty when you No, but wasn't secure
register in conference?
Q4. If yes, what is the difficulty and how That I have an account and only special list
we can fix it?
people can see them.
Q5. Did you attend conference as Yes
speaker?
Q6. If yes how do you give your review?
From Facebook, friend and newspaper, Youth
spirit controls it, but it was ok.
Q7. what about services provided by the They have Facebook pages that announce
organizer of the conference?
about their activity and people who like attend
,and some photos
Q8. What are the things that you don't Boring speakers and the registration is offline.
like in the conference?
Q9. What are your suggestions to fix it?
Having a system that will organize event
notification, more exiting feature.
Q10. What are the most Important Attending, guest list and contacts
21 | P a g e
things that should be in the organization Sponsors list and their contacts
of the conference?
Hall reservation, equipment
Album of event
Handout and presentation slide
Video of conference
Ads which get …..
Summary:
She was friendly and ready to answer our questions, after the interview we have benefited a
lot of information about the disadvantages of previous systems and how they work.
Table 6 : Interviews 2
Interviewer
Mohammed Hassan & Ismail Khalil
Location
Main Hall
Objective
Conference management systems problems
Agenda
Date: 9 NOV 2011
Time:13:00
Duration: 45 minutes
He was friendly and has a lot of
information about conferences.
Interviewee
Prof. Dr. Waheeb Essa Alnasser
Question
Note and answers
For the Management part
Q1. What positions that you have Manager ,Reviewer and Attended
taken in the conferences “manager,
reviewers, attended “?
22 | P a g e
Q2.
What
major
challenges
and Main problem are logistic services, sponsorship,
problems did you face when you are organization
committee,
international
corresponding, human resources, team work.
manager of the conference?
Q3. How you communicate with your By E-mail.
team / contact with him?
Q4. How you distribute the task Use technical committee and sub technical
between the team “there is a Director committee for manage all work.
Team, registration team and reviewer
team”?
Q5. What are tools you have used to By E-mail for all author and reviewer and use
contact with author / reviewers?
telephone only with keynote speaker.
Q6. How you manage the schedule of We put poster session for big conference but in
the conference/ is there is any problem small conference we use parallel session and the
problem occurs when they attended want to
you have faced?
attend more than one conference.
Q7. How the acceptance process of By accepting email form the author than we send
papers was done / is there is any it to reviews to chick the rule of the paper. If it
acceptable we contact with the author to notify
problem you have faced?
him about that.
Q8. Did you put a certain rule for Sure, ever session the conference take about
some idea that should be belong to the conference
accepting paper?
title.
Q9. How did you contact with sponsors First we contact with him personally, that we
“by email, ads, meeting”?
email the famous company.
Q10. Did you use the traditional Before we use it, but now we always use the
technique
“manual
way
“for technical way.
registration?
23 | P a g e
Q11. Did you use an on-line system or Yes, we use it now.
process the registration task?
Q12. Which one is better “traditional / Definitely.
online “and why?
Q13.
How
you
are
looking
for Fast communication ,
conferences after 5 or 10 years “New
technologies will be used”?
For attending conference
Q14.
How
you
hear
about Magazine, Email, all social networks.
conferences?
Q15. How did you register in the By online registration, than in the conference
conference “steps”?
they give us a card to premise us to attend the
session and activity.
Q16. Did you face and difficulty while The visa problem
you are registering?
Q17. What is your suggestion to solve Double check everything.
this problem?
Q18. Did you attend a conference as Yes. They contact with me by email
speaker “presenter “/ how they are
contact with you?
Q19. What is the main thing that you -Good organization team.
wish to change it help the conferences -Good research paper.
to be better?
-Full support.
-Fast respond.
-Reduce humanity error.
Summary:
24 | P a g e
He was happy to answer our questions, but he was very busy but we have got important
information about the organization of conferences and difficulties which may face, In
addition to a lot of information and ideas that helped us in building our system.
3.2.2 Questionnaires
A questionnaire is a research instrument consisting of a series of questions and other prompts
for the purpose of gathering information from respondents. Although they are often designed
for statistical analysis of the responses, this is not always the case. We have done an online
questionnaire.
1- Did you attend any conference before?
Figure 10:question 1
Yes
8
No
0
100%
0%
2- How do you complete registration and payment? “simple of answer”
I have use traditional way, so I have to Conference organizer and fill a paper than submit it to
the employee there. Registered and pay in conference office personally. I go to the office of
the conference in a hotel and get a paper and write all my information and return it to the
employee again and pay for them and it get from me a lot of time because I cannot take the
paper and return it after they take it in the same time and also they get their money I fill out a
form and give the necessary cash and documents to a representative. University I write my
name and student...
25 | P a g e
3- Online registration is better than the traditional way?
Figure 11: question 3
Yes
No
7
1
88%
13%
4- I take a lot of time in registration?
Figure 12: question4
Yes 5
63%
No 3
38%
5- I feel comfortable using online registration?
Figure 13: question 5
26 | P a g e
Yes 7 88%
No 1 13%
6- It is easy and safe to register and pay online?
Figure 14: question 6
Yes 6
75%
No 2
25%
7- I was informed of the conference news?
Figure 15: question 7
Yes 5 63%
No 3 38%
8- I was informed of the conference schedule?
Figure 16: question 8
27 | P a g e
Yes 6 75%
No 2 25%
9- I was having speakers (CV)?
Figure 17: question 9
Yes
3 38%
No
5 63%
10- List most negative aspect(s) in the conferences that you have attend? “simple of
answer”
1- long process to register 2- no social network to support them 3- no online website show his
news .-delay in getting news -not much info about the conference -the postpone cuz the poor
info -not very good ID cards-Some systems are left unattended for a long time, often leads to
taking much longer to register without knowing. -Does not feel as good as coming in person.
-Many ways the transaction can be intercepted (key loggers, spyware, phishing, etc).-- risk of
not knowing the contact information of a representative to ask questions. it take a lot of time
to make a request it is not ac...
11- List most positive aspect(s) in the conferences that you have attend: “simple of
answer”
1- Friendly user 2- good organized many -Makes registration easy for both the user and the
registration people. -- easier registration - easier payment - easy update of information more
safe in term of payment you speak with the employees face to face (can explain the request
28 | P a g e
better)- Send to student messages about any important thing like time of start the conference
the hall was very comfortable learn new lesson
3.3 Requirements Analysis
3.3.1 Functional requirements
Functional requirements capture the intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform. Process
requirements relate the entities and attributes from the data requirements to the users’ needs.
State the functional process requirements in a manner that enables the reader to see broad
concepts decomposed into layers of increasing detail.
Table 7:Functional Requirement 1
F1
Description:
Create new conference
This function will help the manager to create new conference contain all
information about the conference e.g. time, activity, session.
Activities:
It shell allow Manager to create new conferences.
Date:
Every conference.
Source of requirement :
Interview
Priority :
This function should be the main function in the
system, it create the conferences.
Table 8: Functional Requirement 2
F2
Add activity
Description:
This function will take all the activity details and add it to the conference.
Activities:
It shell allow Manager to add activity details.
Date:
Every conference.
Source of requirement :
Interview
Priority :
This function will help the attendee to know the
activity in the conferences.
29 | P a g e
Table 9: Functional Requirement 3
F3
Add session
Description:
This function will take all the session details and add it to the conference.
Activities:
It shell allow Manager add conferences session.
Date:
Every conference.
Source of requirement :
Interview
Priority :
This function will help the attendee and the
author to know the sessions in the conferences.
Table 10: Functional Requirement 4
F4
Description:
Create schedule
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.
Table 11 : Functional Requirement 5
F5
Description:
Send notification
This function will help the users of the system to communicate with each
other , they can send a message to each other , the message will saved in
the website and a copy will send to email , also it may send a notification by
SMS .
Activities:
It shell allow the users of the website to communicate with each other
Date:
Source of requirement :
Interview
Priority :
This function will make the communication
between the manager and director and other stuff
in the conferences easier.
Table 12: Functional Requirement 6
F6
Add director
30 | P a g e
Description:
This function will give the manager the ability to add new director or to
upgrade the user to director level.
Activities:
It shell allow the manager to add new director
Date:
Source of requirement :
Interview
Priority :
This function will help the manager to organize
the team in the conference.
Table 13: Functional Requirement 7
F7
Description:
Add reviewer to paper
This function will help the director to retrieve the reviewer list and select
one or more reviewers to each paper.
Activities:
It shell allow the director to select reviewer to each paper .
Date:
Source of requirement :
Interview
Priority :
This function will help the director to organize
the team of reviewer .
3.3.2 Non-Functional Requirement
Non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors.
Table 14: Non-functional requirement
Non-functional requirement type
Explanation
Accessibility
-The user can access the system from any ware; just he/she
need a good internet connection.
-The interface will be same for all internet browsers, so the
user can access the system by any browser.
Usability
-The system user will receive notification by email or SMS.
-The system has the ability to generate deferent type of
reports.
Platform (compatibility)
-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.
security
The system will use sh1 algorithm to encrypt password and
31 | P a g e
use SSL to protect http connection.
3.4 Data Flow Diagram (DFD)
3.4.1 Context diagram
The Data Flow Diagram is commonly used also for the visualization of structured design data
processing. The normal flow is represented graphically. A designer typically draws context
level DFD first showing interaction between the system and the outside entities. Then this
context level DFD will then be exploded in order to further show the details of system being
modeled.
A DFD is one of the three essential perspectives of Structured Systems Analysis and Design
Method (SSADM). In this method, both the project sponsors and the end users need to
collaborate closely throughout the whole stages of the evolution of the system. Having a DFD
will make the collaboration easy because the end users will be able to visualize the operation
of the system, the will see a better perspective what the system will accomplish and how the
whole project will be implemented.
32 | P a g e
Login info
authorization
Proposal
Author
0
Notification about paper
Paper
Presenter name
New sponsor info
Conference dates
Presentation time
Conference schedule
Director list
Paper Rules
Account info
Bank
Manager
Report
Author credit card info
Authorization
JERS Conference
Management System
Reviews list
Selected reviewer
Ads in website
Registration info
Conference activity and schedule
Attendee
Director
Paper list
Selected paper to reviews
Selected event
Reviews commnet
Credit card info
Notification about paper
Bill
Reviewer
Paper list
Comment
Login info
Sponsor
Sponsored activity list
Notification about paper
Respond
MOI
Figure 18: Data Flow Diagram 1
In the context diagram level it shows the scope of the system, the manager will create the
conferences, than the authors will send a proposal to the system. Than the system will send a
notification to the manager, the manager will select the director team. The director will select
the reviewer team and add for each proposal one of more review. The reviewer will see the
proposal and add a comment in the proposal. The director will see the reviewer comment. If
the paper accepted, the director will send a notification to the author to send the paper .Also;
the authors will send the name of the speaker, to present the paper in the conference. The
attendee will register in the website and register in the activity or sessions of the conference.
The Bank will take care with all payment process for online payment, And MOI “Ministry of
interior “will take care with Visa process.
3.4.2 Level zero
Level 0 diagram is result of breaking down the context diagram.
33 | P a g e
1
Author
authorization
Proposal
Notification about paper
Paper
Presenter name
Submit
author
paper
proposal
paper
D20
papers
D1
Login info
users
Progress stat
D21 Reviewers
Presentation time
Notification to
director + Director
D12 notifications
Figure 19: Data Flow Diagram 2
Level zero –author
It show how the author will have a one process will take care with all his needed in the
system. Also, it show the data store related with the author.
Account info
Bank
Author credit card info
2
Maintain
payment
process
Credit card info
D9 Registration
Authorization
Figure 20: Data Flow Diagram 3
Level zero – bank
It shows that the bank will take care with payment process in the system.
34 | P a g e
D9 Registration
payment
Registration info
D5 conferences
Conference event
3
Attendee
Conference activity and schedule
Selected event
Maintain
attendee
process
D1
Attendee info
users
D8 Registration_content
Event list
Credit card info
Bill
Attendee info
D4
contact
Figure 21: Data Flow Diagram 4
Level zero – attendee
It shows that the maintain attendee process will take care with registration process in the
system.
Notification about paper
Reviewer
Paper list
Comment
7
Maintain
reviewer
process
paper
Comment
D20
Notification about paper
papers
D12 notifications
Progress stat
D21 Reviewers
Figure 22: Data Flow Diagram 5
Level zero – reviewer
It shows that the maintain reviewer process will take care with registration process in the
system.
35 | P a g e
Sponsored activity list
Sponsor requist
Activation Email
Sponsor
Login info
4
Maintain
sponsor
process
D17 Sponsor_session
Login info
D18
sponsors
Activity list
Sponsored activity list
Figure 23: Data Flow Diagram 6
Level zero – sponsor
It shows that the sponsor will need only two data store and one mine process in this level.
D9 Registration
Visa
Visa
8
Maintain
MOI
process
Notification about visa
Respond
MOI
Figure 24: Data Flow Diagram 7
Level zero – MOI
It shows that the ministry of interiority will take care with visa process in the system and use
registration data store.
36 | P a g e
D6 conferences
D1
users
Name +descr
Director list
Director info
Attendee report
Review info
Author info
D2
5
Email_template
Sponsor list
Title+body+desc+key
D18
sponsors
Sponsor info
Maintain
management
process
Sponsor list
D3
Conferences_setting
D22 Groups
Director list
Selected director
Paper Rules
Group name
+ title + desc
Notification to director
D19
Manager
Conference dates
Conference schedule
Sponsor info
+Hall info
Paper rule
D12 notifications
New sponsor info
Title
+start date
+end date
+desc
Title
+ location + date
+desc
+ location
session
D16
Date + email id
D11 Sent_email
schedule
Director id
+ conference id
D15
Schedule
Activity
D23 director
Figure 25: Data Flow Diagram 8
Level zero – Manager
It shows Manager Data store and one main process for level zero.
37 | P a g e
D10
Paper_authors
D12 notifications
Presenter name
paper Present
time
Notification to reviewer
D1
D7
D20
D13 presenters
Notification
users
news
papers
Reviewer list
6
Ads + news
Maintain
director
process
Paper list
Notification about paper
Reviews list
Selected reviewer
Ads in website
Director
Paper list
Selected paper to reviews
Reviews commnet
Paper list
D21 Reviewers
Date + email id
D11 Sent_email
Figure 26: Data Flow Diagram 9
Level zero – Director
This diagram show the main process that will contain all the function need to the director,
also the data store need.
38 | P a g e
3.4.3 Level one
5.1
Email
Group id
D1 users
Director info
Add new
user
Name
+type
+descr
+manager
5.9
Add
conference info
Author info
Review info
D2
Title
+body
+desc
+key
Email_template
5.2
Add new email
template
Name
+company name
+ phone
+email
D18 sponsors
D19
5.10
Add session
Email template
Session info
Sponsor info
Maintain
sponsor
Sponsor list
Manager
D3 Conferences_setting
D22 Groups
D11
Hall info
+Start_date_reg
+end_date_reg
5.4
+start_date_revw
Add
+end_date_revw
conference
+star_sub_papr
setting
+end_sub_papr
+rules
Group name
5.5
+ title + desc
Add group
5.6
Send email
D1 users
5.7
Send notification
to director
5.11
Add activity
Director
5.12
Add
schedule
Group info
5.13
Add director
Email
Report Report type
Notification
D16 Activity
Activity detail
Schedule
Dates
Director list
Director list
Tite + content
+from id + to id
+date
Create new
conference
Sponsor info
Sent_email
Date + email id
5.8
Conferee info
+ session info
+ activity detail
+schedule
+ director
Paper rule
Title
+time
+ descr
+type
+room
D15
Title
+date
+ descr
+ location
Schedule
Conference id
+ director id
5.14
Create report
Report
session
Title
+ start date
+ end date
+ descr
+ location
+sponsor
Conference
info
5.3
D6 conferences
D23 director
Report
Report
D9 Registration
D1 users
Account info
Bank
Figure 27: Data Flow Diagram 10
Level one – Manager
Show the different process can the Manager use it to control the system. E.g. add new
sponsor to add new sponsor information, create new conference to create new conference and
call with other function related to the conference
39 | P a g e
D7
D11
Tile
+ intro
+body
+thumb
+date
+draft
+user id
+record
news
6.1
Add news
and ads
Ads + news
Sent_email
D13 presenters
6.2
Send email
Date + email id
Email
Name + time + paper id
Review list
D1 users
Send notification
to review
6.10
Present
time
paper
Notification
6.3
Review list
Tite + content
+from id + to id
+date
Presenter name
Add presenter
Director
Notification about paper
D10 Paper_authors
Tite + content
+from id + to id
+date
6.9
Send notification
about paper
6.4
Send notification
to authors
D21 Reviewers
Notification
Paper list
Paper id
+ user id
D20 papers
6.5
Add paper for
each reviewer
Paper list
Reviews commnet
Selected paper to reviews
6.8
Read reviewer
comment
Selected reviewer
D20 papers
Comment
Paper list
6.6
Retrieve paper list
Reviewer list
Paper list
D1
users
6.7
Retrieve reviewer
list
D21 Reviewers
Reviewer list
Figure 28: Data Flow Diagram 11
Level one – Director
This show the director process that generated from Previous process in level 0 , it consist of
needed process to help directors to contact with the reviewer and manager , also it show the
data store related with the Director .
40 | P a g e
D12 notifications
Notification
1.1
authorization
Accept
author
Notification to
director + Director
Proposal
Proposal
D20
1.2
Send
proposal
papers
Author
Paper
Paper
1.3
D12 notifications
D12 notifications
Send paper
Paper notification
Presenter
name
1.4
Send
presenter
info
Presenter name
paper
1.5
Paper id
D21 Reviewers
Show paper
progress
Progress value
Progress stat
Figure 29: Data Flow Diagram 12
Level one – Author
This level for Author in DFD show the main process that help the author to communicate
with the system ,such as send paper to provide the needed tools to make the submission of
paper more easer
41 | P a g e
D1
users
3.1
Attendee info
D4
Registration info
Registration
new
attendee
contact
Activation Email
Contact info
Activation code
D9 Registration
Registration info
3.2
Registration info
Attendee
D5 conferences
Conference event
D8 Registration_content
Registered event
activity
Registration
+session schedule
in
conference
payment
Selected event
Credit card info
Attendee info
Authorization
Credit card info
Credit card info
Bank
3.3
Process
payment
Bill
Authorization
Figure 30: Data Flow Diagram 13
Level one – Attendee
This diagram show the process of attendee .Attendee will register in system and he will pay
to attend the conference after he select the wanted activity and session.
42 | P a g e
Sponsor request
4.1
Notify
manager
D12 notifications
Notification
Sponsor
Activation Email
Session
Login info Login info
Manager
4.2
Accept sponsor
request
Activation Email
Login info
4.4
Sponsored
activity
Session to sponsored
4.3
Show sponsored
activity
D18
sponsors
Sponsor id
Sponsored activity list
Session list
D17 Sponsor_session
D17 Sponsor_session
D19
session
Figure 31: Data Flow Diagram 14
Level one – Sponsor
Show the main function that the sponsor needs to communicate with the system, such as
notify manager to send notification to the manager.
D12 notifications
Notification about paper
7.2
Update
paper
status
Progress stat
+ paper id
Reviewer
7.1
Paper notification Receive /
send
notification
Respond
Respond
Progress value
Comment
paper
D21 Reviewers
Paper list
D20 papers
Comment
+ paper id
7.3
Add
comment to
paper
Figure 32: Data Flow Diagram 15
Level one – Reviewer
This diagram shows the functions and data stores will be used by the reviewer.
43 | P a g e
3.5 Process Specification
Structure English
Process Specification refers to a description of the procedure to be followed by an actor
within an elementary level business activity, as represented on a process model such as a
dataflow diagram model. A common alias is mini space short for miniature specification.
3.5.1 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 database
Else
Re-enter user information
EndIf
Remark
This process will used only by manager.
 Process ID : 5.2
 Process Name: add new email template.
 Process Description: add new email template to send it latter with other
process.
 Input: email title and content.
 Logic :
IF email and title not empty
Add new Email template
Else
Re-enter Email title and content
EndIF
Remark
44 | P a g e
This process will used only by manager.
 Process ID : 6.6
 Process Name : retrieve paper list.
 Process Description: show list of paper that need to reviewer.
 Input: request paper list.
 Logic :
While there are paper in paper table
IF paper didn’t has a reviewer.
Add paper to paper list
End while
Retrieve
paper list
Remark
This process will used only by director.
 Process ID : 6.8
 Process Name: read reviewer comment.
 Process Description: show paper and comment of reviewer.
 Input: request paper list.
 Logic :
While there are paper in paper table
IF paper has a comment.
Add paper to paper list
End while
Retrieve
paper list
Remark
This process only retrieve paper has been commented by reviewer.
45 | P a g e
 Process ID : 1.2
 Process Name: send proposal.
 Process Description: form to send proposal.
 Input: Author id.
 Logic :
IF all proposal information correct
Send notification to director
Else
Re-Enter proposal information
EndIF
Remark
This process will used by Author to send proposal .
 Process ID : 1.5
 Process Name: show paper progress.
 Process Description: show the remaining time for paper to be finish from
reviewer.
 Input: paper id.
 Logic :
Search for paper with author id in reviewer table
IF paper found
Retrieve paper progress value.
Else
Print “paper not reviewed yet“
Remark
These processes will used by Author to show progress that represent the value of time
taken while the reviewer review the paper.
46 | P a g e
 Process ID : 3.3
 Process Name: process payment.
 Process Description: this process will take the credit card information and
retrieve the bill.
 Input: the credit card information.
 Logic :
IF credit card number valid and date not expired
Send request payment to the bank.
Retrieve bill from bake
Else
Re-enter payment information
End IF.
Remark
This process will be used by the system to take the payment form the bank , if the
payment is done the process will retrieve the bill , else it will require the attendant to re-enter
payment information .
 Process ID : 3.1
 Process Name: Registration new attendee.
 Process Description: Attendees register to attend to the conference.
 Input: registration information.
 Logic :
IF all attendee information correct
add new attendee to database
Else
Re-enter attendee information
EndIf
Remark
47 | P a g e
 Process ID : 5.14
 Process Name: create report.
 Process Description: show report for the manger about conference
 Input: report type.
 Logic :
IF report type
Display report type
Else
Re-enter report type
EndIF
Remark
This process will used only by manager.
 Process ID : 6.10
 Process Name: add presenter.
 Process Description: add presenter for a paper
 Input: presenter name, presenter time and paper.
 Logic :
While there are paper in paper table
IF paper didn’t has a presenter.
Add presenter and time to paper
End while
Remark
This process will used only by director.
48 | P a g e
3.5.2 Decision Table
A decision table lists causes and effects in a matrix. Each column represents a unique
combination.
Table 15 : Decision Table 1
1 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
E E E L L L O O O E
E
E
Registration due
Early Registration price
X X X
X X
Late Registration price
On-Site Registration price
X X
X
X
X
X
Table key:
I: in the country.
O: out of the country.
N: no.
Y: yes.
E: Early.
L: late.
O: on the conference time.
3.6 Entity Relationship Diagram (ERD)
An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an information
system.
This ERD shows all entity and relationship between the user of the system and the system.
the table of user will contain all the user information , the user are Attendee , Manager ,
Director , Author and reviewer , the user can take a permission from group table which has
all user title and levels . Paper table will store the paper submit it by the Author, and the
director will use notify relationship to sort notification about the paper to reviewer .Reviewer
will see the paper from paper table and add comment about the paper in review relation .The
attendee will register in the system and all information related with him will stored in
registration and user table. Conference table will contain general information about the
49 | P a g e
conference, more conference information will stored in session, activity, schedule and
conference setting. News table will store the news and Announcement of the website.
Num_page
title
uid
deleted
pid
End_time
End_date
attachment
size
date
Start_time
title
Start_date
title
sid
description
sid
description
language
type
Paper
M
Schedule
puplish
1
Part of
Session
subject
room
location
M
Visa
type
M
communt
1
M
1
1
Present
amount
M
Created by
onSite_Reg_d
M
early_Reg_p
sid
M
M
1
Note
Reviewed
Sponsored by
Belong to
early_Reg_d
phone
email
late_Reg_d
late_Reg_p
Sponsor
deleted
progress
date
1
price
onSite_Reg_p
Company_name
password
M
address
name
N
Submit_paper
date
cid
job
1
M
Director
uid
name
Conference
description
email
Visa
contact
User
payment
M
type
N
Last_date_review
Register
fname
1
Has
lname
Payment_type
country
Last_date_register
date
gender
Mange
Last_date_submit_
paper
Reset_pass
password
1
1
1
Conference_
setting
M
M
date
Notifications
deleted
nid
Start_accept_review
content
1
activate
Autor_rule
From_uid
Start_registration
title
To_uid
Is_read
Has
Start_accept_paper
M
record
M
Add
M
Draft
M
1
is
deleted
Activity
description
location
Member_of
aid
M
1
date
title
1
Send
Public_user
nid
Img_paht
title
News
description
intro
thumb
date
name
deleted
Description
M
Group
body
date
Email_template
level
gid
name
description
eid
Email_key
title
body
Figure 33: Entity Relationship Diagram 1
50 | P a g e
3.6.1 Mapping
Figure 34: Entity Relationship Diagram 2- Mapping
51 | P a g e
3.7 Data Dictionary
A data dictionary, or metadata repository, as defined in the IBM Dictionary of Computing, is
a "centralized repository of information about data such as meaning, relationships to other
data, origin, usage, and format."
3.7.1 Defining Dataflow
Table 16: Defining Dataflow 1
ID:
F1
Name :
Ads + news
Description
Contain advertisement and news
Source :
external entity (Director)
Destination:
Process 6.1
Type:
Form
Volume/Time
1/Day
Comments:
Contain advertisement and news that will be
added to the website.
Table 17: Defining Dataflow 2
ID:
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.
52 | P a g e
Table 18: Defining Dataflow 3
ID:
F3
Name :
Credit card info
Description
Contain Credit card info
Source :
Process 3.2
Destination:
Process 3.3
Type:
Internal
Volume/Time
10/Day
Comments:
Contain Credit card info that will be sent to the
process to complete payment process.
Table 19: Defining Dataflow 4
ID:
F4
Name :
Bill
Description
Contain Bill information
Source :
Process 3.3
Destination:
External entity (Attendee)
Type:
Form
Volume/Time
10/Day
Comments:
Contain Billing information after complete
payment process.
Table 20: Defining Dataflow 5
ID:
F5
Name :
Respond
Description
Contain value accept or reject of the request.
Source :
external entity (Reviewer)
Destination:
Process 7.1
Type:
report
Volume/Time
3/Day
Comments:
Contain reviewer accept or reject.
53 | P a g e
3.7.2 Defining Data structures
Email_template = eid + title + body + email_key + (description)
Groups = gid + title + description + level + [deleted]
News = nid+ title + intro + body + thumb + date +
draft +[ deleted ]+ user_id +
record
sponsors = Sid + name + Company_name + phone + email + password + deleted
Schedule = sid + title + start_time + end_time +room+ (description).
Conference = cid +name+ type + description
Activity = aid+ title + location+ date+ (description)+ [deleted].
Session = Sid+ title + start_time + end_time + location+ (description).
3.7.3 Defining Elements
Table 21: Defining Elements 1
is_read
Name
Alias
Read , status
Description
Show where the notification is read or not
Length
1
Input Format
9(1)
Output Format
9(1)
Default Value
0
Continuous/Discrete
Discrete
Type
Bit
Base or Derived
Derived
54 | P a g e
Upper Limit
1
Lower Limit
0
Comments
This element will work as a Boolean value
Table 22: Defining Elements 2
Name
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.
Table 23: Defining Elements 3
Name
title
Alias
headline
Description
Show the title of Activity
Length
6
Input Format
X(6)
Output Format
X(6)
Default Value
Continuous/Discrete
Discrete
Type
string
Base or Derived
Base
Upper Limit
<999999
Lower Limit
>18
Comments
-
55 | P a g e
Table 24: Defining Elements 4
Name
location
Alias
site
Description
The location of the session
Length
6
Input Format
X(6)
Output Format
X(6)
Default Value
0
Continuous/Discrete
Discrete
Type
string
Base or Derived
Base
Upper Limit
<999999
Lower Limit
>18
Comments
-
Table 25:Defining Elements 5
Name
Description
Alias
Details , more info , information
Description
The location of the session
Length
300
Input Format
X(300)
Output Format
X(300)
Default Value
Continuous/Discrete
Discrete
Type
string
Base or Derived
Base
Upper Limit
<9999999
Lower Limit
>20
Comments
-
56 | P a g e
3.7.4 Defining Data Stores
Table 26: Defining Data Stores 1
ID
D1
Name
Users
Alias
-
Description
Store user information
File type
Compute
File 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
Table 27: Defining Data Stores 2
ID
D19
Name
Session
Alias
-
Description
Store session information
File type
Compute
File format
Database
Record size
150
Maximum record
40000
Average record
35000
Percent growth/years
10%
Data set/table name
Session
Data structure
Session record
Primary key
sid
57 | P a g e
Secondary keys
Comments
This data store will used to store the Session information
Table 28: Defining Data Stores 3
ID
D15
Name
Schedule
Alias
Time table
Description
Store the Schedule of the conference
File type
Compute
File format
Database
Record size
150
Maximum record
40000
Average record
35000
Percent growth/years
10%
Data set/table name
Schedule
Data structure
Schedule record
Primary key
SID
Secondary keys
-
Comments
This data store will used to store the Schedule of the conference
Table 29: Defining Data Stores 4
ID
D21
Name
Reviewer
Alias
Paper reviewer
Description
Store reviewer and paper information
File type
Compute
File format
Database
Record size
150
Maximum record
40000
Average record
35000
Percent growth/years
10%
Data set/table name
Reviewers
Data structure
Reviewers record
58 | P a g e
Primary key
User_id + paper_id
Secondary keys
User_id , paper_id
Comments
This data store will used to store the reviewer and paper information
Table 30: Defining Data Stores 5
ID
D22
Name
Groups
Alias
Groups info
Description
Store group information
File type
Compute
File format
Database
Record size
50
Maximum record
200
Average record
100
Percent growth/years
2%
Data set/table name
Groups
Data structure
groups record
Primary key
Gid_id
Secondary keys
Comments
This data store will used to store the groups information
Table 31: Defining Data Stores 6
ID
D7
Name
News
Alias
Website news , ads , advertisement ,
Description
Store news and advertisement
File type
Compute
File format
Database
Record size
90
Maximum record
10000
Average record
8000
Percent growth/years
10%
Data set/table name
News
Copy Member
59 | P a g e
Data structure
News record
Primary key
Nid
Secondary keys
User_id ,
Comments
This data store will used to store the news and advertisement of the
website
60 | P a g e
Chapter 4: System Design
4.1 Overview
Software design is a process of problem solving and planning for a software solution. After
the purpose and specifications of software are determined, software developers will design or
employ designers to develop a plan for a solution. It includes low-level component and
algorithm implementation issues as well as the architectural view.
Software design can be considered as putting solution to the problem(s) in hand using the
available capabilities. Hence the main difference between Software analysis and design is
that the output of the analysis of a software problem will be smaller problems to solve and it
should not deviate so much even if it is conducted by different team members or even by
entirely different groups. But since design depends on the capabilities, we can have different
designs for the same problem depending on the capabilities of the environment that will host
the solution (whether it is some OS, web, mobile or even the new cloud computing
paradigm). The solution will depend also on the used development environment (Whether
you build a solution from scratch or using reliable frameworks or at least implement some
suitable design patterns).
The design concepts provide the software designer with a foundation from which more
sophisticated methods can be applied. A set of fundamental design concepts has evolved.
They are: Abstraction, Refinement, Modularity, Software Architecture, Control Hierarchy,
Structural Partitioning, Data Structure, Software Procedure, and Information Hiding.
4.2 Designing System Database
Database design is the process of producing a detailed data model of a database. This logical
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a Data Definition Language, which can then be
used to create a database. A fully attributed data model contains detailed attributes for each
entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. However, the term database design
could also be used to apply to the overall process of designing, not just the base data
61 | P a g e
structures, but also the forms and queries used as part of the overall database application
within the database management system.
The design process consists of the following steps:
1. Determine the purpose of your database - This helps prepare you for the remaining
steps.
2. Find and organize the information required - Gather all of the types of information
you might want to record in the database, such as product name and order number.
3. Divide the information into tables - Divide your information items into major
entities or subjects, such as Products or Orders. Each subject then becomes a table.
4. Turn information items into columns - Decide what information you want to store
in each table. Each item becomes a field, and is displayed as a column in the table.
For example, an Employees table might include fields such as Last Name and Hire
Date.
5. Specify primary keys - Choose each table’s primary key. The primary key is a
column that is used to uniquely identify each row. An example might be Product ID
or Order ID.
6. Set up the table relationships - Look at each table and decide how the data in one
table is related to the data in other tables. Add fields to tables or create new tables to
clarify the relationships, as necessary.
7. Refine your design - Analyze your design for errors. Create the tables and add a few
records of sample data. See if you can get the results you want from your tables. Make
adjustments to the design, as needed.
8. Apply the normalization rules - Apply the data normalization rules to see if your
tables are structured correctly. Make adjustments to the tables
62 | P a g e
The following tables show the design of our database that used in implement our system:
Activity
Table 32:Activity
Name
Type
Primary key
Aid
int(11)
Title
varchar(100)
Date
date
Description
text
Location
varchar(100)
conference_id
int(11)
Deleted
tinyint(1)
Foreign key
Null
●
●
conferences_setting
Table 33: conferences_setting
Name
Type
conference_id
int(11)
s_registration
date
e_registration
date
start_review
date
end_review
date
s_submit_paper
date
e_submit_paper
date
Rules
text
Introduction
text
Primary key
Foreign key
Null
●
contact
Table 34: contact
Name
Type
cid
int(11)
user_id
int(11)
type
varchar(100)
value
int(150)
Primary key
Foreign key
Null
●
●
63 | P a g e
email_template
Table 35: email_template
Name
Type
eid
int(11)
title
varchar(100)
body
text
email_key
int(11)
description
text
Primary key
Foreign key
Null
●
Groups
Table 36: Groups
Name
Type
gid
int(11)
title
varchar(60)
description
varchar(200)
level
int(11)
deleted
tinyint(1)
Primary key
Foreign key
Null
Foreign key
Null
●
news
Table 37: news
Name
Type
nid
int(11)
title
varchar(150)
intro
text
body
text
thumb
varchar(150)
date
date
draft
tinyint(1)
user_id
int(11)
record
varchar(150)
deleted
tinyint(1)
Primary key
●
●
●
64 | P a g e
Notifications
Table 38: Notifications
Name
Type
Primary key
Foreign key
nid
int(11)
title
varchar(60)
content
text
from_uid
int(11)
●
to_uid
int(11)
●
is_read
tinyint(1)
date
date
Null
●
Papers
Table 39: papers
Name
Type
pid
int(11)
title
varchar(150)
type
varchar(50)
subject
text
date
date
size
int(11)
attachment
varchar(150)
num_page
int(11)
language
varchar(40)
publish
tinyint(1)
Primary key
Foreign key
Null
Foreign key
Null
●
paper_authors
Table 40: paper_authors
Name
Type
Primary key
paper_id
int(11)
●
user_id
int(11)
●
65 | P a g e
presenters
Table 41: presenters
Name
Type
Primary key
Foreign key
user_id
int(11)
●
paper_id
int(11)
●
schedule_id
int(11)
●
visa
tinyint(1)
Null
registration
Table 42: registration
Name
Type
rid
int(11)
user_id
int(11)
date
timestamp
payment
int(11)
payment_type
varchar(20)
visa
tinyint(1)
Primary key
Foreign key
Null
●
●
registration_content
Table 43: registration_content
Name
Type
Primary key
Foreign key
rid
int(11)
session_id
int(11)
●
activity_id
int(11)
●
Null
●
reviwer
Table 44: reviwer
Name
Type
Primary key
Foreign key
Null
user_id
int(11)
●
paper_id
int(11)
●
progress
int(11)
●
comment
text
●
66 | P a g e
schedule
Table 45: schedule
Name
Type
sid
int(11)
title
varchar(100)
type
varchar(100)
start_time
time
start_end
time
description
text
room
varchar(50)
session_id
int(11)
Primary key
Foreign key
Null
●
●
sent_emai
Table 46: sent_emai
Name
Type
Primary key
Foreign key
email_id
int(11)
●
user_id
int(11)
●
date
date
Null
session
Table 47: session
Name
Type
sid
int(11)
title
varchar(100)
start_date
date
end_date
date
description
text
location
varchar(50)
conference_id
int(11)
deleted
tinyint(1)
Primary key
Foreign key
Null
●
●
67 | P a g e
sponsors
Table 48: sponsors
Name
Type
sid
int(11)
name
varchar(100)
Company_name
varchar(100)
phone
varchar(50)
email
varchar(80)
password
varchar(100)
deleted
tinyint(1)
Primary key
Foreign key
Null
●
sponsor_session
Table 49: sponsor_session
Name
Type
Primary key
Foreign key
sponsor_id
int(11)
●
session_id
int(11)
●
amount
int(11)
type
varchar(50)
Null
submit_paper
Table 50: submit_paper
Name
Type
Primary key
Foreign key
user_id
int(11)
●
paper_id
int(11)
●
conference_id
int(11)
●
date
timestamp
Null
68 | P a g e
users
Table 51: users
Name
Type
uid
int(11)
email
varchar(100)
password
varchar(100)
fname
varchar(50)
lname
varchar(50)
gender
varchar(2)
date
date
address
varchar(100)
country
varchar(50)
rest_pass
tinyint(1)
activity
tinyint(1)
job
varchar(50)
group_id
int(11)
deleted
tinyint(1)
Primary key
Foreign key
Null
●
69 | P a g e
4.3 Graphical User Interface Design
A graphical user interface is a type of user interface that allows users to interact with
electronic devices with images rather than text commands. GUIs can be used in computers,
hand-held devices such as MP3 players, portable media players or gaming devices, household
appliances and office equipment. A GUI represents the information and actions available to a
user through graphical icons and visual indicators such as secondary notation, as opposed to
text-based interfaces, typed command labels or text navigation. The actions are usually
performed through direct manipulation of the graphical elements.
The following show the GUI of some services that provide by our system and how you can
interact with them and also the process or procedure of each of these services.
4.3.1 Author maintaining
From: home > login
User: author that register in JRES Conference.
Task: login in the system.
System: JRES Conference Management System.
Environment: online system.
70 | P a g e
Figure 35: Author maintaining 1
Testing and usability assessment:User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 3.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
71 | P a g e
From: User page > add new paper
User: author.
Task: add new paper to the author .
System: JRES Conference Management System.
Environment: online system.
72 | P a g e
Figure 36: Author maintaining 2
Testing and usability assessment:73 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
1.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
From: user page > my page
User: author.
Task: list paper of the author.
System: JRES Conference Management System.
Environment: online system.
74 | P a g e
Figure 37:Author maintaining 3
Testing and usability assessment:User rated perceptions (average 14 users):
75 | P a g e
Consistency [1 = consistent to 7 = inconsistent]: 3.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.33
Accuracy [1= accurate to 7 =inaccurate]:
2.67
From: user page > my page > share
User: author.
Task: select the conference that the author wants to share in.
System: JRES Conference Management System.
Environment: online system.
76 | P a g e
Figure 38: Author maintaining 4
Testing and usability assessment:77 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.55
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.33
Accuracy [1= accurate to 7 =inaccurate]:
2.57
From: user page > my page > more info > share
User: author that register in JRES Conference.
Task: show the conference information and allow the author to share in.
System: JRES Conference Management System.
Environment: online system.
78 | P a g e
Figure 39:Author maintaining 5
Testing and usability assessment:79 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
1.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
80 | P a g e
4.3.2 Notification
From: user page >notification.
User: author / manager / reviewer / director.
Task: create new notification to send it.
System: JRES Conference Management System.
Environment: online system.
81 | P a g e
Figure 40: Notification 1
Testing and usability assessment:82 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 1.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.53
Accuracy [1= accurate to 7 =inaccurate]:
1.33
From: user page > notification > Green Green.
User: author / manager / reviewer / director.
Task: show notification details.
System: JRES Conference Management System.
Environment: online system.
83 | P a g e
Figure 41: Notification 2
Testing and usability assessment:84 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 4.25
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.23
Accuracy [1= accurate to 7 =inaccurate]:
1.63
From: user page > notification > inbox
User: author / manager / reviewer / director.
Task: show notification list.
System: JRES Conference Management System.
Environment: online system.
85 | P a g e
Figure 42: Notification 3
Testing and usability assessment:86 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
4.3.3 Registration in the conference
From: registration in website.
User: visitor.
Task: register in the system.
System: JRES Conference Management System.
Environment: online system.
87 | P a g e
Figure 43: Registration in the conference 1
88 | P a g e
Testing and usability assessment:User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
1.43
Accuracy [1= accurate to 7 =inaccurate]:
2.47
From: login.
User: visitor.
Task: login in the system.
System: JRES Conference Management System.
Environment: online system.
89 | P a g e
Figure 44: Registration in the conference 2
Testing and usability assessment:User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
1.43
Accuracy [1= accurate to 7 =inaccurate]:
3.67
90 | P a g e
From: main page of the user.
User: author / manager / reviewer / director.
Task: show general information about user.
System: JRES Conference Management System.
Environment: online system.
91 | P a g e
Figure 45: Registration in the conference 3
Testing and usability assessment:92 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 1.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
3.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
From: user page > register in new conference.
User: author / reviewer / director / attendee.
Task: show conference list.
System: JRES Conference Management System.
Environment: online system.
93 | P a g e
Figure 46: Registration in the conference 4
Testing and usability assessment:94 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 1.22
Sufficiency [1 = sufficient to 7 =insufficiency]:
3.33
Accuracy [1= accurate to 7 =inaccurate]:
2.67
From: user page > register in new conference > more info.
User: author / attendee / reviewer / director.
Task: show conference information.
System: JRES Conference Management System.
Environment: online system.
95 | P a g e
Figure 47: Registration in the conference 5
Testing and usability assessment:96 | P a g e
User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.22
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.13
Accuracy [1= accurate to 7 =inaccurate]:
1.67
4.3.4 Member Status Report
From: Admin page > member statue.
User: Manager.
Task: show number of member in each group.
System: JRES Conference Management System.
Environment: online system.
97 | P a g e
Figure 48: Member Status Report 1
Testing and usability assessment:User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 2.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
2.43
Accuracy [1= accurate to 7 =inaccurate]:
2.67
98 | P a g e
4.3.5 Attendee Status Report
From: admin panel > attendee status.
User: Manager.
Task: show number of attendee in each year.
System: JRES Conference Management System.
Environment: online system.
Figure 49: Attendee Status Report 1
99 | P a g e
Testing and usability assessment:User rated perceptions (average 14 users):
Consistency [1 = consistent to 7 = inconsistent]: 1.52
Sufficiency [1 = sufficient to 7 =insufficiency]:
3.23
Accuracy [1= accurate to 7 =inaccurate]:
2.67
100 | P a g e
4.4 Dialog Diagram
Figure 50: Dialog Diagram
This diagram shows the dialog diagram of our system. Home page will be the main page of
our system, than the user can login from login page and redirector from admin panel or
profile according to his group.
101 | P a g e
Chapter 5: Implementation
5.1 Overview
In this phase, the production system is installed, initial user training is completed, user
documentation is delivered, and the post implementation review meeting is held. When this
phase is completed, the application is in steady-state production. Once the system is in
steady-state production, it is reviewed to ensure that we met all of the goals in the project
plan for a satisfactory result.
5.2 Case tools
5.2.1 Language used:
1- HTML
2- PHP
3- JavaScript
4- SQL
5- CSS
5.2.2 Software & Suites:
1- Notpade ++
2- Gedit ‘Linux’
3- LAMP server ‘Linux’
4- WAMP server
5- Photoshop CS4
6- Opera
7- Firefox
8- Internet Explorer
9- Filezilla
10- CodeIgniter
11- MySql
102 | P a g e
5.2.3 Hardware:
Intel Core2 Quad Q6600
250 GB SATA HDD
2 GB RAM
10,000 GB Bandwidth
5.2 Testing
Software testing is an investigation conducted to provide stakeholders with information about
the quality of the product or service under test. Software testing can also provide an
objective, independent view of the software to allow the business to appreciate and
understand the risks of software implementation. Test techniques include, but are not limited
to, the process of executing a program or application with the intent of finding software bugs
(errors or other defects).
5.3 Testing purpose
A primary purpose of testing is to detect software failures so that defects may be discovered
and corrected. Testing cannot establish that a product functions properly under all conditions
but can only establish that it does not function properly under specific conditions .The scope
of software testing often includes examination of code as well as execution of that code in
various environments and conditions as well as examining the aspects of code: does it do
what it is supposed to do and do what it needs to do. In the current culture of software
development, a testing organization may be separate from the development team. There are
various roles for testing team members. Information derived from software testing may be
used to correct the process by which software is developed.
5.4 Testing methods
Black box testing refers to testing a system with no specific knowledge to the internal
workings of the system, no access to the source code, and no knowledge of the architecture.
In essence, this approach most closely mimics how an attacker typically approaches your
application. However, due to the lack of internal application knowledge, the uncovering of
bugs and/or vulnerabilities can take significantly longer.
103 | P a g e
Chapter 6: Conclusions
6.1 learned from this project
I have learned from this project a lot of things:
1- How to communicate with company.
2- How to collect system requirement.
3- How to analysis requirement.
4- How to take an interview with people.
5- How to work in group.
6- How to create a DFD and ERD.
7- Understand a business domain.
8- Use the traditional and modern methods of collecting requirements.
6.2 benefit of the report
The report shows the group work and the level of understanding problem domain, also it
show the task distribution for each member.
6.3 future work
We would like to create a full implementations and documentation for the system, but
unfortunately no time to do that, also we are looking to add more functionally to the system.
104 | P a g e
References:
de Wilde, Decision Tables, [ppt],13-feb-2010, Available at:
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=7&ved=0CF4QxQEw
Bg&url=https%3A%2F%2Fdocs.google.com%2Fviewer%3Fa%3Dv%26q%3Dcache%3Aq5
jG9SCwr98J%3Awww.sqnz.org.nz%2Fdocuments%2FDecision%252520Table%252520trai
ning%252520session.ppt%2B%26hl%3Den%26pid%3Dbl%26srcid%3DADGEEShawEj813
IiUj1U5t7eLApsI5ynfNQiZDPkSicsHmH5n7iBD3VPm2PUxtjpFIrrfZ9h6Q0Xn9eJYtfFS030Hv1T9j2WXKmq3KEj0tW8_71JK2juFNKrngDpFlgoXV4H
NHlOV6W%26sig%3DAHIEtbTrEoXp8Ksgw-RSzPzCbVdPIxVmw&ei=gr7QTtK6G6Xe4QTTppQl&usg=AFQjCNGqEx_H39IclZ4UrsO8GbeatBbiA , 26-Nov-2011.
jiludwig,
Functional
Requirements
Document
,[doc],12-Aug-2006,
Available
at:
http://www.jiludwig.com/templates/FRDTemplate.doc , 26-Nov-2011.
Dr. Chung , ER Diagram , [html] , , Available at: http://ltu164.ltu.edu/mmaa/doc/erd.htm ,
26-Nov-2011.
Kenneth E. Kendall, Julie E. Kendall, March 11, 2004, Systems Analysis and Design (6th
Edition), Saddle River.
V.Rajaraman, “Analysis and Design of Information Systems”, 2nd Edition, Prentice Hall of
India, New Delhi, 2002. Most of the material in this module is based on Chapter 8 and 9 of
the above book. The book is perhaps the only one which has extensive discussion on error
detection in Decision Tables.
Brown, Dan M. (2011). Communicating Design: Developing Web Site Documentation for
Design and Planning, Second Edition. New Riders.
Garrett, Jesse James (2010). The Elements of User Experience: User-Centered Design for the
Web and Beyond. New Riders.
105 | P a g e
Wodtke, Christina; Govella, Austin (2009). Information Architecture: Blueprints for the Web,
Second Edition. New Riders.
McConnell, Steve. "7: Lifecycle Planning". Rapid Development. Redmond, Washington:
Microsoft Press. p. 140.
106 | P a g e