Helwan University Faculty of computers and information Information system department

Graduation project documentation

Under supervision of:

Prof. Dr. Maha Atia

Table of Contents
Chapter 1 - Introduction....................................................................................... 4
1.1 Project Overview ...........................................................................................................5 1.2 Motivation .....................................................................................................................7 1.3 Objectives.......................................................................................................................8 1.4 Scope of work ................................................................................................................9 1.5 Risk analysis...................................................................................................................10 1.6 Problem Definition .......................................................................................................10 1.7 Problem Solutions.........................................................................................................11 1.8 Survey...........................................................................................................................12

Chapter 2 - Software Requirements ............................................................... 13

2.1 User Requirements.......................................................................................................14 2.2 System Requirements ..................................................................................................14 2.2.1 Functional Requirements .......................................................................................14 2.2.1.1 Login Use case .19 2.2.1.2 Edit profile Use case.19 2.2.1.3 View profile Use case .20 2.2.1.4 Log out Use case 21 2.2.1.5 Register course Use case .21 2.2.1.6 Organize sections table Use case ..23 2.2.1.7 Show table Use case ...24 2.2.1.8 Show grades Use case ...24 2.2.1.9 Show status report Use case ....25 2.2.1.10 View staff profiles Use case ...25 2.2.1.11 View registered courses profile Use case ....26 2.2.1.12 View open courses profile Use case .27 2.2.1.13 Upload materials Use case ..27 2.2.1.14 Delete materials Use case ...29 2.2.1.15 Write notes Use case 29 2.2.1.16 Create account Use case 30 2.2.1.17 Record grades Use case ..31 2.2.1.18 Access profile Use case 32 2.2.1.19 Organize table Use case ..33 2.2.1.20 Update news and events Use case ..34 2.2.2 Non-Functional Requirements ................................................................................. 35

Page 2

Chapter 3 Design ...................................................................................... 38

3.1 Use case Diagram .................................................................................................... 39 3.2 Activity Diagram....................................................................................................... 40 3.3 State Diagram........................................................................................................... 49 3.4 Sequence Diagram.................................................................................................... 51 3.5 Entity relationship diagram....................................................................................... 52 3.6 Class Diagram ............................................................................................................ 54

Chapter 4 Tools .......................................................................................... 55

Chapter 5 Progress ....................................................................................... 57

5.1 What have been done? ............................................................................................... 58 5.2 What will be done? ...................................................................................................... 59

Project team ...................................................................................... 60

Page 3

1. 2. 3. 4. 5. 6. 7. 8.

Overview Motivation Objectives Scope of work Risk analysis Problem definition Problem solution Survey

Page 4

1.1 Project overview

This is FCIH website that makes the connection between students, doctors, and the faculty easier and faster. There are four actors in this system(student, teaching staff, and administrator).every actor has an account in the system which containing the features that help him to transact with the system The main functions in this system are:
1. Table organizing: The administrator is the responsible for this step where he gets all courses that will be opened to be registered in this semester, and then he organizes them in a time table where each course associated with a specific time through the week, so it is easy to students to register in the suitable, available courses through courses registration function. 2. Courses registration: In this step students are able to select the available courses which he sees that it is suitable to be studied in this semester. The graduates are the same in addition to that they also select courses that they will teach them.

Page 5

3. Grades recording: Here the administrator receives sheet with the grades of all students that are registered in a specific course from the doctor of this course, and then the administrator records this grades in the system, so each student is able to get its grades easier and faster through show result function that is existing in his(her) account. 4. Edit course: Teaching staff can upload materials of the courses and connect with their students through write notes. 5. News and events updating: This function is provided to all users of the system. Where all available news about faculty is continuously updated and displayed in the home page of the site, the administrator is also the responsible for this function.

Page 6

1.2 Motivation
Our faculty is a great faculty and its students and staff deserve better services than manual manner in its operation or this boring web site. This subject makes us want to produce a new web site to help students and faculty staff to be more satisfied. What make us want to make our graduation project as a web site for our faculty is to help students, professors and faculty staff to do all their operations and actions thorough internet in an easy way.

a) We will help students in: Students want to register their courses online. They want to choose their sections time table online. They want to know their grades after every semester online without needing to go to faculty. They want to communicate with their professors online to take all material they want.

Page 7

