Beruflich Dokumente
Kultur Dokumente
DEPARTMENT OF INFORMATICS
PROGRAM OF COMPUTER
SCIENCE
To
By
1. Asress Tilaye……………………….InfR/0731/13
2. Biftu Tesfaye……………………….InfR/0098/13
3. Temesegen Tekilu………………….InfR/0849/13
4. Aster Sisay…………………………InfR/0733/13
5. Bontu Endalew ………………….....InfR/0750/13
6. Firaol Girma………………………..InfR/0779/13
Secondly we wish to extend our sincere appreciation to Mr. Misganaw his continuous
supervision, guidance, advice and constructive ideas throughout our work and making this
partial project to be successful. We hope his cooperation will proceed till the end of the project.
The special thanks extend to the University industrial linkage directorate director Mr. Getu
Abebe who gave us great detail knowledge of the existing system. We would also like to thank
instructors that we had in informatics department for all valuable contribution of knowledge that
they thought us while asking.
At the last, but not least, even if it is unusual, special gratitude for the group member
participates with a great role with each other. Without the contribution of the group, our work
would not be successful.
ABSTACT
A common concern in institutions of higher education is to keep its former students involved with
academic activities.
It is an agreement that one of the most valuable assets of universities is their alumni, given that
their accomplishments ensure more exposure for the university. In recent years, universities
have encouraged a movement toward the establishment of alumni associations, as they provide
networking opportunities and contact between the university and the alumni or among the
alumni.
An association that seeks membership and participation of its alumni should invest in the
development of an attractive way.
In this sense, the project is aimed at analyzing a new system for alumni association mainly
designed for Wollega University which is easy, fast, and efficient communication system. The
system is a web based application that can be accessed throughout the World which manages
information about the university and the students, gone together with technology.
Contents
CHAPTER-ONE..............................................................................................................................8
1. INTRODUCTION....................................................................................................................8
1.1. Background information...................................................................................................8
1.2. Strength and weakness of current system......................................................................9
1.3. Background of the project...............................................................................................10
1.4. Statement of the problem................................................................................................10
1.5. Objective of the project...................................................................................................11
1.6. Scope and limitation of the project.................................................................................12
1.7. Feasibility analysis..........................................................................................................12
1.7.1. Operational or organizational feasibility.................................................................12
1.7.2. Technical feasibility.................................................................................................13
1.7.3. Economic feasibility................................................................................................13
1.8. Significance of the project..............................................................................................14
1.9. Beneficiaries of the project.............................................................................................15
1.10. Methodology of the project.........................................................................................16
1.11. Budget and activity schedule.......................................................................................17
1.12. Hardware and software specification..........................................................................18
1.13. Risk and constraints....................................................................................................19
CHAPTER-TWO...........................................................................................................................20
2. DESCRIPTION OF THE EXISING SYSTEM.....................................................................20
2.1. Description of existing system........................................................................................20
2.2. Business rules of existing system....................................................................................21
2.3. Report generation in the existing system........................................................................21
2.4. Forms and documents used in the existing system.........................................................21
2.5. Problems of the existing system using pieces frame work.............................................23
2.6. Practice to be preserved from the existing system..........................................................24
2.7. Alternative options to address problems of the existing system.....................................24
2.8. System requirement of the new system...........................................................................24
CHAPTER THREE.......................................................................................................................26
3. MODELING...........................................................................................................................26
3.1. Use-case modeling..........................................................................................................26
3.2. Use-case documentation.................................................................................................30
3.3. Sequence diagram or activity diagram............................................................................39
3.3.1. Sequence diagram........................................................................................................39
3.3.2. Activity diagram.........................................................................................................47
3.4. Analysis level class diagram...........................................................................................55
3.5. Supplementary specification...........................................................................................56
3.6. Business rules of the new system....................................................................................57
CHAPTER-FOUR.........................................................................................................................58
4. DESIGN.................................................................................................................................58
4.1. Introduction.....................................................................................................................58
4.2. Class type architecture....................................................................................................58
4.3. Class modeling................................................................................................................60
4.4. Component modeling......................................................................................................61
4.5. Deployment modeling.....................................................................................................63
4.6. Persistence data management..........................................................................................65
4.7. Mapping ( Hardware and Software mapping).................................................................67
4.8. Object models (revised class diagram and service specification)...................................67
Table of figures
Figure 1- 1 the structure of the existing system...............................................................................9
YFigure 2- 1 registration form of the existing system
…………………………………………....22
YFigure 3- 1 general use diagram of the
system…………………………………………………..27
Figure 3- 2 partial use case diagram for alumni officer office......................................................28
Figure 3- 3 partial use case diagram for the alumni......................................................................29
Figure 3- 4 partial use case diagram of the administrator.............................................................29
Figure 3- 5 sequence diagram for login.........................................................................................40
Figure 3- 6 sequence diagram for registration...............................................................................41
Figure 3- 7 sequence diagram for search alumni...........................................................................42
Figure 3- 8 sequence diagram for sent mail...................................................................................43
Figure 3- 9 sequence diagram for insert data.................................................................................44
Figure 3- 10 sequence diagram for add forum...............................................................................45
Figure 3- 12 sequence diagram for add events..............................................................................46
Figure 3- 13 sequence diagram for upload file..............................................................................47
Figure 3- 14 activity diagram for registration................................................................................48
Figure 3- 15 activity diagram for login..........................................................................................49
Figure 3- 16 activity diagram for update profile...........................................................................50
Figure 3- 17 activity diagram for sent mail...................................................................................51
Figure 3- 18 activity diagram for upload file.................................................................................52
Figure 3- 20 activity diagram for add forum.................................................................................53
Figure 3- 21 activity diagram for insert data.................................................................................54
Figure 3- 22 activity diagram for add event..................................................................................55
Figure 3- 23 analysis class level diagram......................................................................................56
YFigure 4- 1 the class type architecture…………………………………………………...………
59
Figure 4- 2the overall architecture of the proposed system...........................................................60
Figure 4- 3 Class modeling............................................................................................................61
Figure 4- 4 over all component diagram........................................................................................62
Figure 4- 5 Outlook component diagram.......................................................................................63
Figure 4- 6 deployment diagram....................................................................................................64
Figure 4- 7 the overall deployment diagram..................................................................................65
Figure 4- 8 persistence data management diagram........................................................................66
Figure 4- 9hardware and software mapping..................................................................................67
Figure 4- 10 object model for office..............................................................................................68
Figure 4- 11 object model for administrator.................................................................................69
Figure 4- 12 object model for alumni...........................................................................................70
Figure 4- 13 object model for message..........................................................................................71
Figure 4- 14 object model for upload file......................................................................................72
Figure 4- 15 object model for account...........................................................................................72
Figure 4- 16 object model for forum.............................................................................................73
Figure 4- 17 object model for event..............................................................................................73
Figure 4- 18 object model for report..............................................................................................74
List of tables
YTable 1- 1 budget schedule for the project.................................................................................19
Table 1- 2 activity (work plan) schedule for the project...............................................................20
YTable 3- 1 use case description for
login…………………………………………………...........31
Table 3- 2 use case description for registration.............................................................................32
Table 3- 3 use case description for sent mail.................................................................................33
Table 3- 4 use case description for view mail...............................................................................34
Table 3- 5 use case description for upload file..............................................................................35
Table 3- 6 use case description for delete data..............................................................................36
Table 3- 7 use case description for search data.............................................................................37
Table 3- 8 use case description for add events..............................................................................37
Table 3- 9 use case description for search alumni.........................................................................38
Table 3- 10 use case description for add forum.............................................................................39
Table 3- 11 use case description for view forum...........................................................................40
List of acronyms
WUAAMS Wollega University Alumni Association Management System
WAMP Window, Apache, MySQL, PHP
PHP Hypertext Preprocessor
MySQL Structured Query Language
CD Compact Disk
RAM Random Access Memory
CSS Cascading Style Sheet
HTML Hyper Text Markup Language
MSc Master
GUI Graphical User Interface
BR Business Rule
IE Internet Explorer
UC Use Case
UML Unified Modeling Language
CHAPTER-ONE
1. INTRODUCTION
Alumni association is an association of graduates (alumni) or, more broadly, of former students.
In the universities, colleges and schools often form groups with alumni from the same
organization. These associations often organize social events; publish newsletters or magazines
raise funds for the organization. It provides a variety of benefits and services that help alumni
maintain connections to their educational institution and fellow graduates. Additionally, such
groups often support new alumni, and provide a forum to form new friendships and business
relationships with people of similar background.
Alumni associations are mainly organized around universities or departments of universities, but
may also be organized among students that studied in a certain country. In the past, they were
often considered to be the universities or schools of old boy network. Today, alumni associations
involve graduates of all age groups and demographics.
Alumni association has been in existence for decades and they are constantly changing with
time. There have been very big changes in the recent years with the development of the internet
and social networking that forces the alumni system to undergo huge changes. Therefore, it is
really important for universities to focus on the alumni networks and find ways to enhance their
growth and development.
The system called “alumni association management system (AAMS) proposed in this ideas
offers an inter mix of traditional alumni systems and social networking sites. The brief study on
both systems is undertaken and important features of these systems are incorporated into the new
proposed system.
Why Social networking? This can be described as the act of social relationships for the purpose
of common needs, interests or goals. Networking has been taking place all over the world since
the existence of humans. Nowadays networking has become easy because of the development of
technology. People can interact with one another and share their ideas, discuss their personal and
professional lives without even moving from their desks. The existing systems are usually
developed to facilitate networking between the alumni and their respective universities, but most
of these current systems are not being used by the majority of the alumni.
1.2. Strength and weakness of current system
Even if the WU hasn’t completed management system for the association, in general using the
manual system has their own weakness and strength.
Strength of the current system
In the current system, since it is used computerized in some way in addition to paper; those who
perform that activity doesn’t need more of computer knowledge, since there is no more work in
addition to excel and word program and managing is simple those who have less knowledge of
English language (since mostly used local languages while communication). It also allows
physical interaction of individuals with their friends.
Weakness of the current system
In Ethiopian university, almost most of them are using alumni association as a manual system
including Wollega University. This way of managing system doesn’t give more sense in their
work. Since most of the time information’s regarding their system is posted on notes board and
the beneficiaries are only those who lives belongs to around there i.e. it is difficult to manage the
alumni who live far from the university. The system also takes much time and energy to contact
alumnus when needed and using phone number and Gmail as a method of an interaction doesn’t
give much more scenes. Using paper and excel sheets for data storage have a great risk and there
is no effective data protection. The status of the alumni also does not updated easily and not
uniform redistribution of information for all members at the same time.
1.3. Background of the project
Alumni Association of Wollega University is an independent self-governing organization
charged with the mission of engaging the talents and resources of alumni students and friends in
the life, work and aspiration of Wollega University. It is the most ways to build strong holds
between the university and the ever increasing graduates. Apparently the previous and
prospective graduates are in equal responsibility for the establishment and development of
university alumni association.
Wollega University alumni association allows promoting the health of the university by
cultivating mutually beneficial relationship between university and its growing alumni.
Membership of Alumni Association of WU will support
Encourage lifelong relationship with and among current and future alumni.
Facilitate communication with the alumni and the office.
Works to strengthen alumni bonds of fellowship, professional association and university
association. Structure of the current WUAAM
General assembly
3 Compact disk 3 8 24
Total 594
Table 1- budget schedule for the project
Activity schedule
We arrange program for finishing our task within the specified period of time. The predefined
tentative schedule that we try to specify is as shown below.
Activities 2016/17
No.
February –
November
December
January
June
1 project proposal
2 Requirement analysis
In Wollega University, the community service and industrial linkage office maintains
information manually about alumni students. This does not allow efficient data management and
retrieval process. Often the information may not be available on time. Inside the administrative
office several activities performed which benefits graduated as well as the university itself. The
office uses computer to record different data of the alumni which is maintained at individual
database i.e. building innumerable excel sheets and papers which is timely delay process. These
sheets may be collected by the organization and shared with all the alumni but this activity may
not be frequent. Email IDs and phone numbers may be freely shared and can lead to excessive
spam mails. This apparent lack of privacy will force many alumni to avoid sharing of their
details to fellow alumni. All the information regarding the alumni has only accessed by the office
manager and other bodies have not any information, the activity performed by the office and how
the alumni system operates. Even if the alumni may become a member, there is no any meeting
of the whole member about how we run the system. Each member doesn’t make interaction with
each other and there is no a method of expressing their suggestion about the association. The
existing system has the following formation methods.
The association has general congress which includes all members.
Those who lead the congress are chairman, secretary and one member.
The group has one executive comity and three different sub comities that are selected
on the general congress.
2.2. Business rules of existing system
Even if there is no clearly defied approved regulations, there is a rule which is printed out as
principles or obligations that the alumni accepting to become a member.
BR1. Should respect the legislation of the association and work on success.
BR2. It should accept the majority right and decision.
BR3. It should willingness to participate on the societies according to his professions.
BR4. It should work in honesty when he/she is selected on some position by the
association.
BR5. It should respecting the association vision and work for achiness, developing work
habit.
BR6. When he/she resign from the member, has to give back all resources of the
association if it has taken.
BR7. To be a member, happy to pay the membranes payment while it is decided by the
general assembly according to their income.
2.3. Report generation in the existing system
Even if there is no more previously done result, the report generation has performed annually to
the appropriate person using paper and specified on the notice board. The report is written by the
managers manually which includes the list of the member and the budget that are consumed.
Date____/____
Applicant
Name__________________________
Father’s Name_____________________
Grand father’s name___________________________
Sex(use ’x’ mark) M F
Birth date _____ month ______ year _____
field of study : under graduate
: Post graduate
indicate the amount of money you want to contribute for the Association monthly,
based on your personal interest Birr________( )
Approval: Full name_____________ signature _____ Date ____ year______
Figure 2- registration form of the existing system
Non-functional requirement
Our system gives requirements that are not visible aspects for the user and not essential for the
system but support and give quality of the system. It is not described what the software will do
but how the software will do it. It includes:-
Graphical user interface (GUI)
The system provides web application user interface that are compatible with internet
browser.
Performance requirement
The system shall function in real time: any operation trigged by the alumni shall
complete in few seconds.
Help and support
For unfamiliar users it will have a guide line to know how to use the system and how
to handle if a mistake happens.
Security requirement
In order to use certain features of the system, users must first authenticate themselves
by user name and password. The system shall not allow access if the user fails to
provide correct login information.
Scalability
Since the number of graduated is increases from time to time the system not effect
on the database size.
Maintainability
The system will maintain or update with time.
Documentation
The system has well defined documents that helps the user to understand and easy
to maintain.
CHAPTER THREE
3. MODELING
System modeling is the conceptual model that describes and represents a system. The system
comprises multiple views such as planning, analyzing, designing, implementing, input data and
output data view. It involves in making decision about which abstraction is the part of the system
under consideration and which fall outsides its boundaries.
3.1. Use-case modeling
Use case modeling is the unified modeling language artifact which is intended to capture the
essence of problems through idealized and abstract descriptions. Use case diagram identifies a
sequence of actions that provides a measurable value to the actor and describing the ways in
which the environment interact with the system. It model unit of functionality provided by the
system to the user and highlights what users are trying to accomplish and the responsibility of the
system. It is the collection of all actors and use-cases. We also use extends and includes (uses)
concept in the use case.
Actors of the system
Director office
Alumni/Graduated student
Administrator
Guest user/visitors
General use case of the system
manage forum
view detail_alumni
logout
generate report
view forum
<<include>>
«extends»
<<include>>
manage data <<include>> <<include>> search alumni
<<include>> <<include>>
manage member <<includes>> login <<include>> profile
office Alumni/
director <<include>>
<<include>> graduated
upload file <<include>>
<<include>> view file
<<include>>
manage events
messaging register
manage account
add event
update profile
comment
view forum
register <<include>>
<<include>>
view member
members <<include>>
<<include>>
search member <<include>>
alumni/graduated login
<<include>>
view details <<include>>
<<include>>
view events <<include>>
<<include>>
view file
messaging
view mail
sent mail
view member
members <<include>>
create_account
<<include>>
login
manage account <<include>>
update_account
<<include>>
<<include>>
administrator delete_account
events
view event
Pre-condition They must have already registered or have an account before login to the
system.
A4. The system display error message and promotes to re-enter correct
username, password or to select correct user type. And if the user forgot
password, “forgot password” option is provided
Actor Alumni
Description A form that the new applicant fill to become the member of association.
Flow of events 1. The alumnus enter into the website of the system
2. The system displays the home of the system.
3. The alumnus clicks the register link.
4. The system prompts the alumnus to fill the data.
5. The alumnus fills up the text field and clicks enter.
6. The system checks the data.
7. The system displays the registration form.
8. The user fills the provided information on the text field.
9. The system checks the validity of the information.
10. The user clicks on the registered button.
11. The system prompts successfully registered messages to
the alumni.
12. The use case end.
Actor Officer/alumni
Description The alumni can communicate with the officer and with their friends.
Flow of events 1. The user wants to enter the website of the system.
2. The system displays the home page.
3. The user goes to the message link area.
4. The system activates the message form.
5. The user clicks the sent mail option.
6. The system activates the sent form.
7. The users select the receiver name and fill the message
text area.
8. The users click the send button.
9. The system checks the name if it is exists on the
member and the validity of the content.
10. The system promotes message sent.
11. The use case end.
Alternative flow Case 1: when the receiver is not a member of the association
Description The office and the alumni can view the incoming messages
form another body.
Pre-condition The office and the alumni type the web address and login into
the system.
Actor Office
Pre-condition The office types the address of the system and approves the legality of
the information.
Actor Office
Description The removal of data which is stored previously when the data is
unwanted or when the member is not authorized for the association.
Pre-condition The data was inserted and the user must be login to the system
Flow of events 1. The user clicks the manage data link on the home page.
2. The system activates the link.
3. The user clicks the delete data link from the option.
4. The system displays the delete data form to the user.
5. The user fills the necessary information
6. The system checks the inserted field.
7. The user clicks the delete button
8. The system prompts successfully deleted information
message to the user.
9. Use case end.
Actor Office
Description The office can find the specific data which is stored previously for
different purposes.
Pre-condition The data was inserted and the user must be login to the system
Flow of events 1. The user clicks the manage data link on the home page.
2. The system activates the link.
3. The user clicks the search data link from the option.
4. The system displays the search form to the user.
5. The user fills the necessary information in the appropriate
field.
6. The system checks the inserted field.
7. The user clicks enter.
8. The system display all data based on the appropriate
search form.
9. Use case end.
Alternative flow Case 1:-when the data does not exist.
Actor Office
Description The office can delivery latest information to the whole member
Pre-condition The office type the web address of the system and login into the system
Flow of events 1. The user click the manage event link on their home page.
2. The system displays the link
3. The user can write the events on the text area or brows from the computer.
4. The user click the add button.
5. The system performs the task.
6. The use case end.
Alternative flow When the file name does not exist or maximum weight of file.
A2. The system prompts the office pleas re-enter the event and
the admin resume at step 3 of basic flow
Actor Office/alumni
Pre-condition The user types the web address of the system and login into the system.
Flow of events 1. The users click the member link on the menu of the page.
2. The system displays the list in the member page.
3. The users click the search link.
4. The system displays the search page with their form.
5. The users fill the provided text field and clicks enter.
6. The system checks the text on the database.
7. The system displays the required information on to the alumnus.
8. Use case end.
Actor Office
Post condition The forum is added and display with the previously
form.
Table 3- use case description for add forum
Actor Office/alumni
Description The office can view the previously delivered forum to view the idea of
the alumnus. The alumnus can also view the forum to give feedback as
a comment.
:main window :login link :login form login controler account db :home page
user
1:user activate UI()
6:transfer action()
7:validate()
8:[invalid i/t] go to step 4()
X
9:[valid account] continue()
X
10:check()
11:[incorrect]response to login form()
X X X X
X
Figure 3- sequence diagram for login
registration registration registration
:alumni main window link data form form controller data base
1:activate UI()
9:[if exist]
10:registration form displayed to the user[]
13:validate field()
14:[invalid] go to step 11()
15:stored on the data base()
16:message responces()
17: succussfully registered message displayed to the user()
X X
X X
X X X
5:fill name ()
6:submit()
7:action transfer()
8:check()
9:[if not exist] go to step 4()
10:request()
X X
X
X X
X
12:action response()
13:successfully registered message()
X
X X
X X
6:action transfer()
7:validate the field()
9:create()
10:action response()
10:successfully inserted()
X X X X X
X
6:action transfer()
7:validate()
9:[valid] save()
10:response()
11:successfully add message ()
X
X
X
X X X
1:user activate()
5:click()
6:action transfer()
7:validate()
10:response()
11:successfully added()
X X X
X X
X
1:activate window()
2:click()
6:action transfer()
7:check()
8:[if not exist]go to step 3[]
9:save()
10:response()
11:successfully uploaded()
X X
X X X
X
search data
Search id
no
yes
If exist?
[registration details]
invalid
validate
Valid
successfully registered
Correct?
No
Yes
Successfully login
invalid
validate
Valid
succesfully changed
sent mail
message form
send button
check
[found]
displaye response
File?
photo video
select file
[invalid]
[valid]
display responce
forum link
the forumdisplayed
invalid
valid
succesfully added
action response
invalid
Validate
invalid
succesfully inserted
display response
add event
add button
successfully
administrator
alumni
-alumni_id Alumni_officer
-image +manage_account() -address
-firs_name +manage_data()
-middle_name +sent_mail()
-last_name +manage_member()
-gender +manage_data()
account +manage_forum()
-DOB
-field_of_study event +manage_file()
+forgot()
-department -event_id
+update()
-geraduation_year +create() -subject
-address +view() -content
-phone_no -date
-email +add_event()
-employement +delete_event()
+view_event() file
+register()
-file_id
+sent_mail()
-file_name
+view_mail()
forum -file_type
+view_forum()
-forum_id -date
+comment-forum()
+search_member() -subject +view()
+update_profile() -content +upload()
-date
+add_forum()
+view_forum()
+delete_forum()
The purpose of designing is to show how the system is built and to obtain clear and enough
information needed to make the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer. If one want to changes to the system after it has been put in to operation
depends on the quality of the system design. So if the system is design effectively, it will be easy
to make changes to it.
During system design, we focus on the processes, data structures, and software and hardware
components necessary to implement it. The challenge of system design is that many conflicting
criteria and constraints need to be met when decomposing the system.
4.2. Class type architecture
The architecture which will be used for the proposed system is a two tier architecture where the
first tier is the client or the user side is a web browser containing user interfaces like data entry
interfaces; it is used to display information to the user. User directly interacts with the system
through the interfaces on this layer. The second layer is the storage layer (server side) which is
the SQLite database that stores the data. This increase the extensibility, maintainability and
portability of the new system. This class type architecture includes interface class, controller
class, business class, system class, and persistence class and persistence store.
Interface classes: - These classes initiate access to the logic of our system and this interface
class is the UI classes that provide people access to our system. An example of interface class is
login interface class.
Business classes: - These classes implement the concepts and focusing on the data aspects of the
business objects, plus behaviors specific to individual objects of the system. Examples:-Record
new member, uploading file, delivering information and generate discussion forum.
Controller classes:-these classes implement business logic that involves collaborating with
several domain classes or even other process classes.
Examples of Controller classes are password, user name and account type.
Persistence classes: - These classes can be used to the capability of store, retrieve, and delete
objects permanently without revealing details of the underlying storage technology.
Example of this class is database class.
System classes:-These classes provide operating-system-specific functionality for your
applications, isolating your software from the operating system (OS) by initiating OS-specific
features, increasing the portability of your application.
Persistence store: -These classes can be used to store data permanently on the database that we
can retrieve by other classes.
All types of classes interact with system classes. This is because new systems layer implements
fundamental software features.
Architecture of the system
Since our system modeling approach is object oriented, we have to describe the system in terms
of its architecture. Therefore, this session mainly concerned with the design part of alumni
system.
Http/
www.wuaams.com
Connection browser
user
interact
Http protocol
Database server
4.3.Class modeling
Class is abstraction that specifies the attributes and behavior of a set of objects, whereas objects
are entities that encapsulate state and behavior. Class diagram describe the structure of the
system in terms of class and object. Class models shows the classes of the system, their
Interrelationship (including inheritance, aggregation, and association), and the operations and
attributes and type of the classes
user
-user_name : string report
-password : string -report_id : string
-account_type : string -case : string
+view_event() : void -content : string
+View_member() : void -date : Date
+login() : void +generate() : void
*
alumni
administrator 1
-alumni_id : string
-image : string +manage_account() : void 1 Alumni_officer
-firs_name : string 1
-middle_name : string -address : string
1
-last_name : string * * 1 +manage_data() : void
-gender : char 1 1 +sent_mail() : void
-DOB : Date event 1 +manage_member() : void
-field_of_study : string account -event_id : string +manage_data() : void
-department : string -subject : string +manage_forum() : void
-geraduation_year : string 1 +forgot() : void -content : string +manage_file() : void
-address : string +update() : void -date : Date
-phone_no : int +craete() : void +add_event() : void 1 1
-email : string 1 +view() : void +delete_event() : void
-employement : string +view_event() : void
+register() : void *
*
+sent_mail() : void
+view_mail() : void
+view_forum() : void message *
+comment-forum() : void -sender_name
+search_member() : void *
-reciever_name file
+update_profile() : void -content -file_id : string
-date forum -file_name : string
* *
* -forum_id : string -file_type : string
* * -subject : string -date : Date
-content : string +view() : void
-date : Date +upload() : void
* +add_forum() : void
*
+view_forum() : void
+delete_forum() : void
4.4.Component modeling
A component diagram is used to show the physical architecture of the system in terms of its
component. It represents the components that compose an application or system. The
relationships, interactions and their interfaces are depicted. In some extent it shows which
component or object will be accessed by whom and what type of security infrastructure it is
using. It also describes the components dependencies that the SW has on the other SW
components (E.g. Software libraries) in the system Component.
view_event
visitor
view_member
search_alumni
view_detail
update_profile
alumni
view_forum SQLite database
persistence
registration
messaging
security login
manage_forum
generate_report
manage_event
office
upload_file
manage_data
manage_member
Request to
application program
Contents
stored
database
4.5.Deployment modeling
A UML deployment diagram describes how a system will be physically deployed in the
hardware environment. It depicts the a static view of run time configuration of processing node
(either physical machine or virtual machine node) and the components that run on those nodes
i.e. the hardware of the system and the software that is installed on that hardware. Its purpose is
to show where the different components the system will run physically and how they
communicate with each other. And also visualize topology of the physical components of a
system where the software components are deployed.
Purpose of deployment diagram
The name deployment describes the purpose of diagram. It is use full describe the hardware
components where software components are deployed. Most of the time deployment diagram is
related to component diagram. But component diagram is describes the component whereas
deployment shows they are deployed in hardware. Both this two diagrams special diagrams used
to focus on hardware and software components. Deployment mainly focuses on hardware
topology of a system.
Visualize hardware topology of a system
Describe hardware components used to deploy software components
Describing run time processing nodes.
Application server
view event
manage account
profile
view member
Database Server
view detail
registeration
messaging
DB
event
forum
manage data
manage member
generate report
upload file
server
database
application
layer
excution
environment
l
Web Browser
web server
http
-user_name : string
-password : string
-account_type : string
-address : string
+insert_data()
+search_data()
+update_data()
+delete_data()
+view_data()
+sent_mail()
+view_mail()
+search_member()
+view_detail()
+delete_member()
+add_event()
+view_event()
+delete_event()
+add_forum()
+view_forum()
+upload()
+login()
-user_name : string
-password : string
-account_type : string
+update()
+delete()
+view()
+login()
Figure 4- object model for administrator
meassage
-message id
-sender_name : string
-Reciver_name : string
-message : string
-date : Date
+sent_mail()
+view_mail()
account
-user_name : string
-password : string
-login_type : string
+login()
+forgot()
forum
-id
-subject : string
-content : string
-date : Date
+view()
+add()
+comment()
event
-subject : string
-content : string
-date : Date
+view()
+add()
+delete()
report
-report_id
-case : string
-content : string
-date : string
+generate()
Figure 4- object model for report
1. http://www.capterra.com/alumni-management-software/
2. https://www.bitrix24.com/uses/free-association-management-software-ams-alumni.php
3. http://www.yourmembership.com/articles/alumni-association-software-managing-your-
members/
4. https://www.getapp.com/customer-management-software/membership-management/
5. http://www.creatrixcampus.com/alumni-management-software
6. http://www.slideshare.net/ShankerGoud/alumni-portal-ppt
7. http://projectsgeek.com/2015/11/alumni-management-system-java-project.html
8. https://creately.com/diagram/example/hza130532/Alumni%20Association
9. http://web.mit.edu/annualreports/pres04/24.00.pdf
10. https://www.etsu.edu/125/documents/Tracking%20Alumni.pdf
11. http://pharmacy.utah.edu/alumni_old/AlumniAssocBylaws.pdf
12. http://www.iitk.ac.in/dord/power/documents/PoWER_AMP.pdf
13. https://www.jyu.fi/studentlife/ViestintCOMAlumniReportLong.pdf
14. http://www.hacc.edu/Alumni/AlumniLeadership/upload/Bylaws-of-the-Alumni-Assoc-
Sept-2011-rev4-6.pdf
15. https://200.iu.edu/doc/iu200-project-proposal-guidelines.pdf
16. http://alumni.unimelb.edu.au/sites/default/files/FINAL_Alumni%20Groups%20at%20the
%20University%20of%20Melbourne_Alumni%20Associations%20Guidelines_0.pdf
17. Barnard, Z. (2007). UJDigispace. Online Community Portals for Enhanced Alumni
Networking, Tese de Doutorado, University of Johannesburg. Johannesburg, South
Africa. [ Links ]
18. Newman, M. D., & Petrosko, J. M. (25 de January de 2011). Predictors of Alumni
Association Membership.
19. Research in Higher Education, pp. 52:738-759. [ Links ]