Cover Page

Table of content

1. System description

2. System Request

3. Feasibility analysis
- Technical
- Economical
- Organizational
4. Project planning - Gantt Chart

5. Information System Analysis

- Requirement collection *
- Requirements definition (functional and non-functional)
- Case diagram
- Class diagrams
- Activity diagrams
6. Design
- Class diagrams

7. Conclusion and Future Enhancements

 System description

Intuition Financial Services is a company that offers a variety of financial services for both individual and
corporate customers. Investing in the latest financial software and state-of-the-art customer-oriented
systems has always been a priority for the company. Intuition Financial Services IT department has
played an important role in the development of these systems.

However, in a recent meeting of department directors, the marketing director raised a concern about
delays and other issues related to handling requests for IT related changes. The IT director explained
that currently, the IT department handles change requests using a paper-based system. However, as the
number of change requests has increased significantly, the department is facing issues with handling
them. Following discussions on this matter, it was decided that the IT department should consider
development of a web-based system to automate the procedure of managing IT changes.

The IT department deals with requests of different types. They can be categorized as change requests,
software defect reports, and requests for new systems. These are generally referred to as Change
Orders. The new system should allow a change order to be submitted by designated employees in each
department. However, an order must be approved by the department director before being considered
by the IT department. When the IT department receives the request, an analyst reviews the change order
and categorizes it. Software defect reports type of orders are assigned a priority level and assigned to an
individual or a team to handle them. Change requests and requests for new systems must be reviewed
by CCB (Change Control Board). If CCB approves the change order, it assigns a priority level and the IT
department proceeds with assigning it to an individual or team to handle the change.

During this process, the analyst can also manage the order to change its status (for example, under
review, approved, assigned, completed, closed etc.). The department that requested the change should
be able to view the status of their request.

The web-based system should also allow authorized users (such as IT administrators) to generate various
reports. Specifically:

-Generate reports about orders by department.

-Generate reports about orders by status.

The system should also notify designated analysts when order requests are submitted.
 System Request

System request documents the business reasons for building the system and the value that the
system is expected to provide. The system request is a general name for any document
or system used to initiate the systems development life cycle process. This implies for instance,
if the framework should be conveyed at a specific value point or it should be conveyed by a
specific date, these eventual significant business necessities to list as a feature of the framework
demand record. The business esteem is basically how the framework is going to pay for itself.

In this project, the company offers a variety of financial services for both individual and corporate
customers. In order to increase the customer base, the company invest in the latest financial
software and state-of-the-art customer-oriented systems. Development of these systems, has
always played a significant role to improve the IT related issues and deal with the problem to
maintain the lead in providing the best IT solutions to the customers.

The change order requests are been carried out with web application to maximize the efforts and
deliver the IT solution as quick as possible with proper outcomes. The system request is been
modified from paper-based handling to the web-based handling, this ensures the customers to
get required solution for their IT related concern in given time period.
 Feasibility analysis:

Feasibility deals with step-by-step analysis of the system. Analysis showed that this project was
feasible in all respects. Three kinds of feasibility factors are considered:

Technical:
The main aim of our project is to solve the issues related to handling requests for IT related
changes. At present, the IT division handles change demands utilizing a paper-based
framework. However, as the quantity of progress demands has expanded essentially, the
division is confronting issues with dealing with them Hence, there is the need of
development in paper-based system and generate the web-based system to automate the
procedure of managing IT changes.
Order handling is the next important thing that must be done in our project to process the
orders in distributed manner and complete the ongoing task as soon as possible by setting
the priority values by analyzing the change requests.

Economical:
The system is developed only using that software that are very well used in the market, so
there is no need for installation of new software. Hence, the cost incurred towards this
project is negligible.
Further, the framework is been also designed by just utilizing that product that are very
much utilized in the market, so there is no requirement for establishment of new
programming. Thus, the expense acquired towards this undertaking is immaterial.
For web-based system the skills required for making the web-based applications are easily
available online via various website building sites. Hence, there is no need of special skillsets
to buildup the web-based system. Therefore, the system design becomes more economical.

Organizational:
Organizational analysis is been carried out to determine whether a proposed idea has
sufficient management expertise, organizational competence and resources to successfully
complete the new change order requests.
Project planning - Gantt Chart
 Information System Analysis

Requirement collection:
Project Requirements are defined as the features, functions, or tasks that must be completed in
order to successfully wrap up a project. Requirements provide a crystal-clear picture of the
work that needs to be done so you can plan your project appropriately to ensure the goals are
met and you achieve the desired final output of your project.

For this project, in order to build the web-based system to automate the procedure of
managing IT changes, the required materials are easily available in the market and for
electronic framework the abilities required for making the electronic web applications are
effectively accessible online through different site building locales. This will feature the
accelerated process in handling the orders and categorizing them according to the change order
requests, giving the orders proper priority will allow the customers to get the end results more
quickly if required. The function of the project is to automate and decrease the workload on the
IT department. Tasks of the systems are been evenly distributed and classified which will
ensure the accurate and expedite solutions for the change orders requested.

Requirements definition (functional and non-functional):

Functional Requirements:
The functional requirement is describing the behavior of the system as it relates to the system's
functionality. Functional requirements define what a system is supposed to do.

An example of a functional requirement would be:

A system must send an email whenever a certain condition is met (e.g. an order is placed, a
customer sign up, etc.

Non-Functional Requirements:
A non-functional requirement (NFR) is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviors. The non-functional
requirement elaborates a performance characteristic of the system. Non-functional
requirements define how a system issupposed to be.

A related non-functional requirement for the system may be:

Emails should be sent with a latency of no greater than 12 hours from such an activity.
Case Diagram:
Class diagram:
Activity diagram:
 Design

- Class diagram:
 Conclusion and Future Enhancements

-From this project, the pace of delivering the IT solution from the IT Department to the customers
are been increased substantially.
-Due to use of web-based framework, the time period of delivering the IT solution to customers
in been reduced. Hence, lot of time is been saved.
-It is easy to maintain the track record of each orders in web-based system than in the paper-
based system.
-The assigning of workload is been proper distributed among the department to ensure the
precise and timely managed solution to be delivered to customers.
-Also, it becomes easy to the customers to check the current status of their request and order
the report of the ongoing solution at any stage of the process.