b)We will help professors in: Easy communication between them and their student. Easy way to upload materials and write note for students. As we explain, all this reasons make us excited to develop a new web site for our faculty and we hope to make it complete and correct as we imagine it.

1.3 Project objectives:

Our objective is to create a website for our faculty to help students and teaching staff. First this site help students by giving them the ability to register courses online, know their results after every semester, know their GBA, choose their study table for sections, view and download all material of the courses to help them in studying and all notes about the courses, and know their statue report. Give the ability to teaching staff to upload material and edit the material of his courses, add assignment and write notes to the students. Site help visitor to know about the collage and its departments and courses and teaching staff.

Page 8

1.4 Scope of work:

Internal scope:
Faculty departments and information about every department. a) Computer Science. b) Information System. c) Internet Technology. Student Profile in which every student can: a) See information about him. b) Register for subjects and departments. c) See his Statue report. d) access lectures tables and exams tables e) see his exam results teaching staff profile in which he can: a) add notes b) Add assignments for Students who take the course with. c) Add material d) Edit material Famous alumni who will aid the Students.

External scope:
Student activities. Online lectures and sections.
Page 9

 Online exams. Way to connect with the teaching staff to ask them question. Graduate studies.

1.5 Risk analysis:

Risk can be defined in our project as the probability of the user of the system who isnt able to access the internet. So there are students wont be able to transact with the system at specific time like registration time.

1.6 Problem definition:

As we see in our faculty there are important operations like registration and grades and communication between student and professors are still done in manual manner and this annoy students and professors and student affairs staff. All manual processes that require presence of students and professors and their signature, so all this transactions make it so hard and make all uncomfortable.

Page 10

As we know our faculty has a web site but not active as we want it not active in the way that make us dont need to do all this manual things. We just want to do all this manual things online through our web site. So we think to solve that problem and have an active web site which we can do all what we need without manual manner and make all student and staff do it by easy way online way.

1.7 Problem solution:

Faculty like faculty of computer science and information system must have a web site that perform all transactions and operations that facilitates communication between student and faculty staff. This site should provide a perfect service for student in faculty stuff like registration, statues report, grades and be aware of new events and news in the faculty. Web site for the faculty will also provide perfect connection between students and professors. It will be so easy for professors to upload new materials and write notes if they want to tell all students anything about courses.

Page 11

Having a web site for the faculty will be so good for visitors to know any information about the faculty and its system. Visitors will have all information they want to know about courses, staff and faculty activities.

1.8 Survey:
We have done a survey on a sample of people including Students with a percent of about 70% of the sample of people, and rest are different categories of people (e.g. graduated, professors..). From the survey we have found that: Most of people with 85% have said that the best way for courses registration is the online way. Most of people with 90% have said that they want to organize their sections tables and choose they desired time for sections. All of people have said that they want to view their grades, status report and GPA online.

Page 12

1. User requirements 2. System requirements

Page 13

2.1 User requirements

1. Student needs to register his courses. 2. After registration student needs to show his courses time table. 3. At the end of the semester student needs to know his grades. 4. Student needs to show his status report after every semester. 5. Professor needs to upload to, or delete from materials of a specific course, or write notes about this course.

2.2 System requirements

2.2.1 Functional requirements
All user requirements are specified in use cases step by step.

Page 14

 Use case diagram

Page 15

 Student use cases diagram:

Page 16

 Doctor use cases diagram

Page 17

 Admin use cases diagram:

Page 18

 Use cases:
2.2.1.1 Use case: Login

Brief description Student, graduated, professors and admin are able to access their profiles. Precondition A. User has a valid ID and password. Main flow of events 1. User enter his ID and password 2. System validate the entered ID and password 3. User accesses his profile Alternate flow of events User enters an invalid password or ID so.
1. System displays an error message 2. System goes back to step 2.

2.2.1.2

Use case: Edit profile

Brief description Student, graduated, professors, admin are able to edit in their profiles data and save a new data. Precondition

Page 19

A. User has an account. B. User is accessing his profile. Main flow of events 1. User select edit profile. 2. System displays edit page 3. User chooses the profile section he wants to edit. 4. User changes the data in this section. 5. User clicks save button 6. System saves the data 7. System displays profile page with updated data Alternate flow of events User clicks cancel button so.
1. System displays profile page

2.2.1.3

Use case: View profile

