Chapter 4

ONLINE HELP DESK SYSTEM ANALYSIS
CHAPTER-4
SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM

At present the current system works manually. It provides the information in written or orally
within the organization/campus. Individual has to spare his time and energy in order to obtain
even the basic information regarding the organization/campus. Apart from this there can be a
long and tedious procedure in order to have a solution regarding any particular query. In
addition to all this an individual has to move from one place to another to get any
information.
4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

 First of all the main problem with the current system is that it is quite time consuming
sometimes.
 It has long procedures to obtain the information.
 It does not provide all information regarding any query at a time.
 It has time limitation, individual has to apply within the working hours of an
organization/campus.
 Another problem with the current system is that suppose an individual wants the detail
or any information about more than two departments, then he has to approach all the
departments personally.
 In addition, current system does not have good security features regarding the
organization/campus.
4.3 REQUIREMENT OF NEW SYSTEM

 Requirements Specification:
Requirements Specification adds further information to the requirements definition:
 Non- functional Requirements:
Product requirements:
16
Swami Sachchidanand Polytechnic College
(Computer Engineering)
• Usability:
The interface should use terms and concepts, which are from the experience of
the people who will make most of the system.
• Efficiency:
The system must provide easy and fast access without consuming cost.
• Reliability:
User should be surprised by the behavior of the system and it should also
provide meaningful feedback when errors occur so that user can recover.
 Functional Requirements:
The only requirement is to automate the whole system as a good source of providing
the reliable information to that the user so that he can get the maximum benefit of
the services provided by the campus/organization.
4.4 FEASIBILITY STUDY

The main aim of the feasibility study activity is to determine whether it would be financially
and technically feasible to develop a project. The feasibility study activity involves the
analysis of the problem and collection of all relevant information relating to the product such
as the different data items which would be input to the system, the processing required to be
carried out on these data, the output required to be produced by the system as well as the
various constraints on the behavior of the system. During feasibility study most of the high-
level architectural design decisions are made.
The collected data are analyzed to arrive at the following:
 An abstracted problem definition, which considers only the important requirements
and ignores the rest.
 Formulation of different solutions strategies.
 Analysis of alternative solutions strategies to compare their benefits and shortcomings.
This analysis usually requires making approximate estimates of the resources required,
cost of development and development time for each of the options.
Operational Feasibility:
17
Proposed projects are beneficial only if they are turned into information system that will meet
organization’s operating requirements. This test of feasibility asks if the system will work
when it is developed and installed. Are there any barriers to implementation? A few questions
that may be of help to test the operational feasibility of a project are:
1. Is there sufficient support for the project from the management? From users? If the
current system is well liked and used to extent that person will not able to see reason
for a change, there may be resistance.
Ans: yes there is enough and more support and motivation from the management. The
existing system has got series of limitation that has been mentioned in the earlier chapters.
2. Are current methods acceptable to the users? If they are not, users may welcome a
change that will bring about a more operational and useful system.
Ans: No the current methods are not completely acceptable to the users, which leaded to
the requirement of the new enhanced software.
3. Have the users being involved in the planning and development of the project?
Ans: yes, the users are completely engrossed in the planning and development of the
project, at each stage the users gives the feed back to the developers as per their
requirements.
Technical Feasibility:
The technical issues usually raised during the feasibility stage of the investigation include
these,
 Does the necessary technology exist to do what it is suggested (and can be it
required)?
 Are developers aware of these technologies?
 Are there technical guarantees of accuracy, reliability, is of access security?
 Can the system be expanded if developed?
Schedule Feasibility:
Projects are initiated with a specific deadline. We need to evaluate whether the deadline are
mandatory or desirable. Time is one of the critical factors in the development of any system
and hence proper scheduling is very essential for the timely completion of a project.
Financial and Economic Feasibility:
18
A system that can be developed technically and that will be used if installed must still be a
good investment for the organization. Financial benefits must equal or exceed the costs
incurred to develop the system. Some of the questions that are generally raised are as follows,
 Is the organization having the suitable budget to develop the proposed system?
 How much profit can be earned from the system by the organization?
 Would it be cost-effective to develop the system or it is worthwhile to remain with
current system?
4.5 FUNCTIONS OF SYSTEM
19
4.5.1 Use Case Diagrams:
Fig 4.1: Use case Diagram of User
20
Fig 4.2: Use case Diagram of Facility head
21
Fig 4.3: Use case Diagram of Assignee
22
4.6 DATA MODELING

4.6.1 E-R diagram:
Fig 4.4: E-R diagram

4.6.2 System Activity
Activity diagram
Conventions used in drawing the Activity Chart here, are given as below:
23
LOGIN
Yes No
AS AN END- AS AN AS AN REGISTER
USER ADMINISTRATORR ASSIGNEE
2 3
VIEW
CHANGE SUBMIT
ANSWERED
PASSWORD QUERIES
QUERIES
4 24
Fig 4.5: Activity Diagram for End-users
Fig 4.6: Activity Diagram for Facility-Head
25
CHANGE VIEW NEW UPDATE

