Monday, 26 August 2019

What is SQL? Why it is needed

SQL (pronounced "ess-que-el") stands for Structured Query Language. SQL is used to communicate with a database. According to ANSI (American National Standards Institute), it is the standard language for relational database management systems. SQL statements are used to perform tasks such as update data on a database, or retrieve data from a database. Some common relational database management systems that use SQL are: Oracle, Sybase, Microsoft SQL Server, Access, Ingres, etc. 
Although most database systems use SQL, most of them also have their own additional proprietary extensions that are usually only used on their system. However, the standard SQL commands such as "Select", "Insert", "Update", "Delete", "Create", and "Drop" can be used to accomplish almost everything that one needs to do with a database. This tutorial will provide you with the instruction on the basics of each of these commands as well as allow you to put them to practice using the SQL Interpreter.
  1. Allows users to access data in relational data base management system
  2. Allows users to describe the data.
  3. Allows users ti define the data in the data base and manipulate that data.
  4. Allows to embedded with in other languages using SQL modules, libraries, per-compilers.
  5. Allows users to create and drop data base and tables.
  6. Allows users to create view, stored procedure, functions in a database.
  7. Allows users to set permission on tables, procedures and views.
Features of SQL
  1. Accepts SQL statements from file. It provides a line editor.
  2. It provides format, iteration and file commands.
  3. Format query design and display reports on the screen.
  4. It supports control environment settings.
  5. It access remote and local data base.


Saturday, 24 August 2019

Requirements Elicitation and Analysis Process in Software Engineering

It’s a process of interacting with customers and end-users to find out about the domain requirements, what services the system should provide, and the other constrains.

It may also involve a different kinds of stockholders; end-users, managers, system engineers, test engineers, maintenance engineers, etc.

The requirements elicitation and analysis has 4 main process

We typically start by gathering the requirements, this could be done through a general discussion or interviews with your stakeholders, and also it may involve some graphical notation.

Then you organize the related requirements into sub components and prioritize them, and finally, you refine them by removing any ambiguous requirements that may rise from some conflicts.

Here are the 4 main processes of requirements elicitation and analysis.

It shows that it’s an iterative process with a feedback from each activity to another. The process cycle starts with requirements discovery and ends with the requirements document. The cycle ends when the requirements document is complete.

1. Requirements Discovery

It’s the process of interacting with, and gathering the requirements from, the stakeholders about the required system and the existing system (if exist).

It can be done using some techniques, like interviews, scenarios, prototypes, etc, which help the stockholders to understand what the system will be like.

Gathering and understanding the requirements is a difficult process

That’s because stakeholders may not know what exactly they want the software to do, or they may give un-realistic requirements.

They may give different requirements, which will result in conflict between the requirements, so we have to discover and resolve these conflicts.

Also there might be some factors that influence on the stakeholder’s decision, like for example; managers at a company or professors at the university want to take a full control over the management system.


In Interviews, requirements engineering teams put the questions to the stakeholder about the system that’s currently used, and the system to be developed, and hence they can gather the requirements from the answers.

The questions fall under two categories:
  1. Closed-Ended questions: A pre-defined set of question.
  2. Open-Ended questions: There is no a pre-defined expected answer, they are more of generic questions. It’s used to explore an issue that’s not clear in a less structured way.
In practice, interviews usually use mixture of both. Usually, start with the open-ended questions, and then use the closed-ended questions to be more specific about some requirements that aren’t clear yet.
Interviews are good to get an overall understanding of what stakeholders need, how they might interact with the new system, and the difficulties they face with the current system.

However, interviews aren’t so helpful in understanding the domain requirements. This is for two reasons:
  1. Domain requirements may be expressed using special domain terminologies, and software engineers often find it difficult to understand and it’s easy for them to misunderstand.
  2. Sometimes stakeholders won’t tell you some requirements because they assume it’s so fundamental and it doesn’t worth mentioning, or they find it difficult to explain, which won’t be taken into consideration in the requirements.
 Use Cases and Scenarios