Brief description Users are able to see all information and data in his profile. Precondition A. User has an account. B. User is accessing his profile. Main flow of events 1. User clicks on "my profile" button.
Page 20

2. System displays user profile page. Alternate flow of events None

2.2.1.4

Use case: Log out

Brief description Student, graduated, professors, and admin are going to log out from his profile Pre-condition A. User has an account. B. User is accessing his profile. Main flow of events 1. User clicks on "log out" button. 2. System displays the site home page. Alternate flow of events None

2.2.1.5

Use case: Register courses

Brief description Student selects courses that he will study in this semester. Precondition A. Student has signed in his profile. B. Student is viewing his profile.
Page 21

C. Registration time is active. Main flow of events 1. Student chooses register option. 2. System opens registration page which contains all available courses. 3. Student selects the desired courses. 4. After finishing selecting, the user clicks submit button. 5. System displays confirmation message. 6. System displays page with the selected courses. Alternate flow of events 1. Student selects a course without passing its prerequisite course.
A. System displays an error message. B. System backs to step 3.

2. Student clicks cancel button.

A. System backs to the profile page.

3. Student selects more than maximum number of courses.

A. System displays error massage. B. System backs to step 3.

Page 22

2.2.1.6

Use case: Organize sections table

Brief description Student is able to choose the time for his sections. Precondition A. Student has logged in his profile. B. Student is viewing his profile. C. Table is organized by admin. Main flow of events 1. Student selects organizing table option. 2. System opens available time tables. 3. Student chooses his desired time for all sections. 4. After finishing the user clicks "submit button. 5. System displays page with chosen sections in a time table. Alternate flow of events 1. Student choses section for not registered courses.
A. System displays an error message. B. System backs to step 3.

2. Student chooses more than max allowed sections.

A. System displays an error message. B. System backs to step 3.

3. Student clicks "cancel" button.

A. System backs to the profile page.

Page 23

2.2.1.7

Use case: Show table

Brief description Student is able to show his table for this semester. Precondition A. Student has logged in his profile. B. Student is viewing his profile. C. Table is organized by admin. Main flow of events 1. Student selects show table option. 2. System displays the users tables for this semester. Alternate flow of events None

2.2.1.8

Use case: Show grades

Brief description Student is able to view his all courses grades in this semester. Precondition A. Student has logged in his profile. B. Student is viewing his profile. C. Grades for this semester are published. Main flow of events 1. Student selects "view grades" button. 2. System displays a page that containing this student grades in this semester.
Page 24

 Alternative flow steps 1. Grades havent published yet.

A. System displays an information message. B. System backs to profile page.

2.2.1.9

Use case: show status report

Brief description Student is able to view his all courses grades and his GPA. Precondition A. Student has logged in his profile. B. Student is accessing his profile. C. Student has to be passed one course at least. Main flow of events 1. Student chooses status report option. 2. System displays status report page. Alternative flow steps None

2.2.1.10 Use case: View staff profile

Brief description Student is able to view Profs and graduated profiles.
Page 25

 precondition A. Student has logged in his profile. Main flow of events 1. Student chooses staff button. 2. System viewing a page with all staff. 3. Student chooses the person he wants. 4. System view this person page Alternative flow of events None

2.2.1.11 Use case: View registered courses profile

Brief description Student is able to view course profile and see its materials. Precondition A. Student has logged in his profile. B. Student is accessing his profile. Main flow of events 1. Student selects registered courses option. 2. System displays a page with his registered courses. 3. Student chooses any course to view its profile.
Page 26

4. System displays the profile of this course. Alternative flow of events None

2.2.1.12 Use case: view open courses profile.

Brief description Student is able to access all open courses to get information about it. Precondition A. Student has logged in his profile. B. Student is accessing his profile. Main flow of events 1. Student clicks on courses button. 2. System displays a page which contains all courses. 3. Student selects the course that he wants to view. 4. System displays the selected course profile. Alternate flow of event None

2.2.1.13 Use case: Upload materials:

Brief description Professor can upload new course materials. Precondition A. Professor has logged in his profile.
Page 27

B. Professor has selected the course that he wants to edit. C. System has displayed the course profile. Main flow of events 1. Professor select edit course option. 2. System displays edit course page. 3. Professor selects upload materials option. 4. System explores the device of doctor to let him select the material which he needs to upload. 5. Professor selects the material and press upload button. 6. System displays confirmation message. 7. System backs to step 4. Alternate flow of event 1. Professor selects to upload an already existing material.
A. System displays an information message. B. System backs to step 4.

