Analysis And Design Feasibility Computer Science Essay

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

This chapter will describe the process of factual data, comprehend the processes involved, identify problems and recommend feasible suggestions for improving the system functionalities. The first step is the feasibility studies to identify the importance of the proposed system, then the requirement gathering, where the investigation of the business processes and documentation of the new system.

4.2 FEASIBILTY STUDIES

Feasibility study here is done to check the viability of the project under consideration. Theoretically several types of feasibilities were conducted, but mainly three types of feasibilities conducted are explained below.

4.2.1 ORGANIZATIONAL FEASIBILITY

This aspect defines the acceptability of the system. Will there be no problems such as internal and external issues. It shows that the current work supports the new system and social factors, that this system will make the work easier for the users of this system.

Ticket booking is faster because system is easy to use (user friendly).

can avoid double booking using online system

error occurrence is reduced

manager can make changes of price, movies and seats

Reduce effort and frustration for movie goers in scheduling, especially in searching for latest movies.

4.2.2 ECONOMICAL FEASIBILITY

To check the economic feasibility, cost and benefit analysis is done in which expected cost is evaluated. these include:

the need of new software to develop the system

acquire more computer units to use the system, different for staff, and administrator

the system will economically utilize resources for the development

4.2.3 TECHNICAL FEASIBILITY

The new system requires trained personnel to work with the system in overall clerks and staffs with computer literacy are sufficient.

Provide training to staff of the organization

The choice of processing unit depends on the user

The technology can be easily applied to the conduct of the organization.

4.3 SYSTEM ACTORS

Actors of the system are basically four in general, which include customer, an unregistered user, staff and the administrator, with each user having a distinct role in the system, the unregistered user and customer have similarities in some of their functionalities.

4.3.1 Unregistered User.

This user can also be referred to as guest, which is basically a first time user who can only view movies in show and register with the system to be come registered customer.

4.3.2 Customer

Clearly the system is developed for a customer to reserve tickets for movies in show, this user has the ability login, query movies, and select seat

4.3.3 Administrator

This user monitors all activities in the system, from maintaining users, updating seat allocation, package pricing to adding and deleting movies. The administrator can also reply customers' complain.

4.4 REQUIREMENT SPECIFICATION

4.4.1 Functional Requirement

Register user

Viewing options {package price, movie information and replied complain}

User login

Make complain

Make reservation {select movie, package and seat}

Cancel reservation

Handle reservation

Check-in customers

Update movies {add, delete or edit}

Manage users

Handle complain {reply}

Package pricing

View reservation log

logout

4.4.2 Non-Functional Requirement

System should generate reservation confirmation number and save

System should retrieve information fast

System saves customer registration and reservation information

System must authenticate users

4.4.3 User Requirement

Users can register using the system registration form

System should provide users with ability to login annd logout with valid ID and password

System shuold provide customer with ability to view movies in show

Customer should be able to reserve ticket using the system

Customer can be able to make complain with the system

Administrator can be able to handle staff information using the system

Administrator must be able to manage movie, package and seat information.

4.5 UML DIAGRAMS

Fig. 3 use case diagram for MCTRS systemThe figure below is a use case diagram which describes the behavior of the MCTRS system as it responds to external request from the system users.

4.5.1 Sequence Diagram

Fig. 4 Handle reservation sequence diagramA sequence diagram describes the interaction of processes in a function, MCTRS system functions are expressed in th e Figures below.

Fig.5 make reservation sequence diagram

4.5.1.1Use case Specification

Function; Make reservation

Actors; Customer

Description; Users will use this function to reserve for movie ticket, were the function generates a unique code.

Input; Select movie, time, seat, and package

Input source; Mouse

Output; Reserved ticket information displayed

Pre-condition; Registration and login

Post-condition; none

Function; Handle reservation

Actors; Staff

Description; staff user this function to verify and confirm a reservation by inserting a customer's reservation code.

Input; unique reservation code

Input source; keyboard and mouse

Output; Reserved tickets information

Pre-condition; handle reservation

Post-condition; None.

4.5.2 Class Diagram

This is a constant diagram that describes the fundamental structure of MCTRS system that shows the system classes, their operations, attributes and relationships between them.

4.6 CONCLUSION

After gathering all the information that will help to develop a reservation system for Misau Cinema. The analysis and design of the system was done in this chapter using the feasibility studies and UML diagrams, which gives detailed description of the system.