Professors Portal

End of Year Project

Prepared By Ahmed Mehdi && Zaoui Trabelsi Yassine

Supervised By Ayadi Ahmed

13/07/2009

Professors Portal

Table Of Content
Acknowledgements .................................................................................................................... 4 IIIIIIIVIV.1 IV.2 IV.3 IV.4 IV.5 VVIVI.1 VI.2 VIIVIIIIXXXIXIIXIIIXIVXVXVI-

The company profile ........................................................................................................... 6

Problem statement.......................................................................................................................... 7 LOCATION OF the PROJECT AND THE OBJECTIVES ...................................................................... 7 MODELING AND METHODOLOGY ............................................................................................... 8 The UML modeling (Unified Modeling Language)................................................................... 8 The choice of the Unified Process ........................................................................................... 9 The Process 2-TUP (2 Track Unified Process) ........................................................................ 10 THE parallel study of 2 branches: the functional and technique .......................................... 10 The third branch: a synthesis of 2 roads ............................................................................... 11

Conclusion ..................................................................................................................................... 11 Preliminary study....................................................................................................................... 13 Expected features .................................................................................................................. 13 Capture and analysis of the functional needs ....................................................................... 13 Behavior of the project.............................................................................................................. 14 Analysis ...................................................................................................................................... 14 General conception ................................................................................................................... 18 Conclusion ..................................................................................................................................... 19 ANALYSIS OF THE TECHNICAL NEEDS ........................................................................................ 21 DETAILED CONCEPTION............................................................................................................. 22 conclusion.................................................................................................................................. 26 WORKING ENVIRONMENT ........................................................................................................ 28 Conception of user interfaces ................................................................................................... 28 Conclusion ................................................................................................................................. 30

Professors Portal

Table of Figures
Figure 1-Web Application Architecture................................................................................................... 8 Figure 2-Process 2-TUP.......................................................................................................................... 10 Figure 3-Use case Authentication ...................................................................................................... 16 Figure 4-Use case of Manage Messages ............................................................................................ 16 Figure 5-Use Case of General Management: Users and Groups ........................................................... 17 Figure 6-Class Diagram .......................................................................................................................... 18 Figure 7-Authenticate Sequence ........................................................................................................... 23 Figure 8-Managing Groups Sequence ................................................................................................... 24 Figure 9-Sending Message Sequence .................................................................................................... 24 Figure 10-Activity diagram of sending a message ................................................................................. 25 Figure 11-Activity diagram of Managing Goups .................................................................................... 25 Figure 12-Case of authenticate ............................................................................................................. 29 Figure 13-Case of Managing professors ................................................................................................ 29 Figure 14-Case of Send Message ........................................................................................................... 30

Professors Portal

Acknowledgements
First of all, we would like to thank our family. They always supported us whenever we needed it. We are also very grateful to Mr. Ayadi Ahmed for his assistance and his leadership.

Professors Portal

General Introduction
Portals are increasingly being adopted by many institutions. Some are called corporate portals, others are more specific. We can briefly describe portals as frameworks for integrating information, people and processes. One of the most important features of Portals is providing a secure unified access point. Unifying access point pushes us to mention permissioning, which is the ability for portal administrators to limit specific types of content and services to some category of users. Portals bring us many other services that will be described with more details, later on next sections. ESPRIT, our university like many other educational institutions needs to provide to its educational stuff a common platform which will be designed to facilitate their work. It is according to this context that our end of year project was proposed by ESPRIT. The purpose of this current report is to describe the different steps and sections of design and implementation. Our work consisted on four chapters. In the first we study the company profile and the problematic statement. In the second, we talk about the analysis of Functional needs and the design methodology. The third chapter is devoted to the construction of our modules and the implementation

Professors Portal

I- THE COMPANY PROFILE

ESPRIT is a limited company steered by a Chairman and a Chief Executive Officer elected by the board of directors. The members of the board are appointed by the general assembly for a period of three years. ESPRIT is a school of engineer's training steered by a director who belongs to the teaching profession of the higher education according to the current rule. The direction of the studies controls the implementation of the educational strategy of the school through the coordination of the various educational departments, the leaders and the members of the unit of educational innovation. It also defines the needs of the students in training courses of companies and the control of their realization in good conditions. The direction of the studies includes 4 educational departments: 1. The IT department 2. The department telecommunications 3. The electro mechanic department 4. The IT department for evening classes

Every department includes leaders whose mission is to coordinate the educations relative to a module or a group of modules so as to harmonize the contents, the educational progress and the evaluations. The direction of the studies coordinates the activities of the Unit of educational innovation which includes besides the Department Heads and the leaders of eminent teachers, researchers and professionals whose missions consist in suggesting innovations as for the new subjects taught, the new technologies to be introduced and the new modes of training in adopt The research unit Development is in charge of the definition of the areas of research to meet the needs of companies, look for the industrial and educational partners for the implementation of these axes, affect the researchers and watch the good execution of the reserved shares.

