The Purpose Of System Analysis 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.

The purpose of system analysis is the to discuss the nature of the computer system development process ,outline the activities within the requirement analysis phases, find out the fact of the project in theoretically and finally understand the nature and role of use cases descriptions ( Scott Raeburn, 2008) .

3.1 Introduction:-

After analyzing the requirements of the proposed system, the next step is to analyze the problem briefly and understand its circumstance. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.

3.2 Analysis Model:-

This document played an important role in the development of the life cycle (SDLC), since it is the full requirements of the system are described. That means for use by developers and the base during the test phase. Any changes to the requirements in the future will have to go through formal change approval process (Booch, Rumbaugh and Jacobson, 1999).

Analysis model is already discussed in the chapter 2 Methodologies section (spiral model) (Bennett, Skelton and Lunn, 2005).

3.3 Study of the system

In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browser interface. The GUI’S at the top level have been categorized as

Administrative user interface

The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Data updating along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.


The system after careful analysis has been identified to be presented with the following modules:





General Public

Web Registration




3.4.1 Administrator:-

Administrator is treated as a super user in this system. He can have all the privileges to do anything in this system. He is the people who received the Profile of a Doctor and accept/reject the registration.

He is the person who receives the Complaints from the Patient and redirects to respective Doctor for response.

He should have a facility to communicate using chat, email facility with other stakeholders.

He should take care of Backup of Patient, Doctor Details and maintain history.

Another tasks done by the administrator is he can generates reports, log files, backup, and recovery of data any time.

3.4.2 Doctors:-

He should able to see a Patient’s appointment details on a particular date.

Also if the Patient is already visited, able to see the previous Prescription given the Patient, Disease History, Visiting details, etc.

They should be able to see the Feedback given by the Patient.

They should be able to see the Complaints given by the Patient and must provide the Response for that.

He should have a facility to communicate using chat, email facility with other stakeholders.

3.4.3 Patients:-

They should have a facility to register to the site with their Personal data along with Health details Height, Weight, Family inherited Diseases, Blood Group, etc.

Being a Patient (after registration) should able to take an Appointment of a Doctor visit.

They should have a facility to give Complaints about Kiosk Manager or Doctor Service.

They should able to Search for a Doctor and can see the Doctor’s Profile for an appointment.

3.4.4 Managers:-

He should be able to provide an Appointment of a Doctor to a Patient on request (based on Doctor’s available timings).

They should be able to see the Complaints given by the Patient and must provide the Response for that.

He should have a facility to communicate using chat, email facility with other stakeholders.

They should have a Search facility to find a Patient or Doctor and can check their Profile or History details.

3.4.5 General Public:-

General Public (i.e. Guest visitors) should able to access the site Home page, Registration Page, etc. common pages of the site.

This user should able to see the Doctors Schedules, Contact details, Specialization details, etc.

They should able to Search for a Doctor.

3.4.6 Web Registration:-

The system has a process of registration. Every end user must register to use the all facilities to use the system effectively and to communicate the Doctor by using the Web-enabled chat. Whenever a User registration completed automatically he/she can get a user id and password. By using that user id and password he/she can log into the system.

3.4.7 Search:-

This system provides search facility to the patients. Patient can search for Doctors and their available timings for take appointments

3.4.8 Reports:-

Different kind of reports is generated by the system.

Patients History and prescriptions

Doctors list

Lab reports

Daily & Monthly Reports, Appointment list of Patients for Kiosk Managers

3.4.9 Authentication:-

Authentication is nothing but providing security to the system. Here every must enter into the system throw login page. The login page will restrict the UN authorized users. A user must provide his credential like user Id and password for log into the system. For that the system maintains data for all users. Whenever a user enters his user id and password, it checks in the database for user existence. If the user is exists he can be treated as a valid user. Otherwise the request will throw back.

3.5 Requirement Analysis:-

The main purpose for the preparation of this document is to provide an overview and analysis requirements of the current system or situation and to determine the operational characteristics of the system and this paper will play an important role in the development life cycle (SDLC) and fully describes the system requirements. It is intended for use by developers and base during the test phase. Any change in conditions in the future will have to go through the formal approval process changes.

3.5.1 Functional requirements:-