2. Professor clicks on cancel button.

A. System backs to course profile

Page 28

2.2.1.14 Delete materials

Brief description Professor can delete existing course materials. Precondition A. Professor has logged in his profile. B. Professor has selected the course that he wants to edit. C. System has displayed the course profile. Main flow of events 1. Professor selects edit course option. 2. System displays edit course page. 3. Professor selects Delete materials option. 4. System opens course profile. 5. Professor selects the material and press delete button. 6. System displays confirmation message. 7. System backs to step 4. Alternate flow of event 1. Professor clicks on cancel button.
A. System backs to course profile.

2.2.1.15 Use case: Write note

Brief description Professor writes notes to students. Precondition A. Professor has logged in his profile.
Page 29

B. Professor has selected the course that he wants to edit. C. System has displayed the course profile. Main flow of events 1. Professor select edit course option. 2. System displays edit course page. 3. Professor selects write notes option. 4. System displays an empty sheet to write in it. 5. Professor writes his note in the sheet. 6. After finish writing doctor clicks "save note" button. 7. System displays an information message. 8. System backs to course profile page. Alternate flow of events 1. Professor clicks cancel button
A. System backs to course profile.

2.2.1.16 Use case: Create accounts

Brief description Administrator creates a new account for an actor. Precondition A. Admin has logged in the system. B. Admin in the admin profile page.

Page 30

 Main flow of events 1. Admin clicks create new account option. 2. System displays new account register page. 3. Admin fills all details required for the new account. 4. Admin clicks submit. 5. System displays confirmation message. 6. System displays administration profile page. Alternate flow of events 1. Admin didnt fill all required details.
A. System displays error message. B. System backs to step 3.

2. Admin click cancel.

A. System backs to administration profile page.

3. Admin enters an ID which exists before.

A. System displays error message. B. System backs to step 3.

2.2.1.17 Use case: Record grades

Brief description Administrator records grades of all registered courses. Precondition A. Admin has logged in the system.

Page 31

B. Admin is in his profile page. Main flow of events 1. Admin clicks record grades option. 2. System displays a page contains all courses. 3. Admin selects a course he wants to record its grades. 4. System displays a grid view to record grades in it. 5. Admin fills the grid by the ID of the student and the grade. 6. After recording all grades, admin clicks "save" button. 7. System displays confirmation message. 8. System backs to step 2. Alternate flow of events 1. Admin has recorded course grade large than the maximum grade in specific course
A. System displays error message. B. System backs to step 4.

2. Admin clicks cancel button.

A. System backs to administration profile page.

2.2.1.18 Use case: Access profile

Brief description Administrator can access any actor profile. Precondition A. Admin has logged in the system.

Page 32

 Main flow of events 1. Admin clicks profile categories (student staff ) 2. System displays profiles links. 3. Admin clicks on one profile link. 4. System displays this profile. Alternate flow of events None

2.2.1.19 Use case: Organize table

Brief description Administrator organizes the table for all courses. Pre-conditions A. Admin has logged in the system. B. Admin is in his profile page. Main flow of events 1. Admin selects organize table option. 2. System opens a page that containing an empty table and all open courses. 3. Admin organizes the table using all open courses. 4. After organizing the table the admin clicks submit button. 5. System displays the organized table to users. Alternative flow of events 1. There is an open course has not organized in the table
Page 33

A. System displays error message. B. System backs to step 3.

2. Admin clicks cancel button. A. System backs to admin profile page.

2.2.1.20 Use case: Update news &events

Brief description Administrator updates news and events of the site. Pre-conditions A. Admin has logged in the system. B. Admin is in his profile page. C. There is news or event that is unknown to users. Main flow of events 1. Admin chooses updating news & events option. 2. System displays news and events updating page. 3. Admin writes the news. 4. Admin clicks update button when he finished. 5. System displays the newest news on the site home page. Alternative flow of events 1. Admin clicks cancel button.
A. System backs to administrator profile home page.

Page 34

2.2.2 Non-Functional Requirements