Professors Portal

The direction of the relations with companies is in charge of the widening of the network of companies and of maintaining partnership relations with them in research development and for a reception of the training students.

II- PROBLEM STATEMENT

According to the current markets situation and the expansion of our school, and given to the growing number of teachers that can be permanent or temporary replacements of the technologists, our university is facing the necessity of finding a way to manage different kind of teachers status. communicate between them. Our problematic statement can be described as the following: How our teachers would connect to our Web Portal, according to their roles and the degree of privileges they have. It is a question of developing modules and integrate them to our web application Portal that allows and give the teachers the possibility to communicate by exchange messages, according to the level of their privileges, they can manage the different parts of the Portal. These professors have also to be capable de

III- LOCATION OF THE PROJECT AND THE

OBJECTIVES
Objectives of the project
Development of requirement documents. Design of web pages. Development of codes for web pages. Validation Implementation. Testing of various coding interfaces. Implementation of the system.

Professors Portal

Advantage of the proposed system Fully web-based system. Easy maintenance of a large volume of data. No delay in selection procedure.

Figure 1-Web Application Architecture

IV- MODELING AND METHODOLOGY

The fundamental motivation of modeling languages is to supply a sufficient level of abstraction facilitating information exchanges during the conception.

IV.1 THE UML MODELING (UNIFIED MODELING LANGUAGE)

It is a method of object directed modeling developed in answer to the call for proposals launched by the OMG (Object Management Group) with the aim of defining the standard notation for the modeling of the applications built by means of objects. It is inherited from several other methods such as OMT (Object Modeling Technique) and OOSE (Object Oriented Software Engineering) and Booch.

Professors Portal

In UML, there are several models: the model of the classes, the model of states, the model of the uses cases, the model of interaction, the model of realization, and the model of deployment. The model of uses case is the most useful. It allows describing the needs of the end user of the software. The model of the classes is a formalism to represent the usual concepts of object directed. As for the model of states and that of interaction, they allow representing the dynamics of objects. Finally, the model of realization and the model of deployment allow realizing projects centered on the architecture. Unified Process The process of development must be piloted by the uses case. The modeling is guided by the identification of the sequences of events which correspond to the typical use of a system seen as a black box. The U.P shows that the system which will be built defines itself at first with the users (get needs). This approach allows a division of the development by uses case and the reception of the software will also be made by uses case.

IV.2 THE CHOICE OF THE UNIFIED PROCESS

The application is sensitive to the functional changes of the school according to its needs, which will imply certain technical changes; so, it will be brought to us to synchronize both evolutions, thats why the separation of the study of these two types of needs can be only an advantage. So by separating functional and technical needs during our unified process, we can better control the changes. For that purpose, the unified process 2-TUP is situated as the unified process the most adapted for our project because. Thus we choose to apply the process 2-TUP for the modeling UML and we shall use for it Visual Paradigm.

10

Professors Portal

IV.3 THE PROCESS 2-TUP (2 TRACK UNIFIED PROCESS)

2-TUP is a unified process (figure) which contains at once the constraints - Functional: initiative of the functional needs - Techniques: connected to the platform of implementation. 2-TUP presents particularly interesting characteristics. It seems to constitute a good synthesis of the knowledge and the experiments of the Object Directed development today.

Figure 2-Process 2-TUP

IV.4 THE

PARALLEL STUDY OF

BRANCHES: THE FUNCTIONAL AND

TECHNIQUE

The functional branch corresponds to the traditional task of modeling of the domain, to the problem to be solved and to the needs of the users. But what changes profoundly the nature of the process is the addition of an independent technical branch. Indeed, we have considered for a long time that the technical aspect deducted somehow functional aspects. What changed, it is that:

11

Professors Portal

- It is necessary to choose in techniques: - There is no more inevitably a unique central BD but a BD distributed who communicate between them - The software implements components others than the only storage and secured access to the data: User interfaces, communication of the information via networks (local, intranet, internet), display of the information about jobs etc. - It is thus necessary to create any pieces a model of these components and their interactions: It is what we call software architecture. The IT technology becomes itself a subject of the conception and the modeling. The expected profit is the one of the re-use and the extensibility.

IV.5 THE THIRD BRANCH: A SYNTHESIS OF 2 ROADS

It consists in articulating components "profession" with technological components as well as possible. We can see this articulation as the fact that architecture (right branch of Y) is used as a control lever which, applied to the functional specifications (left branch of Y) is going to produce a software solution (common branch of Y).

V- CONCLUSION
After the documentation by Internet and by bibliographical references, we were able to find rather important information to explain the subject of this work. During this chapter, we presented the company profile, the problematic statement and the modeling methodology.

12

Professors Portal

