Decomposition of software into components

dc.contributor.author	Parnas, David Lorge
dc.date.accessioned	2009-03-03T14:27:44Z
dc.date.available	2009-03-03T14:27:44Z
dc.date.issued	2003
dc.identifier.uri	http://hdl.handle.net/10344/119
dc.description	non-peer-reviewed
dc.description.abstract	Most software products are too large to be completed by a single person in a short period. To make the development manageable, the software must be divided into components that can be developed (and later maintained) separately. Each component will be a work assignment for a team or individual. It is often thought that this decomposition is a management decision, determined primarily by the talent available. This lecture explains that the decomposition is a critical design decision to be made on the basis of simple technical criteria, which will be stated and illustrated. The result is a very unconventional, but easily maintained, design.	en
dc.language.iso	eng	en
dc.subject	software	en
dc.title	Decomposition of software into components	en
dc.type	Report	en
dc.type.supercollection	all_ul_research	en
dc.type.restriction	none	en
dc.contributor.sponsor	SFI
dc.relation.projectid	01/P1.2/C009
dc.relation.projectid	03/CE3/1405

Files in this item

Name: 09sqrl1004.pdf

Size: 106.7Kb

Format: PDF