Best method to create software modules for usuability by others

Dear All,

I am working in organization as Sr. Design Engineer. Our major problem is
to have standard modules to be shared between all software engineers. I
dont want all to write their own code, Can there be any method by which
code can be shared by all without allowing others to modify the proven
part, what i mean is only application layer should be modifiable to others
- basic core should remain unchanged.

Regards,
Priti

On 23 Apr, 04:46, "pritiselec" <pde...@selec.com> wrote:
> Dear All,
>
> I am working in organization as Sr. Design Engineer. Our major problem is
> to have standard modules to be shared between all software engineers. I
> dont want all to write their own code, Can there be any method by which
> code can be shared by all without allowing others to modify the proven
> part, what i mean is only application layer should be modifiable to others
> - basic core should remain unchanged.
>
> Regards,
> Priti

Supply compiled modules that can be linked into their programs?

leon

On Wed, 22 Apr 2009 22:46:00 -0500
"pritiselec" <pdesai@selec.com> wrote:

> Dear All,
> 
> I am working in organization as Sr. Design Engineer. Our major
> problem is to have standard modules to be shared between all software
> engineers. I dont want all to write their own code, Can there be any
> method by which code can be shared by all without allowing others to
> modify the proven part, what i mean is only application layer should
> be modifiable to others
> - basic core should remain unchanged.
> 
> Regards,
> Priti

Yes, fiat.  Provide them with the code that is to be shared, and tell
them not to change it.

-- 
Rob Gaddi, Highland Technology
Email address is currently out of order

pritiselec wrote:
> 
> I am working in organization as Sr. Design Engineer. Our major problem is
> to have standard modules to be shared between all software engineers. I
> dont want all to write their own code, Can there be any method by which
> code can be shared by all without allowing others to modify the proven
> part, what i mean is only application layer should be modifiable to others
> - basic core should remain unchanged.

Assuming you are using C, write re-entrant functions in pure
standard C code.  For other languages, use the ISO standard for
that language.  Avoid proprietary languages, such as C#.

-- 
 [mail]: Chuck F (cbfalconer at maineline dot net) 
 [page]: <http://cbfalconer.home.att.net>
            Try the download section.

pritiselec wrote:

> I am working in organization as Sr. Design Engineer. Our major problem is
> to have standard modules to be shared between all software engineers. I
> dont want all to write their own code, Can there be any method by which
> code can be shared by all without allowing others to modify the proven
> part, what i mean is only application layer should be modifiable to others
> - basic core should remain unchanged.

Others have suggested providing compiled libraries and house rules.

I recommend guidelines for designing and documenting modules so that 
they don't carry unneeded features or constraints to allow easy reuse.
Also, publish each module with a test driver to verify operation.

-- 
Thad