Chapter II main page (Dont print)

13

Professors Portal

VI- PRELIMINARY STUDY

VI.1 EXPECTED FEATURES
Our solution has to insure the following features: Every teacher will connect to the portal with different degree of privileges that allow him to realize some specific tasks. For example, the Super User, or the administrator can manage groups by adding or removing a group of professor. Plus, they will be able to communicate via a messaging module. The system also has a private space which can be visited by connected users (the professors) By connecting with a certain login and password, the professor reaches a private space that is dedicated for all professors with the same degree of privileges as him. He will find his Electronic-Mails, Agenda, blogetc. He can also search for professors. The Super User can access to another portal space with its own menus and can delete or add, a professor, a group, or send messages to a specific professor, to a specific group or to all portals users.

VI.2

CAPTURE AND ANALYSIS OF THE FUNCTIONAL NEEDS

a. Specification of the functional needs

The desired features allowed us to loosen the functional needs of our application which must: Authenticate. Navigate to home page. Consult Electronic-Mails. Managing professors Managing groups b. Specification of the non functional needs We can kick away the non functional needs as follows: The interface must be friendly, customizable and evolutionary. The integration of new parameters of authentication must be simple, easy and fast. Speed of the functioning (recovery of the results) The application must be simple to update, because the changes are rather frequent.

14

Professors Portal

Certain needs which we shall have to take into account during the development specifically: Insurance of security services According to the desired requirements, it is essential to make sure of the security services or a part of these services according to the cases. Modularity This application is frequently used; it must be easy to be changed at every need Performance The performance of the application is a constraint not to be neglected.

VII- BEHAVIOR OF THE PROJECT

After the validation of the wanted features and the functional and not functional needs, we are going to elaborate the planning for the behavior of the project. The planning of the project includes: Authenticate. Navigate to home page. Consult Electronic-Mails. Managing professors Managing groups

VIII- ANALYSIS
VIII.1 IDENTIFICATION OF THE ACTORS

Professor, Super user: the users of the system who are going to interact with the various interfaces of the site.

15

Professors Portal

VIII.2

DESCRIPTION OF THE EXPECTED FEATURES Description Each user may be identified by entering a login and password The user can reach home page and navigate through it. The Super user or the professor can receive / send messages to his colleagues or to a group of teachers Each Professor can send emails to his colleagues The super User can add or remove a group of teachers belonging to a specific group The super User can add or remove a new professor to our institute

Use case Name Authenticate

Navigate to Home Page Consult Electronic-Mails

Send Emails Add or remove groups

Add or remove Professor

VIII.3 IDENTIFICATION OF USES CASE Now, we present a description of every uses case; this description will allow us to understand the expectations of the user. Use case Name Authenticate Description Each user may be identified by entering a login and password The user can reach home page and navigate through it. The user or the professor can receive / send messages to his colleagues or to a group of teachers The user can send emails to his colleagues The User can add or remove a group of teachers belonging to a specific group The User can add or remove a new professor to our institute Actor Super User Professor Super User Professor Super User Professor

Navigate to Home Page Consult ElectronicMails

Send Emails Add or remove groups

Super User Professor Super User

Add or remove Professor

Super User

16

Professors Portal

>>The professor and the super user can authenticate by putting their login and password. The authentication: It consists of verifying roles and privileges.

Enseignent

S'authentifier

Super Utilisateur

Figure 3-Use case Authentication The message management: The professor can add, edit and delete messages.

Enseignent Gestion des messages

Figure 4-Use case of Manage Messages

17

Professors Portal

The super user is the manager of users and groups. He has privileges to: Add, edit and delete users. Add, edit and delete groups. Assign privileges to groups Assign lessons to groups.

Gestion des users

Super Utilisateur

Gestion des groupes

Figure 5-Use Case of General Management: Users and Groups

18

Professors Portal

IX- GENERAL CONCEPTION

IX.1 CLASS DIAGRAM

Users +Login +PWD +Id_Enseignent 1..*

Message +Id_Message +Source +Destination +Contenu +Id_Enseignent

Groupe_Message +Id_Message +Id_Groupe +Envoi_Message()

1..* Envoyer Message Enseignent_Groupe +Id_Enseignent +Id_Groupe +Privilege

Authentification

Groupe +Id_Groupe +Nom +Privilege

1 Enseignent +Id_Enseigent +Nom +Prenom +Departement +Email +Telephone

Groupe_Publication Commentaire_Publication +Id_Commentaire +Id_Publication 1 1..* Commentaire +Id_Commentaire +Contenu +Id_enseignent Publication +Id_Publication +Contenu_Publication +Id_Enseignant +Ajouter_Commentaire() +Id_publication +Id_Groupe +Envoi_Publication()

Figure 6-Class Diagram

19

Professors Portal

IX.2
Class
Users Messages Commentaries Publication

