Large enterprises typically own and operate a large number of software applications either of the shelf, developed in-house or inherited through mergers and acquisitions. Applications can be of heterogeneous e.g. they are written in the same language(s) or they use the same data storage mechanisms and formats. They may also run on the same operating
Category: Software Engineering
The linear software processes come from manufacturing goods. In the past, software was expensive. Virtually all linear software development models suffer from several key disadvantages: limited (or none) client interaction limited (or none) client feedback limited (or none) adaptability to changing requirements In this article, I will explore the 3 fundamental processes: Waterfall V-Model Sawtooth
Software testing used to be one of the most underrated area in software development process. Indeed, it is not even covered at the undergraduate level at university (thanks BCS). This article provides an introduction into software testing. It covers: what software testing is, types of testing as well as what and when you should test?
I had a chance to get my hands on the Software Estimation - Demystifying the Black Art by Steve McConnell. It is a fantastic and well-written book. I thought I would share some of the key things I learnt. This article is the 1st part of a series of relatively short articles summing up the
The factory is one of the most popular design patterns out there. It is used to simply the creation of the objects of different classes that inherit from a common super-class (or interface X) depending on some condition. The Recipe In order to create a factory for a class X: Create an XFactory class Add
Cohesion is a measure of the degree to which the elements of a module belong together. Yourdon & Constantine in Structured Design, 1979 In essence, cohesion is a measure of ensuring that one element (one class) has a single responsibility. Measuring cohesion is tricky (as pretty much everything else in SE). The metrics tend to
Singleton is also a very popular design pattern, although when not used appropriately it does become an anti- pattern. It is used when we need an object to be unique and easily accessible from all parts of the application e.g. database handler or loggers are frequently used. It is often considered an anti-pattern because is
Callback design pattern allows us to avoid "freezing" the rest of the application if a method takes too long to return. It is very useful if running computationally-expensive or time unpredictable methods. It does generally involve running in a separate thread/task. The solution involves creating IXCallback interface which contains method called whn the slow operation
Command stack is a design pattern if we need to support for undo/redo operations. There are two aspects to this design pattern ICommand interface where we can define the behaviour of the execution and undo operation and a CommandStack which is a generic. Create an ICommand interface with methods execute() and undo() All undoable/redoable actions
Listener design pattern (also known as Subscriber/Observer) is a 'well-proven' technique for asynchronous message passing. It is used when the client needs to be notified when 'something interesting' happens to another object (of class X) in a passive manner (i.e. the client is not checking every so often (pulling) in the state has changed). The
Search
Categories
- .NET (21)
- Android (7)
- AngularJS (1)
- ASP (6)
- Azure (1)
- Bootstrap (2)
- Data Structures (2)
- Design Patterns (5)
- Docker Swarms (1)
- Entity Framework (8)
- Estimation (2)
- Ethics (1)
- Feuilleton (1)
- FHIR (1)
- HTML & CSS (5)
- Java (6)
- jQuery (4)
- Model Driven Engineering (1)
- MongoDB (6)
- Nginx (1)
- Oracle (1)
- Primitive Integration Patterns (1)
- Semantic UI (1)
- SEO (1)
- SOA (1)
- Software Engineering (1)
- Software Processes (1)
- SQL Server (3)
- System Architectures (7)
- Test-Driven Development (2)
- Ubuntu (1)
- Uncategorised (9)
- Visual Studio (3)
- WCF (5)
- WinForms (1)
- Wordpress (1)
- WPF (4)