Ved International Discussion Board

Modular Programming

Go down

Modular Programming Empty Modular Programming

Post by jp2012 on Fri Aug 02, 2013 8:26 am

Modular programming is a software design technique that increases the extent to which software is composed from separate parts, called modules. Conceptually, modules represent a separation of concerns, and improve maintainability by enforcing logical boundaries between components. Modules are typically incorporated into the program through interfaces. A module interface expresses the elements that are provided and required by the module. The elements defined in the interface are visible to other modules. The implementation contains the working code that corresponds to the elements declared in the interface.

Languages that formally support the module concept include IBM/360 Assembler, COBOL, RPG and PL/1, Ada, D, F, Fortran, Haskell, Pascal (some derivatives), ML, Modula-2, Erlang, Perl, Python and Ruby. The IBM System i (aka AS/400 and iSeries) also uses Modules in RPG, COBOL and CL, when programming in the ILE environment.

Modular programming can often be performed even where the language lacks explicit syntax or semantics to support modules. The use of libraries 'hooked together' by a linker are a common mechanism for combining parts of the software into a whole from the separately compiled modules.

Module Interconnection Languages

Module interconnection languages (MILs) provide formal grammar constructs for deciding the various module interconnection specifications required to assemble a complete software system. MILs enable the separation between programming-in-the-small and programming-in-the-large. Coding a module represents programming in the small, while assembling a system with the help of a MIL represents programming in the large. An example of MIL is MIL-75.
jp2012
jp2012
Worker
Worker

Posts : 145
Join date : 2013-06-30
Location : Japan

Back to top Go down

Back to top


 
Permissions in this forum:
You cannot reply to topics in this forum