DESCRIPTION
Description
A Class which contains All kind of Users The messages that users can receive or send The commentaries that user can make on their personal space All publication of users Relation between Commentaries and Publication Groups that a user can belong to Relation between Groups and Messages Relation between Groups and Publication List of all professors of ESPRIT Relation between Professor and Group

Commentaries_Publication Groups Groups_ Messages Groups_Publication Professor Professor_Group

X- CONCLUSION
In the present chapter, we proceeded to a study of the existing as regards the portal. In the chapters which are going to follow, we are successively going to be interested in the sub-systems. These sub-systems based on a material and software infrastructure which will be detailed in what will follow.

20

Professors Portal

Chapter III main page (Dont print)

21

Professors Portal

XI- ANALYSIS OF THE TECHNICAL NEEDS

XI.1 NET FRAMEWORK The Microsoft .NET Framework is a software framework available with several Microsoft Windows operating systems. It includes a large library of coded solutions to prevent common programming problems and a virtual machine that manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform. The framework's Base Class Library provides a large range of features including user interface, data and data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications. Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together compose the .NET Framework. Version 3.0 of the .NET Framework is included with Windows Server 2008 and Windows Vista. The current version of the framework can also be installed on Windows XP and the Windows Server 2003 family of operating systems. A reduced "Compact" version of the .NET Framework is also available on Windows Mobile platforms, including smart phones.2 XI.2 SQL SERVER 2005

SQL Server 2005, released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database

22

Professors Portal

columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML, which allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML. For relational data, T-SQL has been augmented with error handling features and support for recursive queries. SQL Server 2005 has also been enhanced with new indexing algorithms and better error recovery systems. Data pages are checksummed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.

XII- DETAILED CONCEPTION

At the moment, we are going to define all the significant decisions concerning the organization of our system, the selection of the structural elements and their interfaces which compose the system, as well as their behavior such as specified in collaborations between these elements.

23

Professors Portal

The general conception of the Web site is made so as to allow the system to:

Authenticate. Navigate to the Home Page. Add or Remove a Group. Send a message to a professor or to a group Manage Groups Consult Electronic-Mails.

In what follows, we are going to be interested in the details of the various modules constituting the system, and this by presenting the diagrams of sequence of messages exchanged between modules for the already quoted cases of use, and to allow to assimilate better certain scenarios made by the system. In addition of that, we also add some activity diagrams in order to explain some specific activity of our modules.

XII.1

MODULE OF AUTHENTICATION

Figure 7-Authenticate Sequence

24

Professors Portal

XII.2

MODULE OF MANAGING GROUPS

Figure 8-Managing Groups Sequence XII.3 MODULE OF SENDING MESSAGE

Figure 9-Sending Message Sequence

25

Professors Portal

UML 2 activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario. >>>The user can send or remove a message. The system verifies the existence of the Mail address.

Figure 10-Activity diagram of sending a message

>>The super user create , modify or remove groupe with a avalidation message for each case.

Figure 11-Activity diagram of Managing Goups

26

Professors Portal

XIII- CONCLUSION
In the present chapter, we have presented the various sub-systems composing the proposed solution.

27

Professors Portal

Chapter IV main page (Dont print)

28

Professors Portal

XIV- WORKING ENVIRONMENT

1. MATERIAL ENVIRONMENT
This project was realized with the following computing tools: CPU : Intel Core2 P7450 @2.13GHz RAM : 4GB CPU : Intel Core2 P8400 @2.43GHz RAM : 4GB

2. SOFTWARE ENVIRONMENT
The realization of this project required the interaction of several software components namely: Tool of modeling and conception: Visual paradigm Tools of development: Visual Studio 2008 SQL Server EXPRESS edition

XV- CONCEPTION OF USER INTERFACES

We realized the graphic interfaces with Microsoft Visual Studio on 2008. In this section we are going to describe the realized application while illustrating it by print screens of the main modules. Indeed, having developed our system and having implemented software modules which compose it, the last stage of the process of the IT development consists in verifying the smooth running of the system in all the terms of service. The application contains some interfaces which are: Navigate to the Home Page. Look for Professors. Authenticate. Consult and send internal-mails. Manage Groups

29

Professors Portal

Case of authentication. According to the login, the user connects and can do some specific tasks that depend on the degree of privileges he got.

Figure 12-Case of authenticate Case of manage Professors. Administrator can add a new professor and adding his name, department, email to the database.

Figure 13-Case of Managing professors

30

Professors Portal

Case of Send message. The simple user or the administrator can send a message to all the persons connected to the Portal, to a specific Group or to a Professor.

Figure 14-Case of Send Message

XVI- CONCLUSION
In the last chapter, we presented the last stage of our project. This stage is the realization of software components of our system. To conclude, we collected some screen shots of the user interface of software modules of this system to give an outline onto the functioning of these modules.