Results from computer systems are mainly required to communicate the results of processing the user. They are also used to provide a permanent copy of the results for later consultation. Various types of results are generally

Results External whose destination is outside the organization.

Results of internal whose destination is within the organization and they are Main Interface User's computer.

Operational use of products which is just within the department computer.

Interface products, which include direct user communication.

In general, the results are described using terms such as type of output, content output, output format, output location, frequency of output, output volume and Sequence Output. There is always desirable to print or display the data as it is held in a computer. It should be placed as a form of output that is more suitable. Media (Scott Raeburn, 2008):

In the next stage is to decide which medium is most suitable for output. The main considerations when deciding to media outputs are:

Suitable for application specific device.

The need for a hard copy.

Required response time.

Place of the users.

Software and hardware available.

Keeping in view the project description is to have results mainly comes under the category of internal results. The main results desired by the specification requirements are: the results were needed to generate heat and a copy of, and actions to be viewed on the screen. Given these results, forms of output are taken from the results, which are currently being taken after manual processing. Standard printer will be used as output media for hard copies.

Input Design(Scott Raeburn, 2008):

This is an important part of system design. The purpose of the design data would produce a cost-effective method of input, to achieve the highest possible accuracy and to ensure data that is acceptable and understood by users. Main Stages of data are: data entry, data transcription, data conversion, data verification, data control, data transmission, data validation, data correction. After that, we need to make a choice of I / p media. The media can describe performs symbol: type of input, format flexibility, speed, accuracy, methods of verification, and rejection rates, ease of correction, storage and handling requirements and security, easy to use, portability. Keeping given on the description of the types of inputs and input media, may be said that most of the inputs are internal and interactive form. How, data entry is to be allocated directly to the user, the keyboard can be considered to be the most appropriate input device. Error Avoidance and Error Detection:

In this phase is to be taken care to ensure that data remains accurate form of data phase in which it is registered to the stage in which data is received by the system. This can only be achieved through careful control any time information is treated. Although every effort is made to avoid the appearance of mistakes, still a small part of the error is always likely to happen, these types of errors can be detected using validations to check data information. Data Validation(Scott Raeburn, 2008):

Procedures are designed to detect errors in the data at a lower level of detail. Validations are included in the system data in almost any area where there is an opportunity for the user to commit errors. System will not accept invalid data. Whenever invalid data is keyed in, immediately makes the user system and users must key in the data again the system will only accept data if the data is accurate. Validations are included when necessary. User Interface Design (Scott Raeburn, 2008):

The system is designed to be a user of a friendly. In other words the system is designed to communicate effectively with users. The system is designed with popup menu. It is essential to consult users of the system and to discuss their needs, while designing the user interface. User interface system can be classified by User started in early user interface, controls the progress of users / computer dialogue. In computer-start interface, the computer selects the next stage in the interaction. User interfaces fall classes begin withdrawal approximate:

Interfaces Command run: In this type of user interface input commands or actions that are interpreted by computer.

Format oriented interface: the user calls up an image to form his / her screen and fill in the form. Format oriented interface was chosen because it is the best solution. Computer interface design (Scott Raeburn, 2008):

The computer guides computer interfaces starting the user's progress / computer dialogue. Information displayed and answer computer user takes action or show information. Computers in the following - start interfaces are used:

System user selects a menu; alternatives.

Question - answer kind of computer dialogue system, asking questions and taking action based on the basis of user response.

Right from the beginning the system will be driven menu, opening menu shows options available. Choose an option gives another popup menu with more options. In this way any possibility of leading users of the data entry form where users can key in data.

3.5.2 Performance Requirements:-

Performance is measured in terms of output offered by the application. Requirements specification plays an important role in the analysis of a system. Only when specification requirements are given properly, it is possible to design a system that will suit the environment necessary. It lies mainly in the existing system users to give specifications request because they are people who in the end use system. This is because the requirements are known during the initial stages so that the system can be designed in accordance with these requirements. After designed of the system, It is very difficult to change the system and on the other hand designing a system which does not cater for the requirements of users, it is useless. System requirement specification can be said given as follows:

The system should be able to interface with existing system.

The system should be accurate.

The system should be better than the existing system.

The existing system is completely dependent on the user to perform all tasks.