Posted by: ahmedashfaque | March 14, 2018

Technical support software product free download

Today I have completed design and implementation of a software product which can be used for providing technical support. This software product is part of my effort to provide many software products to students and budding software engineers so that they can learn how software products are built. I have provided complete documentation as well as source code free of cost. You can download them from this website from the software engineering page – I am also providing links to the files below:

  1. Java Server page files
  2. Java class files
  3. database design
  4. Technical documentation

This effort is part of my book “Software Engineering in the Agile World“. This book has become a textbook at many universities in countries including USA, India, Bangladesh, Australia, Canada, Jordan, UAE, Israel, Pakistan etc. Professors from around the world are praising this book for its simple and easy to understand language, excellent linkage between software engineering processes and Scrum processes, excellent object oriented design and programming coverage etc.


Posted by: ahmedashfaque | January 26, 2018

Software Engineering in the Agile World

I love doing 2 things in life: writing books and creating software products. The twain meet through my books and accompanying software products. I have been writing textbooks on subjects related to software engineering for the last 10 years. My previous book “Foundations of software engineering” was received well at many universities in USA, India, Canada, Australia, UAE, Nigeria, Jordan, Israel, Malaysia and universities in many other countries.

I have written my new book “Software engineering in the Agile World” based on the feedback I received from many professors from Universities around the world. Some important features in my new book include:
* Hands on approach to learning software engineering,
* Easy to understand object oriented programming concepts,
* Database programming including Entity relationship diagram,
* Model-view-controller architecture,
* Building a software product as a Scrum project,

* Use of agile models (Scrum) in building software products, etc.

I have used an easy to understand language in writing my book so that it is easy to grasp even difficult concepts of software engineering by almost anyone. No prior knowledge in software engineering including software programming is assumed from readers of my book to understand the concepts provided in my book.

A complete case study to build a complete software product is provided in my new book “Software Engineering in the Agile World”. The case study is based on creating a smart city system which will provide information about various facilities available in a city (parks, zoos, museums, restaurants, malls, colleges, libraries, industries, hotels etc.). All the requirement specifications, software architecture and software design is provided in the book. The source code of this software product can be downloaded from my website This case study is based on Scrum. The software product is built incrementally. The Release and Sprint plans have been created accordingly (there are 10 Sprints in 3 Releases of the software product). I have also provided the design and source code for this project on my Google drive. To access my google drive, you will have to send an email to me as all material there is not in public domain.

A recorded video lecture series on a course in software engineering is provided on my youtube channell. This lecture series is completely based on my book. All the videos are contained inside my youtube channel
I have also provided all the instructions (including youtube videos at the channel mentioned in the above link) as to how to install the source code of the software product and run the application. If you still find difficulties then you can send me an email and I will help you out.

