System Analysis and Design

The system should be considered as a whole.

It should be created by designing the system components and their roles. The processes that make up the system, its data, software, hardware and, of course users should be considered together. With the right and holistic approach, different technologies work in harmony and productivity increases.

For this reason, perhaps the most important point of software development projects is system analysis. This process determines what will be done in the project and the boundaries of the work. All visible and invisible costs are determined by the decisions to be taken at this stage.

Determining customer expectations is never enough to meet with senior management. We start by interviewing all users of the system to be developed and determining their expectations. At this stage, we use proven methods to speak the same language as our customer. We create UML diagrams with the notes we take during the analysis phase and the system design phase, and with client meetings.

We create design drawings and prototypes to make sure our customers understand us and our customers correctly. Together with our client, we go over these printouts and approve the technical details of the project.

Determining the Business Process

We listen to our customer's work first and then monitor it on site. We take notes, collect forms and model the data flow. We identify and diagram the business process of our customer, respectively. At this stage, we collect new ideas that our customer will add and determine the new business process.

Sometimes, our customer is starting a new job and there are points that even he has not decided yet. In such cases, we make the design as variable as possible and keep up with our customer so that changes can be managed.

User Interface Designs

Each application has a user. Designing and developing interfaces where users communicate with software is a different expertise. It requires mastery of different technologies used in different types of applications.

Before starting the development of interfaces for any application, we create wireframes (draft drawings) and share them with our customers. The notes we receive are details that were not conveyed during the transfer of expectations. We take all our notes, update the drawings and finalize the screen designs.

System Principles

Security, workflow, etc. establishing principles on issues shortens the taking of initiative and therefore the development process. When we need to take decisions on issues that were not discussed at the meetings, we attach strict importance to compliance with the principles. These policies can be on various issues such as processing speed, password length, user privileges, data sharing, formats.

Cost Management

The cost of developing a project is the tip of the iceberg. Calculating and reducing the lifetime cost depends on the decisions taken at this stage. Hidden costs often cause projects to fail.

Hardware and Communications

A camera, temperature sensor, bluetooth headset or automatic door; hardware is controlled by software. Embedded software on hardware can communicate with other software and become part of a system.

Data Processing

A word, an image, a number or all together or singularly should be processed. There is no room for inexperience when performing tasks such as storage, querying, protection, and some situations are irreversible.