1)    The use cases and scenarios are two different techniques, but, usually they are used together.
2)    Use cases identify interactions between the system and its users or even other external systems (using graphical notations), while a scenario is a textual description of one or more of these interactions.
Use case involves some symbols to describe the system:

  1. Actors: Are those who interact with the system; human or other systems
  2. Interaction (Use Case): It denotes the name of the interaction (verb). It’s represented as a named ellipse.
  3. Connection: Lines that links between the actors and the interactions.
  4. Include Relationship: It denotes a connection between two interactions when an interaction is invoked by another. As an example, splitting a large interaction into several interactions.
  5. Exclude Relationship: It denotes a connection between two interactions when you want to extend an interaction by adding an optional behavior, but you can use the main interaction on it’s own without the extending interaction.
Now, we are going to use scenarios to describe the interactions in each use case textually. They should have a format and include the following:

  1. A description of the initial situation.
  2. A description of the flow of the events or interactions with the system
  3. A description of the exceptions, or in other words, what can go wrong, and how it can be handled.
  4. Any concurrent activities should be mentioned
  5. A description of the final state.
Here is the example for a scenario for the use case example above.

2. Requirements Classification and Organization

  • It’s very important to organize the overall structure of the system.
  • Putting related requirements together, and decomposing the system into sub components of related requirements. Then, we define the relationship between these components.
  • What we do here will help us in the decision of identifying the most suitable architectural design patterns.

3. Requirements Prioritization and Negotiation

We previously explained why eliciting and understanding the requirements is not an easy process.
One of the reasons is the conflicts that may arise as a result of having different stakeholders involved. Why? because it’s hard to satisfy all parties, if it’s not impossible.

This activity is concerned with prioritizing requirements and finding and resolving requirements conflicts through negotiations until you reach a situation where some of the stakeholders can compromise.

We shouldn’t reach a situation where a stakeholder is not satisfied because his requirements is not taken into consideration.

Prioritizing your requirements will help you later to focus on the essentials and core features of the system, so you can meet the user expectations. It can be achieved by giving every piece of function a priority level. So, functions with higher priorities need higher attention and focus.

4. Requirements Specification

The requirements are then documented.

Feasibility Study in Software Engineering

The purpose of feasibility study is not to solve the problem, but to determine whether the problem is worth solving. A feasibility study is a short, focused study that aims to answer a number of questions.
  1. Does the system contribute to the overall objectives of the organization?
  2. Can the system be implemented using current technology and with given coast and schedule constraints?
  3. Can the system be integrated with the other systems which are already in place?
The main aim of the feasibility study activity is to determine whether it would be financially and technically feasible to develop the product. 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 data required to be produced by the system as well as various constraints on the behavior of the system.

Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include :
  1. The facility to produce outputs in a given time.
  2. Response time under certain conditions.
  3. Ability to process a certain volume of transaction at a particular speed.
  4. Facility to communicate data to distant locations.

In examining technical feasibility, configuration of the system is given more importance than the actual make of hardware. The configuration should give the complete picture about the system’s requirements:

How many workstations are required, how these units are interconnected so that they could operate and communicate smoothly?

What speeds of input and output should be achieved at particular quality of printing.

Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as Cost / Benefit analysis, the procedure is to determine the benefits and savings that are expected from a proposed system and compare them with costs. If benefits outweigh costs, a decision is taken to design and implement the system. Otherwise, further justification or alternative in the proposed system will have to be made if it is to have a chance of being approved. This is an outgoing effort that improves in accuracy at each phase of the system life cycle.

Operational Feasibility

This is mainly related to human organizational and political aspects. The points to be considered are:
  1. What changes will be brought with the system?
  2. What organizational structures are disturbed?
  3. What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time?
This feasibility study is carried out by a small group of people who are familiar with information system technique and are skilled in system analysis and design process.

Proposed projects are beneficial only if they can be turned into information system that will meet the operating requirements of the organization. This test of feasibility asks if the system will work when it is developed and installed.

Scribe to Youtube Channel


Find Us On Facebook

C Programming


C++ Tutorial


Java Tutorial


software engineering


MS Office


Database Management