REQUEST REQUEST
26
(Computer4Engineering)
Fig 4.7: Activity Diagram for Assignee
LOGOUT
4.7 FUNCTIONAL AND BEHAVIORAL MODELING
27
Dataflow Diagrams
Data-flow design is concerned with designing a sequence of functional transformations that
convert system inputs into the required outputs. The design is represented as data-flow
diagrams. These diagrams illustrate how data flows through a system and how the output is
derived from the input through a sequence of functional transformations.
Data- flow diagrams are a useful and intuitive way of describing a system. They are normally
understandable without special training, especially if control information is excluded. They
show end-to-end processing: that is, the flow of processing from when data enters the system
to where it leaves the system can be traced.
Conventions used in drawing the Data Flow Diagrams here, are given as below:
4.7.1: Context Diagram
28
29
Fig 4.8: Context Diagram
4.7.2 0th Level DFD:
User login
User Request Login
For Authorized User
Reply
Information
Registration,
Assets Search
30
Admin login
Administrator
Logi
n
Check Information
requests,
Reply
assign
requests to
assignee
Assignee login
Assignee Request Login
For Authorized User
Reply
Answer the Information
requests,
update, add,
delete the
requests. 31
Fig 4.9:0th Level DFD for End-user, Facility Head and Assignee
1st Level DFD:
Administrator User Id Authent

-itcation
Password
Check Status
Login_detail
View
Queries
submitted
By the
users
Assign the Assignee’s Add, Delete

task to the Update,
task Solve queries.
assignees.
processedRequest
32
Fig 4.9: 1st Level DFD
4.8 MAIN MODULES OF NEW SYSTEM

Project work is divided in three modules namely: create request, authenticate request and
solve request.
 In Create request module, request will be created by the students.
 Authenticate request module, in this module administrator will authenticate the
assignees with the queries or requests submitted by the students/user.
 Solve request module, in this module Assignee will provide students/users with the
appropriate solutions to their queries submitted.
4.9 SELECTION OF HARDWARE AND SOFTWARE AND

JUSTIFICATION
Introduction To .Net Platform:
Visual studio .Net is now built on top of the.net framework. This will be significant change
from Visual Basic 6.0.The new .Net Framework takes application development to viewing the
Internet as your new operating system. Your applications will no longer recognize hardware
as a boundary limitation this is an evaluations of the Window DNA Model, this new frame
work is built on open internet protocol for a Standardization interoperability between platform
and programming language the New .Net framework also allows the creation of new types of
applications. Applications will now run using the common Language Runtime (CLR).All .Net
applications will use this same runtime environment, which allows your Visual Basic
applications to run on equal ground with other languages. The CLR allows Visual basic to
provide inheritance and free threading, whose absence created two glaring limitations to
visual basic application. Visual basic.Net is object oriented. Every thing is now an object, and
33
every object is inherited from standard base class. Another benefit of CLR is common type
system. Which means that all programming Languages share the same types This greatly
increases interoperability between Languages. The internet has entered a new phase. First it
was used to display static Web Page as time change and the business requirement is increased.
At that time the Business soon found that this did not help them significantly. Next, the
internet has evolved to dynamic content and allowing electronic commerce. The next step is
to move towards complete application running on the internet. Visual Basic.Net also promotes
these new web applications. Web services allow objects to be located anywhere on the
internet and to be called from any application across the internet ( no more trying to get
DCOM configured). Of course, extending applications across the internet will increase
security risks. The .Net Framework has many security features built-in to it to protect your
applications. ASP.NET is one of the most popular languages for building scalable, Interactive
web sites. Several of the highest traffic web sites on the internet employ ASP.NET.Prominent
examples include the Home Shopping Network, MSN, and the Microsoft site itself.
What is .NET?
.NET is a “revolutionary new platform, built on open internet protocol and standards with
tools and services that meld computing and communication in new ways”. The .NET
Framework is just part of Microsoft’s overall .NET platform strategy. The framework is made
up of the Common Language Runtime environment, Base Class Library, and higher-level
frameworks such as ASP.NET and Windows Forms as shown in Figure 4.10.
34
Fig 4.10: .NET Framework

The common language runtime (CLR) is the foundation that sits on top of the Windows
operating system. The base class library is a set of hundreds of classes that are provided as
part of the framework to help us build applications that will execute in the CLR. To make
building applications even easier Microsoft provides some higher level frameworks like
ASP.NET and Windows Forms that utilize and extend the functionality provided by the Base
Class Library.ASP.NET greatly simplifies the building of Internet applications by using Web
Forms and Web Services. Windows forms provide the ability to develop for the rich
environment that the Windows platform provides.
ASP.NET:
ASP.NET is used to create programmable Web pages as part of web form applications. Not
only can ASP.Net produce dynamic Web pages, but it can also tailor them to the browser
being used by the user. Development in ASP.Net is much easier because it contains a wide
range of object-oriented server-side controls ready for use in applications. ASP.Net actually
supports four different types of control:
35
HTML Server Controls