More case studies based on object oriented software design and Scrum are available on my website ((given above) and on my Google drive. I will also keep building some more case studies on new technologies (mobile platforms, Artificial Intelligence etc.). All this material will become available on my website and Google drive.

You can buy my book from Amazon. The landing page is provided at The book comes in 2 formats: Kindle and paperback versions.

Warm Regards

Ashfaque Ahmed,


Posted by: ahmedashfaque | September 29, 2017

Why Agile is beautiful?

In Agile methods of developing software products; the emphasis is on thinking small at a time. Project teams work on developing small software products at a time. The small software product referred here is actually a set of software product features, which can be developed and can be deployed within a short period of time (1 weeks to 4 weeks). This is an enormous gain on traditional software development methods which used to take 6 months – 1 year – or even many years.

In many cases, by the time, the software product was ready, it had already become obsolete. You can easily imagine this kind of scenario where a software product being developed took 2 years to complete. By that time many changes may already have occurred in technology (mobile technology including operating system etc.) or business processes (tax system, company focus etc.). So taking such a long time in developing a software product was always a bad idea (may be good when things were not changing that fast. Some 50 years ago or so).

Agile methods changed all that. Now project teams do not consider to build a large software product over a long period of time. Instead they build small increments over a small time frame of some weeks. These small increments in software product are actually some software product features which are developed as per current market demand. This means that software development is always in synch with the market. The beauty lies in the fact that, these small increments in the software product are always executable and thus are a new version of the software product. These software product versions are shippable and can be used  by end users.

Posted by: ahmedashfaque | August 26, 2017

Smart city system project source code

Source code for Smart city system:

I have created another case study for my book “Foundations of software engineering”. I am giving the source code for this software product free to everyone so that people can learn how to build good software products. You can download it freely from the software engineering page.

I have ensured that there are no error in the software product itself. But the source code files may create problems while installation as they are on Microsoft word file. java is very case sensitive and so if any file names have uppercase letters then please make them all lower caps.

The entire source code of the Smart city system is contained in the following Microsoft word files. You can download these files and then separate out various web pages and class files. The web page names are given and below them is the code. Just copy the content of each of the file on a separate HTML page if it is a jsp file, In case of java files, create a package named “smart_city” and create java files as per the java file names given in the java class files document and then paste appropriate source code in each of the class files.

There is also a database creation script file named “smart-city-database.doc”. Install Oracle database and create a user. For this user create the database tables and sequence as given in this document. I have created a user with user name as “city” with a password “city”. If you create a user with different user name and password then provide those user name and password in the “” class file.

If you have problems in installation after downloading then you can send me a mail at and I will try to help.

Download these installation files here:

smart city JSP files

Smart city class files

Smart city technical documentation

Smart city database script

Posted by: ahmedashfaque | July 26, 2017

Software programming – a challenge?

Recently I was working on a project and came on a peculiar problem. I had a single character value coming from method and needed to check its value in another method inside another class.

In Java, there are 2 types of variables dealing with strings. One variable deal with only one character. The other variable deals with strings consisting of more than one character. Generally the string variable type should also be handle single characters. This is the general common sense. But not so in Java.

I had this single character variable value coming from a JSP (Java Server Pages) file. I had to check this value inside a compiled Java class file. I had defined a variable of string type in JSP file and in JSP there is no problem. So I had also defined a variable in my Java class as a string type to check its value.

This program was part of a dynamic web project. I was using Tomcat as the application server. When I ran the program to test i was getting a null pointer exception error in the program. I checked from where this error was coming. I found that the program was not correctly evaluating the checking of the character variable and thus wrongly executing the next piece of code and giving error.

So I had to change the variable type to character from string. When I ran the program, this time it was not giving error.

Programming in any case is not easy even when you have all the tools to debug and test and get error description. Even when your logic is correct, your program may not run correctly due to these small compiler problems and you need to be careful.

Posted by: ahmedashfaque | June 12, 2017

What is a servlet in Java?

In object oriented programming languages, there is a need to create many classes resulting from the breaking of the entire software product. These classes keep all the programming code. Interaction among all these classes is done through method calls.

In Internet programming (software products hosted as websites), writing source code for the software product is a bit difficult. It is because, there are so many components (servers) get involved: you have a database server, an application server, a web server etc. Due to this type of architecture, all outcomes of computations which need to be displayed to the user should be in HTML format so that it can shown on the user web browser.

Due to these practical considerations, the source code needs to be written in scripting languages or a combination of compiled code and scripting languages. Since scripting languages are interpreted and thus run slow (performance issues will arise), writing source code in compiled classes is far better.

But when you have your source code inside a compiled class then accessing it from HTML or scripting web pages is impossible. There is only one way to do it. Define the path of the compiled code file in an XML file and then call this piece of compiled code in your scripts.

In Java programming, servlets are the compiled classes which can be called from scripts. All other compiled classes need to be accessed from scripts only through the servlet classes.

Posted by: ahmedashfaque | June 11, 2017

Mock up screens: best way to design software products

Designing software products is one of the most difficult tasks. Not many people can actually create designs for good software products.

Software designs usually consist of user interface designs, component diagrams, class diagrams, object diagrams, statechart diagrams, object interaction diagrams, sequence diagrams, entity relationship diagrams etc. when you need to create a software product using object oriented design and programming.

When I design software products, I usually create all these types of software designs. Apart from software designs, i also create use case diagrams to model the software requirements.

The best way to design software products is by creating mock up screens first. I always prefer this way because mock up screens can be used to create all other types of software design diagrams easily. Why it is so? Let us understand.

Mock up screens depict user screens and what the user will do or receive information after computations. Mock up screens can also be easily understood by both the business domain experts and the project teams. So there are no chances of misunderstanding between the 2 parties.

Generally for a software product, there are user screens from where the user will provide inputs. These inputs are then used for computations and after computation, the user is provided with computed results on their user screens. The user screens where the user is supposed to provide inputs can be used to create classes easily. All the fields on a user screen become properties of a class or classes. The screens which show computed results can be used to model behavior of classes. So most of the classes and their members can easily be captured from the mock up screens.

You can also create relationship among classes from the mock up screens. For example, if a user screen where computed results are shown uses field data from more than one class then the classes having members corresponding to those fields will have some kind of relationship.

Similarly if one user screen needs inputs from the user to show another screen requiring user inputs on this screen again then the class which will be built corresponding to this screen will definitely will be a child class of the class corresponding to the first screen.

Thus you will end up creating all classes, their members and their relationships from mock up screens. From mock up screens you can also create all other types of software design diagrams easily.

Posted by: ahmedashfaque | June 3, 2017

Importance of technical documentation

Everybody knows importance of user manuals. Without user manuals, using a software product by end users becomes very difficult as software products have become very large and complex. navigating and finding the right functionality to be used sometimes becomes laborious task. How transactions need to be performed using a software product also sometimes become tricky. user manuals become very handy in these scenarios.

For the technical support people, user manuals are also handy. But they need more than just user manuals. They need to know the internals of the software product do perform any kind of maintenance. So for them a complete knowledge about the software design is extremely important.

Very often, the project team which designed and built the software product become lazy and do not create the important software designs. In most cases, they know the design by heart and they have use for themselves for elaborate software designs. They consider it waste of time in doing this work. But when the software product is deployed and goes into production and users find defects or difficulty in using the software product then lack of good software design becomes a real handicap for the technical support team. In such a scenario, the software vendor is bound to face loss of revenue as users will not be able to use such a software product.

During software development process, software design often gets changed. The initial software design is not changed and updated whenever this change in software design happens. This is one of the most common problems on software projects.

Updated and complete technical documentation thus is very important for any software product to become successful.

There is a big gap between what a software product needs to do and how it is actually used by users. As long as the software product works fine, there is no problem for the support staff; no matter how it is being used by users.

Despite best efforts by the testing team, invariably a software product contains defects which prevents end users to use the software product effectively. Changing the source code and creating a new version of the software product to remove software defects is a big issue for software vendors. It is not possible to take software maintenance projects too often. They are costly too.

So what can be a good strategy for a software vendor in this scenario? Here comes, “Walk Arounds”. A walk around is a temporary solution which allows a software product to work effectively despite having defects. When a software defect is found in a software product then it is still possible to do transactions using the defective software product by using some other way of doing the same transaction. If a walk around is found and provided to end users then the end users can still use the defective software product effectively. So there is no immediate need to take a maintenance project to fix the defect.

Just recently I had ordered a medicine for my father for his brain tumor. It was shipped from Kentucky, USA and had to be delivered in India at my home address. For international parcels, the Indian government requires the shipping companies to get KYC (Know your customer) form filled by the customers. So I went on the website of the shipping company (DHL) and filled and submitted the KYC form online. The next day I received an email stating that my KYC form was rejected as I had put name of the shipper (Medicine Manufacturing company) as a consignee. The consignee should be the receiver of the parcel. So I went again on their website and tried to edit my KYC form. Unfortunately I discovered that the consignee field was not editable. So I phoned the shipping company (DHL) to know what to do. They told me that the consignee field indeed is not editable. But they provided me an alternative. They told me that i should use an alternate telephone number in the form and i will be able to submit the form with the correct consignee name. I immediately did it and my form was submitted successfully.

The shipping company used a walk around here when there was a defect in their software product (non-editable consignee field). This is a very good example of how to use a walk around.


Posted by: ahmedashfaque | April 30, 2017

Transparency of information – The limits

When any organization is computerized, one of the first things which is considered as a benefit is transparency. Computers ensure that all transactions are recorded cleanly and are available whenever required. All this transaction data can be kept for years and when required for purposes like tax records etc. can be shown. This aspect of computerization definitely curbs corruption and helps bring transparency.

But the other aspect of computerization is that all this sensitive data can be hacked and can be misused. For example, a person’s bank account information can be hacked and money can be stolen from his/her account. Then one more aspect is about privacy of people. If personal details of people can be hacked from a computer system then privacy of that person is compromised.

How to ensure that only the required information about people is taken and stored in a database? The other question is: how to ensure that only authorized people have access to data (information). The next question is: how to ensure that any sensitive data is never hacked.

Generally most governments like to get as much information about citizens as possible for many reasons. So through various computer systems they store information about citizens. But all this sensitive information about citizens is always in danger of being hacked by some unscrupulous people.

This fact puts a limit as to how much information any government can store about its citizens. If any private company stores sensitive information about its customers then again the misuse of this information is always a risk.

The best solution for these scenarios is 2 pronged: to put a limit as to how much information should be stored and how to provide a security mechanism so that this data is never hacked.

Older Posts »