Post on 11-Dec-2014
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
1.Scope Of System
Event management is the application of project management to the creation and development of festivals, events and conferences.
Event management involves studying the intricacies of the brand, identifying the
target audience, devising the event concept, planning the logistics and coordinating
the technical aspects before actually executing the modalities of the proposed
event. Post-event analysis and ensuring a return on investment have become
significant drivers for the event industry.
To organize event with maximum usage of resources (inward as well
as outward) as time bounding in an efficient way.
In order to facilitate and simplify these actions one of the major
tool is to have automated EVENT MANAGEMENT SYSTEM.
An Event includes…….
Competition, Workshop
Conference, meetings
Hands-on training
Marketing exhibition
Many others . . .
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
2.Problem Areas In Existing System
Scheduling Problem
Event Scheduling is major administrative activity in any event.
A number of competitions arranged by the corresponding
committee members are allocated into a number of available
classroom and a number of timeslots, competitions to
constraints.
Time Slot Assignment
The Event Scheduling is a time scheduling for all the classes of a
school, avoiding competitions two classes at the same time, and
vice versa. This means that an event may be placed in the
timetable only in such a way that it doesn’t violate constraints.
Currently Manual System
The current system is totally manual so there is a need of large
amount of Employees. All the works are done on paper so there
is a lot of wastage of paper. Due to some accidental problem
data might be lost because there isn’t any proper storage
facility.
Very Tedious Process to get all Details
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
If you required getting the detail of student that is name,
semester year, college name, copy of registration form to create
the certificate. You have to search for all the papers and then
collect all the detail to create the certificate. So report can’t
create very easily
3.Need For the New System
Inefficient Existing System
The current manual system is inefficient to handle the work as
the volume of data is increasing day by day.
Time Savage
The main reason for new system is to save the time in every
aspect of retrieving, storing, processing tasks.
Reduction of Overhead
The extra overhead in storing and retrieving should be also
reduced to major extent.
Storage of Data
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
The storage of data is needed because in manual system data
might be lost and member is responsible for the lost of data.
4.Objectives to be Fulfilled
Time Scheduling done easily
In this time Scheduling problem is solved easily with the time
slot assignment. Based on time one member can access only a
single class at a time. If there is any assignment of a member on
a same time in different class room then it can’t be generated.
According to Requirement
In the new system many of the needs will be fulfilled according
to the need of the event.
Storing of Data
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
In the new system the data is stored in database. And there is
less possibility of lost of data.
User Friendly
This system is user friendly with good interface, so user can
work with the application very easily.
Reports
Reports can be easily generated in the system so that the exact
information regarding the sub-events will be displayed in the
system.
5.Requirement Analysis
Register a Student
It is used when the on the spot registration of new student is
taking participate in the event then all the personal detail of a
student is filled up.
Record performance of a Student
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
The performance of a particular student in particular
competition can be stored as per student id. This performance
of the student can be further used when the certificate of a
particular student will e produced at the end of the event.
Generate Various Reports
As per the requirements all the reports is generated. If that is
annual report of the whole event so all the data about the event
is produced in the report. If report is used for the office person
than it can be easily generated.
Generate Timetable
Time table of the particular sub-event and particular resource
is generated as per the time allotment to the particular subject.
Generate Rules
Rules of the particular competition are defined in the
information of each competition.
6. System Requirement Specification
6.1 Hardware Specification
Recommended Hardware Specification
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
Monitor : 13’’ Color Monitor
Keyboard : Any Standard 104 key board
Mother Board : Any branded mother board
RAM : 512 MB or Higher
HDD : 40GB or Higher
Processor : Intel(R) Pentium(R) CPU 3.00GHz
Mouse : Any Standard mouse
Printer : Any printer
Minimum Hardware Specification
Monitor : 640 X 480 Displays
Keyboard : Any Standard 104 key board
Mother Board : Any branded mother board
RAM : 256 MB
HDD : 40GB
Processor : Intel(R) Pentium(R) 2 or Other
Mouse : Standard mouse
Printer : Any printer
6.2 Hardware Specification
Document Tool : Microsoft Word 2007
Diagram Tool : Microsoft Visio 2003
Operating System : Windows xp
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
Diagrams
7.Class diagram
Overview:
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
The class diagram is a static diagram. It represents the static view of an application.
Class diagram is not only used for visualizing, describing and documenting
different aspects of a system but also for constructing executable code of the
software application.
The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the
modeling of object oriented systems because they are the only UML diagrams
which can be mapped directly with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations,
collaborations and constraints. It is also known as a structural diagram.
Purpose:
The purpose of the class diagram is to model the static view of an application. The
class diagrams are the only diagrams which can be directly mapped with object
oriented languages and thus widely used at the time of construction.
The UML diagrams like activity diagram, sequence diagram can only give the
sequence flow of the application but class diagram is a bit different. So it is the most
popular UML diagram in the coder community.
So the purpose of the class diagram can be summarized as:
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
8.Use case diagram
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
Overview:
To model a system the most important aspect is to capture the dynamic
behavior. To clarify a bit in details, dynamic behavior means the
behavior of the system when it is running /operating.
So only static behavior is not sufficient to model a system rather
dynamic behavior is more important than static behavior. In UML there
are five diagrams available to model dynamic nature and use case
diagram is one of them. Now as we have to discuss that the use case
diagram is dynamic in nature there should be some internal or external
factors for making the interaction.
These internal and external agents are known as actors. So use case
diagrams are consists of actors, use cases and their relationships. The
diagram is used to model the system/subsystem of an application. A
single use case diagram captures a particular functionality of a system.
So to model the entire system numbers of use case diagrams are used.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
Purpose:
The purpose of use case diagram is to capture the dynamic aspect of a
system. But this definition is too generic to describe the purpose.
Because other four diagrams (activity, sequence, collaboration and
State chart) are also having the same purpose. So we will look into
some specific purpose which will distinguish it from other four
diagrams.
Use case diagrams are used to gather the requirements of a system
including internal and external influences. These requirements are
mostly design requirements. So when a system is analyzed to gather its
functionalities use cases are prepared and actors are identified.
Now when the initial task is complete use case diagrams are modeled
to present the outside view.
So in brief, the purposes of use case diagrams can be as follows:
Used to gather requirements of a system.
Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
9.Activity diagram:
Overview:
Activity diagram is another important diagram in UML to describe
dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an
operation of the system.
So the control flow is drawn from one operation to another. This flow
can be sequential, branched or concurrent. Activity diagrams deals with
all type of flow control by using different elements like fork, join etc.
Purpose:
The basic purposes of activity diagrams are similar to other four
diagrams. It captures the dynamic behaviour of the system. Other four
diagrams are used to show the message flow from one object to
another but activity diagram is used to show message flow from one
activity to another.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
Activity is a particular operation of the system. Activity diagrams are
not only used for visualizing dynamic nature of a system but they are
also used to construct the executable system by using forward and
reverse engineering techniques. The only missing thing in activity
diagram is the message part.
It does not show any message flow from one activity to another.
Activity diagram is some time considered as the flow chart. Although
the diagrams looks like a flow chart but it is not. It shows different flow
like parallel, branched, concurrent and single.
So the purposes can be described as:
Draw the activity flow of a system.
Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the
system.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
8.1. Event Management:
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
8.2. Registration process:
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
10.Sequence diagram:
Overview:
From the name Interaction it is clear that the diagram is used to describe some type
of interactions among the different elements in the model. So this interaction is a
part of dynamic behaviour of the system.
This interactive behaviour is represented in UML by two diagrams known as
Sequence diagram and Collaboration diagram. The basic purposes of both the
diagrams are similar.
Sequence diagram emphasizes on time sequence of messages and collaboration diagram emphasizes on the structural organization of the objects that send and receive messages.
Purpose:
The purposes of interaction diagrams are to visualize the interactive behaviour of
the system. Now visualizing interaction is a difficult task. So the solution is to use
different types of models to capture the different aspects of the interaction.
That is why sequence and collaboration diagrams are used to capture dynamic
nature but from a different angle.
So the purposes of interaction diagram can be describes as:
To capture dynamic behaviour of a system.
To describe the message flow in the system.
To describe structural organization of the objects.
To describe interaction among objects.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach
11. Collaboration diagram:
Overview:
From the name Interaction it is clear that the diagram is used to describe some type
of interactions among the different elements in the model. So this interaction is a
part of dynamic behaviour of the system.
This interactive behaviour is represented in UML by two diagrams known as
Sequence diagram and Collaboration diagram. The basic purposes of both the
diagrams are similar.
Sequence diagram emphasizes on time sequence of messages and collaboration diagram emphasizes on the structural organization of the objects that send and receive messages.
Purpose:
The purposes of interaction diagrams are to visualize the interactive behaviour of
the system. Now visualizing interaction is a difficult task. So the solution is to use
different types of models to capture the different aspects of the interaction.
That is why sequence and collaboration diagrams are used to capture dynamic
nature but from a different angle.
So the purposes of interaction diagram can be describes as:
To capture dynamic behaviour of a system.
To describe the message flow in the system.
To describe structural organization of the objects.
To describe interaction among objects.
19
SADOOA
Case Study-System Analysis & Design Using Object Oriented Approach