These are programmable HTML elements that are exposed to the server. HTML server
controls expose an object model that maps very closely to the HTML elements that they
render.
Web Server controls
These controls have more built-in features than HTML server controls. Web server controls
include not only form-type controls, such as buttons and text boxes, but also special-purpose
controls, such as calendar. Web server controls are more abstract than HTML server controls
in their object model does not necessarily reflect HTML syntax.
Validation controls
These are controls that incorporate logic and that can be attached to an input control to test
what the user enters. Some validation controls check for a required field, a specific value or
pattern of characters, that a value falls within a specified range, and so on.
User controls
These are custom controls created as Web form pages. Web forms user controls can be
embedded in other Web Forms pages and provide an easy way to create menus, reusable
elements, toolbars. Asp.Net also implements an event-driven programming model that is very
similar to the Visual FoxPro 7.0 so that custom code be attached to events and executed when
the event Fires. Every times a web page(which is an object itself) is called, a series of stages
are run through :initializing, processing and disposing of information. One key difference
between the event sequence in asp.net and Visual Foxpro 7.0 is that the Page_Init event
comes before page Load in Asp.Net. One of the greatest benefit of Asp.net over classic ASP
is that Asp.Net reduce the amount of coding needed to write an application. With the
introduction of server-side control, it is no longer necessary to write the complex HTML and
scripts that were necessary to render the pages on different browser. In addition ASP.Net can
automatically keep track of the state between Web Pages, without all the tedious
programming necessary in classic Asp.net tests have shown that rendering pages using
Asp.net is typically 2-3 times faster than using classic ASP.
36
ADVANTAGES: -
Separation of code from the content.Asp.Net allows the developer to separate script code from
html. This allows for a clean Separation of code from content and formatting and promotes
code reuse.
 Executable portion of a Web application compiled so they execute more quickly than
interpreted scripts.
 On-the-fly updates of deployed Web application without restarting the server.
 Access to the .NET Framework, which simplifies many aspects of windows
programming.
 Use of the widely known visual basic programming language, which has been
enhanced to fully support object oriented language.
 Automatic state Management for controls on Web page (called server controls) so that
they behave much more like windows controls.
 The ability to create new customized server controls from existing controls.
 Built in security through the windows server or through other automatically
/authorization methods.
 Integration with ADO.NET to provide database access and design tools from within
Visual Studio.NET.
 Full supports for Extensible markup language (XML) cascading style sheets (CSS)
and other new and establishment web standards.
 Built in feature for caching frequently requested web pages on the server, localizing
content for specific language and culture, and detecting browser capabilities.
Support for compiled languages. While ASP.Net still supports the traditional set of scripting
languages, support is also provided for fully compiled language, Instead of using vbscript the
developer can use VB.NET and access features such as strong typing and object oriented
programming.Asp.Net pages are precompiled to byte code and just in time compiled when
first requested.
Greater support for different browsers via server side controls and events. Following object
oriented design principles, ASP.NET pages make use of server side controls called ASP.NET
Web controls. These controls are instantiated on the server, and like regular objects they have
37
associated methods, properties, and events. The advantage of the server side controls is that
they render themselves on the client as standard HTML 3.2 (optionally DHTML), depending
on the capabilities of the client browser.
38

Chapter 4

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 4

Uploaded by

Copyright:

Available Formats

ONLINE HELP DESK SYSTEM ANALYSIS

4.1 STUDY OF CURRENT SYSTEM

4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

4.3 REQUIREMENT OF NEW SYSTEM

4.4 FEASIBILITY STUDY

4.5.1 Use Case Diagrams:

Fig 4.1: Use case Diagram of User

Fig 4.2: Use case Diagram of Facility head

Fig 4.3: Use case Diagram of Assignee

4.6 DATA MODELING

Fig 4.4: E-R diagram

Fig 4.5: Activity Diagram for End-users

Fig 4.6: Activity Diagram for Facility-Head

CHANGE VIEW NEW UPDATE

Fig 4.7: Activity Diagram for Assignee

4.7 FUNCTIONAL AND BEHAVIORAL MODELING

4.7.1: Context Diagram

Fig 4.8: Context Diagram

4.7.2 0th Level DFD:

User Request Login

For Authorized User

Assignee Request Login

For Authorized User

1st Level DFD:

Administrator User Id Authent

Assign the Assignee’s Add, Delete

Fig 4.9: 1st Level DFD

4.8 MAIN MODULES OF NEW SYSTEM

4.9 SELECTION OF HARDWARE AND SOFTWARE AND

Fig 4.10: .NET Framework

HTML Server Controls

You might also like