System should be able to handle multiple users Database updating should follow transaction processing to avoid data Inconsistency. 2.2.2.1 Software System Attributes 2.2.2.1.1 Browser Compatibility The system is a web based system. So it requires Compatibility with a good enough web Browsers.

2.2.2.1.2 Security Administrator is the only person who has the highest authority to edit/delete/create database. Students can only view their records. Critical information like passwords should be transferred in encrypted form. Passwords should be stored in encrypted form.

Page 35

2.2.2.1.3 Reliability Data validation and verification needs to be done at every stage of activity. Validating user input Use of locking mechanism while updating database like transaction processing Recovering the transaction using rollback. 2.2.2.1.4 Availability System being an online system should be available anytime. The registrations of courses may be limited. 2.2.2.1.5 Portability The web application will be built using asp.net which has support to run on any platform provided the required compilers are available. For database either XML or MySQL would be used, that too has extensive support over many popular architectures and operating systems.

Page 36

2.2.2.1.6 Performance The system would be used by multiple users at a time and may grow as time passes; the system would need to implement multithreading to achieve acceptable performance. Further a database connection pool may also be required for assigning faster database connection.

Page 37

1. 2. 3. 4. 5. 6.

Use case diagram Activity diagram State diagram Sequence diagram Entity relationship diagram Class diagram

Page 38

3.1 Use case diagram

Main use cases diagram

Page 39

3.2 Activity diagrams

3.2.1 Log in activity diagram:

Page 40

3.2.2

Edit student profile activity diagram

Page 41

3.2.3 Edit profile activity diagram

Page 42

3.2.4 Record grades activity diagram

Page 43

3.2.5 Create new account

Page 44

3.2.6 Register courses

Page 45

3.2.7 Update news and events

Page 46

3.2.8 Organize section table activity diagram

Page 47

3.2.9 Write notes activity diagram:

Page 48

3.3 State diagrams

3.3.1 Login state diagram:

Page 49

3.1.1

Register course state diagram:

Page 50

3.4 Sequence diagram

User Admin
1: Login()

System

2:verify login() 3: Create users accounts()

4: Send account information to user() 5: Organize tables()

6: Record grades()

7: Logout()

8: Login()

9:verify login() 10: Redirect to user homepage()

11: Course registration()

12: Edit profile()

13: Logout()

Page 51

3.5 Entity relationship diagram

Page 52

Page 53

3.6 Class diagram

Page 54

Page 55

 ASP.Net using Microsoft Visual Studio professional 2010

Microsoft Visual Syudio2010 is a tool for Developing, developed by Microsoft. It supports many languages such as C++, C#, ASP.NET. So, we will use Microsoft Visual studio 2010 to apply Asp.Net in developing our website.

Database using Microsoft SQL Server 2008

Microsoft SQL Server is a relational database server, developed by Microsoft. We will use it to store and retrieve data as requested.

UML Diagrams using Visio Professional 2010

IT Is a UML design tool and UML CASE tool developed by Microsoft to aid software development.

Page 56

1. 2.

What have been done What will be done

Page 57

5.1 what have been done

activity Gathering information Faculty of science Cairo university meeting Making survey Group meeting analysis Group meeting design

start 5th November 2011 25th November 2011 3rd December 2011 25th Jan 2012 8th Feb 2012

end 20th November 2011 1st December 2011 10th December 2011 8th Feb 2012 15th Feb. 2012

Page 58

5.1 what have been done

activity

start

end

Implantation

19th Feb. 2012

30th April 2012

Testing

1st may 2012

15th may 2012

deployment

16th may 2012

30th may 2012

Maintain

1st June 2012

15th June 2012

Page 59

Project team
Presented by:
Name
Mohamed Ahmed Mustafa

Department
Information System

Contacts
mohamed.shaarawy2191@hotm ail.com 01064980457 Moh.abdel3aty90@yahoo.com 01145909494 Zamalek.eslam@yahoo.com 01069177378 yassermohamedkhiry@yahoo.co m 01115594537 hero2149@yahoo.com 01060073736 Mido_elshemy2001@yahoo.co m 01092789568

Mohamed Ahmed Abd El-Aty Information Syaytem Islam Ramadan Ahmed Information Syaytem Yasser Mohamed khairy Information Syaytem Khaled Ahmed Shafek Mohamed Samir Abdel Bary Information Syaytem Information Syaytem

Under supervision of:

Prof. Dr. Maha Atia

Page 60