Documentation (Version 1) FCIH

7/30/2019 Documentation (Version 1) FCIH

http://slidepdf.com/reader/full/documentation-version-1-fcih 1/60

“Graduation project documentation

”

Under supervision of:

Prof. Dr. Maha Atia

Helwan University

Faculty of computers and

information

Information system

department



Page 2

Table of Contents

Chapter 1 - Introduction....................................................................................... 41.1 Project Overview ...........................................................................................................5

1.2 Motivation .....................................................................................................................7

1.3 Objectives.......................................................................................................................81.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 ............................................................... 132.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 3

Chapter 3 – Design ...................................................................................... 383.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 4

1. Overview

2. Motivation

3. Objectives

4. Scope of work

5. Risk analysis

6. Problem definition

7. Problem solution8. Survey



Page 5

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 6

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, soeach 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 7

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 8

b) We will help professors in:

Easy communication between them and their

student.

Easy way to upload materials and write note forstudents.

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.

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 afterevery 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 assignmentand write notes to the students.

Site help visitor to know about the collage and its

departments and courses and teaching staff.



Page 9

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 10

Online exams.

Way to connect with the teaching staff to ask them

question.

Graduate studies.

Risk can be defined in our project as the probability

of the user of the system who isn’t able to access theinternet. So there are students won’t be able to transact

with the system at specific time like registration time.

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 11

As we know our faculty has a web site but not

active as we want it not active in the way that make us

don’t 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”.

Faculty like faculty of computer science and

information system must have a web site that perform

all transactions and operations that facilitatescommunication 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 beso easy for professors to upload new materials and

write notes if they want to tell all students anything

about courses.



Page 12

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.

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 13

1. User requirements

2. System requirements



Page 14

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 aboutthis course.

2.2.1 Functional requirements

All user requirements are specified in use cases

step by step.



Page 15

Use case diagram



Page 16

Student use cases diagram:



Page 17

Doctor use cases diagram



Page 18

Admin use cases diagram:



Page 19

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 eventsUser 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 descriptionStudent, graduated, professors, admin are able to

edit in their profiles data and save a new data.

Precondition



Page 20

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.


Main flow of events

1. User clicks on "my profile" button.



Page 21

2. System displays user profile page.


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.


Main flow of events

1. User clicks on "log out" button.

2. System displays the site home page.


None

2.2.1.5 Use case: Register courses

Brief description

Student selects courses that he will study in thissemester.

Precondition

A. Student has signed in his profile.

B. Student is viewing his profile.



Page 22

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.


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 23

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.


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.



2. Student chooses more than max allowed sections.



3. Student clicks "cancel" button. A. System backs to the profile page.



Page 24

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.


C. Table is organized by admin.

Main flow of events

1. Student selects show table option.

2. System displays the user’s 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 thissemester.

Precondition



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 25

Alternative flow steps

1. Grades haven’t 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


B. Student is accessing his profile.

C. Student has to be passed one course at least.

Main flow of events1. 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 26

precondition


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 itsmaterials.

Precondition



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 27

4. System displays the profile of this course.


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



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 28

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.


7. System backs to step 4.


1. Professor selects to upload an already existing

material….

A. System displays an information message.


2. Professor clicks on cancel button….

A. System backs to course profile



Page 29

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.


Main flow of events1. Professor selects edit course option.


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.



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 30

B. Professor has selected the course that he

wants to edit.


Main flow of events

1. Professor select edit course option.


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.


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 31

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.


6. System displays administration profile page.


1. Admin didn’t fill all required details.

A. System displays error message….


2. Admin click cancel….

A. System backs to administration profile page.

3. Admin enters an ID which exists before…. A. System displays error message.


2.2.1.17 Use case: Record grades

Brief description

Administrator records grades of all registeredcourses.

Precondition




Page 32

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.




1. Admin has recorded course grade large than the

maximum grade in specific course

A. System displays error message.


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




Page 33

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.


None

2.2.1.19 Use case: Organize table

Brief description

Administrator organizes the table for all courses.

Pre-conditions



Main flow of events1. 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.


1. There is an open course has not organized in the

table



Page 34

A. System displays error message.


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



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.


1. Admin clicks “cancel” button.

A. System backs to administrator profile home page.



Page 35

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 webBrowsers.

2.2.2.1.2 Security

Administrator is the only person who has the

highest authority to edit/delete/createdatabase.

Students can only view their records.

Critical information like passwords should be

transferred in encrypted form.

Passwords should be stored in encrypted

form.



Page 36

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 usingasp.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 operatingsystems.



Page 37

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 implementmultithreading to achieve acceptable

performance. Further a database connection

pool may also be required for assigning faster

database connection.



Page 38

1. Use case diagram

2. Activity diagram

3. State diagram

4. Sequence diagram

5. Entity relationship diagram

6. Class diagram



Page 39



Page 40



Page 41



Page 42



Page 43



Page 44



Page 45



Page 46



Page 47



Page 48



Page 49



Page 50



Page 51

SystemAdminUser

1: Login()

3: Create users accounts()

4: Send account information to user()

5: Organize tables()

2:verify login()

6: Record grades()

7: Logout()

8: Login()

9:verify login()

10: Redirect to user homepage()

11: Course registration()

13: Logout()

12: Edit profile()



Page 52



Page 53



Page 54



Page 55



Page 56

ASP.Net using Microsoft Visual Studio

professional 2010Microsoft 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 2008Microsoft 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 57



Page 58

activity start end

Gathering

information

5th

November

2011

20th

November

2011

Faculty of science

Cairo university

meeting

25th

November

2011

1st

December

2011

Making survey 3rd

December

2011

10th

December

2011

Group meeting

analysis

25th

Jan 2012 8th

Feb 2012

Group meeting

design

8th

Feb 2012 15th

Feb. 2012



Page 59

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



Presented by:

Name Department Contacts

Mohamed Ahmed Mustafa Information

System

mohamed.shaarawy2191@hotm

ail.com 01064980457

Mohamed Ahmed Abd El-Aty Information

Syaytem [email protected]

01145909494 Islam Ramadan Ahmed Information


01069177378 Yasser Mohamed khairy Information


m

01115594537

Khaled Ahmed Shafek InformationSyaytem

[email protected]

01060073736

Mohamed Samir Abdel Bary Information


m

01092789568

Under supervision of:

Prof Dr Maha Atia

mailto:[email protected]






















Documents

Documentation (Version 1) FCIH